Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030410AbWLTWjS (ORCPT ); Wed, 20 Dec 2006 17:39:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030411AbWLTWjS (ORCPT ); Wed, 20 Dec 2006 17:39:18 -0500 Received: from smtp.nildram.co.uk ([195.112.4.54]:1767 "EHLO smtp.nildram.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030410AbWLTWjS (ORCPT ); Wed, 20 Dec 2006 17:39:18 -0500 X-Greylist: delayed 1400 seconds by postgrey-1.27 at vger.kernel.org; Wed, 20 Dec 2006 17:39:17 EST From: Alistair John Strachan To: Chuck Ebbert <76306.1226@compuserve.com> Subject: Re: Oops in 2.6.19.1 Date: Wed, 20 Dec 2006 22:15:50 +0000 User-Agent: KMail/1.9.4 Cc: linux-kernel@vger.kernel.org References: <200612201550_MC3-1-D5C7-74C6@compuserve.com> In-Reply-To: <200612201550_MC3-1-D5C7-74C6@compuserve.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612202215.50315.s0348365@sms.ed.ac.uk> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 714 Lines: 22 On Wednesday 20 December 2006 20:48, Chuck Ebbert wrote: [snip] > I'd guess you have some kind of hardware problem. It could also be > a kernel problem where the saved address was corrupted during an > interrupt, but that's not likely. Seems pretty unlikely on a 4 year old Via Epia. Never had any problems with it before now. Maybe a cosmic ray event? ;-) -- Cheers, Alistair. Final year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK. - 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/