From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 106227] GP107 hangs on boot
Date: Fri, 04 May 2018 02:17:01 +0000 [thread overview]
Message-ID: <bug-106227-8800-u1VIi9aINV@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106227-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 686 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106227
--- Comment #1 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
GPU lockup right on boot. nofbaccel makes fbdev not accelerated (and noaccel=1
makes userspace not able to access the accel features), so the gr unit is never
used. The GPU is still used, but only for outputs.
Perhaps PCIe PM is getting in the way? You could try killing it with
pcie_port_pm=off although that hasn't helped a lot of people.
You could try adding nouveau.runpm=0 although since the hang is right on load,
I doubt that would affect matters.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1382 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2018-05-04 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 3:25 [Bug 106227] New: GP107 hangs on boot bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-106227-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-05-04 2:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2018-05-09 20:40 ` [Bug 106227] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:38 ` 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-106227-8800-u1VIi9aINV@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.