From: Tejun Heo <htejun@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: Gerold Jury <gml@inode.at>,
efault@gmx.de, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
vsu@altlinux.ru
Subject: Re: extra bytes written to SATA DVD drive on kernel 2.6.23 till 2.6.24.2
Date: Mon, 17 Nov 2008 12:05:00 +0900 [thread overview]
Message-ID: <4920DF5C.3030400@gmail.com> (raw)
In-Reply-To: <E1JXic1-0000Yo-K8@faramir.fjphome.nl>
Frans Pop wrote:
> Gerold Jury wrote:
>> 0001ffe0 e0 ff e1 ff e2 ff e3 ff e4 ff e5 ff e6 ff e7 ff |................|
>> 0001fff0 e8 ff e9 ff ea ff eb ff ec ff ed ff ee ff ef ff |................|
>> 00020000 2a 00 00 00 00 40 00 00 40 00 00 00 00 40 00 00 |*....@..@....@..|
>
> Looks broken here too.
>
>> 00020010 08 ff 09 ff 0a ff 0b ff 08 ff 09 ff 0a ff 0b ff |................|
>> 00020020 00 00 01 00 02 00 03 00 04 00 05 00 06 00 07 00 |................|
>
> It also seems like part gets repeated after the break in both cases.
Can you guys please add yourselves to bz#10743?
http://bugzilla.kernel.org/show_bug.cgi?id=10743
Please test 2.6.28-rc5 as it contains sata_via changes (TF access needed
specific workaround) and see whether the problem is fixed and report on bz.
Thanks a lot. Let's get this thing solved.
--
tejun
next prev parent reply other threads:[~2008-11-17 3:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 19:05 extra bytes written to SATA DVD drive on kernel 2.6.23 till 2.6.24.2 Gerold Jury
2008-02-25 23:32 ` Andrew Morton
2008-02-26 18:57 ` Gerold Jury
2008-02-28 7:30 ` Mike Galbraith
2008-02-29 21:59 ` Gerold Jury
2008-03-01 11:53 ` Sergey Vlasov
2008-03-01 12:29 ` Gerold Jury
2008-03-07 8:40 ` Tejun Heo
2008-03-07 19:09 ` Gerold Jury
2008-03-07 19:52 ` Frans Pop
2008-03-07 20:32 ` Frans Pop
2008-11-17 3:05 ` Tejun Heo [this message]
2008-11-17 8:18 ` Frans Pop
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=4920DF5C.3030400@gmail.com \
--to=htejun@gmail.com \
--cc=efault@gmx.de \
--cc=elendil@planet.nl \
--cc=gml@inode.at \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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.