From: Philip Armstrong <phil@kantaka.co.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Christian.Engstler@gmx.net, evaner@bigfoot.com,
jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: Related VIA PCI crazyness?
Date: Wed, 10 Jan 2001 21:55:09 +0000 [thread overview]
Message-ID: <20010110215509.A2846@kantaka.co.uk> (raw)
In-Reply-To: <20010107122800.A636@kantaka.co.uk> <200101072352.PAA28348@penguin.transmeta.com>
In-Reply-To: <200101072352.PAA28348@penguin.transmeta.com>; from torvalds@transmeta.com on Sun, Jan 07, 2001 at 03:52:41PM -0800
On Sun, Jan 07, 2001 at 03:52:41PM -0800, Linus Torvalds wrote:
> In article <20010107122800.A636@kantaka.co.uk>,
> Philip Armstrong <phil@kantaka.co.uk> wrote:
> >In supplement to Evan Thompson's emails with the subject "Additional
> >info. for PCI VIA IDE crazyness. Please read." I've noticed the
> >following message with recent 2.4.0 test + release kernels:
> >
> >IRQ routing conflict in pirq table! Try 'pci=autoirq'
>
> But the machine still works fine, ie the SCSI driver and the network
> driver still seem happy?
extra information. I just spent an hour trying to convince this board
to play nice with an ISA PNP AWE64 sound card.
This caused the BIOS to throw its hands in the air and give up
entirely as far as I can see. IRQ conflicts all over the place. Linux
runs; windows manages to start, but can't talk to the scsi card at
all.
And isa-pnp.o in 2.4.0 resulted in a never ending stream of messages
to the console, hanging the machine, like so:
isapnp: unexpected or unknown tag type 0xff ...
Taking the AWE64 out solved the issues. It could be a bust card of
course, but I think the BIOS is stuffed.
cheers,
Phil
--
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-10 21:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 12:28 Philip Armstrong
2001-01-07 14:33 ` Adrian Bunk
2001-01-07 23:52 ` Linus Torvalds
2001-01-07 21:02 ` Albert Cranford
2001-01-08 3:18 ` Linus Torvalds
2001-01-09 6:06 ` Eric W. Biederman
2001-01-08 2:31 ` Adrian Bunk
2001-01-09 0:53 ` Evan Thompson
2001-01-09 17:19 ` Pete Toscano
[not found] ` <200101072352.PAA28348@penguin.transmeta.com>
2001-01-08 1:44 ` Evan Thompson
2001-01-08 9:08 ` Philip Armstrong
2001-01-10 21:55 ` Philip Armstrong [this message]
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=20010110215509.A2846@kantaka.co.uk \
--to=phil@kantaka.co.uk \
--cc=Christian.Engstler@gmx.net \
--cc=evaner@bigfoot.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®