public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Vanoni <vanonim@bluewin.ch>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 2.4.26: first crash 100%, NFS?
Date: Thu, 06 May 2004 21:04:31 +0200	[thread overview]
Message-ID: <409A8C3F.5080005@bluewin.ch> (raw)

8 machines running 2.4.26, >=19 days uptime.

P4HT3400, ASUS P4R800-V deluxe,
1GB memory, 1GB swap, 80GB IDE disk,
on-board 100Mb/s LAN.

- downloaded the last KNOPPIX...en
- 2 setitathome -nice 19 running

- mounted from another machine (UP P3-550)
- from P3-550 machine cp -a KNOPPIX...en
- after about 367MB of ~700MB ...
   P4HT3400 machine dead, message on console:

   Kernel panic: Aiee, killing interrupt handler!
   In interrupt handler -not syncing.

   Power switch ultima ratio, following fsck.

- the console on P3-550 was logged _out_.

No time for deeper researches, sorry,
kernel compiled -static with gcc-3.3.2,
no modules, without all lkml helps wanted.

_Feedback_ _only_ !!!

Kind regards

Mario, _not_ _in_ _lkml_.


             reply	other threads:[~2004-05-06 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 19:04 Mario Vanoni [this message]
2004-05-07 13:42 ` 2.4.26: first crash 100%, NFS? Marcelo Tosatti

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=409A8C3F.5080005@bluewin.ch \
    --to=vanonim@bluewin.ch \
    --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