All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Sloan <jjs@pobox.com>
To: Matthew Kirkwood <matthew@hairy.beasts.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Networking: repeatable oops in 2.4.15-pre2
Date: Sat, 10 Nov 2001 10:46:00 -0800	[thread overview]
Message-ID: <3BED75E8.F87460A9@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111101148250.20176-100000@sphinx.mythic-beasts.com>

Matthew Kirkwood wrote:

> On Fri, 9 Nov 2001, J Sloan wrote:
>
> > I have been running the 2.4.15-pre kernels and
> > have found an interesting oops. I can reproduce
> > it immediately, and reliably, just by issuing an ssh
> > command (as a normal user).
>
> I'm seeing the same thing on my gateway,

Good to know it's not just me!


> I am back to 2.4.10 for now.

2.4.14 runs fine here, much faster than 2.4.10

> My setup:
>
> K6-200 w/64 MB RAM
> Debian Woody
> a 3c905B and an RTL-8139

Excellent, that rules out CPU specifics, distro
specifics, and ethernet adapter specifics -

> using iptables and transparent proxying (no masq).

Aha, we are both using iptables - (I am using nat)

Rusty, I hope you are reading this.

> >  <0>Kernel panic: Aiee, killing interrupt handler!
>
> I haven't decoded the oops, but I'm certainly seeing this
> line.

Good info, thanks for your input.

cu

jjs


  parent reply	other threads:[~2001-11-10 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-10  6:23 Networking: repeatable oops in 2.4.15-pre2 J Sloan
2001-11-10 11:53 ` Matthew Kirkwood
2001-11-10 13:31   ` David S. Miller
2001-11-10 18:50     ` J Sloan
2001-11-10 19:53     ` Confirm netfilter: " J Sloan
2001-11-10 18:46   ` J Sloan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-10 12:21 Networking: " Sven Vermeulen
2001-11-10 13:31 ` David S. Miller
2001-11-10 18:48 ` J Sloan
2001-11-10 23:14   ` Mike Fedyk
2001-11-11 22:16     ` Alok K. Dhir

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=3BED75E8.F87460A9@pobox.com \
    --to=jjs@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@hairy.beasts.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.