Problems with ac12 kernels and up

Problems with ac12 kernels and up

[John Chris Wren]

I have been running 2.4.4-ac11 for a few weeks, and decided to upgrade to
2.4.4-ac18. I applied the patches, compiled, and installed (all per usual),
and when booting, get a kernel panic at the point VFS is trying to mount the
root file system. I started working backwards to find the last kernel that
would boot. I got down to ac13, and the panics stopped, but I get the
following message:

Checking root filesystem. /dev/hde13 is mounted.
Cannot continue, aboorting.
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.

Same for ac12. I used the same config file I used for ac11 and previous ac
kernels. I then decided to try the 2.4.5 kernel, which worked fine. I then
applied the 2.4.5-ac1 patches, and got the above message, again.

The system is an Abit KT7A-RAID w/ a 1Ghz Athlon. The dmesg output link
below describes the drive configuration.  The BIOS is configured to boot
from the HPT-370.

As part of the test, I completely reinstalled the 2.4.4 kernel source,
applied the ac11 patch, and my config file, rebuilt and reinstalled. All
worked fine. Any thoughts on why this might be occurring?

I can provide any additional information as necessary. Here are the various
files:

http://jcwren.com/linux/config.txt - config file
http://jcwren.com/linux/dmesg.txt - ac11 dmesg log
http://jcwren.com/linux/lilo.txt - lilo.conf

I'm not smart enough to know how to capture the output for a kernel that
panics and halts. If I can provide any additional information for resolving
the problem, I would be happy to. Oh, and as best as I can tell before it
all scrolls by, the kernel reporting looks to be the same between all
kernels, with only the version being different.

--John

Re: Problems with ac12 kernels and up

[Alan Cox]

> Checking root filesystem. /dev/hde13 is mounted.
> Cannot continue, aboorting.
> *** An error occurred during the file system check.
> *** Dropping you to a shell; the system will reboot
> *** when you leave the shell.

That means the file system was mounted read/write at boot time. That normally
indicates a lilo misconfiguration however your lilo.conf looks 
correct.

Alan

RE: Problems with ac12 kernels and up

[John Chris Wren]

>
>> Checking root filesystem. /dev/hde13 is mounted.
>> Cannot continue, aboorting.
>> *** An error occurred during the file system check.
>> *** Dropping you to a shell; the system will reboot
>> *** when you leave the shell.
>
>That means the file system was mounted read/write at boot time. That
normally
>indicates a lilo misconfiguration however your lilo.conf looks
>correct.
>
>Alan

I've built the ac18 kernel with the serial console enabled, and dumped the
results (this is the one that kernel panics).

http://jcwren.com/linux/ac18.txt - ac18 dmesg dump
http://jcwren.com/linux/build.txt - sequence I'm using to build

The apparent interleaved garbage closer to the bottom is exactly what came
out on the console.  (Is linking to the dumps perferred over including it in
the mail, or would folks prefer to have the text included?  Since I'm not a
judge of exactly what you need to see, I'm not sure if 200 lines of dump
would be appropriate or not).

Just for good measure, I've installed the latest RH 7.1 LILO, mkinitrd, and
associated tools.

I also rebuilt the ac12 kernel, and tried again.  Same results as the quoted
text above.

--John

Re: Problems with ac12 kernels and up

[Alan Cox]

> http://jcwren.com/linux/ac18.txt - ac18 dmesg dump
> http://jcwren.com/linux/build.txt - sequence I'm using to build
> 
> The apparent interleaved garbage closer to the bottom is exactly what came
> out on the console.  (Is linking to the dumps perferred over including it in
> the mail, or would folks prefer to have the text included?  Since I'm not a

The link is fine..

> I also rebuilt the ac12 kernel, and tried again.  Same results as the quoted
> text above.

This looks a lot like the superblock changes not only broke reiserfs but also
initd usage.

Al ?

Re: Problems with ac12 kernels and up

[Jeff Garzik]

Alan Cox wrote:
> 
> > Checking root filesystem. /dev/hde13 is mounted.
> > Cannot continue, aboorting.
> > *** An error occurred during the file system check.
> > *** Dropping you to a shell; the system will reboot
> > *** when you leave the shell.
> 
> That means the file system was mounted read/write at boot time. That normally
> indicates a lilo misconfiguration however your lilo.conf looks
> correct.

On 'ac' kernels at MDK, only when initrd is used, we are seeing the root
filesystem mounted read-write, no matter what rdev and bootloader
settings are...  Things are fine with no initrd.

I looked at the root_mountflags usage and it looks ok, so I put it in
the "figure out later" pile.

Haven't yet verified if this 'ac' only problem....

-- 
Jeff Garzik      | Disbelief, that's why you fail.
Building 1024    |
MandrakeSoft     |

Re: Problems with ac12 kernels and up

[Alan Cox]

> I looked at the root_mountflags usage and it looks ok, so I put it in
> the "figure out later" pile.
> 
> Haven't yet verified if this 'ac' only problem....

Think I have it sussed. Time for -ac2

RE: Problems with ac12 kernels and up

[John Chris Wren]

>> I looked at the root_mountflags usage and it looks ok, so I put it in
>> the "figure out later" pile.
>>
>> Haven't yet verified if this 'ac' only problem....
>
>Think I have it sussed. Time for -ac2

I took down my Jerry Garcia poster, and put up an Alan Cox poster.
2.4.5-ac2 boots like a champ.   Thanks!  (will this make it into a
2.4.4-ac19 patch?)

-- John

RE: problems with ac12 kernels and up

[John Chris Wren]

>> http://jcwren.com/linux/ac18.txt - ac18 dmesg dump
>> http://jcwren.com/linux/build.txt - sequence I'm using to build
>>
>> The apparent interleaved garbage closer to the bottom is exactly what
came
>> out on the console.  (Is linking to the dumps perferred over including it
in
>> the mail, or would folks prefer to have the text included?  Since I'm not
a
>
>The link is fine..
>
>> I also rebuilt the ac12 kernel, and tried again.  Same results as the
quoted
>> text above.
>
>This looks a lot like the superblock changes not only broke reiserfs but
also
>initd usage.
>
>Al ?

If it's of any help, here's the System.map around that EIP:

c017f0d0 T floppy_eject
c017f100 t get_dma_residue
c017f150 t rd_make_request
c017f280 t rd_ioctl
c017f380 t initrd_read
c017f3d0 t initrd_release
c017f420 t rd_open
c017f4b0 t rd_release

--John