From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: linux-kernel@vger.kernel.org
Subject: Oops in 2.2.18-22 with non-existent TCPIP route
Date: Tue, 21 Nov 2000 16:57:03 -0700 [thread overview]
Message-ID: <3A1B0BCF.71731541@timpanogas.org> (raw)
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/
reply other threads:[~2000-11-22 0:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A1B0BCF.71731541@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox