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  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:	Sun, 17 Jun 2007 13:04:45 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Soeren Sonnenburg <kernel@....de>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Stefan Seyfried <seife@...e.de>,
	Christoph Lameter <clameter@....com>
Subject: Re: git-current: slub breaks s2ram with fglrx...

On Sunday, 17 June 2007 11:49, Soeren Sonnenburg wrote:
> 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 ?

I have no idea.

I guess we should let Christoph know about it (CC added), but I'm afraid
we won't be able to figure out what's wrong without access to the driver's
source code ...

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth
-
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