Date: Fri, 30 Mar 2018 17:09:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 227116] CURRENT doesn't boot with integer divide fault in uma_startup_count Message-ID: <bug-227116-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227116 Bug ID: 227116 Summary: CURRENT doesn't boot with integer divide fault in uma_startup_count Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: daniel@octaforge.org CC: jeff@FreeBSD.org Created attachment 191980 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D191980&action= =3Dedit backtrace Hello, trying to boot a recent 12-CURRENT snapshot memstick image results in kernel panic. The system is actually HardenedBSD, but the affected code suggests i= t's not relevant to HBSD-related changes. Attached are pictures with a backtrac= e; sadly I can't save a dump because it's an installer image. The pictured snapshot is from March 21, I tried a recent one from today as well. This is on 2x Xeon E5-2683v3, so it's a NUMA configuration. The kernel in question has NUMA off and is effectively equivalent to GENERIC mins old Fre= eBSD compat and plus hardening. I can possibly try later on a vanilla FreeBSD -CURRENT snapshot and see if I can reproduce it there as well. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227116-8>