Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261348AbVDTG6B (ORCPT ); Wed, 20 Apr 2005 02:58:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261368AbVDTG6B (ORCPT ); Wed, 20 Apr 2005 02:58:01 -0400 Received: from ylpvm43-ext.prodigy.net ([207.115.57.74]:16513 "EHLO ylpvm43.prodigy.net") by vger.kernel.org with ESMTP id S261348AbVDTG55 (ORCPT ); Wed, 20 Apr 2005 02:57:57 -0400 X-ORBL: [67.124.119.21] Date: Tue, 19 Apr 2005 23:57:51 -0700 From: Chris Wedgwood To: Harish K Harshan Cc: linux-kernel@vger.kernel.org Subject: Re: i830 lockup Message-ID: <20050420065751.GA9791@taniwha.stupidest.org> References: <42225.203.197.150.195.1113980805.squirrel@mail.amrita.ac.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42225.203.197.150.195.1113980805.squirrel@mail.amrita.ac.in> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 576 Lines: 14 On Wed, Apr 20, 2005 at 12:36:45PM +0530, Harish K Harshan wrote: > CPU 0 : Machine Check Exception : 0000000000000004 > Bank 0 : a200000084010400 > Kernel panic : CPU context corrupt > In interrupt handler - not syncing CPU got messed up... could be a bad CPU/cache/chipset or simply it's over heating or has a bad powersupply. - 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/