Date: Fri, 12 Oct 2018 10:01:33 -0500 From: Eric van Gyzen <eric@vangyzen.net> To: freebsd-current <freebsd-current@freebsd.org>, Stephen Hurd <shurd@llnw.com>, Sean Bruno <sbruno@FreeBSD.org> Subject: iflib_timer hits hung label; never recovers Message-ID: <ad857347-4f23-d2e1-eec3-474f4dbb5821@vangyzen.net>
next in thread | raw e-mail | index | archive | help
My firewall is running head at r338402 (30 Aug). It has three I211 NICs (PCI dev 0x1539). About 24 hours ago, it said: Oct 11 22:29:03 asbestos kernel: igb1: TX(1) desc avail = 42, pidx = 524 Oct 11 22:29:03 asbestos kernel: Link state changed to down Oct 11 22:29:03 asbestos kernel: core: link state changed to DOWN It keeps saying this periodically: Oct 12 09:46:05 asbestos kernel: igb1: TX(1) desc avail = 1024, pidx = 0 $ dmesg | uniq -c 2455 igb1: TX(1) desc avail = 1024, pidx = 0 I can panic the box and get a vmcore, but what other information should I get before then? I tried to attach kgdb to the running kernel, but it failed. :( I grabbed sysctl dev.igb.1 and dropped it here: http://vangyzen.net/FreeBSD/igb.hang/ I haven't tried manually recovering with ifconfig because I want to diagnose why the driver couldn't do it automatically. I imagine it's hard to test this code path. :) Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ad857347-4f23-d2e1-eec3-474f4dbb5821>