Hi Nick,
Out of curiosity, are you running a 64-bit kernel (uname -m) ?

Debug is turned on until the production release so pre-release testers can send logfiles to the feedback email address. When reporting mass storage bugs, logfiles of use are:
/var/log/messages
/var/opt/SUNWut/log/utstoraged.log
/var/opt/SUNWut/log/utmountd.log

Thank

-a-


From: "Nick Merrett" <[EMAIL PROTECTED]>
Reply-To: SunRay-Users mailing list <[email protected]>
To: [email protected]
Subject: [SunRay-Users] utdisk under linux
Date: Wed, 19 Jul 2006 09:47:40 +1000

Hi,

After getting the Early Access Release and USB mass storage running
under Linux i have noticed a few bugs.

There seems to be a bad memory leak, before i start a transfer
VmallocUsed only has about 5MB used.

I start a large transfer after a few minutes it will die due to an I/O
error, all disk operations don't seem to work, when i checked Vmalloc:
VmallocTotal:   114680 kB
VmallocUsed:    114628 kB
VmallocChunk:        8 kB

Checking dmesg there are insufficient memory errors etc.

Which
Some memory

Secondly there is a massive amount of debug information that is dumped
into logs from the two modules, i don't know if this is compounding
the memory leak problem or not, but running top while a transfer is
taking place
    utlog is running around 25% cpu,
    syslogd is 8%
    klogd 2%

This is on a P4 3GHz, 1GB Ram.

The kernel in use is 2.6.15-1-686-smp

Another note, libcairo2 1.2 is broken for sunray and many other vnc
type applications, downgrading to 1.0.4 seemed to fix the problem

Regards

Nick
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to