oss_sblive kernel panic

[hash]

I'm posting it here because bugzilla down.
Just recently I've got my self problem, any attempt to play sound through my Creative Labs SB Audigy result in kernel panic.
Here is screen shot.
It appear to happens only with oss_sblive as I've tried HDAudio and USB modules and they work without crashing.
Here is my emerege --info, list of installed packages, kernel config.
If any additional info is needed just ask.

[cesium]

Can you post 'lspci -vnn' or 'ossinfo -v3' output for the card? Knowing exactly which card it is may help a bit...

[hash]

Here it is: lspci -vnn, ossinfo -v3 and also installation history.
Also the thing I've forgot to mention, only thing that come in my mind of the cause is glibc, you see I've was using 2.6.36-r3 for long time and only when 2.6.37 hit portage tree I tried to compile it, it is entirely my fault that I haven't left a backup of 2.6.36-r3 but it is no use to mourn other spilled milk.
I've tried to recompile 2.6.36-r3 with same old config, same result.
Also I've tried to recompile gcc and then kernel with this "new" couple (gcc+glibc) no change.
I've tried also to downgrade glibc but emerge refused to do that stating that this is sure way to ruin my system and I'm tend to believe it.

[cesium]

I'm pretty sure glibc has nothing to do with it (it isn't compiled into or used by kernel and kernel modules). I also gather oss_sblive didn't use to work in the past, right?

[hash]

Before this attempt to compile 2.6.37 kernel oss_sblive was working flawlessly.

[hash]

I've found the cause of kernel panic.
It is hidden in

Code: Select all

CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"

if I perform:

Code: Select all

gcc -march=native -O2 -pipe -fomit-frame-pointer -E -v - </dev/null 2>&1 | sed -n 's/.* -v - //p'

I've got this result

Code: Select all

-D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf -msse4.1 --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=3072 -mtune=core2 -fomit-frame-pointer -O2

and that -march=core2 is the cause.
If I compile oss-devel with -march=i686 oss_sblive work flawlessly stable!
Now to find out how can I set CFLAGS's for one package...

[akarz]

Did you make any progress on this ?

I have a system freeze when trying to load my oss_sblive for my audigy 2 zs notebook card. The other modules seem to load fine. Before I pursue opening a thread specifically abt my problems, I thought, I'd check here.

My system lenovo t61 with ubuntu 10.10 32 bit, oss deb built using mercurial.

[hash]

If you compile oss you can prefix make with CFLAGS="-march=i686".
At least that solved my problem with kernel panic at any sound (osstest as example).

[kosproger]

hash
Did you compile like this:

Code: Select all

configure
CFLAGS="-march=i686" make
make install

??

[cesium]

Yea, that would add to CFLAGS. The build system alas is somewhat insistent when they are concerned since they are added "CFLAGS+=" in the Makefiles.

Something like
find . -name Makefile | xargs sed -i -e 's/CFLAGS.*/CFLAGS={WHAT YOU WANT}/'
before make should let you decide on your own cflags.