[Dropped John Stultz from the cc list as this doesn't seem to relate to
his changes.]
On Fri, 2012-04-27 at 15:30 +0200, Sven Hoexter wrote:
> On Fri, Apr 27, 2012 at 04:19:21AM +0100, Ben Hutchings wrote:
>
> Hi,
>
> > So it looks like in this case at least you're seeing a bug in USB error
> > recovery and not anything to do with timing using the TSC vs HPET.
>
> Ok, a few minutes ago I got aware of another system with the given
> symptoms with a SandyBridge CPU (E3-1220) and the same CallTrace.
>
>
> I'm now wondering what I could do to help to debug such issue
> further?
>
>
> All those Dell systems (R210 and R210 II) are equipped with DRAC
> KVM cards. They expose the input of the KVM Java applet as USB
> devices to the system. For at least one of the effected systems
> I'm pretty sure that nobody tried to use the KVM applet while
> that issue appearead but that doesn't mean anything.
> External USB devices were not connected to the systems.
>
> Kernel is linux-image-2.6.32-5-amd64 2.6.32-38
The description of an update for RHEL 6
<https://rhn.redhat.com/errata/RHSA-2012-0481.html> says:
"BZ#797205
Due to a bug in the hid_reset() function, a deadlock could occur
when a Dell iDRAC controller was reset. Consequently, its USB
keyboard or mouse device became unresponsive. A patch that fixes
the underlying code has been provided to address this bug and
the hangs no longer occur in the described scenario."
Could this possibly be the same bug?
Ben.
--
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.
Attachment:
signature.asc
Description: This is a digitally signed message part