DragonFly users List (threaded) for 2005-02
Re: xl device doesn't work with ACPI enabled under -current and -stable
On Thu, Feb 03, 2005 at 09:50:25AM -0500, Rongsheng Fang wrote:
> >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?
Hmm, I have no idea other than backing out the commit. However, I have
a desktop PC in my office which has the exact same NIC but it doesn't have
the problem you described. I need to guess what's happening on your
computer. Can you send me the following things?
- output of `acpidump -t -d' as rfang.asl by running
# acpidump -t -d > rfang.asl
- verbose /var/run/dmesg.boot from unpatched kernel with both acpi enabled
and disabled (drop in the boot loader prompt and type `boot -v')