> > If you can bear with slower operation, keeping issuing sync repeatedly > > (ie. something like while true; do sync; sleep 1; done) and see how > > the behavior changes might shed some light on what's going on too. > > I wouldn't expect it to have any diagnostic value, really. The sync > command > locks up just like every other disk I/O when the event occurs. I tried this and it doesn't seem to have made a difference. Neither does using noop as the scheduler. -- 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
