Mitsuru IWASAKI writes:
> > > > If still NG, please try the attached patch against SupermicroP3TDE6.asl.
> > > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it
> > > > # if failed.
> > >
> > > Maybe 0x2 is correct.
> >
> > I tried 2, and it seems to work correctly now.
> >
> > Thanks!
>
> Congratulations!
>
> # Now we can start discussing ACPI PCI vs. legacy PCI :)
> DSDT in ACPI BIOS on Supermicro P3TDE6 has obviously wrong _BBN value,
Actually, I'd like to hijack this thread for just a second.
I have a buggy supermicro board too:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000
cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000
io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000
io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000
Pentium Pro MTRR support enabled
ACPI-0623: *** Warning: Type override - [DEB_] had invalid type (Integer) for
Scope operator, changed to (Scope)
<... 11 similar lines deleted>
ACPI-0623: *** Warning: Type override - [CMOS] had invalid type (Integer) for
Scope operator, changed to (Scope)
It also misses the peer bus.
Non ACPI:
pcib1: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard IOAPIC #1 intpin 8
-> irq 11
pci1: <PCI bus> on pcib1
pci1: <unknown card> (vendor=0x14c1, dev=0x8043) at 1.0 irq 11
ACPI:
pcib1: <ACPI Host-PCI bridge> on acpi0
acpi0: couldn't attach pci busdevice_probe_and_attach: pcib1 attach returned 6
What's nearly as bad, each time I get an interrupt on the on-board
fxp, my (serial) console is spammed like this:
Doing initial network setup: hostname domain.
ACPI-1047: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[20],
disabling event
ACPI-1047: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[21],
disabling event
<...> up to
ACPI-1047: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[3f],
disabling event
At which point it cycles back to GPE[20]. If missing the peer bus
didn't make it useless, this console spammage certainly does.
What can I do?
Thanks,
Drew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
