se7520af2 intel motherboard acpi problem
John Baldwin
jhb at freebsd.org
Mon Apr 10 18:05:34 UTC 2006
On Friday 07 April 2006 13:10, Nate Lawson wrote:
> John Baldwin wrote:
> > On Friday 07 April 2006 05:02, Anton Menshutin wrote:
> >> On Thu, 6 Apr 2006, John Baldwin wrote:
> >>
> >>> Can you give more detail about how the pci-e busses do not work?
> >>>
> >> In dmesg output you can see kernel says nothing about areca raid
> >> controller, which is on pci-e bus. And
> >> pcib5: <ACPI PCI-PCI bridge> at device 0.0 on pci6
> >> pcib5: secondary bus 8
> >> pcib5: subordinate bus 8
> >> pcib5: I/O decode 0xf000-0xfff
> >> pcib5: memory decode 0xfe900000-0xfe9fffff
> >> pcib5: prefetched decode 0xfbc00000-0xfbffffff
> >> device_attach: pcib5 attach returned 6
> >> what i think means there is a problem during init of pci-e bus.
> >
> > Ah, ok. It would be most helpful if you could add a bunch of printf's
> > to the attach routine in sys/dev/acpica/acpi_pcib_pci.c to see where
> > the error comes from.
> >
> > Oh, I think I've seen this before. This is due to incompetent BIOS
> > writers. Edit sys/dev/acpica/acpi_pcib.c and in the acpi_pcib_attach()
> > function comment out the acpi_DeviceIsPresent() check. The BIOS is
> > claiming that the specific PCI bus doesn't exist.
>
> If that is the case, we should change acpi_pcib to have a separate check
> for just the "functional" bit or whatever the AML does report. I
> thought we did that before, but it's been a year or so.
I think it is indistinguishable from other cases like the PCI bus in
the docking station on my (older) Dell laptop.
--
John Baldwin <jhb at FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
More information about the freebsd-acpi
mailing list