[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Q35 FreeBSD install status
From: |
Bret Ketchum |
Subject: |
Re: [Qemu-devel] Q35 FreeBSD install status |
Date: |
Wed, 18 Sep 2013 12:35:27 +0000 |
For those following along. The mptable I presented was an old table,
updating to SeaBIOS 1.7.3 fixed that but still no interrupts. However, it
appears FreeBSD has trouble parsing the ACPI tables presented via
q35-acpi-dsdt.aml as it does not create the sysresource devices associated with
ACPI. A work around until I uncover the parsing issue it to revert to using the
mptable to wire PCI interrupts via 'debug.acpi.disabled=pci_link'. FreeBSD will
whine about failing to force attach of GSIs but thus far all seems to be well
with the world. I've yet to check but I suspect the parsing issue is also root
cause of uhci/ehci missing interrupts.
-----Original Message-----
From: Michael S. Tsirkin [mailto:address@hidden
Sent: Tuesday, September 17, 2013 11:44 AM
To: Bret Ketchum
Cc: Gerd Hoffmann; address@hidden
Subject: Re: [Qemu-devel] Q35 FreeBSD install status
Could be MPT is not parsed correctly?
I see that we put 0 in the ID in bios code.
Could you dump the MPT and send it on list?
On Tue, Sep 17, 2013 at 03:25:38PM +0000, Bret Ketchum wrote:
>
> The emulated e1000 uses legacy interrupts. I'm wondering if someone can
> help me understand the mptable (used by FreeBSD to route interrupts and
> defined in Intel's MP spec):
>
> Bus: Bus ID Type
> 0 PCI
> 1 ISA
>
> I/O APICs: APIC ID Version State Address
> 0 0x11 usable 0xfec00000
>
> I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID
> PIN#
> INT active-hi conforms 0 31:A 2 10
> INT active-hi conforms 0 3:A 2 11
>
>
> The interrupts associated with the PCI bus where e1000 hangs suggest
> there is an APIC with an ID of 2 but there is only one APIC (with an ID of
> 0).
>
> -----Original Message-----
> From: Gerd Hoffmann [mailto:address@hidden
> Sent: Monday, September 16, 2013 10:15 AM
> To: Bret Ketchum
> Cc: address@hidden; address@hidden
> Subject: Re: [Qemu-devel] Q35 FreeBSD install status
>
> On Mo, 2013-09-16 at 12:57 +0000, Bret Ketchum wrote:
> > Tried that - looks like FreeBSD expects to use MSI for AHCI devices
> > which does not appear to be supported in q35.
>
> It is supported and linux has no problems using ahci with msi.
>
> Given that e1000 seems to have interrupt problems too I wouldn't be surprised
> if both issues have the same root cause. Might be something in the seabios
> acpi tables. Or a bug in FreeBSD.
>
> cheers,
> Gerd
>
>
>
- Re: [Qemu-devel] Q35 FreeBSD install status, (continued)
- Re: [Qemu-devel] Q35 FreeBSD install status, Michael S. Tsirkin, 2013/09/10
- Re: [Qemu-devel] Q35 FreeBSD install status, Bret Ketchum, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Michael S. Tsirkin, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Bret Ketchum, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Bret Ketchum, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Gerd Hoffmann, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Bret Ketchum, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Gerd Hoffmann, 2013/09/16
- Re: [Qemu-devel] Q35 FreeBSD install status, Bret Ketchum, 2013/09/17
- Re: [Qemu-devel] Q35 FreeBSD install status, Michael S. Tsirkin, 2013/09/17
- Re: [Qemu-devel] Q35 FreeBSD install status,
Bret Ketchum <=