All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Schroeder <mdhs@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Bug in console driver?
Date: Sun, 16 Sep 2001 13:32:06 GMT	[thread overview]
Message-ID: <20010916.13320600@sirius.imsch.de> (raw)

Hi!

I suppose there is a bug in the 2.4-kernel console driver 
(../drivers/char/console.c).

It seems that (if there is a slow video device) this driver disables the 
handling of interrupts while writing or switching the consoles. 

Symptoms:

If you use the VESA framebuffer, switching to another console prevents 
updating the internal kernel clock (jiffies, xtime) for a short time. 
This effect can grow up to some seconds:

Load the GNU Midnight Commander (mc) and synchronize kernel clock and 
hardware clock with the command 'hwclock --hctosys'.

Then you can see the the difference with 'hwclock && date'.

  # hwclock && date
  Sun Sep 16 10:31:33 2001  -0,154753 ...
  Sun Sep 10 10:31:32 CEST 2001

Now hold down the keys <Ctrl+o> for a some seconds. (This switches the 
window of the Midnight Commander on/off many times)

If you now compare the clocks you yield a difference of some seconds:

  # hwclock && date
  Sun Sep 16 10:33:17 2001  -0,456384 ...
  Sun Sep 16 10:33:12 CEST 2001

5 seconds - I think this is a bug.


My system:

Intel Pentium II, 512 MB RAM
NVIdia Riva TNT2 M64 with 32 MB
Kernel 2.4.4 and 2.4.7
SuSE Linux 7.2
VESA Framebuffer 


Greetings

Michael






             reply	other threads:[~2001-09-16 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-16 13:32 Michael Schroeder [this message]
2001-09-17  4:55 ` Bug in console driver? Andrew Morton

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=20010916.13320600@sirius.imsch.de \
    --to=mdhs@gmx.de \
    --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.