poma
2014-Sep-13 21:25 UTC
[Nouveau] VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
On 13.09.2014 22:58, Ilia Mirkin wrote:> On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.09.2014 07:02, poma wrote: >>> On 13.09.2014 06:57, poma wrote: >>>> >>>> Actually I have nothing to show cause logs are all OK. >>>> Haha, it seems to me that the bugs become intelligent. >>>> >>>> 3.15.10-201.fc20.x86_64 >>>> 3.16.2-200.fc20.x86_64 >>>> 3.17.0-0.rc4.git3.2.fc22.1.x86_64 >>>> nouveau [ DRM] suspending display... >>>> nouveau [ DRM] unpinning framebuffer(s)... >>>> nouveau [ DRM] evicting buffers... >>>> nouveau [ DRM] waiting for kernel channels to go idle... >>>> nouveau [ DRM] suspending client object trees... >>>> nouveau [ DRM] suspending kernel object tree... >>>> ... >>>> nouveau [ DRM] re-enabling device... >>>> nouveau [ DRM] resuming kernel object tree... >>>> nouveau [ VBIOS][0000:02:00.0] running init tables >>>> nouveau [ PTHERM][0000:02:00.0] fan management: automatic >>>> nouveau [ CLK][0000:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz >>>> nouveau [ DRM] resuming client object trees... >>>> nouveau [ DRM] resuming display... >>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>> >>>> Logs(dmesg) are literally identical. >>>> >>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>> >>>> >>> >>> Excusez-moi, >>> BROKEN == The display remains OFF. >>> >> >> More precisely stated it looks like this: >> >> - Last kernel with working resume/thaw >> http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 >> kernel-3.16.0-0.rc0.git9.1.fc21 >> 2014-06-13 >> >> - First kernel with broken resume/thaw >> kernel-3.16.0-0.rc0.git10.1.fc21 >> http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 >> http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz >> 2014-06-13 >> >> The only difference in dmesg between working and broken kernel module with drm.debug=14 is >> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >> >> - git commit probably introduced breakage >> drm/nouveau/disp: add internal representaion of output paths and connectors >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm?id=7a014a >> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau?id=7a014a >> 2014-06-11 > > Do you have any special reason to believe this to be the culprit > (besides the fact that it has something to do with hpd)? Can you do an > actual bisect to confirm? > > Thanks, > > -ilia"hpd" what? First Fedora Kernel with broken video resume/thaw aka FFKWBVRT i.e. kernel-3.16.0-0.rc0.git10.1.fc21 comes with 'patch-3.15-git10.xz' which closely resembles "git/commit/drivers/gpu/drm/nouveau?id=7a014a". Simple as that. Why are you asking me that bisect formality, man is it not enough that I tested two dozen kernels. poma
Roy Spliet
2014-Sep-13 21:45 UTC
[Nouveau] VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
Dear Poma, Don't get anyone wrong, your input is greatly valued. The reason why "we" (nouveau developers) generally ask for a git bisection is because we don't know or track specific distributions. Although your search has narrowed the problem down (thanks for that!), we don't know how big the difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and kernel-3.16.0-0.rc0.git10.1.fc21. Is the difference literally just that one patch? Or were there more patches to nouveau or drm that might have been the culprit? So far I haven't succeeded in finding the exact differences between the two kernels. Git bisect on the upstream kernel on the other hand will always point at the precise patch that broke the kernel, narrowing down the search space of the bug for developers thus reducing the time it takes to fix your issue. Unless developers can reproduce your issue, Unfortunately the user is the person who has to do the bisecting. So in short: narrowing down the search space often saves a lot of time of the developer, reducing the time it takes to fix your issue! Thus, if you can find the time to perform a git bisect (with the right good/bad markers it really should not take that many kernels to build), or if you can validate that the patch you mention *really* is the only difference between the two kernels, it'd be greatly appreciated. Thanks! Yours, Roy Op 13-09-14 om 23:25 schreef poma:> On 13.09.2014 22:58, Ilia Mirkin wrote: >> On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >>> On 13.09.2014 07:02, poma wrote: >>>> On 13.09.2014 06:57, poma wrote: >>>>> Actually I have nothing to show cause logs are all OK. >>>>> Haha, it seems to me that the bugs become intelligent. >>>>> >>>>> 3.15.10-201.fc20.x86_64 >>>>> 3.16.2-200.fc20.x86_64 >>>>> 3.17.0-0.rc4.git3.2.fc22.1.x86_64 >>>>> nouveau [ DRM] suspending display... >>>>> nouveau [ DRM] unpinning framebuffer(s)... >>>>> nouveau [ DRM] evicting buffers... >>>>> nouveau [ DRM] waiting for kernel channels to go idle... >>>>> nouveau [ DRM] suspending client object trees... >>>>> nouveau [ DRM] suspending kernel object tree... >>>>> ... >>>>> nouveau [ DRM] re-enabling device... >>>>> nouveau [ DRM] resuming kernel object tree... >>>>> nouveau [ VBIOS][0000:02:00.0] running init tables >>>>> nouveau [ PTHERM][0000:02:00.0] fan management: automatic >>>>> nouveau [ CLK][0000:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz >>>>> nouveau [ DRM] resuming client object trees... >>>>> nouveau [ DRM] resuming display... >>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>> >>>>> Logs(dmesg) are literally identical. >>>>> >>>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>>> >>>>> >>>> Excusez-moi, >>>> BROKEN == The display remains OFF. >>>> >>> More precisely stated it looks like this: >>> >>> - Last kernel with working resume/thaw >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 >>> kernel-3.16.0-0.rc0.git9.1.fc21 >>> 2014-06-13 >>> >>> - First kernel with broken resume/thaw >>> kernel-3.16.0-0.rc0.git10.1.fc21 >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 >>> http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz >>> 2014-06-13 >>> >>> The only difference in dmesg between working and broken kernel module with drm.debug=14 is >>> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >>> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >>> >>> - git commit probably introduced breakage >>> drm/nouveau/disp: add internal representaion of output paths and connectors >>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm?id=7a014a >>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau?id=7a014a >>> 2014-06-11 >> Do you have any special reason to believe this to be the culprit >> (besides the fact that it has something to do with hpd)? Can you do an >> actual bisect to confirm? >> >> Thanks, >> >> -ilia > "hpd" what? > First Fedora Kernel with broken video resume/thaw aka FFKWBVRT i.e. kernel-3.16.0-0.rc0.git10.1.fc21 > comes with 'patch-3.15-git10.xz' which closely resembles "git/commit/drivers/gpu/drm/nouveau?id=7a014a". > Simple as that. > Why are you asking me that bisect formality, man is it not enough that I tested two dozen kernels. > > > poma > > > _______________________________________________ > Nouveau mailing list > Nouveau at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/nouveau >
Ilia Mirkin
2014-Sep-13 21:46 UTC
[Nouveau] VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
On Sat, Sep 13, 2014 at 5:25 PM, poma <pomidorabelisima at gmail.com> wrote:> On 13.09.2014 22:58, Ilia Mirkin wrote: >> On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >>> On 13.09.2014 07:02, poma wrote: >>>> On 13.09.2014 06:57, poma wrote: >>>>> >>>>> Actually I have nothing to show cause logs are all OK. >>>>> Haha, it seems to me that the bugs become intelligent. >>>>> >>>>> 3.15.10-201.fc20.x86_64 >>>>> 3.16.2-200.fc20.x86_64 >>>>> 3.17.0-0.rc4.git3.2.fc22.1.x86_64 >>>>> nouveau [ DRM] suspending display... >>>>> nouveau [ DRM] unpinning framebuffer(s)... >>>>> nouveau [ DRM] evicting buffers... >>>>> nouveau [ DRM] waiting for kernel channels to go idle... >>>>> nouveau [ DRM] suspending client object trees... >>>>> nouveau [ DRM] suspending kernel object tree... >>>>> ... >>>>> nouveau [ DRM] re-enabling device... >>>>> nouveau [ DRM] resuming kernel object tree... >>>>> nouveau [ VBIOS][0000:02:00.0] running init tables >>>>> nouveau [ PTHERM][0000:02:00.0] fan management: automatic >>>>> nouveau [ CLK][0000:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz >>>>> nouveau [ DRM] resuming client object trees... >>>>> nouveau [ DRM] resuming display... >>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>> >>>>> Logs(dmesg) are literally identical. >>>>> >>>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>>> >>>>> >>>> >>>> Excusez-moi, >>>> BROKEN == The display remains OFF. >>>> >>> >>> More precisely stated it looks like this: >>> >>> - Last kernel with working resume/thaw >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 >>> kernel-3.16.0-0.rc0.git9.1.fc21 >>> 2014-06-13 >>> >>> - First kernel with broken resume/thaw >>> kernel-3.16.0-0.rc0.git10.1.fc21 >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 >>> http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz >>> 2014-06-13 >>> >>> The only difference in dmesg between working and broken kernel module with drm.debug=14 is >>> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >>> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >>> >>> - git commit probably introduced breakage >>> drm/nouveau/disp: add internal representaion of output paths and connectors >>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm?id=7a014a >>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau?id=7a014a >>> 2014-06-11 >> >> Do you have any special reason to believe this to be the culprit >> (besides the fact that it has something to do with hpd)? Can you do an >> actual bisect to confirm? >> >> Thanks, >> >> -ilia > > "hpd" what?hpd = hotplug detect> First Fedora Kernel with broken video resume/thaw aka FFKWBVRT i.e. kernel-3.16.0-0.rc0.git10.1.fc21 > comes with 'patch-3.15-git10.xz' which closely resembles "git/commit/drivers/gpu/drm/nouveau?id=7a014a". > Simple as that.I see. So no reason to believe that it's not e.g. 20014cb or 377b1f1 or any one of the other patches pulled in by merge commit bc1dfff04a?> Why are you asking me that bisect formality, man is it not enough that I tested two dozen kernels.Doing a bisect would involve half as many kernels... Knowing the exact commit that breaks things is a fairly useful debug tactic, and drastically increases the chances that a problem gets fixed. Not sure why you're referring to it as a formality. git bisect start v3.16-rc1 v3.15 -- drivers/gpu/drm/nouveau (Pro tip: use a config tailored to your machine rather than a distro config if you want to spend 5 min/compile instead of 1 hour/compile) Or you can wait and hope that someone else will have the same problem and works out the commit that causes it. Or you can see if it has already been fixed in the latest kernels. Or try the experimental repo at http://cgit.freedesktop.org/~darktama/nouveau/ (a bit of a pain to build, unfortunately, you need some unknown kernel version to build against, usually ~latest works). Good luck, -ilia
poma
2014-Sep-13 21:56 UTC
[Nouveau] VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
On 13.09.2014 23:46, Ilia Mirkin wrote:> On Sat, Sep 13, 2014 at 5:25 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.09.2014 22:58, Ilia Mirkin wrote: >>> On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >>>> On 13.09.2014 07:02, poma wrote: >>>>> On 13.09.2014 06:57, poma wrote: >>>>>> >>>>>> Actually I have nothing to show cause logs are all OK. >>>>>> Haha, it seems to me that the bugs become intelligent. >>>>>> >>>>>> 3.15.10-201.fc20.x86_64 >>>>>> 3.16.2-200.fc20.x86_64 >>>>>> 3.17.0-0.rc4.git3.2.fc22.1.x86_64 >>>>>> nouveau [ DRM] suspending display... >>>>>> nouveau [ DRM] unpinning framebuffer(s)... >>>>>> nouveau [ DRM] evicting buffers... >>>>>> nouveau [ DRM] waiting for kernel channels to go idle... >>>>>> nouveau [ DRM] suspending client object trees... >>>>>> nouveau [ DRM] suspending kernel object tree... >>>>>> ... >>>>>> nouveau [ DRM] re-enabling device... >>>>>> nouveau [ DRM] resuming kernel object tree... >>>>>> nouveau [ VBIOS][0000:02:00.0] running init tables >>>>>> nouveau [ PTHERM][0000:02:00.0] fan management: automatic >>>>>> nouveau [ CLK][0000:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz >>>>>> nouveau [ DRM] resuming client object trees... >>>>>> nouveau [ DRM] resuming display... >>>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>>> nouveau 0000:02:00.0: no hotplug settings from platform >>>>>> >>>>>> Logs(dmesg) are literally identical. >>>>>> >>>>>> 3.15.10-201.fc20.x86_64 - nouveau(fb) resume & thaw PASSED, and that's all what works. >>>>>> Kernels >= 3.16 - nouveau(fb) resume & thaw BROKEN >>>>>> ALL Kernels - vesa(fb) resume & thaw BROKEN. >>>>>> >>>>>> >>>>> >>>>> Excusez-moi, >>>>> BROKEN == The display remains OFF. >>>>> >>>> >>>> More precisely stated it looks like this: >>>> >>>> - Last kernel with working resume/thaw >>>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 >>>> kernel-3.16.0-0.rc0.git9.1.fc21 >>>> 2014-06-13 >>>> >>>> - First kernel with broken resume/thaw >>>> kernel-3.16.0-0.rc0.git10.1.fc21 >>>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 >>>> http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz >>>> 2014-06-13 >>>> >>>> The only difference in dmesg between working and broken kernel module with drm.debug=14 is >>>> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >>>> [drm:drm_helper_hpd_irq_event] [CONNECTOR:18:DVI-I-1] status updated from connected to connected >>>> >>>> - git commit probably introduced breakage >>>> drm/nouveau/disp: add internal representaion of output paths and connectors >>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm?id=7a014a >>>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau?id=7a014a >>>> 2014-06-11 >>> >>> Do you have any special reason to believe this to be the culprit >>> (besides the fact that it has something to do with hpd)? Can you do an >>> actual bisect to confirm? >>> >>> Thanks, >>> >>> -ilia >> >> "hpd" what? > > hpd = hotplug detect > >> First Fedora Kernel with broken video resume/thaw aka FFKWBVRT i.e. kernel-3.16.0-0.rc0.git10.1.fc21 >> comes with 'patch-3.15-git10.xz' which closely resembles "git/commit/drivers/gpu/drm/nouveau?id=7a014a". >> Simple as that. > > I see. So no reason to believe that it's not e.g. 20014cb or 377b1f1 > or any one of the other patches pulled in by merge commit bc1dfff04a? > >> Why are you asking me that bisect formality, man is it not enough that I tested two dozen kernels. > > Doing a bisect would involve half as many kernels... Knowing the exact > commit that breaks things is a fairly useful debug tactic, and > drastically increases the chances that a problem gets fixed. Not sure > why you're referring to it as a formality. > > git bisect start v3.16-rc1 v3.15 -- drivers/gpu/drm/nouveau > > (Pro tip: use a config tailored to your machine rather than a distro > config if you want to spend 5 min/compile instead of 1 hour/compile) > > Or you can wait and hope that someone else will have the same problem > and works out the commit that causes it. > > Or you can see if it has already been fixed in the latest kernels. Or > try the experimental repo at > http://cgit.freedesktop.org/~darktama/nouveau/ (a bit of a pain to > build, unfortunately, you need some unknown kernel version to build > against, usually ~latest works). > > Good luck, > > -ilia >Man, I am not a kernel developer, I do not understand what you're saying. I did the best I could and spent a lot of time besides. If that's not enough, so be it. Thank you very much. poma
poma
2014-Sep-14 08:31 UTC
[Nouveau] VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
On 13.09.2014 23:45, Roy Spliet wrote:> Dear Poma, > > Don't get anyone wrong, your input is greatly valued. The reason why > "we" (nouveau developers) generally ask for a git bisection is because > we don't know or track specific distributions. Although your search has > narrowed the problem down (thanks for that!), we don't know how big the > difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and > kernel-3.16.0-0.rc0.git10.1.fc21. Is the difference literally just that > one patch? Or were there more patches to nouveau or drm that might have > been the culprit? So far I haven't succeeded in finding the exact > differences between the two kernels. Git bisect on the upstream kernel > on the other hand will always point at the precise patch that broke the > kernel, narrowing down the search space of the bug for developers thus > reducing the time it takes to fix your issue. Unless developers can > reproduce your issue, Unfortunately the user is the person who has to do > the bisecting. > So in short: narrowing down the search space often saves a lot of time > of the developer, reducing the time it takes to fix your issue! > Thus, if you can find the time to perform a git bisect (with the right > good/bad markers it really should not take that many kernels to build), > or if you can validate that the patch you mention *really* is the only > difference between the two kernels, it'd be greatly appreciated. > Thanks! Yours, > > Roy >Are you saying Fedora kernels aren't valid for testing purposes!? Madre m?a! Moreover, this regression is not just for my device. Apart from Ben, in "Red Fedora" there are several skilled kernel developers. Why they do not help!? Everything is on the user's back, really? WORKING VIDEO RESUME/THAW KERNEL: $ ls -1 kernel-3.16.0-0.rc0.git9.1.fc21.src/*.xz kernel-3.16.0-0.rc0.git9.1.fc21.src/linux-3.15.tar.xz kernel-3.16.0-0.rc0.git9.1.fc21.src/patch-3.15-git9.xz $ xzgrep -P '(?=.*^diff)(?=.*nouveau)' kernel-3.16.0-0.rc0.git9.1.fc21.src/patch-3.15-git9.xz diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c b/drivers/gpu/drm/nouveau/nouveau_backlight.c $ grep nouveau kernel-3.16.0-0.rc0.git9.1.fc21.src/*.patch kernel-3.16.0-0.rc0.git9.1.fc21.src/acpi-video-Add-use-native-backlight-quirk-for-the-Th.patch:"nouveau: Don't check acpi_video_backlight_support() before registering backlight" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ BROKEN VIDEO RESUME/THAW KERNEL: $ ls -1 kernel-3.16.0-0.rc0.git10.1.fc21.src/*.xz kernel-3.16.0-0.rc0.git10.1.fc21.src/linux-3.15.tar.xz kernel-3.16.0-0.rc0.git10.1.fc21.src/patch-3.15-git10.xz $ xzgrep -P '(?=.*^diff)(?=.*nouveau)' kernel-3.16.0-0.rc0.git10.1.fc21.src/patch-3.15-git10.xz diff --git a/drivers/gpu/drm/nouveau/Makefile b/drivers/gpu/drm/nouveau/Makefile diff --git a/drivers/gpu/drm/nouveau/core/core/event.c b/drivers/gpu/drm/nouveau/core/core/event.c diff --git a/drivers/gpu/drm/nouveau/core/core/object.c b/drivers/gpu/drm/nouveau/core/core/object.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/gm100.c b/drivers/gpu/drm/nouveau/core/engine/device/gm100.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nv04.c b/drivers/gpu/drm/nouveau/core/engine/device/nv04.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nv10.c b/drivers/gpu/drm/nouveau/core/engine/device/nv10.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nv20.c b/drivers/gpu/drm/nouveau/core/engine/device/nv20.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nv30.c b/drivers/gpu/drm/nouveau/core/engine/device/nv30.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nv40.c b/drivers/gpu/drm/nouveau/core/engine/device/nv40.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nv50.c b/drivers/gpu/drm/nouveau/core/engine/device/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c b/drivers/gpu/drm/nouveau/core/engine/device/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/device/nve0.c b/drivers/gpu/drm/nouveau/core/engine/device/nve0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/base.c b/drivers/gpu/drm/nouveau/core/engine/disp/base.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/conn.c b/drivers/gpu/drm/nouveau/core/engine/disp/conn.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/conn.h b/drivers/gpu/drm/nouveau/core/engine/disp/conn.h diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/dport.c b/drivers/gpu/drm/nouveau/core/engine/disp/dport.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/dport.h b/drivers/gpu/drm/nouveau/core/engine/disp/dport.h diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/gm107.c b/drivers/gpu/drm/nouveau/core/engine/disp/gm107.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nv04.c b/drivers/gpu/drm/nouveau/core/engine/disp/nv04.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c b/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nv50.h b/drivers/gpu/drm/nouveau/core/engine/disp/nv50.h diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nv84.c b/drivers/gpu/drm/nouveau/core/engine/disp/nv84.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nv94.c b/drivers/gpu/drm/nouveau/core/engine/disp/nv94.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nva0.c b/drivers/gpu/drm/nouveau/core/engine/disp/nva0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nva3.c b/drivers/gpu/drm/nouveau/core/engine/disp/nva3.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c b/drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nve0.c b/drivers/gpu/drm/nouveau/core/engine/disp/nve0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/nvf0.c b/drivers/gpu/drm/nouveau/core/engine/disp/nvf0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/outp.c b/drivers/gpu/drm/nouveau/core/engine/disp/outp.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/outp.h b/drivers/gpu/drm/nouveau/core/engine/disp/outp.h diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/outpdp.c b/drivers/gpu/drm/nouveau/core/engine/disp/outpdp.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/outpdp.h b/drivers/gpu/drm/nouveau/core/engine/disp/outpdp.h diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/piornv50.c b/drivers/gpu/drm/nouveau/core/engine/disp/piornv50.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/priv.h b/drivers/gpu/drm/nouveau/core/engine/disp/priv.h diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/sornv50.c b/drivers/gpu/drm/nouveau/core/engine/disp/sornv50.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/sornv94.c b/drivers/gpu/drm/nouveau/core/engine/disp/sornv94.c diff --git a/drivers/gpu/drm/nouveau/core/engine/disp/sornvd0.c b/drivers/gpu/drm/nouveau/core/engine/disp/sornvd0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/base.c b/drivers/gpu/drm/nouveau/core/engine/fifo/base.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/gk20a.c b/drivers/gpu/drm/nouveau/core/engine/fifo/gk20a.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c b/drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nv84.c b/drivers/gpu/drm/nouveau/core/engine/fifo/nv84.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nvc0.c b/drivers/gpu/drm/nouveau/core/engine/fifo/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nve0.c b/drivers/gpu/drm/nouveau/core/engine/fifo/nve0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h b/drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/ctxgk20a.c b/drivers/gpu/drm/nouveau/core/engine/graph/ctxgk20a.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/ctxnv108.c b/drivers/gpu/drm/nouveau/core/engine/graph/ctxnv108.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/ctxnvc0.h b/drivers/gpu/drm/nouveau/core/engine/graph/ctxnvc0.h diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c b/drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/ctxnvf0.c b/drivers/gpu/drm/nouveau/core/engine/graph/ctxnvf0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/gk20a.c b/drivers/gpu/drm/nouveau/core/engine/graph/gk20a.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/nv50.c b/drivers/gpu/drm/nouveau/core/engine/graph/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c b/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.h b/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.h diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/nve4.c b/drivers/gpu/drm/nouveau/core/engine/graph/nve4.c diff --git a/drivers/gpu/drm/nouveau/core/engine/software/nv50.c b/drivers/gpu/drm/nouveau/core/engine/software/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/engine/software/nv50.h b/drivers/gpu/drm/nouveau/core/engine/software/nv50.h diff --git a/drivers/gpu/drm/nouveau/core/engine/software/nvc0.c b/drivers/gpu/drm/nouveau/core/engine/software/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/include/core/class.h b/drivers/gpu/drm/nouveau/core/include/core/class.h diff --git a/drivers/gpu/drm/nouveau/core/include/core/event.h b/drivers/gpu/drm/nouveau/core/include/core/event.h diff --git a/drivers/gpu/drm/nouveau/core/include/engine/disp.h b/drivers/gpu/drm/nouveau/core/include/engine/disp.h diff --git a/drivers/gpu/drm/nouveau/core/include/engine/fifo.h b/drivers/gpu/drm/nouveau/core/include/engine/fifo.h diff --git a/drivers/gpu/drm/nouveau/core/include/engine/graph.h b/drivers/gpu/drm/nouveau/core/include/engine/graph.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/bios/conn.h b/drivers/gpu/drm/nouveau/core/include/subdev/bios/conn.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/bios/dp.h b/drivers/gpu/drm/nouveau/core/include/subdev/bios/dp.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/clock.h b/drivers/gpu/drm/nouveau/core/include/subdev/clock.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/fb.h b/drivers/gpu/drm/nouveau/core/include/subdev/fb.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/gpio.h b/drivers/gpu/drm/nouveau/core/include/subdev/gpio.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/i2c.h b/drivers/gpu/drm/nouveau/core/include/subdev/i2c.h diff --git a/drivers/gpu/drm/nouveau/core/include/subdev/ibus.h b/drivers/gpu/drm/nouveau/core/include/subdev/ibus.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/bar/base.c b/drivers/gpu/drm/nouveau/core/subdev/bar/base.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c b/drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/bios/base.c b/drivers/gpu/drm/nouveau/core/subdev/bios/base.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/bios/conn.c b/drivers/gpu/drm/nouveau/core/subdev/bios/conn.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/bios/dp.c b/drivers/gpu/drm/nouveau/core/subdev/bios/dp.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/bios/init.c b/drivers/gpu/drm/nouveau/core/subdev/bios/init.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/base.c b/drivers/gpu/drm/nouveau/core/subdev/clock/base.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nv04.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nv04.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nv40.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nv40.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nv50.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nvaa.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nvaa.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nvc0.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/clock/nve0.c b/drivers/gpu/drm/nouveau/core/subdev/clock/nve0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/gk20a.c b/drivers/gpu/drm/nouveau/core/subdev/fb/gk20a.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/priv.h b/drivers/gpu/drm/nouveau/core/subdev/fb/priv.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/ramgk20a.c b/drivers/gpu/drm/nouveau/core/subdev/fb/ramgk20a.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/ramnv50.c b/drivers/gpu/drm/nouveau/core/subdev/fb/ramnv50.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c b/drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c b/drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/fb/ramnve0.c b/drivers/gpu/drm/nouveau/core/subdev/fb/ramnve0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/base.c b/drivers/gpu/drm/nouveau/core/subdev/gpio/base.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/nv10.c b/drivers/gpu/drm/nouveau/core/subdev/gpio/nv10.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/nv50.c b/drivers/gpu/drm/nouveau/core/subdev/gpio/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/nv92.c b/drivers/gpu/drm/nouveau/core/subdev/gpio/nv92.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/nvd0.c b/drivers/gpu/drm/nouveau/core/subdev/gpio/nvd0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/nve0.c b/drivers/gpu/drm/nouveau/core/subdev/gpio/nve0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/gpio/priv.h b/drivers/gpu/drm/nouveau/core/subdev/gpio/priv.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/anx9805.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/anx9805.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/aux.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/aux.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/base.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/base.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/bit.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/bit.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nv04.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/nv04.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nv4e.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/nv4e.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.h b/drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nv94.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/nv94.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nvd0.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/nvd0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/nve0.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/nve0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/pad.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/pad.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/pad.h b/drivers/gpu/drm/nouveau/core/subdev/i2c/pad.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/padnv04.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/padnv04.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/padnv94.c b/drivers/gpu/drm/nouveau/core/subdev/i2c/padnv94.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/port.h b/drivers/gpu/drm/nouveau/core/subdev/i2c/port.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/i2c/priv.h b/drivers/gpu/drm/nouveau/core/subdev/i2c/priv.h diff --git a/drivers/gpu/drm/nouveau/core/subdev/ibus/gk20a.c b/drivers/gpu/drm/nouveau/core/subdev/ibus/gk20a.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/mc/nv50.c b/drivers/gpu/drm/nouveau/core/subdev/mc/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/mc/nv98.c b/drivers/gpu/drm/nouveau/core/subdev/mc/nv98.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/mc/nvc0.c b/drivers/gpu/drm/nouveau/core/subdev/mc/nvc0.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/mxm/nv50.c b/drivers/gpu/drm/nouveau/core/subdev/mxm/nv50.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/ic.c b/drivers/gpu/drm/nouveau/core/subdev/therm/ic.c diff --git a/drivers/gpu/drm/nouveau/core/subdev/therm/nva3.c b/drivers/gpu/drm/nouveau/core/subdev/therm/nva3.c diff --git a/drivers/gpu/drm/nouveau/dispnv04/dac.c b/drivers/gpu/drm/nouveau/dispnv04/dac.c diff --git a/drivers/gpu/drm/nouveau/dispnv04/dfp.c b/drivers/gpu/drm/nouveau/dispnv04/dfp.c diff --git a/drivers/gpu/drm/nouveau/dispnv04/disp.c b/drivers/gpu/drm/nouveau/dispnv04/disp.c diff --git a/drivers/gpu/drm/nouveau/dispnv04/tvnv04.c b/drivers/gpu/drm/nouveau/dispnv04/tvnv04.c diff --git a/drivers/gpu/drm/nouveau/dispnv04/tvnv17.c b/drivers/gpu/drm/nouveau/dispnv04/tvnv17.c diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c b/drivers/gpu/drm/nouveau/nouveau_backlight.c diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c b/drivers/gpu/drm/nouveau/nouveau_connector.c diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.h b/drivers/gpu/drm/nouveau/nouveau_connector.h diff --git a/drivers/gpu/drm/nouveau/nouveau_crtc.h b/drivers/gpu/drm/nouveau/nouveau_crtc.h diff --git a/drivers/gpu/drm/nouveau/nouveau_display.c b/drivers/gpu/drm/nouveau/nouveau_display.c diff --git a/drivers/gpu/drm/nouveau/nouveau_dp.c b/drivers/gpu/drm/nouveau/nouveau_dp.c diff --git a/drivers/gpu/drm/nouveau/nouveau_encoder.h b/drivers/gpu/drm/nouveau/nouveau_encoder.h diff --git a/drivers/gpu/drm/nouveau/nouveau_fence.c b/drivers/gpu/drm/nouveau/nouveau_fence.c diff --git a/drivers/gpu/drm/nouveau/nouveau_ioc32.c b/drivers/gpu/drm/nouveau/nouveau_ioc32.c diff --git a/drivers/gpu/drm/nouveau/nouveau_vga.c b/drivers/gpu/drm/nouveau/nouveau_vga.c diff --git a/drivers/gpu/drm/nouveau/nv50_display.c b/drivers/gpu/drm/nouveau/nv50_display.c $ grep nouveau kernel-3.16.0-0.rc0.git10.1.fc21.src/*.patch kernel-3.16.0-0.rc0.git10.1.fc21.src/acpi-video-Add-use-native-backlight-quirk-for-the-Th.patch:"nouveau: Don't check acpi_video_backlight_support() before registering backlight" http://git.linuxtv.org/cgit.cgi/media_build.git Whether the nouveau project has something like this? poma
Apparently Analagous Threads
- VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
- VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
- VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
- VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively
- VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively