From: Brian King <brking@linux.vnet.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Jeff Garzik <jgarzik@pobox.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: ipr SATA problems in 2.6.20
Date: Tue, 16 Jan 2007 16:24:45 -0600 [thread overview]
Message-ID: <45AD50AD.2040700@linux.vnet.ibm.com> (raw)
I'm currently debugging some problems with SATA on ipr and figured I would
give a heads up. The problems include overlength errors and data corruption.
Basically SATA on ipr is completely broken in its current state.
>From what I have found so far, it looks like due to some libata changes
made recently, qc->nbytes is no longer getting setup for ATAPI devices
all the time.
Jeff - should qc->nbytes be used a libata user? If not, what is the proper
way to determine the total command length in bytes? Summing all the sg entries?
I was using nbytes + pad_len.
The other oddity I've been seeing is that I am getting zero length commands,
such as TEST_UNIT_READY with a dma_dir of DMA_FROM_DEVICE. Shouldn't this be
DMA_NONE? I'm still tracking this down.
Brian
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next reply other threads:[~2007-01-16 22:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 22:24 Brian King [this message]
2007-01-16 22:41 ` ipr SATA problems in 2.6.20 Alan
2007-01-16 22:45 ` Jeff Garzik
2007-01-16 23:11 ` James Bottomley
2007-01-16 23:17 ` Brian King
2007-01-16 23:30 ` James Bottomley
2007-01-16 23:33 ` Brian King
2007-01-17 2:34 ` [PATCH] libata: initialize qc->dma_dir to DMA_NONE Tejun Heo
2007-01-17 3:43 ` Brian King
2007-01-17 3:59 ` Jeff Garzik
2007-01-17 14:37 ` Brian King
2007-01-17 18:35 ` Brian King
2007-01-17 15:19 ` James Bottomley
2007-01-17 15:49 ` Tejun Heo
2007-01-17 16:07 ` James Bottomley
2007-01-20 0:19 ` Jeff Garzik
2007-01-16 23:28 ` ipr SATA problems in 2.6.20 Alan
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=45AD50AD.2040700@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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.