From: "Miller, Mike (OS Dev)" <Mike.Miller@COMPAQ.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] System hang
Date: Tue, 15 May 2001 19:00:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005584@msgid-missing> (raw)
Sorry if this not the right forum for this problem.
I have encountered a system hang when running heavy I/O. It only occurs when
running MP and >4GB RAM. I have seen this under the 2.4.3 and 2.4.4 kernels.
Current setup is 2.4.4 with the 010508 ia64 diff patch and kdb applied. The
system has 2 C0 processors and 8GB of memory. The test is very simple, just
using cpio -p to copy files. It causes a machine check within 5 minutes that
locks up the boot strap processor. We've looked at HW and cannot pinpoint a
HW failure. This has been reproduced on several different systems including
one with B3 processors.
After stripping out all the extraneous drivers from the kernel including
USB, storage drivers not in use, WAN, etc. the problem has gone away. I am
now trying to add drivers back one at a time to isolate the problem w/o any
luck so far.
Has anyone else observed a similiar hang? The outward symptoms are all I/O
stops and the keyboard does not respond. The system must be power cycled.
Thanks,
mikem
reply other threads:[~2001-05-15 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590693005584@msgid-missing \
--to=mike.miller@compaq.com \
--cc=linux-ia64@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