mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: Scott <linux-kernel@bluecamel.eml.cc>
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: Thu, 20 Dec 2007 06:53:28 +0100	[thread overview]
Message-ID: <200712200653.28996.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <1198122641.8341.1.camel@oasis.donpoo.home>

On Donnerstag, 20. Dezember 2007, you wrote:
> On Thu, 2007-12-20 at 03:13 +0100, Hemmann, Volker Armin wrote:
> > 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:
>
> This really sounds like bad hardware. Either memory or the mobo/riser
> card the memory is on. You might try lowering the memory timings of your
> memory in BIOS. Try removing 1/2 of your memory. If it still remove the
> other 1/2 and put the first 1/2 back and try again.

if this is bad hardware why:

- didn't this show up earlier?

- did a several hour memtest run couple of weeks ago didn't show up anything?

- and does stuff like compiling all of kde 3.5.8 or the latest kde4 rc finish 
without any problems?

If it would be bad hardware, I should see segfaults left and right, right? but 
I don't see them.  In fact, apart from the oopses the system works fine - 
even with the oopses the system works fine, apart from the occasional stuck 
ps aux

And this messages:
[41160.823959] kio_http_cache_[25229] general protection rip:32621f1fe9 
rsp:7fff59a3d270 error:0
show up on closing konqueror tabs/Konqueror. There are no surprising exits, no 
apps vanishing. 

But I will run memtest86+ (or should I use memtest86?).

Glück Auf,
Volker

  reply	other threads:[~2007-12-20  5:53 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 [this message]
2007-12-20 14:38             ` David Newall
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=200712200653.28996.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --cc=linux-kernel@bluecamel.eml.cc \
    --cc=linux-kernel@vger.kernel.org \
    /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®