HP xw4400 Workstation won't resume from Suspend - Nouveau Driver

[Griff]

inxi -Fxz

Code: Select all

System:
  Kernel: 5.4.0-80-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.5 Distro: Linux Mint 20.2 Uma 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Hewlett-Packard product: HP xw4400 Workstation 
  v: N/A serial: <filter> 
  Mobo: Hewlett-Packard model: 0A68h serial: <filter> BIOS: Hewlett-Packard 
  v: 786D7 v02.07 date: 10/28/2010 
CPU:
  Topology: Dual Core model: Intel Core2 6400 bits: 64 type: MCP 
  arch: Core Merom rev: 2 L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 8533 
  Speed: 1600 MHz min/max: 1596/2133 MHz Core speeds (MHz): 1: 1600 2: 1600 
Graphics:
  Device-1: NVIDIA G73GL [Quadro FX 560] driver: nouveau v: kernel 
  bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.9 driver: nouveau 
  unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz 
  OpenGL: renderer: NV4B v: 2.1 Mesa 20.2.6 direct render: Yes 
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k5.4.0-80-generic 
Network:
  Device-1: Broadcom and subsidiaries NetXtreme BCM5755 Gigabit Ethernet PCI 
  Express 
  vendor: Hewlett-Packard driver: tg3 v: 3.137 port: 1000 bus ID: 3f:00.0 
  IF: enp63s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: TP-Link 802.11ac WLAN Adapter type: USB driver: usb-network 
  bus ID: 1-5:4 
Drives:
  Local Storage: total: 614.81 GiB used: 172.49 GiB (28.1%) 
  ID-1: /dev/sda vendor: Western Digital model: WD1600AAKS-00L9A0 
  size: 149.05 GiB 
  ID-2: /dev/sdb type: USB vendor: Sony model: Hard Drive size: 465.76 GiB 
RAID:
  Hardware-1: Intel 82801GR/GDH (ICH7R/ICH7DH) SATA Controller [RAID mode] 
  driver: ahci v: 3.0 bus ID: 00:1f.2 
