RE: Merchant loader texture problems

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++reading.sgi.com)
Thu, 9 Sep 1999 16:57:21 +0100

KONA_DMAWRITE could be caused by several things, I would suggest this
customer speaks to SGI support first so they can sanity check the HW and
also the level of patches/OS installed before thinking about chasing an
application problem.

Cheers
Rob

-----Original Message-----
From: Bryan Housel [mailto:bryan++at++drawcomp.com]
Sent: 09 September 1999 16:08
To: info-performer++at++sgi.com
Subject: Re: Merchant loader texture problems

One of our customers is having the following problem.. Any idea what the
KONA_DMAWRITE message means, and why the child process might be getting
killed?

Thanks,
Bryan

Roland Holm wrote:
>
> Hi Bryan,
>
> loading spindel.wrl with a correctly sized texture works. Well, at least
> perfly does not crash. But the object is black - there are no textures.
> Every textured object appears black (even though it's actually white
> material).
>
> Loading test.wrl or other complex models still causes perfly to crash.
> I always get the following (or a similar) message:
>
> PF
> PF Info: pfuRunProcOn() - Process 73595 running on
> CPU 0.
> PF Info: pfuDownloadTexList texture processing
> PF Loading texture:
> PF File name =
> x00000+ImageTexture_10
> PF Image size (SxTxR) = 256x256x1
> KONA_DMAWRITE: Bad address
> PF Notice: Using 72Hz video rate.
> PF Notice: Caught SIGCHLD. Exiting due to death of
> child with pid 69704.

-- 
DRaW Computing Associates, Inc.    http://www.drawcomp.com
OpenWorlds VRML C++ toolkit        http://www.openworlds.com
-----------------------------------------------------------------------
List Archives, FAQ, FTP:  http://www.sgi.com/software/performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Thu Sep 09 1999 - 08:57:43 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.