linux-kernel - Re: Kernel oops in 2.6.18.3 with RAID5

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.61.0702211744290.12039@yvahk01.tjqt.qr>
Date:	Wed, 21 Feb 2007 17:46:30 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Andrew Robinson <andrew.rw.robinson@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Kernel oops in 2.6.18.3 with RAID5

>
> Update: I think that you can ignore this error. I am getting
> segmentation faults when I attempt to rebuild the kernel. This is
> exactly the same problem I had with slackware 10.1 with the 2.6.10
> kernel. So I think it is a hardware issue. Memtest86 didn't show any
> errors after 35 passes, so I'll have to check the CPU and motherboard.

Googling for "iret exception: 0000" also reveals quite few
results (= one distinct), so this seems to be an issue that comes
up even less than now and then.


>> I was having instability with this machine before (slackware 10.1 with
>> 2.6.10 kernel) while compiling code (especially the kernel). I just
>> rebuilt is as a debian box. It never died in the raid array code
>> before though, just in gcc.

temperature problem?


Jan
-- 
-
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/