public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Charles Shannon Hendrix <shannon@widomaker.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_nv adma issues
Date: Mon, 11 Jun 2007 23:55:47 -0600	[thread overview]
Message-ID: <466E3563.1030900@shaw.ca> (raw)
In-Reply-To: <fa.FTA/czKnA9MrTZ9ueGrcQfRm9qs@ifi.uio.no>

Charles Shannon Hendrix wrote:
> 
> My system has issues running adma mode with sata_nv.  I have an nforce4 
> motherboard.
> 
> What is the current status of this problem?

You'll have to be a bit more specific than that. A few problems have 
arisen in the past, but currently I don't think there is anything known 
outstanding other than one hotplug issue which currently is lacking in 
information to debug.

> 
> Is there any information I can provide to help debug it?
> 
> I gave up trying various fixes about 6 months ago, and put 
> "sata_nv.adma=0" on the kernel command line in LILO, and that fixed the 
> problem.
> 
> However, recently I changed distributions and went back to 2.6.20 
> (kubuntu 7.04).
> 
> This kernel says that sata_nv.adma=0 is an invalid kernel option.
> 
> I'm pretty puzzled by that, because it is supposed to disable adma mode 
> in the sata_nv driver.
> 
> /proc/cmdline says:
> 
> root=<hash> ro sata_nv.adma=0 quiet splash
> 
> ..so it seems I did give the parameter properly.
> 
> Any ideas appreciated.

If sata_nv is built modular, then you may need to put:

options sata_nv adma=0

in /etc/modprobe.conf instead.

However I should point out that adma=0 is a poor workaround, it would be 
better to find the real cause of the problem.

> 
> Is there a better way to deal with this?
> 
> Also, one more: does it hurt to wait until the sata_nv driver fails a 
> few times (at which point it stops bitching) and use the machine?  Once it
> fails about 6 times, I no longer have any issues, and speed is still 
> good enough to use until a real fix can be had.

Please post the dmesg output from when this happens. If it starts 
working after the kernel disables NCQ, then it might mean that your 
drive has some problems with NCQ..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-06-12  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.FTA/czKnA9MrTZ9ueGrcQfRm9qs@ifi.uio.no>
2007-06-12  5:55 ` Robert Hancock [this message]
     [not found]   ` <466ECA55.8020100@widomaker.com>
2007-06-12 23:27     ` sata_nv adma issues Robert Hancock
2007-06-11 23:55 Charles Shannon Hendrix

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=466E3563.1030900@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shannon@widomaker.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox