Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] sddm not loading (and other potential issues) (Read 4872 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: sddm not loading (and other potential issues)

Reply #15 –
The broken sddm theme from 2 days ago was my fault; other than that, I'd advise against re-installing the whole system. If nothing else, we'll never know what caused the problem in the first place.   ;)

Re: sddm not loading (and other potential issues)

Reply #16 –
I can keep it going to diagnostic purposes - I'm just not technically skilled enough yet to figure it out quickly and my time is pinched to do the normal "learn, apply, repeat" method.

And while they all might be related, it looks like I have a udev, kvm, and sddm issue that no one else has reported or chimed in on - so very possible I (or some random package) had some unintended effect on my system and I feel like i would be wasting everyone's time.

What I'm getting at is, I'll keep it if it might help the distro and keep working on this puzzle with those that are interested.
But I may still install a second copy and also practice better backup/restore habits.


Quote from: nous – on
The broken sddm theme from 2 days ago was my fault; other than that, I'd advise against re-installing the whole system. If nothing else, we'll never know what caused the problem in the first place.   ;)

And no problem there. Just to be clear.
Hiccups happen.

Re: sddm not loading (and other potential issues)

Reply #17 –
Regarding the udev issue.
There is a snippet of messages that pop up at boot that never happened before. I've barely been able to capture a screen shot with my phone. If i can find the log, I'd post it here.

The message is many lines long. Happens right before "* Setting up tmpfiles.d entries ..."

And the last line of the message is
udevd[911]: worker [950] failed while handling '/devices/pci0000"00/000    ...

there is more after the ... , i just didn't capture it.

Any clues where this log might be.

Re: sddm not loading (and other potential issues)

Reply #18 –
Regarding the original issue of being thrown to tty1  instead of sddm.

A reboot, and things worked Another reboot, and I'm back to the above.
would kvm or udev cause a hang or race condition for sddm which would explain the temperamental nature of this problem?



edit: clarity

Re: sddm not loading (and other potential issues)

Reply #19 –
If you suspect there is a race condition, try disabling parallel start in openrc. Well, I'm assuming you are using otherwise it shouldn't be possible for openrc to have a race in its handling of services.

Re: sddm not loading (and other potential issues)

Reply #20 –
Quote from: InkStone – on

Any clues where this log might be.




Not sure if it would be in openrc /var/log/rc.log.  You may need to turn on openrc logging, in /etc/rc.conf:

Code: [Select]
rc_logger="YES"


You may also want to set verbose logging on :

Code: [Select]
rc_verbose=YES


And openrc has an interaactive option:

Code: [Select]
rc_interactive="YES"


The only place "udevd" appears in any of my logs is dmesg; showing that its starting up along with entries on urandom.


Re: sddm not loading (and other potential issues)

Reply #21 –
Quote from: Dudemanguy – on
If you suspect there is a race condition, try disabling parallel start in openrc. Well, I'm assuming you are using otherwise it shouldn't be possible for openrc to have a race in its handling of services.


parallel is set to no (actually commented out, so default).
So I guess that isn't it. Bothersome that it may or may not work seemingly randomly (so far)

Re: sddm not loading (and other potential issues)

Reply #22 –
Quote from: dxrobertson – on

...



I captured the dmesg from the last boot after enabling verbose and interactive (didn't use that, just enabled for later)
The new entries I noticed during boot start at this line:
[    6.472829] RIP: 0033:0x7fb2edf0c73e

There is more to the log, I just hit the 40k characters limit.


Code: [Select]
[    5.578234] [TTM] Initializing DMA pool allocator
[    5.578268] [drm] amdgpu: 8176M of VRAM memory ready
[    5.578270] [drm] amdgpu: 8176M of GTT memory ready.
[    5.578272] [drm] GART: num cpu pages 131072, num gpu pages 131072
[    5.578496] [drm] PCIE GART of 512M enabled (table at 0x000000F400900000).
[    5.583371] [drm] use_doorbell being set to: [true]
[    5.583960] [drm] use_doorbell being set to: [true]
[    5.584051] amdgpu: [powerplay] hwmgr_sw_init smu backed is vega10_smu
[    5.586084] [drm] Found UVD firmware Version: 66.43 Family ID: 17
[    5.586090] [drm] PSP loading UVD firmware
[    5.587716] [drm] Found VCE firmware Version: 57.6 Binary ID: 4
[    5.587752] [drm] PSP loading VCE firmware
[    5.755009] kvm: Nested Virtualization enabled
[    5.755020] SVM: kvm: Nested Paging enabled
[    5.755021] SVM: Virtual VMLOAD VMSAVE supported
[    5.755021] SVM: Virtual GIF supported
[    5.758272] MCE: In-kernel MCE decoding enabled.
[    5.759775] ppdev: user-space parallel port driver
[    5.761006] EDAC amd64: F17h_M10h detected (node 0).
[    5.761081] EDAC amd64: Node 0: DRAM ECC disabled.
[    5.776960] [drm] reserve 0x400000 from 0xf5fe800000 for PSP TMR
[    5.826283] r8169 0000:1b:00.0 enp27s0: renamed from eth0
[    5.827091] EDAC amd64: F17h_M10h detected (node 0).
[    5.827174] EDAC amd64: Node 0: DRAM ECC disabled.
[    5.903719] EDAC amd64: F17h_M10h detected (node 0).
[    5.903849] EDAC amd64: Node 0: DRAM ECC disabled.
[    5.935166] [drm] kiq ring mec 2 pipe 1 q 0
[    5.946902] [drm] Display Core initialized with v3.2.76!
[    5.960109] Adding 8388604k swap on /dev/mapper/lonestar_LVM-LVM_SWAP.  Priority:-2 extents:1 across:8388604k SSFS
[    5.966978] snd_hda_intel 0000:12:00.1: bound 0000:12:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[    6.001929] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    6.003974] EDAC amd64: F17h_M10h detected (node 0).
[    6.004062] EDAC amd64: Node 0: DRAM ECC disabled.
[    6.023302] [drm] UVD and UVD ENC initialized successfully.
[    6.054120] EDAC amd64: F17h_M10h detected (node 0).
[    6.054216] EDAC amd64: Node 0: DRAM ECC disabled.
[    6.058447] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: discard
[    6.061651] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: discard
[    6.063798] EXT4-fs (dm-7): mounted filesystem with ordered data mode. Opts: discard
[    6.065580] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: discard
[    6.117187] EDAC amd64: F17h_M10h detected (node 0).
[    6.117267] EDAC amd64: Node 0: DRAM ECC disabled.
[    6.123987] [drm] VCE initialized successfully.
[    6.125205] kfd kfd: Allocated 3969056 bytes on gart
[    6.125802] Virtual CRAT table created for GPU
[    6.125803] Parsing CRAT table with 1 nodes
[    6.125812] Creating topology SYSFS entries
[    6.125961] Topology: Add dGPU node [0x687f:0x1002]
[    6.125964] kfd kfd: added device 1002:687f
[    6.127280] [drm] fb mappable at 0xE0CEE000
[    6.127281] [drm] vram apper at 0xE0000000
[    6.127281] [drm] size 11059200
[    6.127282] [drm] fb depth is 24
[    6.127282] [drm]    pitch is 10240
[    6.127365] fbcon: amdgpudrmfb (fb0) is primary device
[    6.151737] Console: switching to colour frame buffer device 320x67
[    6.172410] amdgpu 0000:12:00.0: fb0: amdgpudrmfb frame buffer device
[    6.196647] EDAC amd64: F17h_M10h detected (node 0).
[    6.196757] EDAC amd64: Node 0: DRAM ECC disabled.
[    6.213439] amdgpu 0000:12:00.0: ring gfx uses VM inv eng 0 on hub 0
[    6.213441] amdgpu 0000:12:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[    6.213443] amdgpu 0000:12:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[    6.213444] amdgpu 0000:12:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[    6.213445] amdgpu 0000:12:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[    6.213447] amdgpu 0000:12:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[    6.213448] amdgpu 0000:12:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[    6.213449] amdgpu 0000:12:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[    6.213450] amdgpu 0000:12:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[    6.213451] amdgpu 0000:12:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[    6.213452] amdgpu 0000:12:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[    6.213453] amdgpu 0000:12:00.0: ring page0 uses VM inv eng 1 on hub 1
[    6.213454] amdgpu 0000:12:00.0: ring sdma1 uses VM inv eng 4 on hub 1
[    6.213455] amdgpu 0000:12:00.0: ring page1 uses VM inv eng 5 on hub 1
[    6.213456] amdgpu 0000:12:00.0: ring uvd_0 uses VM inv eng 6 on hub 1
[    6.213457] amdgpu 0000:12:00.0: ring uvd_enc_0.0 uses VM inv eng 7 on hub 1
[    6.213458] amdgpu 0000:12:00.0: ring uvd_enc_0.1 uses VM inv eng 8 on hub 1
[    6.213460] amdgpu 0000:12:00.0: ring vce0 uses VM inv eng 9 on hub 1
[    6.213461] amdgpu 0000:12:00.0: ring vce1 uses VM inv eng 10 on hub 1
[    6.213462] amdgpu 0000:12:00.0: ring vce2 uses VM inv eng 11 on hub 1
[    6.213463] [drm] ECC is not present.
[    6.213466] [drm] SRAM ECC is not present.
[    6.214782] [drm] Initialized amdgpu 3.37.0 20150101 for 0000:12:00.0 on minor 0
[    6.214964] amdgpu 0000:38:00.0: enabling device (0000 -> 0003)
[    6.215067] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1462:0x7A38 0xC6).
[    6.215087] [drm] register mmio base: 0xFE400000
[    6.215088] [drm] register mmio size: 524288
[    6.215107] [drm] add ip block number 0 <soc15_common>
[    6.215108] [drm] add ip block number 1 <gmc_v9_0>
[    6.215109] [drm] add ip block number 2 <vega10_ih>
[    6.215110] [drm] add ip block number 3 <psp>
[    6.215111] [drm] add ip block number 4 <gfx_v9_0>
[    6.215112] [drm] add ip block number 5 <sdma_v4_0>
[    6.215113] [drm] add ip block number 6 <powerplay>
[    6.215114] [drm] add ip block number 7 <dm>
[    6.215115] [drm] add ip block number 8 <vcn_v1_0>
[    6.226499] [drm] BIOS signature incorrect ff ff
[    6.226505] amdgpu 0000:38:00.0: BAR 6: can't assign [??? 0x00000000 flags 0x20000000] (bogus alignment)
[    6.231037] [drm] BIOS signature incorrect ff ff
[    6.232475] ATOM BIOS: 113-RAVEN-107
[    6.233137] [drm] VCN decode is enabled in VM mode
[    6.233137] [drm] VCN encode is enabled in VM mode
[    6.233138] [drm] JPEG decode is enabled in VM mode
[    6.233156] [drm] GPU posting now...
[    6.233416] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[    6.233422] amdgpu 0000:38:00.0: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[    6.233424] amdgpu 0000:38:00.0: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[    6.233426] amdgpu 0000:38:00.0: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
[    6.233430] [drm] Detected VRAM RAM=2048M, BAR=2048M
[    6.233430] [drm] RAM width 128bits DDR4
[    6.233452] [drm] amdgpu: 2048M of VRAM memory ready
[    6.233454] [drm] amdgpu: 3072M of GTT memory ready.
[    6.233456] [drm] GART: num cpu pages 262144, num gpu pages 262144
[    6.233581] [drm] PCIE GART of 1024M enabled (table at 0x000000F400900000).
[    6.241062] [drm] use_doorbell being set to: [true]
[    6.241121] amdgpu: [powerplay] hwmgr_sw_init smu backed is smu10_smu
[    6.242314] [drm] Found VCN firmware Version ENC: 1.9 DEC: 1 VEP: 0 Revision: 28
[    6.242321] [drm] PSP loading VCN firmware
[    6.260186] EDAC amd64: F17h_M10h detected (node 0).
[    6.260262] EDAC amd64: Node 0: DRAM ECC disabled.
[    6.263393] [drm] reserve 0x400000 from 0xf47f800000 for PSP TMR
[    6.303406] elogind-daemon[1604]: Watching system buttons on /dev/input/event1 (Power Button)
[    6.360247] elogind-daemon[1604]: Watching system buttons on /dev/input/event0 (Power Button)
[    6.440029] amdgpu 0000:38:00.0: RAS: optional ras ta ucode is not available
[    6.461645] [drm] kiq ring mec 2 pipe 1 q 0
[    6.461994] [drm] DM_PPLIB: values for F clock
[    6.461995] [drm] DM_PPLIB:	 1600000 in kHz, 4399 in mV
[    6.461996] [drm] DM_PPLIB: values for DCF clock
[    6.461997] [drm] DM_PPLIB:	 300000 in kHz, 3649 in mV
[    6.461997] [drm] DM_PPLIB:	 600000 in kHz, 4074 in mV
[    6.461997] [drm] DM_PPLIB:	 626000 in kHz, 4250 in mV
[    6.461998] [drm] DM_PPLIB:	 654000 in kHz, 4399 in mV
[    6.462156] [drm] Unsupported Connector type:21!
[    6.462161] [drm] Unsupported Connector type:21!
[    6.462165] [drm] Unsupported Connector type:21!
[    6.462170] [drm] Unsupported Connector type:21!
[    6.462171] [drm] Display Core initialized with v3.2.76!
[    6.462529] BUG: kernel NULL pointer dereference, address: 0000000000000f28
[    6.462557] #PF: supervisor write access in kernel mode
[    6.462574] #PF: error_code(0x0002) - not-present page
[    6.462589] PGD 0 P4D 0 
[    6.462600] Oops: 0002 [#1] PREEMPT SMP NOPTI
[    6.462615] CPU: 2 PID: 958 Comm: udevd Not tainted 5.7.6-artix1-1 #1
[    6.462634] Hardware name: Micro-Star International Co., Ltd. MS-7A38/B350M BAZOOKA (MS-7A38), BIOS 1.J0 01/21/2019
[    6.462760] RIP: 0010:hdcp_create_workqueue+0x67/0x2f0 [amdgpu]
[    6.462778] Code: 48 89 c7 e8 ab e6 d7 e2 49 89 c4 48 85 c0 0f 84 8d 02 00 00 48 8b 3d 10 4f cf e3 ba 00 14 00 00 be c0 0d 00 00 e8 79 ed d7 e2 <49> 89 84 24 18 0f 00 00 48 85 c0 0f 84 44 02 00 00 48 8b 3d e9 4e
[    6.462830] RSP: 0018:ffffa3f801d87860 EFLAGS: 00010286
[    6.462847] RAX: ffff953cdcafe000 RBX: ffff953cdca60000 RCX: 0000000000000000
[    6.462868] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff953cdcb00000
[    6.462889] RBP: 0000000000000000 R08: ffff953cdcafe000 R09: ffff953cdcafe000
[    6.462910] R10: 00d0afdc3c95ffff R11: 0000000000000006 R12: 0000000000000010
[    6.462931] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000007
[    6.462952] FS:  00007fb2edac1bc0(0000) GS:ffff953cf0e80000(0000) knlGS:0000000000000000
[    6.462976] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    6.462993] CR2: 0000000000000f28 CR3: 000000042d3de000 CR4: 00000000003406e0
[    6.463014] Call Trace:
[    6.463115]  amdgpu_dm_init.isra.0.cold+0xa0/0x1057 [amdgpu]
[    6.463311]  dm_hw_init+0xe/0x20 [amdgpu]
[    6.463507]  amdgpu_device_init.cold+0x1531/0x195b [amdgpu]
[    6.463675]  amdgpu_driver_load_kms+0x5c/0x200 [amdgpu]
[    6.463838]  amdgpu_pci_probe+0xf4/0x180 [amdgpu]
[    6.463871]  local_pci_probe+0x42/0x80
[    6.466104]  ? pci_match_device+0xd7/0x100
[    6.468323]  pci_device_probe+0xfa/0x1b0
[    6.470549]  really_probe+0x167/0x410
[    6.472777]  driver_probe_device+0xb6/0x100
[    6.472780]  device_driver_attach+0xa1/0xb0
[    6.472783]  __driver_attach+0x8a/0x150
[    6.472786]  ? device_driver_attach+0xb0/0xb0
[    6.472788]  ? device_driver_attach+0xb0/0xb0
[    6.472791]  bus_for_each_dev+0x89/0xd0
[    6.472794]  bus_add_driver+0x12b/0x1e0
[    6.472797]  driver_register+0x8b/0xe0
[    6.472799]  ? 0xffffffffc0f05000
[    6.472803]  do_one_initcall+0x59/0x240
[    6.472808]  do_init_module+0x5c/0x260
[    6.472811]  load_module+0x2137/0x23a0
[    6.472818]  __do_sys_init_module+0x172/0x1a0
[    6.472824]  do_syscall_64+0x49/0x90
[    6.472827]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    6.472829] RIP: 0033:0x7fb2edf0c73e
[    6.472832] Code: 48 8b 0d 55 f7 0b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 22 f7 0b 00 f7 d8 64 89 01 48
[    6.472834] RSP: 002b:00007ffeb453d608 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    6.472836] RAX: ffffffffffffffda RBX: 000055c6b5cb20e0 RCX: 00007fb2edf0c73e
[    6.472836] RDX: 00007fb2edfe697d RSI: 00000000009e8461 RDI: 00007fb2ebe3b010
[    6.472837] RBP: 00007fb2ebe3b010 R08: 000055c6b5cc2b10 R09: 00000000009e8470
[    6.472838] R10: 0000000000000007 R11: 0000000000000246 R12: 00007fb2edfe697d
[    6.472839] R13: 00007ffeb453d780 R14: 000055c6b5cb5110 R15: 000055c6b5cb20e0
[    6.472842] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat ppdev edac_mce_amd kvm_amd wmi_bmof kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd amdgpu(+) glue_helper pcspkr r8169 ccp k10temp sp5100_tco realtek i2c_piix4 rng_core libphy snd_hda_codec_realtek gpu_sched input_leds snd_hda_codec_generic i2c_algo_bit ledtrig_audio ttm snd_hda_codec_hdmi joydev drm_kms_helper snd_hda_intel snd_intel_dspcfg cec snd_hda_codec rc_core drm snd_hda_core snd_hwdep snd_pcm snd_timer agpgart snd syscopyarea sysfillrect sysimgblt mousedev fb_sys_fops soundcore sg parport_pc evdev crypto_user parport mac_hid pinctrl_amd gpio_amdpt wmi acpi_cpufreq ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid uas usb_storage dm_mod xhci_pci crc32c_intel xhci_hcd
[    6.472878] CR2: 0000000000000f28
[    6.472880] ---[ end trace 026b364343728c26 ]---
[    6.473058] RIP: 0010:hdcp_create_workqueue+0x67/0x2f0 [amdgpu]
[    6.473062] Code: 48 89 c7 e8 ab e6 d7 e2 49 89 c4 48 85 c0 0f 84 8d 02 00 00 48 8b 3d 10 4f cf e3 ba 00 14 00 00 be c0 0d 00 00 e8 79 ed d7 e2 <49> 89 84 24 18 0f 00 00 48 85 c0 0f 84 44 02 00 00 48 8b 3d e9 4e
[    6.547346] RSP: 0018:ffffa3f801d87860 EFLAGS: 00010286
[    6.547348] RAX: ffff953cdcafe000 RBX: ffff953cdca60000 RCX: 0000000000000000
[    6.547350] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff953cdcb00000
[    6.547351] RBP: 0000000000000000 R08: ffff953cdcafe000 R09: ffff953cdcafe000
[    6.547352] R10: 00d0afdc3c95ffff R11: 0000000000000006 R12: 0000000000000010
[    6.547353] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000007
[    6.547355] FS:  00007fb2edac1bc0(0000) GS:ffff953cf0e80000(0000) knlGS:0000000000000000
[    6.547356] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    6.547358] CR2: 0000000000000f28 CR3: 000000042d3de000 CR4: 00000000003406e0
[    6.549594] udevd[916]: worker [958] terminated by signal 9 (Killed)
[    6.566940] udevd[916]: worker [958] failed while handling '/devices/pci0000:00/0000:00:01.1/0000:10:00.0/0000:11:00.0/0000:12:00.0'
[    6.830413] elogind-daemon[1604]: Watching system buttons on /dev/input/event10 (Logitech G9 Laser Mouse Consumer Control)
[    6.833544] elogind-daemon[1604]: Watching system buttons on /dev/input/event9 (Logitech G9 Laser Mouse Keyboard)
[    6.836583] elogind-daemon[1604]: Watching system buttons on /dev/input/event3 (ErgoDox EZ ErgoDox EZ)
[    6.839615] elogind-daemon[1604]: Watching system buttons on /dev/input/event5 (ErgoDox EZ ErgoDox EZ System Control)
[    6.841878] elogind-daemon[1604]: Watching system buttons on /dev/input/event6 (ErgoDox EZ ErgoDox EZ Consumer Control)
[    6.844073] elogind-daemon[1604]: Watching system buttons on /dev/input/event7 (ErgoDox EZ ErgoDox EZ)
[    7.216835] elogind-daemon[1604]: New seat seat0.
[    7.783405] Generic FE-GE Realtek PHY r8169-1b00:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-1b00:00, irq=IGNORE)
[    7.864535] r8169 0000:1b:00.0 enp27s0: Link is Down
[    8.954771] random: crng init done
[    8.955874] random: 7 urandom warning(s) missed due to ratelimiting
[   10.611720] amdgpu 0000:12:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[   10.611726] amdgpu 0000:38:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
[   10.855468] r8169 0000:1b:00.0 enp27s0: Link is Up - 1Gbps/Full - flow control rx/tx
[   10.855481] IPv6: ADDRCONF(NETDEV_CHANGE): enp27s0: link becomes ready
[   11.769132] elogind-daemon[1604]: New session c1 of user sddm.
[   16.448979] elogind-daemon[1604]: New session 1 of user lonestar.
[   16.482613] elogind-daemon[1604]: Removed session c1.
[   16.946161] fuse: init (API version 7.31)
[   20.505727] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)






