9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steven Stallion <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] rdbfs(4) woes
Date: Tue, 28 Aug 2012 19:07:13 -0700	[thread overview]
Message-ID: <CAGGHmKEo1Fv=oK-MRW8dUgCVhmDpnh53-8xNdnTmvFu=_2tvTg@mail.gmail.com> (raw)

9fans,

I dusted off rdbfs(4) today to dig into a kernel issue and ended up
running into what looks like the same issue bwc reported back in 2005:

barstow% import cons /mnt/consoles
barstow% rdbfs -d -t /386/9pccpu /mnt/consoles/target
attach /mnt/consoles/target
barstow% acid -k 1 /386/9pccpu
/386/9pccpu:386 plan 9 boot image
/sys/lib/acid/port
/sys/lib/acid/386
acid: lstk()
got Tread tag 1190 fid 768 offset 56 count 4: here
goes...r00000038...error interrupted
r00000038...error interrupted
r00000038...error interrupted
r00000038...error interrupted
r00000038...error interrupted

Other relevant bits of info:

barstow% 9fat:
barstow% grep console'=' /n/9/plan9.ini
console=0

barstow% import cons /lib/ndb /n/cons
barstow% ndb/query -f /n/cons/consoledb console target
console=target port=7 dev=/dev/eia8

barstow% import cons '#t' /n/t
barstow% cat /n/t/eia8status
b9600 c0 d1 e0 l8 m0 pn r1 s1 i0
dev(8) type(0) framing(4) overruns(0) berr(0) serr(0) cts dsr

All of this was done post ^t ^t D on the target's console.

Any ideas?

Steve



             reply	other threads:[~2012-08-29  2:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  2:07 Steven Stallion [this message]
2012-09-02 18:49 ` Steven Stallion
2012-09-03  6:57   ` Rudolf Sykora
2012-09-03 10:49     ` hiro
     [not found] ` <CAGGHmKGQBSEy18C_4rHkaP5qN_bGwkq2Kr9NmLSURHWCeyYiPA@mail.gmail.c>
2012-09-03 14:18   ` erik quanstrom

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='CAGGHmKEo1Fv=oK-MRW8dUgCVhmDpnh53-8xNdnTmvFu=_2tvTg@mail.gmail.com' \
    --to=sstallion@gmail.com \
    --cc=9fans@9fans.net \
    /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).