Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422672AbXBUQqr (ORCPT ); Wed, 21 Feb 2007 11:46:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422678AbXBUQqr (ORCPT ); Wed, 21 Feb 2007 11:46:47 -0500 Received: from tmailer.gwdg.de ([134.76.10.23]:33551 "EHLO tmailer.gwdg.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422675AbXBUQqq (ORCPT ); Wed, 21 Feb 2007 11:46:46 -0500 Date: Wed, 21 Feb 2007 17:46:30 +0100 (MET) From: Jan Engelhardt To: Andrew Robinson cc: linux-kernel@vger.kernel.org Subject: Re: Kernel oops in 2.6.18.3 with RAID5 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Report: Content analysis: 0.0 points, 6.0 required _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1026 Lines: 27 > > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/