Description of problem: Noticed the following spew generated when I was running "gdb audacity". Also had rhythmbox/pulseaudio running. Did not notice that anything "broke".... System is Thinkpad X200 running fresh rawhide + koji. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon pulseaudio[3171]: alsa-source.c: Increasing minimal latency to 36.00 ms Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 1. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Apr 7 07:24:28 tlondon kernel: kmmio: spurious debug trap on CPU 0. Version-Release number of selected component (if applicable): kernel-2.6.29.1-54.fc11.x86_64 How reproducible: Not sure..... Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
wtf.. you have mmiotrace enabled somehow. That should only happen if you explicitly set it up. Ben, any idea what's going on here?
AFAICT it's not actually enabled, that's why it's complaining when it gets the debug trap. It seems the message is only being shown because the kernel is being built with debugging turned on.
This is kernel-2.6.29.1-54.fc11.x86_64 though, and we turned off debugging in -46 Oh wait, we didn't hook up MMIOTRACE to the 'move to debug' switch in the Makefile. I'll go do that.
Fixed in 2.6.29.1-58
I can no longer reproduce this. Closing.