On Thu, Sep 25, 2014 at 08:13:57AM +0200, Thomas Schwinge wrote: > This testing was done in a QEMU/KVM Hurd system, configured with 1536 GiB > of RAM. Some time after beginning to execute the jc1 command, the system > stops responding, but still consumes 100 % host CPU time. And, if QEMU's > built-in gdbserver is to be believed, it is still doing "something":
You can also use the in-kernel debugger for more information, in particular show all threads, to see if it's a thread storm caused by too many concurrent page cache writebacks. This is the main issue I have when building "large" files (see [1]). -- Richard Braun [1] https://www.sceen.net/iceweasel-31-on-debian-gnuhurd/
