From: Joshua Kwan <joshk@ludicrus.ath.cx>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.59-mm6
Date: Mon, 27 Jan 2003 00:46:04 -0800 [thread overview]
Message-ID: <20030127084604.GA19453@ludicrus.ath.cx> (raw)
In-Reply-To: <20030127004059.5717e8e3.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]
On Mon, Jan 27, 2003 at 12:40:59AM -0800, Andrew Morton wrote:
[snip]
> This is debug stuff - it tells us which drivers are disabling interrupts for
> more than one or two clock ticks. Please send the full trace so we can bug
> the maintainers into fixing the drivers up.
>
Sure:
------
Warning! Detected 30879 micro-second gap between interrupts.
Compensating for 29 lost ticks.
Call Trace:
[<c010a948>] handle_IRQ_event+0x38/0x60
[<c010ab77>] do_IRQ+0x97/0x120
[<c010957c>] common_interrupt+0x18/0x20
[<c02601f4>] i8042_command+0x94/0xc0
[<c02602b6>] i8042_aux_write+0x36/0x70
[<c025e1cd>] atkbd_sendbyte+0x7d/0x80
[<c025e2b1>] atkbd_command+0xe1/0xf0
[<c025e64b>] atkbd_probe+0x12b/0x180
[<c025e96a>] atkbd_connect+0x25a/0x2b0
[<c025fb93>] serio_find_dev+0x53/0x60
[<c0105075>] init+0x35/0x160
[<c0105040>] init+0x0/0x160
[<c010713d>] kernel_thread_helper+0x5/0x18
Warning! Detected 113343 micro-second gap between interrupts.
Compensating for 112 lost ticks.
Call Trace:
[<c010a948>] handle_IRQ_event+0x38/0x60
[<c010ab77>] do_IRQ+0x97/0x120
[<c010957c>] common_interrupt+0x18/0x20
[<c02601f4>] i8042_command+0x94/0xc0
[<c0260436>] i8042_close+0x46/0x90
[<c025ff81>] serio_close+0x11/0x20
[<c025e989>] atkbd_connect+0x279/0x2b0
[<c025fb93>] serio_find_dev+0x53/0x60
[<c0105075>] init+0x35/0x160
[<c0105040>] init+0x0/0x160
[<c010713d>] kernel_thread_helper+0x5/0x18
Warning! Detected 30145 micro-second gap between interrupts.
Compensating for 29 lost ticks.
Call Trace:
[<c010a948>] handle_IRQ_event+0x38/0x60
[<c010ab77>] do_IRQ+0x97/0x120
[<c010957c>] common_interrupt+0x18/0x20
[<c02601f4>] i8042_command+0x94/0xc0
[<c0260436>] i8042_close+0x46/0x90
[<c025ff81>] serio_close+0x11/0x20
[<c025fa7e>] psmouse_connect+0x19e/0x1c0
[<c025fb93>] serio_find_dev+0x53/0x60
[<c0105075>] init+0x35/0x160
[<c0105040>] init+0x0/0x160
[<c010713d>] kernel_thread_helper+0x5/0x18
---
>> Each of these warnings reproduces for each input device on my system
>> (there are 3 now, so if i disconnect, say, my USB mouse, there will be
>> only 2.)
A closer look tells me that this isn't quite true. Sorry..
Regards
Josh
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-27 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 7:10 2.5.59-mm6 Andrew Morton
2003-01-27 7:10 ` 2.5.59-mm6 Andrew Morton
2003-01-27 8:17 ` 2.5.59-mm6 Andres Salomon
2003-01-27 8:24 ` 2.5.59-mm6 Joshua Kwan
2003-01-27 8:40 ` 2.5.59-mm6 Andrew Morton
2003-01-27 8:46 ` Joshua Kwan [this message]
2003-01-27 9:51 ` 2.5.59-mm6 Helge Hafting
2003-01-27 9:51 ` 2.5.59-mm6 Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2003-01-27 12:27 2.5.59-mm6 Luuk van der Duim
2003-01-27 18:50 ` 2.5.59-mm6 Mike Galbraith
2003-01-27 19:17 ` 2.5.59-mm6 Zwane Mwaikambo
[not found] ` <Pine.LNX.4.44.0301271414230.28141-100000@montezuma.mastece nde.com>
2003-01-27 20:11 ` 2.5.59-mm6 Mike Galbraith
2003-01-27 21:13 ` 2.5.59-mm6 Zwane Mwaikambo
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=20030127084604.GA19453@ludicrus.ath.cx \
--to=joshk@ludicrus.ath.cx \
--cc=akpm@digeo.com \
--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 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.