On Mon, Jan 08, 2007 at 17:17:19 +0100, Pavel Machek wrote: > On Sun 2007-01-07 23:27:06, Tino Keitel wrote: > > On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote: > > > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote: > > > > On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote: > > > > > No information about the device/driver that refuses to resume. > > > > > > > > You should be able to identify the problematic driver by removing each > > > > driver manually before suspending. > > > > > > I can not reproduce it anymore, resume now works. I really hope that it > > > will stay so. > > > > It didn't. It looks like it is unusable, becuase it isn't reliable in > > 2.6.20-rc3. > > What was last working version? Can you pinpoint driver breaking it?
I just used 2.6.18.2 with a manual driven suspend/resume loop and fully loaded userspace for ca. 40 minutes, without a failure. I tried to pinpoint the driver with pm_trace, without success (see my original posting). Regards, Tino - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
