Re: Lockups with 1.3.x kernels but not 1.2.8+Jun14. (fwd)

Todd Fries (
Wed, 2 Aug 1995 04:05:36 +0000 (GMT)

I just wanted to say that I have seen this behavior on 2 of my friend's
computers. They were both very frustrated and re-installed slackware on
their machines. One even went back to a.out and pre 1.3.x kernels.

Both were running totally elf, and I would venture a guess they had
compiled the kernel as elf. This behavior was completely unwarranted, as
earlier reboots had succeeded in mounting the root filesystem fine.

email, or for the exact system configuration,
but both machines were 486dx2 66's using ide controllers, and the ext2

Basically, you are not alone in this mysterious problem. I keep about 4-5
kernels available to lilo at boot time, so I'm crossing my fingers I don't
run into this.

> > I have been runnning Linux-1.2.8 + Jun14 patch for quite some time,
> > and it seems to work ok.
> > In the last week I have tried kernels 1.3.x (x=5,6,7,8,9,12) and all
> > give a total lockup just after mounting the root file system.
> I have the same problem !
> > I have tried gcc-2.6.3 and gcc-2.7.0 (both ELF version). I have tried
> Me too. I also tried A-OUT versions.
> > VFS: Mounted root (ext2 filesystem) readonly.
> When I use an A-OUT-Init, it prints in an endless loop of "No more
> processes left in runlevel" to my screen, after this message.
> The ELF-version of SysVInit the VFS:-message is the last I get.
> BUT it's not a problem of the AIC7xxx-Driver (whicht I thought first)
> since I had the same result with an old AHA1542b-SCSI-Adaptor.
> My hardware is a P60, PCI-ECS-Board (SiS-Chipset), AHA2940, ElsaWinner
> 1000PRO, 32MB Ram, SMC Elite Ultra.