netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: lenehan@twibble.org
Cc: netdev@oss.sgi.com
Subject: Re: 2.5.69 IPv6 (modular) crash on boot
Date: Tue, 06 May 2003 20:16:18 -0700 (PDT)	[thread overview]
Message-ID: <20030506.201618.39175334.davem@redhat.com> (raw)
In-Reply-To: <20030506232037.GA5576@twibble.org>

   From: Jamie Lenehan <lenehan@twibble.org>
   Date: Wed, 7 May 2003 09:20:37 +1000

   IPv6 worked fine in 2.5.68, but I get a crash in 2.5.69 on boot. I
   haven't seen anyone else mention this though. This is a RedHat 8
   systems with the new modutils added and pretty much everything built
   modular:
   
Yes, we know it's broken and we're thinking about how
to fix it...

  reply	other threads:[~2003-05-07  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 23:20 2.5.69 IPv6 (modular) crash on boot Jamie Lenehan
2003-05-07  3:16 ` David S. Miller [this message]
2003-05-08 11:48   ` Jamie Lenehan

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=20030506.201618.39175334.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=lenehan@twibble.org \
    --cc=netdev@oss.sgi.com \
    /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;
as well as URLs for NNTP newsgroup(s).