[Top] [All Lists]

Re: kernelcrash during root filesystem recovery

To: linux-xfs@xxxxxxxxxxx
Subject: Re: kernelcrash during root filesystem recovery
From: Thomas Graichen <news-innominate.list.sgi.xfs@xxxxxxxxxxxxx>
Date: 1 Dec 2000 08:09:25 GMT
Distribution: local
Organization: innominate AG, Berlin, Germany
References: <20001130202247.A24118@s2y4n2c.de> <3A26F641.45226EF7@thebarn.com>
Reply-to: Thomas Graichen <graichen@xxxxxxxxxxxxx>
Reply-to: thomas.graichen@xxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.0-XFS-test10 (i686))
just a very trivial idea (maybe wrong): i think i have seen this then
i did not change the lilo entry for the xfs root from read-only to
read-write ... but i might be wrong ... but if that should be the
case the xfs code should maybe change it to read-write itself
(if that is possible)

just an idea


Russell Cattelan <cattelan@xxxxxxxxxxx> wrote:
> utz lehmann wrote:

> Hmm not good.
> We are going to need a bit more go to on.

> Can you get a backtrace from kdb?

> If you could hook up to a serial console that would
> help in capturing the output.

>> hi
>> i found a bug in yesterdays (2000-11-29) kernel (the test11 one).
>> i had powered off my computer without a clean shutdown. i do this very
>> often, no problems since month with xfs.
>> the kernel traped into kdb while recovering the xfs root filesystem. i write
>> the messages down from the screen, maybe there are typos:
>> XFS: WARNING: recovery required on readonly filesystem.
>> XFS: write access will be enabled recovery.
>> Staring XFS recovery on filesystem: ide0 (3,6) (dev:3/6)
>> Unable to handle kernel NULL pointer dereference at virtual address 00000008
>>  printing eip:
>> c016482b
>> *pde = 00000000
>> Entering kdb (currect=0xc125c000, pid1) Panic: Oops
>> due to panic @ 0xc016482b
>> eax = 0x00000000 ebx = 0xc12c3460 ecx = 0xc12c3460 edx = 0x00000000
>> esi = 0xc12c0e60 edi = 0x00000000 esp = 0xc125d940 eip = 0xc016482b
>> ebp = 0x00000000 xss = 0x00000018 xcs = 0x00000010 eflags = 0x00010246
>> xds = 0x00000018 xes = 0x00000018 origeax = 0xffffffff &regs = 0xc125d90c
>> i rebooted the machine with the same result.
>> rebooting with a kernel from 2000-11-14 works with no problems.
>> i made some tests with the buggy kernel:
>> clean shutdown works.
>> hardreset after "sync" works.
>> hardreset after booting without sync works.
>> hardreset during booting works.
>> hardreset during writing (cp -av /usr/src/linux /tmp) triggers the bug.
>> 4 times it traped into kdb, 1 time the kernel hangs.
>> booting with the older kernel always works.
>> my system:
>> K6-500, 128MB
>> xfs root filesystem on a ide disk.
>> hope that helps.
>> utz

technical director                                       innominate AG
clustering & security                             the linux architects
tel: +49-30-308806-13   fax: -77             http://www.innominate.com

<Prev in Thread] Current Thread [Next in Thread>