From: Arjan van de Ven <arjan@infradead.org>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel paging request at 0000000000002328 __d_lookup+0xc8/0x1d0
Date: Wed, 4 Feb 2009 07:11:36 -0800 [thread overview]
Message-ID: <20090204071136.2f682dc2@infradead.org> (raw)
In-Reply-To: <c4e36d110902040649v3810c96du1c84caa9052ef4c6@mail.gmail.com>
On Wed, 4 Feb 2009 15:49:52 +0100
Zdenek Kabelac <zdenek.kabelac@gmail.com> wrote:
> Hi
>
> Today I've got this ugly oops - my machine T61, 4GB of memory (checked
> with memtest), SMP, C2D
> kernel commit: 33bfad54b58cf05cfe6678c3ec9235d4bc8db4c2
>
> The only 'strange' thing I've been doing today is testing ext4 and its
> online resize functionality.
> But this oops happened somewhat later - so I'm not really sure whether
> there is some correlation.
>
> (Full kernel log follows)
if you have CONFIG_DEBUG_INFO enabled, you can run the oops through
http://www.kerneloops.org/download/markup_oops.pl (or
scripts/markup_oops.pl, but the 64 bit support is pending in a
maintainer tree) to turn this into an even better bug report...
... it will show exactly where in the code the oops was.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-02-04 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 14:49 BUG: unable to handle kernel paging request at 0000000000002328 __d_lookup+0xc8/0x1d0 Zdenek Kabelac
2009-02-04 15:11 ` Arjan van de Ven [this message]
2009-02-04 15:27 ` Zdenek Kabelac
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=20090204071136.2f682dc2@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zdenek.kabelac@gmail.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