From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: 2.6.23.1 - sata_mv (7042) hang with large file operations Date: Wed, 14 Nov 2007 17:31:05 -0500 Message-ID: <473B7729.1070703@rtr.ca> References: <45ED682A.9040408@garzik.org> <4728A816.8020608@garzik.org> <473B36D7.8000205@rtr.ca> <473B44CB.6010209@rtr.ca> <473B76E0.7010500@rtr.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rtr.ca ([76.10.145.34]:4173 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753174AbXKNWbH (ORCPT ); Wed, 14 Nov 2007 17:31:07 -0500 In-Reply-To: <473B76E0.7010500@rtr.ca> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: "Morrison, Tom" Cc: Jeff Garzik , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org Mark Lord wrote: > Morrison, Tom wrote: >> I have gotten it to boot from those hard-drives and it has the same >> behavior: >> >> Copying a large file to the same partition (>150MEG) >> causes the system to hang (no I/O - no input/output - nothing - >> complete freeze - like a primary resource is locked up or >> interrupts got completely & totally turned off in an ISR and its >> pending for something? >> >> Only way to get out of this is to power-cycle the box! > .. > > Okay, a couple of things: > > Do this from a text console, not a GUI. > And preferably without ever starting klogd/syslogd during init. > > That way you've a much better chance of seeing some kernel diagnostic > messages when it locks up. > > Can you boot with "nomsi" kernel parameter? > And I guess we'll need to see the entire kernel .config as well. ... And also a copy of the full kernel log messages from boot up until just before you run the lockup sequence. Thanks