From: Tejun Heo <htejun@gmail.com>
To: mark.paulus@verizonbusiness.com
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_sil issue on 2.6.22
Date: Thu, 06 Dec 2007 09:25:00 +0900 [thread overview]
Message-ID: <4757415C.9010906@gmail.com> (raw)
In-Reply-To: <4756BA80.1020902@verizonbusiness.com>
Mark Paulus wrote:
> Yes, I am. It's a SD-ADSAIDE-S1, with a sil3611ct80 chip on board.
>
> My question would be, what makes the 2.6.22 kernel different enough
> than the 2.6.18 kernel that this setup is causing problems in .22.
> Is .18 masking the problems, or is .22 just looking at things with
> tighter tolerences, so it's more sensitive?
That's to be investigated. There's another report of similar problem.
Can you please add yourself to the following bugzilla and add your log
there?
http://bugzilla.kernel.org/show_bug.cgi?id=9505
Thanks.
--
tejun
next prev parent reply other threads:[~2007-12-06 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 20:35 sata_sil issue on 2.6.22 Mark Paulus
2007-11-28 1:21 ` Tejun Heo
2007-11-30 15:56 ` Mark Paulus
2007-12-04 2:54 ` Tejun Heo
2007-12-05 14:29 ` Mark Paulus
2007-12-05 14:33 ` Tejun Heo
2007-12-05 14:49 ` Mark Paulus
2007-12-06 0:25 ` Tejun Heo [this message]
2007-12-06 2:10 ` 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=4757415C.9010906@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mark.paulus@verizonbusiness.com \
/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).