Bug 5776

Please report the archive created by nvidia-bug-report.sh run root.

Are you able to connect via ssh from another computer when the problem occurs ?
(would be better to run nvidia-bug-report.sh in this case).

Created attachment 2231 [details]
nvidia bug report

wrong file. Please verify your local directory.

Created attachment 2232 [details]
nvidia bug report

Hi Nicolas and thanks,
Please find the bug report.
I've done this one with ssh after the screen goes black. So i can ssh , it's not a total freeze.
This problem was not present on F31.

Created attachment 2233 [details]
bug report

Created attachment 2234 [details]
nvidia bug report

Hi Nicolas, had you the time to see the bug report ? 

Thanks

HI, Nicolas and Herault

I was able to duplicate this issue:
" When I lock the screen (Super+L), my screen won't wake up. I can't even have a TTY. 
I must reset the computer. I have official the latest rpmfusion kmod. 
"

I have duplicated and found the solution; the issue is with the drivers published in the rpmfusion repository.

there are two drivers:
long time lived Version: 450.80.02    Release Date: 	2020.9.30 
short time lived Version: 455.28      Release Date: 	2020.10.7  

As always the long one is the one to be used because is stable; the short one is the one on development with bugs.

So the driver published in the rpmfusion repo is the 455 which is the short time one.

This 455 driver no only have this issue also have another issue related the Thinkpad Thunderbolt Dock 2 gen that use usb-c connection. Everytime you disconnect the cable it freeze the computer also you can't boot the computer with the dock connected because it will freeze.

I am using a Thinkpad p52 with Fedora 33 (32 before) and downgrade to 450 nvidia driver to fix this issue.

Basically please don't push the short time lived driver into the repo please, especially the nvidia driver's.

Hope It will help you.

(In reply to victor sosa from comment #8)
> HI, Nicolas and Herault
> 
> I was able to duplicate this issue:
Thks for the report.
However please attach the archive generated to nvidia-bug-report.sh in this report and eventually forward the bug to nvidia at devhelp.nvidia.com

As reports are valuable, but without forward to nvidia and technical info, they are just "heard says". 

As a side, note I've prevented f31 from upgrading to the new short term release on purpose of stability. But as Fedora is concerned, we will follow whatever is the latest stable and will eventually provide a "longterm" driver alternative if any issue with the "latest short term" stable default.

This may be provided as a module as effort permit.
See also https://rpmfusion.org/Contribute

HI, Nicolas

 Herault alredy sent the report; that should enough.

In any case I could send my report later; I have to reinstall the drivers and duplicate the issue;

(In reply to Herault from comment #7)
> Hi Nicolas, had you the time to see the bug report ? 

From your report:
[    0.000000] secureboot: Secure boot enabled

You need to disable secure boot so the nvidia driver can load. From what I've seen, you never used the nvidia proprietary driver and felt back to nouveau.
(which seems appropriate if it fits your needs).

It will be interesting to see if you can reproduce the lock with the nvidia driver been removed. In which case please consider a report to fedora of the kernel component (at bugzilla.redhat.com).


Once that tested, please disable secure boot in your EFI/bios and re-install the nvidia driver.


@victor sosa
If it's the same for you, you can duplicate the protocol. If not, please submit a "separate" ticket with the nvidia-bug-report.sh archive attached.

Created attachment 2241 [details]
nvidia-bug-report

@Nicolas

This is my nvidia-bug-report using the driver 455 on Fedora 33 with Thinkpad 52 and Quadro P1000

(In reply to Nicolas Chauvet from comment #11)
> (In reply to Herault from comment #7)
> > Hi Nicolas, had you the time to see the bug report ? 
> 
> From your report:
> [    0.000000] secureboot: Secure boot enabled
> 
> You need to disable secure boot so the nvidia driver can load. From what
> I've seen, you never used the nvidia proprietary driver and felt back to
> nouveau.
> (which seems appropriate if it fits your needs).
> 
> It will be interesting to see if you can reproduce the lock with the nvidia
> driver been removed. In which case please consider a report to fedora of the
> kernel component (at bugzilla.redhat.com).
> 
> 
> Once that tested, please disable secure boot in your EFI/bios and re-install
> the nvidia driver.

@Nicolas : 
Hi Nicolas , 

I think we're going in the wrong direction. The nvidia proprietary driver is well loaded and I've been using it for years without any problem. 

lsmod | grep nvidia
nvidia_drm 57344 6
nvidia_modeset 1216512 9 nvidia_drm
nvidia_uvm 1138688 0
nvidia 27705344 361 nvidia_uvm,nvidia_modeset
drm_kms_helper 262144 1 nvidia_drm
drm 626688 9 drm_kms_helper,nvidia_drm


Secureboot off does not change anything. My nvidia drivers are signed using Nicolas Vieville's work. 
https://bugzilla.redhat.com/show_bug.cgi?id=1454824
I'm using : kmod-nvidia-5.8.15-201.fc32.x86_64-3:455.28-1.fc32.x86_64

Having a problem with the wake up is quite recent for me.

(In reply to Herault from comment #13)
...
> Secureboot off does not change anything. My nvidia drivers are signed using
> Nicolas Vieville's work. 
...
That's worth mentioning in the report, because 
> Having a problem with the wake up is quite recent for me.
Recent as in with nvidia upgrade or with kernel upgrade ?
Can you reproduce using an older kernel ?

If needed, can you give a try with my copr 5.4 kernel. (that's not secure boot capable yet, unless you can sign a kernel with your own secure boot keys).
https://copr.fedorainfracloud.org/coprs/kwizart/kernel-longterm-5.4/

Basically this issue may have to be forwarded to nvidia (or fedora if it's a kernel regression). As the driver is installed appropriately.

Also worth mentioning that I'm not reproducing the issue with Gnome, so desktop environment might interfere also...

Nicolas,

I have just tested with your kernel longterm. Kernel which has fallback on new but it doesn't matter.

Because still have the problem... What thus pushes aside the nvidia driver but now I am lost because it is clear that on 5.4 in the past that worked.

I have the problem since FC32. So it comes from something else, maybe gnome or xorg... ?

(In reply to Herault from comment #15)
> Nicolas,
> 
> I have just tested with your kernel longterm. Kernel which has fallback on
> new but it doesn't matter.
> 
> Because still have the problem... What thus pushes aside the nvidia driver
> but now I am lost because it is clear that on 5.4 in the past that worked.
> 
> I have the problem since FC32. So it comes from something else, maybe gnome
> or xorg... ?

@Herault

For me is the nvidia driver since f32; I had duplicated the issue several times by now. I had blocked the driver on every update to avoid the bug.

(In reply to victor sosa from comment #16)
...
> For me is the nvidia driver since f32; I had duplicated the issue several
> times by now. I had blocked the driver on every update to avoid the bug.
Then forward to nvidia

devtalk.nvidia.com