All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: Chris Meadors <twrchris@hereintown.net>,
	Amit Shah <shahamit@gmx.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alsa-devel@lists.sourceforge.net"
	<alsa-devel@lists.sourceforge.net>
Subject: Re: [Alsa-devel] Re: 2.6.0-test1: ALSA problem
Date: Tue, 15 Jul 2003 17:33:14 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307151732280.26334-100000@pnote.perex-int.cz> (raw)
In-Reply-To: <s5h7k6j3jvk.wl@alsa2.suse.de>

On Tue, 15 Jul 2003, Takashi Iwai wrote:

> At 15 Jul 2003 10:57:55 -0400,
> Chris Meadors wrote:
> > 
> > On Tue, 2003-07-15 at 01:18, Amit Shah wrote:
> > > I don't know what the problem is exactly, since alsa shows it found one 
> > > card... I'm using debian woody with alsa-base installed. Even if alsa shows 
> > > one card detected, it doesn't play. (It doesn't recognize /dev/dsp?)
> > > 
> > > 
> > > Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 
> > > 2003 UTC).
> > > kobject_register failed for Ensoniq AudioPCI (-17)
> > > Call Trace:
> > >  [<c01f6b8a>] kobject_register+0x32/0x48
> > >  [<c0248a1b>] bus_add_driver+0x3f/0xa0
> > >  [<c0248e0a>] driver_register+0x36/0x3c
> > >  [<c01fb236>] pci_register_driver+0x6a/0x90
> > >  [<c04117ba>] alsa_card_ens137x_init+0xe/0x3c
> > >  [<c03f86f5>] do_initcalls+0x39/0x94
> > >  [<c03f876c>] do_basic_setup+0x1c/0x20
> > >  [<c010509b>] init+0x33/0x188
> > >  [<c0105068>] init+0x0/0x188
> > >  [<c0107145>] kernel_thread_helper+0x5/0xc
> > > 
> > > ALSA device list:
> > >   #0: Intel 82801BA-ICH2 at 0xe800, irq 17
> > 
> > I see exactly the same thing with my Sound Blaster 16 PCI.
> 
> 
> hmm, something gets wrong when no irq is generated and the pcm stream
> is forced to be closed.  i'll check this.
> 
> are you using a UP kernel or an SMP kernel?

It might be related that we have not initialized the owner field from the 
pci_dev structure for 2.6 kernels. I will fix that soon.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


WARNING: multiple messages have this Message-ID (diff)
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: Chris Meadors <twrchris@hereintown.net>,
	Amit Shah <shahamit@gmx.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"alsa-devel@lists.sourceforge.net"
	<alsa-devel@lists.sourceforge.net>
Subject: Re: Re: 2.6.0-test1: ALSA problem
Date: Tue, 15 Jul 2003 17:33:14 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0307151732280.26334-100000@pnote.perex-int.cz> (raw)
In-Reply-To: <s5h7k6j3jvk.wl@alsa2.suse.de>

On Tue, 15 Jul 2003, Takashi Iwai wrote:

> At 15 Jul 2003 10:57:55 -0400,
> Chris Meadors wrote:
> > 
> > On Tue, 2003-07-15 at 01:18, Amit Shah wrote:
> > > I don't know what the problem is exactly, since alsa shows it found one 
> > > card... I'm using debian woody with alsa-base installed. Even if alsa shows 
> > > one card detected, it doesn't play. (It doesn't recognize /dev/dsp?)
> > > 
> > > 
> > > Advanced Linux Sound Architecture Driver Version 0.9.4 (Mon Jun 09 12:01:18 
> > > 2003 UTC).
> > > kobject_register failed for Ensoniq AudioPCI (-17)
> > > Call Trace:
> > >  [<c01f6b8a>] kobject_register+0x32/0x48
> > >  [<c0248a1b>] bus_add_driver+0x3f/0xa0
> > >  [<c0248e0a>] driver_register+0x36/0x3c
> > >  [<c01fb236>] pci_register_driver+0x6a/0x90
> > >  [<c04117ba>] alsa_card_ens137x_init+0xe/0x3c
> > >  [<c03f86f5>] do_initcalls+0x39/0x94
> > >  [<c03f876c>] do_basic_setup+0x1c/0x20
> > >  [<c010509b>] init+0x33/0x188
> > >  [<c0105068>] init+0x0/0x188
> > >  [<c0107145>] kernel_thread_helper+0x5/0xc
> > > 
> > > ALSA device list:
> > >   #0: Intel 82801BA-ICH2 at 0xe800, irq 17
> > 
> > I see exactly the same thing with my Sound Blaster 16 PCI.
> 
> 
> hmm, something gets wrong when no irq is generated and the pcm stream
> is forced to be closed.  i'll check this.
> 
> are you using a UP kernel or an SMP kernel?

It might be related that we have not initialized the owner field from the 
pci_dev structure for 2.6 kernels. I will fix that soon.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs



-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1

  parent reply	other threads:[~2003-07-15 15:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  5:18 2.6.0-test1: ALSA problem Amit Shah
2003-07-15 14:57 ` Chris Meadors
2003-07-15 15:11   ` Takashi Iwai
2003-07-15 15:11     ` Takashi Iwai
2003-07-15 15:17     ` Chris Meadors
2003-07-15 15:33     ` Jaroslav Kysela [this message]
2003-07-15 15:33       ` Jaroslav Kysela
2003-07-15 15:37       ` [Alsa-devel] " Takashi Iwai
2003-07-15 16:12         ` Takashi Iwai
2003-07-16  4:50     ` Amit Shah

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=Pine.LNX.4.44.0307151732280.26334-100000@pnote.perex-int.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shahamit@gmx.net \
    --cc=tiwai@suse.de \
    --cc=twrchris@hereintown.net \
    /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.