FS#49400 - System fails to boot with systemd-journal Tainted error

Attached to Project: Arch Linux
Opened by Jordan Sledge (raedeus) - Thursday, 19 May 2016, 17:04 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 22 May 2016, 15:05 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Both my current running image of arch and a fresh live .iso will not boot.
Laptop system fans spool up to high RPM suggesting severe system load.

Unfortunately, I cannot dump any logs because the system fails to get far enough to do so.

Meaningful output may be the following:

NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [systemd-journal:192]
CPU: 1 PID: 192 Comm: systemd-journal Tainted: G L 4.5.1-1-ARCH

Other live ISO's and linux partitions on local drive work just fine.
I have used this particular persistent arch image on a USB drive for over 1.5yrs now
and this just started a few weeks back. Unfortunately I can't pin-point exactly which
update did it. I attempted to rescue the persistent image with a separate Arch live ISO
but I am getting same results. Both 32bit and 64bit are showing same outcome though the
32bit is printing some more info, particularly a Code: e0 1f a3 ....... which is quite long.


Hardware
Sony SVE 11135CXB/VAIO
BIOS R0140D8 11/14/2012
AMD E-2000 1.70GHz


Steps to reproduce:

Burn live ISO to USB and attempt to boot.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 22 May 2016, 15:05 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#48596 
Comment by Doug Newgard (Scimmia) - Thursday, 19 May 2016, 23:18 GMT
Try the lts kernel, this is likely a kernel bug. You should be able to chroot into your system from one of the other setups mentioned.
Comment by Doug Newgard (Scimmia) - Sunday, 22 May 2016, 13:12 GMT
Ping?

Loading...