Partition:
  ID-1: / size: 145.22 GiB used: 16.50 GiB (11.4%) fs: ext4 dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 49.0 C mobo: N/A gpu: nouveau temp: 60 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 188 Uptime: 55m Memory: 7.77 GiB used: 1.88 GiB (24.2%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

When I attempt to resume from suspend the computer seems to awaken and the screen comes to life but consists only of clearly defined static black and white lines which are misaligned at regular intervals. It seems the Nouveau driver is responsible. Driver Manager informs me "Your computer does not need any additional drivers." I have tried loading several Nvidia drivers such as 390 and 460 without success. Although some seemed to load they were all incompatible in that the screen resolution was incorrect and could not be adjusted. None of them solved the resumption problem.

The Hewlett-Packard driver website offers graphics drivers for the HP xw4400 Workstation. I have not tried any of them because they seemed very old and the references to the Kernel seemed out of date.

I am trying to achieve a computer that will resume properly from the suspend or sleep state.

Is it possible to obtain a Nvidia driver or any other driver which will work with the Nvidia G73GL (Quadro FX 560) graphics card or must I simply accept an inability for my computer to resume from the suspend state? Alternatively, if I am barking up the wrong tree is there some other way to address the problem.

Any assistance or suggestions will be appreciated.

[SMG]

When I attempt to resume from suspend the computer seems to awaken and the screen comes to life but consists only of clearly defined static black and white lines which are misaligned at regular intervals. It seems the Nouveau driver is responsible.

Why do you say the nouveau driver is responsible?

The last Nvidia driver which had support for your Quadro FX 560 was the Nvidia-304. That driver is no longer supported by Nvidia nor by Ubuntu/Mint. That is why Driver Manager does not give you any options. Nvidia designs their drivers to work with specific hardware and neither the Nvidia-390 nor the Nvidia-460 have your card listed as one which is supported. Your only driver option is the open-source nouveau driver which is what is installed.

Alternatively, if I am barking up the wrong tree is there some other way to address the problem.

I noticed in the data you posted the gpu has a somewhat high temperature. It's not really all that high of a temp if your system is running. However, if it is getting warm and then you suspend the computer (which is probably turning off the fans?), I wonder if it is overheating while the computer is suspended. Perhaps that might be a reason for the messed up screen?

Sensors:
System Temperatures: cpu: 49.0 C mobo: N/A gpu: nouveau temp: 60 C
Fan Speeds (RPM): N/A

If temperature is not the issue, we could check the logs/journalctl to see if there are any errors or messages about the nouveau driver.

[Griff]

Here is the hardware log for a boot followed by a manual suspend followed by an attempted resume (wake up).

Code: Select all

BOOT SUSPEND AND ATTEMPTED RESUME

21:23:14 kernel: tg3 0000:3f:00.0 enp63s0: Flow control is off for TX and off for RX
21:23:11 kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 0 [DRM] get 00000004 put 00002e20 state 80000000 (err: INVALID_CMD) push 00000000
21:23:06 kernel: tg3 0000:3f:00.0 enp63s0: Flow control is off for TX and off for RX
21:23:04 kernel: usb 4-2: reset low-speed USB device number 2 using uhci_hcd
21:23:04 kernel: nouveau 0000:01:00.0: DRM: 0xC328: Parsing digital output script table
21:23:04 kernel: sd 2:0:0:0: [sda] Starting disk
21:23:04 kernel: serial 00:04: activated
21:23:04 kernel: parport_pc 00:03: activated
21:23:04 kernel: tg3 0000:3f:00.0 enp63s0: Link is down
21:23:04 kernel: usb usb5: root hub lost power or was reset
21:23:04 kernel: sd 2:0:0:0: [sda] Stopping disk
21:23:04 kernel: parport_pc 00:03: disabled
21:23:04 kernel: serial 00:04: disabled
21:21:00 kernel: tg3 0000:3f:00.0 enp63s0: Flow control is off for TX and off for RX
21:20:44 kernel: snd_hda_codec_realtek hdaudioC0D0:      Aux=0x14
21:20:43 kernel: coretemp coretemp.0: Using relative temperature scale!
21:20:41 kernel: parport_pc 00:03: reported by Plug and Play ACPI
21:20:39 kernel: sd 6:0:0:0: [sdb] Attached SCSI disk
21:20:39 kernel: scsi 6:0:0:0: Direct-Access     Sony     Hard Drive       5438 PQ: 0 ANSI: 6
21:20:39 kernel: usb-storage 1-2:1.0: USB Mass Storage device detected
21:20:39 kernel: hid-generic 0003:046D:C05A.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.2-2/input0
21:20:39 kernel: usb 4-2: Manufacturer: Logitech
21:20:39 kernel: nouveau 0000:01:00.0: fb0: nouveaudrmfb frame buffer device
21:20:39 kernel: usb 1-2: new high-speed USB device number 3 using ehci-pci
21:20:39 kernel: nouveau 0000:01:00.0: DRM: 0xC328: Parsing digital output script table
21:20:39 kernel: hid-generic 0003:03F0:0024.0001: input,hidraw0: USB HID v1.10 Keyboard [CHICONY HP Basic USB Keyboard] on usb-0000:00:1d.0-1/input0
21:20:39 kernel: sd 2:0:0:0: [sda] Attached SCSI disk
21:20:39 kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WD1600AAKS-0 3E01 PQ: 0 ANSI: 5
21:20:39 kernel: nouveau 0000:01:00.0: DRM: Setting dpms mode 3 on TV encoder (output 4)
21:20:39 kernel: usb 2-1: Manufacturer: CHICONY
21:20:39 kernel: nouveau 0000:01:00.0: fb: 128 MiB GDDR3
21:20:39 kernel: tg3 0000:3f:00.0 enp63s0: renamed from eth0
21:20:39 kernel: gpio_ich gpio_ich.2.auto: GPIO from 462 to 511
21:20:39 kernel: tg3 0000:3f:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
21:20:39 kernel: scsi host5: ahci
21:20:39 kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part 
21:20:39 kernel: usb 2-1: new low-speed USB device number 2 using uhci_hcd
21:20:39 kernel: sr 0:0:0:0: Attached scsi generic sg0 type 5
21:20:39 kernel: scsi 0:0:0:0: CD-ROM            HL-DT-ST DVD+-RW GSA-H21L W516 PQ: 0 ANSI: 5
21:20:39 kernel: rtc_cmos 00:00: setting system clock to 2021-07-22T13:20:29 UTC (1626960029)
21:20:39 kernel: tty tty53: hash matches
21:20:39 kernel: platform eisa.0: EISA: Detected 0 cards
21:20:39 kernel: rtc_cmos 00:00: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
21:20:39 kernel: hub 5-0:1.0: 2 ports detected
21:20:39 kernel: usb usb5: SerialNumber: 0000:00:1d.3
21:20:39 kernel: uhci_hcd 0000:00:1d.3: irq 22, io base 0x00002060
21:20:39 kernel: hub 4-0:1.0: 2 ports detected
21:20:39 kernel: usb usb4: SerialNumber: 0000:00:1d.2
21:20:39 kernel: uhci_hcd 0000:00:1d.2: irq 21, io base 0x00002040
21:20:39 kernel: hub 3-0:1.0: 2 ports detected
21:20:39 kernel: usb usb3: SerialNumber: 0000:00:1d.1

Does this provide any useful information?

[SMG]

Here is the hardware log for a boot followed by a manual suspend followed by an attempted resume (wake up).

That appears to be the kernel log and I do not see any information in that log which indicates the system was suspended. When the system is suspended, not only is the suspend requested logged, but all the actions which happen to put the computer into suspend and then the subsequent resume are logged.

Are you powering off the system when it does not resume to a recognizable screen? If so, then run the following after you restart the computer:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the corrupted screen should be near the top) and sends it to termbin.

