From: Takashi Iwai <tiwai@suse.de>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next - strange audio bug
Date: Sat, 04 Apr 2015 14:37:21 +0200 [thread overview]
Message-ID: <s5hpp7kxe66.wl-tiwai@suse.de> (raw)
In-Reply-To: <57781.1428021275@turing-police.cc.vt.edu>
At Thu, 02 Apr 2015 20:34:35 -0400,
Valdis Kletnieks wrote:
>
> Next-20150310 works OK, next-20150324 has the bug.
>
> Dell Latitude E6530 laptop, lspci tells me:
>
> 01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1)
> Subsystem: Dell Device 0535
> ...
> Kernel driver in use: snd_hda_intel
>
> Symptoms: Audio works perfectly at boot, and for some amount
> of time after. But somewhere around 6-8 hours of uptime, it gets
> into a strange state where I'll get no audio... and then it will
> cut in for all of 2 seconds or so (fairly consistent, that part),
> and then cut back out for anywhere from 10 seconds to a minute,
> then another 2 seconds of sound.. lather rinse repeat.
>
> Before I start the thankless task of bisecting this (which means I'll
> be able to do only 1, *maybe* 2 steps a day), does this ring any bells?
Try for-next branch of sound git tree
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
Now I merged fixes that might be relevant with the runtime PM on some
codecs, so it might work better.
In anyway, please give alsa-info.sh outputs at good and bad-working
states.
thanks,
Takashi
prev parent reply other threads:[~2015-04-04 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 0:34 linux-next - strange audio bug Valdis Kletnieks
2015-04-03 0:44 ` Hui Wang
2015-04-03 2:21 ` [alsa-devel] " Valdis.Kletnieks
2015-04-04 12:37 ` Takashi Iwai [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=s5hpp7kxe66.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--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