crash on 2.0.35

Scott R. Every (scott@emji.net)
Sun, 07 Feb 1999 20:21:09 -0500

Got this error in my syslog and the whole machine went to hell...

syslog:
Feb 6 21:36:21 beast kernel: Unable to handle kernel paging request at virtual
address cf41889c
Feb 6 21:36:21 beast kernel: current->tss.cr3 = 00ac6000, ^Lr3 = 00ac6000
Feb 6 21:36:21 beast kernel: *pde = 00000000
Feb 6 21:36:21 beast kernel: Oops: 0000
Feb 6 21:36:21 beast kernel: CPU: 0
Feb 6 21:36:21 beast kernel: EIP: 0010:[__release_sock+50/132]
Feb 6 21:36:21 beast kernel: EFLAGS: 00010296
Feb 6 21:36:21 beast kernel: eax: 0741889c ebx: 07418810 ecx: 0f41889c ed
x: 05368810
Feb 6 21:36:21 beast kernel: esi: 00000212 edi: 069a8ea8 ebp: 00000002 es
p: 069a8e8c
Feb 6 21:36:21 beast kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 00
18
Feb 6 21:36:21 beast kernel: Process httpd (pid: 4216, process nr: 22, stackpag
e=069a8000)
Feb 6 21:36:21 beast kernel: Stack: 07418810 00147b38 07418810 0000000b 0741881
0 00000000 00000002 05368810
Feb 6 21:36:21 beast kernel: 023e1048 00147c3f 07418810 00000000 0741881
0 0536f390 00000002 001514ae
Feb 6 21:36:21 beast kernel: 07418810 00000002 00000000 0536f390 023e109
0 bffff93c 001382c3 023e1090
Feb 6 21:36:21 beast kernel: Call Trace: [wait_for_connect+92/184] [tcp_accept+
171/188] [inet_accept+78/356] [sys_accept+287/424] [flock_lock_file+273/388] [fl
ock_lock_file+303/388] [sys_socketcall+338/732]
Feb 6 21:36:21 beast kernel: [system_call+85/128]
Feb 6 21:36:21 beast kernel: Code: 8b 11 8b 41 04 c7 01 00 00 00 00 c7 41 04 00
00 00 00 c7 41
Feb 6 21:36:21 beast kernel: Aiee, killing interrupt handler

I got about one of the above every second until I received the following
message in the messages file:

messages:
Feb 6 21:38:17 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:38:43 beast kernel: : 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:39:33 beast kernel: : 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:39:57 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:40:19 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:41:22 beast kernel: s: 0018 es: 0018 fs: 002b gs: 002b ss: 001
8
Feb 6 21:41:41 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:42:31 beast kernel: 018 fs: 002b gs: 002b ss: 0018
Feb 6 21:42:56 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:43:30 beast kernel: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:44:25 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Feb 6 21:44:32 beast kernel: 0018 es: 0018 fs: 002b gs: 002b ss: 0018

It kept fillinf the syslog with errors for the next 15 hours until the system
was able to be rebooted. During this time the system answered pings, but was
otherwise dead.

This was running Linux 2.0.35 and had been running smoothly for 97 days.
I have upgraded the kernel to 2.0.36, but would appreciate any suggestions
of what went wrong and what I can do to insure it does not happen again.

I have other machine using 2.0.35 with similar(and longer) uptimes so this
worries me.

Any help would be appreciated.

scott

--
Scott R. Every        "Everything is controlled by a small evil group to 
 EMJ Internet          which, unfortunately, no one we know belongs."
 voice : 1-800-548-2319  fax : 1-919-363-4423  mailto:scott@emji.net
 WWW - http://www.emji.net   


Do you believe in Macintosh? Learn how to help the cause by 
subscribing to the "EvangeList" listserver! Send email to:
<evangelist@macway.com> or go to: 
<http://www.lists.apple.com/>




-
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.tux.org/lkml/