All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-hotplug@vger.kernel.org
Subject: Re: Weird race-like problem in udev
Date: Tue, 22 Jun 2010 12:06:45 +0000	[thread overview]
Message-ID: <201006221506.45266.ozan@pardus.org.tr> (raw)
In-Reply-To: <4C1F97A0.2040905@pardus.org.tr>

Salı 22 Haziran 2010 günü (saat 14:31:57) Kay Sievers şunları yazmıştı:

> 
> Please, this isn't a quiz here, so provide the needed basic
> information that goes beyond "a device" and " the driver". :)

Ok, I'm very suspicious about the report and what the user describes, too. 
I'll try to detail in here.

What he's talking about in its bug report is a USB mass storage device:

[ 4741.302054] usb 1-2: new high speed USB device using ehci_hcd and address 3
[ 4743.914330] usb 1-2: New USB device found, idVendor\x066f, idProduct€00
[ 4743.914343] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 4743.914353] usb 1-2: Product: <USB PRODUCT>
[ 4743.914360] usb 1-2: Manufacturer: <USB MF>
[ 4743.914367] usb 1-2: SerialNumber: 0002F68C0A104E19
[ 4743.914623] usb 1-2: configuration #1 chosen from 1 choice

He also mentions that its webcam driver doesn't get loaded too. He posted the 
test-webcam output which complains about a non existing /dev/video0 node.

If the devices are plugged and then the system is rebooted, all the related 
drivers are loaded and he tells that he has no problems at all.


> 
> > * He discovered that spawning a 2nd udevd by hand resolves the issue
> 
> That's not possible, udevd will refuse to start a second time, and not
> do anything. It lets this report look suspicious that something is
> wrong with the way the behavior is described.

I misunderstood this. He was talking about killing and respawning udevd, not 
spawning a 2nd or a 3rd one, sorry. But yes he says that killing and 
respawning it resolves the issue.

I am not really hopeful to get this resolved as trying to ask him and waiting 
for an answer is very hard for that kind of standard users who are not 
familiar at all with udev, kernel, etc. Sorry for the inconvenience, I will 
report back here if I get something valuable.

Regards,


---
Ozan Çağlayan
TUBITAK/UEKAE - Pardus Linux
http://www.pardus.org.tr/eng

  parent reply	other threads:[~2010-06-22 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 16:47 Weird race-like problem in udev Ozan Çağlayan
2010-06-22 11:31 ` Kay Sievers
2010-06-22 12:06 ` Ozan Çağlayan [this message]
2010-06-22 13:40 ` Kay Sievers

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=201006221506.45266.ozan@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --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 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.