Re: Oops still present in lastest CVS/nm256

[Takashi Iwai <tiwai@suse.de>]

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/