public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>,
	mhf@berlios.de, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.11-rc[234] setfont fails on i810 after resume from ACPI-S3
Date: Mon, 21 Feb 2005 23:13:04 +0000	[thread overview]
Message-ID: <421A6B00.5060501@superbug.co.uk> (raw)
In-Reply-To: <20050215202212.GK7338@elf.ucw.cz>

Pavel Machek wrote:
> Hi!
> 
> 
>>Any thoughts on this one?  We should come back from resume in 30-row mode,
>>shouldn't we?
> 
> 
> Well, current state of video resume is "we are happy to see anything
> at all". 
> 
> 
>>HW info
>>
>>Using vga=0xf07, default8x16 font, display has 30 lines
>>
>>On powerup from S3 console has only 25 lines but still scrolls 
>>at 30 lines. Setfont historically fixes it. 
>>
>>Tested with 2.6.10, 2.6.11-rc1: OK
>>
>>Tested with 2.6.11-rc2-Vanilla and 2.6.11-rc[234]+swsusp2.
>>When using setfont, screen goes blank. Power up after S3
>>returns console in 25 lines mode with 30 lines scroll. 
>>Several attempts - same result.
> 
> 
> So... screen goes blank even when suspend is not involved, right?
> Sounds like a bug to me ;-).
> 
> 
>>Another bug I see only on this HW and only with 2.6 is that
>>when - and only when - using gentoo emerge --usepackage in
>>text console, scroll area resets to _25_ when portage 
>>"dumps" the (binary) package contents which scrolls pretty
>>fast. I was unable to reproduce this in any other way. 
>>Tried also echo loop in bash but perhaps it is too slow
>>or not random enough. Note that 2.4.2[789] no problem.
> 
> 
> Well, dumping random stuff to console can produce funny results. I'd
> call that normal. Try cat /dev/urandom, that should be "enough
> random".
> 
> 								Pavel

I am also getting strange effects. I boot into  2.6.11-rc4 and the 
console fonts looks fine. Come back a day later and the console font has 
  corrupt characters. E.g. Displays a "D" instead of an "L" and stuff 
like that. It is mostly readable, except for a few characters.
It is only the local console that is corrupted. ssh into the box 
displays correct characters, so all I can assume is that the VGA console 
is being programmed with different characters. The bad characters also 
survive a soft reboot( During BIOS boot up), until the linux kernel 
starts booting, and then it switches to a good font.

  reply	other threads:[~2005-02-21 23:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050215122233.22605728.akpm@osdl.org>
2005-02-15 20:22 ` [BUG] 2.6.11-rc[234] setfont fails on i810 after resume from ACPI-S3 Pavel Machek
2005-02-21 23:13   ` James Courtier-Dutton [this message]
2005-02-21 23:14   ` James Courtier-Dutton
2005-02-27 16:59     ` Pavel Machek
2005-02-28  9:59 mhf
  -- strict thread matches above, loose matches on Subject: below --
2005-02-15 11:41 mhf
2005-02-15 11:32 mhf

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=421A6B00.5060501@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@berlios.de \
    --cc=pavel@suse.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