>
> Greetings,
>
>
> kernel BUG at page_alloc.c:81!
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c012fa2f>]
> EFLAGS: 00010282
> eax: 0000001f ebx: 00000000 ecx: 00000000 edx: 00000002
> esi: c1b97ee8 edi: 00000000 ebp: 00000000 esp: e8629d54
> ds: 0018 es: 0018 ss: 0018
> Process popper (pid: 1155, stackpage=e8629000)
> Stack: c02c4914 c02c4a08 00000051 c01387c3 c1b97ee8 00000000 c1b97ee8
> c1b97ee8
> c1b97ee8 c1b97f10 00000000 c5f4f5c0 c0126d3d 00000000 c1b97ee8
> e8629db8
> 00000000 c01915f0 ea0f96a0 ea0f96a0 e8629db8 00000000 00000000
> d2062184
> Call Trace: [<c01387c3>] [<c0126d3d>] [<c01915f0>] [<c0126dbd>]
> [<c01b4f84>] [<c01cb608>] [<c01d6959>]
> [<c014c4a6>] [<c01cbbcf>] [<c0134517>] [<c014949c>] [<c0140e40>]
> [<c01347c2>] [<c0106edb>]
>
> Code: 0f 0b 83 c4 0c 8b 46 18 83 e0 20 74 16 6a 53 68 08 4a 2c c0
>
>
> Got the above today. Machine was forced to reboot after weeks online
> hw info:
>
> kernel 2.4.8 SMP
> P3 733 x 2
> 1G RAM
> SCSI based
As Seth said, this needs to be fed through ksymoops to be useful,
but what it amounts to is freeing a locked page which should not
happen. A decoded stack trace will help track it down.
Steve
|