oops v2.0.33 net/ipv4/tcp.c:cleanup_rbuf net/core/sock.c:sock_wfree

Robert Frey (bobf@advansys.com)
Tue, 19 May 98 20:31 PDT

I'm running 2.0.33 on a WWW server and have seen these two oops
over the last week. Over the past year I've seen oops once a month
or so but they seem to be getting more frequent now. Over most
of this time I've run 2.0.30 or earlier kernels; I upgraded to 2.0.33
two weeks ago hoping these oops would go away.

In both these oops cases the process http-gw was running, but last
month I saw something similar with httpd or inetd. Since 2.0.33's
networking is very stable is there something that I may be overlooking
in upgrading on this system? Or could this be a real problem in 2.0.33?

Bob Frey

general protection: 0000
CPU: 0
EIP: 0010:[cleanup_rbuf+70/148]
EFLAGS: 00010286
eax: e4ddaf89 ebx: 012fa018 ecx: 01b6fa00 edx: edbbf79d
esi: 012fa0d8 edi: 0170bf7c ebp: 012fa018 esp: 0170bed8
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process http-gw (pid: 4215, process nr: 60, stackpage=0170b000)
Stack: 0170bf08 00000202 00145442 012fa018 012fa018 0170bf7c 00000000 00000000
0000019e 012fa03c 00000000 00000001 009ce414 007bc148 057e4297 0014fede
012fa018 0170bf78 00000000 00000000 00000000 0170bf7c 00000001 007bc100
Call Trace: [tcp_recvmsg+1002/1036] [inet_recvmsg+114/136] [sock_read+171/192] [sys_read+192/232] [system_call+82/128]
Code: 89 42 04 89 10 6a 01 51 e8 11 2c ff ff 83 c4 08 eb b4 53 e8

stack segment: 0000
CPU: 0
EIP: 0010:[<02a90c0f>]
EFLAGS: 00010206
eax: 02a90c0c ebx: 01645c0c ecx: 0175abf8 edx: 0175a000
esi: 00000154 edi: 00000000 ebp: 487b55a1 esp: 01666d40
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process http-gw (pid: 7098, process nr: 44, stackpage=01666000)
Stack: 001379df 01645c0c 01645c0c 0175acc0 00137cdf 01645c0c 0175acc0 0175acc0
01645c0c 00000000 0014764a 0175acc0 00000000 01645c0c 02a2a244 16f22eee
02a2a260 00137c01 00000000 000000ff 00000050 00000750 0216f7cc 00000000
Call Trace: [<001379df>] [<00137cdf>] [<0014764a>] [<00137c01>] [<001487fb>] [<0013fdc4>] [<049e3ecb>]
[<00138d84>] [<00117bef>] [<0010a55b>] [<001379fb>] [<00137cce>] [<00145017>] [<00145442>] [<0014fede>]
[<00135947>] [<00122ca8>] [<0010a5d2>]
Code: 01 0c ec a7 03 00 00 00 00 00 00 00 00 d0 f8 7e b7 03 00 00
Aiee, killing interrupt handler
Unable to handle kernel paging request at virtual address cfad202e
current->tss.cr3 = 00101000, \r3 = 00101000
*pde = 00000000
Oops: 0002

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

Trace: 1379df <sock_wfree+23/2c>
Trace: 137cdf <kfree_skb+b7/f4>
Trace: 14764a <tcp_ack+566/8c4>
Trace: 137c01 <show_net_buffers+41/68>
Trace: 1487fb <tcp_rcv+7f3/954>
Trace: 13fdc4 <ip_rcv+430/588>
Trace: 49e3ecb
Trace: 138d84 <net_bh+fc/11c>
Trace: 117bef <do_bottom_half+3b/60>
Trace: 10a55b <handle_bottom_half+b/20>
Trace: 1379fb <sock_rfree+13/20>
Trace: 137cce <kfree_skb+a6/f4>
Trace: 145017 <cleanup_rbuf+53/94>
Trace: 145442 <tcp_recvmsg+3ea/40c>
Trace: 14fede <inet_recvmsg+72/88>
Trace: 135947 <sock_read+ab/c0>
Trace: 122ca8 <sys_read+c0/e8>
Trace: 10a5d2 <system_call+52/80>

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu