Bug 1112024 - [abrt] xorg-x11-server-Xorg: Xorg killed by SIGABRT
Summary: [abrt] xorg-x11-server-Xorg: Xorg killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:f5144156d8ff8a1a21506625621...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-22 21:34 UTC by raffamaiden
Modified: 2015-06-29 21:16 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:16:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (22.71 KB, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: cgroup (154 bytes, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: core_backtrace (6.63 KB, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: dso_list (5.58 KB, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: environ (198 bytes, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: maps (28.27 KB, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: proc_pid_status (905 bytes, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
File: var_log_messages (346 bytes, text/plain)
2014-06-22 21:34 UTC, raffamaiden
no flags Details
Error Logs from Devon (4.22 MB, application/octet-stream)
2014-09-14 06:25 UTC, Devon Janitz
no flags Details
Error Logs from Devon (34.87 KB, application/octet-stream)
2014-09-14 06:28 UTC, Devon Janitz
no flags Details
Error Logs from Devon (28.06 KB, application/octet-stream)
2014-09-14 06:29 UTC, Devon Janitz
no flags Details

Description raffamaiden 2014-06-22 21:34:14 UTC
Description of problem:
Without reason at a certain point my system logs out automatically. A black screen appear with strings (like the one you see starting up in older versions when there was no fedora logo), then the "choice user" screen appears, where i have to click on my user, digit my password and then it re-logs in. After some seconds it logs out again. It seems to be related to my Samsung Tablet connected as a MTP device at the login step, but i'm not sure at all

Version-Release number of selected component:
xorg-x11-server-Xorg-1.14.4-9.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-mvVfXO/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.14.7-200.fc20.x86_64
open_fds:       
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #9 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:171
 #10 memcpy at /usr/include/bits/string3.h:51
 #11 EVERGREENUploadToScreen at evergreen_exa.c:1726
 #12 exaCopyDirty at exa_migration_classic.c:220
 #13 exaDoMigration_mixed at exa_migration_mixed.c:118
 #14 exaTryDriverComposite at exa_render.c:719
 #15 exaComposite at exa_render.c:1006
 #16 damageComposite at damage.c:563
 #17 exaTrapezoids at exa_render.c:1149
 #18 ProcRenderTrapezoids at render.c:759

Comment 1 raffamaiden 2014-06-22 21:34:22 UTC
Created attachment 911187 [details]
File: backtrace

Comment 2 raffamaiden 2014-06-22 21:34:25 UTC
Created attachment 911188 [details]
File: cgroup

Comment 3 raffamaiden 2014-06-22 21:34:27 UTC
Created attachment 911189 [details]
File: core_backtrace

Comment 4 raffamaiden 2014-06-22 21:34:29 UTC
Created attachment 911190 [details]
File: dso_list

Comment 5 raffamaiden 2014-06-22 21:34:31 UTC
Created attachment 911191 [details]
File: environ

Comment 6 raffamaiden 2014-06-22 21:34:34 UTC
Created attachment 911192 [details]
File: limits

Comment 7 raffamaiden 2014-06-22 21:34:36 UTC
Created attachment 911193 [details]
File: maps

Comment 8 raffamaiden 2014-06-22 21:34:39 UTC
Created attachment 911194 [details]
File: proc_pid_status

Comment 9 raffamaiden 2014-06-22 21:34:44 UTC
Created attachment 911195 [details]
File: var_log_messages

Comment 10 D. Hugh Redelmeier 2014-07-12 06:40:38 UTC
Another user experienced a similar problem:

Step 1: display locked up while I was away from it.  Several hours after I was away.

Step 2: I sshed into the machine from another, captured dmesg and /var/log/Xorg*

Step 3: reboot (without power being off)

Step 4: X never properly came up after the reboot.

Step 5: shutdown, all the way to power off

Step 6: reboot and run ABRT.

Here we are.

I'm not actually sure which step ABRT is reporting.

The problem appears to be a nouveau bug.  Certainly the dmesg output I've examined show problem with nouveau.

Previously I've had nouveau lockups with ver pretty curdled screens.  Not this time.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-hNwbHE/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.15.3-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 11 Mikhail Yarashevich 2014-07-15 07:10:52 UTC
Another user experienced a similar problem:

Laptop wakes up from suspend.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/X -background none :0 vt01 -nolisten tcp
executable:     /usr/bin/Xorg
kernel:         3.15.4-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 12 Fred Odendaal 2014-07-28 03:44:57 UTC
Another user experienced a similar problem:

System hangs randomly and display goes black. The frequency of this occurrance can be increased by watching flash videos or playing flash games.

When this happens, the computer has to be reset manually. It doesn't reboot on its own. I'm hoping this stack trace isn't from that manual reset.

The LCD monitor (model #W2242TQ) is connected via DVI. The graphics card is ATI HD5000 series. I think it's an HD5450, but I'd have to open the case to confirm.

Here is the output of lspci -nn:
00.0 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:0364]
00:00.1 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:1364]
00:00.2 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:2364]
00:00.3 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:3364]
00:00.4 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:4364]
00:00.5 PIC [0800]: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller [1106:5364]
00:00.6 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device [1106:6364]
00:00.7 Host bridge [0600]: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge [1106:7364]
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198]
00:02.0 PCI bridge [0604]: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:a364] (rev 80)
00:03.0 PCI bridge [0604]: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller [1106:c364] (rev 80)
00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VT8237/8251 Serial ATA Controller [1106:5372]
00:0f.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 07)
00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.3 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev b0)
00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237S PCI to ISA Bridge [1106:3372]
00:11.7 Host bridge [0600]: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller [1106:287e]
00:13.0 Host bridge [0600]: VIA Technologies, Inc. VT8237A Host Bridge [1106:337b]
00:13.1 PCI bridge [0604]: VIA Technologies, Inc. VT8237A PCI to PCI Bridge [1106:337a]
02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
02:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series] [1002:aa68]
80:01.0 Audio device [0403]: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller [1106:3288] (rev 10)

