public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
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 20:56:19 +0200	[thread overview]
Message-ID: <20030716185619.GD20241@ucw.cz> (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
> 
> > Yes. You can try and make the situation a little better by unmasking
> > interrupts with -u1. Or you can try and use a ripper that actually uses
> 
> He already is 
> 
> > SG_IO, that way you can use dma (and zero copy) for the rips. That will
> > be lots more smooth.
> 
> So why isnt this occuring on 2.4 .. thats the important question here is
> this a logging thing, a new input layer bug, an ide bug or what ?

This is basically because the check for lost bytes wasn't present in
2.4. Now that it is there, it works well with real lost bytes, but will
fire also in case when the mouse interrupt was delayed for more than
half a second, or if indeed a mouse interrupt gets lost. The 2.5 kernel
by default programs the mouse to high speed reporting (up to 200 updates
per second). This may, possibly make the problem show up easier. There
might be real lost bytes on some machines, too. This can be checked by
defining DEBUG in i8042.c

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2003-07-16 18:44 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 [this message]
2003-07-16 21:05     ` Andries Brouwer
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
  -- strict thread matches above, loose matches on Subject: below --
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=20030716185619.GD20241@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=davej@codemonkey.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox