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: Mon, 5 Sep 2005 00:56:40 +0200 [thread overview]
Message-ID: <9a8748490509041556771499f5@mail.gmail.com> (raw)
In-Reply-To: <200509042242.j84MgYWg019419@ms-smtp-01-eri0.southeast.rr.com>
On 9/5/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 Jesper Juhl
> > Sent: Sunday, September 04, 2005 2:49 PM
> > To: Matt LaPlante
> > Cc: Herbert Xu; linux-kernel@vger.kernel.org
> > Subject: Re: Potential IPSec DoS/Kernel Panic with 2.6.13
> >
> > >
> > 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)
> >
>
> Well I've tried for several hours now to get netconsole working, but it just
> won't give me output. I've tried using both built in as well as module, and
> I've tried two different clients using both netcat and syslogd on different
> ports. The most output I ever get is when loading the module I manage to
> receive one message saying "netconsole: network logging started". I've
> verified all the netconsole settings are correct in the kernel logs when it
> loads. I'm not one to give up easily, but this one's got me stumped.
>
> I know the option to use a printer is out...I might be able to manage a
> serial connection, but I'll have to rebuild my kernel to support it. I'll
> look into that later...
>
Hmm, just a guess; since your bug kills networking I'd suspect that
perhaps netconsole is not the best option. Serial console or printer
(if you have one obviously) would probably be better options.
If you can't get netconsole to work even for stuff prior to triggering
the oops, then that's a bit odd. Perhaps if you posted a description
of exactely what it is you are doing someone could point out the
error... Personally I haven't used netconsole for quite a while, so
my memory of how to set it up is a bit rusty, but I don't recall it
being /that/ tricky.
--
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
next prev parent reply other threads:[~2005-09-04 22:56 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
2005-09-04 22:42 ` Matt LaPlante
2005-09-04 22:56 ` Jesper Juhl [this message]
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=9a8748490509041556771499f5@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