Hi Dâniel
From http://marc.info/?l=linux-usb&m=139560312908515, I'm glad to see that
I'm not the trouble maker.
Since this bug cannot be reproduced in each boot, I suggest you stick to
the bisect method and write a script to do valid bisecting. The script
should be able to boot the kernel, say, 5 times, and grep the boot log or
dmesg to determine if any of the 5 attempts triggers the bug.
Deng-Cheng
---------------------------------------------------------------------------
*From:* Alan Stern <mailto:stern@xxxxxxxxxxxxxxxxxxx>
*Sent:* Saturday, March 22, 2014 8:07AM
*To:* Dâniel Fraga <mailto:fragabr@xxxxxxxxx>
*Cc:* dengcheng.zhu <mailto:dengcheng.zhu@xxxxxxxxxx>, James Hogan
<mailto:james.hogan@xxxxxxxxxx>, USB list <mailto:linux-usb@xxxxxxxxxxxxxxx>
*Subject:* Re: Regression cause by commit f1125f81 (from Deng-Cheng Zhu)
Messages like this should always be sent to the linux-usb mailing list.
On Sat, 22 Mar 2014, Dâniel Fraga wrote:
Hi! I posted this bug and it seems your commit caused the
regression:
https://bugzilla.kernel.org/show_bug.cgi?id=72611
Can you take a look?
Thank you!
Ps: I put James and Alan on CC just in case.
I don't see how that particular commit could cause your problem. The
code changed by the commit is used only in debugging. Are you certain
you found the correct commit?
To track the bug further, you should turn on CONFIG_USB_DEBUG and post
the dmesg log showing what happens when the mouse gets stuck. You also
should post a usbmon trace (see Documentation/usb/usbmon.txt).
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
