From: Johannes Erdfelt <johannes@erdfelt.com>
To: josh <skulcap@mammoth.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB problems since 2.4.2
Date: Tue, 24 Apr 2001 00:54:00 -0400 [thread overview]
Message-ID: <20010424005400.O12435@sventech.com> (raw)
In-Reply-To: <20010423230911.M12435@sventech.com> <Pine.LNX.4.20.0104232346140.15411-100000@www>
In-Reply-To: <Pine.LNX.4.20.0104232346140.15411-100000@www>; from josh on Mon, Apr 23, 2001 at 11:46:52PM -0500
On Mon, Apr 23, 2001, josh <skulcap@mammoth.org> wrote:
>
> > On Mon, Apr 23, 2001, josh <skulcap@mammoth.org> wrote:
> > > Kernel: 2.4.2 - latest (2.4.3-ac12)
> > > Platform: x86 on mangled Slack7.1
> > > Hardware: MSI 694D Pro-AR
> > > ( http://www.msicomputer.com/products/detail.asp?ProductID=150 )
> > >
> > > Problem: USB devices timeout on address assignment. Course thats with the
> > > non JE driver, with the JE driver the bus doesnt even say that anything
> > > gets connected.
> > >
> > > when any device is plugged in:
> > > *************************************
> > > hub.c: USB new device connect on bus1/1, assigned device number 4
> > > usb_control/bulk_msg: timeout
> > > usb.c: USB device not accepting new address=4 (error=-110)
> > > hub.c: USB new device connect on bus1/1, assigned device number 5
> > > usb_control/bulk_msg: timeout
> > > usb.c: USB device not accepting new address=5 (error=-110)
> > > *************************************
> >
> > Can you try booting your kernel with the "noapic" option and see if it
> > still happens?
>
> DING DING DING! that did the trick. Thnx!
It's less than optimal however. You have an IRQ routing problem with
your I/O APIC's it seems. A BIOS upgrade may fix this, but I don't know
if it will in your particular case.
"noapic" will make things work atleast, but everything will be sent to
one CPU (assuming you have more than one CPU :)
JE
prev parent reply other threads:[~2001-04-24 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 1:49 USB problems since 2.4.2 josh
2001-04-24 3:09 ` Johannes Erdfelt
2001-04-24 4:46 ` josh
2001-04-24 4:54 ` Johannes Erdfelt [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=20010424005400.O12435@sventech.com \
--to=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skulcap@mammoth.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