From: Ingo Molnar <mingo@elte.hu>
To: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, 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 12:19:21 +0100 [thread overview]
Message-ID: <20071221111921.GB687@elte.hu> (raw)
In-Reply-To: <200712210309.02865.volker.armin.hemmann@tu-clausthal.de>
* Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de> wrote:
> Ok, so after the holidays I will do the following:
>
> let memtest86+ run several hours. do a full backup&restore to switch
> to r3 and build an unpatched kernel. see if I can reproduce the oops
> with .21 and .22 (because AFAIR no oops with 21.. but I might be
> wrong).
>
> Not exactly in that order.
yeah, that would help. But generally it a big PITA to figure out such
bugs where there's no specific 'smoking gun' in the oopses themselves.
What usually happens is that people try to figure out a faster way of
triggering the bug - and then bisection can be done. But the hardware
must be eliminated first as the cause of the bug. Taking out half of the
RAM (i know it's painful ...) can help too in isolating RAM problems.
Ingo
next prev parent reply other threads:[~2007-12-21 11:19 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
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 [this message]
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=20071221111921.GB687@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--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