From: Michael Collard <quadfour@iinet.net.au>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: snd-ioctl32 and hard lockups
Date: Thu, 09 Dec 2004 08:51:33 +0800 [thread overview]
Message-ID: <1102553493.1459.0.camel@natalie> (raw)
In-Reply-To: <s5hy8g8akif.wl@alsa2.suse.de>
On Wed, 2004-12-08 at 16:15 +0100, Takashi Iwai wrote:
> At Wed, 08 Dec 2004 22:16:45 +0800,
> Michael Collard wrote:
> >
> > After modprobing the snd-ioctl32 module from Alsa 1.0.7, then next
> > attempt to play _any_ audio causes the machine to hard lock, not even
> > the SysRq commands do anything. I've had no luck with a response form
> > alsa-users or #alsa on freenode, hence emailing the devel list.
> >
> > 1.0.7 compiled, not from kernel.
> > Custom x86_64 2.6.8.1 kernel
> > Vibra16 card (es1371 driver)
> >
> > Alsa sound works quite OK in every other respect. Any hints on how to
> > diagnose/fix the problem appreciated.
>
> Try the CVS version. The ioctl32 wrapper was rewritten in large
> parts.
Thank you, the CVS version functions correctly :)
Wish I'd done that before.
Regards
Michael Collard
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-12-09 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 14:16 snd-ioctl32 and hard lockups Michael Collard
2004-12-08 15:15 ` Takashi Iwai
2004-12-09 0:51 ` Michael Collard [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=1102553493.1459.0.camel@natalie \
--to=quadfour@iinet.net.au \
--cc=alsa-devel@lists.sourceforge.net \
--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