what mobo/chipset are you using? i and a bunch of other people have
been having very similar problems with this and the 2.4.0-test kernels.
we all use the tyan tiger 133 mobo with the apollo pro 133a chipset. i
believe that the 2.2.18 usb support has been pulled from the 2.4.0-test
source, so i'm not surprised to be seeing this.
on the linux-usb list, i was talking with johannes erdfel and doing some
checks for him. he thinks that it's a pci irq problem as the usb
controller (uhci and usb-uhci) don't get any interrupts on smp-enabled
kernels when apic is enabled. i've written martin mares about this (but
to the email address listed on his web page -- not mj@suse.cz, yet -- so
it probably got dropped into /dev/null) and i'm eager to hear his
opinion on matters. i'll bet that now that the problem has moved into
the 2.2 line, we'll be seeing more noise about it.
laramie, try disabling apic at the lilo prompt (add "noapic" after your
kernel image's name) and see if that helps.
pete
On Tue, 12 Dec 2000, Greg KH wrote:
> On Tue, Dec 12, 2000 at 02:07:59PM -0000, Laramie Leavitt wrote:
> > [1.] One line summary of the problem:
> > USB (MS Intellimouse specifically) does not work with SMP kernel 2.2.18.
> >
> > [2.] Full description of the problem/report:
> > When trying to install a Microsoft Intellimouse Explorer (USB)
> > to a SMP kernel, I get the following error multiple times:
> >
> > usb.c: USB device not accepting new address (error=-110)
>
> What's your BIOS setting for MSR?
>
> And how about the contents of /proc/interrupts?
>
> This is a case of when the usb code isn't getting the hardware interrupt
> delivered properly.
>
> thanks,
>
> greg k-h
-- Pete Toscano p:sigsegv@psinet.com w:pete@research.netsol.com GPG fingerprint: D8F5 A087 9A4C 56BB 8F78 B29C 1FF0 1BA7 9008 2736
This archive was generated by hypermail 2b29 : Fri Dec 15 2000 - 21:00:25 EST