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  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, 7 Feb 2011 21:38:04 +0800
From:	Jeff Chua <>
To:	Takashi Iwai <>
Cc:	Chris Wilson <>,
	Linus Torvalds <>,
	"Rafael J. Wysocki" <>, Len Brown <>,
	LKML <>
Subject: Re: Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_

On Mon, Feb 7, 2011 at 6:15 PM, Takashi Iwai <> wrote:
>> Thanks, that looks good.  What about other files?  Did you change
>> (especially intel_drv.h) from Linus git tree?

I will try again  from a fresh build tonight.

>> I'll also check later to be sure (now I have no machine for testing).
> I don't see any problem with my machine (but running in 32bit).
> Are you sure that you are seeing the same CRTC?  There are two active
> CRTCs on Intel, and both are initialized and set up.

I don't know about that. Even when I attempt to just the pointer
directly as in "static void intel_crtc_reset(struct intel_crtc
*intel_crtc)", it ended up getting a different value. Strange.

intel_crtc ffff880239aa5800
intel_crtc ffff880239aa5000

I'm building everything fresh now.

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