All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sune Mølgaard" <sune@molgaard.org>
To: linux-kernel@vger.kernel.org
Subject: WRITE SAME failed in recent kernels
Date: Sun, 14 Apr 2013 08:35:25 +0200	[thread overview]
Message-ID: <516A4E2D.30203@molgaard.org> (raw)

Dear All,

In the setting of an SSD and an HDD connected to a HighPoint RocketRAID
620, I am seeing quite a number of log messages such as:

Apr 14 06:02:30 jekaterina kernel: [  952.460537] sd 8:0:1:0: [sde]
Unhandled error code
Apr 14 06:02:30 jekaterina kernel: [  952.460542] sd 8:0:1:0: [sde]
Apr 14 06:02:30 jekaterina kernel: [  952.460544] Result: hostbyte=0x05
driverbyte=0x05
Apr 14 06:02:30 jekaterina kernel: [  952.460546] sd 8:0:1:0: [sde] CDB:
Apr 14 06:02:30 jekaterina kernel: [  952.460548] cdb[0]=0x41: 41 00 a8
c6 fb 78 00 00 18 00
Apr 14 06:02:30 jekaterina kernel: [  952.460557] end_request: I/O
error, dev sde, sector 2831612792
Apr 14 06:02:30 jekaterina kernel: [  952.460566] sde1: WRITE SAME
failed. Manually zeroing.

with sde being the regular HDD.

Now, I am aware that the HighPoint driver, rr62x, isn't part of
mainline, and thus I have contacted HighPoint Technologies as well, but
I would like to know how to ascertain whether this is, indeed, a problem
with their driver, or if it's a problem pertaining to the kernel itself.

Any help, really, is much appreciated, even if it amounts to "HighPoint
is to blame", as I would then have that on higher authority than myself.

Best regards,

Sune Mølgaard

-- 
It's 106 miles to Chicago, we got a full tank of gas, half a pack of
cigarettes, it's dark and we're wearing sunglasses. Hit it.
- Blues Brothers

             reply	other threads:[~2013-04-14  6:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14  6:35 Sune Mølgaard [this message]
2013-04-17 13:30 ` WRITE SAME failed in recent kernels Juno Krahn

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=516A4E2D.30203@molgaard.org \
    --to=sune@molgaard.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.