xfs
[Top] [All Lists]

Re: xfs recovery oops in 2.6.4-mm1

To: William Lee Irwin III <wli@xxxxxxxxxxxxxx>
Subject: Re: xfs recovery oops in 2.6.4-mm1
From: Steve Lord <lord@xxxxxxx>
Date: Fri, 12 Mar 2004 09:19:51 -0600
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20040312100025.GP655@xxxxxxxxxxxxxx>
References: <20040312100025.GP655@xxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.5 (X11/20040208)
William Lee Irwin III wrote:
> Console log attached. Remote kernel hacking -level access to the system
> for debugging can be arranged.

Hi,

I see this is a sparc, any chance you could provide disassembly of the
xfs_next_bit function. I wonder if it is playing up on this processor,
it makes use of ffs and we have had some architecture issues with it
before.

Not that I can read sparc assembler, but I can take a crack at it ;-)

Have you successfully used xfs on this box with older kernels, or is
this a new filesystem? Was this the first mount under 2.6.4-mm1?

Steve

> 
> -- wli
> 
> 
> mount(272): Oops [#1]
> 
> TSTATE: 0000000011009601 TPC: 00000000005414d0 TNPC: 00000000005414d4 Y: 
> 00000000    Not tainted
> 
> TPC: <xfs_next_bit+0x30/0xe0>
> 
> g0: 0000000000000000 g1: 0000000000000000 g2: 0000000000000000 g3: 
> 0000000000000000
>    
> g4: fffff800edc88140 g5: 0000000000000000 g6: fffff800ece10000 g7: 
> fffff80002cb6810
>    
> o0: ffffffffffffffff o1: ffff001da00f6300 o2: 0000000000000001 o3: 
> 0000000000000080
>    
> o4: 0000000000000080 o5: 0000000000200200 sp: fffff800ece12611 ret_pc: 
> 0000000000575004
> 
> RPC: <xlog_recover_do_reg_buffer+0xe4/0x160>
> 
> l0: 0000000000000001 l1: 0000000000000000 l2: 0000000000160929 l3: 
> 0000000000000001
>    
> l4: fffff800ee9ff334 l5: 0000000000000000 l6: 000000000000000f l7: 
> fffff800ef827fd0
>    
> i0: fffff800eed8c660 i1: fffff800ee9ff2e0 i2: fffff800ed007ac0 i3: 
> fffff800ee9ff320
>    
> i4: fffff80002cb7810 i5: fffff800eed04048 i6: fffff800ece126d1 i7: 
> 00000000005755c0
>    
> I7: <xlog_recover_do_buffer_trans+0x200/0x2e0>
> 
> Caller[00000000005755c0]: xlog_recover_do_buffer_trans+0x200/0x2e0
> 
> Caller[0000000000576428]: xlog_recover_do_trans+0x188/0x1a0
> 
> Caller[00000000005765b0]: xlog_recover_commit_trans+0x30/0x60
> 
> Caller[0000000000576700]: xlog_recover_process_data+0xe0/0x1e0
> 
> Caller[00000000005772fc]: xlog_do_recovery_pass+0x15c/0x680
> 
> Caller[00000000005778d8]: xlog_do_log_recovery+0xb8/0x120
> 
> Caller[0000000000577950]: xlog_do_recover+0x10/0x140
> 
> Caller[0000000000577b0c]: xlog_recover+0x8c/0xc0
> 
> Caller[000000000056f578]: xfs_log_mount+0x78/0x100
> 
> Caller[000000000057913c]: xfs_mountfs+0x53c/0xac0
> 
> Caller[000000000058000c]: xfs_mount+0x2cc/0x500
> 
> Caller[0000000000591d34]: vfs_mount+0x34/0x60
> 


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