http://bugzilla.kernel.org/show_bug.cgi?id=14583 Robert Hancock <hancockrwd@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hancockrwd@xxxxxxxxx --- Comment #25 from Robert Hancock <hancockrwd@xxxxxxxxx> 2009-12-09 02:40:49 --- It looks like most of these bug reports indicate BMDMA status 0x04 or 0x64 when the timeout occurs, indicating that the controller should be asserting an interrupt and the BMDMA transfer is not or is no longer active. But the device registers indicate DRQ is asserted, indicating the device wants to transfer more data. It looks like this is why libata reports an HSM violation. The amount of data drained indicates that no data was actually transferred (I notice there's a bug that causes the amount of data reported as drained to be half the actual amount, I'll submit a patch for that). I don't see a reason for the device to generate an interrupt at this point. Thus I tend to suspect that the cause is a bug in the device. As far as why an interrupt is shown as generated but doesn't actually get received, I'm not sure. Maybe the controller doesn't propagate the interrupt if the state machine doesn't say it should be getting one? DRQ + interrupt asserted certainly doesn't seem like a combination that should happen. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
