From owner-freebsd-arm@freebsd.org Sun May 21 16:42:46 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C585BD775BC for ; Sun, 21 May 2017 16:42:46 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-9.reflexion.net [208.70.210.9]) (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 834301946 for ; Sun, 21 May 2017 16:42:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 28287 invoked from network); 21 May 2017 16:42:39 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 21 May 2017 16:42:39 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Sun, 21 May 2017 12:42:39 -0400 (EDT) Received: (qmail 3980 invoked from network); 21 May 2017 16:42:39 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 May 2017 16:42:39 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 528C5EC7B9D; Sun, 21 May 2017 09:42:38 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Can't get 11.0-RELEASE to boot on Banana PI M3 [From back in 2016-Dec] From: Mark Millard In-Reply-To: Date: Sun, 21 May 2017 09:42:37 -0700 Cc: freebsd-arm , jmcneill@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: <32E842C2-496F-4BB2-A8B9-9E84480649B3@dsl-only.net> References: <20161124222152.dfd02dcafdc25182b6b46e50@bidouilliste.com> <66508AA3-436A-4D9E-AAB5-B85D0B4FC40C@dsl-only.net> <9C8B313C-A058-44DF-8673-D23B481CE312@dsl-only.net> <1E9515A0-06D5-4CF9-9D29-D6FF591686F4@dsl-only.net> <53608BFE-4653-4407-AFBE-7AB5E45AF2C1@dsl-only.net> To: Michael Sperber X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 May 2017 16:42:46 -0000 [Sent in part because of bugzilla 219436's submittal, in essence here I repeat my comment 1 to that report.] On 2016-Dec-11, at 1:47 AM, Mark Millard wrote: > . . . > I've not gotten nearly as far as you have for that issue. > I've been trying to gather information on why in the new > context the BPi-M3 shuts down or reboots on its own, no > matter if Ethernet is connected or not. No console messages > about why it shuts down. No log file information. No drop > into ddb, despite how I specified the kernel configuration. >=20 > In the prior environment it had been up for something like > 22 days, with a mix of idle time and used time. Now it > rarely stays up for more than 12 hours, even sitting idle. >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 > On 2016-Dec-11, at 1:15 AM, Michael Sperber wrote: >=20 >=20 > So I've got debug output now: >=20 > Dec 10 22:14:23 kernel: awg0: mem = 0x1c30000-0x1c300ff on simplebus0 > Dec 10 22:14:23 kernel: awg0: soft reset timed out > Dec 10 22:14:23 kernel: awg0: BASIC_CTL_0 00000000 > Dec 10 22:14:23 kernel: awg0: BASIC_CTL_1 08000001 > Dec 10 22:14:23 kernel: awg0: INT_STA 40000000 > Dec 10 22:14:23 kernel: awg0: INT_EN 00000000 > Dec 10 22:14:23 kernel: awg0: TX_CTL_0 00000000 > Dec 10 22:14:23 kernel: awg0: TX_CTL_1 00000000 > Dec 10 22:14:23 kernel: awg0: TX_FLOW_CTL 00000000 > Dec 10 22:14:23 kernel: awg0: TX_DMA_LIST 00000000 > Dec 10 22:14:23 kernel: awg0: RX_CTL_0 00000000 > Dec 10 22:14:23 kernel: awg0: RX_CTL_1 00000000 > Dec 10 22:14:23 kernel: awg0: RX_DMA_LIST 00000000 > Dec 10 22:14:23 kernel: awg0: RX_FRM_FLT 00000000 > Dec 10 22:14:23 kernel: awg0: RX_HASH_0 00000000 > Dec 10 22:14:23 kernel: awg0: RX_HASH_1 00000000 > Dec 10 22:14:23 kernel: awg0: MII_CMD 00000000 > Dec 10 22:14:23 kernel: awg0: ADDR_HIGH0 0000ffff > Dec 10 22:14:23 kernel: awg0: ADDR_LOW0 ffffffff > Dec 10 22:14:23 kernel: awg0: TX_DMA_STA 0000ffff > Dec 10 22:14:23 kernel: awg0: TX_DMA_CUR_DESC ffffffff > Dec 10 22:14:23 kernel: awg0: TX_DMA_CUR_BUF 0000ffff > Dec 10 22:14:23 kernel: awg0: RX_DMA_STA 00000000 > Dec 10 22:14:23 kernel: awg0: RX_DMA_CUR_DESC 00000000 > Dec 10 22:14:23 kernel: awg0: RX_DMA_CUR_BUF 00000000 > Dec 10 22:14:23 kernel: awg0: RGMII_STA 00000000 > Dec 10 22:14:23 kernel: device_attach: awg0 attach returned 60 >=20 > (I'd also increased the retry count from 1000 to 5000, which did not > help.) >=20 > Enough for a PR? I eventually solved my problem on the BPI-M3. That was now months ago: I've not had such a problem in months. Out of all the things that I tried what made the difference was replacing the power supply that I was using to power the BPI-M3. After that the BPI-M3 worked and had no more Ethernet problems, both in the unusual environment that I was in back then and in my usual environment when I returned. It still works just fine. This change was made and tested for a time without making any other simultaneous changes. I eventually started updating the BPI-M3 FreeBSD and ports again. Note: I did not expect the power supply change to make the difference based on the symptoms and other uses of the power supply that I'd made. But I tried replacing it=20 with a different model power supply anyway. (The problem might be the individual power supply rather than a model but I tried a different model.) I've not done anything to examine the properties of the output of the bad/odd power supply when powering the BPI-M3 (or any other use). So I do not know what its technical issue(s) are that a BPI-M3 might be sensitive to. =3D=3D=3D Mark Millard markmi at dsl-only.net