From: Jens Axboe <axboe@suse.de>
To: Dave Jones <davej@codemonkey.org.uk>,
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 19:31:22 +0200 [thread overview]
Message-ID: <20030716173122.GQ833@suse.de> (raw)
In-Reply-To: <20030716172823.GE21896@suse.de>
On Wed, Jul 16 2003, Dave Jones wrote:
> > > > 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..
> > Thanks.
>
> Well, that didn't take long..
>
> procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu----
> r b swpd free buff cache si so bi bo in cs us sy id wa
> 2 0 109376 9632 2576 44368 0 0 136 28 1636 1304 1 4 90 4
> 0 0 109376 8036 2588 45852 0 0 1492 0 2166 15874 2 11 82 5
> 1 0 109376 8036 2588 45852 0 0 0 0 1089 1230 1 1 99 0
> 1 0 109376 8004 2612 45896 0 0 8 144 2660 1088 1 11 85 4
> 1 0 109376 5880 2616 46436 0 0 0 0 1338 1263 2 24 74 0
> 2 0 109376 5512 2576 45320 0 0 0 72 2108 1434 4 35 61 0
> 2 0 109376 5816 2520 45252 56 0 60 940 1852 2340 6 33 59 2
> 1 0 109376 4880 2448 45800 0 0 0 520 1940 2930 6 33 60 2
> 0 0 109376 5468 2412 45300 0 0 16 1672 2504 3077 9 42 44 7
> 1 0 109376 5532 2396 45792 0 0 0 344 2172 3504 4 33 61 2
> 1 0 109376 4132 2416 46452 0 0 8 4 2727 3483 5 39 54 1
> 0 0 109376 4864 2384 45484 0 0 4 1324 2186 3448 5 34 59 4
> 1 0 109376 5024 2384 46436 0 0 0 600 2484 3533 4 36 58 2
>
> Lost sync here. Mouse dancing. vmstat output stopped for a few seconds.
Doesn't look really bogged down by interrupt load, still half idle. So
that looks like a PS2 bug. Unless the irq latencies are really bad, I
guess that could be it too. Vojtech knows a hell of a lot more about
that than me :)
--
Jens Axboe
next prev parent reply other threads:[~2003-07-16 17:18 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 [this message]
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
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=20030716173122.GQ833@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.