From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: "Manuel A. McLure" <mmt@unify.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Still IRQ routing problems with VIA
Date: Tue, 10 Apr 2001 19:31:25 +0200 [thread overview]
Message-ID: <20010410193125.A31792@pua.domain> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A0@pcmailsrv1.sac.unify.com>
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A0@pcmailsrv1.sac.unify.com>; from mmt@unify.com on Tue, Apr 10, 2001 at 09:51:18AM -0700
On Tue, Apr 10, 2001 at 09:51:18AM -0700, Manuel A. McLure wrote:
> Axel Thimm said...
> > Several weeks ago there had been a thread on the pirq assignments of newer
> > VIA and SiS chipsets ending with everybody happy.
> > Everybody? Not everybody - there is a small village of chipsets resisting
> > the advent of 2.4.x :(
> > The system is a KT133A (MSI's K7T Turbo MS-6330 board)/Duron 700
> > system. Kernel 2.4.x have IRQ routing problems and USB failures (the
> > latter will most probably be due to IRQ mismatches, I believe).
> I have the same motherboard with the same lspci output (i.e. I get the "pin
> ?" part), but I don't see any problems running 2.4.3 or 2.4.3-ac[23]. I am
> only using a trackball on my USB port - what problems are you seeing?
Well, a part of the attached dmesg output yields:
> PCI: Found IRQ 11 for device 00:07.2
> IRQ routing conflict in pirq table for device 00:07.2
> IRQ routing conflict in pirq table for device 00:07.3
> PCI: The same IRQ used for device 00:0e.0
> uhci.c: USB UHCI at I/O 0x9400, IRQ 5
and later:
> uhci: host controller process error. something bad happened
> uhci: host controller halted. very bad
0.7.[2,3] are the usb devices. BIOS (and 2.2 kernels) had them at IRQ 5. 2.4
somehow picks the irq of the ethernet adapter, iqr 11, instead.
At least usb is then unusable.
As you say that you have the same board, what is the output of dump_pirq - are
your link values in the set of {1,2,3,5} or are they continuous 1-4? Maybe you
are lucky - or better say, I am having bad luck :(
--
Axel.Thimm@physik.fu-berlin.de
next prev parent reply other threads:[~2001-04-10 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 17:52 Still IRQ routing problems with VIA 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 ` Axel Thimm [this message]
2001-04-10 17:38 ` Still IRQ routing problems with VIA Jeff Garzik
2001-04-10 19:16 ` Axel Thimm
2001-04-11 15:13 ` Pierre Etchemaite
2001-04-10 21:05 Manuel A. McLure
2001-04-10 21:11 ` Jeff Garzik
2001-04-11 19:56 ` Axel Thimm
2001-04-10 21:24 Manuel A. McLure
2001-04-10 21:36 ` Jeff Garzik
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=20010410193125.A31792@pua.domain \
--to=axel.thimm@physik.fu-berlin.de \
--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).