From: "Ahna, Christopher J" <christopher.j.ahna@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] uni-processor kernel on SMP machine
Date: Wed, 18 Oct 2000 19:30:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205593@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205576@msgid-missing>
Are you using a kernel with ptc.g enabled? A problem similar to the one you
are seeing has shown up B1-based systems running kernels that include ptc.g.
Thanks,
Chris
-----Original Message-----
From: Pat O'Rourke [mailto:orourke@mclinux.com]
Sent: Wednesday, October 18, 2000 6:23 AM
To: Jun Nakajima
Cc: linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] uni-processor kernel on SMP machine
> Both UP and SMP kernels (2.4.0-test9) work fine on at least two 4-way
> Lions (A2-stepping CPUs each with latest and a bit old firmware) at our
> site. Can you be more specific about the problem you are seeing?
The system appears to hang right after printing "POSIX conformance testing
by UNIFIX", i.e. just before the creation of the init thread. The kernel
is pretty locked up, alt-sysrq doesn't work. I have not really tried to
debug it yet, so that is about all I can say at the moment.
Pat
--
Patrick O'Rourke
orourke@missioncriticallinux.com
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2000-10-18 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-17 16:44 [Linux-ia64] uni-processor kernel on SMP machine Pat O'Rourke
2000-10-17 20:34 ` Jun Nakajima
2000-10-17 21:51 ` Broadfoot, KenX
2000-10-18 13:22 ` Pat O'Rourke
2000-10-18 19:30 ` Ahna, Christopher J [this message]
2000-10-18 19:59 ` Pat O'Rourke
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-105590678205593@msgid-missing \
--to=christopher.j.ahna@intel.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