From nobody Tue Oct 12 08:43:45 2021
X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 901CD17F8535;
	Tue, 12 Oct 2021 08:44:04 +0000 (UTC)
	(envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4HT8N439m4z3Q3x;
	Tue, 12 Oct 2021 08:44:04 +0000 (UTC)
	(envelope-from hps@selasky.org)
Received: from hps2020.home.selasky.org (unknown [178.17.145.105])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by mail.turbocat.net (Postfix) with ESMTPSA id 6C2FA260245;
	Tue, 12 Oct 2021 10:43:57 +0200 (CEST)
Subject: Re: After updating main (so: 14) Orange Pi+ 2E panicked:
 ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command
 after login
To: marklmi@yahoo.com, Free BSD <freebsd-arm@freebsd.org>,
 freebsd-current <freebsd-current@freebsd.org>
References: <ADD31C61-F8AF-4FBF-B29D-5E79FB2DE8C1.ref@yahoo.com>
 <ADD31C61-F8AF-4FBF-B29D-5E79FB2DE8C1@yahoo.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <e0f6e7e4-197c-034f-dec4-ba6306cd24ac@selasky.org>
Date: Tue, 12 Oct 2021 10:43:45 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
List-Id: Porting FreeBSD to ARM processors <freebsd-arm.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-arm
List-Help: <mailto:freebsd-arm+help@freebsd.org>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Subscribe: <mailto:freebsd-arm+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-arm+unsubscribe@freebsd.org>
Sender: owner-freebsd-arm@freebsd.org
MIME-Version: 1.0
In-Reply-To: <ADD31C61-F8AF-4FBF-B29D-5E79FB2DE8C1@yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4HT8N439m4z3Q3x
X-Spamd-Bar: ----
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-4.00 / 15.00];
	 REPLY(-4.00)[]
X-Spam: Yes
X-ThisMailContainsUnwantedMimeParts: N

On 10/12/21 3:11 AM, Mark Millard via freebsd-arm wrote:
> There is this "mixer" oddity for each boot:
> 
> Feeding entropy: .
> mixer: 75:75: no such device
> mixer: 75:75: no such device
> mixer: 75:75: no such device
> mixer: 25:25: no such device
> mixer: 75:75: no such device
> mixer: 75:75: no such device
> mixer: =rec: no such device
> lo0: link state changed to UP
> 
> (in case that matters for some reason).

Hi,

Add this script to /etc/rc.d/ and you'll be fine from now on.
https://cgit.freebsd.org/src/tree/libexec/rc/rc.d/mixer

Then run:
service mixer stop && service mixer start

And the problem should go away.

See "git: 903873ce1560 - main - Implement and use new mixer(3) library 
for FreeBSD"

--HPS