Small correction:
>> > > Should I just push commit 1e75540ec5202cae63cd238c86bd880e3d496546
>> > > ("ide-tape: remove back-to-back REQUEST_SENSE detection") to Linus
>> > > or there is more needed to bring ide-tape to the world of living?
>> >
>> > The oops will probably fixed the above commit. I don't have much idea
>> > about the DMA problem on 2.6.24 tho. But even with the above commit
>> > fixed, I doubt it would work. The buffer allocation code is broken
>> > and reliably triggered OOM on my test machine. While trying to locate
>> > the bug, I realized the complex code didn't do much good to begin with
>> > and just stripped it down, so I didn't actually tracked down the
>> > actual bug && the patch to simplify buffer management is way too large
>> > for 2.6.29, so unless someone is willing to hunt down the bug just for
>> > 2.6.29, we're kind of stuck. :-(
>>
>> So I take it that 2.6.30 (or one of the RCs) is worth trying (at least in so
>> far as preventing the oops on boot)?
>
> You could try 30-rc6 which runs pretty stable on my machines. It has the
> patch mentioned above in it.
the patch mentioned above got actually merged after 30-rc6 so you could try
30-rc7 - if there will be one - or a current linux-next release.
Thanks.
--
Regards/Gruss,
Boris
--
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
