> That's weird. Another EH is scheduled after one completes but EH > doesn't kick in. Hmmm... can't see how that can happen. How easily > can you reproduce the problem? > > Thanks. Hi Tejun, I hope you are well :-) I have been trying to determine if the problem is that it is failing to schedule the EH, or whether it is correctly scheduling it but for some reason it is getting blocked or lost. Unfortunately it has so far been quite difficult to reproduce when specifically attempting to. In normal use cases I reproduced it twice by unplugging a drive from a RAID array with redundancy intact. This was out of around a dozen cycles of waiting until redundancy was restored while the unit was under load, popping the disk, reinserting, and triggering a RAID rebuild. I have only twice managed to trigger a lockup deliberately. In both cases the tracing showed a scheduled EH which was subsequently not enacted. How long could it take for the EH to be enacted? In the lockups that I have reproduced it did not seem to have recovered minutes later, but perhaps if I had waited longer...? I have noticed that error recovery sometimes backs off for 8s and even 33s, but it always warns when that sort of delay is coming up. I shall continue to try to track down why the scheduled EH does not happen. Kind Regards, Bruce. Latest News at: http://www.indigovision.com/index.php/en/news.html -- 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
