From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: oops with current ALSA CVS + gcc3 Date: Wed, 05 Mar 2003 14:10:05 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200303051242.h25Cgi401244@linuxaudiosystems.com> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <200303051242.h25Cgi401244@linuxaudiosystems.com> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Paul Davis Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Wed, 5 Mar 2003 07:42:44 -0500, Paul Davis wrote: > > is anybody else using gcc 3.2.2 to compile their kernel and ALSA CVS? > > i switched in the last couple of days, and have found: > > * just trying to load wavefront driver causes lockup without oops message. > * use of trident driver causes oops whenever used. > > i haven't tried the hammerfall/hdsp drivers yet, though they load just > fine and the /proc card-specific files work just fine. > > the oops trace from using the trident points to problems with process > wakeup after an interrupt, and doesn't seem to involve ALSA specific > code (the call trace points to a set of functions that start at > synchronize_irq() and end with wake_up_process(). > > i am not sure if this is an ALSA CVS issue, or if its to do with my > use of gcc 3.2.2. i don't have gcc2.95 around anymore, and am > reluctant to do so, but if i have to ... did you compile the kernel itself with the same gcc? the combination of gcc-2.x and gcc-3.x on the kernel space will likely cause oops. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf