From: Matt R Hall <mhcomputing@gmail.com>
To: sparclinux@vger.kernel.org
Subject: I'm glad I'm not the only one who noticed SMP Hard Lock issues...
Date: Tue, 21 Sep 2004 19:15:23 +0000 [thread overview]
Message-ID: <703d4eaa0409211215625c27a8@mail.gmail.com> (raw)
It's good to hear that other people are grappling with the same
problem. I'm hoping other people with the same problem and more skills
with hardware than I have can help with this.
Thanks for all of your informational replies.
reply other threads:[~2004-09-21 19:15 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=703d4eaa0409211215625c27a8@mail.gmail.com \
--to=mhcomputing@gmail.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.