Marco d'Itri wrote on Wed, Mar 03, 2010 at 04:59:31PM +0100: > On Mar 03, Martin Cracauer <[email protected]> wrote: > > > Again, this worked fine until the udev update in this Debian installation. > This still does not mean that udev is doing anything wrong. > > > VMware isn't involved at this point at all, it never gets to see the > > device after the udev change. It happens just fine with VMware not > > running at all. > The kernel log you pasted showed that vmware was involved.
I tried several times, some of which had vmware running, others didn't. The log was from after the last attempt, presumably I had vmware back up at that point. > > Just connecting the device to a Debian with this udev version (but not > > previous versions) with no proprietary software running causes the > > lockup. > This is very different from what you explained in your original report. No it's not. I said in the original report that the device is grabbed by the kernel respectively udev before vmware can even see it. That vmware somehow choked was your reading only. VMware never even gets notified of the new USB device. Can we move this to a more constructive base and you give me something to try to debug this further? I honestly thought this is a matter of just disabling something in the current udev configuration and the device is left alone. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer <[email protected]> http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
