Re: External USB2 HDD affects speed hda

[David Brownell]

On Thursday 02 June 2005 4:56 pm, Rene Herman wrote:
> Grant Coady wrote:
> 
> > root@sempro:~# cat /sys/class/usb_host/usb1/registers
> > bus pci, device 0000:00:10.4 (driver 10 Dec 2004)
> > EHCI 1.00, hcd state 1
> > structural params 0x00004208
> > capability params 0x00006872
> > status a008 Async Recl FLR
> > command 010009 (park)=0 ithresh=1 period=256 RUN
> 
> David, did I understand correctly that the Async status bit should not 
> be set without the Async command bit, period? Or was that just in my 
> case, with everything idle/off/disconnected?

It's like this:  turn on the command bit, then after a while the status
bit changes and shows the command took effect.  Turn off the command bit,
ditto.  And if everything is idle/disconnected, nothing should be
turning the bit on ... both bits should stay off at all times.

The driver needs to avoid doing certain things while the chip is in
the middle of activating or de-activating one of the schedules, so
it checks to see whether the bits agree.  If they disagree, the chip
hasn't finished the last enable/disable command.


> If first, then I'm happy that it's not just me ...
> 
> > 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
> 
> ... although maybe still just VIA.

Maybe.  Thing is, normally it should take just no more than a
millisecond or two for the command to take effect.  So the fact
that either of you can consistently see something happening there
is pretty strange.  Something would seem to be turning the async
schedule on/off a lot.  The driver isn't _supposed_ to do that.
But then, neither is the chip (without the driver telling it to
do so) ... something's being annoying there.


> 
> > 2.6.12-rc5-mm2a third run
> 
> [ snip, no Async or Recl status bit ]
> 
> > irq normal 8184 err 0 reclaim 5387 (lost 82)
> 
> No idea about those. Not seeing lost interrupts here, even after 
> generating quite some traffic.

The "lost" interrupts are cases where the VIA hardware (it's never
been seen by me on any other hardware) is supposed to issue an IRQ
as part of the reclaim process, but doesn't.  

- Dave

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