LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Hazelton <dhazelton@enter.net>
Cc: Harald Dunkel <harald.dunkel@t-online.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Date: Mon, 14 Jan 2008 12:04:20 +0100	[thread overview]
Message-ID: <s5h8x2sllcb.wl%tiwai@suse.de> (raw)
In-Reply-To: <200801121211.22280.dhazelton@enter.net>

At Sat, 12 Jan 2008 12:11:20 -0500,
Daniel Hazelton wrote:
> 
> On Saturday 12 January 2008 04:41:21 Harald Dunkel wrote:
> > Takashi Iwai wrote:
> > > At Thu, 10 Jan 2008 23:02:53 +0100,
> > >
> > > Harald Dunkel wrote:
> > >> Takashi Iwai wrote:
> > >>> Hm...  Just to be sure, try the patch below.  It's a clean up patch
> > >>> that I'd like to apply later.
> > >>
> > >> Sorry, no sound.
> > >
> > > OK, but I'd like to know whether this makes no regression to rc6.
> > > Could you check?
> > >
> > > Also, what exactly did you test?  "No sound" means that no sound from
> > > the headphone / line-out or from the speaker?
> > >
> > > One interesting test would be to increase the value of udelay() in the
> > > reverted patch.  What happens if it's set to 500?
> >
> > There is no udelay() in the reverted patch. If I replace "udelay(10)"
> > by "udelay(500)" in the original rc7, then there is still no sound.
> >
> > This is like fishing in the dark. We've got a working version. Why not
> > keep it?
> >
> >
> > Regards
> >
> > Harri
> 
> Could this have anything to do with the following messages I've seen when 
> trying -rc7 ?
> 
> [    7.760269] pnpacpi: exceeded the max number of mem resources: 12

Judging from Harald's report, it looks like a different problem.
The buggy patch (regarding HDA-intel) was, at least, already reverted
on Linus git tree.  Could you give it a try?


Takashi

  reply	other threads:[~2008-01-14 11:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 19:53 Harald Dunkel
2008-01-08  7:24 ` Takashi Iwai
2008-01-08 10:10   ` Ingo Molnar
2008-01-08 17:01   ` Harald Dunkel
2008-01-08 17:43     ` Takashi Iwai
2008-01-09  6:03       ` Harald Dunkel
2008-01-09  7:31         ` Takashi Iwai
2008-01-09 20:10           ` Harald Dunkel
2008-01-10 13:30             ` Takashi Iwai
2008-01-10 22:02               ` Harald Dunkel
2008-01-11  6:49                 ` Takashi Iwai
2008-01-11 21:55                   ` Harald Dunkel
2008-01-13 11:17                     ` Takashi Iwai
2008-01-14 20:46                       ` Harald Dunkel
2008-01-15 10:07                         ` Takashi Iwai
2008-01-12  9:41                   ` Harald Dunkel
2008-01-12 17:11                     ` Daniel Hazelton
2008-01-14 11:04                       ` Takashi Iwai [this message]
2008-01-14 21:03                         ` Daniel Hazelton
2008-01-15 10:08                           ` Takashi Iwai
2008-01-15 19:00                             ` Daniel Hazelton
2008-01-13 11:26                     ` Takashi Iwai
2008-01-16  6:53       ` Harald Dunkel

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=s5h8x2sllcb.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=dhazelton@enter.net \
    --cc=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.24-rc7, intel audio: alsa doesn'\''t say a beep' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).