From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Jellinghaus Date: Fri, 16 Mar 2007 10:59:16 +0000 Subject: Re: udev or kernel broken with rsdl 0.30 patch Message-Id: <200703161159.16367.aj@leogic.com> List-Id: References: <20070315104654.19025CA4097@mx1.ciphirelabs.net> In-Reply-To: <20070315104654.19025CA4097@mx1.ciphirelabs.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Am Freitag, 16. M=C3=A4rz 2007 11:35 schrieb Kay Sievers: > On Fri, 2007-03-16 at 11:06 +0100, Andreas Jellinghaus wrote: > > Am Donnerstag, 15. M=C3=A4rz 2007 20:57 schrieb Kay Sievers: > > > > why are the endpointes removed and added in the working case? > > > > the device is unchanged. > > > > > > Don't know what's with the endpoints, but what device event do you > > > miss? It looks like it's all there in the udevmonitor output, right? > > > > it was not a missing event. > > Well, you wrote: "why udev/kernel emit less events?" :) and debugging shows udev gets the event, but does not emit it, i.e. doesn't run my script. in one case it runs my script, in the other case it does not. why? > You mean, that the /proc file is not there, does udev look for the /proc file? I don't get a chance to do so - my script is not even run, as udev indicates. the udev config lines are the same: refering to BUS and some SYSFS stuff, but not to /proc, so why do you think it has to do with /proc? also my script would work fine with both $DEVICE - traditional /proc stuff - and $DEVNAME - was used when introducing /dev/bus/usb stuff. but I don't get to that point, the script isn't run at all (I checked with a echo in the first line of the script and with udevd in debug logging mode where it logs each time it runs something). > Or don't use it at all, and hook into the "usb_device" event and use the > files in /dev with the same layout, instead of the crappy usbfs files. earlier I got those events, but these days I don't get called for them. any idea why? (ubuntu edgy, config as posted). guess I got them with dapper - and had to implement proper interface claiming to prevent two processes talking to the same hardware through different devices. how can I debug why udev doesn't run openct on the /dev/bus/usb device? I can see in udev log that it creates the device: Mar 15 11:19:07 localhost udevd[2622]: udev_event_run: seq 2873 forked, pid= =20 [6094], 'add' 'usb_device', 1 seconds old Mar 15 11:19:07 localhost udevd-event[6094]:=20 run_program: 'usb_device_name --export usbdev2.16' Mar 15 11:19:07 localhost udevd-event[6094]:=20 run_program: '/lib/udev/usb_device_name' (stdout) 'USB_BUS=002' Mar 15 11:19:07 localhost udevd-event[6094]:=20 run_program: '/lib/udev/usb_device_name' (stdout) 'USB_DEV=016' Mar 15 11:19:07 localhost udevd-event[6094]:=20 run_program: '/lib/udev/usb_device_name' returned with status 0 Mar 15 11:19:07 localhost udevd-event[6094]: udev_rules_get_name: rule=20 applied, 'usbdev2.16' becomes 'bus/usb/002/016' Mar 15 11:19:07 localhost udevd-event[6094]: udev_db_get_device: no db file= to=20 read /dev/.udev/db/class@usb_device@usbdev2.16: No such file or directory Mar 15 11:19:07 localhost udevd-event[6094]: udev_node_add: creating device= =20 node '/dev/bus/usb/002/016', major =3D '189', minor =3D '143', mode =3D '06= 64', uid=20 =3D '0', gid =3D '0' Mar 15 11:19:07 localhost udevd-event[6094]: pass_env_to_socket: passed 305= =20 bytes to socket '/org/freedesktop/hal/udev_event',=20 Mar 15 11:19:07 localhost udevd-event[6094]: pass_env_to_socket: passed -1 = bytes to socket '/org/kernel/udev/monitor',=20 Mar 15 11:19:07 localhost udevd-event[6094]: udev_event_run: seq 2873 finis= hed Mar 15 11:19:07 localhost udevd[2622]: udev_done: seq 2873, pid [6094] exit= =20 with 0, 1 seconds old see, the device is created and udev is run. but my openct rule: BUS!=3D"usb", ACTION!=3D"add", GOTO=3D"openct_usb_rules_end" SYSFS{bInterfaceClass}=3D"0b", SYSFS{bInterfaceSubClass}=3D"00",=20 SYSFS{bInterfaceProtocol}=3D"00" RUN+=3D"/lib/udev/openct_usb" is not run. why? or does udev create these new /dev/bus/usb devices are /proc/bus/usb=20 replacement, but does not allow to match simple usb config values like interface class on them? that would be a huge step back, so I hope it isn't the case. 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=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ 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