linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Power <rpower@sysreset.com>
To: Robert Hancock <hancockr@shaw.ca>, Tejun Heo <htejun@gmail.com>
Cc: Petr Vandrovec <petr@vandrovec.name>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Unbreak build of PMP with ACPI disabled
Date: Fri, 13 Jul 2007 18:00:36 -0600	[thread overview]
Message-ID: <6.2.0.14.2.20070713175627.031aada0@linux.sysreset.com> (raw)
In-Reply-To: <46980AFD.3000503@shaw.ca>

I'm also experiencing this problem on a with the sata_nv module.  I suspect 
that it may at least not be controller dependant, as it's also occurring on 
my silicon image controller (sata_sil, SiI3512).  It looks like something 
is zeroing out part of the return registers for the overall smart status.

Tested with Maxtor 6L300S0 and Western Digital WD3200JS drives on both the 
sil and nv controllers.  This was working in 2.6.21.6, but I haven't had a 
chance to try and isolate the problem any further.

Thanks.
-Ryan Power

At 05:30 PM 7/13/2007, Robert Hancock wrote:
>Tejun Heo wrote:
>>>Only problem I've noticed is that smartctl on drives connected to sata_nv
>>>needs '-T permissive', while if same drive is connected to sata_sil24's PMP,
>>>it works without problem.
>>>
>>>Error SMART Status command failed
>>>Please get assistance from http://smartmontools.sourceforge.net/
>>>Values from ATA status return descriptor are:
>>>  00     09 0c 00 00 00 00 00 00  00 00 00 00 00 50
>>>A mandatory SMART command failed: exiting. To continue, add one or more 
>>>'-T permissive' options.
>>Yeah, we seem to have some problem with passing result TF to userland in
>>sata_nv (cc'ed Robert).
>>Thanks.
>
>I've seen that report, but it's a bit of a mystery to me. Apparently the 
>problem still happens if ADMA is disabled, and in that mode we just use 
>the standard ata_tf_read function, so it's not clear how it could not be 
>working on that controller but work on others..
>
>Also I haven't noticed any SMART problems on my machine with ADMA 
>enabled.. maybe it's drive or motherboard dependent?


  reply	other threads:[~2007-07-14  0:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13  6:56 [PATCH] Unbreak build of PMP with ACPI disabled Petr Vandrovec
2007-07-13  7:09 ` Tejun Heo
2007-07-13 23:30   ` Robert Hancock
2007-07-14  0:00     ` Ryan Power [this message]
2007-07-14  2:31       ` Tejun Heo
2007-07-14 12:13         ` Petr Vandrovec
2007-07-16  3:38           ` Ryan Power
2007-07-16 10:32           ` Tejun Heo
2007-07-17 10:54             ` [PATCH] Fix SMART reporting on 2.6.22 Petr Vandrovec
2007-07-18  3:08               ` Tejun Heo
2007-07-20 11:44               ` Jeff Garzik

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=6.2.0.14.2.20070713175627.031aada0@linux.sysreset.com \
    --to=rpower@sysreset.com \
    --cc=hancockr@shaw.ca \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=petr@vandrovec.name \
    /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;
as well as URLs for NNTP newsgroup(s).