[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200911091647.03502.rjw@sisk.pl>
Date: Mon, 9 Nov 2009 16:47:03 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Mike Galbraith <efault@....de>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
pm list <linux-pm@...ts.linux-foundation.org>,
Greg KH <gregkh@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: Help needed: Resume problems in 2.6.32-rc, perhaps related to preempt_count leakage in keventd
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists