[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201404022116.HIB82683.FOJMFFHVStOLOQ@I-love.SAKURA.ne.jp>
Date: Wed, 2 Apr 2014 21:16:56 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: struan.bartlett@...il.com, mpm@...enic.com
Cc: linux-kernel@...r.kernel.org, schwab@...ux-m68k.org,
netdev@...r.kernel.org, davem@...emloft.net, nikolay@...hat.com,
andy.shevchenko@...il.com, gregkh@...uxfoundation.org,
jiri@...nulli.us, joe@...ches.com, alonid@...tram.com
Subject: Re: [PATCH v2] netconsole: Add tty driver
Struan Bartlett wrote:
> Adds tty driver to netconsole module. When module is loaded,
> creates /dev/netcon0 device and enables support for console=netcon0
> kernel cmdline option, causing /dev/console output to be sent to
> /dev/netcon0. This allows startup/shutdown script output from
> headless platforms to be logged over (secure) network.
Excuse me, but I think that the netconsole logging can work only during network
interfaces (e.g. eth0) are up. Did this patch description assume that the
network interfaces are up before the startup script is started and the shutdown
script is finished before the network interfaces are down?
By the way, I uploaded a logger specialized for receiving netconsole messages
to http://sourceforge.jp/projects/akari/scm/svn/tree/head/branches/udplogger/ .
The shortage of netconsole approach compared to serial console approach is that
the netconsole logging cannot work if the network interfaces are down. If we
could log kernel messages via the netconsole module while initializing kdump
kernel by adding console=netcon0 to kdump kernel's command line, we can utilize
netconsole as an alternative tool for logging kernel messages in case
initialization of kdump kernel fails.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists