Tejun Heo wrote:
While playing with nvraid, I found out that rmmoding and insmoding often trigger hardreset failure on the first port (the second one was always okay). Seriously, how diverse can you get with hardreset behaviors? Anyways, make ck804 use noclassify variant too. Signed-off-by: Tejun Heo <tj@xxxxxxxxxx> --- Robert, ISTR that a user was reporting probing problem on ck804, I think the user could have been seeing this. The behavior on my motherboard is very curious. The problem is always with the first port. If booted from cdrom, it always fails. If booted from harddrive, the initial probing works fine but from the second time on, it fails. Argh...
Yeah, it's amazing how their controllers can be messed up with hardreset in so many varying and creative ways. One only hopes their newer AHCI based controllers have fewer bugs..
I saw another problem recently on CK804, where an error occurs on a DVD drive (due to a scratched disc or something). This was in Windows, using the default Microsoft IDE driver. It would either blue-screen the machine with a machine check exception or just cause a hard lockup. People have reported this in Linux as well, it seems like the controller fails to respond to register accesses and triggers a northbridge transaction timeout MCE. Obviously not a driver problem, then.. Ended up switching the optical drives to the Silicon Image controller on this board because the CK804 controller just wasn't reliable with them.
-- 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
