public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel crash - howto find out what happened?
Date: Mon, 13 Oct 2008 21:30:30 -0200	[thread overview]
Message-ID: <342e1090810131630v306f6c37v5b2de6e3e0cd5cdc@mail.gmail.com> (raw)
In-Reply-To: <200810121108.57840.alexander.puchmayr@linznet.at>

On Sun, Oct 12, 2008 at 07:08, Alexander Puchmayr
<alexander.puchmayr@linznet.at> wrote:
> Hi there!
>
> 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).
>
> Since I'm using the box as desktop, I have only a frozen X-server and no
> possibility to switch to console (maybe there's some hint whats happened?).
>
> How do I find out what happened, why it crashed? Modern systems have
> MCE-logs, but how do I read it in this case? After reboot, all information
> seems to be gone since mcelog is always empty.
>
> I assume there's some problem with some hardware, I already tested RAM with
> memtest86, but no errors.
>

I had one of this freezes today.
Simply killed X using CTRL+SYSREQ+K and got back a console with error messages.

Have you tried the SYSREQ keys?

-- 
Daniel da Veiga



  parent reply	other threads:[~2008-10-13 23:30 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
2008-10-13 23:30 ` Daniel da Veiga [this message]
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=342e1090810131630v306f6c37v5b2de6e3e0cd5cdc@mail.gmail.com \
    --to=danieldaveiga@gmail.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