All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA
Date: Thu, 07 May 2009 00:40:37 -0700	[thread overview]
Message-ID: <1241682037.1864.4.camel@unix> (raw)
In-Reply-To: <20090507072352.GA6513@mac.home>

On Thu, 2009-05-07 at 09:23 +0200, Tino Keitel wrote:
> On Thu, May 07, 2009 at 00:27:53 +0200, Tino Keitel wrote:
> > On Tue, Apr 28, 2009 at 02:23:09 +0200, Tino Keitel wrote:
> > 
> > [...]
> > 
> > > 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.
> > 
> > FYI: I just tried 2.6.28 and line-in was still broken. So the last
> > working kernel is 2.6.27.
> 
> I tried this:
> 
> git bisect start v2.6.28 v2.6.27 sound/pci/hda/patch_sigmatel.c
> 
> The result is commit 4f1e6bc3646ab50b8181555ab7e6eeab68b8632a.
> 
> I can't use git revert because of conflicts, so I crafted the attached
> patch against 2.6.30-rc4-00288-g413f81e, and now line-in works.
> 
> Regards,
> Tino

It's funny you mention left audio broken
with hda(testing out the imac91.patch,
works good, but as soon as I boot into osx
the left audio speaker sounds blown out)
nice... ehhh...

(probably nothing of the sort, but
you never know)

Justin P. Mattock

WARNING: multiple messages have this Message-ID (diff)
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org
Subject: Re: 2.6.29 regression: left audio channel broken after resume from suspend with Intel HDA
Date: Thu, 07 May 2009 00:40:37 -0700	[thread overview]
Message-ID: <1241682037.1864.4.camel@unix> (raw)
In-Reply-To: <20090507072352.GA6513@mac.home>

On Thu, 2009-05-07 at 09:23 +0200, Tino Keitel wrote:
> On Thu, May 07, 2009 at 00:27:53 +0200, Tino Keitel wrote:
> > On Tue, Apr 28, 2009 at 02:23:09 +0200, Tino Keitel wrote:
> > 
> > [...]
> > 
> > > 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.
> > 
> > FYI: I just tried 2.6.28 and line-in was still broken. So the last
> > working kernel is 2.6.27.
> 
> I tried this:
> 
> git bisect start v2.6.28 v2.6.27 sound/pci/hda/patch_sigmatel.c
> 
> The result is commit 4f1e6bc3646ab50b8181555ab7e6eeab68b8632a.
> 
> I can't use git revert because of conflicts, so I crafted the attached
> patch against 2.6.30-rc4-00288-g413f81e, and now line-in works.
> 
> Regards,
> Tino

It's funny you mention left audio broken
with hda(testing out the imac91.patch,
works good, but as soon as I boot into osx
the left audio speaker sounds blown out)
nice... ehhh...

(probably nothing of the sort, but
you never know)

Justin P. Mattock



  reply	other threads:[~2009-05-07  7:40 UTC|newest]

Thread overview: 39+ 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:41   ` Takashi Iwai
2009-04-20 19:46   ` Tino Keitel
2009-04-21  5:24     ` Takashi Iwai
2009-04-21  5:24       ` Takashi Iwai
2009-04-21  7:32       ` Tino Keitel
2009-04-21  7:39         ` Takashi Iwai
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-24 14:41                   ` Takashi Iwai
2009-04-28  0:23                   ` Tino Keitel
2009-04-28  5:24                     ` Takashi Iwai
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 [this message]
2009-05-07  7:40                           ` Justin P. Mattock
2009-05-07 10:07                         ` Takashi Iwai
2009-05-07 10:07                           ` Takashi Iwai
2009-05-07 10:45                         ` 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 12:16                               ` Takashi Iwai
2009-05-07 20:42                               ` Nigel Cunningham
2009-05-07 20:56                                 ` Justin P. Mattock
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
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=1241682037.1864.4.camel@unix \
    --to=justinmattock@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tino.keitel@gmx.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 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.