On Thu, Aug 9, 2018 at 5:10 AM, Stanislaw Gruszka <[email protected]> wrote: > I'm reluctant to replace _warn by _dbg messages as if somethings > will go wrong we will not notice that. We can use printk_ratelimited() > variant instead to do not spam log in speed that it will hung > the machine. But the correct fix should be in USB host drivers, > which seems to be not in perfect shape on those embedded platforms.
Agreed about the "correct" fix likely being on the USB side, but at least using printk_ratelimited() will avoid the log spamming, and avoid locking the machine, as you said. Will someone else take that approach and come up with a patch, or is this something I should try to take on myself? I could certainly test such a patch, if desired. Meanwhile, I'll look into reporting the USB bug, if it hasn't already been.
