Please note that I am not subscribed to linux-usb-devel, and CC me on any replies.
At the moment, the 2.6.x USB core is /very/ noisy, giving KERN_WARNING
level messages for all failed usbfs bulk transactions (in addition to
returning the error), and for all usb transfer timeouts (in addition to
returning the error).
This results in two messages to syslog (and often the console) for all
bulk transfer timeouts, which seems rather excessive for information
which /may/ be useful when attempting to debug things, but which the
calling program has every chance to deal with itself.
It also gives KERN_INFO level messages for all connections and
disconnections, and while this may have more value then the debugging
messages above, it can still get somewhat extensive for cases of heavy
hot-plugging.
In both cases the messages are unconditional. Would it be reasonable
for these messages to be controlled by some of the various debugging
settings?
Thanks.
--
1024D/E65A7801 Zephaniah E. Hull <[EMAIL PROTECTED]>
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
Mike Sphar (Scary Devil Monastery):
>I am hired because I know what I am doing, not because I will do
>whatever I am told is a good idea. This might cost me bonuses, raises,
>promotions, and may even label me as "undesirable" by places I don't
>want to work at anyway, but I don't care. I will not compromise my own
>principles and judgement without putting up a fight. Of course, I
>won't always win, and I will sometimes be forced to do things I don't
>agree with, but if I am my objections will be known, and if I am shown
>to be right and problems later develop, I will shout "I told you so!"
>repeatedly, laugh hysterically, and do a small dance or jig as
>appropriate to my heritage.
signature.asc
Description: Digital signature
