From: "Antonino A. Daplas" <adaplas@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Chua <jeff.chua.linux@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.23-rc2
Date: Sun, 05 Aug 2007 05:02:13 +0800 [thread overview]
Message-ID: <1186261333.5079.4.camel@daplas> (raw)
In-Reply-To: <46B4C011.8090802@zytor.com>
On Sat, 2007-08-04 at 11:06 -0700, H. Peter Anvin wrote:
> Linus Torvalds wrote:
> >
> > On Sat, 4 Aug 2007, Jeff Chua wrote:
> >> On 8/4/07, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> >>>> After resume from s2ram or switching to console from X, my console is
> >>>> messed up on rc1 and rc2. Is there a fix for this?
> >>> This is on IBM X60. i915 chipset. No problem on 2.6.22. If this is a
> >>> known problem, than I don't need to bisect all over again.
> >> I managed to bisect down to this commit. Without this, console screen
> >> can resume without video mess.
> >
> > [ The commit being 4fd06960f120e02e9abc802a09f9511c400042a5: "Use the new
> > x86 setup code for i386" ]
> >
> > Very interesting.
> >
> > 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?
>
> Also, can you please describe "messed up" in more detail? We had one
> report of "screen messed up" already that did get fixed
> (CONFIG_FIRMWARE_EDID not working.)
I believe this is the case where VBE DDC reading is non-contributory.
>
> Are you using the VGA console or a framebuffer console?
>
> Also, please submit your .config and kernel command line.
The dmesg output, the X logs and the s2ram options will also be useful.
Tony
next prev parent reply other threads:[~2007-08-04 21:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 3:50 Linux 2.6.23-rc2 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=1186261333.5079.4.camel@daplas \
--to=adaplas@gmail.com \
--cc=hpa@zytor.com \
--cc=jeff.chua.linux@gmail.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