On Mon, Jan 13, 2014 at 01:59:39PM -0800, Greg KH wrote: > That really sounds like a driver problem, especially given your trace > shows it is failing somewhere. The udevd PID is probably because udev > loaded your driver.
Sorry, not loading it, but rather reading sysfs files that your driver is creating. As your driver isn't a closed source one, have a pointer to the source anywhere that we can see what you are doing in your sysfs callbacks? thanks, greg k-h _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