[Griff]

Thanks for your response. I put the computer into suspend manually. As expected the screen went dark. I then tried to resume by pressing the power button on the computer. The computer seemed to wake up but as expected the screen although active was filled with black and white lines (misaligned or torn) and nothing else. I then powered off the computer by using REISUO which I think is gentler than depressing the power button for a few seconds. I then rebooted the computer and followed your advice. Here is the command followed by the return;

rod@rod-HP-WS:~$ journalctl -rb -1 | nc termbin.com 9999
https://termbin.com/n4ss

Does this help clarify the problem?

[SMG]

rod@rod-HP-WS:~$ journalctl -rb -1 | nc termbin.com 9999
https://termbin.com/n4ss

Your description sounds like the computer is resuming from suspend which is a separate issue from the display resuming from suspend. If the computer is still running, then there is no reason to power it off to get it to restart.

The journalctl does indicate the computer was put to sleep.

Code: Select all

Jul 23 16:01:23 rod-HP-WS systemd[1]: Reached target Sleep.
Jul 23 16:01:23 rod-HP-WS systemd[1]: Starting Suspend...
Jul 23 16:01:23 rod-HP-WS systemd-sleep[1477]: Suspending system...
Jul 23 16:01:23 rod-HP-WS kernel: PM: suspend entry (deep)

Did you let it sleep before waking it? Based on the timestamps, the system was waking up less than a minute later. I do not know if you just woke it that fast or there was an issue with the computer reaching sleep state which woke it. I have seen cases where a hardware issue prevented the computer from fulling suspending and woke it right away.

Code: Select all

Jul 23 16:02:11 rod-HP-WS kernel: ACPI: Waking up from system sleep state S3
...
Jul 23 16:02:11 rod-HP-WS kernel: PM: suspend exit
Jul 23 16:02:11 rod-HP-WS systemd-sleep[1477]: System resumed.
...
Jul 23 16:02:17 rod-HP-WS systemd-logind[596]: Operation 'sleep' finished.

A second later are these lines:

Code: Select all

Jul 23 16:02:18 rod-HP-WS kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 0 [DRM] get 000027d8 put 00002f18 state 60008000 (err: RET_SUBR_INACTIVE) push 00000000
Jul 23 16:02:18 rod-HP-WS kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [cinnamon[1127]] get 000e0150 put 0046fa7c state 80020000 (err: INVALID_CMD) push 00000000

which appear to be errors related to nouveau. I will not have time until later today to hunt for the nouveau bug list to see if this is a known issue and what one might be able to do.

I did notice the below in the log, but I would not think it is related to this issue.

Code: Select all

Jul 23 15:59:55 rod-HP-WS kernel: intel_rng: Firmware space is locked read-only. If you can't or
                                  intel_rng: don't want to disable this in firmware setup, and if
                                  intel_rng: you are certain that your system has a functional
                                  intel_rng: RNG, try using the 'no_fwh_detect' option.

[Griff]

Thanks for your interesting and informative response. I respond to your queries as follows.

I think the computer was still running but because the display was inactive or frozen (covered in static black and white misaligned lines) I did not know how to give the computer commands and for this reason I had to power it off and restart it.

I did in fact let the computer sleep for less than a minute. I then tried to wake it by depressing the power button and almost immediately the display resumed but covered in black and white lines.

[SMG]

