[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#757982: xserver segmentation fault



On 07.09.2014 04:39, repron wrote:


Dnia 13 sierpnia 2014 3:05 Michel Dänzer <michel@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 (0x7fcf52270000+0x1af469)> [0x7fcf5241f469]
[  5884.304] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6> (0x7fcf4ff78000+0x35480) [0x7fcf4ffad480]
[  5884.304] (EE) 3: /usr/bin/X (0x7fcf52270000+0x12b70d)> [0x7fcf5239b70d]
[  5884.304] (EE) 4: /usr/bin/X (0x7fcf52270000+0x55ee7)> [0x7fcf522c5ee7]
[  5884.304] (EE) 5: /usr/bin/X (0x7fcf52270000+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 (0x7fcf52270000+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 tained    3.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: ffff880129ec71b0   ti:ffff880129ec8000   task.ti ffff880129ec8000
[1812.375170]  RIP: 0010:[<ffffffff811a2ba4>]   [<ffffffff811a2ba4>]    __fget+0x14/0x80
[1812.375210]  RSP: 0018:ffff880129ec9f00     EFLAGS: 00010202
[1812.375235]  RAX: 00ffffff00ffffff           RBX: ffff880129ec9f2c        RCX: 00000000ffffffff
[1812.375269]  RDX: 0000000000ffffff     RSI: 0000000000004000    RDI: 0000000000000043
[1812.375302]  RBP: ffff880129ec9f28     R08: 00007fff374b55e4      R09: 0000000000000009
[1812.375335]  R10: 00000000ffffffff        R11: 0000000000000293   R12: 0000000040000000
[1812.375368]  R13: 00007fff374b5540   R14: 00007fff374b55e4      R15: 00007fff374b5760
[1812.375403]  FS:  00007f3eb16ab880(0000)   GS:ffff88012edc0000(0000)   kn1GS:0000000000000000
[1812.375442]  CS:  0010   DS: 0000   ES: 0000   CR0: 0000000080050033
[1812.375469]  CR2: 0007f8d80cf6e38   CR3: 00000000c8aab000   CR4: 00000000000407e0
[1812.375503]   Stack:
[1812.375514]     ffffffff811a304c           ffffffff813c669d     00007fff374b5550     00007fff374b5550
[1812.375556]     ffffffff813c8c0b           00000000ffffffff     ffff8800c89c5cc0       00007fff374b5760
[1812.375597]     0000000000000001   ffffffff811cc474     ffffffff814d33fa           0000000000002754
[1812.375639]  Call Trace:
[1812.375656]     [<ffffffff811a304c>]   ?   __fget_light+0x1c/0x60
[1812.375686]     [<ffffffff813c669d>]   ?   sockfd_lookup_light+0xd/0x70
[1812.375718]     [<ffffffff813c8c0b>]   ?   __sys_recvmsg+0x1b/0x70
[1812.375747]     [<ffffffff811cc474>]   ?   sys_epoll_wait+0xb4/0xe0
[1812.375778]     [<ffffffff814d33fa>]    ?   int_signal+0x12/0x17
[1812.375806]     [<ffffffff814d313d> ]  ?   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 [<ffffffff811a2ba4>]    __fget+0x14/0x80
[1812.376040]  RSP <ffff880129ec9f00>
[1812.387056]  Kernel Panic - not syncing:  Attempted to kill init!    exitcode=0x0000000b
[1812.387056]
[1812.387107]  Kernel Offset: 0x0 from 0xffffffff81000000   (relocation range: 0xffffffff80000000-0xffffffff9fffffff)
[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


Reply to: