Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On 14.09.2014 11:53, Roy Spliet wrote: Op 14-09-14 om 10:31 schreef poma: 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!? No, that's not what I'm saying. You used a Fedora kernel which is fairly recent and found a bug. However, they're less useful for pinpointing your problem to the offending bit of code, as you demonstrate below. Madre mía! Salud... 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
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On Mon, Sep 15, 2014 at 4:23 AM, poma pomidorabelis...@gmail.com wrote: Chipset: G98 (NV98) Family : NV50 WORKING VIDEO RESUME(S3) 3.15.0-rc8.1.git.7a014a8 3.15.0-rc8.2.git.456b057 3.15.0-rc8.3.git.b8407c9 3.15.0-rc8.4.git.bb7ef1e BROKEN VIDEO RESUME(S3) STARTING WITH: 3.15.0-rc8.5.git.415f12e commit 415f12efc1b2308411b2cbc3e82666b3db8a7758 Author: Ben Skeggs bske...@redhat.com Date: Wed May 21 11:24:43 2014 +1000 drm/nv50/disp: start removing direct vbios parsing from supervisor Signed-off-by: Ben Skeggs bske...@redhat.com https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e Looks like the same issue as reported in https://bugs.freedesktop.org/show_bug.cgi?id=83550 Ben, any ideas? Poma, can you attach your vbios to the bug above? -ilia ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On 15.09.2014 15:36, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 4:23 AM, poma pomidorabelis...@gmail.com wrote: Chipset: G98 (NV98) Family : NV50 WORKING VIDEO RESUME(S3) 3.15.0-rc8.1.git.7a014a8 3.15.0-rc8.2.git.456b057 3.15.0-rc8.3.git.b8407c9 3.15.0-rc8.4.git.bb7ef1e BROKEN VIDEO RESUME(S3) STARTING WITH: 3.15.0-rc8.5.git.415f12e commit 415f12efc1b2308411b2cbc3e82666b3db8a7758 Author: Ben Skeggs bske...@redhat.com Date: Wed May 21 11:24:43 2014 +1000 drm/nv50/disp: start removing direct vbios parsing from supervisor Signed-off-by: Ben Skeggs bske...@redhat.com https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e Looks like the same issue as reported in https://bugs.freedesktop.org/show_bug.cgi?id=83550 Ben, any ideas? Poma, can you attach your vbios to the bug above? -ilia A Video BIOS dumped. poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On Mon, Sep 15, 2014 at 1:28 PM, poma pomidorabelis...@gmail.com wrote: On 15.09.2014 15:36, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 4:23 AM, poma pomidorabelis...@gmail.com wrote: Chipset: G98 (NV98) Family : NV50 WORKING VIDEO RESUME(S3) 3.15.0-rc8.1.git.7a014a8 3.15.0-rc8.2.git.456b057 3.15.0-rc8.3.git.b8407c9 3.15.0-rc8.4.git.bb7ef1e BROKEN VIDEO RESUME(S3) STARTING WITH: 3.15.0-rc8.5.git.415f12e commit 415f12efc1b2308411b2cbc3e82666b3db8a7758 Author: Ben Skeggs bske...@redhat.com Date: Wed May 21 11:24:43 2014 +1000 drm/nv50/disp: start removing direct vbios parsing from supervisor Signed-off-by: Ben Skeggs bske...@redhat.com https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e Looks like the same issue as reported in https://bugs.freedesktop.org/show_bug.cgi?id=83550 Ben, any ideas? Poma, can you attach your vbios to the bug above? -ilia A Video BIOS dumped. Thanks! If possible, please provide kernel logs (which include the initial boot and the resume) for both 415f12efc1 and 415f12efc1^ (i.e. parent commit). Please boot those kernels with 'nouveau.debug=trace,PDISP=spam' so that we get the maximal debug info. In order for that to work, you'll need to change CONFIG_NOUVEAU_DEBUG to 7 (spam). [Don't use such kernels for anything other than debugging, setting the debug level so high adds a ton of code and will slow things down significantly.] -ilia ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On 16.09.2014 01:21, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 1:28 PM, poma pomidorabelis...@gmail.com wrote: On 15.09.2014 15:36, Ilia Mirkin wrote: On Mon, Sep 15, 2014 at 4:23 AM, poma pomidorabelis...@gmail.com wrote: Chipset: G98 (NV98) Family : NV50 WORKING VIDEO RESUME(S3) 3.15.0-rc8.1.git.7a014a8 3.15.0-rc8.2.git.456b057 3.15.0-rc8.3.git.b8407c9 3.15.0-rc8.4.git.bb7ef1e BROKEN VIDEO RESUME(S3) STARTING WITH: 3.15.0-rc8.5.git.415f12e commit 415f12efc1b2308411b2cbc3e82666b3db8a7758 Author: Ben Skeggs bske...@redhat.com Date: Wed May 21 11:24:43 2014 +1000 drm/nv50/disp: start removing direct vbios parsing from supervisor Signed-off-by: Ben Skeggs bske...@redhat.com https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau/core/engine/disp/nv50.c?id=415f12e Looks like the same issue as reported in https://bugs.freedesktop.org/show_bug.cgi?id=83550 Ben, any ideas? Poma, can you attach your vbios to the bug above? -ilia A Video BIOS dumped. Thanks! If possible, please provide kernel logs (which include the initial boot and the resume) for both 415f12efc1 and 415f12efc1^ (i.e. parent commit). Please boot those kernels with 'nouveau.debug=trace,PDISP=spam' so that we get the maximal debug info. In order for that to work, you'll need to change CONFIG_NOUVEAU_DEBUG to 7 (spam). [Don't use such kernels for anything other than debugging, setting the debug level so high adds a ton of code and will slow things down significantly.] -ilia In 415f12e proximity no kernel is useful, resumed machine is stuck. The display remains OFF meaning everything else works(likely to Daredevil), only applies to recent kernels. poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [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
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
Op 14-09-14 om 10:31 schreef poma: 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!? No, that's not what I'm saying. You used a Fedora kernel which is fairly recent and found a bug. However, they're less useful for pinpointing your problem to the offending bit of code, as you demonstrate below. Madre mía! Salud... 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
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
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][:02:00.0] running init tables nouveau [ PTHERM][:02:00.0] fan management: automatic nouveau [ CLK][:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz nouveau [ DRM] resuming client object trees... nouveau [ DRM] resuming display... nouveau :02:00.0: no hotplug settings from platform nouveau :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 - Ref. fdbs Video failed on resume from suspend https://bugs.freedesktop.org/show_bug.cgi?id=77599 https://bugs.freedesktop.org/show_bug.cgi?id=80506 poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On Sat, Sep 13, 2014 at 4:52 PM, poma pomidorabelis...@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][:02:00.0] running init tables nouveau [ PTHERM][:02:00.0] fan management: automatic nouveau [ CLK][:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz nouveau [ DRM] resuming client object trees... nouveau [ DRM] resuming display... nouveau :02:00.0: no hotplug settings from platform nouveau :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 - Ref. fdbs Video failed on resume from suspend https://bugs.freedesktop.org/show_bug.cgi?id=77599 https://bugs.freedesktop.org/show_bug.cgi?id=80506 poma ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [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 pomidorabelis...@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][:02:00.0] running init tables nouveau [ PTHERM][:02:00.0] fan management: automatic nouveau [ CLK][:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz nouveau [ DRM] resuming client object trees... nouveau [ DRM] resuming display... nouveau :02:00.0: no hotplug settings from platform nouveau :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@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [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 pomidorabelis...@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][:02:00.0] running init tables nouveau [ PTHERM][:02:00.0] fan management: automatic nouveau [ CLK][:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz nouveau [ DRM] resuming client object trees... nouveau [ DRM] resuming display... nouveau :02:00.0: no hotplug settings from platform nouveau :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@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] VGA resume thaw (wake up from S3 S4) broken - kernel(nouveau) exclusively
On Sat, Sep 13, 2014 at 5:25 PM, poma pomidorabelis...@gmail.com wrote: On 13.09.2014 22:58, Ilia Mirkin wrote: On Sat, Sep 13, 2014 at 4:52 PM, poma pomidorabelis...@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][:02:00.0] running init tables nouveau [ PTHERM][:02:00.0] fan management: automatic nouveau [ CLK][:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz nouveau [ DRM] resuming client object trees... nouveau [ DRM] resuming display... nouveau :02:00.0: no hotplug settings from platform nouveau :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 ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [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 pomidorabelis...@gmail.com wrote: On 13.09.2014 22:58, Ilia Mirkin wrote: On Sat, Sep 13, 2014 at 4:52 PM, poma pomidorabelis...@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][:02:00.0] running init tables nouveau [ PTHERM][:02:00.0] fan management: automatic nouveau [ CLK][:02:00.0] --: core 566 MHz shader 1400 MHz memory 399 MHz nouveau [ DRM] resuming client object trees... nouveau [ DRM] resuming display... nouveau :02:00.0: no hotplug settings from platform nouveau :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 ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
