From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265353AbTLHJ2p (ORCPT ); Mon, 8 Dec 2003 04:28:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265354AbTLHJ2p (ORCPT ); Mon, 8 Dec 2003 04:28:45 -0500 Received: from adsl-216-102-91-59.dsl.snfc21.pacbell.net ([216.102.91.59]:34189 "EHLO nasledov.com") by vger.kernel.org with ESMTP id S265353AbTLHJ2o (ORCPT ); Mon, 8 Dec 2003 04:28:44 -0500 Date: Mon, 8 Dec 2003 01:30:45 -0800 To: linux-kernel@vger.kernel.org Subject: Re: 2.6.0-test11 Oops Message-ID: <20031208093045.GA32664@nasledov.com> References: <20031208032127.GA14638@nasledov.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031208032127.GA14638@nasledov.com> User-Agent: Mutt/1.5.4i From: Misha Nasledov Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I forgot to mention that this oops happened during bootup; I had just revived my dead laptop and rebooted from 2.4 to 2.6. On Sun, Dec 07, 2003 at 07:21:28PM -0800, Misha Nasledov wrote: > I just encountered an Oops on my IBM ThinkPad T21 with 2.6.0-test11. I > suspect that it has something to do with my battery being so low that it would > not even give a reading. I had to copy down the oops and by the time I > rebooted the machine, it had charged enough and booted successfuly. Here is > the text of the oops: -- Misha Nasledov misha@nasledov.com