From: Tejun Heo <htejun@gmail.com>
To: Fajun Chen <fajunchen@gmail.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: PATA Sil680 Warm Plug Caused 2.6.18-rc2 Kernel Internel Error
Date: Fri, 25 Aug 2006 02:02:09 +0900 [thread overview]
Message-ID: <44EDDB91.1050102@gmail.com> (raw)
In-Reply-To: <8202f4270608240942i6b620961t1a03d4148dd4a32d@mail.gmail.com>
[cc'ing linux-ide again]
Fajun Chen wrote:
> Hi Tejun,
>
> Your patch is successful at fixing the kernel error when adding pata
> drive on 2.6.18-rc2 but there's some sg availability issue. I did the
> same sequence of test: power off drive -> remove drive -> power on
> drive -> add drive. From dmesg log, pata drive was added back
> successfully as sg0 but somehow it is unavailable for upper level. For
> instance, sg_scan didn't detect it. It is not shown in
> /sys/class/scsi_generic/. Sg utilities sg_inq and sg_dd complained
> about no such device for sg0. Is there any magic command I need to
> issue to populate sg information up to the user space? If not, then
> there is still bug somewhere. Complete log of the test sequence is
> attached.
>
> I'll hold off the testing on 2.6.18-rc4 for now. Please let me know if
> you think it still makes sense to test your patch in the new release.
> Thanks for your help!
The thing is that the patch shouldn't really change behavior. With the
patch, libata might be more forgiving about SCSI refcnt bugs but the
code before and after are identical correctness-wise. ISTR there has
been SCSI ref bug fixed sometime inbetween. I can't pinpoint it though.
So, please try 2.5.18-rc4 w/ or w/o the patch. Pull
libata-dev#pata-drivers, that's basically current linus #master +
libata-dev#upstream updates + Alan's pata-drivers.
Of course, I might be wrong, but I kind of have too little lead to
follow on at the moment, especially because I can't reproduce it here.
If testing new kernel on your target platform takes a lot of effort,
just perform preliminary tests on x86. As far as SCSI and libata are
concerned, there's little difference.
--
tejun
next prev parent reply other threads:[~2006-08-24 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 16:06 PATA Sil680 Warm Plug Caused 2.6.18-rc2 Kernel Internel Error Fajun Chen
2006-08-23 16:24 ` Tejun Heo
2006-08-23 19:12 ` Fajun Chen
2006-08-23 19:24 ` Tejun Heo
2006-08-23 19:55 ` Fajun Chen
[not found] ` <8202f4270608231349v5aabace2xaff8fe93c133a7ca@mail.gmail.com>
[not found] ` <20060824070257.GD21866@htj.dyndns.org>
[not found] ` <8202f4270608240942i6b620961t1a03d4148dd4a32d@mail.gmail.com>
2006-08-24 17:02 ` Tejun Heo [this message]
2006-08-25 0:01 ` Fajun Chen
2006-08-25 15:26 ` Fajun Chen
2006-08-25 15:35 ` Tejun Heo
2006-08-25 17:27 ` Fajun Chen
2006-08-25 18:00 ` Tejun Heo
2006-08-25 20:19 ` Fajun Chen
2006-08-25 20:32 ` Tejun Heo
2006-08-23 16:24 ` Jeff Garzik
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=44EDDB91.1050102@gmail.com \
--to=htejun@gmail.com \
--cc=fajunchen@gmail.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).