On Mon, Sep 17, 2007 at 09:18:26PM +0400, Alexey Zaytsev wrote: > On 9/17/07, Sergey Dolgov <dolgovs@xxxxxxxxx> wrote: > > On 9/17/07, Tejun Heo <htejun@xxxxxxxxx> wrote: > > > > [...] > > > >>>> BTW, this only happens when using libata of course. The > > > >>>> old CONFIG_IDE stuff works fine every time. > > > >>> This maybe one of libata weirdness (I really don't get it why some hardware > > > >>> works perfectly fine with an old IDE and don't work well with libata). > > > >> Hmmm... Is MWDMA2 mode used with ide driver too? > > > >> > > > > > > > > What's the best way to tell whether it does or not? (the log says > > > > "selected mode 0x22", see below) > > > > > > Yes, that's MWDMA2. Hmm... We're seeing many cases where MWDMA doesn't > > > work with libata while it works fine with IDE but have no idea what's > > > going on yet. :-( > > > > > > > This may be well a hardware problem. Same laptop (HP nx7300 GB848ES) > works fine with either 2.6.22 and 2.6.23-rc. Maybe actually using the > DVD is required to trigger the problem on the next reboot? No, that is not required. The problem shows up on a fresh start from powered-off state just as well. > Sergey, btw, on this laptop I've observed lockups twice with the -rc5. > After switching to 2.6.22 it was stable for at least one day. Can you > confirm or refute this? I've been using 2.6.23 rcs (rc3, rc6) since August, often for days without rebooting the machine. Haven't seen any lockups (except the ones on a return from suspend-to-RAM, but that's another story). -- Sergey - 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
