Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: Fail to load display manager after DU  (Read 901 times)

Offline titan

  • User
  • Posts: 273
Fail to load display manager after DU
« on: 2021/10/28, 10:11:34 »
After DU this morning booting only gets as far as failing to load display manager SDDM. Reverting to previous kernel works fine.


CPU: Quad Core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT MCP-) speed/min/max: 2964/1600/3600 MHz
Kernel: 5.14.14-1-siduction-amd64 x86_64 Up: 5m Mem: 1791.4/5868.5 MiB (30.5%) Storage: 1.34 TiB (29.1% used) Procs: 257
Shell: Bash inxi: 3.3.07

Offline charlyheinz

  • User
  • Posts: 49
Re: Fail to load display manager after DU
« Reply #1 on: 2021/10/28, 10:25:37 »
Same here. Did a DU with upgrading kernel and Nvidia-driver- no login any-more. Tried to load previous kernel- no luck (Nvidia-driver problem) So take care!!!
I've tried to playback a Image but I can not get access to the root-partition using sudo dd with an booted install USB- media.
Anyone any idea.

Online Mister00X

  • User
  • Posts: 130
Re: Fail to load display manager after DU
« Reply #2 on: 2021/10/28, 10:54:10 »
I can not confirm that the display manager doesn't load on kernel 5.14.15-1 but that it takes very long to do so. Nevertheless the kernel spews errors on my laptop. Here are the specs (taken from a working kernel):
Code: [Select]
System:    Kernel: 5.14.14-1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.23.0
           Distro: siduction 18.3.0 Patience - kde - (201912231837)
Machine:   Type: Laptop System: HP product: HP Laptop 17-ca1xxx v: N/A serial: <filter>
           Mobo: HP model: 85B3 v: 91.47 serial: <filter> UEFI: AMI v: F.55 date: 06/04/2020
Battery:   ID-1: BAT0 charge: 11.1 Wh (27.3%) condition: 40.7/40.7 Wh (100.0%) volts: 11.3 min: 11.3
CPU:       Info: Quad Core AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx [MT MCP] speed: 1222 MHz min/max: 1400/2100 MHz
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel
           Device-2: Cheng Uei Precision Industry (Foxlink) HP TrueVision HD Camera type: USB driver: uvcvideo
           Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: AMD Radeon Vega 8 Graphics (RAVEN DRM 3.42.0 5.14.14-1-siduction-amd64 LLVM 12.0.1)
           v: 4.6 Mesa 21.2.4
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           Device-2: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtl8821ce
Drives:    Local Storage: total: 1.14 TiB used: 472.76 GiB (40.4%)
Info:      Processes: 313 Uptime: 4m Memory: 13.58 GiB used: 2.36 GiB (17.4%) Shell: Bash inxi: 3.3.07

In the logs I got error messages like this snippets from journalctl -b-1 --dmesg -p 4:
Code: [Select]
Okt 28 10:28:08 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
Okt 28 10:28:21 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Okt 28 10:28:34 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
Okt 28 10:28:47 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Okt 28 10:29:01 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
Okt 28 10:29:14 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Okt 28 10:29:27 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Code: [Select]
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:128 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:   in page starting at address 0x0000000000872000 from IH client 0x1b (UTCL2)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00040D00
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          Faulty UTCL2 client ID: CPG (0x6)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          MORE_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          WALKER_ERROR: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          MAPPING_ERROR: 0x1
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          RW: 0x1
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:128 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:   in page starting at address 0x0000000000872000 from IH client 0x1b (UTCL2)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00040D00
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          Faulty UTCL2 client ID: CPG (0x6)
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          MORE_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          WALKER_ERROR: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          MAPPING_ERROR: 0x1
Okt 28 10:29:40 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu:          RW: 0x1

I've uploaded a full dmesg log of that boot to https://termbin.com/7csz

EDIT: On my desktop PC which has an dedicated amd GPU this problem does not occur. So maybe it's specific to iGPUs.
« Last Edit: 2021/10/28, 11:06:21 by Mister00X »
Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say. – Edward Snowden

