On Thu, 4 Feb 2010, Greg KH wrote: > On Thu, Feb 04, 2010 at 11:20:20AM -0500, Alan Stern wrote: > > Greg: > > > > Something in gregkh-all-2.6.33-rc6 is causing excess USB uevents to be > > issued. It happens when switching between VT consoles. Not every > > time... but it shouldn't happen at all. Here's an example from a > > recent bootup: I was wrong about this happening only when the gregkh-all patch is applied. It happens in vanilla 2.6.33-rc6 also; I missed it before because the kernel I tested didn't have CONFIG_USB_DEBUG enabled. > > ... > > [ 9.841567] usb usb6: uevent > > [ 9.844146] usb usb7: uevent > > can you run 'udevadm monitor' to see what these uevents are? Nothing shows up. Evidently these aren't real uevents. > I'm about to jump on a plane to go to FOSDEM, so will not really be able > to debug this for a few days :( It turns out that these messages come from the pr_debug() line near the start of usb_uevent(). What has changed is that now the function gets called a lot more often than it used to (for example, whenever a new user logs on to the console). This observation may be related to the fact that I recently upgraded to Fedora 12. The new calls are triggered by udev-acl, which apparently runs at these times and reads through all the /sys/bus/usb/devices/*/uevent files. Each file generates a debug message in the log. Is udev-acl supposed to do that? What's the purpose? Assuming everything is behaving as desired, can we remove that pr_debug() line? Is it still useful for anything? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
