Date: Sat, 31 Mar 2018 19:45:49 +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-5ho6wNESm6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227116-8@https.bugs.freebsd.org/bugzilla/> References: <bug-227116-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227116 --- Comment #21 from Daniel Kolesa <daniel@octaforge.org> --- Created attachment 192015 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192015&action=edit different panic after patch I rebuilt the kernel once again with my patch this time (the updated condition, see comment above). It didn't panic there, but it did panic in another place. Backtrace attached. Here's relevant kgdb listing: 0xffffffff80e3f015 is in keg_ctor (/usr/src/sys/vm/uma_core.c:1294). 1289 shsize = 0; 1290 else 1291 shsize = sizeof(struct uma_slab); 1292 1293 keg->uk_ipers = (slabsize - shsize) / rsize; 1294 KASSERT(keg->uk_ipers > 0 && keg->uk_ipers <= SLAB_SETSIZE, 1295 ("%s: keg->uk_ipers %u", __func__, keg->uk_ipers)); 1296 1297 memused = keg->uk_ipers * rsize + shsize; 1298 wastedspace = slabsize - memused; Looks like the assertion is failing this time. -- 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-5ho6wNESm6>