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 <[email protected]> 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 > 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
