With the same config, in mm3, it works.
boot log for mm4 attached.
On Sat, May 03, 2003 at 03:55:12PM +0300, Andrei Ivanov wrote:
> usb 1-2: USB device not accepting new address=2 (error=-110)
> hub 1-0:0: new USB device on port 2, assigned address 3
> usb 1-2: USB device not accepting new address=3 (error=-110)
Hm, interrupts aren't getting to the usb host controller. Does this
work ok on the latest -bk tree for you?
thanks,
greg k-h
No, on bk11 it does the same thing.
On Sat, 3 May 2003, Greg KH wrote:
> On Sat, May 03, 2003 at 03:55:12PM +0300, Andrei Ivanov wrote:
> > usb 1-2: USB device not accepting new address=2 (error=-110)
> > hub 1-0:0: new USB device on port 2, assigned address 3
> > usb 1-2: USB device not accepting new address=3 (error=-110)
>
> Hm, interrupts aren't getting to the usb host controller. Does this
> work ok on the latest -bk tree for you?
>
> thanks,
>
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Sun, May 04, 2003 at 12:38:04PM +0300, Andrei Ivanov wrote:
>
>
> No, on bk11 it does the same thing.
Booting with "noapic" help any?
Or if this is a acpi based box, can you disable that?
thanks,
greg k-h