Skip to contentSkip to conversation

VGA resume & thaw (wake up from S3 & S4) broken - kernel exclusively

DISCUSSION poma 4 participants 16 messages Sep 13, 2014 – Sep 30, 2014 13 messages not in the archive

Subsystems (3)
lore
Share & tools
lore

poma

author
#0 lore raw

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.

Have a nice weekend folks.

poma

author
#1 lore raw
Quoted 21 lines · poma

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...
Quoted 10 lines

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.

poma

#3 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 27 lines · poma
Quoted 26 lines · poma

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.

Quoted 9 lines
Quoted 5 lines

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

#5 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 55 lines · poma
Quoted 27 lines · poma
Quoted 26 lines · poma

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.

Quoted 9 lines
Quoted 5 lines

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

Quoted 5 lines

- 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

Quoted 9 lines

- 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

#7 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 62 lines · Ilia Mirkin
Quoted 55 lines · poma
Quoted 27 lines · poma
Quoted 26 lines · poma

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.

Quoted 9 lines
Quoted 5 lines

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

Quoted 5 lines

- 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

Quoted 7 lines

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

#9 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive

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:

Quoted 81 lines · Ilia Mirkin
Quoted 58 lines · poma
Quoted 52 lines · poma
Quoted 26 lines · poma
Quoted 25 lines

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.

Quoted 8 lines
Quoted 5 lines

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

Quoted 5 lines

- 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

Quoted 7 lines

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 [email protected]
http://lists.freedesktop.org/mailman/listinfo/nouveau

#26 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 67 lines · poma
Quoted 66 lines · Ilia Mirkin
Quoted 55 lines · poma
Quoted 27 lines · poma
Quoted 26 lines · poma

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.

Quoted 9 lines
Quoted 5 lines

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

Quoted 5 lines

- 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?

Quoted 5 lines
Quoted 3 lines

Thanks,

-ilia

"hpd" what?

hpd = hotplug detect

Quoted 3 lines

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?

Quoted 1 line

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

#28 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 104 lines · Ilia Mirkin
Quoted 67 lines · poma
Quoted 66 lines · Ilia Mirkin
Quoted 55 lines · poma
Quoted 27 lines · poma
Quoted 26 lines · poma

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.

Quoted 9 lines
Quoted 5 lines

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

Quoted 5 lines

- 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?

Quoted 5 lines
Quoted 3 lines

Thanks,

-ilia

"hpd" what?

hpd = hotplug detect

Quoted 3 lines

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?

Quoted 1 line

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).

Quoted 4 lines

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

#11 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 24 lines · Roy Spliet

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,

Quoted 2 lines

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
drivers/gpu/drm/nouveau/nouveau_backlight.c +0 -0
$ 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
drivers/gpu/drm/nouveau/Makefile +0 -0
drivers/gpu/drm/nouveau/core/core/event.c +0 -0
drivers/gpu/drm/nouveau/core/core/object.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/gm100.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv10.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv20.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv30.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv40.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/base.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/conn.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/conn.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/dport.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/dport.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/gm107.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv84.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv94.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nva0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nva3.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nvf0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outp.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outp.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outpdp.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outpdp.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/piornv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/priv.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornv94.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornvd0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/base.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nv84.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxgk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnv108.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnvc0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnvf0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nve4.c +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/include/core/class.h +0 -0
drivers/gpu/drm/nouveau/core/include/core/event.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/disp.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/fifo.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/graph.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/bios/conn.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/bios/dp.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/clock.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/fb.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/gpio.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/i2c.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/ibus.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/bar/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/conn.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/dp.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/init.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv40.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nvaa.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramgk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv10.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv92.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/anx9805.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/aux.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/bit.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv4e.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv94.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/pad.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/pad.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv94.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/port.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/ibus/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nv98.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mxm/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/therm/ic.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/therm/nva3.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/dac.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/dfp.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/disp.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/tvnv04.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/tvnv17.c +0 -0
drivers/gpu/drm/nouveau/nouveau_backlight.c +0 -0
drivers/gpu/drm/nouveau/nouveau_connector.c +0 -0
drivers/gpu/drm/nouveau/nouveau_connector.h +0 -0
drivers/gpu/drm/nouveau/nouveau_crtc.h +0 -0
drivers/gpu/drm/nouveau/nouveau_display.c +0 -0
drivers/gpu/drm/nouveau/nouveau_dp.c +0 -0
drivers/gpu/drm/nouveau/nouveau_encoder.h +0 -0
drivers/gpu/drm/nouveau/nouveau_fence.c +0 -0
drivers/gpu/drm/nouveau/nouveau_ioc32.c +0 -0
drivers/gpu/drm/nouveau/nouveau_vga.c +0 -0
drivers/gpu/drm/nouveau/nv50_display.c +0 -0
$ 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

#13 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive

Op 14-09-14 om 10:31 schreef poma:

Quoted 25 lines · Roy Spliet
Quoted 24 lines

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,

Quoted 3 lines
Quoted 2 lines

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.

Quoted 1 line

Madre mía!

Salud...

Quoted 166 lines

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
drivers/gpu/drm/nouveau/nouveau_backlight.c +0 -0
$ 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
drivers/gpu/drm/nouveau/Makefile +0 -0
drivers/gpu/drm/nouveau/core/core/event.c +0 -0
drivers/gpu/drm/nouveau/core/core/object.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/gm100.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv10.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv20.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv30.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv40.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/base.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/conn.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/conn.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/dport.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/dport.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/gm107.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv84.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv94.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nva0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nva3.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nvf0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outp.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outp.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outpdp.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outpdp.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/piornv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/priv.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornv94.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornvd0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/base.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nv84.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxgk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnv108.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnvc0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnvf0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nve4.c +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/include/core/class.h +0 -0
drivers/gpu/drm/nouveau/core/include/core/event.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/disp.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/fifo.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/graph.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/bios/conn.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/bios/dp.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/clock.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/fb.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/gpio.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/i2c.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/ibus.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/bar/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/conn.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/dp.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/init.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv40.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nvaa.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramgk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv10.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv92.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/anx9805.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/aux.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/bit.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv4e.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv94.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/pad.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/pad.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv94.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/port.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/ibus/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nv98.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mxm/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/therm/ic.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/therm/nva3.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/dac.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/dfp.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/disp.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/tvnv04.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/tvnv17.c +0 -0
drivers/gpu/drm/nouveau/nouveau_backlight.c +0 -0
drivers/gpu/drm/nouveau/nouveau_connector.c +0 -0
drivers/gpu/drm/nouveau/nouveau_connector.h +0 -0
drivers/gpu/drm/nouveau/nouveau_crtc.h +0 -0
drivers/gpu/drm/nouveau/nouveau_display.c +0 -0
drivers/gpu/drm/nouveau/nouveau_dp.c +0 -0
drivers/gpu/drm/nouveau/nouveau_encoder.h +0 -0
drivers/gpu/drm/nouveau/nouveau_fence.c +0 -0
drivers/gpu/drm/nouveau/nouveau_ioc32.c +0 -0
drivers/gpu/drm/nouveau/nouveau_vga.c +0 -0
drivers/gpu/drm/nouveau/nv50_display.c +0 -0
Quoted 2 lines
$ 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"

This is precisely why the user is often asked to perform a git bisect. There's a mountain of files touched between the two Fedora kernels (xzgrep output), corresponding witk something like 20 patches. Any of those could be the offender. We don't know, and now the search space still is 20 patches. Git bisect is nothing more than taking a kernel, marking a good and a bad kernel in terms of patches in the git history (like you requested below), and compiling and testing a few. Git makes sure that every kernel you try roughly halves the search space, so you'll have the offender in 5 steps. It's not that we hate you and want you to suffer on complex procedures preferably including kernel compiles, but this process just gives more precise information to the developers... and I bet it takes less time than trying random kernels from Koji to narrow down the search space.
Anyway, we're not forcing you to do a bisect. If you don't, that's fine, but it probably takes longer to find the specific bug. We'd be grateful if you do though, as it'll save a lot of time from the hard-working developers that rather want to focus their attention on problems like reclocking and getting the latest generations of cards to work.

Quoted 2 lines

http://git.linuxtv.org/cgit.cgi/media_build.git
Whether the nouveau project has something like this?

We do, it's right here: http://cgit.freedesktop.org/nouveau/linux-2.6/log/?h=linux-3.16 . Problem is that it's not aligned with distributions' kernels, so it doesn't tell you a lot.
To come back to putting all the burden on the user: bugs don't always trigger for everyone. I've never seen this bug before. Most often it's a software error that only hits on one or several video cards in very specific configurations (like dual monitor, specific output port, optimus, VRAM), and developers don't always have this configuration available for testing. If developers can't reproduce and they don't know where to look, they're not going to be able to fix a bug.

Roy

Quoted 2 lines

poma

#15 lore raw

Re: [Nouveau] VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 234 lines · Roy Spliet

Op 14-09-14 om 10:31 schreef poma:

Quoted 25 lines · Roy Spliet
Quoted 24 lines

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,

Quoted 3 lines
Quoted 2 lines

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.

Quoted 1 line

Madre mía!

Salud...

Quoted 166 lines

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
drivers/gpu/drm/nouveau/nouveau_backlight.c +0 -0
$ 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
drivers/gpu/drm/nouveau/Makefile +0 -0
drivers/gpu/drm/nouveau/core/core/event.c +0 -0
drivers/gpu/drm/nouveau/core/core/object.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/gm100.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv10.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv20.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv30.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv40.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/device/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/base.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/conn.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/conn.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/dport.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/dport.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/gm107.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv84.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nv94.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nva0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nva3.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/nvf0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outp.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outp.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outpdp.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/outpdp.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/piornv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/priv.h +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornv94.c +0 -0
drivers/gpu/drm/nouveau/core/engine/disp/sornvd0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/base.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nv84.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/fifo/nve0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxgk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnv108.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnvc0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnve4.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/ctxnvf0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nvc0.h +0 -0
drivers/gpu/drm/nouveau/core/engine/graph/nve4.c +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/engine/software/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/include/core/class.h +0 -0
drivers/gpu/drm/nouveau/core/include/core/event.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/disp.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/fifo.h +0 -0
drivers/gpu/drm/nouveau/core/include/engine/graph.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/bios/conn.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/bios/dp.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/clock.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/fb.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/gpio.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/i2c.h +0 -0
drivers/gpu/drm/nouveau/core/include/subdev/ibus.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/bar/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/conn.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/dp.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/bios/init.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv40.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nva3.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nvaa.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/clock/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramgk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/fb/ramnve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv10.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nv92.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/gpio/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/anx9805.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/aux.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/base.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/bit.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv4e.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv50.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nv94.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nvd0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/nve0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/pad.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/pad.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv04.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/padnv94.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/port.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/i2c/priv.h +0 -0
drivers/gpu/drm/nouveau/core/subdev/ibus/gk20a.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nv98.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mc/nvc0.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/mxm/nv50.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/therm/ic.c +0 -0
drivers/gpu/drm/nouveau/core/subdev/therm/nva3.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/dac.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/dfp.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/disp.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/tvnv04.c +0 -0
drivers/gpu/drm/nouveau/dispnv04/tvnv17.c +0 -0
drivers/gpu/drm/nouveau/nouveau_backlight.c +0 -0
drivers/gpu/drm/nouveau/nouveau_connector.c +0 -0
drivers/gpu/drm/nouveau/nouveau_connector.h +0 -0
drivers/gpu/drm/nouveau/nouveau_crtc.h +0 -0
drivers/gpu/drm/nouveau/nouveau_display.c +0 -0
drivers/gpu/drm/nouveau/nouveau_dp.c +0 -0
drivers/gpu/drm/nouveau/nouveau_encoder.h +0 -0
drivers/gpu/drm/nouveau/nouveau_fence.c +0 -0
drivers/gpu/drm/nouveau/nouveau_ioc32.c +0 -0
drivers/gpu/drm/nouveau/nouveau_vga.c +0 -0
drivers/gpu/drm/nouveau/nv50_display.c +0 -0
Quoted 2 lines
$ 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"

This is precisely why the user is often asked to perform a git bisect. There's a mountain of files touched between the two Fedora kernels (xzgrep output), corresponding witk something like 20 patches. Any of those could be the offender. We don't know, and now the search space still is 20 patches. Git bisect is nothing more than taking a kernel, marking a good and a bad kernel in terms of patches in the git history (like you requested below), and compiling and testing a few. Git makes sure that every kernel you try roughly halves the search space, so you'll have the offender in 5 steps.
It's not that we hate you and want you to suffer on complex procedures preferably including kernel compiles, but this process just gives more precise information to the developers... and I bet it takes less time than trying random kernels from Koji to narrow down the search space. Anyway, we're not forcing you to do a bisect. If you don't, that's fine, but it probably takes longer to find the specific bug. We'd be grateful if you do though, as it'll save a lot of time from the hard-working developers that rather want to focus their attention on problems like reclocking and getting the latest generations of cards to work.

