NetBSD Problem Report #54103

From www@netbsd.org  Sat Apr  6 14:19:25 2019
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id BA4A97A1A4
	for <gnats-bugs@gnats.NetBSD.org>; Sat,  6 Apr 2019 14:19:24 +0000 (UTC)
Message-Id: <20190406141923.C45547A1BD@mollari.NetBSD.org>
Date: Sat,  6 Apr 2019 14:19:23 +0000 (UTC)
From: bernhard@netmuc.net
Reply-To: bernhard@netmuc.net
To: gnats-bugs@NetBSD.org
Subject: "rust never sleeps" wrong on one of my machines
X-Send-Pr-Version: www-1.0

>Number:         54103
>Category:       pkg
>Synopsis:       "rust never sleeps" wrong on one of my machines
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 06 14:20:00 +0000 2019
>Closed-Date:    Fri May 22 23:13:59 +0000 2020
>Last-Modified:  Fri May 22 23:13:59 +0000 2020
>Originator:     Bernhard Riedel
>Release:        NetBSD-8.99.36/amd64 as of April 4, pkgsrc-2019Q1
>Organization:
>Environment:
NetBSD tja.crg.de 8.99.36 NetBSD 8.99.36 (GENERIC) #0: Wed Apr  3 18:57:32 CEST 2019  root@wip.crg.de:/sdata/test-current-20190403000000Z/obj/amd64/sys/arch/amd64/compile/GENERIC amd64

>Description:
Hi,

when building pkgsrc/lang/rust on one of my machines, I could observe
 long pauses with load = 0.00, 0.00, 0.00 and rustc waiting:

  PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
 3535 root      85    0   244M   71M 3535 7/9   0:00  0.00%  0.00% rustc

This could go on for quite some time, but I stumbled over a workaround.
Typing a few characters in an unused console or sshing in a few times
 would end rustc's siesta.

Suspicion: rustc could be hungry for entropy and maybe uses /dev/random
 instead of /dev/urandom.

Why am *I* seeing this? That box doesn't have any sdN or wdN, only an ld0
 attached to nvme, and there is no mouse attached either.
As confirmed by 'rndctl -l', nvme/ld0 aren't used as entropy sources.

Cheers, Bernhard Riedel.

>How-To-Repeat:
See above. When trying to repeat, the pauses don't always happen for the same source files.
>Fix:

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: nia@NetBSD.org
State-Changed-When: Sun, 07 Jul 2019 15:37:38 +0000
State-Changed-Why:
Should be fixed as of rust-1.35.0nb1 due to tnn's commit:
http://mail-index.netbsd.org/pkgsrc-changes/2019/06/13/msg193003.html


State-Changed-From-To: feedback->closed
State-Changed-By: maya@NetBSD.org
State-Changed-When: Fri, 22 May 2020 23:13:59 +0000
State-Changed-Why:
Closing as it's "double fixed". Even if rust had been reading /dev/random, the entropy depletion mechanism is gone as part of Riastradh's entropy rework, so it's not expected to block very many times. 


>Unformatted:

Home	PR Database Search