On Saturday 18 September 2010 21:22:54 Maxim Levitsky wrote: > On Sat, 2010-09-18 at 11:12 -0600, Joshua Hintze wrote: > > I'm dedicated to continue working on the problem, I just need to advice from > > the linux community. I've tried different I/O schedulers such as noop and > > anticipatory and I'm studying the ide-dma code but still lost to where this > > is happening. > > > > Thanks! > > > Maybe you can just bisect this? That would probably help to pinpoint the problem. A regression somewhere between 2.6.10 and 2.6.32 is not that interesting when people are working on stabilizing 2.6.36 and adding features to 2.6.37. One important question would be if this happens with the libata drivers in 2.6.36-rc4 or linux-next as well. Note that the IDE subsystem has been replaced with libata a few years ago, and that is what all development happens on. If libata is good enough, there is probably no point in chasing down ide bugs. Arnd -- 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
