On Thu, 15 Feb 2007 [EMAIL PROTECTED] wrote:
> So I think ideally linux needs some way of coordinating ehci-hcd and
> powernow, so that the EHCI controller can be stopped temporarily while
> the processors are changing speed... I'm going to try to hack something
> to do that, just to verify that i
Greg KH wrote:
> On Wed, Feb 14, 2007 at 04:49:11PM -0600, [EMAIL PROTECTED] wrote:
>>
>> Hello... While running minor stress on a system, I'm seeing messages
>> like this quite frequently:
>
> What kernel version are you using?
>
2.6.20
>
>> It seems to me that ehci-hcd itself should perhaps
On Wed, 14 Feb 2007 [EMAIL PROTECTED] wrote:
> It seems to me that ehci-hcd itself should perhaps retry a transaction
> immediately--at least a couple of times--if it gets QTD_STS_MMF. If
> that is wrong for some reason, it might be nice if there was some way
> for hid-core (et al?) to know what'
On Wednesday 14 February 2007 2:49 pm, [EMAIL PROTECTED] wrote:
> I think this is happening because the EHCI controller is getting delayed
> trying reading main memory while the processors are changing speed (this
> is where the cpufreq/powernow stuff comes in). If this happens between
> the star
On Wed, Feb 14, 2007 at 04:49:11PM -0600, [EMAIL PROTECTED] wrote:
>
> Hello... While running minor stress on a system, I'm seeing messages
> like this quite frequently:
What kernel version are you using?
> usb 3-1.1: reset full speed USB device using ehci_hcd and address 5
>
> These messages a
Hello... While running minor stress on a system, I'm seeing messages
like this quite frequently:
usb 3-1.1: reset full speed USB device using ehci_hcd and address 5
These messages are occurring for all 4 of my low/full speed HID devices
that are connected to a USB2.0 hub (so all are using split
