Unable to handle kernel paging request

Jon Lewis (jlewis@inorganic5.fdt.net)
Sun, 23 Feb 1997 18:09:00 -0500 (EST)


What's this mean?

Unable to handle kernel paging request at virtual address 40007000
current->tss.cr3 = 01f84000, %cr3 = 01f84000
*pde = 00ec5067
*pte = 0013bc00
Oops: 0000
CPU: 0
EIP: 0010:[<00157b45>]
EFLAGS: 00010216
eax: 00986bb0 ebx: 00000400 ecx: 00000100 edx: 016bd400
esi: 40007000 edi: 016bd400 ebp: 00000400 esp: 01384c08
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process bloodgeon (pid: 19831, process nr: 37, stackpage=01384000)
Stack: 00001000 40007000 40007000 00856000 00000000 00000000 001d9148 00000000
00000000 00000058 00016000 00000000 00986bb0 ffffffe4 019f3ba0 00de2908
01384c94 01c481f0 00008180 01384c94 01c481f0 00008180 00123d52 00de2908
Call Trace: [<00123d52>] [<0015ab26>] [<0012ef24>] [<0012f05b>] [<0012ef24>]
[<0012fa34>] [<00136600>] [<0010a42f>] [<0010a672>]
Code: 64 f3 a5 83 e3 03 89 d9 64 f3 a4 55 8b 54 24 34 8b 52 24 03

Using `/kernels/System.map-2.0.27-fdt-elf' to map addresses to symbols.

>>EIP: 157b45 <ext2_file_write+249/45c>
Trace: 123d52 <__brelse+22/44>
Trace: 15ab26 <ext2_create+152/168>
Trace: 12ef24 <dump_write+1c/2c>
Trace: 12f05b <writenote+a7/c8>
Trace: 12ef24 <dump_write+1c/2c>
Trace: 12fa34 <elf_core_dump+9b8/a50>
Trace: 136600 <sock_lseek>
Trace: 10a42f <do_signal+1ef/280>
Trace: 10a672 <signal_return+12/40>

Code: 157b45 <ext2_file_write+249/45c> repz movsl %ds:(%esi),%es:(%edi)
Code: 157b48 <ext2_file_write+24c/45c> andl $0x3,%ebx
Code: 157b4b <ext2_file_write+24f/45c> movl %ebx,%ecx
Code: 157b4d <ext2_file_write+251/45c> repz movsb %ds:(%esi),%es:(%edi)
Code: 157b50 <ext2_file_write+254/45c> pushl %ebp
Code: 157b51 <ext2_file_write+255/45c> movl 0x34(%esp,1),%edx
Code: 157b55 <ext2_file_write+259/45c> movl 0x24(%edx),%edx
Code: 157b58 <ext2_file_write+25c/45c> addl (%eax),%eax
Code: 157b5a <ext2_file_write+25e/45c> nop
Code: 157b5b <ext2_file_write+25f/45c> nop
Code: 157b5c <ext2_file_write+260/45c> nop

This is 2.0.27 compiled ELF with gcc 2.7.2..1, libc 5.4.17, binutils
2.7.0.3. The process was a mud a user of ours runs, which is generally a
RAM hog, but not a major problem. The system still seems to be running
normally enough.

------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______