ALSA + GCC 4.1.1 + -Os is known to be a bad combination on some arches; see http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27363 . (I tripped over it on an ARM target, but my limited understanding of GCC internals does not allow me to conclude that it is ARM-specific.) A patch claiming to fix the bug was integrated into the 4.1 branch, but my tests with a recent (20070115) gcc-4.1 snapshot indicate that it has regressed again.
You might also check /proc/cpu/alignment; we have seen the alignment fixup code trigger for alignment errors in both kernel and userspace. The default appears to be to IGNORE alignment traps from userspace, which results in bogus data and potentially a wacky series of system calls, which could conceivably trigger an oops. I am told that echo 2
/proc/cpu/alignment activates the kernel alignment fixup code, and
that 3 turns on some sort of logging in addition to the fixup (haven't pursued this myself). No idea whether this is relevant to your CPU. Cheers, - Michael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
