From: David Newall <david@davidnewall.com>
To: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
Cc: Scott <linux-kernel@bluecamel.eml.cc>, linux-kernel@vger.kernel.org
Subject: Re: almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well
Date: Fri, 21 Dec 2007 01:08:54 +1030 [thread overview]
Message-ID: <476A7E7E.7030704@davidnewall.com> (raw)
In-Reply-To: <200712200653.28996.volker.armin.hemmann@tu-clausthal.de>
>>> On Montag, 17. Dezember 2007, you wrote:
>>>
>>> and another one, this time tainted with the nvidia module:
>>> 5194.130985] Unable to handle kernel paging request at 0000030000000000
>>> RIP:
Numbers like that don't suggest hardware faults. All those zeros: It's
far too round. Sounds very like software. In fact, it sounds like the
start of significant hardware region. And lo! there's a closed-source,
possibly buggy nvidia module. Try another; older or newer are equally good.
next prev parent reply other threads:[~2007-12-20 14:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 0:06 almost daily Kernel oops with 2.6.23.9 Hemmann, Volker Armin
2007-12-17 14:59 ` almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as well Hemmann, Volker Armin
2007-12-17 15:47 ` Hugh Dickins
2007-12-17 19:44 ` Hemmann, Volker Armin
2007-12-20 2:13 ` Hemmann, Volker Armin
2007-12-20 3:50 ` Scott
2007-12-20 5:53 ` Hemmann, Volker Armin
2007-12-20 14:38 ` David Newall [this message]
2007-12-20 18:37 ` Hemmann, Volker Armin
2007-12-20 21:48 ` Pekka Enberg
2007-12-20 22:13 ` Ingo Molnar
[not found] ` <1198134579.4429.10.camel@homer.simson.net>
2007-12-20 18:14 ` Hemmann, Volker Armin
2007-12-21 7:47 ` Mike Galbraith
2007-12-21 12:54 ` Hemmann, Volker Armin
2007-12-20 15:25 ` Stefan Richter
2007-12-20 18:12 ` Hemmann, Volker Armin
2007-12-20 19:04 ` Ingo Molnar
2007-12-20 20:29 ` Hemmann, Volker Armin
2007-12-21 2:09 ` Hemmann, Volker Armin
2007-12-21 11:19 ` Ingo Molnar
2007-12-29 23:03 ` Hemmann, Volker Armin
2007-12-20 19:06 ` Stefan Richter
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=476A7E7E.7030704@davidnewall.com \
--to=david@davidnewall.com \
--cc=linux-kernel@bluecamel.eml.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=volker.armin.hemmann@tu-clausthal.de \
/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®