All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 71357] New: After S3 resume X is broken and reboot needed
Date: Thu, 07 Nov 2013 21:26:47 +0000	[thread overview]
Message-ID: <bug-71357-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1436 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=71357

          Priority: medium
            Bug ID: 71357
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: After S3 resume X is broken and reboot needed
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: krah.tm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 9.2
         Component: Drivers/DRI/nouveau
           Product: Mesa

Created attachment 88845
  --> https://bugs.freedesktop.org/attachment.cgi?id=88845&action=edit
Xorg.0.log

Got a Lenovo T530 notebook with a NVS 5400M card.
Suspending to RAM and resume from console only does work fine.

But doing it from X i've get a broken X system, starting X after the resume
basic stuff from mdm display manager is ok, but as soon as cinnamon is starting
its broken again.

Attached is the Xorg.0.log with errors logged.

dmesg is also there - the first 2 errors with cinnamon were logged when i did
"service mdm stop", the other 4 were logged after "kill -9 7350".
Only a reboot did work and it was possible to reboot the box.
Attached is also a full backtrace from gdb after X was tried to shut down via
"kill -9" which did not work.

Its a stock ubuntu 13.10 with mesa 9.2.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2820 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-11-07 21:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 21:26 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-71357-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-07 21:27   ` [Bug 71357] After S3 resume X is broken and reboot needed bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-07 21:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-07 21:31   ` [Bug 71357] [NVC1] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-07 21:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-07 21:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-08  8:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-08  8:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-08  8:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-08  8:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-11 23:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-16 14:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22  2:59   ` 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-71357-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.