mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Alexander Kappner" <agk@godking.net>
Cc: <Jim.Qu@amd.com>, <bhelgaas@google.com>,
	<guneshwor.o.singh@intel.com>, <perex@perex.cz>,
	<hdegoede@redhat.com>, <lukas@wunner.de>,
	<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [snd_hda_intel] snd_hda_intel causes high CPU lockup and system instability if mic disabled in BIOS on Lenovo P50
Date: Mon, 26 Nov 2018 09:24:46 +0100	[thread overview]
Message-ID: <s5hpnus6yb5.wl-tiwai@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1811251505140.20766@REDDOT>

On Mon, 26 Nov 2018 00:17:15 +0100,
Alexander Kappner wrote:
> 
> My Lenovo P50 laptop has a BIOS option to disable the microphone. When
> this option gets chosen, the snd_hda_intel driver causes high CPU load
> on a single kworker thread, spinning on "process_unsol_events", and
> system
> instability. This behavior occurs from the time that the snd_hda_intel
> module is loaded, irrespective of whether anything is attempting to access
> the mic. The sound output still works.
> 
> When in this state, the module cannot be removed cleanly; attempting to
> remove it (even without rmmod -f) triggers an oops.
> 
> I have attached two exemplary dmesg outputs. Strangely enough, the exact
> location of the oops varies, but further up the call chain, I always see
> process_unsol_events.
> 
> When the mic is not disabled in the BIOS, the module works stable,
> regardless whether or not the mic is muted in ALSA.
> 
> I wasn't able to pinpoint the root cause. Any pointers on where to
> start? Much appreciated.

Could you load snd-hda-intel driver with probe_only=1 option, and give
alsa-info.sh output (run it with --no-upload option)?  This should
leave only the codec probing without configuring, so we can see the
codec widget contents and check the emulator.


thanks,

Takashi

  reply	other threads:[~2018-11-26  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-25 23:17 Alexander Kappner
2018-11-26  8:24 ` Takashi Iwai [this message]
2018-11-27  5:34   ` Alexander Kappner
2018-11-27 13:21     ` Takashi Iwai
2018-12-01 19:33       ` Alexander Kappner
2018-12-05 14:08         ` Takashi Iwai
2019-01-07  2:18           ` Alexander Kappner

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=s5hpnus6yb5.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Jim.Qu@amd.com \
    --cc=agk@godking.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=guneshwor.o.singh@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=perex@perex.cz \
    /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

all inboxes | Powered by JetHome®