From: Pete Toscano <pete@research.netsol.com>
To: linux-kernel@vger.kernel.org
Subject: Re: VIA chipset discussion
Date: Wed, 17 Jan 2001 17:40:06 -0500 [thread overview]
Message-ID: <20010117174006.E1503@tesla.admin.cto.netsol.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101171358020.1171-100000@ns-01.hislinuxbox.com>
In-Reply-To: <Pine.LNX.4.21.0101171358020.1171-100000@ns-01.hislinuxbox.com>; from pgpkeys@hislinuxbox.com on Wed, Jan 17, 2001 at 02:02:17PM -0800
well, i know there's a problem with the via apollo pro 133a chipset,
smp, apic, and usb. it looks like the usb driver (usb-uhci) doesn't
receive any interrupts if apic is enabled. if you disable apic from the
lilo prompt with "noapic", then it'll all work (of course, without
apic).
according to the linux-usb maintainers, it's a pci irq routing problem.
i've asked jeff garzik and martin mares if they'll look into it, but
they're pretty busy and i haven't heard anything back from them (not
that'd i'd expect to for quite a while, considering their load). i've
asked on the list too, but i've only heard back from people with the
same problem, not anyone who can fix the problem.
i've pretty much got the same system as you, except for the ultra66
promise card.
pete
On Wed, 17 Jan 2001, David D.W. Downey wrote:
>
> Could those that were involved in the VIA chipset discussion email me
> privately at pgpkeys@hislinuxbox.com?
>
> I'm truly interested in solving this issue. I personally think it's more
> than just the chipset causing the problems.
>
>
> I'm looking for members of the list that are using the kernel support for
> the following
>
>
> VIA chipset
> Promise controller (PDC2026# with specifics on the PDC20265 (ATA100))
> SMP support
> IDE + SCSI mix in the system.
>
>
> I'm trying to track a number of POSSIBLE bugs (can't say they are for
> sure) and any input from folks with this mix of drivers would be
> exponentially useful, even if for nothing more than discounting some of my
> thoughts.
>
>
> Also, can anyone summurize the already known and specific problems with
> combinations of the above requirements? I would truly appreciate that.
>
> David D.W. Downey
-
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/
next prev parent reply other threads:[~2001-01-17 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 22:02 VIA chipset discussion David D.W. Downey
2001-01-17 22:40 ` Pete Toscano [this message]
2001-01-18 4:04 ` Rogerio Brito
2001-01-18 18:13 ` Matthew Fredrickson
2001-01-18 23:32 ` John O'Donnell
2001-01-18 23:42 ` Howard Johnson
2001-01-19 14:53 ` Vojtech Pavlik
2001-01-19 16:42 ` John O'Donnell
2001-01-19 21:54 ` Matthew Fredrickson
2001-01-21 18:39 ` David D.W. Downey
2001-01-22 8:54 ` Howard Johnson
2001-01-19 6:42 ` Rogerio Brito
2001-01-20 8:39 ` Andy Galasso
2001-01-21 18:46 ` David D.W. Downey
2001-01-23 17:28 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-01-18 10:18 Petr Vandrovec
[not found] <20010118081259.A694@suse.cz>
[not found] ` <Pine.LNX.4.21.0101181548230.9718-100000@ns-01.hislinuxbox.com>
2001-01-21 11:54 ` Vojtech Pavlik
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=20010117174006.E1503@tesla.admin.cto.netsol.com \
--to=pete@research.netsol.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