Newsgroups: comp.sys.transputer
From: andyr@teal.csn.org (Andy Rabagliati)
Subject: Re: network booting problem with iserver
Organization: Colorado SuperNet, Inc.
Date: Fri, 21 Oct 1994 19:59:58 GMT
Message-ID: <Cy1Gvz.wn@csn.org>

[ reposted - newsfeed problems. My apologies ]

Henno Tillema <tillema@cs.utwente.nl> wrote:
>
>We have a major problem with the iserver booting a network:
>
>Sometimes when we try to boot our transputer network the iserver
>stops sending the bootfile into the network with the message:
>       Error - iserver - unable to write byte # to the boot link


>a post-mortem inspection with the debugger shows all transputers
>still in an invalid state for the debugger:
>-Iptr in Stack area or in Vectorspace, Wdesc is NotProcess

What state are the links in ?

The root processor undoubtably has a process stuck outputting to links
1,2, or 3.

Follow that link.

Where is that transputer stuck ?

Keep following links until you find a transputer internally deadlocked
(nothing hanging on the links) or in error (error flag set). It might
conceivably be deadlocked outputting up the link it is being booted
from.

Report back what you find. You might just dis-assemble around the Iptr
of the last (suspect) transputer for extra giggles.

Early toolsets (before D7205, I think) had problems with programs with
very small workspaces.

Cheers,       Andy!

 
--
Andy Rabagliati  .  andyr@wizzy.com  .  OCCAM guru  .  +1.719.635.6099


