Re: [9fans] rdbfs(4) woes

[erik quanstrom <quanstro@quanstro.net>]

On Sun Sep  2 14:52:18 EDT 2012, sstallion@gmail.com wrote:
> Bump, though admittedly this is not as much fan as complaining about
> rc's shortcomings.
>
> On Tue, Aug 28, 2012 at 7:07 PM, Steven Stallion <sstallion@gmail.com> wrote:
> > 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

i've never used rdb.  on quick inspection, it looks like
you're going to have to set consuart = nil in talkrdb().
but that's just a guess.  obviously rdb appears a one-way
trip.

other than that, i've only got trite ideas.  personally,
i would ratrace acid and rdbfs (from another window), and see exactly
what system calls are generating which notes.

you may also wish to temporarly remove consolefs from
the mix, and use stk() or a simplier command like regs()
or *PC instead of lstk().  but again, sorry for the trite
advice.

good luck.

- erik