From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shayne O'Connor Subject: Re: Oops with emu10k1 multichannel device - possible bug Date: Sun, 20 Feb 2005 08:51:30 +1100 Message-ID: <4217B4E2.5080301@machinehasnoagenda.com> References: <1108764903.5278.3.camel@krustophenia.net> <1108841487.10705.12.camel@krustophenia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit In-Reply-To: <1108841487.10705.12.camel@krustophenia.net> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: alsa-devel List-Id: alsa-devel@alsa-project.org 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