From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, "Manuel A. McLure" <mmt@unify.com>,
Jens Dreger <Jens.Dreger@physik.fu-berlin.de>,
David Hansen <David.Hansen@physik.fu-berlin.de>
Subject: Re: Still IRQ routing problems with VIA
Date: Wed, 11 Apr 2001 21:56:34 +0200 [thread overview]
Message-ID: <20010411215634.A6407@pua.domain> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A6@pcmailsrv1.sac.unify.com> <3AD3770E.8AA6D989@mandrakesoft.com>
In-Reply-To: <3AD3770E.8AA6D989@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Apr 10, 2001 at 05:11:42PM -0400
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On Tue, Apr 10, 2001 at 05:11:42PM -0400, Jeff Garzik wrote:
> "Manuel A. McLure" wrote:
> > Jeff Garzik said...
> > > Changing '#undef DEBUG' to '#define DEBUG 1' in
> > > arch/i386/kernel/pci-i386.h is also very helpful. Can you guys do so,
> > > and post the 'dmesg -s 16384' results to lkml? This includes the same
> > > information as dump_pirq, as well as some additional information.
> > Here's my dmesg output - I tried with both PNP: Yes and PNP: No and the
> > dmesg outputs were exactly the same modulo a Hz or two in the processor
> > speed detection.
We are having the same observation here, PNP yse or no does not change dmesg
output of 2.4.x.
> Thanks. I'm building a database of these. There is definitely an issue
> with Via and interrupt routing. Hopefully I can collate this data soon and
> figure out what's going on. I need to find some Via hardware for myself,
> too, since I only have an old Via-based laptop which works 100% ;-)
O.K., here are three further dmesg outputs of the same 2.4.3 kernel
configuration (yes ""|make config) [Thanks to Jens and David!].
Two MSI K7T Pro2A boards (my first report was a MSI K7T Turbo board with
KT133A):
dmesg.David.msi-k7t-pro2a.log.gz
dmesg.Silke.msi-k7t-pro2a.log.gz
An Asus A7V Board:
dmesg.a7v.log.gz
Recognizing any pattern?
--
Axel.Thimm@physik.fu-berlin.de
[-- Attachment #2: dmesg.David.msi-k7t-pro2a.log.gz --]
[-- Type: application/x-gzip, Size: 2979 bytes --]
[-- Attachment #3: dmesg.Silke.msi-k7t-pro2a.log.gz --]
[-- Type: application/x-gzip, Size: 3399 bytes --]
[-- Attachment #4: dmesg.a7v.log.gz --]
[-- Type: application/x-gzip, Size: 3305 bytes --]
next prev parent reply other threads:[~2001-04-11 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 21:05 Still IRQ routing problems with VIA Manuel A. McLure
2001-04-10 21:11 ` Jeff Garzik
2001-04-11 19:56 ` Axel Thimm [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 21:24 Manuel A. McLure
2001-04-10 21:36 ` Jeff Garzik
2001-04-10 17:52 Manuel A. McLure
2001-04-10 18:01 ` Jeff Garzik
2001-04-10 16:51 ` Still IRQ routing problems with VIA (was: VIA KT133 chipset P CI crazyness...) Manuel A. McLure
2001-04-10 17:31 ` Still IRQ routing problems with VIA Axel Thimm
2001-04-10 17:38 ` Jeff Garzik
2001-04-10 19:16 ` Axel Thimm
2001-04-11 15:13 ` Pierre Etchemaite
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=20010411215634.A6407@pua.domain \
--to=axel.thimm@physik.fu-berlin.de \
--cc=David.Hansen@physik.fu-berlin.de \
--cc=Jens.Dreger@physik.fu-berlin.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmt@unify.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;
as well as URLs for NNTP newsgroup(s).