All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Cengiz Günay" <cgunay@emory.edu>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata_nv times out for BD-ROM iHOS104-08
Date: Sat, 23 Jan 2010 12:45:41 +0900	[thread overview]
Message-ID: <4B5A70E5.6050106@kernel.org> (raw)
In-Reply-To: <d2d378041001220611ieb9d715of8d727f8f93ca9f@mail.gmail.com>

Hello,

On 01/22/2010 11:11 PM, Cengiz Günay wrote:
> On Tue, Jan 19, 2010 at 9:59 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
>>>> 2009/12/24 Tejun Heo <tj@kernel.org>:
>>> 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

  reply	other threads:[~2010-01-23  8:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 16:07 sata_nv times out for BD-ROM iHOS104-08 Cengiz Gunay
2009-12-23  7:38 ` Tejun Heo
     [not found]   ` <d2d378040912232302u4b550dap687fcadced237935@mail.gmail.com>
2009-12-24  7:25     ` Tejun Heo
2010-01-16 21:34       ` Cengiz Günay
2010-01-17 15:28         ` Ozan Çağlayan
2010-01-19  9:05           ` Tejun Heo
2010-01-19  9:34             ` Ozan Çağlayan
2010-01-20  2:13         ` Tejun Heo
2010-01-20  2:59           ` Robert Hancock
2010-01-22 14:11             ` Cengiz Günay
2010-01-23  3:45               ` Tejun Heo [this message]
2010-01-23 21:39                 ` Cengiz Günay
     [not found]                   ` <4B67A149.10406@kernel.org>
2010-02-17 16:14                     ` Cengiz Günay
2010-02-18  1:50                       ` Tejun Heo
2010-02-20 19:11                         ` Cengiz Günay
2010-02-21  1:01                           ` Tejun Heo
2010-02-21 21:28                             ` Cengiz Günay
2010-02-23  2:38                               ` Tejun Heo
2010-02-28 17:24                                 ` Cengiz Günay
2010-03-02 11:48                                   ` Tejun Heo
2010-03-08 19:17                                     ` Cengiz Günay
2010-03-08 23:46                                       ` Robert Hancock
2010-03-09  1:21                                       ` Tejun Heo
2010-03-09  5:18                                         ` Cengiz Günay
2010-05-25 19:34                                           ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2010-01-17  4:54 Gregory Moyer
2010-01-21  3:15 Gregory Moyer
2010-06-03 17:40 Gregory Moyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B5A70E5.6050106@kernel.org \
    --to=tj@kernel.org \
    --cc=cgunay@emory.edu \
    --cc=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.