Date: Mon, 28 Aug 2006 13:49:08 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: freebsd-arch@FreeBSD.org Subject: msgbuf default size... Message-ID: <20060828204908.GI37035@funkthat.com>
next in thread | raw e-mail | index | archive | help
Well, today w/ PCIe around the corner (or in some cases already here),
and some relatively complex PCI debug output, normal dmesg when booted
-v is now well over the default of 32k meaning that basic info such as
memory size and processor type are no longer stored in
/var/run/dmesg.boot if booted -v... Already amd64 has acknoledged the
issue and defaults to 64k...
I believe we should make the default 64k, and let other platforms,
like arm, use DEFAULTS to change it to smaller values if necessary...
Anyone have any objections to this?
On my recent box I built (AMD X2 3800+ w/ Gigabyte mobo), the
/var/run/dmesg.boot starts w/:
pci_link19: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 5 7 9 10 11 14 15
w/ a larger msgbuf size I end up w/:
-bash-2.05b$ wc -c dmesg.boot
46362 dmesg.boot
-bash-2.05b$ head -n 3 dmesg.boot
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
-bash-2.05b$ grep -n '^pci_link19: Links after initial validation' dmesg.boot
381:pci_link19: Links after initial validation:
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060828204908.GI37035>