> > Upon resuming, I > > checked dmesg and found the time seems to be totally out of whack: > > So sched_clock() went bad. That's another tree or three we can't merge. Right now sched_clock doesn't have a call back to resync for suspend/resume. I will add one. -Andi - 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/
- References:
- 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- software suspend failed (1 tasks refusing to freeze)
- From: "Miles Lane" <[email protected]>
- Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- software suspend failed (1 tasks refusing to freeze)
- From: "Miles Lane" <[email protected]>
- Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- software suspend failed (1 tasks refusing to freeze)
- From: Andrew Morton <[email protected]>
- 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- software suspend failed (1 tasks refusing to freeze)
- Prev by Date: Re: [PATCH] cfq: get rid of cfqq hash
- Next by Date: Re: [RFC][PATCH] syctl for selecting global zonelist[] order
- Previous by thread: Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- software suspend failed (1 tasks refusing to freeze)
- Next by thread: Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- software suspend failed (1 tasks refusing to freeze)
- Index(es):
 |