Издание монографии в короткие сроки

2020-02-14 Thread Среда


___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

Bug ID: 244118
   Summary: 13-CURRENT Kernel post r357547 hang during boot on
PowerMac G5Q
   Product: Base System
   Version: CURRENT
  Hardware: powerpc
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: o...@farscape.co.uk

As posted to the mailing list recently, Kernels post r357547 hang during boot
on my PowerMac G5 Quad, at:

mountroot waiting for /dev/ada0s3

(This is with SMP disabled)

I have tried revisions:

357547 - Works

357550 - hangs on boot
357556 - hangs on boot
357566 - hangs on boot
357875 - hangs on boot

I think the issue may be with commit 357548 as it changes something in:
head/sys/powerpc/aim/slb.c

Although what its changing may be beyond me!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||maintainer-feedback?(rlibby
   ||@freebsd.org)
   Keywords||needs-qa, regression
 CC||rli...@freebsd.org
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244123] libfetch: memory leak when processing multiple HTTP location response headers

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244123

Bug ID: 244123
   Summary: libfetch: memory leak when processing multiple HTTP
location response headers
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: chwoi...@yahoo.com

Created attachment 211646
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211646&action=edit
patch to libfetch

fetchMakeURL() or fetchParseURL() are used to create a new url struct when
processing a location header.  In the event that the HTTP response contains
multiple location headers, the previously allocated url is freed using free()
instead of fetchFreeURL().  This currently prevents the struct's "doc" member
from being freed.

Please find attached a patch to use fetchFreeURL().

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244123] libfetch: memory leak when processing multiple HTTP location response headers

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244123

Hans Christian Woithe  changed:

   What|Removed |Added

 Attachment #211647|text/x-python   |text/plain
  mime type||

--- Comment #1 from Hans Christian Woithe  ---
Created attachment 211647
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211647&action=edit
Simple Python server useful for testing

Please find attached a simple Python server useful for testing the scenario
described in the bug report.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #1 from Ryan Libby  ---
Hmm, r357548 shouldn't have had an effect by itself, but it could be
fallout from related r357549.  Could you try setting this from the boot
loader or in /boot/loader.conf?

vm.debug.uma_multipage_slabs="0"

If that works then we can try to find which zone causes trouble.  Would
you be able to try out a patch that would print debugging info?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244127] man-page for ul(1) cross-references colcrt(1) & nroff(1) which don't exist

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244127

Bug ID: 244127
   Summary: man-page for ul(1) cross-references colcrt(1) &
nroff(1) which don't exist
   Product: Documentation
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: Manual Pages
  Assignee: b...@freebsd.org
  Reporter: free...@tim.thechases.com
CC: d...@freebsd.org

Reading the man-page for ul(1) noticed reference to colcrt and went to learn
more but found it didn't exist. Noticed that there was no man-page for nroff
either when I checked.

$ man ul | grep -B1 colcrt
SEE ALSO
 colcrt(1), man(1), nroff(1)
$ man colcrt nroff
No manual entry for colcrt
No manual entry for nroff

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #2 from Francis Little  ---
(In reply to Ryan Libby from comment #1)

Hi,

Yep, that works, so r357550 now boots successfully with:

vm.debug.uma_multipage_slabs="0"

I'm happy to test a patch and update to a more recent rev also.

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #3 from Ryan Libby  ---
Created attachment 211651
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211651&action=edit
Print zone layouts

Okay, could you try out this patch?  It won't fix anything, it will
hopefully just tell us what difference r357549 makes.  So, first could
you try it with vm.debug.uma_multipage_slabs="0", and then grep for
"keg.*layout" in /var/log/messages and attach that somewhere, and then
again with vm.debug.uma_multipage_slabs="1"?  There should be a number
of zones which end up with different layouts between the two and likely
one of those is causing the issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

Ryan Libby  changed:

   What|Removed |Added

 Attachment #211651|0   |1
is obsolete||

--- Comment #4 from Ryan Libby  ---
Created attachment 211652
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211652&action=edit
Print zone layouts

Sorry, update to patch, I realized I left off a newline.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244123] libfetch: memory leak when processing multiple HTTP location response headers

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244123

--- Comment #2 from Conrad Meyer  ---
Your fix looks correct to me.

Technically this is a non-compliant server, right?  IIRC, modern HTTP does not
allow duplicate instances of headers.  So it would also be valid for libfetch
to just reject the connection when encountering the second Location.  No?

