'Unable to handle...' in 1.3.69

Chris Adams (cadams@sh1.ro.com)
Sun, 24 Mar 1996 16:43:32 -0600 (CST)

Using 1.3.69, I get the following (sometimes every few hours on
different processes, sometimes not for several days). It seems to
happen regularly when making a tape backup with 'tar -cz' of a large
amount of disk (that's when the following happened).

Unable to handle kernel paging request at virtual address c81b0d20
current->tss.cr3 = 01860000, %cr3 = 01860000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<0010fd77>]
EFLAGS: 00010206
eax: 081b0d14 ebx: 02546810 ecx: 081b0d14 edx: 00000000
esi: 001acfc4 edi: 00000000 ebp: 01862fb4 esp: 01862f90
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process gzip (pid: 6335, process nr: 73, stackpage=01862000)
Stack: 02546810 0805618c 00000002 081b0d14 0805718c 00005000 02546810 0805618c
00000002 bffffdd4 0010a420 00000000 0805618c 00006000 0805618c 00000002
bffffdd4 00001000 0000002b 0000002b 0000002b 0000002b 00000003 400190ac
Call Trace: [<0010a420>]
Code: 8b 41 0c 8b 51 08 8b 19 c7 41 04 00 00 00 00 50 ff d2 89 5d

Using `/System.map' to map addresses to symbols.

>>EIP: 10fd77 <schedule+67/2b4>
Trace: 10a420 <ret_from_sys_call>

Code: 10fd77 <schedule+67/2b4> movl 0xc(%ecx),%eax
Code: 10fd7a <schedule+6a/2b4> movl 0x8(%ecx),%edx
Code: 10fd7d <schedule+6d/2b4> movl (%ecx),%ebx
Code: 10fd7f <schedule+6f/2b4> movl $0x0,0x4(%ecx)
Code: 10fd86 <schedule+76/2b4> pushl %eax
Code: 10fd87 <schedule+77/2b4> call *%edx
Code: 10fd89 <schedule+79/2b4> movl %ebx,0x0(%ebp)
Code: 10fd8c <schedule+7c/2b4> nop
Code: 10fd8d <schedule+7d/2b4> nop

Sometimes it will happen to init, which will cause the system to have to
be rebooted (by hitting the RESET switch). This system is a mail
server, WWW server, and shell server for an ISP, so I can't just go
jumping to the latest kernel with every new version, however, if this
problem is fixed in a newer version please let me know!

-- 
Chris Adams (C.Adams@Yellow-Jackets.com)
"So, if anybody wants to have hardware sent to them: don't call me, but
instead write your own unix operating system.  It has worked every time
for me." - Linus Torvalds, author of Linux (Unix-like) OS