From: "Matthias B." <matthias@winterdrache.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to report kernel panic in 4.4.x
Date: Fri, 24 Aug 2018 16:09:47 +0200 [thread overview]
Message-ID: <20180824160947.49387d7b@ninja> (raw)
In-Reply-To: <20180824125950.GA29673@kroah.com>
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.
next prev parent reply other threads:[~2018-08-24 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 12:24 How to report kernel panic in 4.4.x Matthias B.
2018-08-24 12:59 ` Greg KH
2018-08-24 14:09 ` Matthias B. [this message]
2018-08-24 14:11 ` Greg KH
2018-08-24 14:24 ` Matthias B.
[not found] ` <20180824154344.1c53a68c@ninja>
2018-08-24 14:12 ` Greg KH
2018-08-24 14:33 ` Matthias B.
2018-08-24 15:55 ` Greg KH
2018-08-24 16:19 ` Matthias B.
2018-08-24 19:18 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180824160947.49387d7b@ninja \
--to=matthias@winterdrache.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).