public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Jim Faulkner <jfaulkne@ccs.neu.edu>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: major network performance difference between 2.4 and 2.6.2-rc2
Date: Wed, 4 Feb 2004 22:28:41 +0100	[thread overview]
Message-ID: <20040204212841.GA9205@bytesex.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0402041529160.7454@denali.ccs.neu.edu>

> While doing a large network transfer, and not at any other time, I get
> tons of messages like this from the kernel:
> 
> Feb  4 15:14:05 delta-9 i2c IR (Hauppauge): unknown key: key=0x3f raw=0x3fff down=0
> Feb  4 15:14:06 delta-9 i2c IR (Hauppauge): unknown key: key=0x3f raw=0x3fff down=1
> 
> I do have a hauppauge remote which works great under the 2.6 kernels
> (thanks Gerd), but I am not pressing any keys while this is happening.

Hmm, what happens if you rmmod the ir-kbd-i2c module?  Any difference?

>   3 root      35  19     0    0    0 S 45.9  0.0   0:46.98 ksoftirqd/0
>   6 root       5 -10     0    0    0 S 43.3  0.0   1:56.63 events/0

One of the two could be ir-kbd-i2c, it polls the i2c IR chip using tasklets.
Not sure which of the kernel threads runs the tasklets ...

  Gerd

-- 
"... und auch das ganze Wochenende oll" -- Wetterbericht auf RadioEins

      parent reply	other threads:[~2004-02-04 21:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  3:06 major network performance difference between 2.4 and 2.6.2-rc2 Jim Faulkner
2004-01-31 14:28 ` Felipe Alfaro Solana
2004-02-04 20:42 ` Jim Faulkner
2004-02-04 20:54   ` Andrew Morton
2004-02-04 21:08     ` David S. Miller
2004-02-04 21:22       ` Andrew Morton
2004-02-05  4:57     ` Jim Faulkner
2004-02-06 21:14       ` Bill Davidsen
2004-02-07 17:56         ` Hilko Bengen
2004-02-18  3:33           ` Bill Davidsen
2004-02-04 21:28   ` Gerd Knorr [this message]

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=20040204212841.GA9205@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=akpm@osdl.org \
    --cc=jfaulkne@ccs.neu.edu \
    --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