I'll only add that I rebooted about 4 times, and about half of them got me to sddm and a graphical interface.
 

Re: sddm not loading (and other potential issues)

Reply #23 –
Quote
    6.463014] Call Trace:
[    6.463115]  amdgpu_dm_init.isra.0.cold+0xa0/0x1057 [amdgpu]
[    6.463311]  dm_hw_init+0xe/0x20 [amdgpu]
[    6.463507]  amdgpu_device_init.cold+0x1531/0x195b [amdgpu]
[    6.463675]  amdgpu_driver_load_kms+0x5c/0x200 [amdgpu]
[    6.463838]  amdgpu_pci_probe+0xf4/0x180 [amdgpu]
[    6.463871]  local_pci_probe+0x42/0x80
[    6.466104]  ? pci_match_device+0xd7/0x100
[    6.468323]  pci_device_probe+0xfa/0x1b0
[    6.470549]  really_probe+0x167/0x410
[    6.472777]  driver_probe_device+0xb6/0x100
[    6.472780]  device_driver_attach+0xa1/0xb0
[    6.472783]  __driver_attach+0x8a/0x150
[    6.472786]  ? device_driver_attach+0xb0/0xb0
[    6.472788]  ? device_driver_attach+0xb0/0xb0
[    6.472791]  bus_for_each_dev+0x89/0xd0
[    6.472794]  bus_add_driver+0x12b/0x1e0
[    6.472797]  driver_register+0x8b/0xe0
[    6.472799]  ? 0xffffffffc0f05000
[    6.472803]  do_one_initcall+0x59/0x240
[    6.472808]  do_init_module+0x5c/0x260
[    6.472811]  load_module+0x2137/0x23a0
[    6.472818]  __do_sys_init_module+0x172/0x1a0
[    6.472824]  do_syscall_64+0x49/0x90
[    6.472827]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    6.472829] RIP: 0033:0x7fb2edf0c73e
[    6.472832] Code: 48 8b 0d 55 f7 0b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 22 f7 0b 00 f7 d8 64 89 01 48
[    6.472834] RSP: 002b:00007ffeb453d608 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
[    6.472836] RAX: ffffffffffffffda RBX: 000055c6b5cb20e0 RCX: 00007fb2edf0c73e
[    6.472836] RDX: 00007fb2edfe697d RSI: 00000000009e8461 RDI: 00007fb2ebe3b010
[    6.472837] RBP: 00007fb2ebe3b010 R08: 000055c6b5cc2b10 R09: 00000000009e8470
[    6.472838] R10: 0000000000000007 R11: 0000000000000246 R12: 00007fb2edfe697d
[    6.472839] R13: 00007ffeb453d780 R14: 000055c6b5cb5110 R15: 000055c6b5cb20e0
[    6.472842] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat ppdev edac_mce_amd kvm_amd wmi_bmof kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd amdgpu(+) glue_helper pcspkr r8169 ccp k10temp sp5100_tco realtek i2c_piix4 rng_core libphy snd_hda_codec_realtek gpu_sched input_leds snd_hda_codec_generic i2c_algo_bit ledtrig_audio ttm snd_hda_codec_hdmi joydev drm_kms_helper snd_hda_intel snd_intel_dspcfg cec snd_hda_codec rc_core drm snd_hda_core snd_hwdep snd_pcm snd_timer agpgart snd syscopyarea sysfillrect sysimgblt mousedev fb_sys_fops soundcore sg parport_pc evdev crypto_user parport mac_hid pinctrl_amd gpio_amdpt wmi acpi_cpufreq ext4 crc32c_generic crc16 mbcache jbd2 hid_generic usbhid hid uas usb_storage dm_mod xhci_pci crc32c_intel xhci_hcd
[    6.472878] CR2: 0000000000000f28
[    6.472880] ---[ end trace 026b364343728c26 ]---
Hey dude, don't be surprised, that your system not works, your kernel crash.
I see, you have ryzen procesor?  What for procesor you have?
Which kernel parameters you use in boot? Put here compete dmesg.
Your problem have nothing to do with openrc, but with your hw (gpu) and kernel.
What for libdrm, mesa, kernel use you?

