cc'ing Kay, hi. On 06/14/2010 11:52 PM, Tejun Heo wrote: > Hello, > > On 06/14/2010 11:41 PM, Greg KH wrote: >> So if there's a routing problem, it turns into a polled interrupt? Do >> we really want that? > > Oh yeah, I really want that for libata. Routing is only part of the > problem and flaky IRQ is something we have to learn to cope with. > >> I wonder how long people will run without realizing that there are >> problems with their system if their devices still work. > > I think things would be better this way. If the drives (both cd and > hard) / input devices are not accessible, most people would simply > give up rather than reporting, and many cases are transient problems > which happen only once in the blue moon. > > It would be great if some kind of automatic reporting can be used > (similar to kerneloops?). Hmm... maybe make the warnings scarier? Hmm... maybe what we can do is generating an uevent when an IRQ is confirmed to be bad and then let udev notify the user. That way we'll probably have better chance of getting bug reports and users have whiny but working system. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
