public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Matt LaPlante <laplam@rpi.edu>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, linux-kernel@vger.kernel.org
Subject: Re: Potential IPSec DoS/Kernel Panic with 2.6.13
Date: Sun, 4 Sep 2005 20:49:15 +0200	[thread overview]
Message-ID: <9a87484905090411492cc3f823@mail.gmail.com> (raw)
In-Reply-To: <200509041638.j84Gc5lA024062@ms-smtp-02-eri0.southeast.rr.com>

On 9/4/05, Matt LaPlante <laplam@rpi.edu> wrote:
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> > owner@vger.kernel.org] On Behalf Of Herbert Xu
> > Sent: Sunday, September 04, 2005 4:24 AM
> > To: Matt LaPlante
> > Cc: linux-kernel@vger.kernel.org
> > Subject: Re: Potential IPSec DoS/Kernel Panic with 2.6.13
> >
> > Matt LaPlante <laplam@rpi.edu> wrote:
> > >
> > > network connectivity on my router.  Upon further inspection I noticed
> > the
> > > packet had actually caused a kernel panic (visible only on the monitor,
> > now
> > > also unresponsive).
> >
> > Thanks for the report.  I'll try to track it down.
> >
> > If you could jot down the important bits of the panic message
> > (IP, Call-Trace) it would help me find the problem much quicker.
> 
> I'd be more than happy to help you track this one down.  The problem here is
> that the panic scrolls up and off the screen after which the system is
> unusable.  Is there a way for me to capture it or redirect it somewhere that
> I can read it?  I can also include my kernel config or any other system
> details of interest.  Thanks.
> 
serial console over a cross-over cable to a second box.
netconsole will let you put the console on a different box over the network.
console on line printer will let you have a permanent record of the
console output on paper.

See 
 Documentation/serial-console.txt
 Documentation/networking/netconsole.txt
 the help entry for "config LP_CONSOLE" (in drivers/char/Kconfig)


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2005-09-04 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-03 20:53 Potential IPSec DoS/Kernel Panic with 2.6.13 Matt LaPlante
2005-09-04  8:23 ` Herbert Xu
2005-09-04 16:38   ` Matt LaPlante
2005-09-04 18:49     ` Jesper Juhl [this message]
2005-09-04 22:42       ` Matt LaPlante
2005-09-04 22:56         ` Jesper Juhl
2005-09-05  0:06           ` Matt LaPlante

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=9a87484905090411492cc3f823@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=laplam@rpi.edu \
    --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