I've tried; it wasn't accepted. The patch below should be more acceptable
to the maintainer. Try it instead of the other one; it ought to get rid
of all those error messages showing up in the log as well as fixing the
mouse problem. That is, it won't prevent the actual errors from occurring
I've dropped Helmut Zeisel as cc: and will send him notice a when the
issue is resolved. He can read our conversation in the mailing list
archive anyway.
I've tried; it wasn't accepted. The patch below should be more acceptable
to the maintainer. Try it instead of the other one; it ought to
On Thu, 22 Dec 2005, Willi Mann wrote:
- Now see what's happening when I unplug the mouse fast:
Dec 21 14:40:44 wmiwilli kernel: drivers/usb/input/hid-core.c: input irq
status -84 received
Dec 21 14:40:44 wmiwilli last message repeated 2 times
...
- When I unplug it slowly:
Dec 21
That particular error generally means that something is interfering with
the USB data transmission. It could be a poor cable connection, or it
could be the mouse sending a bad signal, or it could be some sort of
outside electromagnetic interference.
I would like to test with other USB
On Wed, 21 Dec 2005, Willi Mann wrote:
By the way, it looks like you don't need the entire patch. Just the parts
the remove the lines saying
case -EILSEQ:
should be enough to help.
confirmed. What's needed to get that into the offical kernel releases?
I've tried; it wasn't
Yes. Read Documentation/usb/usbmon.txt in the kernel source.
Ok, here is what I did:
cat 2t
- minimize the gnome-terminal
- surfed the web
- suddenly mouse died
- Strg + Alt + F1, Alt+ F7
- reopened the terminal
- marked the last 200 lines
- pasted in file
- grepped for the mouse identifier
On Sat, 17 Dec 2005, Willi Mann wrote:
Ok, here is what I did:
cat 2t
- minimize the gnome-terminal
- surfed the web
- suddenly mouse died
- Strg + Alt + F1, Alt+ F7
- reopened the terminal
- marked the last 200 lines
- pasted in file
- grepped for the mouse identifier 002:01
here are
Yes indeed. This looks very similar to the problem reported in
http://bugzilla.kernel.org/show_bug.cgi?id=4916
See especially comment #19.
It's possible that the patch adding an HID reset routine (the last
attachment in the bug report) will work for you. You might have to fiddle
with it
I now recreated the patch in a more usable way.
BTW:
Dec 17 20:50:30 wmiwilli kernel: mtrr: 0xe800,0x800 overlaps
existing 0xe800,0x100
Dec 17 21:01:25 wmiwilli kernel: drivers/usb/input/hid-core.c: input irq
status -84 received
Dec 17 21:25:43 wmiwilli kernel:
On Sat, 17 Dec 2005, Willi Mann wrote:
Yes indeed. This looks very similar to the problem reported in
http://bugzilla.kernel.org/show_bug.cgi?id=4916
See especially comment #19.
It's possible that the patch adding an HID reset routine (the last
attachment in the bug report)
On Sat, 17 Dec 2005, Willi Mann wrote:
There seems to be relation between mouse usage and the -84 signal: The
more I use the mouse the less it occurs.
That particular error generally means that something is interfering with
the USB data transmission. It could be a poor cable connection, or
To get more information, turn on USB verbose debugging (CONFIG_USB_DEBUG)
in the kernel configuration and rebuild the USB drivers. Post the kernel
or dmesg log showing what happens when the connection is lost.
I've used the debian source for that. They currently don't patch
anything
On Sun, 4 Dec 2005, Willi Mann wrote:
To get more information, turn on USB verbose debugging (CONFIG_USB_DEBUG)
in the kernel configuration and rebuild the USB drivers. Post the kernel
or dmesg log showing what happens when the connection is lost.
I've used the debian source for
On Thu, 1 Dec 2005, Willi Mann wrote:
I have already reported this bug in the Debian BTS with many details:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314954
I have now tested with a second logitech mouse attached.
Bus 004 Device 004: ID 04b4:6560 Cypress Semiconductor Corp.
14 matches
Mail list logo