Quoted 2 lines

http://git.linuxtv.org/cgit.cgi/media_build.git
Whether the nouveau project has something like this?

We do, it's right here:
http://cgit.freedesktop.org/nouveau/linux-2.6/log/?h=linux-3.16 . Problem is that it's not aligned with distributions' kernels, so it doesn't tell you a lot.
To come back to putting all the burden on the user: bugs don't always trigger for everyone. I've never seen this bug before. Most often it's a software error that only hits on one or several video cards in very specific configurations (like dual monitor, specific output port, optimus, VRAM), and developers don't always have this configuration available for testing. If developers can't reproduce and they don't know where to look, they're not going to be able to fix a bug.

Quoted 1 line

Roy

You guys were in at least right in one, in this particular case Fedora kernel is unusable. .
..
...
Tested with vanilla...

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 <[email protected]>
Date:   Wed May 21 11:24:43 2014 +1000

drm/nv50/disp: start removing direct vbios parsing from supervisor

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

...
CONTINUED VIDEO RESUME(S3) BROKENNESS WITH:

3.15.0-rc8.7.git.3b52a1f
3.15.0-rc8.9.git.1ecee1c
3.15.0-rc8.13.git.8894f49
3.15.0-rc8.22.git.1ae5a62
3.15.0-rc8.100.git.fcc8fd7

==========================

PROCEDURE (especially for fellow tester adamwill)

$ mkdir RESUMEVIDEOTEST
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
$ cd linux-next/
$ git log /* search for offended commit & copy git_sha_short */
$ git archive --format=tar.gz -o ../RESUMEVIDEOTEST/3.15.0-rc8.5.git.<git_sha_short>.tar.gz <git_sha_short>
$ cd ../RESUMEVIDEOTEST/
$ ls
3.15.0-rc8.5.git.415f12e.tar.gz
$ tar xf 3.15.0-rc8.5.git.415f12e.tar.gz
$ cp ../config-mini-3.17.0-0.rc4.git4.1 .config /* mostly removed unnecessary modules via "make menuconfig" */
$ time make -j3 bzImage && time make -j3 modules /* 5m51.210s & 8m24.461s */
$ su
# make -j3 install && make -j3 modules_install
# dracut --kver 3.15.0-rc8.5.git.415f12e -vf
# systemctl reboot
...
$ uname -r
3.15.0-rc8.5.git.415f12e
$ systemctl suspend
...
RESUME(S3)

finito

_______________________________________________
kernel mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/kernel

#17 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 22 lines · poma

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 <[email protected]>
Date:   Wed May 21 11:24:43 2014 +1000
Quoted 6 lines

drm/nv50/disp: start removing direct vbios parsing from supervisor

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

#19 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 30 lines · Ilia Mirkin
Quoted 22 lines · poma

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 <[email protected]>
Date:   Wed May 21 11:24:43 2014 +1000
Quoted 6 lines

drm/nv50/disp: start removing direct vbios parsing from supervisor

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

Quoted 8 lines

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

#21 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 33 lines · poma
Quoted 32 lines · Ilia Mirkin
Quoted 22 lines · poma

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 <[email protected]>
Date:   Wed May 21 11:24:43 2014 +1000
Quoted 6 lines

drm/nv50/disp: start removing direct vbios parsing from supervisor

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

Quoted 8 lines
Quoted 6 lines

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

#23 lore raw

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel(nouveau) exclusively

In reply to a message not in the archive
Quoted 52 lines · Ilia Mirkin
Quoted 33 lines · poma
Quoted 32 lines · Ilia Mirkin
Quoted 22 lines · poma

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 <[email protected]>
Date:   Wed May 21 11:24:43 2014 +1000
Quoted 6 lines

drm/nv50/disp: start removing direct vbios parsing from supervisor

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

Quoted 8 lines
Quoted 6 lines

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.]

Quoted 2 lines

-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