linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Denys Dmytriyenko <denis@denix.org>,
	Gabor FUNK <FUNK.Gabor@hunetkft.hu>,
	linux-ide@vger.kernel.org, Jim Paris <jim@jtan.com>
Subject: Re: sata_sil24 stability and performance
Date: Tue, 18 Mar 2008 16:06:55 -0400	[thread overview]
Message-ID: <47E020DF.9030900@rtr.ca> (raw)
In-Reply-To: <47E02090.80000@rtr.ca>

Mark Lord wrote:
> Tejun Heo wrote:
>> Denys Dmytriyenko wrote:
> ..
>>> Mar 14 23:51:55 [kernel] ata3: failed to read log page 10h (errno=-2)
>>> Mar 14 23:51:55 [kernel] ata3.00: exception Emask 0x1 SAct 0x3f SErr 
>>> 0x0 action 0x0
>>> Mar 14 23:51:55 [kernel] ata3.00: irq_stat 0x00020002, device error 
>>> via SDB FIS
>>
>> This one is different.  The drive reported device error but the driver
>> couldn't get more information about the error (log page 10h contains it).
> ..
> 
> That, is one of the known errata that has yet to be fixed in the driver.
> The READ LOG EXT command cannot be used in the normal fashion after an 
> NCQ error.
..

Whoops.. scratch that.. I thought Denys was trialing sata_mv there,
not sata_sil24 as it turns out.

-ml

      reply	other threads:[~2008-03-19 19:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  2:09 sata_sil24 stability and performance Denys Dmytriyenko
2008-02-19  4:36 ` Jim Paris
2008-02-19  6:39   ` Denys Dmytriyenko
2008-02-19 15:32   ` Mark Lord
2008-03-02  6:14     ` Denys Dmytriyenko
2008-03-02  9:39       ` Gabor FUNK
2008-03-04  0:02         ` Tejun Heo
2008-03-04  0:22           ` Denys Dmytriyenko
2008-03-04  3:28             ` Tejun Heo
2008-03-04  6:29               ` Denys Dmytriyenko
2008-03-05  8:11                 ` Tejun Heo
2008-03-06  4:14                   ` Denys Dmytriyenko
2008-03-06  4:25                     ` Tejun Heo
2008-03-06  6:55                       ` Denys Dmytriyenko
2008-03-06  7:08                         ` Tejun Heo
2008-03-15 21:43                           ` Denys Dmytriyenko
2008-03-17  3:09                             ` Mark Lord
2008-03-18  0:15                               ` Denys Dmytriyenko
2008-03-18  4:09                                 ` Tejun Heo
2008-03-18  4:53                                   ` Denys Dmytriyenko
2008-03-18  6:40                                     ` Tejun Heo
2008-03-20 22:37                                       ` Denys Dmytriyenko
2008-03-21  0:18                                         ` Tejun Heo
2008-04-14  1:19                                           ` Denys Dmytriyenko
2008-04-14  2:49                                             ` Tejun Heo
2008-04-14 10:55                                             ` Gabor FUNK
2008-03-18  9:14                                     ` Gabor FUNK
2008-03-18 13:06                                       ` Gabor FUNK
2008-03-18 20:05                                   ` Mark Lord
2008-03-18 20:06                                     ` Mark Lord [this message]

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=47E020DF.9030900@rtr.ca \
    --to=liml@rtr.ca \
    --cc=FUNK.Gabor@hunetkft.hu \
    --cc=denis@denix.org \
    --cc=htejun@gmail.com \
    --cc=jim@jtan.com \
    --cc=linux-ide@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 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).