radoslav hodnicak <rh at 4096.sk> wrote:
> I have no clue what's happening. There doesn't seem to be anything in 
> RWBinaryOrTextStream>next: that could loop or deadlock. The only change 
> between the old system (running fine) and this one is a minor OS upgrade 
> (kernel 2.6.x to 2.6.y)


I have had some hanging problems using 2.6.x kernels and larger images. 
I can avoid the problem by starting Squeak with "-memory 300m" and thus
avoiding the use of the mmap-based memory allocator.  It's not a real
fix, but it suffices to keep chugging along.

Also, be aware that there is an "experimental" 3.8 VM available for
Unix.  I am using that and it seems to be fine.  It is also the one I
package in the unofficial Debian repository.

Lex