From: "shaun" <mailinglists@unix-scripts.com>
To: linux-kernel@vger.kernel.org
Subject: kernel panic - not syncing: Fatal exception in interupt
Date: Tue, 5 Apr 2005 23:04:11 -0700 [thread overview]
Message-ID: <d2vu0u$oog$1@sea.gmane.org> (raw)
+Hardware Specs
Dual Xeon 800FSB
Intel Server Board
4GB ECC DDR
3ware 9500 Sata Raid Card
5x200 GB sata drives in a raid 10 Config (1 hot spare)
Dual Nic
+OS Specs
CentOS 3.4 running a custom 2.6.x kernel patched with UML SKA's Patch
eth0 is 0.0.0.0 promisc and assigned to a bridge (br0)
tuntap devices up
ebtables is enabled and loaded with rules
My problem is that every other week or so the machine crashes. It never
dumps the error to the logs so all i have is a screen shot of the console.
I have put some serious stress on this machine and have been unable to
duplicate the problem (running 20 guest UML's half running va-ctcs and the
other half compiling a 2.6 kernel). Below is a link to 2 screen shots i
have (about 2 weeks apart). I started off using a 2.6.10 kernel when the
problem started. Last time the machine crashed i built a 2.6.11.5 kernel
and disabled APM and ACPI in the kernel config. Any body know whats going
on here.
http://www.unix-scripts.com/shaun/host-screenshot-1.png
http://www.unix-scripts.com/shaun/host-screenshot-2.png
Kernel Config... http://www.unix-scripts.com/shaun/2.6.11.5-hr1_.config
--
Best Regards,
Shaun Reitan
next reply other threads:[~2005-04-06 6:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 6:04 shaun [this message]
2005-04-06 8:10 ` kernel panic - not syncing: Fatal exception in interupt Zwane Mwaikambo
2005-04-06 21:00 ` mailinglist@unix-scripts.com
2005-04-07 8:09 ` Zwane Mwaikambo
2005-04-07 19:57 ` mailinglist@unix-scripts.com
2005-04-12 8:43 ` mailinglist@unix-scripts.com
2005-04-12 12:19 ` Zwane Mwaikambo
2005-04-17 20:32 ` Shaun Reitan
2005-04-18 6:07 ` Herbert Xu
2005-04-18 6:25 ` Shaun Reitan
2005-04-22 7:40 ` Shaun Reitan
2005-05-12 4:26 ` [stable] " Greg KH
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='d2vu0u$oog$1@sea.gmane.org' \
--to=mailinglists@unix-scripts.com \
--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