From owner-freebsd-current Tue Feb 18 14: 1:25 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D84D237B401; Tue, 18 Feb 2003 14:01:23 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id E167843FA3; Tue, 18 Feb 2003 14:01:22 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0311.cvx40-bradley.dialup.earthlink.net ([216.244.43.56] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18lFnf-0000SP-00; Tue, 18 Feb 2003 14:01:16 -0800 Message-ID: <3E52ACD7.BDC8716@mindspring.com> Date: Tue, 18 Feb 2003 13:59:51 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Darryl Okahata Cc: Tom Rhodes , current@FreeBSD.ORG Subject: Re: ACPI thermal panics ThinkPad 600X References: <200302181705.JAA19695@mina.soco.agilent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a443c22be298a5df6569e1c6f918225611350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Darryl Okahata wrote: > Tom Rhodes wrote: > > > ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it > > does not crash anything I just leave it be waiting for the day > > when the ACPI hackers have time to fix it :) > > It may not necessarily be a FreeBSD problem (or, not only). While > there may be issues with FreeBSD's ACPI, there are definitely issues > with the A31 BIOS: > > http://sourceforge.net/mailarchive/message.php?msg_id=3597168 A more useful reference, I think, is: http://sourceforge.net/mailarchive/message.php?msg_id=3597172 If you add similar code to FreeBSD to detect and patch the BIOS table, this fixes the problem in FreeBSD, as well (though adding the code is somewhat tricky: YMMV, knowledge of both FreeBSD and Linux required; sorry, I do not have a patch against -current). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message