Bug 600754 - Xorg freezes on a Lenovo T410
Summary: Xorg freezes on a Lenovo T410
Keywords:
Status: CLOSED DUPLICATE of bug 596330
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 13
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-05 21:45 UTC by Sebastian Verderber
Modified: 2018-04-11 18:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-08 22:28:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg logfile taken after reboot (106.39 KB, text/plain)
2010-06-05 21:45 UTC, Sebastian Verderber
no flags Details

Description Sebastian Verderber 2010-06-05 21:45:25 UTC
Created attachment 421498 [details]
Xorg logfile taken after reboot

Description of problem:

Every once in a while, X freezes - meaning, i can still move the mouse but i can'T click anywhere and the keyboard also doesn't respond. i can still ssh in, where top gives me Xorg at 100% cpu load (meaning 1 core). i did a reboot and took the Xorg.0.log.old (attached). the main problem seems to be this line:

[ 21178.584] [mi] EQ overflowing. The server is probably stuck in an infinite loop.

dmesg gave me something about a btusb error, unfortunately i didn't save it and the  dmesg log was gone after the reboot :-(

the freezes used to occur 2-3 times a day but seemed to stop after i moved from firefox to chrome (and they did for about a week), but now here we go again... (chrome was running in background).

Version-Release number of selected component (if applicable):


How reproducible:
unfortunately, i don't know.


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Xorg uses 100% cpu on one core and freezes

Expected results:


Additional info:

Comment 1 Matěj Cepl 2010-06-08 13:25:33 UTC
Backtrace:
[ 21178.668] 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49e708]
[ 21178.668] 1: /usr/bin/Xorg (mieqEnqueue+0x1f4) [0x49e0b4]
[ 21178.668] 2: /usr/bin/Xorg (xf86PostMotionEventP+0xc4) [0x477e24]
[ 21178.669] 3: /usr/bin/Xorg (xf86PostMotionEvent+0xa9) [0x477fc9]
[ 21178.669] 4: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f090a94e000+0x38e5) [0x7f090a9518e5]
[ 21178.669] 5: /usr/lib64/xorg/modules/input/synaptics_drv.so (0x7f090a94e000+0x5cc8) [0x7f090a953cc8]
[ 21178.669] 6: /usr/bin/Xorg (0x400000+0x6aae7) [0x46aae7]
[ 21178.669] 7: /usr/bin/Xorg (0x400000+0x117b43) [0x517b43]
[ 21178.669] 8: /lib64/libc.so.6 (0x7f090dcc6000+0x32a20) [0x7f090dcf8a20]
[ 21178.669] 9: /lib64/libc.so.6 (ioctl+0x7) [0x7f090dd9f597]
[ 21178.669] 10: /usr/lib64/libdrm.so.2 (drmIoctl+0x28) [0x342dc03388]
[ 21178.669] 11: /usr/lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x342dc0360b]
[ 21178.669] 12: /usr/lib64/libdrm_nouveau.so.1 (0x7f090c7b4000+0x2dfd) [0x7f090c7b6dfd]
[ 21178.669] 13: /usr/lib64/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xfe) [0x7f090c7b6fee]
[ 21178.669] 14: /usr/lib64/libdrm_nouveau.so.1 (0x7f090c7b4000+0x207a) [0x7f090c7b607a]
[ 21178.669] 15: /usr/lib64/libdrm_nouveau.so.1 (nouveau_pushbuf_flush+0x190) [0x7f090c7b6450]
[ 21178.669] 16: /usr/lib64/xorg/modules/libexa.so (0x7f090b918000+0x9645) [0x7f090b921645]
[ 21178.669] 17: /usr/lib64/xorg/modules/libexa.so (0x7f090b918000+0xa1ea) [0x7f090b9221ea]
[ 21178.670] 18: /usr/bin/Xorg (0x400000+0xd2b0b) [0x4d2b0b]
[ 21178.670] 19: /usr/lib64/xorg/modules/libexa.so (0x7f090b918000+0xb44d) [0x7f090b92344d]
[ 21178.670] 20: /usr/bin/Xorg (0x400000+0xd250e) [0x4d250e]
[ 21178.670] 21: /usr/bin/Xorg (0x400000+0xcc8ae) [0x4cc8ae]
[ 21178.670] 22: /usr/bin/Xorg (0x400000+0x2c32c) [0x42c32c]
[ 21178.670] 23: /usr/bin/Xorg (0x400000+0x219ca) [0x4219ca]
[ 21178.670] 24: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f090dce4c5d]
[ 21178.670] 25: /usr/bin/Xorg (0x400000+0x21579) [0x421579]

Comment 2 Ben Skeggs 2010-06-08 22:28:22 UTC

*** This bug has been marked as a duplicate of bug 596330 ***


Note You need to log in before you can comment on or make changes to this bug.