From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Chris Meadors <twrchris@hereintown.net>,
Amit Shah <shahamit@gmx.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Alsa-devel] Re: 2.6.0-test1: ALSA problem
Date: Tue, 15 Jul 2003 18:12:14 +0200 [thread overview]
Message-ID: <s5h65m3ojkx.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hznjf2443.wl@alsa2.suse.de>
At Tue, 15 Jul 2003 17:37:16 +0200,
I wrote:
>
> At Tue, 15 Jul 2003 17:33:14 +0200 (CEST),
> Jaroslav Kysela wrote:
> >
> > 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.
>
> hmm, it might be also different -- i once experienced a similar
> behavior on 2.4 kernel, too. i'll try to reproduce it now...
err, sorry, i mixed up different posts there.
the bug found here is likely the missing entry.
Takashi
next prev parent reply other threads:[~2003-07-15 15:58 UTC|newest]
Thread overview: 8+ 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:17 ` Chris Meadors
2003-07-15 15:33 ` [Alsa-devel] " Jaroslav Kysela
2003-07-15 15:37 ` Takashi Iwai
2003-07-15 16:12 ` Takashi Iwai [this message]
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=s5h65m3ojkx.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shahamit@gmx.net \
--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 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).