long resume bugs in Lucid (thoughts?).

Manoj Iyer manoj.iyer at canonical.com
Wed Feb 10 01:25:08 UTC 2010


I did some data-mining on the bugs that report resume takes a long time, ie 
in the order of seconds. There are 150 such bugs which I believe spans 
karmic+lucid. The long resume bug#s and their resume time can be found on


The average of the long resume time is 18.141 seconds. The resume times 
that are reported is the total resume time. In my patch I am printing 
resume time per driver:device which is in the order of milli seconds in 
most cases, and I print as I resume, so I wont be able to know the total 
resume time until I fully resume. I don't think I found what I was looking 
for triaging these bugs, as a result. If you look at my sample output most 
devices resume in 0.001ms (on dell Mini10V), and resume took 3.880 seconds 


I estimate that I should print any device that takes more than 100.00 msec 
to resume. This will eliminate a lot of noise from dmesg.

thoughts ?

--- manjo

More information about the kernel-team mailing list