From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [libata/sata_sil] Error on startup Date: Mon, 15 Sep 2008 03:24:54 -0700 Message-ID: <48CE37F6.40301@kernel.org> References: <48CBB831.9030403@ru.mvista.com> <48CE2389.9080205@kernel.org> <48CE3497.4000604@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from hera.kernel.org ([140.211.167.34]:53884 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752146AbYIOK1i (ORCPT ); Mon, 15 Sep 2008 06:27:38 -0400 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Alex Gonzalez Cc: Sergei Shtylyov , linux-ide@vger.kernel.org Hello, Alex Gonzalez wrote: > I haven't placed the drive under stress test, but it does work OK > under normal conditions without errors or timeouts in the log. Hmm... Okay. >>>From the cache error, I know that the physical region iomapped in > 0xf0000000 - 0xf0000200 is the PCI memory space, so the exception is > being caused by trying to access this area. > > I haven't yet looked deeply into it, I was assuming the action of > stopping the bmdma engine might have triggered the exception. If not, > why not receive an immediate exception without the 10secs timeout? Yeah, it's caused by EH trying to stop the BMDMA engine but it shouldn't. It works well on other platforms. Can you try to diagnose the bus failure? Working EH will be able to tell us more about the problem. -- tejun