Bug 184311 - [bge] [panic] kernel panic with bge(4) on SunFire X2100
Summary: [bge] [panic] kernel panic with bge(4) on SunFire X2100
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.2-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2013-11-26 16:10 UTC by Benjamin Stier
Modified: 2022-10-17 12:19 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Stier 2013-11-26 16:10:00 UTC
I'm tried updating a SunFire X2100 from 9.1-RELEASE to 9.2-RELEASE-p1 on a SunFire X2100. The machine was running without problems on 9.1-RELEASE.
After updating, the system won't boot and panics with the following message:

--- SNIP ---
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x004101> mem 0xfdaf0000-0xfdafffff irq 19 at device 0.0 on pci4
bge0: CHIP ID 0x00004101; ASIC REV 0x04; CHIP REV 0x41; PCI-E
miibus1: <MII bus> on bge0
brgphy0: <BCM5750 1000BASE-T media interface> PHY 1 on miibus1
brgphy0:  no media present
ifmedia_set: no match for 0x0/0xfffffff
panic: ifmedia_set
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff80834966 at kdb_backtrace+0x66
#1 0xffffffff807fcb5e at panic+0x1ce
#2 0xffffffff808be5a3 at ifmedia_set+0x53
#3 0xffffffff8051e58d at brgphy_attach+0x18d
#4 0xffffffff8082d70c at device_attach+0xcc
#5 0xffffffff8082ec8a at bus_generic_attach+0x1a
#6 0xffffffff80525b88 at miibus_attach+0xe8
#7 0xffffffff8082d70c at device_attach+0xcc
#8 0xffffffff8082ec8a at bus_generic_attach+0x1a
#9 0xffffffff8052625f at mii_attach+0x52f
#10 0xffffffff803e03f1 at bge_attach+0x3cf1
#11 0xffffffff8082d70c at device_attach+0xcc
#12 0xffffffff8082ec8a at bus_generic_attach+0x1a
#13 0xffffffff803320a4 at acpi_pci_attach+0x164
#14 0xffffffff8082d70c at device_attach+0xcc
#15 0xffffffff8082ec8a at bus_generic_attach+0x1a
#16 0xffffffff80333eda at acpi_pcib_attach+0x19a
#17 0xffffffff803350db at acpi_pcib_pci_attach+0x9b
--- SNIP ---

I can provide further information if needed.

Fix: 

Disabling "hw.bge.allow_asf" on the loader prompt makes the machine boot. However it was working fine without this setting before, so this is not a real fix.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-11-26 21:21:23 UTC
Responsible Changed
From-To: freebsd-amd64->freebsd-net

Over to maintainer(s).
Comment 2 Hiren Panchasara freebsd_committer freebsd_triage 2014-05-19 21:08:14 UTC
I just hit this on FreeBSD10.

