[hardy]psmouse.c kernel panic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: linux-image-
Laptop: Dell Latitude D430
Kernel: Linux serenity 2.6.24-12-generic #1 SMP Wed Mar 12 22:31:43 UTC 2008 x86_64 GNU/Linux
Ubuntu Version: 8.04 Beta 1
Suspected Problem Location: Kernel module - psmouse
This bug is similar to 189814 (https:/
Mar 27 19:19:03 serenity kernel: [ 106.661044] psmouse.c: GlidePoint at isa0060/
Mar 27 19:19:05 serenity kernel: [ 107.810508] psmouse.c: resync failed, issuing reconnect request
Mar 27 19:19:07 serenity kernel: [ 108.284041] input: PS/2 Generic Mouse as /devices/
Mar 27 19:19:08 serenity kernel: [ 108.430153] input: PS/2 Mouse as /devices/
Mar 27 19:19:08 serenity kernel: [ 108.501732] input: AlpsPS/2 ALPS GlidePoint as /devices/
Mar 27 19:19:50 serenity kernel: [ 123.609475] input: PS/2 Mouse as /devices/
Mar 27 19:19:50 serenity kernel: [ 123.657255] input: AlpsPS/2 ALPS GlidePoint as /devices/
If you remove powernowd, the problem goes away. If you rmmod psmouse, then modprobe it after gdm has started, the problem never appears. I will try and get some Kernel debug and paste it in this bug report, but when the Kernel panics it does not log the panic to any of the logs (I have only seen the actual Kernel panic error message twice), when I had a terminal up but still X still running.
If the Kernel doesn't panic, the mouse is just very slow and jerky, almost certainly related to the dynamic CPU scaling that powernowd does on battery power. While removing and re-inserting the psmouse module is an acceptable interim solution, its certainly not a good long term one, as sometimes I don't even get a chance to do so before the Kernel panics!
Confirmed that 7.10 and custom Kernel (2.6.24.4) with psmouse driver compiled in the Kernel doesn't have the problem.
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Hi Dave,
Would you be able to take a digital photo of the kernel panic you see? Also, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.
* cat /proc/version_ signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
For more information regarding the kernel team bug policy, please refer to https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks again and we appreciate your help and feedback.