DragonFly BSD
DragonFly kernel List (threaded) for 2011-04
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: ACPI problems

From: Sepherosa Ziehau <sepherosa@xxxxxxxxx>
Date: Thu, 14 Apr 2011 08:36:20 +0800

On Thu, Apr 14, 2011 at 1:14 AM, ejc <eric.j.christeson@gmail.com> wrote:
> I've been tracking HEAD for a while now and it broke this morning. It
> boots fine with ACPI disabled.
> Here's what I see as relevant from the boot log:
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> acpi_config_intr: Skip SCI config
> vgapci0: <VGA-compatible display> port 0xefa8-0xefaf mem
> 0xfeb80000-0xfebfffff,0xe8000000-0xefffffff irq 11 at device 2.0 on
> pci0
> agp0: <Intel 82865G (865G GMCH) SVGA controller> on vgapci0
> agp0: detected 8060k stolen memory
> agp0: aperture size is 128M
> drm0: <Intel i865G GMCH> on vgapci0
> vgapci0: child drm0 requested pci_enable_busmaster
> info: [drm] AGP at 0xe8000000 128MB
> info: [drm] Initialized i915 1.6.0 20080730
> pcib1: <ACPI PCI-PCI bridge> at device 30.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> em0: <Intel(R) PRO/1000 Network Connection 82540EM 6.9.6> port
> 0xdf40-0xdf7f mem 0xfeae0000-0xfeafffff irq 9 at device 12.0 on pci1
> em0: Unable to allocate bus resource: interrupt
> em0: Allocation of PCI resources failed
> device_probe_and_attach: em0 attach returned 6
> isab0: <PCI-ISA bridge> at device 31.0 on pci0
> isa0: <ISA bus> on isab0
> atapci0: <Intel ICH5 UDMA100 controller> port
> 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 mem
> 0xfeb7fc00-0xfeb7ffff irq 9 at device 31.1 on pci0
> ata0: <ATA channel 0> on atapci0
> ata1: <ATA channel 1> on atapci0
> acd0: DMA limited to UDMA33, controller found non-ATA66 cable
> disk scheduler: set policy of acd0 to noop
> acd0: DVDR <ATAPI DVD A DH20A4H/QP53> at ata1-master UDMA33
> atapci1: <Intel ICH5 SATA150 controller> port
> 0xfea0-0xfeaf,0xfe30-0xfe33,0xfe20-0xfe27,0xfe10-0xfe13,0xfe00-0xfe07
> irq 9 at device 31.2 on pci0
> atapci1: unable to map interrupt
> device_probe_and_attach: atapci1 attach returned 6
> ichsmb0: <Intel 82801EB (ICH5) SMBus controller> port 0xefe0-0xefff
> irq 5 at device 31.3 on pci0
> smbus0: <System Management Bus> on ichsmb0
> Note the 'Skip SCI config' message and the fact that the 2 devices
> trying to use irq 9 can't use it.
> It appears related to commit 3a32a4c6817bea6229e54f81d2e9be3fa8b059d3.
> That contains the 'Skip SCI config' line.  From what I can tell, irq 9
> doesn't get configured because
> it's the SCI interrupt, but this stuff is voodoo magick to me :-)
> Normally I'd just change BIOS settings so these devices would use a
> different irq, but this BIOS doesn't
> have those knobs.
> Let me know if I can provide more information.  A verbose boot doesn't

Temporary solution is to set:

I have made some changes in my local git tree, which will try
detecting SCI interrupt mode.  I will commit it tomorrow.

Best Regards,

Tomorrow Will Never Die

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]