public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: Norbert Preining <preining-DX+603jRYB8@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
Date: Tue, 24 Aug 2004 09:23:48 -0400	[thread overview]
Message-ID: <412B4164.8090601@optonline.net> (raw)
In-Reply-To: <20040824123913.GD25947-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>

Norbert Preining wrote:
> On Die, 24 Aug 2004, Nathan Bryant wrote:
> 
>>For your b44 IRQ problem, try one of the workarounds in the message I'm 
>>forwarding you. For more details, check the mailing list archives for 
>>the thread of the forwarded message
> 
> 
> Thanks a lot, will do it immediately.
> 
> One more question: Which workaround do you think is the `right' one in
> the sense that it is not only a local workaround, but a real fix?
> Accoriding to your comment it looks like 2. is the one.

Both should work just fine for your machine, but I'm not sure that 
either one is fully general. We have other initialization-order problems 
that can't be solved just by changing everything to late_initcall, and 
although it's perfectly fine in all the KNOWN cases to ignore the BIOS' 
possible-IRQ list, for the specific case where the BIOS has already set 
up a different IRQ, there may be some case where the BIOS knows better 
than we do. It just doesn't seem 100% ACPI-compliant to ignore the list, 
even though some BIOSes clearly get the list wrong.

All that being said, if all we do is remove the line that checks the 
possible-IRQ list, that still doesn't solve the case where we have 
deliberately rebalanced IRQ's due to the "acpi IRQ rebalance" kernel 
parameter; we would need to fix the initialization order, to get that 
right... so in that sense, the late_initcall is slightly more correct, 
because it's more in the direction we want to ultimately go in, even 
though it doesn't give us enough fine-grained control over 
initialization order.

Are you running APIC or PIC mode on your machine? If PIC, it would be 
nice if you could try the late_initcall workaround, so that we can 
confirm that it fixes the problem for you.

Nathan


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285

       reply	other threads:[~2004-08-24 13:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <412B2E16.1040904@optonline.net>
     [not found] ` <20040824123913.GD25947@gamma.logic.tuwien.ac.at>
     [not found]   ` <20040824123913.GD25947-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
2004-08-24 13:23     ` Nathan Bryant [this message]
     [not found] ` <20040824142219.GA13607@gamma.logic.tuwien.ac.at>
     [not found]   ` <20040824142219.GA13607-DqSSrKF0TaySnEC3TeqHn5dqbFPxfnh/@public.gmane.org>
2004-08-24 14:32     ` [PATCH][RFC] fix ACPI IRQ routing after S3 suspend Nathan Bryant
     [not found]       ` <412B516B.8030704-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-25 11:19         ` Norbert Preining
2004-08-20 19:00 Pallipadi, Venkatesh
2004-08-20 19:42 ` [ACPI] " Nathan Bryant
     [not found]   ` <41265443.9050800-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-20 20:01     ` Stefan Dösinger
     [not found]       ` <200408202201.54083.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-20 20:42         ` Nathan Bryant
     [not found]           ` <4126621B.3090701-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-20 20:43             ` Nathan Bryant
2004-08-20 20:17     ` Stefan Dösinger
  -- strict thread matches above, loose matches on Subject: below --
2004-08-04  2:36 Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F037BB9C6-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-04  2:55   ` Len Brown
2004-08-04  1:42 Nathan Bryant
     [not found] ` <41103F22.4090303-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-04  2:59   ` Len Brown
2004-08-04 15:57     ` Nathan Bryant
2004-08-19 20:24 ` [ACPI] " Stefan Dösinger
     [not found]   ` <200408192224.08271.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-19 20:54     ` Nathan Bryant

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=412B4164.8090601@optonline.net \
    --to=nbryant-p32f3xycuykqczcgjluoxw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=preining-DX+603jRYB8@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