vgapci0: <VGA-compatible display> mem
0xc9000000-0xc9ffffff,0xd0000000-0xd7ffffff irq 16 at device 5.0 on
pci1
vgapci0: Boot video device
pcib2: <ACPI PCI-PCI bridge> at device 12.0 on pci0
pci2: <ACPI PCI bus> on pcib2
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
0x004101> mem
0xca000000-0xca00ffff irq 16 at device 0.0 on pci2
bge0: CHIP ID 0x00004101; ASIC REV 0x04; CHIP REV 0x41; PCI-E
miibus0: <MII bus> on bge0
brgphy0: <BCM5750 1000BASE-T media interface> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 00:17:08:92:b6:e9
pcib3: <ACPI PCI-PCI bridge> at device 13.0 on pci0
pci3: <ACPI PCI bus> on pcib3
bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.
0x004101> mem
0xca100000-0xca10ffff irq 19 at device 0.0 on pci3
bge1: CHIP ID 0x00004101; ASIC REV 0x04; CHIP REV 0x41; PCI-E
miibus1: <MII bus> on bge1
brgphy1: <BCM5750 1000BASE-T media interface> PHY 1 on miibus1
brgphy1:  no media present
ifmedia_set: no match for 0x0/0xfffffff
panic: ifmedia_set
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xffffffff81a3f1b0
kdb_backtrace() at kdb_backtrace+0x39/frame 0xffffffff81a3f260
vpanic() at vpanic+0x126/frame 0xffffffff81a3f2a0
panic() at panic+0x43/frame 0xffffffff81a3f300
ifmedia_set() at ifmedia_set+0x5a/frame 0xffffffff81a3f310
brgphy_attach() at brgphy_attach+0x3a4/frame 0xffffffff81a3f350
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3f3b0
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3f3d0
miibus_attach() at miibus_attach+0xbd/frame 0xffffffff81a3f410
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3f470
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3f490
mii_attach() at mii_attach+0x435/frame 0xffffffff81a3f520
bge_attach() at bge_attach+0x4151/frame 0xffffffff81a3f600
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3f660
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3f680
acpi_pci_attach() at acpi_pci_attach+0x15f/frame 0xffffffff81a3f6d0
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3f730
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3f750
acpi_pcib_attach() at acpi_pcib_attach+0x23d/frame 0xffffffff81a3f7a0
acpi_pcib_pci_attach() at acpi_pcib_pci_attach+0x9f/frame
0xffffffff81a3f7e0
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3f840
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3f860
acpi_pci_attach() at acpi_pci_attach+0x15f/frame 0xffffffff81a3f8b0
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3f910
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3f930
acpi_pcib_attach() at acpi_pcib_attach+0x23d/frame 0xffffffff81a3f980
acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0x2a9/frame
0xffffffff81a3f9d0
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3fa30
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3fa50
acpi_attach() at acpi_attach+0xdd4/frame 0xffffffff81a3fb10
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3fb70
bus_generic_attach() at bus_generic_attach+0x4a/frame
0xffffffff81a3fb90
nexus_acpi_attach() at nexus_acpi_attach+0x76/frame 0xffffffff81a3fbc0
device_attach() at device_attach+0x3a2/frame 0xffffffff81a3fc20
bus_generic_new_pass() at bus_generic_new_pass+0x116/frame
0xffffffff81a3fc50
bus_set_pass() at bus_set_pass+0x8f/frame 0xffffffff81a3fc80
configure() at configure+0xa/frame 0xffffffff81a3fc90
mi_startup() at mi_startup+0x118/frame 0xffffffff81a3fcb0
btext() at btext+0x2c
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
Comment 3 Stephen Hurd freebsd_committer freebsd_triage 2014-06-16 22:53:28 UTC
Part of the problem may be that the device is being detected incorrectly.  I'm pretty sure the 5750 was never sold to customers, and it was a PCI device, not PCI-E.

Possibly this is a actually 5751?  Could one of you post the pciconf information?
Comment 4 Miroslav Lachman 2014-06-16 23:43:07 UTC
Are you talking about SunFire X2100 or SunFire X2100 M2?

Because "X2100" (withou M2) has only one bge NIC identified as BCM5721 and one nVidia CK804 NIC.

"X2100 M2" has two bge BCM5714 and two nfe NVIDIA nForce MCP55 Networking Adapter 


X2100 M2  - FreeBSD 8.4-RELEASE-p9 i386 GENERIC

from /var/run/dmesg.boot

bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x009003> mem 0xfdff0000-0xfdffffff,0xfdfe0000-0xfdfeffff irq 17 at device 4.0 on pci6
bge0: CHIP ID 0x00009003; ASIC REV 0x09; CHIP REV 0x90; PCI-X 133 MHz
miibus2: <MII bus> on bge0
brgphy0: <BCM5714 10/100/1000baseTX PHY> PHY 1 on miibus2
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 00:1b:24:xx:xx:xx
bge0: [ITHREAD]
bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x009003> mem 0xfdfc0000-0xfdfcffff,0xfdfb0000-0xfdfbffff irq 18 at device 4.1 on pci6
bge1: CHIP ID 0x00009003; ASIC REV 0x09; CHIP REV 0x90; PCI-X 133 MHz
miibus3: <MII bus> on bge1
brgphy1: <BCM5714 10/100/1000baseTX PHY> PHY 1 on miibus3
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge1: Ethernet address: 00:1b:24:xx:xx:xx
bge1: [ITHREAD]


