> Oops: 0000
> CPU: 0
> EIP: 0010:[<c01165c0>]
> EFLAGS: 00010246
> eax: 00000000 ebx: c1830b60 ecx: ffffffff edx: 00000020
> esi: 6c613261 edi: 6c613261 ebp: 000003ef esp: c096df68
> ds: 0018 es: 0018 ss: 0018
> Process insmod (pid: 98, process nr: 23, stackpage=c096d000)
> Stack: fffffffe 08054cc0 00000400 c182c000 00000000 00000000 00000400 c1830e4f
> 08054db8 080550af 0000001f c011688d c182c000 08054cc0 00000011 bffffdec
> c0a71018 00000400 bffffdec bffffda8 c010a530 c0941000 c010a3f8 08054b38
> Call Trace: [<c182c000>] [<c1830e4f>] [<c011688d>] [<c182c000>] [<c010a530>] [<c010a3f8>]
> Code: f2 ae f7 d1 49 89 ce 8d 6c 2e 01 ff 44 24 28 83 c3 08 39 54
>
> Using `/System.map' to map addresses to symbols.
>
> >>EIP: c01165c0 <qm_symbols+1dc/23c>
There is definitely something fishy in here, I've seen too many reports
about oopses like this one, all happening in qm_symbols and with similar
values in %edx. I'll try to take a look at the code tomorrow if no one
else does it before..
Ionut
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.