On Tue, 28 Aug 2007, Adrian McMenamin wrote: > works fine for a minute or two with events/0 reporting, via top, CPU > usage of about 0.3%. Then, without warning, events/0 whacks up to 99% > and the system gets locked The first and easiest way of detecting what's going on might be sticking a few printk()s into your code which is being scheduled in workqueue, to make sure that it's not your code that triggers inifinite loop somewhere. -- Jiri Kosina -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
