public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: PATCH 2.4.5.1: Fix Via interrupt routing issues
Date: Mon, 14 May 2001 21:05:56 +0200	[thread overview]
Message-ID: <20010514210556.A3371@pua.nirvana> (raw)
In-Reply-To: <3AFEC426.50B00B78@mandrakesoft.com> <20010514172104.A2160@pua.nirvana> <3B0004F7.4C54E2E4@mandrakesoft.com>
In-Reply-To: <3B0004F7.4C54E2E4@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, May 14, 2001 at 12:16:55PM -0400

[Cc: list trimmed]

On Mon, May 14, 2001 at 12:16:55PM -0400, Jeff Garzik wrote:
> Axel Thimm wrote:
> > 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?
> 
> Not for MP only, but mostly such:  UP systems with IO-APIC, or MP
> systems.

What about the following dmesg logs:

> Local APIC disabled by BIOS -- reenabling.
> Found and enabled local APIC!
> [...]
> Using local APIC timer interrupts.
> calibrating APIC timer ...

Don't they imply an APIC?

Anyway, I am sending the dmesg with "#define DEBUG 1" in pci-i386.h. It is a
2.4.4-ac5 defconfig kernel, but 2.4.4 has the same errors. System is an
MS-6330 v3.0 (MSI K7T Turbo), KT133A, Duron 700. I you have any idea, how I
could fix the pirq table I'd be glad to test further.

Regards, Axel.
-- 
Axel.Thimm@physik.fu-berlin.de

  reply	other threads:[~2001-05-14 19:09 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
2001-05-14 16:16   ` Jeff Garzik
2001-05-14 19:05     ` Axel Thimm [this message]
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=20010514210556.A3371@pua.nirvana \
    --to=axel.thimm@physik.fu-berlin.de \
    --cc=jgarzik@mandrakesoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox