I got this on my masq box:
general protection: 0000
CPU: 0
EIP: 0010:[__release_sock+15/128]
EFLAGS: 00010202
eax: 50bccf5e ebx: 0065f018 ecx: 0065f1f0 edx: 00000006
esi: 0065f0d8 edi: 00000000 ebp: 00000001 esp: 005a3f2c
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Corrupted stack page
Process squid (pid: 8875, process nr: 35, stackpage=005a3000)
Stack: 0065f018 00143a93 0065f018 0065f018 0034ad90 0034ad90 0014dfe5 0065f018
00000000 0034ad00 00000000 001337ab 0034ad90 00000000 0034ad00 0034ad00
0034ad00 bffffc50 001339dc 0034ad90 001eb3fc 00121690 0034ad00 001eb3fc
Call Trace: [tcp_close+507/536] [inet_release+97/108] [sock_release+91/156] [sock_close+36/44] [__fput+28/64] [close_fp+76/92] [sys_close+68/80]
[system_call+85/124]
Code: 83 78 28 00 74 69 ff 05 d4 02 1a 00 90 8d 83 8c 00 00 00 8b
Is this hazardous? The machine is still up and running.
uptime is around 43 days and squid has been running more than half of that
time. This machine is a 386DX40 with 8MB memory and 25MB of swap -- but
hey, i got it for free :) -- featuring 3c509 and an internal modem for
ppp connection (yes, it was up at the time of the fault).
squid is acting funny, even though i restarted it. I was about to shutdown
the machine anyways, because of a hardware "upgrade", now it seems I'll
compile a new kernel for it, too. Is this a known problem fixed in
2.0.34-pre8? I don't think 2.1.x will do any good to that box :) And i'd
rather not have others in the household complain about not being able to
read mail since that box is also an imap server.
If someone's interested, i can provide more info.
Taneli <vahakang@cs.helsinki.fi>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu