From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 99900] [NVC1] nouveau: freeze / crash after kernel update to 4.10
Date: Wed, 20 Sep 2017 22:08:30 +0000 [thread overview]
Message-ID: <bug-99900-8800-AYoSkdyoE6@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99900-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99900
--- Comment #21 from andrewb03-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org ---
4.13 throws on my Gentoo install (since it wasn't available on Arch yet):
nouveau 0000:0a:00.0: DRM: DDC responded, but no EDID for DP-4
When this happens the console freezes unless I disable KMS via the command line
(SSH works fine).
My GPUs are 660ti in the second PCI slot connected to DP-1 and 1080ti in the
first PCI slot connected to DP-4.
Are you saying 4.12.11+ was supposed to resolve the random freezing?
On Gentoo I don't even have X install so I think it freezes when nouveau tries
to load the FB console.
Would it be worth building nouveau in instead of as a kernel module?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1567 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:[~2017-09-20 22:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-99900-8800@http.bugs.freedesktop.org/>
[not found] ` <bug-99900-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-02-22 13:56 ` [Bug 99900] nouveau: freeze / crash after kernel update to 4.10 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-22 13:58 ` [Bug 99900] [NVC1] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-27 21:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-27 21:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 7:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 8:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 8:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-02-28 9:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-03 9:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-04 7:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-04 7:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-06 7:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-14 12:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 23:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-11 18:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-26 16:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-26 16:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-26 16:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-19 21:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-19 22:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-19 23:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-20 22:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-09-20 22:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-21 0:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-09-21 4:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-23 23:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:24 ` 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-99900-8800-AYoSkdyoE6@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.