You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2019-12-18 20:19:55
- driwach
- Member
- Registered: 2019-12-18
- Posts: 7
[SOLVED]Arch stuck on boot
Hello,
i have a problem when starting arch just
1/3 time it get booted correctly without problem
1/3 : hang on boot after passing grub menu, and before display manager(gnome)
1/3: booted to desktop enviroment but work very slow and i had to reboot it by shutdown button .
and i,ve tired both kde and gnome but still the same
a little info of my hardware
ryzen 5 3500u
[amd vega 8]
ssd nvme 256gb
8 gb ddr4
this
dmesg output
[ 4.216670] Bluetooth: hci0: RTL: fw version 0x826ca99e
[ 4.220523] EDAC amd64: Node 0: DRAM ECC disabled.
[ 4.220525] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 4.254095] [drm] DM_PPLIB: values for F clock
[ 4.254098] [drm] DM_PPLIB: 400000 in kHz, 2974 in mV
[ 4.254099] [drm] DM_PPLIB: 933000 in kHz, 3274 in mV
[ 4.254100] [drm] DM_PPLIB: 1067000 in kHz, 3924 in mV
[ 4.254101] [drm] DM_PPLIB: 1200000 in kHz, 4074 in mV
[ 4.254103] [drm] DM_PPLIB: values for DCF clock
[ 4.254104] [drm] DM_PPLIB: 300000 in kHz, 2974 in mV
[ 4.254105] [drm] DM_PPLIB: 600000 in kHz, 3274 in mV
[ 4.254106] [drm] DM_PPLIB: 626000 in kHz, 3924 in mV
[ 4.254107] [drm] DM_PPLIB: 654000 in kHz, 4074 in mV
[ 4.260588] [drm] Display Core initialized with v3.2.48!
[ 4.260811] snd_hda_intel 0000:04:00.1: bound 0000:04:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[ 4.270200] [drm] SADs count is: -2, don't need to read it
[ 4.271653] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.271654] [drm] Driver supports precise vblank timestamp query.
[ 4.275616] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 4.278977] kfd kfd: Allocated 3969056 bytes on gart
[ 4.281023] Topology: Add APU node [0x15d8:0x1002]
[ 4.281028] kfd kfd: added device 1002:15d8
[ 4.282813] [drm] fb mappable at 0x1BFBC5000
[ 4.282815] [drm] vram apper at 0x1BF000000
[ 4.282816] [drm] size 8294400
[ 4.282817] [drm] fb depth is 24
[ 4.282818] [drm] pitch is 7680
[ 4.282957] fbcon: amdgpudrmfb (fb0) is primary device
[ 4.283596] EDAC amd64: Node 0: DRAM ECC disabled.
[ 4.283599] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
(Note that use of the override may cause unknown side effects.)
[ 4.285980] Console: switching to colour frame buffer device 240x67
[ 4.302965] amdgpu 0000:04:00.0: fb0: amdgpudrmfb frame buffer device
[ 4.332904] amdgpu 0000:04:00.0: ring gfx uses VM inv eng 0 on hub 0
[ 4.332910] amdgpu 0000:04:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 4.332914] amdgpu 0000:04:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 4.332917] amdgpu 0000:04:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 4.332920] amdgpu 0000:04:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 4.332922] amdgpu 0000:04:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 4.332925] amdgpu 0000:04:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 4.332927] amdgpu 0000:04:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 4.332930] amdgpu 0000:04:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 4.332933] amdgpu 0000:04:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[ 4.332936] amdgpu 0000:04:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[ 4.332939] amdgpu 0000:04:00.0: ring vcn_dec uses VM inv eng 1 on hub 1
[ 4.332942] amdgpu 0000:04:00.0: ring vcn_enc0 uses VM inv eng 4 on hub 1
[ 4.332944] amdgpu 0000:04:00.0: ring vcn_enc1 uses VM inv eng 5 on hub 1
[ 4.332948] amdgpu 0000:04:00.0: ring vcn_jpeg uses VM inv eng 6 on hub 1
[ 4.362463] [drm] Initialized amdgpu 3.35.0 20150101 for 0000:04:00.0 on minor 0
[ 4.904082] systemd-journald[332]: File /var/log/journal/6e6dbd09bc1241718fe0a5bd5a67884b/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[ 7.419473] fuse: init (API version 7.31)
[ 7.419562] *** VALIDATE fuse ***
[ 7.419570] *** VALIDATE fuse ***
[ 7.632444] kauditd_printk_skb: 26 callbacks suppressed
[ 7.632447] audit: type=1130 audit(1576702744.116:37): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 8.048093] audit: type=1130 audit(1576702744.533:38): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=upower comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 8.403826] audit: type=1130 audit(1576702744.889:39): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=udisks2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 8.866345] audit: type=1131 audit(1576702745.353:40): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 9.340635] rfkill: input handler disabled
[ 9.437179] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 10.123217] audit: type=1130 audit(1576702746.609:41): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=colord comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 10.576105] audit: type=1130 audit(1576702747.063:42): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 14.178900] audit: type=1131 audit(1576702750.663:43): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 40.100079] audit: type=1131 audit(1576702776.586:44): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 40.609617] audit: type=1131 audit(1576702777.096:45): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 68.200271] audit: type=1131 audit(1576702804.686:46): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 185.342704] audit: type=1130 audit(1576702921.828:47): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 215.386329] audit: type=1131 audit(1576702951.872:48): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 351.446273] audit: type=1130 audit(1576703087.934:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 381.496734] audit: type=1131 audit(1576703117.984:50): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 904.389533] audit: type=1130 audit(1576703640.878:51): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 904.389543] audit: type=1131 audit(1576703640.878:52): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 952.090282] ------------[ cut here ]------------
[ 952.090359] WARNING: CPU: 2 PID: 603 at /var/lib/dkms/rtl8821ce/1.0.5.r76.g7c4f827/build/hal/hal_com.c:11447 rtw_lps_state_chk+0x34/0x3a [8821ce]
[ 952.090361] Modules linked in: fuse amdgpu joydev mousedev edac_mce_amd 8821ce(OE) kvm_amd ccp rng_core gpu_sched i2c_algo_bit snd_hda_codec_realtek ttm kvm snd_hda_codec_generic uvcvideo ledtrig_audio btusb snd_hda_codec_hdmi pktcdvd hid_rmi videobuf2_vmalloc btrtl videobuf2_memops btbcm rmi_core snd_hda_intel videobuf2_v4l2 btintel drm_kms_helper hid_generic wmi_bmof irqbypass snd_intel_nhlt bluetooth snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul videobuf2_common snd_hwdep ecdh_generic drm ghash_clmulni_intel videodev snd_pcm ecc cfg80211 mc r8169 crc16 aesni_intel snd_timer agpgart sp5100_tco crypto_simd input_leds pcspkr syscopyarea snd ideapad_laptop k10temp i2c_piix4 cryptd realtek sysfillrect glue_helper sysimgblt sparse_keymap libphy fb_sys_fops soundcore snd_pci_acp3x rfkill battery i2c_hid hid wmi evdev ac pinctrl_amd mac_hid acpi_cpufreq vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) sg crypto_user ip_tables x_tables sr_mod cdrom btrfs libcrc32c crc32c_generic xor
[ 952.090429] serio_raw atkbd libps2 ahci libahci raid6_pq libata crc32c_intel xhci_pci scsi_mod xhci_hcd i8042 serio
[ 952.090443] CPU: 2 PID: 603 Comm: RTW_CMD_THREAD Tainted: G OE 5.4.3-arch1-1 #1
[ 952.090445] Hardware name: LENOVO 81V5/LNVNB161216, BIOS ARCN33WW 10/28/2019
[ 952.090511] RIP: 0010:rtw_lps_state_chk+0x34/0x3a [8821ce]
[ 952.090515] Code: 55 53 48 89 fd bb 0b 00 00 00 be 04 06 00 00 48 89 ef e8 d7 7a f9 ff 84 c0 79 11 bf 01 00 00 00 e8 b1 7f fd ff 80 eb 01 75 e0 <0f> 0b 5b 5d c3 c3 0f 1f 44 00 00 55 53 48 83 ec 10 48 89 d5 65 48
[ 952.090517] RSP: 0018:ffff9c9c80e7fc90 EFLAGS: 00010246
[ 952.090519] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[ 952.090520] RDX: ffff95cbf889de00 RSI: 0000000000000002 RDI: ffff9c9c80e7fbe0
[ 952.090521] RBP: ffff9c9c804ed000 R08: 0000000000000000 R09: 000000000000000e
[ 952.090523] R10: 0000000000000003 R11: ffff95cbf88a97c0 R12: ffff9c9c80e7fd4c
[ 952.090524] R13: ffff9c9c811df000 R14: ffff9c9c811df000 R15: 0000000000000000
[ 952.090526] FS: 0000000000000000(0000) GS:ffff95cbf8880000(0000) knlGS:0000000000000000
[ 952.090527] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 952.090528] CR2: 00003d3132bc3008 CR3: 00000001a5b16000 CR4: 00000000003406e0
[ 952.090530] Call Trace:
[ 952.090602] SetHwReg+0x17b/0x703 [8821ce]
[ 952.090667] rtl8821c_sethwreg+0xce9/0xd3c [8821ce]
[ 952.090731] sethwreg+0x25/0x140 [8821ce]
[ 952.090797] rtw_hal_set_hwreg+0x15/0x16 [8821ce]
[ 952.090847] rtw_set_ps_mode+0xd7/0x1e7 [8821ce]
[ 952.090897] LPS_Leave+0xcc/0xeb [8821ce]
[ 952.090933] traffic_status_watchdog+0x1de/0x2e4 [8821ce]
[ 952.090979] ? _rtw_mi_dynamic_check_timer_handlder+0x10/0x10 [8821ce]
[ 952.091013] ? session_tracker_cmd_hdl+0x1bf/0x1bf [8821ce]
[ 952.091047] rtw_iface_dynamic_chk_wk_hdl+0x55/0x1a2 [8821ce]
[ 952.091091] ? _rtw_mi_dynamic_check_timer_handlder+0x10/0x10 [8821ce]
[ 952.091134] _rtw_mi_dynamic_chk_wk_hdl+0xa/0x10 [8821ce]
[ 952.091180] _rtw_mi_process+0x60/0x75 [8821ce]
[ 952.091226] rtw_mi_dynamic_chk_wk_hdl+0x1b/0x1c [8821ce]
[ 952.091259] rtw_dynamic_chk_wk_hdl+0xe/0x45 [8821ce]
[ 952.091294] rtw_drvextra_cmd_hdl+0xa9/0x415 [8821ce]
[ 952.091328] rtw_cmd_thread+0x295/0x3ed [8821ce]
[ 952.091335] ? _raw_spin_lock_irqsave+0x26/0x50
[ 952.091340] kthread+0xfb/0x130
[ 952.091374] ? rtw_stop_cmd_thread+0x39/0x39 [8821ce]
[ 952.091376] ? kthread_park+0x90/0x90
[ 952.091378] ret_from_fork+0x22/0x40
[ 952.091384] ---[ end trace 720251df9770f889 ]---journalctl
-- Logs begin at Mon 2019-12-16 21:45:13 CET, end at Wed 2019-12-18 22:18:52 CE>
de des. 16 21:45:13 driwach kernel: Linux version 5.4.3-arch1-1 (linux@archlinu>
de des. 16 21:45:13 driwach kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linu>
de des. 16 21:45:13 driwach kernel: KERNEL supported cpus:
de des. 16 21:45:13 driwach kernel: Intel GenuineIntel
de des. 16 21:45:13 driwach kernel: AMD AuthenticAMD
de des. 16 21:45:13 driwach kernel: Hygon HygonGenuine
de des. 16 21:45:13 driwach kernel: Centaur CentaurHauls
de des. 16 21:45:13 driwach kernel: zhaoxin Shanghai
de des. 16 21:45:13 driwach kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x>
de des. 16 21:45:13 driwach kernel: x86/fpu: Supporting XSAVE feature 0x002: 'S>
de des. 16 21:45:13 driwach kernel: x86/fpu: Supporting XSAVE feature 0x004: 'A>
de des. 16 21:45:13 driwach kernel: x86/fpu: xstate_offset[2]: 576, xstate_siz>
de des. 16 21:45:13 driwach kernel: x86/fpu: Enabled xstate features 0x7, conte>
de des. 16 21:45:13 driwach kernel: BIOS-provided physical RAM map:
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x0000000000000000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x000000000009f000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x00000000000e0000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x0000000000100000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x0000000009c00000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x0000000009cd1000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x0000000009f00000-0x000000>
de des. 16 21:45:13 driwach kernel: BIOS-e820: [mem 0x0000000009f0b000-0x000000>and thankyou for reading all this .
Last edited by driwach (2019-12-19 18:58:19)
Offline
#2 2019-12-18 20:49:38
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 78,156
Re: [SOLVED]Arch stuck on boot
There's a crash in the rtl8821ce module, but please post the complete journal. You can eg. use https://wiki.archlinux.org/index.php/Pastebin to feed it into a pastebin service.
Offline
#3 2019-12-18 20:51:52
- loqs
- Member
- Registered: 2014-03-06
- Posts: 19,097
Re: [SOLVED]Arch stuck on boot
Is the dmesg from a working boot?
Can you please post the journal for a working boot, a slow boot and a stuck boot.
If the journal contents are too large to fit in code tags please post them to a pastebin and provide links.
The warning is from rtl8821ce. If you boot with that module blacklisted is the issue still present?
Offline
#4 2019-12-18 22:28:45
- driwach
- Member
- Registered: 2019-12-18
- Posts: 7
Re: [SOLVED]Arch stuck on boot
seth wrote:
There's a crash in the rtl8821ce module, but please post the complete journal. You can eg. use https://wiki.archlinux.org/index.php/Pastebin to feed it into a pastebin service.
Thankyou for answer yes
i use it
this the link of journal ctl of working system
Working Boot
Offline
#5 2019-12-18 22:35:51
- driwach
- Member
- Registered: 2019-12-18
- Posts: 7
Re: [SOLVED]Arch stuck on boot
loqs wrote:
Is the dmesg from a working boot?
Can you please post the journal for a working boot, a slow boot and a stuck boot.
If the journal contents are too large to fit in code tags please post them to a pastebin and provide links.
The warning is from rtl8821ce. If you boot with that module blacklisted is the issue still present?
Thankyou for your help
yes i did that but i didn't have a slow boot situation just stucks in boot but rarly boot normal
and those two of stuckboot jounalctl output because the first that won't boot i see this journal
First
and after i reboot i have this journal output (and this the same of others reboot until its booted normally)
Second
and i will try adding rtl8821ce to blacklist by grub booting
thankyou .
Offline
#6 2019-12-19 07:10:48
- seth
- Member
- From: Won't reply 2 private help req
- Registered: 2012-09-03
- Posts: 78,156
Re: [SOLVED]Arch stuck on boot
The multi-user.target is reached within 2 seconds bot times, I guess the system doesn't actually *boot* slow but this is related to GDM autostart and/or your gnome session.
Can you trigger slow boots when booting into the multi-user.target only?
https://wiki.archlinux.org/index.php/Sy … _boot_into
Because of
de des. 19 00:04:35 driwach systemd[642]: Started GNOME Session Manager (session: gnome).
de des. 19 00:04:35 driwach systemd[642]: Reached target GNOME Session Manager is ready.
de des. 19 00:04:35 driwach systemd[642]: Starting GNOME Shell on Wayland...
de des. 19 00:04:36 driwach gnome-shell[705]: Failed to open gpu '/dev/dri/card0': GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
de des. 19 00:04:36 driwach gnome-shell[705]: Failed to create backend: No GPUs found
de des. 19 00:04:36 driwach systemd[642]: gnome-shell-wayland.service: Failed with result 'protocol'.
de des. 19 00:04:36 driwach systemd[642]: Failed to start GNOME Shell on Wayland.
de des. 19 00:04:36 driwach systemd[642]: Dependency failed for GNOME Shell on Wayland.
de des. 19 00:04:36 driwach systemd[642]: Dependency failed for GNOME Wayland Session.
de des. 19 00:04:36 driwach systemd[642]: Dependency failed for GNOME Wayland Session (session: gnome).I'd suggest trying https://wiki.archlinux.org/index.php/Ke … _KMS_start
Also remove the <really ugly swearing here> "quiet" parameter so you can actually see what's going on during the boot.
Offline
#7 2019-12-19 18:57:02
- driwach
- Member
- Registered: 2019-12-18
- Posts: 7
Re: [SOLVED]Arch stuck on boot
seth wrote:
The multi-user.target is reached within 2 seconds bot times, I guess the system doesn't actually *boot* slow but this is related to GDM autostart and/or your gnome session.
Can you trigger slow boots when booting into the multi-user.target only?
https://wiki.archlinux.org/index.php/Sy … _boot_intoBecause of
de des. 19 00:04:35 driwach systemd[642]: Started GNOME Session Manager (session: gnome). de des. 19 00:04:35 driwach systemd[642]: Reached target GNOME Session Manager is ready. de des. 19 00:04:35 driwach systemd[642]: Starting GNOME Shell on Wayland... de des. 19 00:04:36 driwach gnome-shell[705]: Failed to open gpu '/dev/dri/card0': GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted de des. 19 00:04:36 driwach gnome-shell[705]: Failed to create backend: No GPUs found de des. 19 00:04:36 driwach systemd[642]: gnome-shell-wayland.service: Failed with result 'protocol'. de des. 19 00:04:36 driwach systemd[642]: Failed to start GNOME Shell on Wayland. de des. 19 00:04:36 driwach systemd[642]: Dependency failed for GNOME Shell on Wayland. de des. 19 00:04:36 driwach systemd[642]: Dependency failed for GNOME Wayland Session. de des. 19 00:04:36 driwach systemd[642]: Dependency failed for GNOME Wayland Session (session: gnome).I'd suggest trying https://wiki.archlinux.org/index.php/Ke … _KMS_start
Also remove the <really ugly swearing here> "quiet" parameter so you can actually see what's going on during the boot.
Thankyou so much of your help its worked well i have tried many time it dosen't stuck any more on boot by adding Early KMS, and very helping to disable quiet mode
thankyou and hope this help other membres in future .
have nice day
Offline
Pages: 1