From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Gerhard Mack <gmack@innerfire.net>,
James Simmons <jsimmons@infradead.org>
Cc: Robert Love <rml@tech9.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.71 - random console corruption
Date: Wed, 18 Jun 2003 12:56:24 +0100 [thread overview]
Message-ID: <200306181256.30735@gjs> (raw)
In-Reply-To: <Pine.LNX.4.44.0306172149150.8889-100000@innerfire.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 18 of June 2003 02:50, Gerhard Mack wrote:
> On Tue, 17 Jun 2003, James Simmons wrote:
> > > > For userland<->kernel transactions we have the console_semaphore to
> > > > protect us. It is also used for console_callback. The
> > > > console_semaphore is not used internally to protect global variables
> > > > :-( To do this properly would take quite a bit of work.
> > >
> > > It looks like all these globals need a lock -- they can race on SMP or
> > > with kernel preemption.
> > >
> > > Is it really going to be that hard to wrap a lock around their access,
> > > because I think this is going to bite SMP users.
> >
> > For things like fg_console and currcon it will be. Those variables are
> > used everyway like mad. That is a whole lot of locks. I doubt this issue
> > will be solved until 2.7.X.
>
> Interestingly enough it's not console switching that does it.. it's
> scrolling also as I mentioned before it's not just with preempt enabled.
>
> I wonder if theres another problem somewhere?
I've got simmilar problem with 2.5.72, sometimes keyboard stops to respond (in
X windows). Mouse is usefull, all i have to do is restart Xwindows and
everything is running well.
- --
Grzegorz Jaskiewicz
K4 Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+8FNtqu082fCQYIgRAkjyAJ9tWkOANrS9jEWo9XytzhM1k9bNEQCfXRzd
3IgRlKPiiJUt3z0gf791bUA=
=Z8VM
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-18 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 0:59 Linux 2.5.71 - random console corruption Gerhard Mack
2003-06-16 21:27 ` James Simmons
2003-06-16 21:31 ` Robert Love
2003-06-16 23:34 ` James Simmons
2003-06-16 23:40 ` Robert Love
2003-06-17 20:50 ` James Simmons
2003-06-18 1:50 ` Gerhard Mack
2003-06-18 11:56 ` Grzegorz Jaskiewicz [this message]
2003-06-18 16:38 ` James Simmons
2003-06-18 16:20 ` Grzegorz Jaskiewicz
2003-06-18 20:28 ` James Simmons
2003-06-18 20:08 ` Grzegorz Jaskiewicz
2003-06-18 16:55 ` Gerhard Mack
2003-06-19 20:43 ` Bill Davidsen
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=200306181256.30735@gjs \
--to=gj@pointblue.com.pl \
--cc=gmack@innerfire.net \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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