All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Brad Fitzpatrick <brad@danga.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Norco DS-1220 (sil3726+sil3124) / libata-tj bug report
Date: Mon, 08 Jan 2007 11:33:40 +0900	[thread overview]
Message-ID: <45A1AD84.5060202@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0701050332200.26166@mailx>

Brad Fitzpatrick wrote:
> Tejun,
> 
> (I wanted to send this to linux-ide, but vger's majordomo isn't replying
> to me.  Feel free to cc: the list...)

Just cc'ing linux-ide@vger.kernel.org is enough.  (done)

> Disks in DS-1220 show up, kinda, but don't work.  Errors reading /
> writing blocks.  Tried a single disk in both a PMP port and a direct
> (non-sil3726) port.

>From full dmesg...

The following is when the drive is attached via PMP.

18:29:55 ata3.01: (irq_stat 0x00020002, device error via D2H FIS)
18:29:55 ata3.01: tag 0 cmd 0xc8 Emask 0x1 stat 0x50 err 0x0 (device error)

And directly.

19:30:23 ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
19:30:23 ata6.00: (irq_stat 0x00060002, device error via D2H FIS)
19:30:23 ata6.00: tag 0 cmd 0xc4 Emask 0x1 stat 0x50 err 0x0 (device error)
19:30:23 ata6: EH complete

Looks like a dead drive to me.  Care to post the result of 'smartctl -d
ata -a /dev/sdX' and test other drives?

-- 
tejun

       reply	other threads:[~2007-01-08  2:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.0701050332200.26166@mailx>
2007-01-08  2:33 ` Tejun Heo [this message]
2007-01-13  2:18   ` Norco DS-1220 (sil3726+sil3124) / libata-tj bug report Brad Fitzpatrick
2007-01-13 23:40     ` Brad Fitzpatrick
2007-01-15  5:08       ` Tejun Heo
2007-01-27  1:08       ` Jim Paris
2007-01-05  4:08 Brad Fitzpatrick
2007-01-05  5:34 ` Jim Paris

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=45A1AD84.5060202@gmail.com \
    --to=htejun@gmail.com \
    --cc=brad@danga.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 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.