From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Hancock Subject: Re: disabling sata_nv ADMA for 2.6.24 Date: Tue, 08 Jan 2008 21:50:09 -0600 Message-ID: <47844471.4070705@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> <4782E78F.9050205@shaw.ca> <4782E912.1050204@gmail.com> <4783493A.7070800@gmail.com> <47838B57.8020407@shaw.ca> <47842A54.2060107@gmail.com> <47842ABA.2060605@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]:31836 "EHLO pd4mo1so.prod.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753067AbYAIDuR (ORCPT ); Tue, 8 Jan 2008 22:50:17 -0500 Received: from pd2mr3so.prod.shaw.ca (pd2mr3so-qfe3.prod.shaw.ca [10.0.141.108]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JUC00GTVYNS1XB0@l-daemon> for linux-ide@vger.kernel.org; Tue, 08 Jan 2008 20:50:16 -0700 (MST) Received: from pn2ml1so.prod.shaw.ca ([10.0.121.145]) by pd2mr3so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JUC000E8YNSDU30@pd2mr3so.prod.shaw.ca> for linux-ide@vger.kernel.org; Tue, 08 Jan 2008 20:50:16 -0700 (MST) Received: from [192.168.1.113] ([70.64.130.4]) by l-daemon (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JUC00NZRYNQ1A30@l-daemon> for linux-ide@vger.kernel.org; Tue, 08 Jan 2008 20:50:15 -0700 (MST) In-reply-to: <47842ABA.2060605@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: >>> Tejun Heo wrote: >>>> Tejun Heo wrote: >>>>>> [ 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)! >>>>> Oops, missed that. I'll see whether there's IRQ storm going on. >>>> I made the nv irq handler to print message every 100th time and it says >>>> nothing after lock up and no response to keyboard, sysrq or serial. It >>>> seems like a solid lock up to me. Anything else you want me to try out? >>> I assume that replugging or unplugging cables after that point doesn't >>> bring it back to life? >> Nope. The machine is a solid brick. >> > > If you want, I can ship the board + processor + cooler to you for > debugging. I guess it will be more useful in your hands than mine. If it's an A8N-E I'd be surprised if it behaved differently from my A8N-SLI Deluxe, though maybe it's a different chipset revision or something.. The last time I tested hotplug on here it seemed to work fine, though I haven't done any rapid disconnect/reconnect tests. How about putting a bunch of printks inside the interrupt handler? That would tell us if it's even reaching the interrupt handler..