From: Tino Keitel <tino.keitel@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA
Date: Tue, 28 Apr 2009 02:23:09 +0200 [thread overview]
Message-ID: <20090428002309.GA29572@x61> (raw)
In-Reply-To: <s5hskjy5d2t.wl%tiwai@suse.de>
On Fri, Apr 24, 2009 at 16:41:14 +0200, Takashi Iwai wrote:
> At Fri, 24 Apr 2009 16:21:13 +0200,
> Tino Keitel wrote:
> >
> > On Fri, Apr 24, 2009 at 16:01:40 +0200, Takashi Iwai wrote:
> >
> > [...]
> >
> > > The codec communication looks a bit unstable on this device...
> > > Does this still happen on the latest 2.6.30 version?
> >
> > Yes, at least with 2.6.30-rc3. I reloaded snd-hda-intel a few times,
> > and at some point /etc/init.d/alsa-utils start complained, I guess
> > because some index numbers in the mixer changed.
>
> And this happens because the codec doesn't respond properly any more.
> So, something triggers to screw up the communication with the codec.
> I have no idea right now. Possibly you can bisect the changes against
> sound/pci/hda/patch_sigmatel.c...
The problem is that I don't have a reliable way to trigger this bug. It
just happens sometimes.
I just saw another, major problem: line in doesn't work anymore with
2.6.29 and also 2.6.30-rc3 (no usable input level). It works with
2.6.27.20.
So it seems that all newer kernels are pretty broken on this hardware
regarding sound.
Regards,
Tino
next prev parent reply other threads:[~2009-04-28 0:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 18:40 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA Tino Keitel
2009-04-20 19:28 ` Rafael J. Wysocki
2009-04-20 19:41 ` Takashi Iwai
2009-04-20 19:46 ` Tino Keitel
2009-04-21 5:24 ` Takashi Iwai
2009-04-21 7:32 ` Tino Keitel
2009-04-21 7:39 ` Takashi Iwai
2009-04-21 18:39 ` Tino Keitel
2009-04-24 14:01 ` Takashi Iwai
2009-04-24 14:21 ` Tino Keitel
2009-04-24 14:41 ` Takashi Iwai
2009-04-28 0:23 ` Tino Keitel [this message]
2009-04-28 5:24 ` Takashi Iwai
2009-04-28 6:30 ` Tino Keitel
2009-05-06 22:27 ` Tino Keitel
2009-05-07 7:23 ` Tino Keitel
2009-05-07 7:40 ` Justin P. Mattock
2009-05-07 10:07 ` Takashi Iwai
2009-05-07 10:45 ` Takashi Iwai
2009-05-07 11:54 ` Nigel Cunningham
2009-05-07 12:16 ` Takashi Iwai
2009-05-07 20:42 ` Nigel Cunningham
2009-05-07 20:56 ` Justin P. Mattock
2009-05-07 12:59 ` Tino Keitel
2009-05-08 6:03 ` Takashi Iwai
2009-05-07 20:42 ` Tino Keitel
2009-05-07 20:53 ` Tino Keitel
2009-05-08 6:06 ` Takashi Iwai
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=20090428002309.GA29572@x61 \
--to=tino.keitel@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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