Hi Ritesh, Okay will do sorry.
I don't have any USB devices plugged in no, but you're right it does appear to be getting started through the udev rules and that's why so many instances are spawned. It also explains why it only tries to start the pm-utils module and no others (it's fed through as an argument from the udev rule). I'm not sure why so many udev events are spawned on boot. I assume it's just the hardware coming online: I don't know if that is normal or not. For now I've removed the udev rules from the system to see if that fixes my issue. I'll get back to you shortly with the results. Many thanks, Tom On Wed, 2015-04-08 at 13:51 +0530, Ritesh Raj Sarraf wrote: > On Wednesday 08 April 2015 01:41 PM, Tom Meumann wrote: > > Hi Ritesh, > > > > My modules aren't disabled. > > > > As I said, during boot they sometimes all start and execute fine but at > > other times fail to execute. They fail more often than they succeed. > > If it were due to me disabling the modules, they would never start > > successfully. > > > > I'll continue to investigate but would appreciate not being brushed off > > as having mis-configured LMT. Have you attempted to reproduce the bug > > at all? > Tom, > Please keep the bug report in CC. > > I think I know what the problem might be. > > Do you have USB devices plugged in ? Like a USB Disk, or anything of > that sort ? > > What's happening is that multiple invocations of LMT are triggered. In a > span of 10 secs, LMT will only honor 2 invocations. So my guess is you > may be having a USB device, which is invoking LMT way too frequently, > thus acquiring the lock. > > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
