mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dimitri Chausson <tri2000@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: linux troubleshooting help
Date: Sun, 13 Aug 2006 12:49:12 +0200	[thread overview]
Message-ID: <20060813124912.6b7b83b9.tri2000@gmx.net> (raw)

Hi all,

since about 1 week, I am experiencing system crashes. I tried kernel versions 2.6.15 and 2.6.16 but it occurs in both. I first thougth it was X related (so not a kernel problem), but the machine is not reachable via network. All logs I list below were obtained with a 2.6.15-1-k7 kernel (debian):

1- When booting, contains:
-------- output------------
Stack:...
Call Trace:...
========================
Unable to handle kernel NULL pointer dereference at virtual address 00000006
printing eip:
c01037ba
*pde = 00000000
Recursive die() failure, output supressed
<0> Kernel panic - not syncing: Fatal exception in interrupt
-------- output------------

2- Running on a terminal (no X running):
-------- output------------
CPU 0: Machine Check Exception: 0000000000000004
Bank 1: ......... at ...........
Kernel panic - not syncing: CPU context corrupt
-------- output------------


And there were other similar crashes. It crashes really often (several times a day, while the computer is not running the whole day). 
Since I did not add any hardware, I thought some hardware may be dying... but is there a way to know what ? Until now I ran a memtest86, and I checked the hard disk with smartmontools. Both went well...

I do not know how to proceed now, and I would appreciate any hint or help on how to further isolate the problem,

thanks for your time,

Dimitri 

PS: of course, I can provide you with more details if necessary

             reply	other threads:[~2006-08-13 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13 10:49 Dimitri Chausson [this message]
2006-08-14  9:34 ` Alex Riesen

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=20060813124912.6b7b83b9.tri2000@gmx.net \
    --to=tri2000@gmx.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®