From: kd@flaga.is
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: MBX (MPC860) Question
Date: Sat, 15 May 1999 00:15:31 +0000 [thread overview]
Message-ID: <00256772.00016CF9.00@notes.flaga.is> (raw)
Hello again,
The solution for me was to unplug the hardwaredebugger. Then all page
faults stopped and everything
seems to be working.
A nice side effect is that the hardware seems to be runniing at least 3-4
times faster than with the dam thing connected. 8-)
K.D.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next reply other threads:[~1999-05-15 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-15 0:15 kd [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-05-14 23:55 MBX (MPC860) Question KiPyo Ryu
1999-05-13 18:51 kd
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=00256772.00016CF9.00@notes.flaga.is \
--to=kd@flaga.is \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).