From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 101184] New: [bisected] Panic on boot with GK106
Date: Thu, 25 May 2017 10:17:09 +0000 [thread overview]
Message-ID: <bug-101184-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1092 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101184
Bug ID: 101184
Summary: [bisected] Panic on boot with GK106
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: sgilles-8yXg+M/94Z32fBVCVOL8/A@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 131503
--> https://bugs.freedesktop.org/attachment.cgi?id=131503&action=edit
Transcription of kernel panic
Since e4311ee51d1e2676001b2d8fcefd92bdd79aad85 "drm/nouveau/therm: remove
ineffective workarounds for alarm bugs", my machine with a GTX 650 panics on
boot. I will attach lspci output and a transcription of the panic, and I can
provide more information or test patches as needed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2529 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-05-25 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 10:17 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-101184-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-05-25 10:17 ` [Bug 101184] [bisected] Panic on boot with GK106 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-27 9:16 ` [Bug 101184] [NVE6] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-29 9:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-29 10:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-29 10:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-29 11:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05 7:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05 12:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-05 17:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-06 1:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-07 17:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-09 16:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-15 6:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-15 7:35 ` 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-101184-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.