From: Matt Mackall <mpm@selenic.com>
To: Park Lee <parklee_sel@yahoo.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: What's the matter with build-in netconsole?
Date: Thu, 16 Dec 2004 10:44:38 -0800 [thread overview]
Message-ID: <20041216184438.GH2767@waste.org> (raw)
In-Reply-To: <20041216143537.41770.qmail@web51502.mail.yahoo.com>
On Thu, Dec 16, 2004 at 06:35:37AM -0800, Park Lee wrote:
> Hi,
> I try to use netconsole to keep Linux kernel oops to
> another machine. I've compiled netconsole into the
> kernel (i.e. select CONFIG_NETCONSOLE=y, when run
> 'make menuconfig').
> After that, I put
> "netconsole=@/,514@192.168.0.1/00:02:3F:03:D2:59"
> (which is described in
> /usr/src/linux/Documentation/networking/netconsole.txt)
You have to configure a source IP address for built-in netconsole, as
interfaces normally don't have addresses assigned to them until init.
> to the kernel command line as provided by grub and
> rerun my machine with the new compiled kernel.
> But then, when the system is booting, it shows the
> following message:
>
> ... ...
> Uncompressing Linux... Ok, booting the kernel.
> audit(1103234064.4294965842:0): initialized
> netconsole: eth0 doesn't exist, aborting.
> ... ...
>
> Then, What's the matter with the build-in
> netconsole? Have I misconfiged the netconsole? and How
> to really run build-in netconsole?
Is your network driver built in? Is it eth0 (you let netconsole use
the default)? Is it initialized before netconsole? Please send your
_entire_ dmesg.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2004-12-16 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 14:35 What's the matter with build-in netconsole? Park Lee
2004-12-16 15:00 ` Paulo Marques
2004-12-16 18:48 ` Issue on netconsole vs. Linux kernel oops Park Lee
2004-12-16 18:55 ` Matt Mackall
2004-12-16 19:06 ` linux-os
2004-12-16 19:31 ` Park Lee
2004-12-16 18:44 ` Matt Mackall [this message]
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=20041216184438.GH2767@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=parklee_sel@yahoo.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