From: Chris McDermott <lcm@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Hard "hangs" with 2.4.16
Date: Mon, 10 Dec 2001 20:46:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805665@msgid-missing> (raw)
Anybody else been seeing hangs with 2.4.16+ia64-1128.diff?
I'm running on 4x Lions, some with B3's and some with C0's.
The BIOS revision is 83B. I have seen the hang on at least
4 of the systems. This is a hard hang, no kb interrupts, so
kdb doesn't help. I don't have much to go on yet. The hangs
occur in random places, sometimes at various places during
boot and sometimes after the system has been up for a few
minutes. I put an ITP (American Arium) on one of the failing
systems and it didn't fail. Stayed up all night. I moved the
ITP to another failing system and was able to catch 1
occurrence of a "hang". I'm still trying to characterize this
hang to determine whether this is the same thing I am seeing
on the other systems or just a hardware (configuration) problem.
What I saw from the ITP was that all of the processors had
apparently reset (all of their IPs had returned to the reset
vector, 0x80000000FFFFFF90 (I did have the ITP set to break on
reset, but it didn't trigger). Not much else to go on, since I
couldn't even dump any useful processor context.
Anyone else seeing this sort of odd behavior with 2.4.16 on
Intel Lion SDVs?
Thanks,
Chris McDermott
next reply other threads:[~2001-12-10 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 20:46 Chris McDermott [this message]
2001-12-10 21:06 ` [Linux-ia64] Hard "hangs" with 2.4.16 Jack Steiner
2001-12-10 21:19 ` Andreas Schwab
2001-12-10 21:21 ` Chris McDermott
2001-12-10 22:49 ` Chris McDermott
2001-12-11 0:00 ` David Mosberger
2001-12-11 0:01 ` David Mosberger
2001-12-11 19:15 ` Chris McDermott
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-105590698805665@msgid-missing \
--to=lcm@us.ibm.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