[Bug 244118] 13-CURRENT Kernel post r357547 hang during boot on PowerMac G5Q

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #12 from Mark Millard <marklmi26-fbsd at yahoo.com> ---
(In reply to Ryan Libby from comment #11)

I tried to use pictures to get your originally requested
informatino.

I only have pictures of the non-booting case so I only
show the booting case line in full, where the
non-booting case had some larger slabsize also listed.

UMA Kegs layout: format 0 (ipers 7 * rsize 512) / slabsize 0x1000 = 87% eff
vs. ipers 15 with slabsize 0x2000

UMA Zones layout: format 0 (ipers 2 * rsize 1792) / slabsize 0x1000 = 87% eff
vs. ipers 9 with slabsize 0x4000

keg VMSPACE layout: format 0 (ipers 2 * rsize 1400) / slabsize 0x1000 = 68% eff
vs. ipers 5 slabsize 0x2000
vs. ipers 8 slabsize 0x3000

keg SLB cache layout: format 0 (ipers 7 * rsize 520) / slabsize 0x1000 = 88%
eff
vs. ipers 15 slabsize 0x2000

keg THREAD layout: format 0 (ipers 2 * rsize 1376) / slabsize 0x1000 = 67% eff
vs. ipers 5 slabsize 0x2000
vs. ipers 8 slabsize 0x3000
vs. ipers 11 slabsize 0x4000

keg NCLNODE layout: format 0 (ipers 6 * rsize 592) / slabsize 0x1000 = 86% eff
vs. ipers 13 slabsize 0x2000

keg socket layout: format 0 (ipers 4 * rsize 904) / slabsize 0x1000 = 88% eff
vs. ipers 9 slabsize 0x2000

keg sctp_asoc layout: format 0 (ipers 1 * rsize 2288) / slabsize 0x1000 = 55%
eff
vs. ipers 3 slabsize 0x2000
vs. ipers 5 slabsize 0x3000

keg sctp_raddr layout: format 0 (ipers 5 * rsize 736) / slabsize 0x1000 = 89%
eff
vs. ipers 11 skabsize 0x2000


I will note that sometimes FFS inode, FFS1 dinode, and FFS2 dinode lines
were listed for the failing boots. In the booting case, those are the last
3 keg lines. slabsize 0x1000 always showed for any that displayed.

I got all but the final lines via booting and getting to
ddb> and then scrolling around, taking pictures.

Picture comparison means a higher probability that I missed some
example(s) that should be listed above.

-- 
You are receiving this mail because:
You are the assignee for the bug.