hello
i am running sarge with kernel 2.6.9 on my laptop.
i was happy with kde 3.3 and all the fonction of my laptop working till i get my system freezed... The problem is that it hapen from time to time.


i have check /var/log/syslog and kern there were so large (about 140 Mo each)
i always have the same notification


when my usbmouse is plugged to the laptop

Dec 20 13:21:12 debian kernel: evbug.c: Event. Dev: usb-0000:00:11.2-1/input0, Type: 2, Code: 0, Value: 1
Dec 20 13:21:12 debian kernel: evbug.c: Event. Dev: usb-0000:00:11.2-1/input0, Type: 0, Code: 0, Value: 0
Dec 20 13:21:12 debian kernel: evbug.c: Event. Dev: usb-0000:00:11.2-1/input0, Type: 2, Code: 0, Value: 1
Dec 20 13:21:12 debian kernel: evbug.c: Event. Dev: usb-0000:00:11.2-1/input0, Type: 2, Code: 1, Value: 1
Dec 20 13:21:12 debian kernel: evbug.c: Event. Dev: usb-0000:00:11.2-1/input0, Type: 0, Code: 0, Value: 0
Dec 20 13:21:12 debian kernel: evbug.c: Event. Dev: usb-0000:00:11.2-1/input0, Type: 2, Code: 0, Value: 1


when i unplugged it i have also lot of notification in kern.log and syslog and my system also freezed...

Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 2, Code: 1, Value: 1
Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 0, Code: 0, Value: 0
Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 2, Code: 1, Value: 1
Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 0, Code: 0, Value: 0
Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 2, Code: 1, Value: 2
Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 0, Code: 0, Value: 0
Dec 20 21:05:59 debian kernel: evbug.c: Event. Dev: isa0060/serio4/input0, Type: 2, Code: 0, Value: -1


i dont find anything with google about this problem
any idea ? two week that i try to solve this problem, i am so exostied...

thanks
nico


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Reply via email to