linux-kernel - git-current: slub breaks s2ram with fglrx...

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 17 Jun 2007 11:49:46 +0200
From:	Soeren Sonnenburg <kernel@....de>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
Cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	"Rafael J\. Wysocki" <rjw@...k.pl>, Stefan Seyfried <seife@...e.de>
Subject: git-current: slub breaks s2ram with fglrx...

OK,

I've found the second root for my 

'2.6.22-rc regression: s2ram fails to suspend + fails to resume w/ Xorg':

The first one was just the wrong coretemp patch (already fixed by Jean).

The second one happens only with Xorg/fglrx loaded and slub enabled, as
I've found after a useless git bisect session, I've traced down the
other s2ram does not work problem to be caused by slub ... FYI: I am now
on git-current which should be rc5:

slab & fglrx works
slub & console works
slub & X11+fglrx creates hangs on suspend (black screen - no further
idea ...)

It should be noted that withouth the proprietary  fglrx.ko module loaded
the machine just reboots on s2ram (though IIRC without fglrx.ko loaded
it worked with 2.6.19 or so...)

Is this a kernel thing or yet another bug in fglrx ?

Soeren 
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.
-
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/