Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078

[Paul Slootman]

On Thu 24 Aug 2006, Nathan Scott wrote:
> On Wed, Aug 23, 2006 at 10:42:10AM +0200, Paul Slootman wrote:
> > 
> > I compiled 2.6.17.9 yesterday with gcc 4.1 (the previous kernel that
> > showed problems was 2.6.17.7 compiled with gcc 3.3.5), and the same
> > problem showed itself again, after 2.6.15.6 had run with no problems
> > whatsoever for 5 days.
> > 
> > I'll now give 2.6.16.1 a go (we have that kernel lying around :-)

That also fell over.

> Hmm, if there's no reproducible case, next best thing is a git bisect
> to try to identify potential commits which are causing the problem...
> not easy on your production server, I know.  I had believed this to be
> a long-standing issue though, I'm sure I've seen it reported before -
> we've never had any information to go on to try to diagnose it however.
> Jesper's rename hint is the most helpful information we've had so far.

To me it seems to have happened somewhere between 2.6.15.6 and 2.6.16.1 :)
I'll have to boot with 2.6.15.6 again and run that for a couple of days,
after that I'll try some kernel  2.6.15.6 < x < 2.6.16.1 (any
suggestions?)


> > BTW, what's the significance of the xfs_repair message
> > LEAFN node level is 1 inode 827198 bno = 8388608
> > (I see a lot more of these this time round).
> 
> It basically means a directory inode's btree has got into an invalid
> state, somehow.

Hmm, what version of xfs_repair is supposed to fix that? Because neither
the 2.6.20 version that comes with Debian nor the CVS version of August
10 which calls itself 2.8.11 makes it go away (i.e. multiple runs will
persistently show those lines).


thanks,
Paul Slootman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/