linux-kernel - Re: [BUG] at drivers/char/vt.c:3332 do_blank

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070215104032.GL26240@elf.ucw.cz>
Date:	Thu, 15 Feb 2007 11:40:32 +0100
From:	Pavel Machek <pavel@....cz>
To:	S.Ça??lar Onur <caglar@...dus.org.tr>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] at drivers/char/vt.c:3332 do_blank_screen() on resume

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/