Bug 33317

I assume you meant to set this to QA.

Please provide packages list.

Assignee: bugsquad => qa-bugs
CC: (none) => fri

With this I experienced the old hang when returning from sleep problem.
After wake up screen wakes up but go black.
In some previous version it was only a screen wakening problem; i could power cycle monitor and it was OK. but now it is that old complete freeze, i have to REISUB to reboot it, last line in journal is "kernel: PM: suspend entry (deep)"; so nothing got logged between wakening up and REISUB.  Strange.

But that is with testing kernel-server-6.6.34-1.mga9.x86_64.
Maybe the 6.6.34 is not intended for testing yet?

Now I will try using 6.6.28 for a while.

$ inxi -SMCG
System:
  Host: svarten.tribun Kernel: 6.6.28-desktop-1.mga9 arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9
Machine:
  Type: Desktop Mobo: ASRock model: P55 Pro serial: <superuser required>
    BIOS: American Megatrends v: P2.60 date: 08/20/2010
CPU:
  Info: dual core model: Intel Core i7 870 bits: 64 type: MT MCP cache:
    L2: 512 KiB
  Speed (MHz): avg: 3481 min/max: 1200/2934 cores: 1: 3481 2: 3481 3: 3481
    4: 3481
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750] driver: nvidia v: 470.256.02
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: nvidia,v4l gpu: nvidia resolution: 3840x2160~60Hz
  API: OpenGL v: 4.6.0 NVIDIA 470.256.02 renderer: NVIDIA GeForce GTX
    750/PCIe/SSE2

Yes.

Files list can be retrieved from newer testing QArepo server, using:

curl -o files-bug-33317.txt http://<server_ip>/rpmsforqa/33317?raw=1

where <server_ip> is the IP of the new qa server.

(In reply to Morgan Leijström from comment #2)

> With this I experienced the old hang when returning from sleep problem.
> After wake up screen wakes up but go black.
> In some previous version it was only a screen wakening problem; i could
> power cycle monitor and it was OK. but now it is that old complete freeze, i
> have to REISUB to reboot it, last line in journal is "kernel: PM: suspend
> entry (deep)"; so nothing got logged between wakening up and REISUB. 
> Strange.
> 
> But that is with testing kernel-server-6.6.34-1.mga9.x86_64.
> Maybe the 6.6.34 is not intended for testing yet?
> 

There will be a 6.6.35.

(In reply to Giuseppe Ghibò from comment #3)
> Yes.
> 
> Files list can be retrieved from newer testing QArepo server, using:
> 
> curl -o files-bug-33317.txt http://<server_ip>/rpmsforqa/33317?raw=1
> 
> where <server_ip> is the IP of the new qa server.

1. Is madb not qarepo
2.

Keywords: (none) => advisory

SRPMS
nvidia470-470.256.02-1.mga9.nonfree

RPMS in

9/x86_64/nonfree/updates_testing

dkms-nvidia470-470.256.02-1.mga9.nonfree
nvidia470-all-470.256.02-1.mga9.nonfree
nvidia470-cuda-opencl-470.256.02-1.mga9.nonfree
nvidia470-devel-470.256.02-1.mga9.nonfree
nvidia470-doc-html-470.256.02-1.mga9.nonfree
nvidia470-lib32-470.256.02-1.mga9.nonfree
nvidia470-utils-470.256.02-1.mga9.nonfree
x11-driver-video-nvidia470-470.256.02-1.mga9.nonfree

mga9-64 OK here

Continuing from comment 2, same system:

Been using this for a couple days with our desktop, server and linus kernels 6.6.28-1 without problems.

MGA9-64 Plasma, i5-7500, Quadro K620. Booted into the server kernel with nvidia-current, switched to the 470 driver with MCC. Rebooted, used it for a half hour, rebooted into the desktop kernel, modules built during boot, using it now.

No issues to report.

CC: (none) => andrewsfarm

Since it works with the current kernel, sending this on. Validating.

Whiteboard: (none) => MGA9-64-OK
CC: (none) => sysadmin-bugs
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0150.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED