From: Alan <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: brking@linux.vnet.ibm.com, linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@steeleye.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: ipr SATA problems in 2.6.20
Date: Tue, 16 Jan 2007 23:28:07 +0000 [thread overview]
Message-ID: <20070116232807.79fa52d3@localhost.localdomain> (raw)
In-Reply-To: <45AD55A4.50208@pobox.com>
On Tue, 16 Jan 2007 17:45:56 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> Alan wrote:
> >> 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.
> >
> > I was looking at a PATA trace that was looking the same 2 days ago and
> > couldn't figure what was going on.
>
> Tejun recently updated the CDB length areas of the code. I bet it's
> either a bug somewhere in there, or the SCSI layer isn't passing us
> proper command lengths in a case or two.
That might explain a few things - the qemu PIIX3 emulation bug possibly
and also perhaps the recent NVidia iommu fun.
Alan
prev parent reply other threads:[~2007-01-16 23:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 22:24 ipr SATA problems in 2.6.20 Brian King
2007-01-16 22:41 ` 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 ` Alan [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=20070116232807.79fa52d3@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@steeleye.com \
--cc=brking@linux.vnet.ibm.com \
--cc=htejun@gmail.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.