From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Linux 2.6.23-rc2
Date: Sun, 5 Aug 2007 10:29:14 +0800 [thread overview]
Message-ID: <b6a2187b0708041929x6afd8787t368d3f9f27b709c1@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708040900170.5037@woody.linux-foundation.org>
On 8/5/07, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> Jeff - do I understand correctly that the "or" means that even *without* a
> suspend-to-ram sequence, and just by going into X and then going back to
> text-mode, the screen is corrupt?
I've done more tests. It seems that "suspend-to-ram" sequence is the
culprit. After resume, the text console is messed up. Not switching
X/console.
Boot up. Console -> X ok -> Console ok -> s2ram -> console bad -> X ok
-> console bad -> X ok.
> I just want to make sure that there is no suspend-related activity
> required for this at all, and the only common issue is probably just that
> suspend ends up *also* triggering the X mode-setting at resume..
It's suspend as indicated above.
> (Side note: if you have a modern distro, you might try to change the line
> that says
> Driver "i810"
> in the /etc/X11/xorg.conf to say
> Driver "intel"
I'll test this and get back.
Thanks,
Jeff.
next prev parent reply other threads:[~2007-08-05 2:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 3:50 Linus Torvalds
2007-08-04 4:14 ` david
2007-08-04 5:13 ` Jeff Chua
2007-08-04 5:34 ` Jeff Chua
2007-08-04 13:52 ` Jeff Chua
2007-08-04 16:11 ` Linus Torvalds
2007-08-04 18:06 ` H. Peter Anvin
2007-08-04 21:02 ` Antonino A. Daplas
2007-08-05 2:37 ` Jeff Chua
2007-08-05 3:11 ` H. Peter Anvin
2007-08-05 11:52 ` Jeff Chua
2007-08-07 17:05 ` David Weinehall
2007-08-08 2:46 ` Jeff Chua
2007-08-05 2:29 ` Jeff Chua [this message]
2007-08-05 12:04 ` Jeff Chua
2007-08-04 10:30 ` Rafael J. Wysocki
2007-08-04 22:15 ` Rafael J. Wysocki
2007-08-05 3:22 ` "Badness at kernel/irq/resend.c:70" on boot - via-pmu? Paul Collins
2007-08-05 4:41 ` Linus Torvalds
2007-08-05 21:51 ` Benjamin Herrenschmidt
2007-08-05 12:11 Linux 2.6.23-rc2 Jeff Chua
2007-08-05 12:40 ` Antonino A. Daplas
2007-08-05 13:26 ` Jeff Chua
2007-08-05 16:47 ` Rafael J. Wysocki
2007-08-06 0:36 ` Jeff Chua
2007-08-06 11:26 ` Rafael J. Wysocki
2007-08-06 12:34 ` Jeff Chua
2007-08-06 16:40 ` H. Peter Anvin
2007-08-06 15:40 ` Jan Engelhardt
2007-08-06 16:06 ` Jeff Chua
2007-08-06 16:34 ` Jan Engelhardt
2007-08-06 16:46 ` Indan Zupancic
2007-08-06 17:16 ` H. Peter Anvin
2007-08-06 17:32 ` Indan Zupancic
2007-08-06 17:33 ` H. Peter Anvin
2007-08-06 22:53 ` Jeff Chua
2007-08-06 22:54 ` H. Peter Anvin
2007-08-06 22:57 ` Jeff Chua
2007-08-06 23:00 ` H. Peter Anvin
2007-08-06 22:48 ` Jeff Chua
2007-08-06 23:20 Jeff Chua
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=b6a2187b0708041929x6afd8787t368d3f9f27b709c1@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®