Re: sddm not loading (and other potential issues)

Reply #24 –
Quote from: alium – on
Hey dude, don't be surprised, that your system not works, your kernel crash.
Don't worry, not surprised given how weird this machine is acting. :)

Quote from: alium – on
I see, you have ryzen procesor?  What for procesor you have?
Short answer is a Ryzen 5 2400G APU.
Added the results of hwinfo --short to the opening post if it helps.



Quote from: alium – on
Which kernel parameters you use in boot? Put here compete dmesg.
Added the dmesg and sysctl -a as attachments to this post.
Weird observation: I have a backup of this Artix on a flash drive during this issue and it never shows the kernel crash I noticed (even though it doesn't always boot into the graphical sddm either). Ubuntu has never shown this error and has never had trouble reaching login.



Quote from: alium – on
Your problem have nothing to do with openrc, but with your hw (gpu) and kernel.
What for libdrm, mesa, kernel use you?
Results from pacman -Qq
Code: [Select]
lib32-libdrm 2.4.100-1
libdrm 2.4.102-1
lib32-mesa 19.3.4-3
lib32-mesa-vdpau 19.3.4-3
libva-mesa-driver 20.1.2-1
mesa 20.1.2-1
mesa-demos 8.4.0-2
mesa-vdpau 20.1.2-1
archlinux-appstream-data 20200612-1
archlinux-keyring 20200622-1
archlinux-mirrorlist 20200411-1
lib32-util-linux 2.35.1-1
libutil-linux 2.35.2-1
linux 5.7.6.artix1-1
linux-api-headers 5.6.11-1
linux-firmware 20200519.8ba6fa6-1
linux-headers 5.7.6.artix1-1

Re: sddm not loading (and other potential issues)

Reply #26 –
the amd-ucode does exist.

I can try the update to the motherboard.
I'm running the latest stable update which was working fine for over a year.
Is it likely that updates to software/kernel/etc would trigger a need for a bios update?

Will report back on the bios update in a bit.

Re: sddm not loading (and other potential issues)

Reply #27 –
Progress!
Attached is the dmesg after the update (OS was already up to date)

Changes:
  • Didn't see the error at boot.
  • Don't see the error in dmesg
  • shutdown doesn't pause at udev then stop a worker
  • kvm exit doesn't hang on shutdown
  • Suspend appears to work again (didn't report that before)/color]

Only two oddities are
  • [    0.347623] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
  • [    5.126973] sp5100-tco sp5100-tco: Watchdog hardware is disabled

Maybe these aren't big deals, just alerts. I have no idea what Watchdog is and will look up later.
Got the gist of what watchdog does and isn't needed on a desktop typically.
Still not sure about the conflicting IOMMU thing (Unable to read/write) then proceeds to add iommu groups two lines later.




I'm going to give it a day or two reboots JUST to make sure because I'm skittish now :)


I'm hopeful though, and I apologize it was a BIOS update that was the culprit (Feels a little like I just found out the computer wasn't plugged in or something simple like that).



Thank you to everyone, but especially alium for your help.

Re: sddm not loading (and other potential issues)

Reply #28 –
good to hear!!

Quote from: InkStone – on
Is it likely that updates to software/kernel/etc would trigger a need for a bios update?

not necessary - should not directly require.  MSI just fixed with combo 1.0.0.4 (this prepare AMD self, what is reason, why is this update important) a lots bugs in BIOS and added  some optimalisation  8)

your dmesg report just looked like something wasn't working perfectly in the HW (and linux has the ability to write what exactly, unlike Windows "an error has occurred")

Re: sddm not loading (and other potential issues)

Reply #29 –
Quote
Only two oddities are
[    0.347623] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[    5.126973] sp5100-tco sp5100-tco: Watchdog hardware is disabled

i have same warnings, but i think is nothing important...
I don't use Watchdog too, but it can be turned on somewhere