From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
arjanv@redhat.com, "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Manuel A. McLure" <mmt@unify.com>,
"Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>,
"ARND BERGMANN" <std7652@et.FH-Osnabrueck.DE>,
"Dunlap, Randy" <randy.dunlap@intel.com>,
"Martin Diehl" <mdiehlcs@compuserve.de>,
"Adrian Cox" <adrian@humboldt.co.uk>,
"Capricelli Thomas" <orzel@kde.org>,
"Ian Bicking" <ianb@colorstudy.com>,
"John R Lenton" <john@grulic.org.ar>,
"Jens Dreger" <Jens.Dreger@physik.fu-berlin.de>,
"David Hansen" <David.Hansen@physik.fu-berlin.de>
Subject: Re: PATCH 2.4.5.1: Fix Via interrupt routing issues
Date: Mon, 14 May 2001 17:21:04 +0200 [thread overview]
Message-ID: <20010514172104.A2160@pua.nirvana> (raw)
In-Reply-To: <3AFEC426.50B00B78@mandrakesoft.com>
In-Reply-To: <3AFEC426.50B00B78@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Sun, May 13, 2001 at 01:28:06PM -0400
On Sun, May 13, 2001 at 01:28:06PM -0400, Jeff Garzik wrote:
> For those of you with Via interrupting routing issues (or
> interrupt-not-being-delivered issues, etc), please try out this patch
> and let me know if it fixes things. It originates from a tip from
> Adrian Cox... thanks Adrian!
Unfortunately the patch does not trigger here. nr_ioapics is zero on my UP
KT133A board. Was this patch for MP only?
--
Axel.Thimm@physik.fu-berlin.de
next prev parent reply other threads:[~2001-05-14 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 17:28 PATCH 2.4.5.1: Fix Via interrupt routing issues Jeff Garzik
2001-05-13 18:38 ` Alan Cox
2001-05-13 18:45 ` Jeff Garzik
2001-05-13 18:47 ` Alan Cox
2001-05-14 15:21 ` Axel Thimm [this message]
2001-05-14 16:16 ` Jeff Garzik
2001-05-14 19:05 ` Axel Thimm
2001-05-14 19:14 ` Axel Thimm
2001-05-14 17:07 ` John R Lenton
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=20010514172104.A2160@pua.nirvana \
--to=axel.thimm@physik.fu-berlin.de \
--cc=David.Hansen@physik.fu-berlin.de \
--cc=Jens.Dreger@physik.fu-berlin.de \
--cc=adrian@humboldt.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=ianb@colorstudy.com \
--cc=jgarzik@mandrakesoft.com \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=mdiehlcs@compuserve.de \
--cc=mmt@unify.com \
--cc=moffe@amagerkollegiet.dk \
--cc=orzel@kde.org \
--cc=randy.dunlap@intel.com \
--cc=std7652@et.FH-Osnabrueck.DE \
/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