From: jacob.ritorto@gmail.com (Jacob Ritorto)
Subject: [TUHS] 211bsd: kernel panic after a 'here document' in tcsh
Date: Mon, 5 Jun 2017 18:08:08 -0400 [thread overview]
Message-ID: <CAHYQbfAgH=iBjQo9NfjwPvyF+iW_k9HmGqoo7f8kafao-qW0Cg@mail.gmail.com> (raw)
In-Reply-To: <014101d2de19$7385e870$5a91b950$@ronnatalie.com>
Nice snipe, Ron! Where might one find the list of trap_types and cpuerrs?
On Mon, Jun 5, 2017 at 12:33 PM, Ron Natalie <ron at ronnatalie.com> wrote:
> Trap type 0 is bus error. The two causes of this are either addressing
> memory location that does not respond (as opposed to being umapped) or an
> word operation on an odd address.
>
> Since you have a cpuerr print out you have a 44/45/70 CPU. The 020 value
> indicates that it was the bus timeout case.
>
> Something touched memory that was mapped in but didn't physically exist.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170605/37b404c5/attachment.html>
next prev parent reply other threads:[~2017-06-05 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 14:12 Walter F.J. Mueller
2017-06-05 16:16 ` Michael Kjörling
2017-06-05 16:33 ` Ron Natalie
2017-06-05 22:08 ` Jacob Ritorto [this message]
2017-06-06 11:43 ` Ron Natalie
2017-06-05 23:05 Noel Chiappa
[not found] <mailman.1.1496714401.14870.tuhs@minnie.tuhs.org>
2017-06-06 19:15 ` Johnny Billquist
2017-06-07 20:14 Walter F.J. Mueller
2017-06-08 7:54 ` Michael Kjörling
[not found] <mailman.884.1496866451.3779.tuhs@minnie.tuhs.org>
2017-06-08 22:29 ` Johnny Billquist
2017-06-10 12:58 Walter F.J. Mueller
2017-06-10 14:24 Noel Chiappa
2017-06-12 15:26 ` Clem Cole
[not found] <mailman.1.1497146402.26080.tuhs@minnie.tuhs.org>
2017-06-11 10:25 ` Johnny Billquist
2017-06-25 16:25 Walter F.J. Mueller
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='CAHYQbfAgH=iBjQo9NfjwPvyF+iW_k9HmGqoo7f8kafao-qW0Cg@mail.gmail.com' \
--to=jacob.ritorto@gmail.com \
/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).