public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernd Pfrommer <berndp-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: ACPI source release updated (20021002)
Date: Thu, 03 Oct 2002 15:46:15 -0400	[thread overview]
Message-ID: <3D9C9E87.8020807@optonline.net> (raw)
In-Reply-To: EDC461A30AC4D511ADE10002A5072CAD0236DEFF@orsmsx119.jf.intel.com

Replaced DSDT, but alas, this still did not fix the problem (I had tried 
that with an earlier version of ACPI, and it didn't help there either).
Some more questions:
    - it seems that there are a lot of these link devices, not just 
LNUS, no? Or do you think LNUS is the only one causing trouble? Maybe I 
can somehow get rid of it then?
    - is there a way to disable the link devices altogether by modifying 
the DSDT?
    - any suggestions as to why pci=noacpi does not fix the problem?
    - any other things I could try?

Thanks,
Bernd

Grover, Andrew wrote:

>>ACPI: PCI Interrupt Link [LNUS] enabled at IRQ 0
>>pci_link-0480 [04] acpi_pci_link_get_irq : Link disabled
>> pci_irq-0258 [03] acpi_pci_irq_lookup   : Invalid IRQ link 
>>routing entry
>> pci_irq-0296 [03] acpi_pci_irq_derive   : Unable to derive IRQ for 
>>device 00:0f
>>.2
>>
>
>            Name(PICA, Package(0xc) {
>                Package(0x4) {
>                    0x000fffff,
>                    0x0,
>                    LNUS,
>                    0x0,
>                },
>--------------------------------------------------
>
>    Device(LNUS) {
>	...
>        Method(_STA) {
>            If(GETI(PIUS)) {
>                Return(0xb)
>            }
>            Else {
>                Return(0x9)
>            }
>--------------------------------------------------
>    Method(GETI, 1) {
>        If(And(Arg0, 0xf, )) {
>            Return(Zero)
>        }
>        Else {
>            Return(\MLIB.CNV2(And(Arg0, 0xf, )))
>        }
>
>This BIOS appears to be unusual, in that it uses a link device (LNUS), even
>in IOAPIC mode. Unfortunately, this causes a bug in GETI to show the link
>device as disabled.
>
>If you are familiar with the whole DSDT-loading process, you might try that,
>and modify GETI by swapping what is in the two parts of the If/Else.
>
>Regards -- Andy
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Acpi-devel mailing list
>Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>https://lists.sourceforge.net/lists/listinfo/acpi-devel
>




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-10-03 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 18:31 ACPI source release updated (20021002) Grover, Andrew
2002-10-03 19:46 ` Bernd Pfrommer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-03 20:29 Grover, Andrew
2002-10-03 21:59 ` Bernd Pfrommer
2002-10-02 21:01 Grover, Andrew
2002-10-03 12:52 ` Bernd Pfrommer

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=3D9C9E87.8020807@optonline.net \
    --to=berndp-p32f3xycuykqczcgjluoxw@public.gmane.org \
    --cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
    --cc=andrew.grover-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