Re: Kernel oops in tcp_ipv4.c

[EMAIL PROTECTED] wrote: > > Hello! > > > 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 t

Re: Kernel oops in tcp_ipv4.c

Hello! > 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

Re: Kernel oops in tcp_ipv4.c

I do not have the System map file for the kernel in question, all I have is the config file and bzImage. In any case the map file will be useless because the log file does not contain any register contents, stack contents or byte code at the crash point. However, I do know which file and function

Re: Kernel oops in tcp_ipv4.c

Mike Galbraith wrote: > > On Fri, 12 Jan 2001, Patrick wrote: > > > 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 > >