From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Randy.Dunlap" Subject: Re: Pointer to info on decoding oops messages Date: Wed, 26 Nov 2003 07:17:09 -0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20031126071709.2a0b43c8.rddunlap@osdl.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from fw.osdl.org ([65.172.181.6]:38604 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S264239AbTKZPXX (ORCPT ); Wed, 26 Nov 2003 10:23:23 -0500 To: Ian Kent In-Reply-To: List-Id: linux-fsdevel.vger.kernel.org On Wed, 26 Nov 2003 21:41:18 +0800 (WST) Ian Kent wrote: | | The subject says it all. | | Any suggestions please. Unless the instruction pointer register is scrogged, you get some registers, some stack data, the code bytes at the next instruction pointer, and some backtrace symbols. These are mostly self-explanatory. However, I'm guessing that you want help with the _cause_ of an oops, not just with decoding the oops messages. Anyway, here's where I pointed out some basic info recently: http://marc.theaimsgroup.com/?l=linux-kernel&m=106433590230743&w=2 and http://marc.theaimsgroup.com/?l=linux-kernel&m=106434159306658&w=2 -- ~Randy MOTD: Always include version info.