Looks like squid blew up. Right before the GP, we had reports that the
squid proxy was very very slow (e.g. taking +5 seconds to respond to
requests).
general protection: 0000
CPU: 0
EIP: 0010:[<00145718>]
EFLAGS: 00010217
eax: f000e987 ebx: 00000000 ecx: 0333c03c edx: f000f84d
esi: 0333c0d4 edi: 03d81f78 ebp: 0333c018 esp: 03d81ee8
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process squid (pid: 23165, process nr: 25, stackpage=03d81000)
Stack: 0333c018 03d81f7c 00000000 00000800 122935a6 0333c03c 00000000 000001a8
028be414 026c5b1c 022a2c4b 0014fe1e 0333c018 03d81f78 00000e57 00000800
00000000 03d81f7c 00000fff 026c5ad4 08690ca0 026c5b60 00136863 026c5b60
Call Trace: [<0014fe1e>] [<00136863>] [<001223e6>] [<0010a54d>]
Code: 8a 40 0d a8 02 74 04 ff 4c 24 10 8b 7c 24 10 39 7b 30 0f 87
(You provided gdb dumps of the call backtrace but not where EIP was,
I am going to assume it was in tcp_recvmsg() as that is where the
other OOPS reports have been that sound like this one)
Does the patch I sent out today cure this?
---------------------------------------------////
Yow! 11.26 MB/s remote host TCP bandwidth & ////
199 usec remote TCP latency over 100Mb/s ////
ethernet. Beat that! ////
-----------------------------------------////__________ o
David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><