On Wed, 29 Aug 2012, Gary E. Miller wrote: > Yo Alan! > > On Wed, 29 Aug 2012 10:07:41 -0400 (EDT) > Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > > > OK, fair enough, but does it need to keep flooding my logs? Can > > > we rate limit that a bit? > > > > Easy enough to do; simply disable CONFIG_USB_DEBUG. > > Uh, not easy. This is a production machine. Acceptable downtime is > very small. There should be a way to turn it off at runtime. No, there shouldn't. It's a debugging feature; while debugging we want to see all occurrences of these messages. Production machines should not run debugging kernels. > > > I really doubt it is a hardware error since this appeared after the > > > last kernel update. > > > > If you think it's caused by a problem in the kernel then you can try > > using git bisect to track it down. > > Sadly the problem went away after a reboot. I suspect an initialization > issue, but doing a git bisect of an intermittent problem on a production > machine is not gonna happen. Especially if the problem doesn't reappear. One-time issues are very hard to fix. > Sadly this machine is the only one with the rare hardware that the > driver did not get exactly right. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
