| Summary: | touching touchpad after resume crashes X | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Mike Kelly <pioto> | ||||
| Component: | Input/synaptics | Assignee: | Peter Hutterer <peter.hutterer> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | Keywords: | NEEDINFO | ||||
| Version: | unspecified | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
I can't reproduce this by VT switching. Does the laptop need to be resumed to trigger this bug? also, suspend or hibernate? (I noticed tuxonice in the kernel string) (In reply to comment #1) > I can't reproduce this by VT switching. Does the laptop need to be resumed to > trigger this bug? also, suspend or hibernate? (I noticed tuxonice in the kernel > string) Plain old VT switching is not a problem. I need to suspend to RAM, at least, to reproduce this. I haven't been using the tuxonice stuff recently for other reasons, so I forget if it also exacerbates this. same thing though, i can't seem to reproduce this. my testing was: - suspend, resume, move touchpad - suspend, resume, vt switch away and back, move touchpad - suspend from TTY, resume, vt switch to server, move touchpad neither causes a crash here. what is your exact test case? (In reply to comment #3) > - suspend, resume, move touchpad That's all I need to do: - Close the lid, which does a `hibernate-ram`. - Open the lid, and press some key to wake up. - Touch the touchpad. The mouse cursor doesn't seem to move, and within a few seconds, X has crashed. I can just do a startx again and things are fine. Or, if I switch to a text console and back before resuming, things are fine. I'm also using an Intel graphics chipset with KMS, though I don't know if that's really related to this. What would be the recommended procedure for me to generate a more useful backtrace? (Since it does appear that it is segfaulting) And, is there any other information about this system would would be useful and relevant? (lspci, dmidecode, etc?) Ideally you could locate a second machine, then ssh in after resume (before touching the pad) and attach gdb to the Xorg process. then, when it crashes do a backtrace including printing some of the variables that may be involved in the crash and debug the output here. If this doesn't work it's down to sprinkling printfs all over the place to figure out what's going on. Hrm, I've reinstalled my system, and this no longer seems to be reproducible. Thanks anyways. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 28458 [details] Xorg.0.log When I resume my laptop, I can use the keyboard fine, and if I switch to a text console and back, then I can use my mouse. But, if I touch the touchpad first, then X crashes: I've attached my Xorg.0.log