public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Lz <elezeta@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Problems with sound on latest kernels.
Date: Fri, 17 Feb 2006 01:17:01 -0500	[thread overview]
Message-ID: <20060217061701.GA17208@neo.rr.com> (raw)
In-Reply-To: <cde01ae70602150542m1b57aa83l62508927276241b@mail.gmail.com>

On Wed, Feb 15, 2006 at 02:42:05PM +0100, Lz wrote:
> On 2/15/06, Andrew Morton <akpm@osdl.org> wrote:
> >
> > Poor guy - that's rocket science.  It looks like it's due to breakage in
> > the pnp code anwyay.
> 
> Yeah, it seemed that to me, alsa wasn't even loaded at that time.

This patch may solve your problem.  Could you send a new dmesg output with it
applied?

Thanks,
Adam

--- a/drivers/pnp/card.c        2006-01-02 22:21:10.000000000 -0500
+++ b/drivers/pnp/card.c        2006-02-17 00:45:37.123525896 -0500
@@ -302,13 +302,11 @@
        down_write(&dev->dev.bus->subsys.rwsem);
        dev->card_link = clink;
        dev->dev.driver = &drv->link.driver;
-       if (drv->link.driver.probe) {
-               if (drv->link.driver.probe(&dev->dev)) {
-                       dev->dev.driver = NULL;
-                       dev->card_link = NULL;
-                       up_write(&dev->dev.bus->subsys.rwsem);
-                       return NULL;
-               }
+       if (pnp_bus_type.probe(&dev->dev)) {
+               dev->dev.driver = NULL;
+               dev->card_link = NULL;
+               up_write(&dev->dev.bus->subsys.rwsem);
+               return NULL;
        }
        device_bind_driver(&dev->dev);
        up_write(&dev->dev.bus->subsys.rwsem);

  reply	other threads:[~2006-02-17  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-14 13:58 Problems with sound on latest kernels Lz
2006-02-14 16:30 ` Lee Revell
2006-02-15  7:22   ` Andrew Morton
2006-02-15 13:42     ` Lz
2006-02-17  6:17       ` Adam Belay [this message]
2006-02-17 16:31         ` Lz
2006-02-17 19:56           ` Adam Belay
2006-02-17 20:17             ` Lz
2006-02-15 18:21     ` Lee Revell

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=20060217061701.GA17208@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=akpm@osdl.org \
    --cc=elezeta@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox