xl device doesn't work with ACPI enabled under -current and -stable

Matthew Dillon dillon at apollo.backplane.com
Thu Feb 3 10:54:27 PST 2005


:> ACPI code hasn't been touched since then, so I guess that the
:> following discussion also applies to you since you're using xl(4) driver:
:> 
:>   http://leaf.dragonflybsd.org/mailarchive/commits/2005-01/msg00325.html
:> 
:> 
:> Please try backing out the commits:
:> # cvsweb="http://www.dragonflybsd.org/cvsweb/src"
:> # fetch -q -o - \
:>         "$cvsweb/sys/bus/pci/pci_if.m.diff?r1=1.4&r2=1.5&f=u" \
:>         "$cvsweb/sys/bus/pci/pci_pcib.c.diff?r1=1.3&r2=1.4&f=u" > ~/pcib.diff
:> # patch -d /usr/src -R -p1 < ~/pcib.diff
:> 
:> and rebuild your kernel and see if it's fixed.
:
:Thanks for the fix. Yes, this fixed the problem. I noticed Eirik Nygaard
:reported the same problem on 1/22. Is there any plan to fix this in the
:-current tree? 
:
:
:Thanks, 
:
:Rongsheng

    Rongsheng, could you do a boot -v and post a copy of you dmesg for
    both the xl-working AND the xl-broken cases ?

    What stands out here is that the interrupt storm is occuring on irq 3.
    It kinda sounds like the XL device is being routed to irq 3 rather then
    to the IRQ it is supposed to be routed to.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>





More information about the Users mailing list