linux-kernel - Re: 2.6.25.1: Kernel BUG at mm/rmap.c:669, General Protection Faults, and generic hard locks

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0805201919420.3783@blonde.site>
Date:	Tue, 20 May 2008 19:33:22 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Randy Johnson <theraptor2005@...il.com>
cc:	akpm@...ux-foundation.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.1: Kernel BUG at mm/rmap.c:669, General Protection Faults,
 and generic hard locks

On Tue, 20 May 2008, Randy Johnson wrote:
> 
> I did manage to steal another complete set of RAM and swapped it in,
> with no change. This still doesn't rule out potential issues with the
> MB (slots or controller); I've got a spare board coming in in the next
> week.

That does indeed reduce the likelihood that it's a hardware issue.

> In the mean time, I've been busy bisecting this one down.
> Unfortunately, it takes a good hour or two of heavy load to trigger
> sometimes, and I've got a good 15000 or so commits to get through, so
> it could still be a while.

If it is bisectable (rather than just taking much longer to go wrong
sometimes than others, so you never know when to say "good" or "bad"),
then that is well worth doing, from my point of view: thank you for
taking the trouble to do so.  But keep an open mind: if it really is
down to a hardware issue of some kind, it may turn out to be a waste
of your time, even though potentially helpful to me.

> I haven't been keeping any traces from
> these, even if I could get them (which typically I can't). Would they
> still be useful even if they're from random commits?

They might be: the more information you can give us the better.
So if you do get something interesting in the logs, please do send
it over, with a note of the head commit at that point.  Please then
also send your .config, and which version of compiler you're using.

Thanks,
Hugh
--
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/