[lkml]   [2005]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: dmesg verbosity [was Re: AGP bogosities]

    On Mon, 14 Mar 2005, Jesse Barnes 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...

    The thing is, this comes up every once in a while (pretty often,
    actually), but the bulk of those messages _do_ end up being useful. For
    certain classes of bugs, I almost invariably ask for the bootup messages:
    the PCI interrupt routing printou stuff is absolutely invaluable.

    In fact, even the ones that have no "information" end up often being a big
    clue about where the hang happened.

    So yes, when things work (and hey, that's happily 99.9% of the time) they
    are almost all worthless. But just _one_ case where they help is a big
    deal. So don't say "most people don't care", because that is a totally
    irrelevant argument. It's not "most people" who matter. It's not even
    kernel developers who matter - they can know how to enable the stuff if
    they ever see a problem. The _only_ people who matter are the very
    occasional regular users that see problems.

    And those occasional people are often not going to eb very good at
    reporting bugs. If they don't see anything happening, they'll just give up
    rather than bother to report it. So I do think we want the fairly verbose
    thing enabled by default. You can then hide it with the graphical bootup
    for "most people".

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2009-11-18 23:46    [W:0.023 / U:11.956 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site