All of lore.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: "Rafael J\. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Stefan Seyfried <seife@suse.de>,
	Christoph Lameter <clameter@sgi.com>
Subject: Re: git-current: slub breaks s2ram with fglrx...
Date: Sun, 17 Jun 2007 17:25:05 +0200	[thread overview]
Message-ID: <1182093905.3841.23.camel@localhost> (raw)
In-Reply-To: <200706171304.46181.rjw@sisk.pl>

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.

  reply	other threads:[~2007-06-17 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17  9:49 git-current: slub breaks s2ram with fglrx Soeren Sonnenburg
2007-06-17 11:04 ` Rafael J. Wysocki
2007-06-17 15:25   ` Soeren Sonnenburg [this message]
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=1182093905.3841.23.camel@localhost \
    --to=kernel@nn7.de \
    --cc=clameter@sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.