Subject: Re: USB stack needs early review (Re: Someone should fix our USB stack...)
To: Hans Petter Selasky <hselasky@c2i.net>
From: Cherry G. Mathew <cherry.g.mathew@gmail.com>
List: tech-kern
Date: 03/19/2007 08:36:29
On 3/18/07, Hans Petter Selasky <hselasky@c2i.net> wrote:
> I don't know. You would have to try the new USB stack.
>
> What kind of processor are you using ?
>
cpu0 at mainbus0 apid 0: (boot processor)
cpu0: Intel Pentium M (Dothan) (686-class), 1099.92 MHz, id 0x6d8
cpu0: features afe9fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features afe9fbff<PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX>
cpu0: features afe9fbff<FXSR,SSE,SSE2,SS,TM,SBF>
cpu0: features2 180<EST,TM2>
cpu0: "Intel(R) Pentium(R) M processor 1.10GHz"
cpu0: I-cache 32 KB 64B/line 8-way, D-cache 32 KB 64B/line 8-way
cpu0: L2 cache 2 MB 64B/line 8-way
cpu0: using thermal monitor 2
cpu0: Enhanced SpeedStep (908 mV) 1100 MHz
cpu0: Enhanced SpeedStep frequencies available (MHz): 1100 1000 900 800 600
cpu0: calibrating local timer
cpu0: apic clock running at 99 MHz
cpu0: 64 page colors
cpu0: kstack at 0xcbf10000 for 12288 bytes
cpu0: idle pcb at 0xcbf10000, idle sp at 0xcbf12f98
> >
> > A USB2.0 stick works properly with uhub3 -> ehci0
> >
> > I disabled ehci and tried again, and got the same error for both the
> > USB2 stick and the USB1 stick which caused the above dmesg.
> >
> > Any pointers on where to start debugging ?
>
> Maybe it is an ACPI interrupt issue. Try disabling apic.
>
I did, but the same error cropped up. Is our current USB code shared
with the other BSDs ?
--
~Cherry