From: Jeff Garzik <jgarzik@pobox.com>
To: Richard A Nelson <kenpocowboy@bellsouth.net>
Cc: Patrick Mochel <mochel@osdl.org>, Rob Landley <rob@landley.net>,
Pavel Machek <pavel@suse.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Fix up power managment in 2.6
Date: Fri, 05 Sep 2003 17:45:36 -0400 [thread overview]
Message-ID: <3F590400.7050600@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0309051548400.18554@onpx40.onqynaqf.bet>
Richard A Nelson wrote:
> On Fri, 5 Sep 2003, Jeff Garzik wrote:
>
>
>>Note that a lot of ThinkPads out in the field need a BIOS update
>>before their ACPI is working. (I know this because IBM was quite
>>helpful and proactive in addressing their Linux-related ACPI BIOS
>>issues)
>
>
> And even that isn't always enough :(
>
> I have a TP30, 2366-51U with the latest BIOS:
> Version: 1IET67WW (2.06 )
> Release: 07/17/2003
> Processor Manufacturer: GenuineIntel
> Processor Version: Pentium(R) 4
> BIOS32 Service Directory present.
> Calling Interface Address: 0x000FD7E0
> ACPI 2.0 present.
> OEM ID: IBM
> RSD table at 0x0FF63195.
> PNP 1.0 present.
> Event Notification: Polling
> Event Notification Flag Address: 0x000004B4
> Real Mode Code Address: F000:9D36
> Real Mode Data Address: 0040:0000
> Protected Mode Code Address: 0x000F9D54
> Protected Mode Data Address: 0x00000400
> PCI Interrupt Routing 1.0 present.
> Table Size: 256 bytes
> Router ID: 00:1f.0
> Exclusive IRQs: None
> Compatible Router: 8086:122e
>
> Up through 2.05, ACPI crashed the kernel during boot(2.4 and 2.6) -
> I posted here about that... I'm going to try this weekend with
> the just flashed 2.06 - even though the changelog doesn't indicate
> anything changed wrt ACPI.
>
> The problem was, iirc, was scanning one of the tables - I can't find
> the message now :(
If you are up for a little debugging and comfortable with building your
own kernels, then please enable the relaxed-aml-checking and debug
options in the ACPI kernel config. Those, and dmidecode output, will
provide useful info to the ACPI folks.
Jeff
next prev parent reply other threads:[~2003-09-05 21:46 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 23:28 Fix up power managment in 2.6 Pavel Machek
2003-09-01 6:57 ` Russell King
2003-09-01 8:11 ` Pavel Machek
2003-09-01 8:26 ` Russell King
2003-09-01 9:33 ` Pavel Machek
2003-09-01 16:28 ` Linus Torvalds
2003-09-01 21:12 ` Pavel Machek
2003-09-01 21:52 ` Russell King
2003-09-01 22:19 ` Pavel Machek
2003-09-01 22:30 ` Russell King
2003-09-01 22:40 ` Pavel Machek
2003-09-01 22:48 ` Russell King
2003-09-02 17:17 ` Greg KH
2003-09-03 15:13 ` Pavel Machek
2003-09-02 10:21 ` Benjamin Herrenschmidt
2003-09-03 13:02 ` Alan Cox
2003-09-03 13:31 ` Benjamin Herrenschmidt
2003-09-03 17:08 ` Pavel Machek
2003-09-05 20:42 ` Pavel Machek
2003-09-01 22:55 ` Patrick Mochel
2003-09-01 23:38 ` Pavel Machek
2003-09-02 0:52 ` Patrick Mochel
2003-09-02 9:02 ` Pavel Machek
2003-09-02 9:47 ` Pavel Machek
2003-09-02 16:11 ` Patrick Mochel
2003-09-03 16:21 ` Pavel Machek
2003-09-03 23:17 ` Patrick Mochel
2003-09-03 17:49 ` Pavel Machek
2003-09-03 17:59 ` bill davidsen
2003-09-03 23:20 ` Patrick Mochel
2003-09-05 9:33 ` Pavel Machek
2003-09-03 20:03 ` Bill Davidsen
2003-09-03 22:14 ` Pavel Machek
2003-09-04 4:06 ` Bill Davidsen
2003-09-04 14:52 ` Patrick Mochel
2003-09-02 10:29 ` Jan Rychter
2003-09-05 5:58 ` Rob Landley
2003-09-05 10:26 ` Pavel Machek
2003-09-05 10:56 ` Michael Frank
2003-09-05 11:08 ` Pavel Machek
2003-09-05 11:51 ` Michael Frank
2003-09-05 12:01 ` Pavel Machek
2003-09-05 17:47 ` Patrick Mochel
2003-09-05 18:02 ` Jeff Garzik
2003-09-05 18:13 ` Patrick Mochel
2003-09-05 21:46 ` Jeff Garzik
2003-09-05 18:57 ` Rob Landley
2003-09-05 19:06 ` Pavel Machek
2003-09-05 20:09 ` Keyboard stuff (was Re: Fix up power managment in 2.6) Rob Landley
2003-09-05 20:31 ` Pavel Machek
2003-09-05 20:01 ` Fix up power managment in 2.6 Richard A Nelson
2003-09-05 21:45 ` Jeff Garzik [this message]
2003-09-05 18:49 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 20:13 Nicolas Mailhot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F590400.7050600@pobox.com \
--to=jgarzik@pobox.com \
--cc=kenpocowboy@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=pavel@suse.cz \
--cc=rob@landley.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox