public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	"Rafael J\. Wysocki" <rjw@sisk.pl>,
	Stefan Seyfried <seife@suse.de>
Subject: git-current: slub breaks s2ram with fglrx...
Date: Sun, 17 Jun 2007 11:49:46 +0200	[thread overview]
Message-ID: <1182073786.3841.11.camel@localhost> (raw)

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.

             reply	other threads:[~2007-06-17 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17  9:49 Soeren Sonnenburg [this message]
2007-06-17 11:04 ` git-current: slub breaks s2ram with fglrx Rafael J. Wysocki
2007-06-17 15:25   ` Soeren Sonnenburg
2007-06-17 15:33     ` Michal Piotrowski
2007-06-17 15:47       ` Soeren Sonnenburg
2007-06-18  2:05         ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1182073786.3841.11.camel@localhost \
    --to=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=seife@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox