Willkommen Gast. Bitte einloggen oder registrieren. Haben Sie Ihre Aktivierungs E-Mail übersehen?
16.05.2021, 23:35:05

.
Einloggen mit Benutzername, Passwort und Sitzungslänge

Mitglieder
  • Mitglieder insgesamt: 25602
  • Letzte: zanu1947
Statistiken
  • Beiträge insgesamt: 735805
  • Themen insgesamt: 59256
  • Heute online: 818
  • Am meisten online: 2287
  • (22.01.2020, 19:20:24)
Benutzer Online

Autor Thema:  Thinkpad e595 - amdgpu problem bei resume aus hibernate  (Gelesen 657 mal)

0 Mitglieder und 1 Gast betrachten dieses Thema.

Hallo,
ich habe das Problem, dass das resume aus dem hibernatestatus scheints nicht funfktioniert.
mein System:
Linux Mint cinnamon 19.3 mit Kernel 5.4.0.40-generic
System:    Host: mp-linux Kernel: 5.4.0-40-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
           Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia
           base: Ubuntu 18.04 bionic
Machine:   Type: Laptop System: LENOVO product: 20NF001HGE v: ThinkPad E595 serial: <filter>
           Chassis: type: 10 serial: <filter>
           Mobo: LENOVO model: 20NF001HGE serial: <filter> UEFI: LENOVO v: R11ET36W (1.16 )
           date: 03/30/2020
Battery:   ID-1: BAT0 charge: 12.2 Wh condition: 46.3/45.7 Wh (101%) volts: 10.9/11.1
           model: Celxpert 5B10W138 serial: <filter> status: Discharging
CPU:       Topology: Quad Core model: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx bits: 64
           type: MT MCP arch: Zen rev: 1 L2 cache: 2048 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 33534
           Speed: 1197 MHz min/max: 1400/2100 MHz Core speeds (MHz): 1: 1198 2: 1197 3: 2383
           4: 2379 5: 1198 6: 1196 7: 1197 8: 1197
Graphics:  Device-1: AMD Picasso vendor: Lenovo driver: amdgpu v: kernel bus ID: 05:00.0
           chip ID: 1002:15d8
           Display: x11 server: X.Org 1.20.8 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: AMD RAVEN (DRM 3.35.0 5.4.0-40-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8
           direct render: Yes
Audio:     Device-1: AMD vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 05:00.1
           chip ID: 1002:15de
           Device-2: AMD vendor: Lenovo driver: snd_rn_pci_acp3x v: kernel bus ID: 05:00.5
           chip ID: 1022:15e2
           Device-3: AMD vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 05:00.6
           chip ID: 1022:15e3
           Sound Server: ALSA v: k5.4.0-40-generic
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo
           driver: r8169 v: kernel port: 3000 bus ID: 02:00.0 chip ID: 10ec:8168
           IF: enp2s0 state: down mac: <filter>
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: Lenovo
           driver: rtw_pci v: N/A port: 2000 bus ID: 04:00.0 chip ID: 10ec:b822
           IF: wlp4s0 state: up mac: <filter>
Drives:    Local Storage: total: 476.94 GiB used: 44.57 GiB (9.3%)
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZALQ512HALU-000L1 size: 476.94 GiB
           speed: 31.6 Gb/s lanes: 4 serial: <filter>
Partition: ID-1: / size: 404.13 GiB used: 44.53 GiB (11.0%) fs: ext4 dev: /dev/nvme0n1p5
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 chip ID: 1d6b:0003
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
           Device-1: 3-1:2 info: Realtek type: Bluetooth driver: btusb rev: 1.1 chip ID: 0bda:b023
           Device-2: 3-2:3 info: Chicony type: Video driver: uvcvideo rev: 2.0 chip ID: 04f2:b6d9
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 1 rev: 3.1 chip ID: 1d6b:0003
Sensors:   System Temperatures: cpu: 44.2 C mobo: 0.0 C
           Fan Speeds (RPM): cpu: 0
Repos:     No active apt repos in: /etc/apt/sources.list
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
           1: deb http: //packages.linuxmint.com tricia main upstream import backport #id:linuxmint_main
           2: deb http: //archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           3: deb http: //archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           4: deb http: //archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ bionic partner
           Active apt repos in: /etc/apt/sources.list.d/remmina-ppa-team-remmina-next-bionic.list
           1: deb http: //ppa.launchpad.net/remmina-ppa-team/remmina-next/ubuntu bionic main
           Active apt repos in: /etc/apt/sources.list.d/teejee2008-ppa-bionic.list
           1: deb http: //ppa.launchpad.net/teejee2008/ppa/ubuntu bionic main
Info:      Processes: 250 Uptime: 29m Memory: 13.61 GiB used: 3.40 GiB (25.0%) Init: systemd
           v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 client
           inxi: 3.0.32

Hier die Fehler aus dem log:


17:38:04 kernel: #PF: supervisor read access in kernel mode
17:38:04 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000040
17:38:04 kernel: #PF: error_code(0x0000) - not-present page
17:38:04 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000040
17:38:04 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 971 thread Xorg:cs0 pid 982
17:37:55 wpa_supplicant: dbus: Failed to construct signal
17:37:54 systemd-rfkill: Failed to open device rfkill3: No such device
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
17:37:54 kernel: amdgpu 0000:05:00.0: couldn't schedule ib on ring <sdma0>
17:37:54 kernel: PM: Device 0000:05:00.0 failed to restore async: error -110
17:37:54 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
17:37:54 kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v9_0> failed -110
17:37:54 kernel: [drm:gfx_v9_0_cp_resume [amdgpu]] *ERROR* KCQ enable failed
17:37:54 kernel: amdgpu 0000:05:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)


