[PLUG] system hung?

Brent Meshier brent@purdue.edu
Tue, 31 Aug 1999 17:21:25 -0400


My server decided to stop accepting inetd connections.  After a quick reboot
everything was back to normal.  I checked /var/log/mesages which is over 3MB
big.  Every 15 seconds for 3 hours, it was filled with similar messages of
this effect:

Aug 31 16:59:37 hostname kernel: Code: f6 9a 02 74 33 9c 5a fa f0 00 ba 2d
80 6b 21 c0 00 0f 82 51
Aug 31 16:59:37 hostname kernel: Unable to handle kernel paging request at
virtual address 9c337402
Aug 31 16:59:37 hostname kernel: current->tss.cr3 = 050e2000, %cr3 =
050e2000
Aug 31 16:59:37 hostname kernel: *pde = 00000000
Aug 31 16:59:37 hostname kernel: Oops: 0002
Aug 31 16:59:37 hostname kernel: CPU:    0
Aug 31 16:59:37 hostname kernel: EIP:    0010:[skb_recv_datagram+372/532]
Aug 31 16:59:37 hostname kernel: EFLAGS: 00010297
Aug 31 16:59:37 hostname kernel: eax: 00000000   ebx: 00000000   ecx:
c6736c80   edx: 00000000
Aug 31 16:59:37 hostname kernel: esi: c4593eec   edi: c6736c80   ebp:
c6736cc4   esp: c4593e0c
Aug 31 16:59:37 hostname kernel: ds: 0018   es: 0018   ss: 0018
Aug 31 16:59:37 hostname kernel: Process httpd (pid: 26357, process nr: 145,
stackpage=c4593000)
Aug 31 16:59:37 hostname kernel: Stack: c4593f6c 00000400 5868e9c7 c6736cc4
0000002f c5020900 c016cf5d c6736c80
Aug 31 16:59:37 hostname kernel:        00000000 00000000 c4593e48 00000000
c6736c80 c4593f6c c4593f6c c017177b
Aug 31 16:59:37 hostname kernel:        c01716e0 c6736c80 c4593f6c 00000400
00000000 00000000 c4593e74 c382b2ac
Aug 31 16:59:37 hostname kernel: Call Trace: [udp_recvmsg+89/296]
[inet_sendmsg+131/144] [inet_recvmsg+116/140] [sock_recvmsg+66/
180] [inet_recvmsg+0/140] [sys_recvfrom+198/304] [schedule+845/952]
Aug 31 16:59:37 hostname kernel:        [schedule_timeout+114/140]
[sock_poll+31/36] [do_poll+123/220] [sys_socketcall+371/480] [
system_call+52/56]
Aug 31 16:59:37 hostname kernel: Code: f6 9a 02 74 33 9c 5a fa f0 00 ba 2d
80 6b 21 c0 00 0f 82 51

Funny thing is, it appears be a problem with httpd, yet the web server was
the only that kept running...  Any ideas?

--Brent