Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 03 Sep 2004 09:34:23 -0700
From:      Nate Lawson <nate@root.org>
To:        Markus Brueffer <markus@brueffer.de>
Cc:        current@freebsd.org
Subject:   Re: Interrupt storm on uhciX with acpi_pci_link.c 1.24.2.3
Message-ID:  <41389D0F.9030204@root.org>
In-Reply-To: <200409030255.00577.markus@brueffer.de>
References:  <413768A9.4020904@root.org> <200409030255.00577.markus@brueffer.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Markus Brueffer wrote:
> Hi Nate,
> 
> On Thursday 02 September 2004 20:38, Nate Lawson wrote:
> 
>>Your ASL is at fault here.  It defines a mixed set of APIC and PCI link
>>irq devices.  (See the _PRT for PCI0, the APIC object).  The MPtable is
>>correct.  Here is the part that is wrong:
>>
>>             Name (APIC, Package (0x18)
>>             {
>>             ...
>>                 Package (0x04)
>>                  {
>>                      0x0004FFFF,
>>                      0x03,
>>                      \_SB.LNKC,
>>                      0x00
>>                  },
>>
>>This one should be:
>>
>>		Package (0x04)
>>		{
>>		    0x0004FFFF,
>>		    0x03,
>>		    0x00,
>>		    0x12,
>>		}
>>
>>It should be possible to add this to /boot/loader.conf:
>>
>>hw.acpi.pci.link.0.4.3.irq="18"
> 
> As you already expected, this doesn't work.

I'll send you a patch that may fix this.

>>But since 18 won't be in your list of valid irqs, your best bet is to
>>patch your ASL as above and recompile with iasl. 
> 
> 
> Patching the ASL did the trick. Thank you very much!

Thanks to jhb@ for also helping with this.

> While compiling tha ASL I got the following warning:
> 
> markus-cuv4x-d.asl.patched   316:     Method (\_WAK, 1, NotSerialized)
> Warning  2026 -                                   ^ Reserved method must 
> return a value (_WAK)
> 
> Maybe this information is of some use for you.

Nope, the warning is harmless.  If you want to feel better, you can put
a Return (Package { 0, 0 }) in there (see the acpi debugging handbook
page for exact syntax).

>>Perhaps a BIOS upgrade will have this fixed?
> 
> I already have the latest BIOS installed and I doubt that there will be a new 
> one in the future (the current one is from mid 2002) :(

Ok.

-Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41389D0F.9030204>