I got this message when I was in a telnet session, trying to start talk:
Unable to handle kernel paging request at virtual address 5b485b1b
current->tss.cr3 = 02255000, %cr3 = 02255000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<5b485b1b>]
EFLAGS: 00010616
eax: 00000000 ebx: 3151b1d9 ecx: 00000000 edx: 080600b6
esi: 5b1b6d30 edi: 48313b32 ebp: c0e8bef4 esp: c0e8bee0
ds: 0018 es: 0018 ss: 0018
Stack: 20726f66 72756f79 ...
...
...
Call trace: [<c01b3bc2>] [<c01b88eb>] [<c01ba7ec>] [<c01b6725>] [<c0127961>]
[<c0109d2c>]
Code: <1>Unable to hande kernel paging request at virtual address 5b485b1b
current->tss.cr3 = 02255000, %cr3 = 02255000
*pde = 00000000
Some info from my System.map:
c01b3ba4 t con_put_char
c01b88f8 t opost_block
c01ba6b4 t write_chan
This is a ordinary 2.1.114 kernel + my little hack for vesa fb and protected
mode interface for panning. But it doesn't seem to be in my functions anyway.
And if I made up this mess with vesa pmi, what's usually causing this?
My system was definently not overloaded and I had lots of ram free.
Best regards,
Ulf Carlsson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html