i've got a panic that appears to be a race in ilock.
but perhaps i'm missing something and it's actually
a h/w problem.
in this situation there are 128 kernel procs that all
increment the same counter with some code
that looks like so:
void
incref(void)
{
ilock(&somelock);
someval
> > I know it's been a while, but that got me farther. The
> > odd thing is that I had already played with the magic
> > define, but it seems that __sun__ wasn't getting set.
>
> Bug in 9c. Fixed and pushed.
Cool.
> Please compare against the BSD sources if you get
> a chance -- I hope I just
> I know it's been a while, but that got me farther. The
> odd thing is that I had already played with the magic
> define, but it seems that __sun__ wasn't getting set.
Bug in 9c. Fixed and pushed.
> - There's also a discrepancy between the V1 inode
> defined in ffs.h and the one defined in the
> That's probably because the stack pointer points at
> the wrong end of the stack. There are some magic
> #defines you can put in that change the meaning of
> ...
> Once you get the thread library working,
> you will probably have to add support for
> the Solaris FS to libdiskfs, unless it is the
> I updated my system today and had trouble with
> the usbfat:, 9fat:, and pull scripts because of errors
> by the new test command.
>
> term% ls /dev/kfs.cmd
> ls: /dev/kfs.cmd: '/dev/kfs.cmd' file does not exist
> term% test -f /dev/kfs.cmd
> term% echo $status
>
>
On Wed, May 28, 2008 at 11:34 AM, Digby Tarvin <[EMAIL PROTECTED]> wrote:
>
> I am interested in connecting more than one graphics adapter so that
> one can be dedicated to low level diagnostics (rather than the more
> usual dual head user interface).. but I am not sure how the hardware
> deals wit
On the subject of diagnostic tools (this is not specifically a Plan9
issue, but someone on this list might know...):
I am interested in connecting more than one graphics adapter so that
one can be dedicated to low level diagnostics (rather than the more
usual dual head user interface).. but I am n
I updated my system today and had trouble with
the usbfat:, 9fat:, and pull scripts because of errors
by the new test command.
term% ls /dev/kfs.cmd
ls: /dev/kfs.cmd: '/dev/kfs.cmd' file does not exist
term% test -f /dev/kfs.cmd
term% echo $status
t
That brings back memories. I think it was Dave Milway who gave
a talk on the BFI at UNSW, where he revealed during question
time at the end that 'BFI' stood for 'Beut Fast Interface'.
Regards,
DigbyT
On Wed, May 28, 2008 at 05:17:07PM +1000, Bruce Ellis wrote:
> I went to that fest, it was an ear
Way back in the dim distant pre-IBMPC days of Z80 PCs, my favourite
debugging technique was to use the screen memory.
My original Exidy Sorcerer had 1920 bytes of character oriented
screen memory (this was when 8K was a respectable amount of main
memory). Each byte displayed a 8x8 character define
> run and get same problem.
Factotum provides a log file that was intended to be
a list of interesting events. While the log file was
implemented, nothing was being logged to it.
I have added log statements tracing the important
events in factotum and p9sk1 in particular.
cd $PLAN9/src/cmd/au
When I did the port to the PS2 there wasn't even a light to blink. To
get thru l.s I discovered a register I could write that resets the
video.
Only a hundred lines (most innocent) to binary chop.
Ken has a better tale of a device that only had a speaker and
debugging by tones.
brucee
On 5/28/0
I went to that fest, it was an early AUUGM.
I think it was the BFI interface team at UNSW.
I'll check the c-side library (I keep everythng).
brucee
On 5/28/08, ron minnich <[EMAIL PROTECTED]> wrote:
> On Tue, May 27, 2008 at 5:16 PM, Bakul Shah <[EMAIL PROTECTED]> wrote:
>
> > Not quite the sam
13 matches
Mail list logo
