From: Andrew Morton <akpm@osdl.org>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: albert@users.sourceforge.net, linux-yoann@ifrance.com,
linux-kernel@vger.kernel.org, akpm@digeo.com, vortex@scyld.com,
jgarzik@pobox.com
Subject: Re: another must-fix: major PS/2 mouse problem
Date: Fri, 25 Jul 2003 20:19:14 -0700 [thread overview]
Message-ID: <20030725201914.644b020c.akpm@osdl.org> (raw)
In-Reply-To: <1059097601.1220.75.camel@cube>
Albert Cahalan <albert@users.sourceforge.net> wrote:
>
> I hope you don't consider a 100 Mb/s PCI device to be
> a nasty old NIC. It's not an NE2000 you know! I have this:
Sorry, I got my boomerangs and vortices mixed up. Vortex is the ancient one.
> I added code to the top and bottom of do_IRQ, as well as to
> the top and bottom of boomerang_interrupt. The lockmeter was
> compiled into the kernel but never enabled. I record the
> minimum and maximum time in microseconds.
>
> -------------------------------
> IRQ num use min max
> --- ------ -------- --- -------
> 0 746770 timer 40 103595
> 1 936 i8042 13 389773
> 2 0 cascade - -
> 3 - - - -
> 4 9 serial 28 56
> 5 0 uhci-hcd - -
> 6 - - 711 711
> 7 - - 25 25
> 8 - - - -
> 9 - - - -
> 10 - - - -
> 11 2417 eth0 87 1535331
> 12 60 i8042 18 102895
> 13 - - - -
> 14 13844 ide0 8 51944
> 15 2 ide1 7 11
But did your instrumentation account for nested interrupts? What happens
if a slow i8042 interrupt happens in the middle of a 3c59x interrupt?
Still, that probably doesn't account for the stalls.
I don't know what does account for it, frankly. You could try dropping the
2.4 driver into the 2.5 tree just to verify that it is not a driver
problem. The driver has hardly changed at all.
next prev parent reply other threads:[~2003-07-26 3:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 1:46 another must-fix: major PS/2 mouse problem Albert Cahalan
2003-06-04 5:47 ` Yoann
[not found] ` <20030603232155.1488c02f.akpm@digeo.com>
2003-06-04 7:47 ` Vojtech Pavlik
2003-06-04 7:53 ` Andrew Morton
2003-06-04 8:00 ` Vojtech Pavlik
2003-06-04 8:14 ` Andrew Morton
2003-06-04 8:40 ` Vojtech Pavlik
2003-06-04 19:20 ` Yoann
2003-06-04 23:09 ` Albert Cahalan
[not found] ` <3EDCF47A.1060605@ifrance.com>
[not found] ` <1054681254.22103.3750.camel@cube>
[not found] ` <3EDD8850.9060808@ifrance.com>
2003-07-23 0:44 ` Albert Cahalan
2003-07-24 17:30 ` Andrew Morton
2003-07-25 1:46 ` Albert Cahalan
2003-07-26 3:19 ` Andrew Morton [this message]
2003-07-26 15:16 ` Zwane Mwaikambo
2003-07-29 2:55 ` Albert Cahalan
2003-07-29 3:14 ` Andrew Morton
2003-07-29 12:40 ` Albert Cahalan
2003-07-29 18:58 ` Andrew Morton
2003-07-29 19:36 ` Zwane Mwaikambo
2003-07-29 19:43 ` Chris Friesen
2003-07-30 5:08 ` Pavel Machek
2003-07-30 6:32 ` Andrew Morton
2003-07-30 12:29 ` Albert Cahalan
2003-07-30 19:18 Mikael Pettersson
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=20030725201914.644b020c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=akpm@digeo.com \
--cc=albert@users.sourceforge.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-yoann@ifrance.com \
--cc=vortex@scyld.com \
/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).