From: w.f.j.mueller@retro11.de (Walter F.J. Mueller)
Subject: [TUHS] 211bsd: kernel panic after a 'here document' in tcsh
Date: Mon, 5 Jun 2017 16:12:47 +0200 [thread overview]
Message-ID: <c5345a44-82e9-7aca-a754-6b09c73e9c44@retro11.de> (raw)
Hi,
I'm using 211bsd (Version 447) and found that a 'here document' in tcsh
leads to a kernel panic. It's absolutely reproducible on my system, both
when run it on my FPGA PDP-11 or in simh. Just doing
tcsh
cat << EOF
is enough, and I get
ka6 31333 aps 147472
pc 161324 ps 30004
ov 4
cpuerr 20
trap type 0
panic: trap
syncing disks... done
looking at the crash dump gives
cd /etc/crash
./why 4
Backtrace:
0147372: _boot(05000,0100) from ~panic+072
0147414: _etext(011350) from ~trap+0350
0147450: ~trap() from call+040
0147516: _psignal(0101520,0160750) from ~trap+0364
0147554: ~trap() from call+040
so the crash is in psignal, which is afaik the kernel internal
mechanism to dispatch signals.
Questions:
1. has anybody seen this before ?
2. any idea what the reason could be ?
With best regards, Walter
next reply other threads:[~2017-06-05 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 14:12 Walter F.J. Mueller [this message]
2017-06-05 16:16 ` Michael Kjörling
2017-06-05 16:33 ` Ron Natalie
2017-06-05 22:08 ` Jacob Ritorto
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=c5345a44-82e9-7aca-a754-6b09c73e9c44@retro11.de \
--to=w.f.j.mueller@retro11.de \
/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).