pciconf

bge0@pci0:6:4:0:        class=0x020000 card=0x534c108e chip=0x167814e4 rev=0xa3 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'BCM5715C 10/100/100 PCIe Ethernet Controller'
    class      = network
    subclass   = ethernet
bge1@pci0:6:4:1:        class=0x020000 card=0x534c108e chip=0x167814e4 rev=0xa3 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'BCM5715C 10/100/100 PCIe Ethernet Controller'
    class      = network
    subclass   = ethernet

Note that pciconf says BCM5715C while dmesg shows BCM5714



X2100 M2 - FreeBSD 9.2-RELEASE-p5 amd64 GENERIC

bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x009003> mem 0xfdff0000-0xfdffffff,0xfdfe0000-0xfdfeffff irq 17 at device 4.0 on pci6
bge0: CHIP ID 0x00009003; ASIC REV 0x09; CHIP REV 0x90; PCI-X 133 MHz
miibus2: <MII bus> on bge0
brgphy0: <BCM5714 1000BASE-T media interface> PHY 1 on miibus2
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 00:1e:68:xx:xx:xx
bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x009003> mem 0xfdfc0000-0xfdfcffff,0xfdfb0000-0xfdfbffff irq 18 at device 4.1 on pci6
bge1: CHIP ID 0x00009003; ASIC REV 0x09; CHIP REV 0x90; PCI-X 133 MHz
miibus3: <MII bus> on bge1
brgphy1: <BCM5714 1000BASE-T media interface> PHY 1 on miibus3
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge1: Ethernet address: 00:1e:68:xx:xx:xx


pciconf

bge0@pci0:6:4:0:        class=0x020000 card=0x534c108e chip=0x167814e4 rev=0xa3 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme BCM5715 Gigabit Ethernet'
    class      = network
    subclass   = ethernet
bge1@pci0:6:4:1:        class=0x020000 card=0x534c108e chip=0x167814e4 rev=0xa3 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'NetXtreme BCM5715 Gigabit Ethernet'
    class      = network
    subclass   = ethernet


I am running "X2100 M2" without any problems on FreeBSD 8.4 and 9.2
Comment 5 Stephen Hurd freebsd_committer freebsd_triage 2014-06-17 00:07:32 UTC
Both of the log bits in the reports contained the lines:

bge0: CHIP ID 0x00004101; ASIC REV 0x04; CHIP REV 0x41; PCI-E
miibus1: <MII bus> on bge0
brgphy0: <BCM5750 1000BASE-T media interface> PHY 1 on miibus1

Which is troubling since there shouldn't be any 5750s out there, and there absolutely aren't any on PCI-E busses.

> Note that pciconf says BCM5715C while dmesg shows BCM5714

It also says 10/100/100 (missing zero there!).  There shouldn't be any differences between the 5715 and 5714 as far as a driver behaviour goes, so this is likely a cosmetic issue.
Comment 6 John Baldwin freebsd_committer freebsd_triage 2014-06-23 15:21:03 UTC
Can you capture a verbose dmesg (boot -v) with the ASF tunable set (so that it works) and in the stock setup (where it breaks)?
Comment 7 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:49:29 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 8 Mark Johnston freebsd_committer freebsd_triage 2019-05-20 17:07:20 UTC
Is this still an issue for anyone, especially on a supported release?  John's request was never answered.
Comment 9 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:19:15 UTC
Keyword: 

    crash

– in lieu of summary line prefix: 

    [panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>