linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Torsten Kaiser <just.for.lkml@googlemail.com>,
	"Ip, Clarence" <CIP@harris.com>,
	linux-ide@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: FW: LIBATA issue with SATA drive
Date: Fri, 19 Oct 2007 11:36:27 +0900	[thread overview]
Message-ID: <4718182B.9040802@gmail.com> (raw)
In-Reply-To: <47180928.3020104@garzik.org>

Jeff Garzik wrote:
> Tejun Heo wrote:
>> Hello,
>>
>> Torsten Kaiser wrote:
>>>> The symptom seems very similar to yours but the kernel is 2.6.22 which
>>>> doesn't have the SG change which you found out to be broken.  Can you
>>>> update us on how the testing of patched kernel went?
>>>
>>> Sorry I didn't realize that you where still waiting for a 'confirm
>>> good'. I intended only to mail, if I got the error again, as the debug
>>> output about SGE_TRM confirmed, that this fix changes the behavior of
>>> sata_sil24 and there was no really 200% sure method of detecting that
>>> this bug was gone.
>>>
>>> Anyway, after fixing ata_sg_is_last() by adding the +1 I did not had a
>>> single failure.
>>>
>>> I'm currently using 2.6.23-mm1 and 16 boots where all good.
>>> (Apart from the unrelated failure with sata_nv and swncq...)
>>
>> I see, a different issue then.  It's just weird to see similar issues 
>> popping up now after allterm the time sata_sil24 has been around.
> 
> What kernel version are we talking about?  If it includes sg-chaining 
> via a git tree somewhere, sata_sil24 has a bug that was just fixed (by 
> removing ata_sg_is_last).

Yeah, that was what I thought and the reason why I cc'd Torsten but the 
kernel version in question here is 2.6.22.  :-(

-- 
tejun

  reply	other threads:[~2007-10-19  2:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17 16:13 FW: LIBATA issue with SATA drive Ip, Clarence
2007-10-18  4:09 ` Tejun Heo
2007-10-18 18:52   ` Torsten Kaiser
2007-10-19  1:13     ` Tejun Heo
2007-10-19  1:32       ` Jeff Garzik
2007-10-19  2:36         ` Tejun Heo [this message]
2007-10-19  4:51       ` Torsten Kaiser
2007-10-19  5:05         ` Tejun Heo
2007-10-19 16:21           ` Torsten Kaiser
2007-10-23  2:58             ` Tejun Heo

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=4718182B.9040802@gmail.com \
    --to=htejun@gmail.com \
    --cc=CIP@harris.com \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=just.for.lkml@googlemail.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).