Here's the info... You'll notice there was a gpf at 13:18 which didn't
cause a crash, then another at 14:55 which did.
Linux 2.0.36 #1 Mon Nov 16 22:44:19 EST 1998
gcc 2.7.2.3
Jun 16 13:18:27 server1 kernel: general protection: 0000
Jun 16 13:18:27 server1 kernel: CPU: 0
Jun 16 13:18:27 server1 kernel: EIP: 0010:[tcp_recvmsg+368/1036]
Jun 16 13:18:27 server1 kernel: EFLAGS: 00010213
Jun 16 13:18:27 server1 kernel: eax: f000e987 ebx: 00000000 ecx: 033a6c30 edx: f000f84d
Jun 16 13:18:27 server1 kernel: esi: 033a6ccc edi: 00000198 ebp: 033a6c0c esp: 01b47ee8
Jun 16 13:18:27 server1 kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jun 16 13:18:27 server1 kernel: Process httpd (pid: 4909, process nr: 50, stackpage=01b47000)
Jun 16 13:18:27 server1 kernel: Stack: 033a6c0c 01b47f7c 00000000 00000000 163cdc29 033a6c30 00000000 00000198
Jun 16 13:18:27 server1 kernel: 031ae810 03eb3648 063dd2de 00153fca 033a6c0c 01b47f78 00000e68 00000000
Jun 16 13:18:27 server1 kernel: 00000000 01b47f7c 00001000 03eb3600 080fd024 03eb3690 00138e03 03eb3690
Jun 16 13:18:27 server1 kernel: Call Trace: [inet_recvmsg+114/136] [sock_read+171/192] [sys_read+192/232] [system_call+85/124]
Jun 16 13:18:27 server1 kernel: Code: 8a 40 0d a8 02 74 04 ff 4c 24 10 8b 7c 24 10 39 7b 30 0f 87
Jun 16 14:55:54 server1 kernel: general protection: 0000
Jun 16 14:55:54 server1 kernel: CPU: 0
Jun 16 14:55:54 server1 kernel: EIP: 0010:[tcp_recvmsg+368/1036]
Jun 16 14:55:54 server1 kernel: EFLAGS: 00010217
Jun 16 14:55:54 server1 kernel: eax: f000e987 ebx: 00000000 ecx: 0069b03c edx: f000f84d
Jun 16 14:55:54 server1 kernel: esi: 0069b0d8 edi: 000001a3 ebp: 0069b018 esp: 003a2ee8
Jun 16 14:55:54 server1 kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jun 16 14:55:54 server1 kernel: Process httpd (pid: 9630, process nr: 87, stackpage=003a2000)
Jun 16 14:55:54 server1 kernel: Stack: 0069b018 003a2f7c 00000000 00000000 2d90f91d 0069b03c 00000000 000001a3
Jun 16 14:55:54 server1 kernel: 0217e414 00861d48 1d91efc7 00153fca 0069b018 003a2f78 00000e5d 00000000
Jun 16 14:55:54 server1 kernel: 00000000 003a2f7c 00001000 00861d00 080fd024 00861d90 00138e03 00861d90
Jun 16 14:55:54 server1 kernel: Call Trace: [inet_recvmsg+114/136] [sock_read+171/192] [sys_read+192/232] [system_call+85/124]
Jun 16 14:55:54 server1 kernel: Code: 8a 40 0d a8 02 74 04 ff 4c 24 10 8b 7c 24 10 39 7b 30 0f 87
Jun 16 14:55:54 server1 kernel: Unable to handle kernel paging request at virtual address f1313d54
Jun 16 14:55:54 server1 kernel: current->tss.cr3 = 03a7c000, %cr3 = 03a7c000
Jun 16 14:55:54 server1 kernel: *pde = 00000000
Jun 16 14:55:54 server1 kernel: Oops: 0000
Jun 16 14:55:54 server1 kernel: CPU: 0
Jun 16 14:55:54 server1 kernel: EIP: 0010:[wake_up_interruptible+53/232]
Jun 16 14:55:54 server1 kernel: EFLAGS: 00010202
Jun 16 14:55:54 server1 kernel: eax: 00861d4c ebx: 43540030 ecx: 00861d4c edx: 31313d54
Jun 16 14:55:54 server1 kernel: esi: 00000128 edi: 00861d48 ebp: 034b2e3c esp: 034b2e30
Jun 16 14:55:54 server1 kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Jun 16 14:55:54 server1 kernel: Process relay-ctrl-allo (pid: 10865, process nr: 52, stackpage=034b2000)
Jun 16 14:55:54 server1 kernel: Stack: 0069b018 00000128 00000000 0108be0e 001535bf 00861d4c 0069b018 0013b8ff
Jun 16 14:55:54 server1 kernel: 0069b018 0069b018 0108be7c 0013bbff 0069b018 0108be7c 000d0300 00000000
Jun 16 14:55:54 server1 kernel: 0108be7c 0013c092 0108be7c 00000000 000d030a 001d70f4 001a8c30 0108be7c
Jun 16 14:55:54 server1 kernel: Call Trace: [def_callback3+39/60] [sock_wfree+35/44] [kfree_skb+183/244] [dev_kfree_skb+62/76] [ewrk3_queue_pkt+1088/1276] [<04f5a5d0>] [ipfw_output_check+35/40]
Jun 16 14:55:54 server1 kernel: [do_dev_queue_xmit+455/504] [dev_queue_xmit+26/36] [ip_queue_xmit+409/492] [tcp_send_ack+553/572] [tcp_delack_timer+0/16] [tcp_delack_timer+10/16] [timer_bh+749/820] [do_bottom_half+59/96]
Jun 16 14:55:54 server1 kernel: [handle_bottom_half+11/24]
Jun 16 14:55:54 server1 kernel: Code: 8b 02 83 f8 01 75 67 9c 5e fa c7 02 00 00 00 00 83 7a 4c 00
Jun 16 14:55:54 server1 kernel: Aiee, killing interrupt handler
Jun 16 15:42:40 server1 syslogd 1.3-3: restart.
Jun 16 15:42:40 server1 kernel: klogd 1.3-3, log source = /proc/kmsg started.
Btw, there was no shell logins at the time and the server provides web,
mail, ftp and dns services via apache, qmail, wu-ftpd and bind4.
Any help is appreciated.
Regards,
Trevor Astrope
astrope@e-corp.net
-
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/