From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: System freezes with kernel >2.6.19 - sata_nv [added crash info kern 2.6.21.1] Date: Wed, 02 May 2007 13:41:25 +0200 Message-ID: <463878E5.4020607@gmail.com> References: <46351BE2.70901@yahoo.de> <4635BF4A.3050509@gmail.com> <46367F58.7000609@shaw.ca> <4636A4DC.8070606@gmail.com> <4637CCEA.8020202@yahoo.de> <4637D3FA.2070403@shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from py-out-1112.google.com ([64.233.166.182]:50897 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755051AbXEBLmg (ORCPT ); Wed, 2 May 2007 07:42:36 -0400 Received: by py-out-1112.google.com with SMTP id a29so72759pyi for ; Wed, 02 May 2007 04:42:36 -0700 (PDT) In-Reply-To: <4637D3FA.2070403@shaw.ca> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Robert Hancock Cc: Stefan , linux-ide@vger.kernel.org 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. -- tejun