From: Mahmood Naderan <nt_mahmood@yahoo.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
"\"linux-kernel@vger.kernel.org\"" <linux-kernel@vger.kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: logging on kernel panic
Date: Wed, 13 Jun 2012 07:52:36 -0700 (PDT) [thread overview]
Message-ID: <1339599156.30833.YahooMailNeo@web111716.mail.gq1.yahoo.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1206131552440.6369@twin.jikos.cz>
@jiri:
>and you can get the dmesg+panic from there
Sorry where? in the bios?
@Cong:
>The kernel log may not hit /var/log/syslog when kernel panics,
Can I ask why. Just before a panic, kernel is still alive and can log.
Isn't that?
// Naderan *Mahmood;
----- Original Message -----
From: Jiri Kosina <jkosina@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mahmood Naderan <nt_mahmood@yahoo.com>; "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Sent: Wednesday, June 13, 2012 6:24 PM
Subject: Re: logging on kernel panic
On Wed, 13 Jun 2012, Alan Cox wrote:
> > Hi everybody
> > If a system receives kernel panic during boot, will it be logged somewhere?
>
> Often not.. especially if it is fatal. Look up netconsole however.
Well your machine's BIOS can still be providing non-volatile sotrage which
under recent kernels registers itself with 'pstore', and you can get the
dmesg+panic from there then (provided you have all the necessary bits,
such as APEI, compiled in and enabled).
--
Jiri Kosina
SUSE Labs
--
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/
next prev parent reply other threads:[~2012-06-13 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 12:18 Mahmood Naderan
2012-06-13 12:39 ` Alan Cox
2012-06-13 13:54 ` Jiri Kosina
2012-06-13 14:52 ` Mahmood Naderan [this message]
2012-06-13 15:15 ` Mark Lord
2012-06-14 8:02 ` Jiri Kosina
2012-06-13 13:38 ` Cong Wang
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=1339599156.30833.YahooMailNeo@web111716.mail.gq1.yahoo.com \
--to=nt_mahmood@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®