linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Dave Jones <davej@codemonkey.org.uk>, Jens Axboe <axboe@suse.de>,
	Alan Cox <alan@lxorguk.ukuu.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 21:00:18 +0200	[thread overview]
Message-ID: <20030716190018.GE20241@ucw.cz> (raw)
In-Reply-To: <20030716172331.GD21896@suse.de>

On Wed, Jul 16, 2003 at 06:23:31PM +0100, Dave Jones wrote:
> On Wed, Jul 16, 2003 at 07:16:07PM +0200, Jens Axboe wrote:
> 
>  > > > 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 ?
>  > Dave, have you tried 2.4 newest?
> 
> I've not booted a 2.4 kernel since 2.4.20..
> 
>  > Some of the newer IDE stuff kept
>  > interrupts off for ages, maybe it's on 2.4 also.
> 
> I can try sometime if you want to know.. (I've got plenty more
> CDs that need encoding, so I'll have plenty of opportunity to
> see this bug if its there 8-)

Dave, can you please enable the DEBUG in i8042.c so that I can see
whether the bytes really get lost or if the unsync check is just
triggering by mistake?

>  > Also Dave, can you try
>  > and do a vmstat 1 while ripping and PS2 dropping out?
> 
> Ok, I just fired that up in another window.
> When it happens next, I'll mail off a snapshot..
> 
> 		Dave
> 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2003-07-16 18:46 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 [this message]
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
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=20030716190018.GE20241@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;
as well as URLs for NNTP newsgroup(s).