From: Pete Toscano <pete.lkml@toscano.org>
To: David DeGeorge <dld@degeorge.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC usb MPS 1.4 and the 2.4.2 kernel
Date: Tue, 13 Mar 2001 00:25:13 -0500 [thread overview]
Message-ID: <20010313002513.A1664@bubba.toscano.org> (raw)
In-Reply-To: <200103130245.f2D2j2J01057@janus.local.degeorge.org>
In-Reply-To: <200103130245.f2D2j2J01057@janus.local.degeorge.org>; from dld@degeorge.org on Mon, Mar 12, 2001 at 09:45:02PM -0500
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
Well, I can't speak for the consequences of noapic (I've wondered as
much myself), but I know that there's been a problem with SMP 2.4
kernels (even the 2.4 test kernels) and USB running on VIA chipsets for
a while now. I'm told by the linux-usb maintainers that it's a problem
with the PCI IRQ routing for the VIA chipsets, but I've been unable to
get anyone who knows about this to do anything (and I've been asking for
a while). Alas, since this stuff is beyond me, I just accept the fact
that it'll probably always be broke.
pete
On Mon, 12 Mar 2001, David DeGeorge wrote:
> I am running 2.4.2 as obtained from redhat, but I have experienced the same
> problems with a kernel compiled from the 2.4.2 sources at kernel.org.
> I am experiencing troubles with enabling MPS 1.4 and USB. I have an ABIT VP6
> motherboard with two stock 733MHz PIIIs.
> If I set MPS1.1 in the bios then my IOmega Photoshow usb zip drive works, the
> usb interrupt appears on irq 9 and after a day or two I experience a hard
> (sysreq doesn't work) lock. It seems usb related since doing usb things i.e.
> mounting the drive sometimes cause the lock.
> If I set MPS1.4 in the bios then the usb interrupt appears on irq 19, whose
> count is alway zero, and the zip drive doesn't get registered. If give the
> noapic command line then things appear to work, irq=9,don't know about the
> hard locks, but booting seems much slower. Of course I can provide much more
> information but I wonder is this a common problem and what are the
> consequences of the noapic command?
> David
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-03-13 5:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 2:45 APIC usb MPS 1.4 and the 2.4.2 kernel David DeGeorge
2001-03-13 5:25 ` Pete Toscano [this message]
2001-03-13 11:59 ` Helge Hafting
2001-03-13 17:28 ` Greg KH
2001-03-13 17:49 ` Pete Toscano
2001-03-13 18:12 ` Greg KH
2001-03-13 20:51 ` Stephen Wille Padnos
2001-03-14 4:03 ` John R Lenton
2001-03-13 19:25 ` Juha Saarinen
2001-03-13 23:31 ` Pete Toscano
2001-03-13 23:48 ` Juha Saarinen
2001-03-13 22:51 ` idalton
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=20010313002513.A1664@bubba.toscano.org \
--to=pete.lkml@toscano.org \
--cc=dld@degeorge.org \
--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