Thanks for the help. It eventually transpired that the network card had gone faulty. The change of memory just happened to be coincidental.
-----Original Message----- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 10:16 AM To: Ali Resting Cc: [EMAIL PROTECTED] Subject: Re: [squid-users] Kernel Panic Which looks like a netfilter problem. See my previous response on what do to with the ksymoops output as squid-users is not the correct place to get help in debugging the Linux kernel. In theory the class of kernel panics (null pointer dereference) could be caused by running out of memory, but most often they are plain kernel bugs. In a few rare cases these may also be caused by bad hardware. Regards Henrik On Wednesday 12 March 2003 08.56, Ali Resting wrote: > I finally managed to get the panic output and analyzed it using > ksymoops this is what I get: > > Unable to handle kernel NULL pointer dereference at virt > >>EIP; c021b113 <ip_nat_setup_info+36c3/a5c0> <===== > > Trace; c01ea250 <ip_finish_output+110/570> > Trace; c01d6fde <dev_queue_xmit+fe/2c0>
