Date: Mon, 20 Jun 2016 18:21:30 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Reproducible igb related panic 11.0-ALPHA4 Message-ID: <8a9bdc85-a0bd-162e-bc4a-d0b742d1b8a9@freebsd.org> In-Reply-To: <20160620221833.GA69507@jodi.ci.com.au> References: <20160620045430.GA47444@jodi.ci.com.au> <20160620221833.GA69507@jodi.ci.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-06-20 18:18, Richard Perini wrote: > On Mon, Jun 20, 2016 at 02:54:30PM +1000, Richard Perini wrote: >> >> Reproducible igb related panic 11.0-ALPHA4 >> >> OS: FreeBSD 11.0-ALPHA4 #6 r302022 >> Hardware: Asus P9D C224 >> (integrated <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k) >> >> >> Hi, >> >> 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. Below is the >> first few pages of crashinfo, + dmesg. The problem occurs on 2 instances >> of similar hardware (with same motherboards). > > Submitted as PR 210417 > > --R > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > I was not able to reproduce this on my hardware. Can you use 'pciconf -lv' to find your card and get more specifics on which model of igb(4) it is? I am guessing by the C224 chipset, that it is haswell-ish -- Allan Jude
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8a9bdc85-a0bd-162e-bc4a-d0b742d1b8a9>