Re: dmesg verbosity [was Re: AGP bogosities]

[David Lang]

On Tue, 15 Mar 2005, Benjamin Herrenschmidt wrote:

> > We already have the 'quiet' option, but even so, I think the kernel is *way*
> > too verbose.  Someone needs to make a personal crusade out of removing
> > unneeded and unjustified printks from the kernel before it really gets better
> > though...
>
> Oh well, I admit going backward here with my new radeonfb which will be
> very verbose in a first release, but that will be necessary to track
> down all the various issues with monitor detection, BIOSes telling crap
> about connectors etc...

This isn't the problem, the fact that if I have all the encryption modes 
turned on I get several hundred lines of output telling me that it tested 
the encryption and got the result it expected is.

you are turning up the verbosity becouse it's needed, if you don't turn it 
down in a few releases (assuming you fix the problems by then ;-) then you 
would become part of the problem.

back in the 1.3/2.0 days when I started useing linux I was a PC repair 
technition and when working on the windows PC's I would use a linux boot 
disk to identify the hardware that was in the machine based on the dmesg 
output (and the ports things were on) so that I could configure the 
windows drivers. So it's not that I can't understand the value of the 
dmesg output, it's that there is now so much additional data that it's no 
longer reasonable to see what's going on.

when the boot dmesg output overflows the 500 line buffer of a VGA console 
so that you can not scroll back and see the messages by the time the 
system starts things have gotten too verbose.

David Lang

--
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
 -- C.A.R. Hoare
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/