Date: Thu, 10 Jan 2019 22:49:38 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0 Message-ID: <bug-234042-227-XlDBHr57I3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234042-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234042 --- Comment #9 from Mike Andrews <mandrews@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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234042-227-XlDBHr57I3>