Re: How to report kernel panic in 4.4.x

Matthias B.
2018-08-24T14:09:52Z

The following is the dmesg output from my working 4.4.147 around the
time when the newer kernel panics.

0.425380] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 0.425932] Bluetooth: HIDP socket layer initialized
[ 0.426617] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x19
[ 0.427203] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x19
[ 0.427772] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x19
[ 0.428688] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x19
[ 0.429221] microcode: CPU4 sig=0x306c3, pf=0x2, revision=0x19
[ 0.429744] microcode: CPU5 sig=0x306c3, pf=0x2, revision=0x19
[ 0.430255] microcode: CPU6 sig=0x306c3, pf=0x2, revision=0x19
[ 0.430761] microcode: CPU7 sig=0x306c3, pf=0x2, revision=0x19
[ 0.431271] microcode: Microcode Update Driver: v2.01
<tigran@aivazian.fsnet.co.uk>, Peter Oruba [ 0.431815] AVX2
version of gcm_enc/dec engaged. [ 0.432347] AES CTR mode by8
optimization enabled [ 0.433358] registered taskstats version 1
[ 0.434086] Btrfs loaded
[ 0.434991] rtc_cmos 00:02: setting system clock to 2018-08-24
13:35:45 UTC (1535117745) [ 0.435586] ALSA device list:
[ 0.436074] No soundcards found.

All of the times visible on screen for the panicking kernel are in this
gap.

[ 0.595677] snd_hda_intel 0000:01:00.1: Too many HDMI devices
[ 0.596251] snd_hda_intel 0000:01:00.1: Consider building the kernel
with CONFIG_SND_DYNAMIC_MINORS=y [ 0.596839] snd_hda_intel
0000:01:00.1: Too many HDMI devices [ 0.597412] snd_hda_intel
0000:01:00.1: Consider building the kernel with
CONFIG_SND_DYNAMIC_MINORS=y [ 0.612466] snd_hda_intel
0000:01:00.1: control 3:0:0:ELD:0 is already present [ 0.613100]
snd_hda_codec_hdmi: probe of hdaudioC0D0 failed with error -16

--
If God hadn't wanted me to be paranoid,
He wouldn't have given me such a vivid imagination.