Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3560

General Questions • System only does not boot after "coldstart"

$
0
0
So, I spoke too soon AND I reactivated ufw cause I thought it will not pop up again (the hanging at boot).

This morning - powered on and voila. Stuck. :-)

As I was so intelligent to fire up the ufw yesterday, I was not able to log in via ssh. *lol*

But I was able to (at least) see something with

Code:

 journalctl -b 1 -p 3
Jän 30 05:53:45 bluecinnamon kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jän 30 05:53:45 bluecinnamon kernel: hid-generic 0003:0D8C:0135.0005: No inputs registered, leaving
Jän 30 05:53:45 bluecinnamon systemd-udevd[479]: /usr/lib/udev/rules.d/90-alsa-restore.rules:16 GOTO="alsa_restore_std" has no matching label, ignoring.
Jän 30 05:53:45 bluecinnamon systemd-udevd[479]: /usr/lib/udev/rules.d/90-alsa-restore.rules:20 GOTO="alsa_restore_std" has no matching label, ignoring.
Jän 30 05:53:45 bluecinnamon (udev-worker)[527]: event13: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
Jän 30 05:53:49 bluecinnamon kernel: [drm:psp_v13_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring
Jän 30 05:53:49 bluecinnamon kernel: amdgpu 0000:03:00.0: amdgpu: PSP firmware loading failed
Jän 30 05:53:49 bluecinnamon kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block <psp> failed -22
Jän 30 05:53:49 bluecinnamon kernel: amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
Jän 30 05:53:49 bluecinnamon kernel: amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
Jän 30 05:53:49 bluecinnamon kernel: amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Jän 30 06:03:28 bluecinnamon kernel: watchdog: watchdog0: watchdog did not stop!



which did not pop up after the next boot:

Code:

Jän 30 06:04:16 bluecinnamon kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)Jän 30 06:04:16 bluecinnamon kernel: hid-generic 0003:0D8C:0135.0005: No inputs registered, leavingJän 30 06:04:16 bluecinnamon systemd-udevd[476]: /usr/lib/udev/rules.d/90-alsa-restore.rules:16 GOTO="alsa_restore_std" has no matching label, ignoring.Jän 30 06:04:16 bluecinnamon systemd-udevd[476]: /usr/lib/udev/rules.d/90-alsa-restore.rules:20 GOTO="alsa_restore_std" has no matching label, ignoring.Jän 30 06:04:16 bluecinnamon (udev-worker)[527]: event13: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Das Argument ist ungültigJän 30 06:04:26 bluecinnamon lightdm[1221]: gkr-pam: unable to locate daemon control fileJän 30 06:04:26 bluecinnamon lightdm[1117]: pam_systemd(lightdm-greeter:session): Failed to release session: Transport endpoint is not connected
So it looks like the amdgpu fails (problems initializing?), when doing a coldstart AFTER a whole night (with switched of pc) passes by. (weird!)

Just read something in an archlinux post (

They are talking about installing amdgpu-dkms, or (another post) switching off powermanagement of the GPU via kernelparameters:
amdgpu.dc=0 or amdgpu.runpm=0

or switching of PCIe Powermanagement:
pcie_aspm=off

So amdgpu-dkms is not existing in the debianrepos, cause its part of the amd-gpu-pro propriarity driver. (I for sure wont install!)

I will give the kernelparameters a shot.

Statistics: Posted by mcdaniels — 2025-01-30 05:14 — Replies 4 — Views 185



Viewing all articles
Browse latest Browse all 3560

Trending Articles