Partial Oops in 2.6.20?

2007-02-18 Thread Arthur Smith

Hi,
I found this this morning on an AMD X2 based system that was unresponsive:


ds: 007b es:007b ss:0068
Process events/1 (pid: 7, ti=f7c48000 task=f7d31560 task.ti=f7c48000)
Stack:   002c f7d1dc18 0022 f7d1dc18 002c f7d1dc00
   c014bfbf   f7d28240 f7d2cde4 f7d2cdc0 f7d28240
  0202 c1710380 c014d12a   c1710384 c17fe240 c01263ca
Call Trace:
[] drain_array+0x92/0xbd
[] cache_reap+0x8e/0x113
[] run_workqueue+0x85/0x125
[] cache_reap+0x0/0x113
[] worker_thread+0xf9/0x124
[] default_wake_function+0x0/0xc
[] worker_thread+0x0/0x124
[] kthread+0xb2/0xdd
[] kthread+0x0/0xdd
[] kernel_thread_helper+0x7/0x10
===
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
 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: [] free_block+0x5f/0xf1 SS:ESP 0068:f7c48f0c
<6>note: events1/[7] exited with preempt_count 1

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.
 Thanks,
   Art Smith

-
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/


Partial Oops in 2.6.20?

2007-02-18 Thread Arthur Smith

Hi,
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:   002c f7d1dc18 0022 f7d1dc18 002c f7d1dc00
   c014bfbf   f7d28240 f7d2cde4 f7d2cdc0 f7d28240
  0202 c1710380 c014d12a   c1710384 c17fe240 c01263ca
Call Trace:
[c014bfbf] drain_array+0x92/0xbd
[c014d12a] cache_reap+0x8e/0x113
[c01263ca] run_workqueue+0x85/0x125
[c014d09c] cache_reap+0x0/0x113
[c0126ab8] worker_thread+0xf9/0x124
[c0114d22] default_wake_function+0x0/0xc
[c01269bf] worker_thread+0x0/0x124
[c012906d] kthread+0xb2/0xdd
[c0128fbb] kthread+0x0/0xdd
[c01036fb] kernel_thread_helper+0x7/0x10
===
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
6note: events1/[7] 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.
 Thanks,
   Art Smith

-
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/