From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Przemysław Pawełczyk" <przemyslaw@pawelczyk.it>
Cc: Alan Cox <alan@linux.intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: consolechars switches tty since 8b92e87 vt: add an event interface
Date: Sun, 15 Nov 2009 20:18:55 +0000 [thread overview]
Message-ID: <20091115201855.2e046427@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <40e92d5b0911151121l68ef89e5s315b6c2b017bfaad@mail.gmail.com>
> ioctl(3, VIDIOC_G_COMP or VT_ACTIVATE, 0x2) = 0
Switch to VT 2
> ioctl(3, VIDIOC_S_COMP or VT_WAITACTIVE, 0x2) = 0
Wait for VT 2 to activate
> ioctl(3, PIO_UNIMAPCLR, 0x7fff042a0160) = 0
> ioctl(3, PIO_UNIMAP, 0x7fff042a0730) = 0
Set maps
> ioctl(3, VIDIOC_G_COMP or VT_ACTIVATE, 0x1) = 0
Switch back to VT 1
> ioctl(3, VIDIOC_S_COMP or VT_WAITACTIVE, 0x1) = 0
Wait for VT1 to activate.
Nothing odd there, definitely looks like a kernel problem.
> I have one thing to add. It looks like that is not fully deterministic
> behavior, at least not at f278a2f^ I'm using now. Occasionally tty
> isn't switched. I wasn't aware of this before.
The console switch is asynchronously handled so a race or a bug in the
handling of the event wait which is what I suspect would indeed show up
that behaviour. X and other apps don't do sudden fast switch and switch
backs which would hide such a bug.
> I just booted that f278a2f^ (i.e. 569ec4c) while consolechars were
> limited only to console-setup script, but this time tty1 remained on
> the screen and I didn't get "INIT: open(/dev/console): Input/output
> error" I was seeing before. I'm not sure whether it is relevant here.
The I/O error is a different bug (technically a user space one), but the
new behaviour was different, not at all expected and was fixed back to
the old sane behaviour.
prev parent reply other threads:[~2009-11-15 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 13:30 Przemysław Pawełczyk
2009-11-15 17:03 ` Alan Cox
2009-11-15 19:21 ` Przemysław Pawełczyk
2009-11-15 20:18 ` Alan Cox [this message]
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=20091115201855.2e046427@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@linux.intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=przemyslaw@pawelczyk.it \
/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
all inboxes | Powered by JetHome®