lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 09 Nov 2009 15:44:56 +0100
From:	Mike Galbraith <>
To:	"Rafael J. Wysocki" <>
Cc:	Thomas Gleixner <>, Ingo Molnar <>,
	LKML <>,
	pm list <>,
	Greg KH <>,
	Linus Torvalds <>,
	Jesse Barnes <>
Subject: Re: Help needed: Resume problems in 2.6.32-rc, perhaps related to
 preempt_count leakage in keventd

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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists