linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Jellinghaus <aj@leogic.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev or kernel broken with rsdl 0.30 patch
Date: Fri, 16 Mar 2007 11:45:03 +0000	[thread overview]
Message-ID: <200703161245.04120.aj@leogic.com> (raw)
In-Reply-To: <20070315104654.19025CA4097@mx1.ciphirelabs.net>

Am Freitag, 16. März 2007 12:34 schrieb Kay Sievers:
> > and debugging shows udev gets the event, but does not emit it,
>
> What shows that?
>
> > i.e. doesn't run my script. in one case it runs my script,
> > in the other case it does not. why?
>
> In both cases in your log, there are no events for the usb-device
> itself: /devices/pci0000:00/0000:00:1d.1/usb2/2-1
> Maybe you missed to copy a few lines?

ok, here are again the criticial lines from syslog messages: with 2.6.20.2:
Mar 15 11:19:06 localhost udevd[2622]: udev_event_run: seq 2869 forked, pid 
[6065], 'add' 'usb', 0 seconds old
Mar 15 11:19:06 localhost udevd-event[6065]: wait_for_sysfs: 
file '/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0/bus' 
appeared after 0 loops
Mar 15 11:19:06 localhost udevd-event[6065]: 
run_program: '/lib/udev/openct_usb'
Mar 15 11:19:07 localhost udevd-event[6065]: 
run_program: '/lib/udev/openct_usb' returned with status 0
Mar 15 11:19:07 localhost udevd-event[6065]: pass_env_to_socket: passed 338 
bytes to socket '/org/freedesktop/hal/udev_event', 
Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/sbin/modprobe -Q 
usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00'
Mar 15 11:19:07 localhost udevd-event[6065]: run_program: '/sbin/modprobe' 
returned with status 1
Mar 15 11:19:07 localhost udevd-event[6065]: pass_env_to_socket: passed -1 
bytes to socket '/org/kernel/udev/monitor', 
Mar 15 11:19:07 localhost udevd-event[6065]: udev_event_run: seq 2869 finished
Mar 15 11:19:07 localhost udevd[2622]: udev_done: seq 2869, pid [6065] exit 
with 1, 1 seconds old

and if I add rsdl:
Mar 15 11:24:32 localhost udevd[2607]: udev_event_run: seq 2717 forked, pid 
[5284], 'add' 'usb', 0 seconds old
Mar 15 11:24:32 localhost udevd-event[5284]: wait_for_sysfs: 
file '/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1.5/2-1.5:1.0/bus' 
appeared after 0 loops
Mar 15 11:24:32 localhost udevd-event[5284]: pass_env_to_socket: passed 338 
bytes to socket '/org/freedesktop/hal/udev_event', 
Mar 15 11:24:32 localhost udevd-event[5284]: run_program: '/sbin/modprobe -Q 
usb:v08E6p3438d0100dc00dsc00dp00ic0Bisc00ip00'
Mar 15 11:24:32 localhost udevd-event[5284]: run_program: '/sbin/modprobe' 
returned with status 1
Mar 15 11:24:32 localhost udevd-event[5284]: pass_env_to_socket: passed -1 
bytes to socket '/org/kernel/udev/monitor', 
Mar 15 11:24:32 localhost udevd-event[5284]: udev_event_run: seq 2717 finished
Mar 15 11:24:32 localhost udevd[2607]: udev_done: seq 2717, pid [5284] exit 
with 1, 0 seconds old

same  hardware, same config, same kernel (except for rsdl patch), and suddenly
it does not spawn openct. why? how can I debug this? if I strace, it works 
fine again, so that didn't help.

> Oh, can you please talk about kernel versions, and not distro nicknames?
> I have no clue what they mean.

ok, sorry. lets skip the question why I don't get events for /dev any more.

> Right, that never worked. The usb-interfaces are childs of the
> usb-device in /sys/devices. The usb_device class-devices (the ones with
> the /dev/bus node) are also just childs of the usb-device and therefore
> can't access the (sibling) interface devices.
>
> With the current usb driver core, you can't match the /dev device-node
> to interfaces, only to the device.
>
> There is a patch pending (now that the new driver core allows us to do
> that), that moves the device-node directly to the /sys/devices
> usb-device, which should solve all the issues in the future.

ok. so until that patch is in the kernel (or udev? or both?), /dev/bus/usb
will not work for udev users as /proc/bus/usb replacement, since the
rules to match the attributes of the usb device won't work. right?

is there some page documenting the compatiblity issues with udev
and the kernel? this might be interesting for other people as well.

Thanks for your help.

Regards, Andreas

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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

  parent reply	other threads:[~2007-03-16 11:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 10:46 udev or kernel broken with rsdl 0.30 patch [u] Andreas Jellinghaus [c]
2007-03-15 15:22 ` Kay Sievers
2007-03-15 17:03 ` udev or kernel broken with rsdl 0.30 patch Andreas Jellinghaus
2007-03-15 19:57 ` Kay Sievers
2007-03-16 10:06 ` Andreas Jellinghaus
2007-03-16 10:35 ` Kay Sievers
2007-03-16 10:59 ` Andreas Jellinghaus
2007-03-16 11:34 ` Kay Sievers
2007-03-16 11:45 ` Andreas Jellinghaus [this message]
2007-03-16 12:08 ` Kay Sievers
2007-03-16 12:32 ` Andreas Jellinghaus
2007-03-16 12:48 ` Kay Sievers
2007-03-16 13:35 ` Andreas Jellinghaus
2007-03-16 13:38 ` Andreas Jellinghaus
2007-03-16 13:58 ` Kay Sievers
2007-03-16 14:39 ` Andreas Jellinghaus
2007-03-16 14:59 ` Kay Sievers
2007-03-16 15:20 ` Andreas Jellinghaus
2007-03-16 15:39 ` 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=200703161245.04120.aj@leogic.com \
    --to=aj@leogic.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 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).