Jonathan Nieder a écrit :
> Thanks, that's interesting. If you have time to test connecting the
> old keyboard and mouse through a hub, that would still be useful.
Ok, I am going to ask for a hub to my friends and to test my hardware
through it.
Sebastien
--
Sébastien Dinot, sebastien.di...@fr
Hi Sébastien,
Sébastien Dinot wrote:
> Alan Stern a écrit :
>> In addition to what Sarah said, it's possible that your problem is
>> related to the fact that the keyboard and mouse operate at low speed.
>> If you connected them through a hub then that hub would communicate
>> with the internal hu
Hi,
Alan Stern a écrit :
> In addition to what Sarah said, it's possible that your problem is
> related to the fact that the keyboard and mouse operate at low speed.
> If you connected them through a hub then that hub would communicate
> with the internal hub at high speed, not low speed.
I had n
On Thu, 4 Oct 2012, Sébastien Dinot wrote:
> Alan Stern a écrit :
> > The log file shows lots and lots of low-level communication errors.
> > They could be caused by bad cabling or by bad USB hardware in your
> > computer. It's unlikely that they were caused by the mouse or
> > keyboard, because t
On Thu, Oct 04, 2012 at 11:36:06PM +0200, Sébastien Dinot wrote:
> Alan Stern a écrit :
> > The log file shows lots and lots of low-level communication errors.
> > They could be caused by bad cabling or by bad USB hardware in your
> > computer. It's unlikely that they were caused by the mouse or
>
Alan Stern a écrit :
> The log file shows lots and lots of low-level communication errors.
> They could be caused by bad cabling or by bad USB hardware in your
> computer. It's unlikely that they were caused by the mouse or
> keyboard, because the log shows errors for both of them starting at
> exa
On Thu, 4 Oct 2012, Sébastien Dinot wrote:
> Hi,
>
> Alan Stern a écrit :
> > Please build a kernel with CONFIG_USB_DEBUG enabled.
>
> Done (3.6.0+ kernel)
>
> > When a hang occurs, get a list of hang tasks (Alt-SysRq-w probably
> > won't work, but "echo w >/proc/sysrq-trigger" from a network l
On Wed, 3 Oct 2012 sebastien.di...@free.fr wrote:
> Hi,
>
> I am encountering random keyboard and mouse freezes which can only be
> resolved by a hard reset (by pushing the power switch of the computer
> case).
> The mouse and keyboard are both USB devices and it seems that the bug
> is coming f
Hi,
I am encountering random keyboard and mouse freezes which can only be resolved
by a hard reset (by pushing the power switch of the computer case).
I have this frequent and irritating issue with two differents Ivy Bridge
platforms:
1. Processor: Intel Core i5 3450 (IGP HD 2500)
Mother
Sébastien Dinot wrote:
> Good point! Keyboard and mouse work again after these commands.
Yay.
Ok, one more test and then we should take this upstream: if you set
the usbcore.autosuspend parameter to -1, does that change anything?
# modprobe -r ehci_hcd; # or unplug mouse
# echo
Jonathan Nieder a écrit :
> Does unloading and reloading the USB driver ("modprobe -r ehci_hcd &&
> modprobe ehci_hcd") have any effect?
Good point! Keyboard and mouse work again after these commands.
Once again, I found the following event in the kern.log file:
-
Jonathan Nieder a écrit :
> Presumably removing and replugging the mouse doesn't help.
No.
> Does unloading and reloading the USB driver ("modprobe -r ehci_hcd &&
> modprobe ehci_hcd") have any effect?
I never tried it. I will test it the next time.
> Did these machines always behave this way,
Hi Sébastien,
Sébastien Dinot wrote:
> I am encountering random keyboard and mouse freezes which can only be
> resolved by a hard reset (push the power button on the computer case).
Thanks for a clear report. Presumably removing and replugging the
mouse doesn't help. Does unloading and reloadi
13 matches
Mail list logo
