From: Pavel Machek <pavel@suse.cz>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
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: Sun, 27 Feb 2005 17:59:48 +0100 [thread overview]
Message-ID: <20050227165948.GF1441@elf.ucw.cz> (raw)
In-Reply-To: <421A6B42.2070108@superbug.demon.co.uk>
Hi!
> >Well, dumping random stuff to console can produce funny results. I'd
> >call that normal. Try cat /dev/urandom, that should be "enough
> >random".
>
> 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.
I have seen something similar on S3 cards with bad video ram (we had
>3 of them). If it survives soft reboot... well, that looks like
hardware problem to me. [We may do something bad in linux, too, but
strange effects should not survive reboot, that's hw bug. I'd suggest
memtest on video ram, but someone would need to write that tool, first].
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-02-27 17:00 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
2005-02-21 23:14 ` James Courtier-Dutton
2005-02-27 16:59 ` Pavel Machek [this message]
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=20050227165948.GF1441@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=James@superbug.demon.co.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@berlios.de \
/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