From: murzin.v@gmail.com (Vladimir Murzin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: power on self test (POST) config option in kernel config
Date: Mon, 27 Jun 2011 13:13:10 +0400 [thread overview]
Message-ID: <BANLkTi=RxUfre+Np-CNXDg=R3bSAwQFvTQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=Jpgrm5rtgCD7kVy0F8PYW6LjQaA@mail.gmail.com>
On Mon, Jun 27, 2011 at 9:57 AM, sri <bskmohan@gmail.com> wrote:
> Hi,
>
> One of my devices runs with Centos 5.3 kernel (kernel-2.6.18-128.el5) and
> that box stops responding occasionally.
> When did hard reboot, it comes to normal execution. I would like to see
> which device failure caused the box to stop rebooting.
> I would like to see the POST process execution (if enabled) during the
> centos kernel boot time.
> Is there any kernel config for POST?
>
> Any suggestions are appreciated.
>
> Thanks,
> --
> --
> ?Krishna Mohan B
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
I am afraid POST is kernel independent feature. Power-On-Self-Test
runs immediately after power applied and, if all went well, invokes
bootstrapping code.
Verbosity of POST is mainly configured into BIOS. Make sure you set up
maximum verbosity level.
To get information about what cause your system not responding it is
better to look up kernel messages. You provide poor information to
make any conclusion or even guessing. Sorry.
When you box is friezed try to invoke "magic keys"
(http://en.wikipedia.org/wiki/Magic_SysRq_key) to collect some
information.
P.S.
Sorry for my English
prev parent reply other threads:[~2011-06-27 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 5:57 power on self test (POST) config option in kernel config sri
2011-06-27 9:13 ` Vladimir Murzin [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='BANLkTi=RxUfre+Np-CNXDg=R3bSAwQFvTQ@mail.gmail.com' \
--to=murzin.v@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).