Bug 210417 - Reproducible igb related panic 11.0-ALPHA4
Summary: Reproducible igb related panic 11.0-ALPHA4
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.2-STABLE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-net mailing list
URL:
Keywords: IntelNetworking
Depends on:
Blocks:
 
Reported: 2016-06-20 22:03 UTC by rpp
Modified: 2019-01-17 18:47 UTC (History)
7 users (show)

See Also:


Attachments
crashino core.txt.1 (239.65 KB, text/plain)
2016-06-20 22:03 UTC, rpp
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rpp 2016-06-20 22:03:37 UTC
Created attachment 171625 [details]
crashino core.txt.1

Kernel panics within a few seconds with heavy network load. Using "iperf -c another_host" is sufficient to induce the problem. Setting hw.igb.enable_msix=0 in loader.conf "solves" the problem. The problem occurs on at least 2 similar machines with same motherboards. Hradware is Asus P9D C224 with integrated <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k.
crashino core.txt.1 attached.

--Richard
Comment 1 Allan Jude freebsd_committer 2016-06-20 23:59:30 UTC
pciconf dump from user:

igb0@pci0:1:0:0:	class=0x020000 card=0x85571043 chip=0x15338086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'I210 Gigabit Network Connection'
    class      = network
    subclass   = ethernet
igb1@pci0:2:0:0:	class=0x020000 card=0x85571043 chip=0x15338086 rev=0x03 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'I210 Gigabit Network Connection'
    class      = network
    subclass   = ethernet
Comment 2 Arcadiy Ivanov 2016-06-21 11:19:28 UTC
Bug 200420 might be related without the crash in the 10.x branch. Same adapters (I210), motherboard Supermicro X11SBA-F.
Comment 3 Kevin Bowling freebsd_committer 2017-01-10 11:29:14 UTC
Can you retry with 12-CURRENT?
Comment 4 rpp 2017-06-15 03:12:36 UTC
(In reply to Kevin Bowling from comment #3)
Sorry for delay, never saw this comment. I've just re-tested the same hardware using Current at r308389 with no change to results/symptoms. I'll retry with something more recent.
Comment 5 rpp 2017-06-15 06:33:31 UTC
(In reply to rpp from comment #4)
Tested with today's head at r319962, and can't reproduce problem, so appears its fixed. Can this be MFC'd to 11?  If not, any idea where/what the change would be so we can create a local patch?
Comment 6 Stephen Hurd freebsd_committer 2019-01-17 18:47:35 UTC
Changing Version to 11.2-STABLE assuming it's still an issue there.