At Tue, 1 Jul 2003 06:00:35 -0700 (PDT), Prince John wrote: > > >Has anybody face this problem? > > > Any ideas to resolve it? > > > > this kind of problem has appeared when different gcc > > versions were > > used for the kernel and the ALSA modules. not sure > > whether it's your > > case. the problem #2 also seems like the behavior > > happening with the > > gcc-mismatch above. > > > > > > Takashi > ------------- > Hi Takashi, > Thank you verymuch for your response. > I'm using sh4-linux-gcc ver 3.0.4 for both Kernel and > ALSA driver, lib and utils. I'm using ALSA driver - > Ver. 0.9.1. Will it help if I change to the latest > version?
hmm, so that's not the case. about upgrading, yes, it's better to use the latest version. it will also make it easier to integrate your code into our tree. > > can SH4 trace oops via ksymoops? > > Sorry, I didn't get it. Could u please clarify it? on intel (and many other) architectures, we can trace the stack printed to the kernel message via ksymoops program when a kernel oops happens. i have no idea about SH4 development environment, but if you have such one, this will help greatly to spot the buggy point out. Takashi ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
