[Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Jan 10 22:49:40 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234042
--- Comment #9 from Mike Andrews <mandrews at bit0.com> ---
All of my systems are dual-stack v4/v6, and the panics happen after a few days
of uptime. Not boot-time. If it was boot-time I wouldn't have finished
upgrading the whole rack. :)
There shouldn't be any churn in the ARP and ND tables -- it's a server rack and
most addresses are statically assigned, and nothing's coming or going. The
expire times are at defaults. So the only churn should be re-populating right
after a normal expire. Traffic does get kinda heavy at times though (lots of
HTTPS, lots of NFSv3) though we had a lightly loaded system get it yesterday.
All the NICs are em(4) -- we have a few systems with igb but none of those have
had the panic yet. No idea if that's relevant or just luck.
I put 12.0-p2 on everything overnight last night and one system has paniced
since then, so it's not anything that was fixed in that patch. The panics did
not happen on 11.x or 10.x -- this is all new with 12.0.
I do now have vmcore images now for many of these, including the 12.0-p2 one
from two hours ago. (Initially I didn't have dumps working on geli+gmirrored
swap. I do now.)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list