From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Nathan Scott" <nathans@sgi.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Fri, 4 Aug 2006 12:43:54 +0200 [thread overview]
Message-ID: <9a8748490608040343p472591b8n9856f4afd78c9dfa@mail.gmail.com> (raw)
In-Reply-To: <20060804200549.A2414667@wobbly.melbourne.sgi.com>
On 04/08/06, Nathan Scott <nathans@sgi.com> wrote:
> On Fri, Aug 04, 2006 at 10:22:21AM +0200, Jesper Juhl wrote:
> > I just hit a BUG that looks XFS related.
> >
> > The machine is running 2.6.18-rc3-git3
> >
> > (more info below the BUG messages)
> >
>
> Thanks for reporting, Jesper - is it reproducible?
I don't know. I only tried that kernel once and when it broke on me
went back to the previous 2.6.11 kernel it was running before.
> Could you try this
> patch for me?
Sure.
The machine is semi-production, so there are limits to how much and
when I can test on it.
roughly wednesday and thursday each week I should be able to run
experimental kernels on it, the rest of the week the box needs to be
stable.
> We had a couple of other reports of this, but the earlier
> reporters have vanished ... could you let me know if this helps?
>
What I'll do is apply that patch to the 2.6.18-rc3-git3 kernel that
BUG'ed on me, then wednesday next week I'll boot the machine with the
patched kernel and it should be able to run for ~24hrs, then I can
report back to you if it crashed or not.
Or is there some other way you'd rather have me do it (subject to the
constraint that I can only do experiments one and a half to two days a
week) ?
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-08-04 10:43 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 [this message]
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
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=9a8748490608040343p472591b8n9856f4afd78c9dfa@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=xfs@oss.sgi.com \
/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®