From: Christian Weiske <cweiske@cweiske.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, 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 19:47:37 +0200 [thread overview]
Message-ID: <4516C4B9.5010509@cweiske.de> (raw)
In-Reply-To: <20060924095029.0262a2c8.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Andrew,
> I assume that you have confirmed that the machine doesn't have hardware
> problems? Does it run some earlier kernel OK?
The disks are both fine, they worked in other pcs without problems. The
ide controller card also worked fine, and the motherboard is new -
whatever you can expect with that. Maybe the combination is the problem.
I had some problems after running the machine for some days but I
thought that wasn't a hardware but more a kernel timing problem:
http://bugzilla.kernel.org/show_bug.cgi?id=6969
> And how long does it take to crash?
After starting the yacy daemon, it's about half a minute until the
"possible recursive locking detected" appears, and after one or two
minutes the whole thing crashes.
--
Regards/MfG,
Christian Weiske
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-09-24 17:46 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
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 [this message]
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=4516C4B9.5010509@cweiske.de \
--to=cweiske@cweiske.de \
--cc=akpm@osdl.org \
--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