From: Jeff Garzik <jeff@garzik.org>
To: Komuro <komurojun-mbn@nifty.com>
Cc: Tejun Heo <htejun@gmail.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
jgarzik@redhat.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-pcmcia <linux-pcmcia@lists.infradead.org>,
Kristoffer Ericson <kristoffer.ericson@gmail.com>
Subject: Re: [KERNEL 2.6.26-rc4] bugreport : pata_pcmcia with Sandisk Extreme III 8GB
Date: Sat, 14 Jun 2008 03:20:41 -0400 [thread overview]
Message-ID: <48537149.4040102@garzik.org> (raw)
In-Reply-To: <20080614120055.ad8fbee0.komurojun-mbn@nifty.com>
Komuro wrote:
> Dear Tejun
>
>>>>>> pcmcia: registering new device pcmcia1.1
>>>>>> 1.1: GetNextTuple: No more items
>>>>>> pata_pcmcia: probe of 1.1 failed with error -12
>
> The patch "libata: kill hotplug related race condition"
> introduced the pata_pcmcia error.
>
> Please fix this problem.
>
>
> Best Regards
> Komuro
>
>>> f046519fc85a8fdf6a058b4ac9d897cdee6f3e52 is first bad commit
> commit f046519fc85a8fdf6a058b4ac9d897cdee6f3e52
> Author: Tejun Heo <htejun@gmail.com>
> Date: Mon May 19 01:15:08 2008 +0900
>
> libata: kill hotplug related race condition
>
> Originally, whole reset processing was done while the port is frozen
> and SError was cleared during @postreset(). This had two race
> conditions. 1: hotplug could occur after reset but before SError is
> cleared and libata won't know about it. 2: hotplug could occur after
> all the reset is complete but before the port is thawed. As all
> events are cleared on thaw, the hotplug event would be lost.
Interesting! Thanks for the diagnosis...
Jeff
next prev parent reply other threads:[~2008-06-14 7:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080528225049.9a134e0d.Kristoffer.Ericson@Gmail.com>
[not found] ` <20080528222740.GB20893@isilmar.linta.de>
[not found] ` <20080530135728.be02d3dc.Kristoffer.Ericson@Gmail.com>
2008-06-07 13:37 ` [KERNEL 2.6.26-rc4] bugreport : pata_pcmcia with Sandisk Extreme III 8GB Komuro
2008-06-11 7:20 ` Dominik Brodowski
2008-06-14 3:00 ` Komuro
2008-06-14 3:00 ` Komuro
2008-06-14 7:20 ` Jeff Garzik [this message]
2008-06-14 12:36 ` Komuro
2008-06-16 3:07 ` Tejun Heo
2008-06-16 13:11 ` Komuro
2008-06-16 13:11 ` Komuro
2008-06-16 13:24 ` Tejun Heo
2008-06-17 12:23 ` Komuro
2008-06-17 14:09 ` Tejun Heo
2008-06-17 14:15 ` Dominik Brodowski
2008-06-18 12:23 ` Komuro
2008-07-06 1:37 ` Komuro
2008-07-06 1:37 ` Komuro
2008-07-06 14:19 ` Tejun Heo
2008-07-07 12:42 ` Komuro
2008-07-07 12:42 ` Komuro
2008-07-09 4:10 ` Tejun Heo
2008-07-12 2:39 ` Komuro
2008-07-12 2:39 ` Komuro
2008-06-22 1:07 ` Komuro
2008-06-22 1:07 ` Komuro
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=48537149.4040102@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=jgarzik@redhat.com \
--cc=komurojun-mbn@nifty.com \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
/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.