On Thu, 26 Nov 2015, Emile `iMil' Heitor wrote:
If this issue _is_ NFS related, which I doubt now, it is then read-related,
as
the build is done in tmpfs.
Pushing the logic further, I just tried with pkgsrc itself being in tmpfs, and
it froze even faster.
On Thu, Nov 26, 2015 at 07:13:04PM +0100, Emile `iMil' Heitor wrote:
> On Thu, 26 Nov 2015, Manuel Bouyer wrote:
>
> >what does 'show uvm' report ?
>
> db{0}> show uvm
> Current UVM status:
> pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12
> , ncolors=8 7444115 VM pages: 53990 active, 180
On Thu, 26 Nov 2015, Manuel Bouyer wrote:
what does 'show uvm' report ?
db{0}> show uvm
Current UVM status:
pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12
, ncolors=8 7444115 VM pages: 53990 active, 1807 inactive, 1 wired, 7302474 fre
e
pages 26626 anon, 25029 file, 4143 exec
fre
On 26 Nov 2015, at 17:22, Emile `iMil' Heitor wrote:
>
> 242691 3 14 0 a0003f446a80cat nfsrcv
> 1868 1 3 15 0 a0003dca59c0 getty nfsrcv
> 2354 1 3 5 0 a0003ed51b00 cron nfsrcv
>
> 2086 1 3
On Thu, Nov 26, 2015 at 05:22:16PM +0100, Emile `iMil' Heitor wrote:
> On Thu, 26 Nov 2015, Emile `iMil' Heitor wrote:
>
> >Again, as there's no log at all, what would help debugging this behaviour?
>
> FWIW, some ddb output (ddb is triggered by hitting + on domU's console):
what does 'show
On Thu, Nov 26, 2015 at 03:55:27PM +0100, Emile `iMil' Heitor wrote:
> [...]
> Again, as there's no log at all, what would help debugging this behaviour?
Can you enter ddb on the console (on a PV domU this is with '+++',
not break which doesn't exists for xl console)
--
Manuel Bouyer
N
On Thu, 26 Nov 2015, Emile `iMil' Heitor wrote:
Again, as there's no log at all, what would help debugging this behaviour?
FWIW, some ddb output (ddb is triggered by hitting + on domU's console):
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip 8012e5ad cs e030 rfla
On Mon, 2 Nov 2015, Emile `iMil' Heitor wrote:
I'm trying to get rid of those hangs for weeks now, tried every mount flag
combination without success, the system would freeze randomly, leaving the
whole
OS unresponsive. There's no log, no kernel message, the domU actually
responds
to network