From: Giuliano Pochini <pochini@shiny.it>
To: "F. Heitkamp" <heitkamp@ameritech.net>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
linux-audio-user@lists.linuxaudio.org,
Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, alsa-user@lists.sourceforge.net
Subject: Re: [Alsa-user] Crash 2.6.32.x, Echo 3G, Alsa, SCSI
Date: Fri, 18 Jun 2010 13:55:09 +0200 [thread overview]
Message-ID: <20100618135509.08a51fe8@Jay> (raw)
In-Reply-To: <4C1A10DA.4080304@ameritech.net>
On Thu, 17 Jun 2010 08:11:06 -0400
"F. Heitkamp" <heitkamp@ameritech.net> wrote:
> >> My goal is to be able to plug in a MIDI keyboard, or USB guitar
> >> interface and play along with songs etc.
> >>
> >> I plugged in a MIDI keyboard, "/proc/asound/cards" showed the keyboard
> >> was recognized. The keyboard has a USB and MIDI interface.
> >> I am not sure if they both work at the same time. I had the MIDI cable
> >> plugged into the Gina3G, but I could not tell if the keyboard was
> >> recognized.
> >> I compiled csound5. When I engaged it the system immediately froze and
> >> started spitting out:
> >> [...]
> > Ok, I compiled csound, but I don't know how to use it. How can I reproduce
> > the problem ?
> >
> Sorry I took so long to get back to you.
> It turns out Csound is not related to the problem.
>
> In this case I am only using kernel 2.6.33.5-rt23-amd64, alsa lib 1.0.2,
> but 2.6.34 does it too.
> I bring up firefox. Web pages attempt to play sound. The kernel
> begans doing:
>
> [ 2879.766331] allocate_pipes: ch=1 int=2
> [ 2879.766332] allocate_pipes: channel already open
> [ 2879.766333] allocate_pipes(1) err=-11
> [ 2879.766334] pcm_hw_freed
> [ 2.821190] pcm_analog_out_open cs=0 oc=2 r=44100
> [ 2879.821266] allocate_pipes: ch=1 int=2
> [ 2879.821267] allocate_pipes: channel already open
>
> ,infinitely. The system is unusable at this point and I have to
> Alt-SysRq-k to get back in.
>
> Let me know what other information to provide.
Perhaps is it related with the OSS emulation ? Do you know if the browser
plays the sound itself or if it is using an external program or plugin ?
--
Giuliano.
prev parent reply other threads:[~2010-06-18 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73211.74714.qm@web180714.mail.sp1.yahoo.com>
2010-02-02 15:30 ` Crash 2.6.32.x, Echo 3G, Alsa, SCSI Clemens Ladisch
2010-02-02 16:02 ` [alsa-devel] " Giuliano Pochini
2010-02-03 2:48 ` Frederick V Heitkamp
2010-02-02 22:09 ` [alsa-devel] " Giuliano Pochini
2010-02-03 2:51 ` Frederick V Heitkamp
2010-02-03 2:53 ` [alsa-devel] " Frederick V Heitkamp
2010-05-31 19:05 ` [LAU] " F. Heitkamp
2010-05-31 20:59 ` Giuliano Pochini
2010-06-01 5:37 ` Takashi Iwai
2010-06-01 12:25 ` [LAU] [Alsa-user] [alsa-devel] " F. Heitkamp
2010-06-02 22:08 ` [Alsa-user] " Giuliano Pochini
2010-06-17 12:11 ` [LAU] [Alsa-user] [alsa-devel] " F. Heitkamp
2010-06-18 11:55 ` Giuliano Pochini [this message]
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=20100618135509.08a51fe8@Jay \
--to=pochini@shiny.it \
--cc=alsa-devel@alsa-project.org \
--cc=alsa-user@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=heitkamp@ameritech.net \
--cc=linux-audio-user@lists.linuxaudio.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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).