On Mon, Jan 08, 2007 at 00:44:45 +0100, Adrian Bunk wrote: > On Sun, Jan 07, 2007 at 11:27:06PM +0100, 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. > > Is this issue still present in -rc4?
I used 2.6.20-rc4 in single user mode, and applied 2 patches from netdev to get wake on LAN support. This way I was able to set up an automatic suspend/resume loop. It looked good, but after e.g. 20 minutes, the resume hang. So it is reproduceable with 2.6.20-rc4. Unfortunately, I can not test the same with 2.6.18, as the wake on LAN patches need 2.6.20-rc. 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/
