do_IRQ: 1.55 No irq handler for vector

[Clinton H]

1) Ubuntu 19.10
2) system
3) no error.
4) Error in log app.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: htpc 9157 F.... pulseaudio
 /dev/snd/controlC1: htpc 9157 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-10-28 (48 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IwConfig:
 lxcbr0 no wireless extensions.

 lo no wireless extensions.

 enp3s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-23-generic N/A
 linux-backports-modules-5.3.0-23-generic N/A
 linux-firmware 1.183.2
RfKill:

Tags: wayland-session eoan
Uname: Linux 5.3.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/13/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6b
dmi.board.name: GA-MA780G-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA780G-UD3H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1856433

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Clinton H (49studebaker)]

apport information

[Blaze (blaze)]

As you can see in the dmesg log it happens when the kernel is initializing the second CPU core.
I believe this started after the AMD microcode update against Spectre/Meltdown mitigations.

Should be reported also to https://bugzilla.kernel.org/

[Timo Witte (spacefish)]

AGESA V2 1.0.0.2 introduced this issue.

[new4u (new4u)]

Affects me too,

Ryzen 7 3700X,
AMD AGESA Combo-AM4 v2 1.0.0.2 + SMU 46.61.

I attached a log where can be seen what is happening before and after the error.

Thank you for looking into this matter.