Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Aug 2018 09:02:33 +0000
From:      bugzilla-noreply@freebsd.org
To:        amd64@FreeBSD.org
Subject:   [Bug 130483] [mxge] MSI must be disabled when Myricom 10Gbps Card is used on Dell PowerEdge T300 Server
Message-ID:  <bug-130483-17361-ZRYpYxYMza@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-130483-17361@https.bugs.freebsd.org/bugzilla/>
References:  <bug-130483-17361@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D130483

John Baldwin <jhb@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhb@FreeBSD.org

--- Comment #4 from John Baldwin <jhb@FreeBSD.org> ---
For posterity in case we have to revisit this in the future.  I ended up
resolving this PR in r189404.  I've included some boot -v output from the
affected machine below along with some additional notes:

MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec00000
ioapic0: Changing APIC ID to 4
ioapic0: Routing external 8259A's -> intpin 0
MADT: Found IO APIC ID 5, Interrupt 256 at 0xfec10000
ioapic1: Changing APIC ID to 5
ioapic1: WARNING: intbase 256 !=3D expected base 24
MADT: Found IO APIC ID 6, Interrupt 64 at 0xfec10000
ioapic2: Changing APIC ID to 6
ioapic2: WARNING: intbase 64 !=3D expected base 280
lapic: Routing NMI -> LINT1
lapic: LINT1 trigger: edge
lapic: LINT1 polarity: high
MADT: Interrupt override: source 0, irq 2
ioapic0: Routing IRQ 0 -> intpin 2
MADT: Interrupt override: source 9, irq 9
ioapic0: intpin 9 trigger: level
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 0-23 on motherboard
ioapic2 <Version 2.0> irqs 64-87 on motherboard

Here the error was that ioapic1 and ioapic2 were actually the same I/O APIC
(note the same memory mapped base address), but ioapic1 used a IRQ base of =
256
which caused IRQ values for MSI to get reserved by the nexus resulting in t=
he
panic.  Here is the MADT table from this machine:

/*
  APIC: Length=3D138, Revision=3D1, Checksum=3D201,
        OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1,
        Creator ID=3DDELL, Creator Revision=3D0x1
        Local APIC ADDR=3D0xfee00000
        Flags=3D{PC-AT}

        Type=3DLocal APIC
        ACPI CPU=3D1
        Flags=3D{ENABLED}
        APIC ID=3D0

        Type=3DLocal APIC
        ACPI CPU=3D2
        Flags=3D{ENABLED}
        APIC ID=3D1

        Type=3DLocal APIC
        ACPI CPU=3D3
        Flags=3D{ENABLED}
        APIC ID=3D2

        Type=3DLocal APIC
        ACPI CPU=3D4
        Flags=3D{ENABLED}
        APIC ID=3D3

        Type=3DLocal NMI
        ACPI CPU=3DALL
        LINT Pin=3D1
        Flags=3D{Polarity=3Dactive-hi, Trigger=3Dedge}

        Type=3DINT Override
        BUS=3D0
        IRQ=3D0
        INTR=3D2
        Flags=3D{Polarity=3Dconforming, Trigger=3Dconforming}

        Type=3DINT Override
        BUS=3D0
        IRQ=3D9
        INTR=3D9
        Flags=3D{Polarity=3Dactive-hi, Trigger=3Dlevel}

        Type=3DIO APIC
        APIC ID=3D4
        INT BASE=3D0
        ADDR=3D0x00000000fec00000

        Type=3DIO APIC
        APIC ID=3D5
        INT BASE=3D256
        ADDR=3D0x00000000fec10000

        Type=3DIO APIC
        APIC ID=3D6
        INT BASE=3D64
        ADDR=3D0x00000000fec10000
 */

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-130483-17361-ZRYpYxYMza>