From: Shawn Starr <shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
To: ipw2100-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
George Socker
<george.socker-H+0wwilmMs3R7s880joybQ@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Ipw2100-devel] [ipw2200]Confirmation of power management problem
Date: Wed, 13 Oct 2004 13:08:46 -0400 [thread overview]
Message-ID: <200410131308.47014.shawn.starr@rogers.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3001AD09EA-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
yes, nolapic in 2.6.9-rc3-bk8 works. I will bump my kernel and apply this
patch unless its merged into -rc4? If not apply manually.
Len, great work on getting ibm-acpi into -mm. us ThinkPad users appreciate it!
This also solves the ipw2200 being stuck on during power off.
Shawn.
On October 13, 2004 12:48, Brown, Len wrote:
> Re: poweroff
>
> Until last week, Linux forced the LAPIC to
> be enabled on systems who's BIOS had it disabled.
> You can observe it is enabled or disabled by
> looking if "LOC" is non-zero on /proc/interrupts.
> (non-zero means you're getting local APIC timer interrupts)
>
> But this caused a number of machines to power-off
> incorrectly. The workaround was to boot with "nolapic".
> This is fixed in the latest 2.6.9 tree, and the patch is here:
> http://linux.bkbits.net:8080/linux-2.6/cset@41696f84CrEcJrCzRqhBpHrjqxy1
> 1w?nav=index.html|ChangeSet@-7d
> Now Linux believes what the BIOS says, and you can force
> the LAPIC to be enabled against the BIOS' wishes with "lapic"
> if you like.
>
> If your system still doesn't poweroff when using this patch,
> or if a manual "nolapic" is still necessary to poweroff
> your machine, please let me know cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>
> thanks,
> -Len
>
> ps. Re: ibm-acpi is in -mm
>
> Yes it is, but it isn't in Linus's tree yet.
> I'm expecting an updated version of this patch soon and
> we'll push it into 2.6.10 as EXPERIMENTAL, which it is.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> ipw2100-devel mailing list
> ipw2100-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/ipw2100-devel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next parent reply other threads:[~2004-10-13 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7DC2337C7631D4386A2DF6E8FB22B3001AD09EA@hdsmsx401.amr.corp.intel.com>
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3001AD09EA-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-10-13 17:08 ` Shawn Starr [this message]
2004-10-13 17:18 [Ipw2100-devel] [ipw2200]Confirmation of power management problem Brown, Len
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 23:32 Shawn Starr
[not found] ` <200410101932.12431.shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
2004-10-11 0:16 ` [Ipw2100-devel] " Alejandro Bonilla
[not found] ` <200410102023.50379.shawn.starr@rogers.com>
[not found] ` <2894.194.77.192.95.1097474839.squirrel@www.mocka.de>
[not found] ` <2894.194.77.192.95.1097474839.squirrel-Iw/ES6IqVGAuZeo0DBJMuQ@public.gmane.org>
2004-10-11 6:38 ` Shawn Starr
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=200410131308.47014.shawn.starr@rogers.com \
--to=shawn.starr-bjeeyj9ojedqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=george.socker-H+0wwilmMs3R7s880joybQ@public.gmane.org \
--cc=ipw2100-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/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