P.S.: passiert oft aber nicht immer, manchmal ist es kein Problem - dann startet das System mit prompt für Passwort...

Kann da jemand helfen ?

DANKE !

lg





Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #1 am: 19.07.2020, 12:09:14 »
Hallo. Ich habe unter 19.3 ebenfalls mit der neuen AMD CPU / GPU meine Schwierigkeiten gehabt. Seit Mint 20 + Kernel 5.6.16 läuft fast alles perfekt. Nur das Touchpad musste ich noch manuell ans Laufen bringen. Gruß  ;D

Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #2 am: 19.07.2020, 12:58:28 »
Hallo Lukas030581,
Danke für den Hinweis - werd mal in den nächsten Tagen auf Mint 20 upgraden... gebe dann Bescheid, ob es dann passt...

lg

Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #3 am: 19.07.2020, 14:34:20 »
Hi :)
resume aus hibernate ohne swap? das wäre mir neu...
bring mal bitte die ergebnisse wenn es funktioniert.

Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #4 am: 20.07.2020, 11:04:54 »
Hallo etron,
swapfile gibt es:

mp@mp-linux:~$ swapon -s
Dateiname Typ Größe Benutzt Priorität
/swapfile                              file    19922940 0 -2

lg

Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #5 am: 20.07.2020, 12:11:52 »
Mit SWAPFILE geht es aber nicht, du brauchst schon eine Swap-Partition.

Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #6 am: 20.07.2020, 14:58:45 »
Hallo Tommix,
ich bin lt. linuxmint forum vorgegangen:
https://forums.linuxmint.com/viewtopic.php?f=42&t=284100

lt. div. Forumseinträgen sollte Hibrenate auch mit Swapfile funktionieren.

geht das doch nicht ?

lg

Re: Thinkpad e595 - amdgpu problem bei resume aus hibernate
« Antwort #7 am: 21.07.2020, 15:15:32 »
Hi :)
hibernate läuft nur mit swap partition und entsprechenden anpassungen.
standby geht auch ohne...