kern/121558: Supermicro X7SB4 Fatal trap 12 when ACPI disabled

[John Baldwin]

On Thursday 13 March 2008 11:20:02 am Leon Kos wrote:
> The following reply was made to PR kern/121558; it has been noted by GNATS.
> 
> From: Leon Kos <leon.kos at lecad.uni-lj.si>
> To: John Baldwin <jhb at freebsd.org>
> Cc: freebsd-acpi at freebsd.org, bug-followup at freebsd.org
> Subject: Re: kern/121558: Supermicro X7SB4 Fatal trap 12 when ACPI disabled
> Date: Thu, 13 Mar 2008 16:13:36 +0100 (CET)
> 
>  I've added
>  
>  hw.pci0.13.0.INTA.irq="16"
>  hw.pci0.15.0.INTA.irq="17"
>  hw.pci0.5.0.INTA.irq="19"
>  
>  and now it boots when ACPI disabled. I have also tried to move hints into 
>  /boot/loader.conf and this also works.
>  
>  Now I have
>  
>  hw.pci0.13.0.INTA.irq="40"
>  hw.pci0.15.0.INTA.irq="41"
>  hw.pci0.5.0.INTA.irq="43"
>  
>  in /boot/loader.conf and I see the following lines in dmesg log:
>  em3: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 
0x5000-0x501f mem 0xd8400000-0xd841ffff irq 40 at device 0.0 on pci13
>  em4: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 
0x6000-0x601f mem 0xd8500000-0xd851ffff irq 41 at device 0.0 on pci15
>  em2: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port 
0x4000-0x401f mem 0xd8320000-0xd833ffff,0xd8300000-0xd831ffff irq 43 at 
device 0.0 on pci5
>  
>  that I plan to stick with.

Odd, does that actually work?  It seemed that from your ACPI dmesg the first 
set of IRQs is correct.

>  I've replaced  src/sys/dev/usb/ehci_pci.c with revision 1.3 from trunk and 
>  now also reboot is handled well.
>  
>  Thank you for all support and now I suggest to close the ticket.
>  We'll see if BIOS will be upgraded by Supermicro. For now, above workaround 
>  is the only cure for this and similar boards.

Since the ehci(4) stuff is fixed you can just stick with ACPI now anyway and 
not worry about the hints.  Since Linux and Windows both use ACPI out of the 
box the non-ACPI case tends to not get tested anymore.  I've seen BIOSes that 
have a completely wrong MP Table in recent years (as if the MP Table was just 
copied over from the BIOS of some other motherboard and never updated).

-- 
John Baldwin