Bug 814869
Summary: | infinite loop in synaptics driver | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karel Volný <kvolny> |
Component: | xorg-x11-server | Assignee: | Peter Hutterer <peter.hutterer> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | peter.hutterer, xgl-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-29 10:37:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Karel Volný
2012-04-20 21:45:12 UTC
appears to be list corruption in the server (In reply to comment #1) > appears to be list corruption in the server thanks for the initial inspection any hints what info from the running system would be interesting if that happens again? (I've killed the process with SIGABRT, hoping that it will dump core and re-reporting this with abrt-gui will provide more info, but it hasn't appeared on the list of crashes after restart ...) Please give xorg-x11-drv-synaptics-1.5.99.904-1 a try. It has a time-related fix that may trigger this bug. bit of a long shot, but worth testing anyway http://koji.fedoraproject.org/koji/buildinfo?buildID=315674 actually, this really looks like list corruption, currently waiting for some feedback on http://patchwork.freedesktop.org/patch/10100/ ok, I've updated the driver if I understand the possible nature of the bug, I'm pretty surprised that I saw this only on that one particular machine, and that it happened so often ... just fyi, you'll need the server update (not yet pushed out) to fix this, the driver had no hand it it after all (that patch is for the server alone). as for the why so often but only on one machine: the timer is set on every touchpad input event. so this code has a potential to corrupt very often, but still needs to interrupt some other code in one specific section. the backtrace shows the intel driver, so you're likely reliant on that as well, and there only since 2.18.0. after exceptionally long time without a hang, it happened again - see the backtrace below, it looks almost the same so I can confirm that the driver(s) update is not enough; now there is: xorg-x11-server-Xorg-1.12.0-2.fc17.x86_64 xorg-x11-drv-synaptics-1.6.0-1.fc17.x86_64 xorg-x11-drv-intel-2.19.0-1.fc17.x86_64 (gdb) bt full #0 0x0000000000461f97 in TimerSet (timer=0x267c980, flags=flags@entry=0, millis=millis@entry=1000000000, func=func@entry=0x7f8eb108ae70 <timerFunc>, arg=arg@entry=0x25ee430) at WaitFor.c:446 prev = 0x2671d60 now = 23396280 #1 0x00007f8eb108ae59 in ReadInput (pInfo=0x25ee430) at synaptics.c:1684 priv = 0x267c5c0 hw = 0x2680dc0 delay = 1000000000 newDelay = 1 #2 0x00000000004802f7 in xf86SigioReadInput (fd=<optimized out>, closure=0x25ee430) at xf86Events.c:298 errno_save = 11 pInfo = 0x25ee430 #3 0x00000000004a4490 in xf86SIGIO (sig=<optimized out>) at ../shared/sigio.c:109 i = <optimized out> ready = {fds_bits = {65536, 0 <repeats 15 times>}} to = {tv_sec = 0, tv_usec = 0} save_errno = 11 r = 1 #4 <signal handler called> No symbol table info available. #5 0x0000000000461fe5 in TimerSet (timer=0x2671d60, flags=flags@entry=0, millis=23399112, millis@entry=3000, func=func@entry=0x7f8eb315ed70 <intel_cache_expire>, arg=arg@entry=0x20dbee0) at WaitFor.c:477 prev = 0x2671d60 now = 23396112 #6 0x00007f8eb31609ff in intel_flush_rendering (intel=0x20dbee0) at intel_uxa.c:979 No locals. #7 intel_uxa_block_handler (intel=intel@entry=0x20dbee0) at intel_uxa.c:1003 No locals. #8 0x00007f8eb315d03e in I830BlockHandler (i=<optimized out>, blockData=<optimized out>, pTimeout=<optimized out>, pReadmask=<optimized out>) at intel_driver.c:753 screen = 0x20ecc90 scrn = <optimized out> intel = 0x20dbee0 #9 0x000000000043812a in BlockHandler (pTimeout=pTimeout@entry=0x7fffd74ef088, pReadmask=pReadmask@entry=0x7de500) at dixutils.c:392 i = <optimized out> j = <optimized out> #10 0x000000000046227c in WaitForSomething (pClientsReady=pClientsReady@entry=0x268b860) at WaitFor.c:219 i = <optimized out> waittime = {tv_sec = 2, tv_usec = 896000} wt = 0x7fffd74ef090 timeout = <optimized out> clientsReadable = {fds_bits = {0 <repeats 16 times>}} clientsWritable = {fds_bits = {34524304, 37703952, 48563472, 48563476, 37773192, 140250855845305, 37703952, 140250866648623, 48563560, 5244799, 0, 37775184, 37775184, 48563472, 37773192, 140250884482313}} selecterr = <optimized out> nready = 0 devicesReadable = {fds_bits = {34506592, 34524304, 0, 34524304, 34521280, 48563472, 8194080, 1073741826, 893, 5085704, 50236400, 0, 63369105, 4542626, 63369105, 50236400}} now = <optimized out> someReady = <optimized out> #11 0x0000000000434061 in Dispatch () at dispatch.c:366 clientReady = 0x268b860 result = <optimized out> client = <optimized out> nready = <optimized out> icheck = 0x7dde70 start_tick = <optimized out> #12 0x00000000004233e5 in main (argc=9, argv=0x7fffd74ef498, envp=<optimized out>) at main.c:287 i = <optimized out> alwaysCheckForInput = {0, 1} xorg-x11-server-1.12.0-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/xorg-x11-server-1.12.0-5.fc17 Package xorg-x11-server-1.12.0-5.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xorg-x11-server-1.12.0-5.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7836/xorg-x11-server-1.12.0-5.fc17 then log in and leave karma (feedback). xorg-x11-server-1.12.0-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |