Messages in this thread | | | Date | Fri, 13 Feb 2009 10:58:40 +0100 | From | Nico Schottelius <> | Subject | [RFC] Make printk() output better readable |
| |
Hey devs,
When reading current dmesg, I notice that some messages have the structure
Introduction: <location>: <text>
Example:
[ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009ec00 (usable) [...]
I also see
<location>: <text>
Example:
[ 0.000000] ACPI: RSDP 000F73A0, 0024 (r2 LENOVO) [ 0.000000] ACPI: XSDT 7C97BD45, 009C (r1 LENOVO TP-6D 1050 LTP 0) [...]
Then, most of the stuff is simply
<text>
[ 0.000000] DMI present. [ 0.000000] last_pfn = 0x7ca00 max_arch_pfn = 0x100000000 [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
The first two blocks are somehow readable, the <text> only is a bit painful to read. I personally would prefer to have at least <location> (which may also be driver, hardware location, etc) before each line, if it's not of type 1 (introduction + indent).
I think currently it is totally inconsistent, as seen, one of the worst cases with TCP, here:
[ 0.355604] NET: Registered protocol family 2 [ 0.402669] IP route cache hash table entries: 65536 (order: 7, 524288 bytes) [ 0.403216] TCP established hash table entries: 262144 (order: 10, 4194304 bytes) [ 0.404925] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [ 0.405538] TCP: Hash tables configured (established 262144 bind 65536) [ 0.405642] TCP reno registered
What do you think about it?
Sincerly,
Nico
-- Think about Free and Open Source Software (FOSS). http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C [unhandled content-type:application/pgp-signature] | |