From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Hancock Subject: Re: disabling sata_nv ADMA for 2.6.24 Date: Mon, 07 Jan 2008 21:01:35 -0600 Message-ID: <4782E78F.9050205@shaw.ca> References: <4781F008.9070404@gmail.com> <4782422C.8020202@rtr.ca> <4782B73B.8080309@shaw.ca> <4782BC48.4000309@gmail.com> <4782C008.3030902@shaw.ca> <4782CB62.7040901@gmail.com> <4782CEF9.3040708@gmail.com> <4782DFFE.50301@shaw.ca> <4782E5A8.9010305@gmail.com> <4782E63E.1000606@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:56024 "EHLO pd4mo2so.prod.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752383AbYAHDCX (ORCPT ); Mon, 7 Jan 2008 22:02:23 -0500 Received: from pd3mr1so.prod.shaw.ca (pd3mr1so-qfe3.prod.shaw.ca [10.0.141.177]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JUB00K6R1QSN700@l-daemon> for linux-ide@vger.kernel.org; Mon, 07 Jan 2008 20:01:40 -0700 (MST) Received: from pn2ml7so.prod.shaw.ca ([10.0.121.151]) by pd3mr1so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JUB00DVV1QS7R60@pd3mr1so.prod.shaw.ca> for linux-ide@vger.kernel.org; Mon, 07 Jan 2008 20:01:40 -0700 (MST) Received: from [192.168.1.113] ([70.64.130.4]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JUB00FBQ1QQK5A0@l-daemon> for linux-ide@vger.kernel.org; Mon, 07 Jan 2008 20:01:39 -0700 (MST) In-reply-to: <4782E63E.1000606@gmail.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: Mark Lord , Jeff Garzik , IDE/ATA development list , Allen Martin , Peer Chen , Kuan Luo Tejun Heo wrote: > Tejun Heo wrote: >> Robert Hancock wrote: >>>> Okay, just succeeded on the current #upstream-fixes, attaching the log. >>>> The machine is a brick after the crash. >>> I assume the cable got reconnected at 325 seconds? It looks like that >>> was during error handling for the previous unplug? >> I don't remember too well (the console was more than two meters away and >> I was just keeping disconnecting and reconnecting. I noticed the >> machine was frozen after I came back to console, so... >> >>> [ 314.987885] ata3: timeout waiting for ADMA IDLE, stat=0x400 >>> [ 314.993556] ata3: timeout waiting for ADMA LEGACY, stat=0x400 >>> [ 315.009915] ata3.00: exception Emask 0x10 SAct 0x1 SErr 0x1910000 >>> action 0xa frozen >>> [ 315.017708] ata3.00: ADMA status 0x00000402: , hot unplug >>> [ 315.017714] ata3: SError: { PHYRdyChg Dispar LinkSeq TrStaTrns } >>> [ 315.029239] ata3.00: cmd 60/01:00:92:d7:12/00:00:05:00:00/40 tag 0 >>> ncq 512 in >>> [ 315.029240] res 40/00:04:92:d7:12/00:04:92:d7:12/40 Emask >>> 0x10 (ATA bus error) >>> [ 315.029243] ata3.00: status: { DRDY } >>> [ 315.048236] ata3: hard resetting link >>> [ 315.774982] ata3: SATA link down (SStatus 0 SControl 300) >>> [ 315.780498] ata3: failed to recover some devices, retrying in 5 secs >>> [ 320.788427] ata3: hard resetting link >>> [ 325.242220] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) >>> >>> Not sure if the port would be frozen at this point or not? >>> >>> It would be useful to add some printks to narrow down at what point the >>> lockup happens. If it's a loop, interrupt storm or something then we can >>> likely fix it, but if the controller's just locking up then we may be >>> out of luck.. >> I think it's machine hard lock up. NMI watchdog doesn't get triggered. Is NMI watchdog actually working on this machine? [ 34.466899] testing NMI watchdog ... <4>WARNING: CPU#0: NMI appears to be stuck (0->0)! [ 34.555056] WARNING: CPU#1: NMI appears to be stuck (0->0)! >> > > Ah.. another thing. Sometimes when I swap two drives, sata_nv fails to > detect the new drive. If I pull out the plug and replug it, it then > recognizes the new drive. No output in that case, I assume?