On Monday 09 November 2009, Mike Galbraith wrote: > On Mon, 2009-11-09 at 15:26 +0100, Rafael J. Wysocki wrote: > > > Well, I can add the printk(), but I can't guarantee that I will get the call > > trace once again. So far I've seen it only once after 20-25 consecutive > > suspend-resume cycles, so ... you get the idea. > > > > However, running on a wrong CPU would very nicely explain all of the observed > > symptoms, so I guess we can try a House M.D.-alike approach and assume that the > > answer is "yes, we're running on the wrong CPU". What would we do next if that > > was the case? > > If you're interested in trying a patch, I have a couple that fix things > up here. My "get a bigger hammer" patch would be best if it's what I > think it is. If it only fails once in a blue moon though, maybe not > worth even trying. If I could suspend/resume, I'd try it myself, but I > have (steenking) nvidia card. No eyecandy or resume for me, though I > can suspend... once. OK, please send me (a) poiter(s) to the patches. I'll first try the patch you've just sent and report back. Thanks, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
