From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 53535] New: G84M [Quadro NVS 140M] X crash after waking up from suspend: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT)
Date: Wed, 15 Aug 2012 10:49:54 +0000 [thread overview]
Message-ID: <bug-53535-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=53535
Bug #: 53535
Summary: G84M [Quadro NVS 140M] X crash after waking up from
suspend: Process /usr/bin/Xorg was killed by signal 6
(SIGABRT)
Classification: Unclassified
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: reklov-EMRzualFZlQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 65596
--> https://bugs.freedesktop.org/attachment.cgi?id=65596
Xorg backtrace
After waking up from suspend and starting firefox X crashes.
cmdline: /usr/bin/Xorg :0 -background none -logverbose 7 -auth
/var/run/gdm/auth-for-gdm-u1CSc3/database -seat seat0 -nolisten tcp vt1
Packages:
kernel.x86_64 3.5.1-1.fc17
xorg-x11-drv-ast.x86_64 0.93.9-6.fc17
xorg-x11-drv-ati.x86_64 6.14.4-6.20120602git930760942.fc17
xorg-x11-drv-cirrus.x86_64 1.3.2-19.fc17
xorg-x11-drv-dummy.x86_64 0.3.5-4.fc17
xorg-x11-drv-evdev.x86_64 2.7.0-2.fc17
xorg-x11-drv-fbdev.x86_64 0.4.2-8.fc17
xorg-x11-drv-intel.x86_64 2.20.1-1.fc17
xorg-x11-drv-mga.x86_64 1.4.13-19.20120104git9223c44a7.fc17
xorg-x11-drv-nouveau.x86_64 1:0.0.16-37.20120306gitf5d1cd2.fc17
xorg-x11-drv-nouveau-debuginfo.x86_64
1:0.0.16-37.20120306gitf5d1cd2.fc17
xorg-x11-drv-openchrome.x86_64 0.2.906-1.fc17
xorg-x11-drv-qxl.x86_64 0.0.22-0.fc17
xorg-x11-drv-synaptics.x86_64 1.6.2-1.fc17
xorg-x11-drv-vesa.x86_64 2.3.1-1.fc17
xorg-x11-drv-vmmouse.x86_64 12.8.0-1.fc17
xorg-x11-drv-vmware.x86_64 12.0.2-1.fc17
xorg-x11-drv-void.x86_64 1.4.0-8.fc17
xorg-x11-drv-wacom.x86_64 0.14.0-2.fc17
xorg-x11-font-utils.x86_64 1:7.5-7.fc17
xorg-x11-fonts-misc.noarch 7.5-5.fc17
xorg-x11-server-Xephyr.x86_64 1.12.2-4.fc17
xorg-x11-server-Xorg.x86_64 1.12.2-4.fc17
xorg-x11-server-common.x86_64 1.12.2-4.fc17
xorg-x11-server-debuginfo.x86_64 1.12.2-4.fc17
xorg-x11-server-utils.x86_64 7.5-12.fc17
xorg-x11-utils.x86_64 7.5-6.fc17
xorg-x11-xauth.x86_64 1:1.0.7-1.fc17
xorg-x11-xinit.x86_64 1.3.2-5.fc17
xorg-x11-xkb-utils.x86_64 7.5-6.fc17
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-08-15 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 10:49 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-53535-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-08-15 10:52 ` [Bug 53535] G84M [Quadro NVS 140M] X crash after waking up from suspend: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-15 10:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-15 11:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 23:34 ` [Bug 53535] [NV84] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 11:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-53535-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.