public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Weiske <cweiske@cweiske.de>
To: linux-kernel@vger.kernel.org
Cc: reiserfs-dev@namesys.com, Ingo Molnar <mingo@elte.hu>,
	Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a
Date: Sun, 24 Sep 2006 11:11:02 +0200	[thread overview]
Message-ID: <45164BA6.60200@cweiske.de> (raw)
In-Reply-To: <20060923134244.e7b73826.akpm@osdl.org>


[-- Attachment #1.1: Type: text/plain, Size: 1652 bytes --]

Andrew,


>> I have a reproducible BUG on my server that occurs whenever disk usage
>> gets too high / too much swapping occurs (at least I think that is). The
>> box has one reiserfs filesystem of about 187GB size, the disk is on an
>> Epia 5000 board, between them is a Promise Ultra 100 PCI IDE controller
>> card.
> Do you think this bug is due to the 2.6.18 upgrade?

No. I already had it in 2.6.17.6.

> Have you run fsck across the filesystem(s)?
fsck at boot turns up
> ReiserFS: hde3: checking transaction log (hde3)
> ReiserFS: hde3: replayed 22 transactions in 0 seconds
> ReiserFS: hde3: Using r5 hash to sort names
nothing more

> Does the oops always look the same as this one?
No, not exactly the same. I attach three log files. If you diff them,
there will be about 30% of the lines different.

One thing I have to note is that the second Oops appears about 10
seconds after the first one.

> Please turn on the various CONFIG_DEBUG_* options, see if that turns up
> anything.
That indeed turns up something. The debug messages indicate that java
wants to lock something and gets stuck. Note that the messages until
"slab corruption" are printed first, and the others about a minute or
two later.

And I still can ping and do everything until the slab corruption occurs.
(Thus the other messages some minute later)


> It would be interesting to find out if enabling CONFIG_4KSTACKS makes this
> go away (although I'm not sure why).
Didn't try this yet, but will.

I put the logs in a tar.bz2 because I didn't want to flood the list with
a 200k message.

-- 
Regards/MfG,
Christian Weiske

[-- Attachment #1.2: dojo kernelpanic + debug.tar.bz2 --]
[-- Type: application/octet-stream, Size: 8522 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  parent reply	other threads:[~2006-09-24  9:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-23 15:56 2.6.18 BUG: unable to handle kernel NULL pointer dereference at virtual address 000,0000a Christian Weiske
2006-09-23 20:42 ` Andrew Morton
2006-09-23 20:39   ` Ingo Molnar
2006-09-24  9:11   ` Christian Weiske [this message]
2006-09-24  9:30     ` Christian Weiske
2006-09-24 10:19     ` Andrew Morton
2006-09-24 17:59       ` Ingo Molnar
2006-09-24 12:20   ` Christian Weiske
2006-09-24 16:50     ` Andrew Morton
2006-09-24 17:47       ` Christian Weiske
2006-09-25  4:14         ` Nick Piggin
2006-09-25 18:36         ` Christian Weiske
2006-09-25 21:26           ` Andrew Morton
2006-10-02 17:01             ` Christian Weiske
2006-10-03 14:20               ` Christian Weiske

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=45164BA6.60200@cweiske.de \
    --to=cweiske@cweiske.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=reiserfs-dev@namesys.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