The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc5 apm suspend failure--ALSA patch?
Date: Mon, 24 Oct 2005 17:38:00 +0200	[thread overview]
Message-ID: <s5hoe5f9b8n.wl%tiwai@suse.de> (raw)
In-Reply-To: <20051024153526.GH9154@fieldses.org>

At Mon, 24 Oct 2005 11:35:26 -0400,
J. Bruce Fields wrote:
> 
> On Mon, Oct 24, 2005 at 11:55:58AM +0200, Takashi Iwai wrote:
> > At Sun, 23 Oct 2005 14:42:02 -0400,
> > J. Bruce Fields wrote:
> > > 
> > > When I upgraded my laptop (Thinkpad X31) from 2.6.14-rc1 to 2.6.14-rc5 I
> > > found apm suspend had stopped working.  With git bisect I found the
> > > commit 16dab54b8cbac39bd3f639db5d7d0fd8300a6cb0, "[ALSA] Add
> > > snd_card_set_generic_dev() call", and verified that suspend worked again
> > > in 2.6.14-rc5 with that patch reverted.
> > > 
> > > The symptoms are that when I suspend to RAM, the screen blanks but
> > > nothing further happens.  At that point I can ssh into the laptop and
> > > find the appended oops.  Any idea what's going on?--b.
> > 
> > Which driver is affected?
> > I've tested the patch with snd-dummy but not with every ISA driver.
> 
> lspci says
> 
> 0000:00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
> 
> And on boot I see this:
> 
> Oct 22 11:44:45 puzzle kernel: ALSA device list:
> Oct 22 11:44:45 puzzle kernel:   #0: Virtual MIDI Card 1

Ah, that's it.  The patch I sent should fix Oops, then.


Takashi

  reply	other threads:[~2005-10-24 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-23 18:42 2.6.14-rc5 apm suspend failure--ALSA patch? J. Bruce Fields
2005-10-24  9:55 ` Takashi Iwai
2005-10-24 15:35   ` J. Bruce Fields
2005-10-24 15:38     ` Takashi Iwai [this message]
2005-10-24 16:01       ` J. Bruce Fields

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=s5hoe5f9b8n.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=bfields@fieldses.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox