From: "Duane Griffin" <duaneg@dghda.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel crash - howto find out what happened?
Date: Mon, 13 Oct 2008 16:09:24 +0100 [thread overview]
Message-ID: <e9e943910810130809i797b82eew7ec6226488e21737@mail.gmail.com> (raw)
In-Reply-To: <200810121108.57840.alexander.puchmayr@linznet.at>
2008/10/12 Alexander Puchmayr <alexander.puchmayr@linznet.at>:
> MY gentoo system (an amd64@4400+, 2GB ram, nforce4-chipset)
> worked fine for nearly two years, but now it frequently freezes, sometimes
> (not always) scrollock and capslock LED blinking).
If you have another machine lying around, try setting up netconsole
and/or serial console logging. They should catch any dying messages
from your kernel. Blinking LEDs indicates a panic, which means you
should get a message in those cases, at least.
Using serial console is the easiest and most reliable way, but
requires a serial cable. Netconsole just uses ethernet but isn't as
reliable. Take a look at Documentation/serial-console.txt and
Documentation/networking/netconsole.txt under your kernel source
directory for more info.
Cheers,
Duane.
--
"I never could learn to drink that blood and call it wine" - Bob Dylan
next prev parent reply other threads:[~2008-10-13 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 9:08 [gentoo-user] Kernel crash - howto find out what happened? Alexander Puchmayr
2008-10-12 9:16 ` Erik Hahn
2008-10-12 11:12 ` Alexander Puchmayr
2008-10-12 11:35 ` Alan McKinnon
2008-10-12 13:00 ` Alexander Puchmayr
2008-10-13 15:09 ` Duane Griffin [this message]
2008-10-13 23:30 ` Daniel da Veiga
2008-10-14 16:31 ` Alexander Puchmayr
2008-10-14 17:09 ` Alex Schuster
2008-10-19 9:58 ` Alexander Puchmayr
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=e9e943910810130809i797b82eew7ec6226488e21737@mail.gmail.com \
--to=duaneg@dghda.com \
--cc=gentoo-user@lists.gentoo.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