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 69488] New: GF108 (NVC1) GPU lockup
Date: Tue, 17 Sep 2013 19:28:04 +0000	[thread overview]
Message-ID: <bug-69488-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 69488
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: GF108 (NVC1) GPU lockup
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: vekinn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 86010
  --> https://bugs.freedesktop.org/attachment.cgi?id=86010&action=edit
journalctl log

GPU locks up during boot and falls back to software frame buffer.

Booting with uefi and Linux stub loader on a t530.

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

[-- Attachment #1.2: Type: text/html, Size: 2281 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-09-17 19:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 19:28 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-69488-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-26 22:26   ` [Bug 69488] GF108 (NVC1) GPU lockup bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27  0:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27  0:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27  0:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27  3:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 15:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 15:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 16:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-30 22:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-30 22:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-02 16:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-02 20:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-02 20:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-02 23:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03  7:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03  7:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03 18:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03 18:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03 18:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-25  3:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-26 13:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-04 16:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-06 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-07  7:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-08 21:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-09  2:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-09 23:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-12 18:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 18:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 18:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 20:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 20:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-18  3:19   ` 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-69488-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.