From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: [BUG] at drivers/char/vt.c:3332 do_blank_screen() on resume
Date: Thu, 15 Feb 2007 12:58:45 +0200 [thread overview]
Message-ID: <200702151258.45648.caglar@pardus.org.tr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]
Hi;
With 2.6.20, resuming from disk sometimes cannot returns on vt7 where X runs
but everything seems working, so just changing to vt1 and returning to vt7
solves the problem. But dmesg shows some BUG() output like [1] whenever this
problem occurs
I'm using 20070207 snapshot of suspend, s2disk is used to suspend2disk,
machine is a Sony Vaio FS-215B which is in the whitelist and works well with
2.6.16/17/18 (all have fbsplash and vesafb-tng patches [from gentoo]
applied).
According to Pavel Machek, this is the true list to report the problem and his
explanations about problem can be found at [2].
[1] http://cekirdek.pardus.org.tr/~caglar/dmesg.2.6.20
[2] http://lkml.org/lkml/2007/2/15/91
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 182 bytes --]
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
reply other threads:[~2007-02-15 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200702151258.45648.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).