Kernel oops in tcp_ipv4.c
I am running a medium-high traffic web server on an SMP machine. I have always had problems with linux hanging (No syslog messages and no console response). I have tried kernel versions 2.2.12, 2.2.14 and 2.2.16
Recently I tried 2.2.17, this kernel was up for about a month, before there was a kernel oops. The syslog messages are:
Jan 11 21:10:06 ws2 kernel: tcp_v4_hash: bug, socket state is 1 Jan 11 21:10:06 ws2 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Jan 11 21:10:06 ws2 kernel: current->tss.cr3 = 0ca7c000, %cr3 = 0ca7c000 Jan 11 21:10:06 ws2 kernel: *pde = 00000000 Jan 11 21:10:06 ws2 kernel: Oops: 0002 Jan 11 21:10:06 ws2 kernel: CPU: 0
The code that outputs the first message is in tcp_ipv4.c, and was added in version 2.2.17. The code deliberately causes a kernel oops when it encounters this bug, presumably because the IP stack is unusable at this point.
If this code was deliberately added then presumably someone knows what might cause the problem. Is there a patch somewhere that fixes this problem?
regards,
Patrick
Signature · 8 lines
Patrick Mackinlay [email protected] ICQ: 59277981 tel: +44 7050699851 fax: +44 7050699852 SpaceSurfer Limited http://www.spacesurfer.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Hello!
Quoted 2 lines
Recently I tried 2.2.17, this kernel was up for about a month, before there was a kernel oops. The syslog messages are:
This is caused by illegal setting of /proc/sys/net/ipv4/ip_local_port_range with kernels before 2.2.18.
Do not touch this value or change it to something reasonable, f.e. to one of values recommended in net/ipv4/tcp_ipv4.c
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · [email protected] wrote:
Hello!
Quoted 2 lines
Recently I tried 2.2.17, this kernel was up for about a month, before there was a kernel oops. The syslog messages are:
Quoted 7 lines
This is caused by illegal setting of
/proc/sys/net/ipv4/ip_local_port_rangewith kernels before 2.2.18.Do not touch this value or change it to something reasonable, f.e. to one of values recommended in
net/ipv4/tcp_ipv4.cAlexey
You are right I had the range set to 16384-65535! I have changed the high limit to 61000, that should be ok. Is there any point in having the low limit above 1024?
regards,
Patrick
Signature · 8 lines
Patrick Mackinlay [email protected] ICQ: 59277981 tel: +44 7050699851 fax: +44 7050699852 SpaceSurfer Limited http://www.spacesurfer.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/