linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 17 Jun 2007 17:25:05 +0200
From:	Soeren Sonnenburg <kernel@....de>
To:	"Rafael J\. Wysocki" <rjw@...k.pl>
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 Sun, 2007-06-17 at 13:04 +0200, Rafael J. Wysocki wrote:
> On Sunday, 17 June 2007 11:49, Soeren Sonnenburg wrote:
> > OK,
[...]
> > 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 ...

I have one question: What if I don't load fglrx.ko but still use the
proprietary binary driver for xorg. Shouldn't s2ram work with that ? And
if not is this considered a kernel bug or still a ati-binary driver
bug ?

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/