public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org, tiwai@suse.de
Subject: Re: 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA
Date: Mon, 20 Apr 2009 21:28:59 +0200	[thread overview]
Message-ID: <200904202129.00316.rjw@sisk.pl> (raw)
In-Reply-To: <20090420184024.GA10155@dose.home.local>

On Monday 20 April 2009, Tino Keitel wrote:
> Hi,
> 
> since 2.6.29 and also with 2.6.29.1 the left audio channel of the
> digital output of my Mac mini Core 2 Duo is noisy.  This didn't happen
> with 2.6.28.  Unloading snd-hda-intel and reloading it does fix the
> noisy sound.
> 
> This happened with some older versions of the Linux kernel (with an
> older Mac mini Core Duo, I don't remeber which kernel version), but got
> fixed at some point.  Now it happens again with 2.6.29.
> 
> Here is the dmesg output for the sound hardware:
> 
> HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
> HDA Intel 0000:00:1b.0: setting latency timer to 64
> hda_codec: STAC922x, Apple subsys_id=100
> input: HDA Intel Line In at Ext Left Jack as /class/input/input18
> input: HDA Intel Mic at Ext Left Jack as /class/input/input19
> input: HDA Intel HP Out at Ext Left Jack as /class/input/input20
> 
> Any hints what I could try to fix this, maybe some commit that I should
> try to revert?

Well, no.

Still, you might try the current Linus' tree.

Best,
Rafael

  reply	other threads:[~2009-04-20 19:30 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 [this message]
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
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=200904202129.00316.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tino.keitel@tikei.de \
    --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