https://bugzilla.novell.com/show_bug.cgi?id=326952#c31
Tejun Heo changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |kasievers@novell.com
--- Comment #31 from Tejun Heo 2007-11-12 03:23:16 MST ---
libata uses different initialization sequence than IDE. libata resets the
channel during initialization while IDE doesn't. libata's sequence is usually
more robust but not in your case. Due to the faulty hardware, the reset
protocol didn't finish in the specified time.
<4>ata2: port is slow to respond, please be patient (Status 0x80)
<3>ata2: SRST failed (errno=-16)
Sorry but I don't think we can fix this. It's broken hardware configuration.
Some method might work while others might not. There isn't much point to
support any particular set of broken configuration.
That said, there can be some problems with the current device signature /
diagnostic failure handling in the current libata code. I'll take a look at
bug 332316 to see whether that's the case.
Is Ralf's case caused by haldaemon's query commands timing out? If so, I now
know what's wrong with libata ATAPI support and am preparing generic fix for
the problem. I think we'll need libata backport driver update disk for SL103.
:-(
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.