From owner-freebsd-questions@FreeBSD.ORG Sun Aug 10 08:57:15 2014 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6046D67A for ; Sun, 10 Aug 2014 08:57:15 +0000 (UTC) Received: from mail.parts-unknown.org (home.parts-unknown.org [50.250.218.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 42F3629B1 for ; Sun, 10 Aug 2014 08:57:15 +0000 (UTC) Received: from mail.parts-unknown.org (unknown [127.0.0.1]) by mail.parts-unknown.org (Postfix) with ESMTP id 409FD598CDCF; Sun, 10 Aug 2014 01:57:13 -0700 (PDT) Received: by mail.parts-unknown.org (Postfix, from userid 1001) id 3D583598CDCC; Sun, 10 Aug 2014 01:57:11 -0700 (PDT) Date: Sun, 10 Aug 2014 01:57:11 -0700 From: David Benfell To: Polytropon Subject: Re: operation not permitted on entropy file Message-ID: <20140810085710.GB59380@home.parts-unknown.org> References: <20140810070239.GA80734@home.parts-unknown.org> <53E72634.5050608@FreeBSD.org> <20140810083440.GA59380@home.parts-unknown.org> <20140810104523.5ccdaf6f.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="24zk1gE8NUlDmwG9" Content-Disposition: inline In-Reply-To: <20140810104523.5ccdaf6f.freebsd@edvax.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-Virus-Scanned: ClamAV using ClamSMTP on home.parts-unknown.org Cc: freebsd-questions@FreeBSD.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2014 08:57:15 -0000 --24zk1gE8NUlDmwG9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 10, 2014 at 10:45:23AM +0200, Polytropon wrote: >=20 > Those could be side-effects on the file system that were caused > by the dfective RAM module. That's why the suggestion to forcedly > check the integrity of all file systems is a very good advice. Fortunately, there's only one. > Examination of the hardware is also a thing worth looking into, > for example, voltages, temperatures, and CPU "correctness". I'm wondering how to do this. The system does have an SMBus, but the smb module doesn't create /dev/smb0 and the tool--I'm forgetting the command name--that will identify the hardware on a system suggests that it's too recent a version to be fully accurate with. Thanks! --=20 David Benfell See https://parts-unknown.org/node/2 if you don't understand the attachment. --24zk1gE8NUlDmwG9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJT5zPlAAoJEBV64x4SNmArBOIP+wcyBy6AtyPjrEHBshLzEqjf pELKzoDQcch/ToYVOreX1ddYY8HPY5IlvGjE2KBGm9JhSUQBwoHC+29AQL53OrYo NeQuyb9RV5UemRH0k0hEVjGOlIZytXowHVRlu4+V6oTofexA1P6ODO/TjqpWujdu tHA6vOC8PyS4Txh70+7ib+w8Vhq3zmW5OhqkmxLSvMFeqYqrVG+hbAmBn2bKDw5e LoLmfEB0/wgVUtxv51ZORsvBrh+VgEAMbKk6IDGmrGfZwr7AWBmEZa9VeTFaOyre n8pm1Pmpepr+84cwQPlfsZHn0y8+jI2e79FlYBKX8RXC5bCjGKRgvPfhHlP32Nos E4HMtc9b/5tgZ0ckyJD/sxtuzIokaSxhrIxHOst73eFQjZHn7qpuzdeED+gXuCVb ugwOSH7p59vmuFJ6olr72Yz1B3SESuykpfd5e8hywV2fxFpk11U67Zhlo4ajXzSt PwNXltbSRfQ7AUa0XX7sXtDAG3A/jU4TCMak7WwTql+Ltx+p7N0pTXirghigQxid ecXsfzH8J8vizovT9zKnBJLavZ6DQbBw/a47/jfVyYsdvBnU7Dq7PQK+WU0jEB5i uNZtnPJIxKsvmYE3A2jWuiWJeIUOUDihskdBpf8AfG9fofTxLxrAIQcaRwXMoJpu rxd1jadRC4a6SHAlpWwO =ZjTT -----END PGP SIGNATURE----- --24zk1gE8NUlDmwG9--