oops with current ALSA CVS + gcc3

oops with current ALSA CVS + gcc3

[Paul Davis]

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 ...

--p


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: oops with current ALSA CVS + gcc3

[Takashi Iwai]

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

Re: oops with current ALSA CVS + gcc3

[Paul Davis]

>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.

no, i knew about that issue, and thats why i had to recompile
everything. i am tempted to go back to my older ALSA CVS tree (i
tar'ed it before fetching current CVS) and see what happens.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: oops with current ALSA CVS + gcc3

[Niklas Werner]

Paul Davis wrote:
>>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.
> 
> 
> no, i knew about that issue, and thats why i had to recompile
> everything. i am tempted to go back to my older ALSA CVS tree (i
> tar'ed it before fetching current CVS) and see what happens.
> 

Just FYI. On my gentoo-1.4 everything compiles and runs fine (via82xx, 
usb-audio, dummy, virmidi)

maybe this helps:
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/specs
Configured with: /var/tmp/portage/gcc-3.2.2-r3/work/gcc-3.2.2/configure 
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/3.2 
--includedir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/include 
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2 
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/man 
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/3.2/info --enable-shared 
--host=i686-pc-linux-gnu --target=i686-pc-linux-gnu --with-system-zlib 
--enable-languages=c,c++,ada,f77,objc,java --enable-threads=posix 
--enable-long-long --disable-checking --enable-cstdio=stdio 
--enable-clocale=generic --enable-__cxa_atexit 
--enable-version-specific-runtime-libs 
--with-gxx-include-dir=/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/include/g++-v3 
--with-local-prefix=/usr/local --enable-shared --enable-nls 
--without-included-gettext
Thread model: posix
gcc version 3.2.2

have fun*

Niklas




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: oops with current ALSA CVS + gcc3

[Fernando Pablo Lopez-Lezcano]

> is anybody else using gcc 3.2.2 to compile their kernel and ALSA CVS? 

I'm currently using gcc-3.2 (default redhat compiler for 8.0- not 3.2.2,
I know) for a preliminary planet ccrma kernel. I'm currently running it
in my laptop and a couple other computers. I did not have any problems
so far (2.4.20-pre5 plus patches, current alsa cvs). 

-- Fernando




-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com