Tejun Heo wrote: > Robert Hancock wrote: > >> Stefan wrote: >> >>> Okay, I had time to set this up. I'm attaching the log messages I got >>> via netconsole. >>> >>> I tested about 20h with adma disabled, the crash won't occur. >>> >>> If I remove >>> >>> sata_nv.adma=0 >>> >>> from boot options again it doesn't take long until my machine locks up. >>> >>> [Attached dmesg output with 2.6.21.1 kernel + crash info I got via >>> netconsole] >>> >>> I hope this is useful to you guys. >>> >> It looks like you've got SError bits set from the controller, 0x200000 >> means link layer CRC error (btw, we really should be decoding that error >> and printing it in human readable form rather than making people pore >> through the SATA spec and count bits). >> > > Hmmm... Maybe, but most of the bits are nearly meaningless to end users > anyway. > > >> First thing you should try is replacing the SATA cable to that drive. >> > > Yeap, please apply some hardware debugging techniques - replacing / > reseating SATA cables and connecting it to different power connector. > But it's disturbing to see machine lock up even if CRC error occurs. > sata_nv non-adma interface locks the whole machine up too after certain > error conditions but I thought adma was saner than that. I hope we can > work around this somehow. > > Thanks. > > Hi folks, got some news: I replaced cables, which didn't change anything. My PSU is strong enough to take a lot more, so I don't think it could be a power problem. Therefore I replaced the SAMSUNG HD401LJ with ST3160812AS. With the seagate attached I don't get the crash. So this may be a problem in combination with the HD401LJ+ NFORCE4 + ADMA. --Stefan - 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
