Bug 12254
| Summary: | oops in alps_process_byte/psmouse_interrupt with AlpsPS/2 after station undock/redock | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Cyril Brulebois (kibi) |
| Component: | Input Devices | Assignee: | drivers_input-devices |
| Status: | CLOSED UNREPRODUCIBLE | ||
| Severity: | normal | CC: | alan, chris, dmitry.torokhov, georgmueller, mail |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.31 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
2 full traces
Kernel config Debug info 2 * Debug info |
||
|
Description
Cyril Brulebois
2008-12-19 12:32:05 UTC
Created attachment 19381 [details]
2 full traces
Created attachment 19382 [details]
Kernel config
Some bits about the system:
2 * Intel(R) Core(TM)2 Duo CPU U7700 @ 1.33GHz
with an x86_64 userland.
Cyril, Any chance you could enable debug (echo 1 > /sys/module/i8042/parameters/debug) before triggering the oops so I could see the data stream leading to it. Dont type any passwords after you enabled debug though. Thanks. Created attachment 19427 [details]
Debug info
Unfortunately, I can't affirm it's the very same oops since I got nothing logged through netconsole, or on the local FS. I'll try and get another trace later today. Created attachment 19431 [details]
2 * Debug info
As you can see here, I'd been using the machine for some hours, turned on debug info, and tried to dedock. From that point, I couldn't interact with the box anymore, either with the mouse or with the keyboard, and I don't think it OOPS'd (the capslock, numlock, etc. leds didn't go blinking), and I didn't get anything through netconsole.
Then, I rebooted and tried again. This time, leds went blinking, but I still haven't any trace of OOPS in my log, I can only see the last module that got loaded there (drm initialized upon X startup).
Not sure whether enabling debug info is sufficient to “hide”/suppress the oops trace…
I have the same issue with 2.6.27.7 (opensuse kernel, diff of alps.c is the same, so I hope this is not an issue) on a Dell Latitude D820, easily reproducible. I do not have to redock, just undock and use the touchpad. My OOPS/panic can be found at https://bugzilla.novell.com/attachment.cgi?id=254581 I will try to enable debug and do the dump as described in comment #3 I have enabled debug (echo 1 > /sys/module/i8042/parameters/debug), but the only output generated by this module is the panic blink right after the panic (about 15 seconds after I enabled debug, I used the touchpad during the whole time): drivers/input/serio/i8042.c: ed -> i8042 (panic blink) [34802] drivers/input/serio/i8042.c: 05 -> i8042 (panic blink) [34802] drivers/input/serio/i8042.c: ed -> i8042 (panic blink) [34802] drivers/input/serio/i8042.c: 00 -> i8042 (panic blink) [34802] ... I don't see any input from the touchpad. As mentioned in my bug report @Novell (https://bugzilla.novell.com/show_bug.cgi?id=445840), then under X11, the touchpad loses it's special functions like tapping, scrolling right after the undock. After some 'moves' the panic occurs. I tried 2.6.31 and the system still panics. Does any one have further suggestions how to debug this problem? Hmm, it seems to work here on D630. Could you please enable debug but also disable panic blinking (echo 0 > /sys/module/i8042/parameters/panicblink) and make it oops again? Thanks. JFTR, I no longer have access to this hardware, sorry. |