All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glauber Costa <gcosta@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Glauber Costa <gcosta@redhat.com>
Subject: Re: 2.6.26-rc1 sound regression
Date: Wed, 14 May 2008 14:41:01 -0300	[thread overview]
Message-ID: <482B242D.7040801@redhat.com> (raw)
In-Reply-To: <20080514130742.GA28872@erig.dyndns.org>

Wolfgang Erig wrote:
> Hi,
> 
> my sound stops working with 2.6.26-rc1,
> alsaplayer makes intermitted random noise.
> Bisecting worked fine and the last steps were:
> 
> $ git bisect good
> Bisecting: 9 revisions left to test after this
> [71848d687e2a477cb7c68a854d8fdeaa5dff0ffc] x86: remove virt_to_bus in pci-dma_64.c
> 
> $ git bisect good
> Bisecting: 4 revisions left to test after this
> [8f19ca1341a6d89bd96e2e69e6e10f46d3258089] x86: unify gfp masks
> 
> $ git bisect bad
> Bisecting: 2 revisions left to test after this
> [45a07e774950ef479f8996c0e2c5550dd6440453] x86: use a fallback dev for i386
> 
> $ git bisect good
> Bisecting: 1 revisions left to test after this
> [5fa78ca75d8e67063948a01b51594a0904af5710] x86: retry allocation if failed
> 
> The last kernel is bad.
> Checked 2.6.26-rc2 too which is bad.
> 
> This is a 10+x year old laptop, but it does useful work for me.
> The driver is snd_sb8.
> 
> Wolfgang
This is probably the same issue we had at http://lkml.org/lkml/2008/5/8/522

Can you please confirm we're talking about the same issue, i.e. , if the 
posted fix also fix your issue?

thanks.

  reply	other threads:[~2008-05-14 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 13:07 2.6.26-rc1 sound regression Wolfgang Erig
2008-05-14 17:41 ` Glauber Costa [this message]
2008-05-14 20:40 ` Rene Herman
2008-05-15 16:05   ` Wolfgang Erig

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=482B242D.7040801@redhat.com \
    --to=gcosta@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.