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 98712] New: [PPC64] GPU Lock Up when Nouveau 2D acceleration is enabled + X failures
Date: Sun, 13 Nov 2016 22:42:05 +0000	[thread overview]
Message-ID: <bug-98712-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 98712
           Summary: [PPC64] GPU Lock Up when Nouveau 2D acceleration is
                    enabled + X failures
           Product: xorg
           Version: 7.7 (2012.06)
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: jeffbai-ymACFijhrKM@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 127956
  --> https://bugs.freedesktop.org/attachment.cgi?id=127956&action=edit
dmesg without nouveau.noaccel=1

Happened to get 2 FX4500's for my PowerMac G5 11,2, but it didn't seem willing
to cooperate.

Without nouveau.noaccel=1 in the kernel parameter, the system starts fine, but
X would only work with fbdev driver - as GPU locks up at early stages of
startup (dmesg attached above).

With nouveau.noaccel=1 in the kernel parameter, system starts fine without the
lock up message, but X will **still** only work with fbdev - using nouveau with
result in a looped output of the following message:

"nouveau 0000:0a:00.0: DRM: 0x13DC: Parsing digital output script table"

And the system is inaccessible, this also appears to hang any `systemctl stop
lightdm` operation and even the `reboot` command itself.

---------------------------

Xorg-Server version: 1.18.4
Kernel version: 4.8.6
xf86-video-nouveau version: 1.0.12

---------------------------

I would happily donate one of my FX4500's to one who's willing to investigate
this issue.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2016-11-13 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-13 22:42 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-98712-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-11-13 22:42   ` [Bug 98712] [PPC64] GPU Lock Up when Nouveau 2D acceleration is enabled + X failures bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-13 22:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-13 22:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-13 22:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-13 22:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-13 23:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:21   ` 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-98712-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.