iflib_timer hits hung label; never recovers
Eric van Gyzen
eric at vangyzen.net
Fri Oct 12 15:01:37 UTC 2018
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
More information about the freebsd-current
mailing list