From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759749AbXEWAU3 (ORCPT ); Tue, 22 May 2007 20:20:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S966035AbXEWAT5 (ORCPT ); Tue, 22 May 2007 20:19:57 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:43027 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965941AbXEWATy (ORCPT ); Tue, 22 May 2007 20:19:54 -0400 X-Sasl-enc: FUQCEU1XXSFau9gu4JmVeMBR0qNfv5L62Y8lPMb0saFG 1179879592 Date: Tue, 22 May 2007 21:19:43 -0300 From: Henrique de Moraes Holschuh To: Matt Mackall Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, akpm@linux-foundation.org Subject: Re: 2.6.21-mm2: ACPI exception on resume Message-ID: <20070523001943.GA3743@khazad-dum.debian.net> References: <20070519165738.GK11115@waste.org> <20070519204504.GA24704@khazad-dum.debian.net> <20070519223843.GN11115@waste.org> <20070520035259.GA13224@khazad-dum.debian.net> <20070521222339.GF11115@waste.org> <20070521230349.GA645@khazad-dum.debian.net> <20070522224515.GW11115@waste.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070522224515.GW11115@waste.org> X-GPG-Fingerprint: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04 3738 EE25 DE3F 1CDB 0FE3 User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 22 May 2007, Matt Mackall wrote: > On Mon, May 21, 2007 at 08:03:49PM -0300, Henrique de Moraes Holschuh wrote: > > On Mon, 21 May 2007, Matt Mackall wrote: > > > BIOS Information > > > Vendor: IBM > > > Version: 1RETDHWW (3.13 ) > > > Release Date: 10/29/2004 > > > > > > No sign of any EC version in the output. > > > > This is a buggy, ancient version of the BIOS, which probably means you have > > an old and slightly buggy EC firmware. I recommend you to upgrade to BIOS > > 3.21 and EC 3.04. See http://thinkwiki.org/wiki/BIOS_Upgrade for more > > details. > > Really, I'd much prefer my kernel not regress instead. Updating > firmware is just introducing more potential instability and ignoring > the problem. We can't very much know if the kernel is really buggy, then. I'd say we need a report from someone with another thinkpad that uses the 1R BIOS that has an up-to-date BIOS, to know for sure. Since that includes the T41 and T42, chances are others would have spoken up about it already if it affected the more recent versions of the 1R BIOS. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh