linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jens Axboe <axboe@suse.de>, Dave Jones <davej@codemonkey.org.uk>,
	vojtech@suse.cz,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PS2 mouse going nuts during cdparanoia session.
Date: Wed, 16 Jul 2003 23:05:48 +0200	[thread overview]
Message-ID: <20030716210548.GA1951@win.tue.nl> (raw)
In-Reply-To: <1058375425.6600.42.camel@dhcp22.swansea.linux.org.uk>

On Wed, Jul 16, 2003 at 06:10:33PM +0100, Alan Cox wrote:
> On Mer, 2003-07-16 at 18:03, Jens Axboe wrote:
> > > The IDE CD drive is using DMA, and interrupts are unmasked.
> > > according to the logs, its happened 32 times since I last
> 
> So why isnt this occurring on 2.4 .. thats the important question here is
> this a logging thing, a new input layer bug, an ide bug or what ?

The default kernel can spend very large amounts of time in IDE code.
With DMA it can be seconds.
With PIO it can be minutes.
This means that with PIO one may think that the system crashed, and see
(under X) keyboard or mouse actions only after for example two minutes.
With DMA things are much better, but still a delay of seconds
is very noticeable.

The input code used to have

        if (psmouse->pktcnt && time_after(jiffies, psmouse->last + HZ/20)) {
                printk(KERN_WARNING "psmouse.c: Lost synchronization, throwing \
%d bytes away.\n", psmouse->pktcnt);
                psmouse->pktcnt = 0;
        }

and I patched it to HZ/2, that helps, but is still not good enough.


Andries


  parent reply	other threads:[~2003-07-16 20:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16 16:57 PS2 mouse going nuts during cdparanoia session Dave Jones
2003-07-16 17:03 ` Jens Axboe
2003-07-16 17:09   ` Dave Jones
2003-07-16 17:13     ` Jens Axboe
2003-07-16 17:20       ` Dave Jones
2003-07-16 17:24         ` Jens Axboe
2003-07-16 17:21     ` Markus Plail
2003-07-16 17:10   ` Alan Cox
2003-07-16 17:16     ` Jens Axboe
2003-07-16 17:23       ` Dave Jones
2003-07-16 17:25         ` Jens Axboe
2003-07-16 17:28           ` Dave Jones
2003-07-16 17:31             ` Jens Axboe
2003-07-16 18:22               ` Alan Cox
2003-07-16 19:03               ` Kristofer T. Karas
2003-07-16 19:13                 ` Valdis.Kletnieks
2003-07-16 19:00         ` Vojtech Pavlik
2003-07-16 19:30           ` Dave Jones
2003-07-16 20:53             ` Vojtech Pavlik
2003-07-16 23:31               ` Dave Jones
2003-07-16 23:47                 ` Vojtech Pavlik
2003-07-17 11:15                   ` Alan Cox
2003-07-17 17:08                     ` Dave Jones
2003-07-16 18:00     ` Andrew Morton
2003-07-16 18:56     ` Vojtech Pavlik
2003-07-16 21:05     ` Andries Brouwer [this message]
2003-07-16 17:10   ` Valdis.Kletnieks
2003-07-16 17:17     ` Jens Axboe
2003-07-16 17:55       ` Dave Jones
2003-07-16 17:57         ` Jens Axboe
     [not found]         ` <1058422511.1164.1440.camel@workshop.saharacpt.lan>
2003-07-17 12:39           ` Dave Jones
2003-07-16 23:43 Mikael Pettersson
2003-07-17  2:03 ` Jacek Kawa
2003-07-17 21:44   ` Jacek Kawa

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=20030716210548.GA1951@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).