public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: video resume stuff
Date: Fri, 05 Oct 2007 11:34:00 -0700	[thread overview]
Message-ID: <47068398.9070304@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710051648440.25413@twin.jikos.cz>

Jiri Kosina wrote:
> On Fri, 5 Oct 2007, Pavel Machek wrote:
> 
>>> I suggest we tackle this *after* the x86 merge.
>> Well, we still have the regression on jikos' strange system, and I would 
>> like to understand what is going on there.
> 
> Sorry for this taking too long. Finally I had the time to play with this 
> again, so here goes the current summary. I have a system here, that:
> 
> - with 1d67953f2bda8876045c24ae58841f27d9bb7572 (just before the setup 
>   code rewrite), resumes nicely in VGA console 
>   (acpi_sleep=s3_bios,s3_mode kernel parameter is needed), everything 
>   works
> 
> - with c39736823232bc3ca113c8228fa852c09fba300e (just after the setup code 
>   rewrite), VGA text console is garbled after resume - looks like the 
>   video RAM contains some strange data (patterns from BIOS post can be 
>   recognized, there are some various-colored stripes across the screen, 
>   etc). The machine also seems to be frozen (no keyboard LEDs working, 
>   etc).
> 
> - with 2.6.23-rc9, the video doesn't come up at all, I can't even see the 
>   garbled picture any more - the display stays blank, the LED diod is 
>   yellow (i.e. looks like completely no signal from VGA card). On the 
>   other hand, the machine seems to work otherwise
> 

Jiri, what particular video mode are you running in?  In other words, 
what is your vga= parameter set to?  In fact, what does your entire 
kernel command line look like?

Also, if you could extract the information requested in:

http://marc.info/?i=46FD802D.2030804@zytor.com

... that would really help.

	-hpa

(who notices we really need to export boot_params to userspace for sanity)

  reply	other threads:[~2007-10-05 18:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 13:05 video resume stuff Pavel Machek
2007-10-04 13:28 ` Arjan van de Ven
2007-10-04 14:24   ` Pavel Machek
2007-10-04 16:29     ` H. Peter Anvin
2007-10-04 16:15 ` H. Peter Anvin
2007-10-05  7:32   ` Pavel Machek
2007-10-05 14:59     ` Jiri Kosina
2007-10-05 18:34       ` H. Peter Anvin [this message]
2007-10-05 21:06         ` Jiri Kosina
2007-10-05 21:29           ` H. Peter Anvin
2007-10-05 21:42           ` H. Peter Anvin
2007-10-08  8:26             ` Jiri Kosina
2007-10-05 15:14     ` H. Peter Anvin

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=47068398.9070304@zytor.com \
    --to=hpa@zytor.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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