From: Shayne O'Connor <forums@machinehasnoagenda.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Oops with emu10k1 multichannel device - possible bug
Date: Sun, 20 Feb 2005 08:51:30 +1100 [thread overview]
Message-ID: <4217B4E2.5080301@machinehasnoagenda.com> (raw)
In-Reply-To: <1108841487.10705.12.camel@krustophenia.net>
Lee Revell wrote:
>On Fri, 2005-02-18 at 17:15 -0500, Lee Revell wrote:
>
>
>>Testing ALSA CVS on a new machine using the emu10k1 multichannel device
>>produced this Oops. I am investigating. Although the multichannel
>>patch was very well tested, until further notice the device should be
>>considered buggy.
>>
>>
>
>I don't think this is anything to worry about. It only happened the
>first time I loaded the new ALSA modules, I think I had unloaded ALSA
>1.0.5 previously. I have been unable to reproduce it despite running
>JACK at very low latencies and doing "dbench 64" for hours.
>
>
sorry - just noticed this ... i had the exact same problem when loading
the alsa modules - but it was only then, no problems since.
shayne
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-19 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 22:15 Oops with emu10k1 multichannel device - possible bug Lee Revell
2005-02-19 19:31 ` Lee Revell
2005-02-19 21:51 ` Shayne O'Connor [this message]
2005-02-19 21:45 ` 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=4217B4E2.5080301@machinehasnoagenda.com \
--to=forums@machinehasnoagenda.com \
--cc=alsa-devel@lists.sourceforge.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.