http://bugzilla.novell.com/show_bug.cgi?id=604966 http://bugzilla.novell.com/show_bug.cgi?id=604966#c21 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kasievers@novell.com | --- Comment #21 from Kay Sievers <kasievers@novell.com> 2010-06-02 11:24:34 UTC --- Udev reports the raw status bytes, and 0x0b is a segfault. The binary seems broken, when it segfaults. And it event tries to fiddle around with signal handlers to catch a segfault. I have really no idea what this thing tries to do here. :) Right, PROGRAM= should only be used if symlinks need to be named. Otherwise RUN+= should be used, because it runs after all event/device naming processing is done. But note, that you want +=, or you reset all possibly added earlier RUN keys. (It might not make a difference here, now that we have devtmpfs in 11.3, and the kernel has already created the node for us -- this wasn't the case before devtmpfs, and the device was never accessible with PROGRAM=) ATTRS{} should always have a corresponding match on the subsystem the attribute is coming from, like SUBSYSTEMS="serio", otherwise we will unefficiently check all parents in the whole sysfs path for this attribute. (This is more about efficiency, and should not make any other difference.) For ACTION= we usually use !="remove", because stuff should run on any possible event. (That's more a cosmetic thing.) And can we please check DMI data or anything else that tells us that we run in vmware? Or is that useful for other things too? It's usually bad behavior to unconditionally fork binaries to probe something, which is not needed on any common system. It's like we would just load all kernel modules from /lib/modules just to check if they can find a device to drive. :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.