linux-kernel - Re: almost daily Kernel oops with 2.6.23.9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Dec 2007 12:19:21 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Hemmann, Volker Armin" <volker.armin.hemmann@...clausthal.de>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org
Subject: Re: almost daily Kernel oops with 2.6.23.9 - and now 2.6.23.11 as
	well

* Hemmann, Volker Armin <volker.armin.hemmann@...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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/