From: Nathan Scott <nathans@sgi.com>
To: Paul Slootman <paul+nospam@wurtel.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Thu, 24 Aug 2006 16:55:34 +1000 [thread overview]
Message-ID: <20060824165534.A3003989@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060823084210.GA7106@wurtel.net>; from paul+nospam@wurtel.net on Wed, Aug 23, 2006 at 10:42:10AM +0200
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 :-)
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.
> 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.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-08-24 6:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 8:22 Jesper Juhl
2006-08-04 10:05 ` Nathan Scott
2006-08-04 10:43 ` Jesper Juhl
2006-08-06 3:07 ` Tony.Ho
2006-08-06 4:05 ` Tony.Ho
2006-08-07 4:34 ` Nathan Scott
[not found] ` <3aa654a40608072039r2b5c5a19hbd3e68e4fee40869@mail.gmail.com>
2006-08-08 3:44 ` Nathan Scott
[not found] ` <9a8748490608080137k596a6290r3567096668449a64@mail.gmail.com>
2006-08-08 8:54 ` Nathan Scott
[not found] ` <9a8748490608100431m244207b1v9c9c5087233fcf3a@mail.gmail.com>
2006-08-10 12:25 ` Jesper Juhl
2006-08-10 22:35 ` Nathan Scott
[not found] ` <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
2006-08-10 22:52 ` Jesper Juhl
2006-08-11 8:33 ` Jesper Juhl
2006-08-11 10:25 ` Jesper Juhl
2006-08-14 2:00 ` Nathan Scott
2006-08-14 7:49 ` Jesper Juhl
2006-08-15 9:03 ` Nathan Scott
2006-08-15 11:42 ` Jesper Juhl
2006-08-16 1:26 ` Nathan Scott
2006-08-17 21:23 ` Jesper Juhl
2006-08-15 14:37 ` Chris Wedgwood
2006-08-15 14:47 ` Jan Engelhardt
2006-08-16 12:38 ` Paul Slootman
2006-08-16 22:47 ` Nathan Scott
2006-08-17 9:01 ` Paul Slootman
2006-08-23 8:42 ` Paul Slootman
2006-08-24 6:55 ` Nathan Scott [this message]
2006-08-24 9:07 ` Paul Slootman
2006-08-10 23:01 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060824165534.A3003989@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul+nospam@wurtel.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®