From: Arjan van de Ven <arjan@fenrus.demon.nl>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21-pre4: PDC ide driver problems with shared interrupts
Date: 23 Feb 2003 16:04:31 +0100 [thread overview]
Message-ID: <1046012671.1964.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030223153316.262a201e.skraw@ithnet.com>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Sun, 2003-02-23 at 15:33, Stephan von Krawczynski wrote:
> On Thu, 06 Feb 2003 15:51:47 +0100
> Hans Lambrechts <hans.lambrechts@skynet.be> wrote:
>
> > Stephan von Krawczynski wrote:
> >
> > <---snip--->
> >
> > >
> > > CPU0 CPU1
> > > 0: 71158 0 IO-APIC-edge timer
> > > 1: 941 0 IO-APIC-edge keyboard
> > > 2: 0 0 XT-PIC cascade
> > > 12: 33166 0 IO-APIC-edge PS/2 Mouse
> > > 15: 4 0 IO-APIC-edge ide1
<snip>
> I am sorry, but this patch is:
> a) already included in 2.4.21-pre4 (which I run)
> b) does therefore obviously not help
>
> Any other suggestions?
could you give the irqbalance daemon from
http://people.redhat.com/arjanv/irqbalance/irqbalance-0.06.tar.gz
a try ?
Greetings,
Arjan van de Ven
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-23 15:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030202153009$2e0d@gated-at.bofh.it>
[not found] ` <20030205181006$107c@gated-at.bofh.it>
[not found] ` <20030205181006$7bb8@gated-at.bofh.it>
[not found] ` <20030205181006$455c@gated-at.bofh.it>
[not found] ` <20030205181006$5dba@gated-at.bofh.it>
[not found] ` <20030205181006$3358@gated-at.bofh.it>
[not found] ` <200302061451.h16Epl0Z001134@pc.skynet.be>
2003-02-23 14:33 ` 2.4.21-pre4: PDC ide driver problems with shared interrupts Stephan von Krawczynski
2003-02-23 15:04 ` Arjan van de Ven [this message]
2003-02-23 17:29 ` Stephan von Krawczynski
[not found] <3F1C54A8.5020404@snarkhunter.com>
2003-07-22 14:44 ` Edward King
2003-07-22 18:07 ` John V. Martinez
2003-07-22 21:02 ` Edward King
[not found] <7b263321.0302140626.2ddb7980@posting.google.com>
2003-02-14 14:41 ` Edward King
2003-02-14 15:41 ` Benjamin Herrenschmidt
2003-02-05 16:44 Robbert Kouprie
2003-02-05 19:45 ` Bryan Andersen
-- strict thread matches above, loose matches on Subject: below --
2003-02-02 15:18 2.4.21-pre4: tg3 " Stephan von Krawczynski
2003-02-02 16:49 ` Jeff Garzik
2003-02-02 17:52 ` Stephan von Krawczynski
2003-02-02 18:28 ` Jeff Garzik
2003-02-05 9:48 ` 2.4.21-pre4: PDC ide " Stephan von Krawczynski
2003-02-05 11:16 ` Benjamin Herrenschmidt
2003-02-05 11:39 ` Stephan von Krawczynski
2003-02-05 12:21 ` Alan Cox
2003-02-05 12:22 ` Benjamin Herrenschmidt
2003-02-05 12:50 ` Alan Cox
2003-02-05 13:19 ` Stephan von Krawczynski
2003-02-05 12:24 ` Alan Cox
2003-02-05 16:56 ` Ross Biro
2003-02-05 17:12 ` Benjamin Herrenschmidt
2003-02-05 17:19 ` Ross Biro
2003-02-05 17:34 ` Benjamin Herrenschmidt
2003-02-05 17:38 ` Stephan von Krawczynski
[not found] ` <1044467091.685.155.camel@zion.wanadoo.fr>
2003-02-05 17:58 ` Stephan von Krawczynski
2003-02-05 20:00 ` Bryan Andersen
2003-02-05 19:10 ` Alan Cox
2003-02-06 12:20 ` Stephan von Krawczynski
2003-02-06 23:04 ` Benjamin Herrenschmidt
2003-02-07 9:10 ` Stephan von Krawczynski
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=1046012671.1964.2.camel@laptop.fenrus.com \
--to=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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