I did in fact let the computer sleep for less than a minute. I then tried to wake it by depressing the power button and almost immediately the display resumed but covered in black and white lines.

I'm thinking this might be more of a screen corruption issue rather than the workstation not resuming from suspend.

When I did a search on nouveau bug reports on Launchpad, I found quite a few which mentioned problems with suspend over the years. Most of the time, however, people were getting black screens or the computer froze rather than just getting a scrambled display like you are seeing. The only workaround I saw mentioned was using an Nvidia driver which is not an option in this case.

You could try to see if restarting the X Server (Ctl-Alt-Backspace) clears the issue.

You might also want to test live sessions of Xfce, or MATE, to see if it might work better due to the difference in how the desktop graphics (different windows managers, etc.) are handled.

Maybe someone else will have some ideas.

[Griff]

I tried restarting the X Server (Ctl-Alt-Backspace) but nothing happened. The display did not change.
I was initially running Xfce when I realised I had a problem with resuming from sleep. It was for this reason I installed Cinnamon which I am now running in the fraught hope the problem might be resolved.
It seems to me I might have an insoluble problem on my hands. This is a pity because I really like this old computer which I purchased for $30.00 and then upgraded to 8GB of RAM. If only a supported Nvidia driver was available! I would in any event like to thank you for your assistance and the attention you have given to my problem.

[Griff]

I have now tried Mate. The problem still exists but in a slightly different form. The horizontal black and white lines are no longer misaligned or torn but are very neat and regular. It almost looks as if the appearance of the black and white lines is by design rather than as a result of some sort of error.

[SMG]

I have now tried Mate. The problem still exists but in a slightly different form.

I'm curious as to whether the journalctl message are similar. Maybe the same thing is happening, but because of the different compositor/windows manager it might be presenting itself differently. Or it might be a different error/issue because of the differences in the desktop. I will take a look at the log if you want to post the url.

MATE does have other windows managers/compositor options, but maybe changing them would just change the lines and not get the desktop to show.

[Griff]

Here is a boot followed by a manual suspend followed by an attempted resume on Linux Mint Uma Mate.
https://termbin.com/5wsr

[SMG]

There was only one error line which happened in this journalctl. It happened at the same time as the suspend exit while the two listed in the Cinnamon journalctl were listed as happening a second after the suspend exit.

Code: Select all

Jul 27 18:27:38 HP-Workstation kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 0 [DRM] get 000098f0 put 00009930 state c0000054 (err: MEM_FAULT) push 00000000

These two lines happened in both logs before the suspend exit. I think they are just informational and not errors.

Code: Select all

Jul 27 18:27:38 HP-Workstation kernel: nouveau 0000:01:00.0: fifo: intr 00010000
Jul 27 18:27:38 HP-Workstation kernel: nouveau 0000:01:00.0: DRM: 0xC328: Parsing digital output script table

For comparison, the first line below is from the MATE log and the two subsequent lines are from the Cinnamon log. Cinnamon does have a higher graphics requirement than MATE which might be why there is a specific cinnamon-related issue listed.

Code: Select all

Jul 27 18:27:38 HP-Workstation kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 0 [DRM] get 000098f0 put 00009930 state c0000054 (err: MEM_FAULT) push 00000000

Jul 23 16:02:18 rod-HP-WS kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 0 [DRM] get 000027d8 put 00002f18 state 60008000 (err: RET_SUBR_INACTIVE) push 00000000
Jul 23 16:02:18 rod-HP-WS kernel: nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 4 [cinnamon[1127]] get 000e0150 put 0046fa7c state 80020000 (err: INVALID_CMD) push 00000000

I did not find any possible workarounds for this (other than the obvious of not suspending the computer).

[Griff]

Thanks once again SMG.

[Griff]

To summarize: Nvidia-304 is the last Nvidia driver which had support for Quadro FX 560. Nvidia-304 is no longer supported by Nvidia nor by Ubuntu/Mint and I therefore cannot use this driver to resolve the problem. The Nouveau driver works well in most respects but if the computer is placed in suspend it cannot resume. Is there a solution or must I simply accept the suspend function cannot work?

[roblm]

Try using the video quirks in this post:
viewtopic.php?p=2050738#p2050738

[Griff]

I tried the video quirks with the same result ie when I attempted to resume the computer woke up but produced a display consisting of regular clearly defined black and white horizontal lines. The only way to give a command to the computer was by using reisub which of course caused a reboot.