Kernel version = 3.15.6-200.fc20.x86_64
xorg-x11-drv-ati version = 7.2.0-3.20131101git3b38701.fc20

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-yGHOWs/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.15.5-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 13 raffamaiden 2014-08-21 09:51:08 UTC
Another user experienced a similar problem:

I really don't know. I was just browsing with google chrom. This happens sometimes, sometimes with severalrestarts in a day. I have an AMD video card with mesa drivers, not catalyst ones

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-0VE1dd/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.15.8-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 14 smokydesperado16 2014-09-05 04:05:32 UTC
Another user experienced a similar problem:

I have an Acer Aspire X1200 (desktop), ever since I switch to Linux distros two years ago, I always have problems with my graphics. My computer uses Nvidia GeForce 8200, so the open source driver is nouveau.

With others distros and Fedora 20, sometimes when I'm doing something, the screen freezes, the mouse moves but everything is stuck. Fedora 20 goes back to the login screen within several minutes but if not I have to restart my computer.

This happens so often, I love Linux and Fedora, but this problem with my graphics or xorg server is extremely frustrating. Any possible fixes would be greatly appreciated.

Thank You

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-kGcNMK/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.15.10-201.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 15 Devon Janitz 2014-09-14 05:39:35 UTC
Another user experienced a similar problem:

Seems to be connected to running Vitual Box, but I am not sure.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-D5G8Mh/database -seat seat0 -nolisten tcp
executable:     /usr/bin/Xorg
kernel:         3.16.2-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 16 Devon Janitz 2014-09-14 06:21:10 UTC
More to offer, I was able to reporduce the problem by starting the same VM backup and running it again for a few minutes.  I am running an Ubuntu 14.04 VM under Virtual Box.  None of my other VM's cause this problem.  I will post more ABART logs soon.
Thanks, Devon

Comment 17 Devon Janitz 2014-09-14 06:25:54 UTC
Created attachment 937286 [details]
Error Logs from Devon

Comment 18 Devon Janitz 2014-09-14 06:28:34 UTC
Created attachment 937287 [details]
Error Logs from Devon

Comment 19 Devon Janitz 2014-09-14 06:29:07 UTC
Created attachment 937288 [details]
Error Logs from Devon

Comment 20 Devon Janitz 2014-09-14 08:03:01 UTC
Good day,
I have verified that I can easily recreate the issue in attachment 937286 [details] above by running the Ubuntu VM along or with other VMs.  So it is only happening when the Ubuntu VM is running inside of Virtual Box.

Let me know if you would like anything else specific from my system at all and I will provide it.
Thanks, Devon

Comment 21 Devon Janitz 2014-09-17 01:52:40 UTC
Hi all,
I have narrowed down the condition on the Ubutu VM.  When you disable 3D Acceleration the system does not crash.  When you turn Enable 3D Acceleration it crashes again.
Thanks, Devon

Comment 22 richard.cardone 2014-11-18 15:27:53 UTC
Another user experienced a similar problem:

Every few days Fedora 20 becomes inoperable.  The symptom is that both monitors go black and even though a mouse pointer is on screen, I cannot move it.  I have a lot of programs idling in 6 workspaces, but no heavy load on the system. 

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-uWs8tP/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.16.7-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 23 Fedora End Of Life 2015-05-29 12:11:37 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 24 Fedora End Of Life 2015-06-29 21:16:24 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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