DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=AXn/FRqBm1r/ErMsN9bS+dWh2syQvMqH6IHLosyWZPwm7qtT53kLcfgjVxJlq0c3UHMSDOgCMH+XgzBnDgRJdcEv9ARwXBpji9dI6w9/26mFi1qs0LYlbCk9vp3RQ3jf1juavmM/uAA4eVNfbaZ+A/IU+0HOGNqby4nZzXJsNbc=
Message-ID: <67029b17050901192933f9618@mail.gmail.com>
Date: Fri, 2 Sep 2005 10:29:12 +0800
From: Zhou Yingchao <yingchao.zhou@gmail.com>
Reply-To: yingchao.zhou@gmail.com
To: "liyu@WAN" <liyu@ccoss.com.cn>
Subject: Re: [Q] how to use syslogd to debug kernel ?
Cc: LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <4317B309.3000404@ccoss.com.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <4317B309.3000404@ccoss.com.cn>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 792
Lines: 21

On 9/2/05, liyu@WAN <liyu@ccoss.com.cn> wrote:
> Hi, everyone.
> 
>    I know kernel oops can be seen by run 'dmesg', but if
> kernel crashed, we can not run it.   so I reconfigure syslogd
> to support remote forward, the debug machine content of
> syslogd.conf is:

When the panic is called, the network system cannt working, no
message will be sent. The panic is only designed to print at least
 oops message on the screen. 
For debug through ethernet, I suggest you to try KGDB, which consist
a patch to debug over ethernet. 

-- 
Yingchao Zhou
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/