Summary: | latest d-r-t has regular X crashes | ||
---|---|---|---|
Product: | DRI | Reporter: | Aidan Marks <aidan> |
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | XOrg git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Aidan Marks
2010-07-10 06:14:46 UTC
Did you update any other components as well (xserver, ddx, libpixman, etc.)? yes. i updated git libdrm/mesa/ddx also. so I went back to an older rc3+ d-r-t kernel and ran it for 24 hours, no crashes. booted back to d-r-t git head and didn't start firefox this time, just started a nxclient session and within 10 seconds I get this X crash: Backtrace: [ 125.117] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a1358] [ 125.117] 1: /usr/bin/X (0x400000+0x636f9) [0x4636f9] [ 125.117] 2: /lib/libpthread.so.0 (0x7f365b498000+0xf120) [0x7f365b4a7120] [ 125.117] 3: /lib/libc.so.6 (memcpy+0x15b) [0x7f3659bc61fb] [ 125.117] 4: /usr/lib64/xorg/modules/libfb.so (fbBlt+0x100) [0x7f3657b2e3b0] [ 125.117] 5: /usr/lib64/xorg/modules/libfb.so (fbBltStip+0x40) [0x7f3657b2f0e0] [ 125.117] 6: /usr/lib64/xorg/modules/libfb.so (fbPutZImage+0x17e) [0x7f3657b3369e] [ 125.117] 7: /usr/lib64/xorg/modules/libexa.so (0x7f3657908000+0x11a3e) [0x7f3657919a3e] [ 125.117] 8: /usr/lib64/xorg/modules/libexa.so (0x7f3657908000+0x7fb7) [0x7f365790ffb7] [ 125.117] 9: /usr/bin/X (0x400000+0xd704c) [0x4d704c] [ 125.117] 10: /usr/bin/X (0x400000+0xb50fd) [0x4b50fd] [ 125.117] 11: /usr/bin/X (0x400000+0xb6055) [0x4b6055] [ 125.117] 12: /usr/bin/X (0x400000+0x2f5ec) [0x42f5ec] [ 125.117] 13: /usr/bin/X (0x400000+0x24de5) [0x424de5] [ 125.117] 14: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f3659b63bbd] [ 125.117] 15: /usr/bin/X (0x400000+0x24999) [0x424999] [ 125.117] Bus error at address 0x7f3652217000 [ 125.118] Fatal server error: [ 125.118] Caught signal 7 (Bus error). Server aborting Can you bisect what commit is problematic? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/139. |
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.