OK, the btaudio error was a red herring. The Ooops seems to be in bttv-0.8.34 not btaudio. I have yet to hook up the serial console (gotta go get one) so that I can get the actual Ooops data into ksymoops, but I did write down and feed the Call Trace: and Code: and feed that into ksymoops and this is what I got: >>EIP; d89ef52a <[bttv]bttv_riscgroup_free+2a/90> <===== Trace; d89f3c9c <[bttv].rodata.end+2cbe/2f82> Trace; d89e8fae <[bttv]release_idle_buffers+4e/70> Trace; d89f7640 <[bttv]bttvs+0/2e30> Trace; d89e8f60 <[bttv]release_idle_buffers+0/70> Trace; c011ed02 <timer_bh+212/250> Trace; c010851c <do_IRQ+9c/b0> Code; d89ef52a <[bttv]bttv_riscgroup_free+2a/90> 00000000 <_EIP>: Code; d89ef52a <[bttv]bttv_riscgroup_free+2a/90> <===== 0: 0f 0b ud2a <===== Code; d89ef52c <[bttv]bttv_riscgroup_free+2c/90> 2: 59 pop %ecx Code; d89ef52c <[bttv]bttv_riscgroup_free+2c/90> 3: 5b pop %ebx Code; d89ef52e <[bttv]bttv_riscgroup_free+2e/90> 4: 6a 00 push $0x0 Code; d89ef530 <[bttv]bttv_riscgroup_free+30/90> 6: 6a 00 push $0x0 Code; d89ef532 <[bttv]bttv_riscgroup_free+32/90> 8: 56 push %esi Code; d89ef532 <[bttv]bttv_riscgroup_free+32/90> 9: 57 push %edi Code; d89ef534 <[bttv]bttv_riscgroup_free+34/90> a: e8 f6 01 00 00 call 205 <_EIP+0x205> d89ef72e <[bttv]bttv_riscgroup_activate+19e/1a0> Code; d89ef538 <[bttv]bttv_riscgroup_free+38/90> f: 8b 15 60 3f 9f 00 mov 0x9f3f60,%edx Is this enough or is there more out of the Ooops data that you need fed into ksymoops to find the problem? b. -- Brian J. Murrell
Attachment:
pgp0uGpo6a8b8.pgp
Description: PGP signature
