Partial Oops in 2.6.20?
From: Arthur Smith
Date: Sun Feb 18 2007 - 14:23:37 EST
I found this this morning on an AMD X2 based system that was unresponsive:
<....this part of the oops was lost off of the top of the screen, then>
ds: 007b es:007b ss:0068
Process events/1 (pid: 7, ti=f7c48000 task=f7d31560 task.ti=f7c48000)
Stack: 00000000 00000000 0000002c f7d1dc18 00000022 f7d1dc18 0000002c f7d1dc00
00000000 c014bfbf 00000000 00000000 f7d28240 f7d2cde4 f7d2cdc0 f7d28240
00000202 c1710380 c014d12a 00000000 00000000 c1710384 c17fe240 c01263ca
Code: 05 03 15 20 d2 4f c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 04 0f 0b eb
<???..4> 24 28 8b 16 8b 7c 85 34 8b 46 04 <89> 42 04 89 10 2b 4e 0c c7 06 00 01 10 00 c7 4?
EIP: [<c014be9b>] free_block+0x5f/0xf1 SS:ESP 0068:f7c48f0c
<6>note: events1/ exited with preempt_count 1
<a few IPTables log messages?>
I copied this from a picture I took of the screen. I'm not sure there is enough there to be of any use.
It looks like the system was recording a tv show from a BT878 card at the time, using mencoder. Everything
is compiled into the kernel, no modules. I haven't seen Oops prior to this on this system. If this
is of any use, let me know and I can provide more details on the system - or anything else that might help.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/