From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Oops still present in lastest CVS/nm256 Date: Tue, 25 Nov 2003 18:57:01 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <16323.37811.445520.249624@ronispc.chem.mcgill.ca> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <16323.37811.445520.249624@ronispc.chem.mcgill.ca> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: david.ronis@mcgill.ca Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Tue, 25 Nov 2003 12:38:59 -0500, David Ronis wrote: > > I've posted this problem before, and the oops reported below seems to > be the same one. > > I just CVS updated and rebuilt in all alsa-* directories. Aplay > sigseg's and I get an oops. The first time I tried lead to a hard > lockup. After rebooting, all I got was the oops. I'm using the nm256 > driver on a Sony Z505S viao notebook with 2.4.22 of the kernel (with > lowlatency and preemptive patches applied). [The usual kernal driver > works fine and I have it configured to build as a module]. what about the kernel without preemptive? i remember this kind of oops, but it happend e.g. when alsa-driver and alsa-kernel versions are not synced, or linux kernel tree doesn't match with the actual one, etc. i don't think it's specific to nm256 driver. Takashi ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/