Oops in 2.2.18-22 with non-existent TCPIP route

Oops in 2.2.18-22 with non-existent TCPIP route

[Jeff V. Merkey]

Alan,

I have an Oops with 2.2.18-22 that only shows up on a Linux server
that's configured as a pppd dial in server with dynamic address
assignment (no DHCP).  Host IP addresses are configured in an
options.ttyS0(192.168.0.1) and options.ttyS1(192.168.0.2) files in
/etc/ppp.  

We caused the Oops by accident when we misconfigured our Cisco CPA 2501
router with a static route for network 207.225.212.40 (mask
255.255.255.248) that pointed to this server (the server had no routes
to this network but used to).  We were moving some servers around to
segregate the law firm onto a private network.

I was not running ksymoops but have it setup now and we are attempting
to recreate the conditions that produced the oops.  The Oops reported is
crashed in process slocate (clearly misleading -- looks like an Oops
from an interrupt).   We will attempt to get the Oops again.  

Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/