linux-kernel - Re: 2.6.19.1: kernel BUG at mm/slab.c:2911!

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]

Date:	Tue, 13 Feb 2007 10:06:36 +0100
From:	Martin MOKREJS( 
	<mmokrejs@...osome.natur.cuni.cz>
To:	Christoph Lameter <clameter@....com>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19.1: kernel BUG at mm/slab.c:2911!

Christoph Lameter wrote:
> On Tue, 30 Jan 2007, Martin MOKREJS wrote:
> 
>> Hi,
>>   is this a known issue? Should I bother to upgrade to 2.6.19.2 if it contains the fix?
>> Thank you any help. It might be related to NFS. The machine in question is NFSv3 client,
>> udp. And used for computations. The process which died is from torque cluster management
>> package.
> 
>> 000: 00 00 00 00 fe ff ff ff fe ff ff ff 3a 00 00 00
> 
> The beginning of the slab was overwritten. The first two words should have 
> been list pointers. color offset is also invalid as is the pointer to the 
> slab memory.
> 
> Are you using cpu hotplug by chance?

No, it is a classical P4 machine, ASUS P4C800E-Deluxe motherboard. However, it might
have been related to the overclocked CPU. Although 12 other, exactly same machines are running
fine at the same over-clock I have decreased the settings. It did not happen since then.
So I believe it was a hardware issue. Thanks for the explanation.
Martin
-
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/