mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "Soeren Sonnenburg" <kernel@nn7.de>
Cc: "Pavel Machek" <pavel@ucw.cz>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: suspend issue
Date: Wed, 9 Apr 2008 15:06:09 +0000	[thread overview]
Message-ID: <dd18b0c30804090806w6a162ca6j196d3db320d17f31@mail.gmail.com> (raw)
In-Reply-To: <1207736730.4320.1.camel@localhost>

First how do I not top message?,
For the situation with suspend I was able to succeed when fglrx was
loaded(not sure about radeonhd)
In what I experienced over here: when not loading fglrx would cause my
system to recover from suspend with a blank screen then a reboot a few
seconds later. Now two days ago I upgraded Xorg to 7.3 then doing the
same test leaves me with a different result;
With having fglrx not loaded the system will recover from suspend, but
with a blank screen and no reboot a few seconds later.
I have not upgraded the opengl drivers yet. From what I can see over
here the kernel is probably O.K. This looks more like a module issue
opengl, fglrx, radeonhd etc...of the three fglrx is recovering(I
havent tried radeonhd) I will look into upgrading my opengl stuff
today  and test to see if they recover from a suspend.
regards;
               Justin P. Mattock

On Wed, Apr 9, 2008 at 10:25 AM, Soeren Sonnenburg <kernel@nn7.de> wrote:
> On Mon, 2008-04-07 at 01:28 +0200, Pavel Machek wrote:
>  > On Sun 2008-04-06 13:55:04, Soeren Sonnenburg wrote:
>  > > On Sun, 2008-04-06 at 04:03 +0000, Justin Mattock wrote:
>  > > > Hello; I seem to have discovered something with echo mem > /sys/power/state.
>  > > > I recompile the kernel and had forgotten to compile fglrx, when
>  > > > performing a suspend without fglrx I was confronted with the dreaded
>  > > > blank screen and a reboot. then as a test I compiled fglrx and loaded,
>  > > > and to my amazement suspend reacted properly again.
>  > >
>  > > Yeah, but I it does not even work without X - console only!
>  > >
>  > > s2ram -f -p used to work since at least 2.6.20 ... and is now not
>  > > anymore in 2.6.25-*
>  >
>  > Can you do git bisect?
>
>  I just tried, and the problem is that 25-rc1 already fails to suspend -
>  so I am not sure how I could get more insight into this failure *on
>  resume*... any ideas?
>
>  Argh!
>  Soeren
>



-- 
Justin P. Mattock

  reply	other threads:[~2008-04-09 15:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06  4:03 Justin Mattock
2008-04-06 13:55 ` Soeren Sonnenburg
2008-04-06 15:48   ` Justin Mattock
2008-04-06 20:31     ` Rafael J. Wysocki
2008-04-07 10:35     ` Rafael J. Wysocki
2008-04-06 23:28   ` Pavel Machek
2008-04-07  0:08     ` Justin Mattock
2008-04-07  8:41       ` R. J. Wysocki
2008-04-07 16:41         ` Justin Mattock
2008-04-09 10:25     ` Soeren Sonnenburg
2008-04-09 15:06       ` Justin Mattock [this message]
2008-04-10 10:02       ` Pavel Machek
2008-04-10 16:04         ` Justin Mattock
2008-04-10 22:05         ` Soeren Sonnenburg
2008-04-11  5:18           ` Justin Mattock
2008-04-11  5:32             ` Soeren Sonnenburg
2008-04-11  6:12               ` Justin Mattock
2008-04-11 10:57           ` Pavel Machek
2008-04-11 12:11             ` Soeren Sonnenburg

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=dd18b0c30804090806w6a162ca6j196d3db320d17f31@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®