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:24:44 +0200 [thread overview]
Message-ID: <20180824162444.71390f71@ninja> (raw)
In-Reply-To: <20180824141120.GA31555@kroah.com>
On Fri, 24 Aug 2018 16:11:20 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> > [ 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
>
> Have you tried enabling CONFIG_SND_DYNAMIC_MINORS like the kernel is
> asking you to here? Does that help?
I've just tried and it doesn't help. Note that the above message is from
my working kernel and has a timestamp later than the panic, so if the
timing of the 152 kernel is somewhat similar to the 147, the panic
occurs before that snd_hda_intel code is even reached.
MSB
--
Bad comments reveal the bad programmer.
prev parent reply other threads:[~2018-08-24 14:24 UTC|newest]
Thread overview: 12+ 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 13:43 ` Matthias B.
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 16:19 ` Matthias B.
2018-08-24 19:18 ` Greg KH
2018-08-24 14:09 ` Matthias B.
2018-08-24 14:11 ` Greg KH
2018-08-24 14:24 ` Matthias B. [this message]
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=20180824162444.71390f71@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.