Bug#757982: xserver segmentation fault
On Thu, Sep 11, 2014 at 21:17:34 +0200, repron wrote: Dnia 9 września 2014 5:13 Michel Dänzer mic...@daenzer.net napisał(a): On 08.09.2014 20:32, repron wrote: Last several freezes of Xorg, coused that Xorg.o.log file ended suddenly, without SIGSEGV. I am still trying to reproduce exactly the same state of freeze as mentioned in the bug. Of course it can be a bug in kernel or somewhere else but if I had uninstalled packages xserver-xorg-video-radeon, xserver-xorg-video-iti and installed in that place packages: fglrx-modules-dkms and firmware-linux-nonfree the error of freezing did not appeared. (Note that the firmware-linux-nonfree package is required for the radeon driver, not for fglrx, but the information you've provided shows that it was installed) It seems like the crashes you're experiencing are more or less random and all over the place. I can think of two basic explanations for that: Either the GPU is scribbling over random system memory locations, or there is a problem with the RAM or some other hardware component in the system. You can test for the latter with the memtest86(+) or memtester package. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer Thanks much for suggestions concerning memtest. In both cases (radeon or fglrx) I had firmware-linux-nonfree package installed. The last freeze was coused by SIGPIPE broken and I was able to get a full backtrace with gdb - enclosed here as a txt file: sigpipe_backtrace.txt. Could you have a look at it and say somthing about it. ? SIGPIPE in the X server is not an issue, it's expected whenever a client goes away. You should continue past that signal, or tell gdb not to stop on it. Cheers, Julien signature.asc Description: Digital signature
Bug#757982: xserver segmentation fault
Dnia 9 września 2014 5:13 Michel Dänzer mic...@daenzer.net napisał(a):
On 08.09.2014 20:32, repron wrote:
Last several freezes of Xorg, coused that Xorg.o.log file ended
suddenly, without SIGSEGV.
I am still trying to reproduce exactly the same state of freeze as
mentioned in the bug.
Of course it can be a bug in kernel or somewhere else but if I had
uninstalled packages
xserver-xorg-video-radeon, xserver-xorg-video-iti
and installed in that place packages:
fglrx-modules-dkms and firmware-linux-nonfree
the error of freezing did not appeared.
(Note that the firmware-linux-nonfree package is required for the radeon
driver, not for fglrx, but the information you've provided shows that it
was installed)
It seems like the crashes you're experiencing are more or less random
and all over the place. I can think of two basic explanations for that:
Either the GPU is scribbling over random system memory locations, or
there is a problem with the RAM or some other hardware component in the
system.
You can test for the latter with the memtest86(+) or memtester package.
--
Earthling Michel Dänzer| http://www.amd.com
Libre software enthusiast |Mesa and X developer
Thanks much for suggestions concerning memtest.
In both cases (radeon or fglrx) I had firmware-linux-nonfree
package installed.
The last freeze was coused by SIGPIPE broken and I was able
to get a full backtrace with gdb - enclosed here as a txt file:
sigpipe_backtrace.txt.
Could you have a look at it and say somthing about it. ?
with regards,
richiDEBUGGING INFORMATION from GDB after BACKTRACE of Xorg freezing
=
Program received signal SIGPIPE, Broken pipe.
0x7fc9bd0368f0 in __libc_writev (fd=38, vector=vector@entry=0x7fff74842ec0,
count=count@entry=1) at ../sysdeps/unix/sysv/linux/writev.c:54
54 ../sysdeps/unix/sysv/linux/writev.c: No such file or directory.
(gdb) bt full
#0 0x7fc9bd0368f0 in __libc_writev (fd=38,
vector=vector@entry=0x7fff74842ec0, count=count@entry=1) at
../sysdeps/unix/sysv/linux/writev.c:54
resultvar = 18446744073709551584
oldtype = 0
result = optimized out
#1 0x7fc9bf405a9c in _XSERVTransSocketWritev (ciptr=0x7fc9c142dc00,
buf=0x7fff74842ec0, size=optimized out) at
/usr/include/X11/Xtrans/Xtranssock.c:2364
No locals.
#2 0x7fc9bf400b7d in FlushClient (who=who@entry=0x7fc9c14203b0,
oc=oc@entry=0x7fc9c1422d60, __extraBuf=__extraBuf@entry=0x7fff74843050,
extraCount=extraCount@entry=32) at ../../os/io.c:941
before = optimized out
remain = optimized out
i = optimized out
len = optimized out
oco = 0x7fc9c1698e80
connection = 38
trans_conn = 0x7fc9c142dc00
iov = {{iov_base = 0x7fff74843050, iov_len = 32}, {iov_base =
0x7fc9c0f93060, iov_len = 3243186256}, {iov_base = 0x7fc9c0f93060, iov_len =
140504502846800}}
padBuffer = \000\000
extraBuf = 0x7fff74843050 W\002\257M\001
written = 0
padsize = 0
notWritten = 32
todo = 32
#3 0x7fc9bf40125e in WriteToClient (who=who@entry=0x7fc9c14203b0,
count=count@entry=32, __buf=__buf@entry=0x7fff74843050) at ../../os/io.c:856
oc = 0x7fc9c1422d60
oco = 0x7fc9c1698e80
buf = optimized out
#4 0x7fc9bf2aa142 in WriteEventsToClient (pClient=0x7fc9c14203b0,
count=optimized out, count@entry=1, events=events@entry=0x7fff74843050)
at ../../dix/events.c:5992
eventCopy = {u = {u = {type = 16 '\020', detail = 49 '1',
sequenceNumber = 29828}, keyButtonPointer = {pad00 = 1954820368, time = 32767,
root = 3243884512,
event = 32713, child = 1954820112, rootX = 32767, rootY = 0,
eventX = 5185, eventY = -17155, state = 0, sameScreen = 0 '\000', pad1 = 0
'\000'},
enterLeave = {pad00 = 1954820368, time = 32767, root = 3243884512,
event = 32713, child = 1954820112, rootX = 32767, rootY = 0, eventX = 5185,
eventY = -17155, state = 0, mode = 0 '\000', flags = 0 '\000'},
focus = {pad00 = 1954820368, window = 32767, mode = 224 '\340', pad1 = 191
'\277',
pad2 = 89 'Y', pad3 = 193 '\301'}, expose = {pad00 = 1954820368,
window = 32767, x = 49120, y = 49497, width = 32713, height = 0, count = 12304,
pad2 = 29828}, graphicsExposure = {pad00 = 1954820368, drawable =
32767, x = 49120, y = 49497, width = 32713, height = 0, minorEvent = 12304,
count = 29828, majorEvent = 255 '\377', pad1 = 127 '\177', pad2 =
0 '\000', pad3 = 0 '\000'}, noExposure = {pad00 = 1954820368, drawable = 32767,
minorEvent = 49120, majorEvent = 89 'Y', bpad = 193 '\301'},
visibility = {pad00 = 1954820368, window = 32767, state = 224 '\340', pad1 =
191 '\277',
pad2 = 89 'Y', pad3 = 193 '\301'}, createNotify = {pad00 =
1954820368, parent = 32767,
Bug#757982: xserver segmentation fault
On 07.09.2014 04:39, repron wrote: Dnia 13 sierpnia 2014 3:05 Michel Dänzer mic...@daenzer.net wrote: On 13.08.2014 09:37, repron wrote: [ 5884.303] (EE) Backtrace: [ 5884.303] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x7fcf5241b3f9] [ 5884.303] (EE) 1: /usr/bin/X (0x7fcf5227+0x1af469) [0x7fcf5241f469] [ 5884.304] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcf4ff78000+0x35480) [0x7fcf4ffad480] [ 5884.304] (EE) 3: /usr/bin/X (0x7fcf5227+0x12b70d) [0x7fcf5239b70d] [ 5884.304] (EE) 4: /usr/bin/X (0x7fcf5227+0x55ee7) [0x7fcf522c5ee7] [ 5884.304] (EE) 5: /usr/bin/X (0x7fcf5227+0x59f16) [0x7fcf522c9f16] [ 5884.304] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fcf4ff99b45] [ 5884.304] (EE) 7: /usr/bin/X (0x7fcf5227+0x4549e) [0x7fcf522b549e] [ 5884.304] (EE) [ 5884.304] (EE) Segmentation fault at address 0x0 [ 5884.304] (EE) Fatal server error: [ 5884.304] (EE) Caught signal 11 (Segmentation fault). Server aborting It would be good to see a full backtrace from gdb, but this doesn't look directly related to the driver. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer Attempting to get backtrace from gdb by ssh from other machine is still unsuccessfull. During Xorg freeze on remote host, gdb screen on main machine says nothing. On the screen still: --- (gdb) continue Continuing. -- As you can see, no info about receiving signal SIGSEGV. I would appreciate any suggestions how to get a miningfull backtrace of Xorg (maybe any trick). You should be able to get a backtrace like this if you can reproduce the crash from your original report. But I got somthing like this, when instead of freezing Xorg disappeared and screen switched to this: [1812.375053] CPU: 7 PID: 1 Comm: systemd Not tained3.14-2-amd64 #1 Debian 3.14.15-2 [1812.375090] Hardware name: To Be Filled By O.E.M. /960GM-GS3 FX, BIOS P1.40 02/05/2013 [1812.375135] task: 880129ec71b0 ti:880129ec8000 task.ti 880129ec8000 [1812.375170] RIP: 0010:[811a2ba4] [811a2ba4] __fget+0x14/0x80 [1812.375210] RSP: 0018:880129ec9f00 EFLAGS: 00010202 [1812.375235] RAX: 00ff00ff RBX: 880129ec9f2c RCX: [1812.375269] RDX: 00ff RSI: 4000RDI: 0043 [1812.375302] RBP: 880129ec9f28 R08: 7fff374b55e4 R09: 0009 [1812.375335] R10: R11: 0293 R12: 4000 [1812.375368] R13: 7fff374b5540 R14: 7fff374b55e4 R15: 7fff374b5760 [1812.375403] FS: 7f3eb16ab880() GS:88012edc() kn1GS: [1812.375442] CS: 0010 DS: ES: CR0: 80050033 [1812.375469] CR2: 0007f8d80cf6e38 CR3: c8aab000 CR4: 000407e0 [1812.375503] Stack: [1812.375514] 811a304c 813c669d 7fff374b5550 7fff374b5550 [1812.375556] 813c8c0b 8800c89c5cc0 7fff374b5760 [1812.375597] 0001 811cc474 814d33fa 2754 [1812.375639] Call Trace: [1812.375656] [811a304c] ? __fget_light+0x1c/0x60 [1812.375686] [813c669d] ? sockfd_lookup_light+0xd/0x70 [1812.375718] [813c8c0b] ? __sys_recvmsg+0x1b/0x70 [1812.375747] [811cc474] ? sys_epoll_wait+0xb4/0xe0 [1812.375778] [814d33fa]? int_signal+0x12/0x17 [1812.375806] [814d313d ] ? system_call_fast_compare_end+0x10/0x15 [1812.375840] Code: 48 89 df e8 7f d9 ff ff 48 89 df 5b e9 96 ed ff ff 66 0f 1f 44 00 00 65 48 8b 04 25 80 c8 00 00 48 8b 80 98 05 00 00 48 8b 40 08 3b 38 73 40 48 8b 40 08 89 ff 48 8d 04 f8 48 8b 10 48 85 c2 74 [1812.376011] RIP [811a2ba4]__fget+0x14/0x80 [1812.376040] RSP 880129ec9f00 [1812.387056] Kernel Panic - not syncing: Attempted to kill init! exitcode=0x000b [1812.387056] [1812.387107] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) [1812.387153] drm_kms_helper: panic occured, switching back to text console This kernel panic looks unrelated to the radeon driver. Maybe this bug report should be reassigned to the kernel. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
(bug #757982): I received also such informationon on the screen after Xserver freeze - (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f09e5f0d7a6] (EE) 1: /usr/bin/X (0x7f09e5d58000+0x1b99a9) (0x7f09e5f119a9) (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f09e3a68000+0x350f0) [0x7f09e3a9d0f0] (EE) 3: /usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1 (0x7f09dcbb8000+0x660920) [0x7f09dd218920] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (0x7f09e3a68000+0x37b39) [0x7f09e3a9fb39] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f09e3a68000+0x37b85) [0x7f09e3a9fb85] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfc) [0x7f09e3a89b4c] (EE) 7: /usr/bin/X (0x7f09e5d58000+0x4550e) (0x7f09e5d9d50e) (EE) (EE) Illegal instruction at address 0x7f09dd218920 (EE) Fatal server error: (EE) Caught signal 4 (Illegal instruction). Server aborting (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help (EE) Please also check the log file at /var/log/Xorg.0.log for additional information (EE) (EE) (EE) Backtrace: with regards, richi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
On 08.09.2014 20:32, repron wrote: Last several freezes of Xorg, coused that Xorg.o.log file ended suddenly, without SIGSEGV. I am still trying to reproduce exactly the same state of freeze as mentioned in the bug. Of course it can be a bug in kernel or somewhere else but if I had uninstalled packages xserver-xorg-video-radeon, xserver-xorg-video-iti and installed in that place packages: fglrx-modules-dkms and firmware-linux-nonfree the error of freezing did not appeared. (Note that the firmware-linux-nonfree package is required for the radeon driver, not for fglrx, but the information you've provided shows that it was installed) It seems like the crashes you're experiencing are more or less random and all over the place. I can think of two basic explanations for that: Either the GPU is scribbling over random system memory locations, or there is a problem with the RAM or some other hardware component in the system. You can test for the latter with the memtest86(+) or memtester package. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
Dnia 13 sierpnia 2014 2:48 maximilian attems m...@stro.at napisał(a): severity 757982 important stop On Wed, Aug 13, 2014 at 02:37:03AM +0200, repron wrote: Package: xserver-xorg-video-radeon Version: 1:7.4.0-2 Severity: grave and no a single failure is not grave. Dear Maintainer, With installed packages: xserver-xorg-video-radeon xserver-xorg-video-ati firmware-linux-nonfree very often randomly X-server freezes with the error: segmentation fault. I use X-window system: xfce4\. This didn't happen when I had installed debian non-free driver: fglrx-driver for my Radeon HD6670 graphic card. thank your for your report, can you please test against 3.16 linux from experimental (currently hold up due to upcoming Debian Installer release) and see if you can reproduce after reboot? -- maks I have tested against kernel 3.16-trunk. No changes. I mean Xorg still freezes randomly. richi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
Dnia 13 sierpnia 2014 3:05 Michel Dänzer mic...@daenzer.net wrote: On 13.08.2014 09:37, repron wrote: [ 5884.303] (EE) Backtrace: [ 5884.303] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x7fcf5241b3f9] [ 5884.303] (EE) 1: /usr/bin/X (0x7fcf5227+0x1af469) [0x7fcf5241f469] [ 5884.304] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcf4ff78000+0x35480) [0x7fcf4ffad480] [ 5884.304] (EE) 3: /usr/bin/X (0x7fcf5227+0x12b70d) [0x7fcf5239b70d] [ 5884.304] (EE) 4: /usr/bin/X (0x7fcf5227+0x55ee7) [0x7fcf522c5ee7] [ 5884.304] (EE) 5: /usr/bin/X (0x7fcf5227+0x59f16) [0x7fcf522c9f16] [ 5884.304] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fcf4ff99b45] [ 5884.304] (EE) 7: /usr/bin/X (0x7fcf5227+0x4549e) [0x7fcf522b549e] [ 5884.304] (EE) [ 5884.304] (EE) Segmentation fault at address 0x0 [ 5884.304] (EE) Fatal server error: [ 5884.304] (EE) Caught signal 11 (Segmentation fault). Server aborting It would be good to see a full backtrace from gdb, but this doesn't look directly related to the driver. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer Attempting to get backtrace from gdb by ssh from other machine is still unsuccessfull. During Xorg freeze on remote host, gdb screen on main machine says nothing. On the screen still: --- (gdb) continue Continuing. -- As you can see, no info about receiving signal SIGSEGV. I would appreciate any suggestions how to get a miningfull backtrace of Xorg (maybe any trick). But I got somthing like this, when instead of freezing Xorg disappeared and screen switched to this: [1812.375053] CPU: 7 PID: 1 Comm: systemd Not tained3.14-2-amd64 #1 Debian 3.14.15-2 [1812.375090] Hardware name: To Be Filled By O.E.M. /960GM-GS3 FX, BIOS P1.40 02/05/2013 [1812.375135] task: 880129ec71b0 ti:880129ec8000 task.ti 880129ec8000 [1812.375170] RIP: 0010:[811a2ba4] [811a2ba4] __fget+0x14/0x80 [1812.375210] RSP: 0018:880129ec9f00 EFLAGS: 00010202 [1812.375235] RAX: 00ff00ff RBX: 880129ec9f2c RCX: [1812.375269] RDX: 00ff RSI: 4000RDI: 0043 [1812.375302] RBP: 880129ec9f28 R08: 7fff374b55e4 R09: 0009 [1812.375335] R10: R11: 0293 R12: 4000 [1812.375368] R13: 7fff374b5540 R14: 7fff374b55e4 R15: 7fff374b5760 [1812.375403] FS: 7f3eb16ab880() GS:88012edc() kn1GS: [1812.375442] CS: 0010 DS: ES: CR0: 80050033 [1812.375469] CR2: 0007f8d80cf6e38 CR3: c8aab000 CR4: 000407e0 [1812.375503] Stack: [1812.375514] 811a304c 813c669d 7fff374b5550 7fff374b5550 [1812.375556] 813c8c0b 8800c89c5cc0 7fff374b5760 [1812.375597] 0001 811cc474 814d33fa 2754 [1812.375639] Call Trace: [1812.375656] [811a304c] ? __fget_light+0x1c/0x60 [1812.375686] [813c669d] ? sockfd_lookup_light+0xd/0x70 [1812.375718] [813c8c0b] ? __sys_recvmsg+0x1b/0x70 [1812.375747] [811cc474] ? sys_epoll_wait+0xb4/0xe0 [1812.375778] [814d33fa]? int_signal+0x12/0x17 [1812.375806] [814d313d ] ? system_call_fast_compare_end+0x10/0x15 [1812.375840] Code: 48 89 df e8 7f d9 ff ff 48 89 df 5b e9 96 ed ff ff 66 0f 1f 44 00 00 65 48 8b 04 25 80 c8 00 00 48 8b 80 98 05 00 00 48 8b 40 08 3b 38 73 40 48 8b 40 08 89 ff 48 8d 04 f8 48 8b 10 48 85 c2 74 [1812.376011] RIP [811a2ba4]__fget+0x14/0x80 [1812.376040] RSP 880129ec9f00 [1812.387056] Kernel Panic - not syncing: Attempted to kill init! exitcode=0x000b [1812.387056] [1812.387107] Kernel Offset: 0x0 from 0x8100 (relocation range: 0x8000-0x9fff) [1812.387153] drm_kms_helper: panic occured, switching back to text console I hope it helps. richi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
Package: xserver-xorg-video-radeon Version: 1:7.4.0-2 Severity: grave Dear Maintainer, With installed packages: xserver-xorg-video-radeon xserver-xorg-video-ati firmware-linux-nonfree very often randomly X-server freezes with the error: segmentation fault. I use X-window system: xfce4. This didn't happen when I had installed debian non-free driver: fglrx-driver for my Radeon HD6670 graphic card. Please, find the bug in the packages xserver-xorg-video-radeon, xserver-xorg-video-ati or in modules: ati_drv.so, radeon_drv.so to stop freezing the system. with regards Richi Xorg.0.log says: --- [ 4706.896] X.Org X Server 1.16.0 Release Date: 2014-07-16 [ 4706.896] X Protocol Version 11, Revision 0 [ 4706.896] Build Operating System: Linux 3.14-1-amd64 x86_64 Debian [ 4706.896] Current Operating System: Linux sypialnia 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 [ 4706.896] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 root=UUID=e129d003-4dda-476d-bd58-b7b00c3e0abe ro initrd=/install/initrd.gz quiet [ 4706.896] Build Date: 17 July 2014 10:22:36PM [ 4706.896] xorg-server 2:1.16.0-1 (http://www.debian.org/support) [ 4706.896] Current version of pixman: 0.32.6 [ 4706.896]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 4706.896] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 4706.897] (==) Log file: /var/log/Xorg.0.log, Time: Tue Aug 12 10:52:55 2014 [ 4706.897] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 4706.897] (==) No Layout section. Using the first Screen section. [ 4706.897] (==) No screen section available. Using defaults. [ 4706.897] (**) |--Screen Default Screen Section (0) [ 4706.897] (**) | |--Monitor default monitor [ 4706.897] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 4706.897] (==) Automatically adding devices [ 4706.897] (==) Automatically enabling devices [ 4706.897] (==) Automatically adding GPU devices [ 4706.897] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 4706.897]Entry deleted from font path. [ 4706.897] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 4706.897] (==) ModulePath set to /usr/lib/xorg/modules [ 4706.897] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 4706.897] (II) Loader magic: 0x7fcf526a2d80 [ 4706.897] (II) Module ABI versions: [ 4706.897]X.Org ANSI C Emulation: 0.4 [ 4706.897]X.Org Video Driver: 18.0 [ 4706.897]X.Org XInput driver : 21.0 [ 4706.897]X.Org Server Extension : 8.0 [ 4706.897] (II) xfree86: Adding drm device (/dev/dri/card0) [ 4706.899] (--) PCI:*(0:1:0:0) 1002:6758:1458:2545 rev 0, Mem @ 0xd000/268435456, 0xfebe/131072, I/O @ 0xd000/256, BIOS @ 0x/131072 [ 4706.899] (II) LoadModule: glx [ 4706.899] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 4706.900] (II) Module glx: vendor=X.Org Foundation [ 4706.900]compiled for 1.16.0, module version = 1.0.0 [ 4706.900]ABI class: X.Org Server Extension, version 8.0 [ 4706.900] (==) AIGLX enabled [ 4706.900] (==) Matched ati as autoconfigured driver 0 [ 4706.900] (==) Matched ati as autoconfigured driver 1 [ 4706.900] (==) Matched modesetting as autoconfigured driver 2 [ 4706.900] (==) Matched fbdev as autoconfigured driver 3 [ 4706.900] (==) Matched vesa as autoconfigured driver 4 [ 4706.900] (==) Assigned the driver to the xf86ConfigLayout [ 4706.900] (II) LoadModule: ati [ 4706.900] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [ 4706.900] (II) Module ati: vendor=X.Org Foundation [ 4706.900]compiled for 1.15.99.904, module version = 7.4.0 [ 4706.900]Module class: X.Org Video Driver [ 4706.900]ABI class: X.Org Video Driver, version 18.0 [ 4706.900] (II) LoadModule: radeon [ 4706.900] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [ 4706.900] (II) Module radeon: vendor=X.Org Foundation [ 4706.900]compiled for 1.15.99.904, module version = 7.4.0 [ 4706.900]Module class: X.Org Video Driver [ 4706.900]ABI class: X.Org Video Driver, version 18.0 [ 4706.900] (II) LoadModule: modesetting [ 4706.900] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 4706.900] (II) Module modesetting: vendor=X.Org Foundation [ 4706.900]compiled for 1.15.99.904, module version = 0.9.0 [ 4706.900]Module class: X.Org Video Driver [ 4706.900]
Bug#757982: xserver segmentation fault
severity 757982 important stop On Wed, Aug 13, 2014 at 02:37:03AM +0200, repron wrote: Package: xserver-xorg-video-radeon Version: 1:7.4.0-2 Severity: grave and no a single failure is not grave. Dear Maintainer, With installed packages: xserver-xorg-video-radeon xserver-xorg-video-ati firmware-linux-nonfree very often randomly X-server freezes with the error: segmentation fault. I use X-window system: xfce4. This didn't happen when I had installed debian non-free driver: fglrx-driver for my Radeon HD6670 graphic card. thank your for your report, can you please test against 3.16 linux from experimental (currently hold up due to upcoming Debian Installer release) and see if you can reproduce after reboot? -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
On 13.08.2014 09:37, repron wrote: [ 5884.303] (EE) Backtrace: [ 5884.303] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0x7fcf5241b3f9] [ 5884.303] (EE) 1: /usr/bin/X (0x7fcf5227+0x1af469) [0x7fcf5241f469] [ 5884.304] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcf4ff78000+0x35480) [0x7fcf4ffad480] [ 5884.304] (EE) 3: /usr/bin/X (0x7fcf5227+0x12b70d) [0x7fcf5239b70d] [ 5884.304] (EE) 4: /usr/bin/X (0x7fcf5227+0x55ee7) [0x7fcf522c5ee7] [ 5884.304] (EE) 5: /usr/bin/X (0x7fcf5227+0x59f16) [0x7fcf522c9f16] [ 5884.304] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fcf4ff99b45] [ 5884.304] (EE) 7: /usr/bin/X (0x7fcf5227+0x4549e) [0x7fcf522b549e] [ 5884.304] (EE) [ 5884.304] (EE) Segmentation fault at address 0x0 [ 5884.304] (EE) Fatal server error: [ 5884.304] (EE) Caught signal 11 (Segmentation fault). Server aborting It would be good to see a full backtrace from gdb, but this doesn't look directly related to the driver. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
