From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 97620] [REGRESSION] KMS having issues after kernel upgrade (4.5.1-1 to 4.6.4-1)
Date: Mon, 19 Sep 2016 05:34:29 +0000 [thread overview]
Message-ID: <bug-97620-8800-79urOrvtCf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97620-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97620
--- Comment #27 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Looking at our VBIOS repo, we have a bunch (but not all) of GF104's that are
missing the 0x2240c write as well as one GK107. Every other (GF100+) GPU sets
0x2240c. I guess it's not as reliable as we'd hoped.
This is how I checked:
for i in nv[cdef]?/*/*.rom nv1??/*/*.rom; do echo $i; nvbios $i |& grep
0x02240c; done
And looked for files without a 'NV_REG R[0x02240c] &= 0xfffffffd |=
0x00000002' command.
Although that in itself shouldn't be a major issue - rerunning the VBIOS
shouldn't cause issues...
Looking at a mmiotrace that came with one of those GF104 VBIOSes that are
missing a 0x2240c write, it doesn't seem like the VBIOS gets executed there, or
at least not that script. It's late and I could have messed up though.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1785 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:[~2016-09-19 5:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 3:39 [Bug 97620] New: [REGRESSION] KMS having issues after kernel upgrade (4.5.1-1 to 4.6.4-1) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-97620-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-09-07 3:40 ` [Bug 97620] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 3:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 3:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 3:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 4:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 4:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 4:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 4:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 4:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 4:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-07 17:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-18 23:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-18 23:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-18 23:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 3:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 4:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 4:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 4:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 4:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 4:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 5:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 5:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-09-20 4:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-10-31 3:57 ` [Bug 97620] [REGRESSION, bisected] KMS can't initialize GeForce GTX 460 after commit a6a0f67ca7aae2e6bec7ebf55d1e4853dc220816 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-06 14:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-06 14:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-27 18:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-27 19:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 4:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 20:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-28 20:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-31 9:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-31 14:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-04 0:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:17 ` 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-97620-8800-79urOrvtCf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox