Oops in tcp-recvmsg 2.0.33 but not in 2.0.32

Christoph Lameter (christoph@lameter.com)
Tue, 24 Feb 1998 21:25:14 -0800 (PST)

I keep getting these oopses. There is something screwy in the 2.0.33 tcp
layer. 2.0.32 works fine:

Feb 22 17:57:54 hur kernel: general protection: 0000
Feb 22 17:57:54 hur kernel: CPU: 0
Feb 22 17:57:54 hur kernel: EIP: 0010:[tcp_recvmsg+368/1036]
Feb 22 17:57:54 hur kernel: EFLAGS: 00010213
Feb 22 17:57:54 hur kernel: eax: f000e987 ebx: 00000000 ecx: 0091a438
edx: f000f84d

Feb 22 17:57:54 hur kernel: esi: 0091a4d4 edi: 0000019b ebp: 0091a414
esp: 00bbfee8

Feb 22 17:57:54 hur kernel: ds: 0018 es: 0018 fs: 002b gs: 002b
ss: 0018
Feb 22 17:57:54 hur kernel: Process apache (pid: 23892, process nr: 28,
stackpage=00bbf00
0)
Feb 22 17:57:54 hur kernel: Stack: 0091a414 00bbff7c 00000000 00000000
10957dbf 0091a438
00000000 0000019b
Feb 22 17:57:54 hur kernel: 00c7b810 00f3b948 00967471 00150f26
0091a414 00bbff78
00000e65 00000000
Feb 22 17:57:54 hur kernel: 00000000 00bbff7c 00001000 00f3b900
080a883c 00f3b990
00135c77 00f3b990
Feb 22 17:57:54 hur kernel: Call Trace: [inet_recvmsg+114/136]
[sock_read+171/192] [sys_read+192/232] [system_call+85/128]
Feb 22 17:57:54 hur kernel: Code: 8a 40 0d a8 02 74 04 ff 4c 24 10 8b 7c
24 10 39 7b 30 0
f 87

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