Offline charlyheinz

  • User
  • Posts: 49
Re: Fail to load display manager after DU
« Reply #3 on: 2021/10/28, 11:49:41 »
After purging Nvidia-driver the system is running with nouveau- driver again. Puh- it 's my productive system. The actual kernel is working here without Nvidia-driver support. The installation of the Nvidia-driver breaks because of the Nvidia-kernel-dkms package which is defect. (Synaptic- Information)

Code: [Select]
uname -r
5.14.15-1-siduction-amd64

Code: [Select]
apt-cache policy nvidia-kernel-dkms
nvidia-kernel-dkms:
  Installiert:           (keine)
  Installationskandidat: 495.44-0~siduction.3
  Versionstabelle:
     495.44-0~siduction.3 500
        500 https://packages.siduction.site/fixes unstable/non-free amd64 Packages
     470.74-1 500
        500 https://deb.debian.org/debian unstable/non-free amd64 Packages
Code: [Select]
apt-cache policy nvidia-driver
nvidia-driver:
  Installiert:           (keine)
  Installationskandidat: 495.44-0~siduction.3
  Versionstabelle:
     495.44-0~siduction.3 500
        500 https://packages.siduction.site/fixes unstable/non-free amd64 Packages
     470.74-1 500
        500 https://deb.debian.org/debian unstable/non-free amd64 Packages

Code: [Select]
apt-get install nvidia-kernel-dkms
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 nvidia-kernel-support : Hängt ab von: nvidia-modprobe (>= 495.29) soll aber nicht installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.

If someone can give me a hand on this...


Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Fail to load display manager after DU
« Reply #4 on: 2021/10/28, 11:55:12 »
Code: [Select]
LANG=C apt policy nvidia-modprobeIs showing what?

Code: [Select]
towo:OMPC-AV2> LANG=C apt policy nvidia-modprobe
nvidia-modprobe:
  Installed: (none)
  Candidate: 495.44-0~siduction.1
  Version table:
     495.44-0~siduction.1 500
        500 http://ftp.uni-stuttgart.de/pub/mirrors/sync.siduction.org/siduction/fixes unstable/contrib amd64 Packages
     495.29.05-0~siduction.1 90
         90 https://packages.siduction.org/extra experimental/contrib amd64 Packages
     470.57.02-1 500
        500 http://deb.debian.org/debian unstable/contrib amd64 Packages
        500 http://deb.debian.org/debian testing/contrib amd64 Packages
     460.32.03-1 500
        500 http://deb.debian.org/debian stable/contrib amd64 Packages

Code: [Select]
towo:OMPC-AV2> LANG=C apt install nvidia-kernel-dkms -s
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  g++-10 libamtk-5-0 libamtk-5-common libbotan-2-17 libbox2d2.3.0 libcbor0 libcmis-0.5-5v5 libdav1d4 libedataserver-1.2-25 libffi7:i386 libgdl-3-5 libgdl-3-common libglew2.1 libgupnp-1.2-0 libllvm11 libntfs-3g883 libqrcodegencpp1 libsidplayfp5 libstdc++-10-dev
  libtepl-5-0 libtinyxml2-8 libtracker-control-2.0-0 libtracker-miner-2.0-0 libtracker-sparql-2.0-0 libx265-192 linux-headers-5.14.5-2-siduction-amd64 linux-headers-5.14.6-2-siduction-amd64 linux-headers-5.14.8-1-siduction-amd64 linux-image-5.14.5-2-siduction-amd64
  linux-image-5.14.6-2-siduction-amd64 linux-image-5.14.8-1-siduction-amd64 x11proto-xext-dev
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-support nvidia-legacy-check nvidia-modprobe update-glx
Suggested packages:
  nvidia-driver | nvidia-driver-any
Recommended packages:
  nvidia-driver | libcuda1
The following NEW packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support nvidia-legacy-check nvidia-modprobe update-glx
0 upgraded, 11 newly installed, 0 to remove and 29 not upgraded.
Inst update-glx (1.2.1 Debian:unstable, Debian:testing [amd64])
Inst glx-alternative-mesa (1.2.1 Debian:unstable, Debian:testing [amd64])
Inst nvidia-installer-cleanup (20151021+13 Debian:unstable, Debian:testing, Debian:11.1/stable [amd64])
Conf nvidia-installer-cleanup (20151021+13 Debian:unstable, Debian:testing, Debian:11.1/stable [amd64])
Inst glx-diversions (1.2.1 Debian:unstable, Debian:testing [amd64])
Inst glx-alternative-nvidia (1.2.1 Debian:unstable, Debian:testing [amd64])
Inst nvidia-legacy-check (495.44-0~siduction.3 unstable [amd64])
Conf nvidia-legacy-check (495.44-0~siduction.3 unstable [amd64])
Inst nvidia-alternative (495.44-0~siduction.3 unstable [amd64])
Inst nvidia-kernel-common (20151021+13 Debian:unstable, Debian:testing, Debian:11.1/stable [amd64])
Inst nvidia-modprobe (495.44-0~siduction.1 unstable [amd64])
Inst nvidia-kernel-support (495.44-0~siduction.3 unstable [amd64])
Inst nvidia-kernel-dkms (495.44-0~siduction.3 unstable [amd64])
Conf update-glx (1.2.1 Debian:unstable, Debian:testing [amd64])
Conf glx-alternative-mesa (1.2.1 Debian:unstable, Debian:testing [amd64])
Conf glx-diversions (1.2.1 Debian:unstable, Debian:testing [amd64])
Conf glx-alternative-nvidia (1.2.1 Debian:unstable, Debian:testing [amd64])
Conf nvidia-alternative (495.44-0~siduction.3 unstable [amd64])
Conf nvidia-kernel-common (20151021+13 Debian:unstable, Debian:testing, Debian:11.1/stable [amd64])
Conf nvidia-modprobe (495.44-0~siduction.1 unstable [amd64])
Conf nvidia-kernel-support (495.44-0~siduction.3 unstable [amd64])
Conf nvidia-kernel-dkms (495.44-0~siduction.3 unstable [amd64])
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline charlyheinz

  • User
  • Posts: 49
Re: Fail to load display manager after DU
« Reply #5 on: 2021/10/28, 12:00:24 »
Hello towo:

Code: [Select]
LANG=C apt policy nvidia-modprobe
nvidia-modprobe:
  Installed: (none)
  Candidate: 470.57.02-1
  Version table:
     470.57.02-1 500
        500 https://deb.debian.org/debian unstable/contrib amd64 Packages
LANG=C apt install nvidia-kernel-dkms -s
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nvidia-kernel-support : Depends: nvidia-modprobe (>= 495.29) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

 The problem depends on the missing nvidia-modprobe 495.29 version. Do I have a problem with my apt-sources?
« Last Edit: 2021/10/28, 12:14:08 by charlyheinz »

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Fail to load display manager after DU
« Reply #6 on: 2021/10/28, 12:19:30 »
Quote
The problem depends on the missing nvidia-modprobe 495.29 version. Do I have a problem with my apt-sources?

Read my post?

Code: [Select]
LANG=C apt policy nvidia-modprobe
nvidia-modprobe:
  Installed: (none)
  Candidate: 495.44-0~siduction.1
  Version table:
     495.44-0~siduction.1 500
        500 http://ftp.uni-stuttgart.de/pub/mirrors/sync.siduction.org/siduction/fixes unstable/contrib amd64 Packages
     495.29.05-0~siduction.1 90
         90 https://packages.siduction.org/extra experimental/contrib amd64 Packages
     470.57.02-1 500
        500 http://deb.debian.org/debian unstable/contrib amd64 Packages
        500 http://deb.debian.org/debian testing/contrib amd64 Packages
     460.32.03-1 500
        500 http://deb.debian.org/debian stable/contrib amd64 Packages
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline charlyheinz

  • User
  • Posts: 49
Re: Fail to load display manager after DU
« Reply #7 on: 2021/10/28, 12:54:11 »
Thanks towo.

Yes I've already read. Still I am always unsure which apt-sources I should use.

Again thanks a lot and stay healthy an well...

Offline hendrikL

  • Administrator
  • User
  • *****
  • Gravatar
  • Posts: 592
Re: Fail to load display manager after DU
« Reply #8 on: 2021/10/28, 13:07:01 »
Code: [Select]
:~$ cat /etc/apt/sources.list.d/fixes.list
deb https://packages.siduction.org/fixes unstable main contrib non-free
# deb-src https://packages.siduction.org/fixes unstable main contrib non-free

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Fail to load display manager after DU
« Reply #9 on: 2021/10/28, 13:12:18 »
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline titan

  • User
  • Posts: 273
Re: Fail to load display manager after DU
« Reply #10 on: 2021/10/28, 14:41:44 »
Those amdgpu  errors seem to have started months ago, but only today for me after du.

Online Mister00X

  • User
  • Posts: 130
Re: Fail to load display manager after DU
« Reply #11 on: 2021/10/28, 20:03:52 »
I have to admit that while my laptop occasionally hangs after waking up from suspend this is on an entire different level.
Before kernel 5.14.15-1 it would not hang at boot only sometimes after suspend. Now booting into kernel 5.14.15 immediately causes problems.

And if someone (like me) tries to login into the graphical environment the error messages get even worse.

The kernel reports BUGs like this
Code: [Select]
Okt 28 19:16:23 kernel: ^[[0;1;39mBUG: Bad page map in process preload  pte:00000168 pmd:16faa6067
Okt 28 19:16:23 kernel: ^[[0;1;39maddr:000055f964e00000 vm_flags:00100073 anon_vma:ffff8881a6c2b268 mapping:0000000000000000 index:55f964e00
Okt 28 19:16:23 kernel: ^[[0;1;39mfile:(null) fault:0x0 mmap:0x0 readpage:0x0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCPU: 3 PID: 74652 Comm: preload Tainted: G           O      5.14.15-1-siduction-amd64 #1 siduction 5.14-15
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mHardware name: HP HP Laptop 17-ca1xxx/85B3, BIOS F.55 06/04/2020
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCall Trace:
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m dump_stack_lvl+0x34/0x44
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m print_bad_pte.cold+0x86/0xed
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? lock_page_memcg+0x1f/0xa0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m vm_normal_page+0xa2/0xb0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m unmap_page_range+0x4af/0xc00
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m unmap_vmas+0x78/0xf0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? lru_add_drain_cpu+0x90/0x130
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m exit_mmap+0x9c/0x1f0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m mmput+0x52/0x120
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_exit+0x2ef/0xa00
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? get_vtime_delta+0x15/0xd0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_group_exit+0x33/0xa0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m __x64_sys_exit_group+0x14/0x20
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_syscall_64+0x5c/0x80
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? get_vtime_delta+0x15/0xd0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? asm_exc_page_fault+0x8/0x30
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? __context_tracking_enter+0x73/0xe0
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m entry_SYSCALL_64_after_hwframe+0x44/0xae
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRIP: 0033:0x7f371db9c119
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCode: Unable to access opcode bytes at RIP 0x7f371db9c0ef.
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRSP: 002b:00007ffdd76e6598 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRAX: ffffffffffffffda RBX: 00007f371dc91630 RCX: 00007f371db9c119
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRBP: 0000000000000000 R08: ffffffffffffff88 R09: 0000000000000001
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mR10: 0000000000000004 R11: 0000000000000246 R12: 00007f371dc91630
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mR13: 0000000000000001 R14: 00007f371dc91b08 R15: 0000000000000000
Okt 28 19:16:23 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mDisabling lock debugging due to kernel taint
Okt 28 19:16:23 kernel: ^[[0;1;39mBUG: Bad rss-counter state mm:00000000d0221ed9 type:MM_ANONPAGES val:1

this
Code: [Select]
Okt 28 19:22:10 kernel: ^[[0;1;39mBUG: Bad page map in process gnome-keyring-d  pte:00000008 pmd:11a3d9067
Okt 28 19:22:10 kernel: ^[[0;1;39maddr:00007f36a5600000 vm_flags:00100073 anon_vma:ffff88812a14b948 mapping:0000000000000000 index:7f36a5600
Okt 28 19:22:10 kernel: ^[[0;1;39mfile:(null) fault:0x0 mmap:0x0 readpage:0x0
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCPU: 4 PID: 32272 Comm: gnome-keyring-d Tainted: G    B      O      5.14.15-1-siduction-amd64 #1 siduction 5.14-15
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mHardware name: HP HP Laptop 17-ca1xxx/85B3, BIOS F.55 06/04/2020
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCall Trace:
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m dump_stack_lvl+0x34/0x44
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m print_bad_pte.cold+0x86/0xed
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m unmap_page_range+0x6fb/0xc00
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m unmap_vmas+0x78/0xf0
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? lru_add_drain_cpu+0x90/0x130
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m exit_mmap+0x9c/0x1f0
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m mmput+0x52/0x120
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_exit+0x2ef/0xa00
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_group_exit+0x33/0xa0
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m __x64_sys_exit_group+0x14/0x20
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_syscall_64+0x5c/0x80
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? asm_exc_page_fault+0x8/0x30
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? __context_tracking_enter+0x73/0xe0
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m entry_SYSCALL_64_after_hwframe+0x44/0xae
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRIP: 0033:0x7f36a6550119
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCode: Unable to access opcode bytes at RIP 0x7f36a65500ef.
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRSP: 002b:00007ffff82ade18 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRAX: ffffffffffffffda RBX: 00007f36a6645630 RCX: 00007f36a6550119
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRBP: 0000000000000000 R08: ffffffffffffff88 R09: 0000000000000000
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mR10: 0000000000000013 R11: 0000000000000246 R12: 00007f36a6645630
Okt 28 19:22:10 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mR13: 0000000000000004 R14: 00007f36a6645b08 R15: 0000000000000000
Okt 28 19:22:10 kernel: ^[[0;1;39mBUG: Bad rss-counter state mm:00000000dfd5aa2f type:MM_SWAPENTS val:-1
Okt 28 19:22:10 kernel: traps: mullvad-gui[35774] general protection fault ip:555d8ceeb6d7 sp:7ffea8c079a0 error:0 in mullvad-gui[555d86f40000+6066000]

and this

Code: [Select]
Okt 28 19:24:51 kernel: ^[[0;1;39m__swap_info_get: Bad swap offset entry 3ffffffffffff
Okt 28 19:24:51 kernel: ^[[0;1;39mBUG: Bad page map in process mysqld  pte:00000002 pmd:15a171067
Okt 28 19:24:51 kernel: ^[[0;1;39maddr:00007fdc40000000 vm_flags:00200073 anon_vma:ffff8881747de840 mapping:0000000000000000 index:7fdc40000
Okt 28 19:24:51 kernel: ^[[0;1;39mfile:(null) fault:0x0 mmap:0x0 readpage:0x0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCPU: 5 PID: 38986 Comm: mysqld Tainted: G    B      O      5.14.15-1-siduction-amd64 #1 siduction 5.14-15
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mHardware name: HP HP Laptop 17-ca1xxx/85B3, BIOS F.55 06/04/2020
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCall Trace:
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m dump_stack_lvl+0x34/0x44
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m print_bad_pte.cold+0x86/0xed
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m unmap_page_range+0x6fb/0xc00
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m unmap_vmas+0x78/0xf0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m exit_mmap+0x9c/0x1f0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m mmput+0x52/0x120
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_exit+0x2ef/0xa00
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_group_exit+0x33/0xa0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m get_signal+0x13e/0x8e0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m arch_do_signal_or_restart+0xfd/0x700
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? get_vtime_delta+0x15/0xd0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? __x64_sys_futex+0x73/0x1c0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m exit_to_user_mode_prepare+0xcb/0x150
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m syscall_exit_to_user_mode+0x12/0x30
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m do_syscall_64+0x69/0x80
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? __context_tracking_enter+0x73/0xe0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? syscall_exit_to_user_mode+0x29/0x30
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? do_syscall_64+0x69/0x80
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? asm_exc_page_fault+0x8/0x30
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m ? __context_tracking_enter+0x73/0xe0
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185m entry_SYSCALL_64_after_hwframe+0x44/0xae
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRIP: 0033:0x7fdcc083ed18
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mCode: Unable to access opcode bytes at RIP 0x7fdcc083ecee.
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRSP: 002b:00007fdcb03f7c20 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRAX: fffffffffffffe00 RBX: 0000000000000000 RCX: 00007fdcc083ed18
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRDX: 0000000000000003 RSI: 0000000000000189 RDI: 0000556ee5da716c
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mRBP: 0000556ee5da7160 R08: 0000000000000000 R09: 00000000ffffffff
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mR10: 0000000000000000 R11: 0000000000000246 R12: 0000556ee5da716c
Okt 28 19:24:51 kernel: ^[[0;1;38;5;185m^[[0;1;39m^[[0;1;38;5;185mR13: 0000556ee5da7164 R14: 0000000000000080 R15: 00000000000000ca

And even a hardware error:
Code: [Select]
Okt 28 19:20:26 kernel: mce: [Hardware Error]: Machine check events logged
Okt 28 19:20:26 kernel: ^[[0;1;39m[Hardware Error]: Deferred error, no action required.
Okt 28 19:20:26 kernel: ^[[0;1;39m[Hardware Error]: CPU:0 (17:18:1) MC20_STATUS[-|-|MiscV|AddrV|-|-|SyndV|UECC|Deferred|-|-]: 0x9c2030000001082b
Okt 28 19:20:26 kernel: ^[[0;1;39m[Hardware Error]: Error Addr: 0x00007ffcffffff00
Okt 28 19:20:26 kernel: ^[[0;1;39m[Hardware Error]: IPID: 0x0000002e00000000, Syndrome: 0x000000005b240203
Okt 28 19:20:26 kernel: ^[[0;1;39m[Hardware Error]: Coherent Slave Ext. Error Code: 1, Address Violation.
Okt 28 19:20:26 kernel: ^[[0;1;39m[Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: WR, part-proc: SRC (no timeout)
Okt 28 19:21:11 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6
Okt 28 19:21:24 kernel: ^[[0;1;39mamdgpu 0000:04:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706
Okt 28 19:22:10 kernel: ^[[0;1;39m__swap_info_get: Bad swap offset entry 3ffffffffffff

All things that don't happen with kernel 5.14.14 so I have a bit of a hard time to imagine that this error was that long already in the kernel but never occurred before.


In the bug towo linked there is the amdgpu.noretry=0 kernel parameter mentioned I will try booting my laptop with that  parameter either today or tomorrow and will report back how it worked out...

P.S.: Log of the boot with kernel 5.14.15 where I logged into KDE https://termbin.com/q56b

EDIT: I should mention that even after login into kde the system still hangs. It took approximately 5 min for plasma to be fully loaded and starting a program like firefox also takes minutes.
« Last Edit: 2021/10/28, 20:09:05 by Mister00X »
Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say. – Edward Snowden

Offline towo

  • Administrator
  • User
  • *****
  • Posts: 2.638
Re: Fail to load display manager after DU
« Reply #12 on: 2021/10/28, 20:07:42 »
Try the next kernel, which is building now.
There i have reverted the patch, which was introducing that problem with amdgpu.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Online Mister00X

  • User
  • Posts: 130
Re: Fail to load display manager after DU
« Reply #13 on: 2021/10/28, 20:34:15 »
THANKS towo

this fixed the issue.

It boots up fine again also no strange errors.  :D
Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say. – Edward Snowden

Offline titan

  • User
  • Posts: 273
Re: Fail to load display manager after DU
« Reply #14 on: 2021/10/28, 21:00:49 »
Thanks Towo, just installed latest kernel it all seems OK at the moment