This case is only encountered when one HTTP response contains two location
headers and not by, e.g., 302 / Location: foo => 302 / Location: bar => ...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #5 from Ryan Libby  ---
(In reply to Francis Little from comment #0)
> As posted to the mailing list recently [...]

I wasn't able to locate this thread, so if there's more information
there then could you please either repost it here or direct me to the
thread?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

Mark Millard  changed:

   What|Removed |Added

 CC||marklmi26-f...@yahoo.com

--- Comment #6 from Mark Millard  ---
(In reply to Ryan Libby from comment #5)

I tink he means:

https://lists.freebsd.org/pipermail/freebsd-ppc/2020-February/011444.html
https://lists.freebsd.org/pipermail/freebsd-ppc/2020-February/011504.html

but I doubt they add anything. (The one between them is from me
and does not have information useful to you.)


Going in another direction . . .

vm.debug.uma_multipage_slabs="1" leaves his G5 unable to
boot (waiting for mountroot). So how is he to follow the
directions for testing that case?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #7 from Francis Little  ---
(In reply to Ryan Libby from comment #3)

Hi, as Mark just mentioned, I can only get the logfile with:

vm.debug.uma_multipage_slabs="0"

With it set as:

vm.debug.uma_multipage_slabs="1"

The Machine doesn't get far enough to write the log out!

Regards

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #8 from Mark Millard  ---
(In reply to Francis Little from comment #7)

If you have an appropriate swap/paging partition you might
be able to have /boot/loader.conf contain an assignment
of the general form:

dumpdev="/dev/"

(substituting as necessary). Then you might be able
to cause a kernel dump from ddb (say). (Of cource,
this might run back into the same or other problems.)

If it worked, rebooting with vm.debug.uma_multipage_slabs="0"
should pick up that dump if you have room in /var/crash.
The dump might contain the tail of the sequence of lines
that would have gone into the log file. There might be a
way to extract those lines.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 244123] libfetch: memory leak when processing multiple HTTP location response headers

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244123

--- Comment #3 from Hans Christian Woithe  ---
Duplicate headers can be allowed in certain situations.  I tend to agree that
the location header probably doesn't qualify.

https://tools.ietf.org/html/rfc7230#section-3.2.2

A generic fix would involve a larger change on how headers are processed.  Such
a change should detect all duplicate headers that aren't allowed and return an
appropriate error to the user.  That could eliminate the need for the code
under scrutiny.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #9 from Mark Millard  ---
(In reply to Mark Millard from comment #8)

I got to thinking about my history investigating
and I think this is too early for the device to
be available for dump to use.

Also the hangup likely prevents getting to ddb.

So I set up -r357550's artifact materials on a
SSD and got into ddb somewhat before the lockup.

One part of acttrace looked potentially interesting
(typed from a picture and avoiding typing everything
for now):

Tracing command cam pid 7 tid 100034 td  . . . (CPU3)
intr_event_handle
powerpc_dispatch_intr
openpic_dispatch
powerpc_interrupt
kernel EXI trap by __mtx_unlock_flags
__mtx_unlock_flags
xpt_copy_path
xpt_async
cam_periph_error
probe_done
xpt_done_process
xpt_done_td
fork_exit
fork_trampoline
-0x04

I've still got the picture to extract other details from
if required.

For thread 100034, "show locks" reported one:
(I split the line below)

exclusive sleep mutex CAM device lock (CAM device lock)
r = 0 (. . .) locked @ /usr/src/sys/cam/cam_xpt.c:5490

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #10 from Mark Millard  ---
I tried non-debug kernel builds (that involve
some of my own PowerMac patches):

Head -r357548 did not have the problem.
Head -r357549 did have the problem.

So: Confirming Ryan's expectation.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #11 from Ryan Libby  ---
Yeah... I guess that's not going to work easily.  (I guess I'm just used
to debugging on my VM and captuing the console.)

Actually, I _may_ be able to debug this with just information from a
system with vm.debug.uma_multipage_slabs="0", and without the above
patch and log, but with the output of

sysctl vm.uma

Otherwise, I can try to reproduce this on a VM, but I am out of town
right now so I probably won't have time to try setting that up until
next weekend.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #12 from Mark Millard  ---
(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.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #13 from Mark Millard  ---
(In reply to Mark Millard from comment #12)

Found one that I missed earlier:

keg Mountpoints layout: format 0 (ipers 1 * rsize 2944) / slabsize 0x1000 = 71%
eff
vs. ipers 4 slabsize 0x3000

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #14 from Ryan Libby  ---
Created attachment 211661
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211661&action=edit
slb_zone_init: unconditional UMA_ZONE_CONTIG

(In reply to Mark Millard from comment #12)

Thanks!

This one looks especially interesting:

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

Based on that, could either of you try out this patch?

I have not compile tested it, so I apologize in advance if it is broken.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #15 from Mark Millard  ---
(In reply to Ryan Libby from comment #14)

It boots. I'll see about getting a diff
of the keg lines. It might catch things
I missed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #16 from Mark Millard  ---
(In reply to Mark Millard from comment #15)

The diff:

# more /mnt/root/keg_lines_diff.txt 
--- /root/keg_lines_0.txt   2020-02-15 06:06:11.31823 +
+++ /root/keg_lines_1.txt   2020-02-15 06:06:55.069131000 +
@@ -1,3 +1,5 @@
 keg UMA Kegs layout: format 0 (ipers 7 * rsize 512) / slabsize 0x1000 = 87%
eff
+keg UMA Kegs layout: format 0 (ipers 15 * rsize 512) / slabsize 0x2000 = 93%
eff
 keg UMA Zones layout: format 0 (ipers 2 * rsize 1792) / slabsize 0x1000 = 87%
eff
+keg UMA Zones layout: format 0 (ipers 9 * rsize 1792) / slabsize 0x4000 = 98%
eff
 keg UMA Slabs 0 layout: format 0 (ipers 50 * rsize 80) / slabsize 0x1000 = 97%
eff
@@ -26,2 +28,4 @@
 keg VMSPACE layout: format 0 (ipers 2 * rsize 1400) / slabsize 0x1000 = 68%
eff
+keg VMSPACE layout: format 0 (ipers 5 * rsize 1400) / slabsize 0x2000 = 85%
eff
+keg VMSPACE layout: format 0 (ipers 8 * rsize 1400) / slabsize 0x3000 = 91%
eff
 keg UPVO entry layout: format 0 (ipers 42 * rsize 96) / slabsize 0x1000 = 98%
eff
@@ -53,2 +57,3 @@
 keg filedesc0 layout: format 0 (ipers 3 * rsize 1104) / slabsize 0x1000 = 80%
eff
+keg filedesc0 layout: format 0 (ipers 7 * rsize 1104) / slabsize 0x2000 = 94%
eff
 keg rangeset pctrie nodes layout: format 0 (ipers 28 * rsize 144) / slabsize
0x1000 = 98% eff
@@ -62,2 +67,5 @@
 keg THREAD layout: format 0 (ipers 2 * rsize 1376) / slabsize 0x1000 = 67% eff
+keg THREAD layout: format 0 (ipers 5 * rsize 1376) / slabsize 0x2000 = 83% eff
+keg THREAD layout: format 0 (ipers 8 * rsize 1376) / slabsize 0x3000 = 89% eff
+keg THREAD layout: format 0 (ipers 11 * rsize 1376) / slabsize 0x4000 = 92%
eff
 keg cpuset layout: format 0 (ipers 31 * rsize 128) / slabsize 0x1000 = 96% eff
@@ -92,2 +100,3 @@
 keg NCLNODE layout: format 0 (ipers 6 * rsize 592) / slabsize 0x1000 = 86% eff
+keg NCLNODE layout: format 0 (ipers 13 * rsize 592) / slabsize 0x2000 = 93%
eff
 keg DIRHASH layout: format 0 (ipers 3 * rsize 1024) / slabsize 0x1000 = 75%
eff
@@ -101,2 +110,3 @@
 keg Mountpoints layout: format 0 (ipers 1 * rsize 2944) / slabsize 0x1000 =
71% eff
+keg Mountpoints layout: format 0 (ipers 4 * rsize 2944) / slabsize 0x3000 =
95% eff
 keg ksiginfo layout: format 0 (ipers 36 * rsize 112) / slabsize 0x1000 = 98%
eff
@@ -105,2 +115,3 @@
 keg socket layout: format 0 (ipers 4 * rsize 904) / slabsize 0x1000 = 88% eff
+keg socket layout: format 0 (ipers 9 * rsize 904) / slabsize 0x2000 = 99% eff
 keg unpcb layout: format 0 (ipers 15 * rsize 256) / slabsize 0x1000 = 93% eff
@@ -123,4 +134,7 @@
 keg sctp_asoc layout: format 0 (ipers 1 * rsize 2288) / slabsize 0x1000 = 55%
eff
+keg sctp_asoc layout: format 0 (ipers 3 * rsize 2288) / slabsize 0x2000 = 83%
eff
+keg sctp_asoc layout: format 0 (ipers 5 * rsize 2288) / slabsize 0x3000 = 93%
eff
 keg sctp_laddr layout: format 0 (ipers 84 * rsize 48) / slabsize 0x1000 = 98%
eff
 keg sctp_raddr layout: format 0 (ipers 5 * rsize 736) / slabsize 0x1000 = 89%
eff
+keg sctp_raddr layout: format 0 (ipers 11 * rsize 736) / slabsize 0x2000 = 98%
eff
 keg sctp_chunk layout: format 0 (ipers 26 * rsize 152) / slabsize 0x1000 = 96%
eff
@@ -136,2 +150,3 @@
 keg swpctrie layout: format 0 (ipers 28 * rsize 144) / slabsize 0x1000 = 98%
eff
+keg swblk layout: format 0 (ipers 29 * rsize 136) / slabsize 0x1000 = 96% eff
 keg FFS inode layout: format 0 (ipers 25 * rsize 160) / slabsize 0x1000 = 97%
eff

So: swblk missing vs. existing is something I missed, along with originally
missing Mountpoints.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2020-02-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244118

--- Comment #17 from Mark Millard  ---
(In reply to Mark Millard from comment #16)

The diff also shows that I missed: filedesc0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"