From: Pavel Machek <pavel@ucw.cz>
To: "S.Ça??lar Onur" <caglar@pardus.org.tr>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] at drivers/char/vt.c:3332 do_blank_screen() on resume
Date: Thu, 15 Feb 2007 11:40:32 +0100 [thread overview]
Message-ID: <20070215104032.GL26240@elf.ucw.cz> (raw)
In-Reply-To: <200702090838.21060.caglar@pardus.org.tr>
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).
>
> [1] http://cekirdek.pardus.org.tr/~caglar/dmesg.2.6.20
Contact fbcon people... They are calling do_blank_screen+0x4e/0x218
from fbcon_event_notify+0x8f1/0xa1e ... probably without taking
neccessary locks.
Aha, it seems their blanking code triggers _while_ resuming, which is
not exactly nice.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-02-15 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 6:38 [BUG] at drivers/char/vt.c:3332 do_blank_screen() on resume S.Çağlar Onur
2007-02-15 10:40 ` Pavel Machek [this message]
2007-02-15 10:56 ` Andrew Morton
2007-02-15 11:00 ` S.Çağlar Onur
2007-02-21 23:43 ` Antonino A. Daplas
2007-02-22 12:53 ` S.Çağlar Onur
2007-02-22 13:41 ` Antonino A. Daplas
2007-02-22 13:52 ` S.Çağlar Onur
2007-02-28 12:10 ` S.Çağlar Onur
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 10:58 S.Çağlar Onur
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=20070215104032.GL26240@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.