watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:0:7893]

[Nicholas Harvey]

Not sure what triggered this.

ProblemType: KernelOops
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-13-generic 5.3.0-13.14
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nharvey 1671 F.... pulseaudio
Date: Sat Sep 28 19:43:38 2019
Failure: oops
InstallationDate: Installed on 2019-09-23 (5 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=8871f847-02c3-4658-891c-d58f0eafa0d5 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 5: phy3: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:0:7893]
UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago)
dmi.bios.date: 05/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.12.0
dmi.board.name: 0TPN17
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 082A
dmi.sys.vendor: Dell Inc.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[robinharvey (harvey-robin)]

Just had this on my router system, the hostapd WIFI and ethernet also failed at the same time, but the strongswan VPN seemed to keep chatting throughout. Attached logs from the beginning of the incident until a manual system reset.