You are not logged in.
I ran the upgrade for linux-4.20.arch1-1-x86_64 (and headers) and on reboot it gets just past the loading systemd verbage and then hangs completely, no response from capslock or ability to change TTY. Chroot in and downgrade to 4.19.12 and boots fine.
journalctl shows kernel messages for "Hardware Error" and then just cycles around repeating that indefinitely, probably the source of the locked boot as it spins its wheels.
Journal output here (i truncated the extra 10k lines of the same thing): https://gist.github.com/ikidd/4b104a6b1 … b953e38523
Error shows up at about line 1270
Dell 5575 laptop with Ryzen 5 2500U cpu, installed on NVME drive.
Offline
I would suggest ensuring you have backups. Installing linux-lts as an alternative to linux to avoid having to keep downgrading.
Testing linux 4.20 booting to multi-user.target instead of graphical.target as the issue seems to start shortly after SDDM has started X.
Offline
Starting in multiuser gets me to a prompt. I pulled up the logs again and see it throwing errors over the Vega Mobile gpu and the PCI Bridge when I investigate the vendor IDs via lspci -nn
And yes, starting SDDM piles it up. Tried Lightdm with gtk greeter and it also piles up very shortly after loading dm with AMDGPU errors.
https://gist.github.com/ikidd/692dea4c6 … 322d066405
Line 978 of journal shows error on boot via vendor ID, and I've included the outputs of lspci grepping for them.
Offline
Tried most DM but GDM, other than that I'm in the same boat as you with 4.20.
The same piles up.
Watching closely.
Offline
What's your hardware, sammiev? I'm seeing other threads elsewhere that indicate it's an integrated AMD gpu issue.
Offline
If you blacklist the amdgpu module on the kernel command line leaving the system with probably just a vesa console are the errors still produced?
Offline
What's your hardware, sammiev? I'm seeing other threads elsewhere that indicate it's an integrated AMD gpu issue.
System: Host: arch Kernel: 4.14.90-1-lts x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Xfce 4.12.4 Distro: Arch Linux
Machine: Type: Laptop System: TOSHIBA product: Satellite L650 v: PSK1E1-1234567 serial: <root required>
Mobo: TOSHIBA model: Portable PC serial: <root required> BIOS: INSYDE v: 2.40 date: 11/09/2011
Battery: ID-1: BAT0 charge: 35.8 Wh condition: 35.8/47.5 Wh (75%) model: PA381 status: Unknown
CPU: Topology: Dual Core model: Intel Core i5 M 480 bits: 64 type: MT MCP arch: Nehalem rev: 5 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21331
Speed: 1467 MHz min/max: 1199/2667 MHz Core speeds (MHz): 1: 1467 2: 1466 3: 1467 4: 1466
Graphics: Device-1: Intel Core Processor Integrated Graphics vendor: Toshiba America Info Systems driver: i915 v: kernel
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.3 driver: modesetting unloaded: vesa resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 18.3.1 direct render: Yes
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Toshiba America Info Systems
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k4.14.90-1-lts
Network: Device-1: Qualcomm Atheros AR8152 v1.1 Fast Ethernet vendor: Toshiba America Info Systems driver: atl1c
v: 1.0.1.1-NAPI port: 3000 bus ID: 01:00.0
IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: 00:26:6c:98:5a:36
Device-2: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce v: kernel port: 2000 bus ID: 02:00.0
IF: wlp2s0 state: down mac: ea:d4:3a:6c:de:ca
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives: Local Storage: total: 232.89 GiB used: 7.56 GiB (3.2%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB
Partition: ID-1: / size: 71.77 GiB used: 7.47 GiB (10.4%) fs: ext4 dev: /dev/sda2
ID-2: /boot size: 1.91 GiB used: 96.0 MiB (4.9%) fs: ext4 dev: /dev/sda1
ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6
Sensors: System Temperatures: cpu: 54.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 150 Uptime: 47m Memory: 7.60 GiB used: 1.20 GiB (15.8%) Init: systemd Compilers: gcc: 8.2.1 Shell: bash
v: 4.4.23 inxi: 3.0.29
Offline
@ikidd, since the errors seem to occur for X11, do you use https://www.archlinux.org/packages/extr … eo-amdgpu/ and what if you toggle between it and the modesetting ddx driver? (Ie. install or uninstall it)
Offline
If you blacklist the amdgpu module on the kernel command line leaving the system with probably just a vesa console are the errors still produced?
@loqs: Indeed, that's what happens when adding modprobe.blacklist=amdgpu
Defaults to kms and doesn't log the hardware errors. Doesn't do anything useful but I can get to a TTY.
I'm guessing this is bug-reporting territory at this point?
Offline
@seth: installing or uninstalling xf86-video-amdgpu has no effect, still hard hang unless I blacklist amdgpu
Offline
Yes if you can not find an already opened report here file it under product DRI component DRM/AMDgpu.
Offline
Will do, thanks.
Looks like https://bugzilla.freedesktop.org/show_bug.cgi?id=108992, not sure how I missed this one, as I had looked, but maybe I hadn't narrowed down that far.
iommu=soft seems to allow boot on 4.20 but like the other reporter, I'm not exactly sure what that impacts. I don't do any VFIO or VM on this system.
Last edited by ikidd (2019-01-01 20:24:17)
Offline