From: Frederik Dannemare <frederik@dannemare.net>
To: Richard Whittaker <rwhittaker@northwestel.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.8 SegFaulting...
Date: Sat, 4 Sep 2004 15:52:28 +0200 [thread overview]
Message-ID: <200409041552.29448.frederik@dannemare.net> (raw)
In-Reply-To: <4137FC68.3010404@northwestel.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 03 September 2004 07:08, Richard Whittaker wrote:
> Hiya..
>
> We have a Proliant DL360 G3 running Linux 2.6.8. This machine has two
> CPUs, 3GB of memory, a pair of 146GB disks on the SmartArray 5i
> contoller, a QL2314 Fibrechannel card, and is using abou 60GB on an
> HP VA7400 via the Fibrechannel card. Under 2.6.6 and 1GB of memory
> this machine had run for 4 months without even a hiccup... As of
> yesterday, I added the space on the VA, and moved our MRTG monitoring
> system to the machine. Our MRTG currently monitors about 300
> different elements, and is pretty I/O intensive. The website that the
> MRTG graphs are being written to is on the VA.
>
> This machine crashed and burned in spectacular fashion last night for
> the first time in 4 months, and I was really suprised. The machine
> SegFaulted, but I couldn't get a capture of the stack spew... I had
> to power the machine off, and restart it this morning. The machine
> ran for about 4 hours, then SegFaulted again... I was able to at
> least see the Segfault info, and it was saying something about
> swapper. Power cycled, and about 5 hours later, Segfaulted again, but
> this time I was able to capture the DMESG output... I thought it
> might have been the software RAID device I'd made out of the two LUNS
> on the VA, but after wiping the LUNS out, and rebuilding them, and
> moving to LVM with striping the problem still persists.
>
> Everything in this Kernel is statically linked, and everything is
> stock, right from ftp.kernel.org...
>
> Now, I have a feeling that this has something to do with the I/O that
> I'm loading on the QLogic controller, but can't be absolutely
> certain... I pose the question here for perusal by the experts, and
> hopefully some suggestions about what I should look at, or do next...
[snip]
Can you rule out bad memory (try memtest86+ for 10-20 hours)? Or could
it be heat? Bad mem and heat problems have been the source of almost
all crashes I've witnessed.
- --
Frederik Dannemare | mailto:frederik@dannemare.net
http://qa.debian.org/developer.php?login=Frederik+Dannemare
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBOcicLSX61ZxOtagRAqyNAKCIlPOdU5Je7NSerF2NcD4qxNzlUQCgi1o2
plUHzPPGixdMT5ULZayszgQ=
=VvlJ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-09-04 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 5:08 Richard Whittaker
2004-09-04 13:52 ` Frederik Dannemare [this message]
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=200409041552.29448.frederik@dannemare.net \
--to=frederik@dannemare.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhittaker@northwestel.ca \
/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®