Re: 2.4.17 usbnet usb.c: USB device not accepting new address

Johannes Erdfelt (johannes@erdfelt.com)
Mon, 7 Jan 2002 17:14:11 -0500


On Mon, Jan 07, 2002, Jörn Nettingsmeier <nettings@folkwang-hochschule.de> wrote:
> Johannes Erdfelt wrote:
> >
> > On Mon, Jan 07, 2002, Pete Zaitcev <zaitcev@redhat.com> wrote:
> > > > kernel: usb.c: USB device not accepting new address=6 (error=-110)
> > >
> > > And your /proc/interrupts is ... ?
> >
> > Almost definately > 0. He was getting hard CRC/Timeout's out of the HC.
>
> before plugging the ipaq in again:
>
> 19: 198150 198207 IO-APIC-level aic7xxx, eth0, usb-uhci
> NMI: 0 0
> LOC: 2554011 2553990
> ERR: 0
> MIS: 0
>
> after plugging in: (doing `cat interrupts` continuously)
>
> 19: 198178 198233 IO-APIC-level aic7xxx, eth0, usb-uhci
> NMI: 0 0
> LOC: 2555170 2555148
> ERR: 0
> MIS: 0
>
> 19: 198187 198241 IO-APIC-level aic7xxx, eth0, usb-uhci
> NMI: 0 0
> LOC: 2555323 2555301
> ERR: 0
> MIS: 0
>
> 19: 198192 198248 IO-APIC-level aic7xxx, eth0, usb-uhci
> NMI: 0 0
> LOC: 2555437 2555416
> ERR: 0
> MIS: 0
>
> 19: 198194 198250 IO-APIC-level aic7xxx, eth0, usb-uhci
> NMI: 0 0
> LOC: 2555515 2555494
> ERR: 0
> MIS: 0
>
> i just realized i might have an issue with shared irqs here. aic7xxx
> has my system disk, and eth0 is a realtek 8139too.o
> aic7xxx and usb are on-board, so there's nothing i can do against
> them sharing an interrupt. i might shuffle my nic around tomorrow,
> if you guys think that it makes a difference.

It shouldn't. It seems to be getting the interrupts correctly since we
saw the CRC/Timeo from the HC.

JE

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/