From: "E. Oltmanns" <oltmanns@uni-bonn.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb-storage bug in 2.6.12-rc3
Date: Thu, 28 Apr 2005 13:35:33 +0000 [thread overview]
Message-ID: <87r7gvgh22.fsf@denkblock.local> (raw)
In-Reply-To: <1114633284.16803.17.camel@daxter.boston.redhat.com>
Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Wed, 2005-04-27 at 16:21 -0400, David Zeuthen wrote:
>> it seems that recent kernels (I'm using the Fedora 2.6.11-1.1268_FC4
>> kernel which I believe is based off 2.6.12-rc3 and AFAIK it doesn't have
>> any invasive patches in that area) has changed behavior wrt hotplug
>> event ordering. In [1], I've attached the debug output from
>> linux-hotplug. Here are the interesting bits:
>
>> 729 scsi_host path=/class/scsi_host/host9
>> physdevpath=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/host9
>>
>> 730 usb (interface) path=/devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0
>
> Btw: This happens only if the modules are already loaded. If the device
> causes the module-load everything looks sane. That must be the reason
> I've never seen HAL failing with this. :)
May I remind you that I've recently reported a problem on this list
which I suspect to be caused by timing problems similar to those discussed
here. In my case though, the problem occurred only when the module
usb-storage had to be loaded during hotplug event processing. You can
find the details of my problem in the Mail Message-ID:
<87br82sg0y.fsf@denkblock.local> with the subject
Once more udev/hotplug and usb-storage devices
If you tell me how to produce these listings as you provided them in
your mail, I can try to generate something useful to analyse my problem.
>
> == add device first time => 941 /devices/pci0000:00/0000:00:1d.1/usb3/3-1
> 942 /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0
> 943 /module/usb_storage
> 944 /bus/usb/drivers/usb-storage
> 945 /class/scsi_host/host0
>
> == reconnect device => 959 /devices/pci0000:00/0000:00:1d.1/usb3/3-1
> 960 /class/scsi_host/host1
> 961 /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0
>
Thank you very much,
Elias
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-04-28 13:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 20:21 usb-storage bug in 2.6.12-rc3 David Zeuthen
2005-04-27 21:21 ` [linux-usb-devel] " Alan Stern
2005-04-27 23:14 ` Patrick Mansfield
2005-04-28 0:47 ` Kay Sievers
2005-04-28 4:34 ` Greg KH
2005-04-28 10:21 ` Kay Sievers
2005-04-28 13:35 ` E. Oltmanns [this message]
2005-04-28 14:15 ` Patrick Mansfield
2005-04-29 14:23 ` E. Oltmanns
2005-04-29 18:23 ` [linux-usb-devel] " Roman Kagan
2005-04-29 19:28 ` David Brownell
2005-04-29 19:35 ` Oliver Neukum
2005-04-29 20:00 ` Greg KH
2005-04-29 20:01 ` Greg KH
2005-04-29 20:16 ` Oliver Neukum
2005-04-29 20:50 ` David Brownell
2005-04-29 21:07 ` David Zeuthen
2005-05-04 7:05 ` Roman Kagan
2005-05-18 14:19 ` David Zeuthen
2005-05-18 17:03 ` Greg KH
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=87r7gvgh22.fsf@denkblock.local \
--to=oltmanns@uni-bonn.de \
--cc=linux-hotplug@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).