From: Greg Huber <ghuber@vanteon.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB driver and udev_run_devd
Date: Fri, 11 May 2007 12:59:26 +0000 [thread overview]
Message-ID: <464468AE.3050400@vanteon.com> (raw)
In-Reply-To: <46437A8C.2070402@vanteon.com>
Kay,
Thank you for your reply.
(sorry for the delay, the last reboot required a filesystem check)
/proc/$(pidof udev_run_devd)/environ returned (formatted)
[root@huberkahn 6282]# cat environ
UDEV_LOG=3
ACTIONd
DEVPATH=/class/usb_endpoint/usbdev4.2_ep81
SUBSYSTEM=usb_endpoint
SEQNUM’0
MAJOR%3
MINOR!
UDEVD_EVENT=1
DEVNAME=/dev/usbdev4.2_ep81
[root@huberkahn 6282]#
Greg
Kay Sievers wrote:
> On 5/10/07, Greg Huber <ghuber@vanteon.com> wrote:
>> I hope this is the correct place for this...
>>
>> I am currently developing a driver for a USB dongle.
>> My development system is based on FC6, fully up-to-date.
>>
>> Everything seems to work fine until I unload the driver
>> (actual device still plugged in). I end up with a
>> "/lib/udev/udev_run_devd" process running rouge and
>> consuming mass amounts of CPU time. After tracing udev
>> events I'm speculating that there is a problem when the
>> system re-adds the device end-points back into the system.
>> (trace below)
>>
>> The 51-hotplug.rules handles (by ignoring) SUBSYSTEM
>> types of 'module' and 'drivers' but not 'usb_endpoint'.
>> I'm guessing that when the rules in the hotplug container
>> get checked, the event with SUBSYSTEM=usb_endpoint
>> causes udev_run_devd to execute but there is something
>> missing or incorrectly configured causing it to loop infintely.
>
> It sounds strange, no idea why the readdir() loop does not exit.
>
> Could you please check which event it is by looking at:
> /proc/$(pidof udev_run_devd)/environ
>
> Thanks,
> Kay
--
Greg Huber
Principal Engineer
Vanteon Corporation
255 Woodcliff Drive, Suite 200
Fairport, NY 14450
Office: (585) 419-9564
Fax: (585) 248-0537
www.vanteon.com <http://www.vanteon.com> - Embedded for Your Future
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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:[~2007-05-11 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:03 USB driver and udev_run_devd Greg Huber
2007-05-10 20:45 ` Kay Sievers
2007-05-11 12:59 ` Greg Huber [this message]
2007-05-11 14:53 ` Kay Sievers
2007-05-11 15:30 ` Greg Huber
2007-05-11 19:55 ` Kay Sievers
2007-05-11 20:42 ` Greg Huber
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=464468AE.3050400@vanteon.com \
--to=ghuber@vanteon.com \
--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.