Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754433Ab0AWIzX (ORCPT ); Sat, 23 Jan 2010 03:55:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752636Ab0AWIzT (ORCPT ); Sat, 23 Jan 2010 03:55:19 -0500 Received: from hera.kernel.org ([140.211.167.34]:48182 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752146Ab0AWIzN (ORCPT ); Sat, 23 Jan 2010 03:55:13 -0500 Message-ID: <4B5A70E5.6050106@kernel.org> Date: Sat, 23 Jan 2010 12:45:41 +0900 From: Tejun Heo User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091130 SUSE/3.0.0-1.1.1 Thunderbird/3.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Cengiz_G=FCnay?= CC: Robert Hancock , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: sata_nv times out for BD-ROM iHOS104-08 References: <4B31C8EE.3030003@kernel.org> <4B331771.3090309@kernel.org> <4B5666B4.6000804@kernel.org> <51f3faa71001191859l3c323a8ev6b7c0cced2c59e92@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (hera.kernel.org [127.0.0.1]); Sat, 23 Jan 2010 08:55:09 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 37 Hello, On 01/22/2010 11:11 PM, Cengiz G?nay wrote: > On Tue, Jan 19, 2010 at 9:59 PM, Robert Hancock wrote: >>>> 2009/12/24 Tejun Heo : >>> Hmm.... it worked? Does kernel parameter sata_nv.adma_enabled=0 make >>> any difference? Can you please attach boot log with the kernel >>> parameter specified? >> >> Think you meant maybe sata_nv.swncq=0 instead - this is an MCP51 >> controller so it doesn't support ADMA. I don't imagine SWNCQ would >> make any difference with an ATAPI device, but wouldn't hurt to try. > > Thanks for following this up. I tried both of your suggested kernel > parameters (attached). Neither solved my problem, but also it looks > like I couldn't turn off the SWNCQ mode. Even though I set it to zero, > sata_nv still shows that it uses it. Although the order of my devices > changed, so I assume it did something. The parameter isn't being passed to the module loaded by initrd. You probably need to edit modules.conf and then regenerate initrd. :-( > I hope this helps shed some light! I will also try the kernel patch -- > not sure if that is suited for the problem I'm having? Yeah, I was about to suggest trying the patch. It could be that the timeout used by the new TUR code is too aggressive. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/