Date: Sun, 11 Dec 2016 01:47:26 -0800 From: Mark Millard <markmi@dsl-only.net> To: Michael Sperber <sperber@deinprogramm.de> Cc: jmcneill@FreeBSD.org, freebsd-arm@freebsd.org Subject: Re: Can't get 11.0-RELEASE to boot on Banana PI M3 Message-ID: <F11B7389-1EA2-4D59-AAF3-164432672343@dsl-only.net> In-Reply-To: <y9lk2b6ddx2.fsf@jellaby.local> References: <y9l7f7t2smo.fsf@jellaby.local> <20161124222152.dfd02dcafdc25182b6b46e50@bidouilliste.com> <66508AA3-436A-4D9E-AAB5-B85D0B4FC40C@dsl-only.net> <y9leg1w11yy.fsf@jellaby.local> <A218DF6A-4EFA-4EB7-99EC-8DA2E077DE3F@dsl-only.net> <y9lzikfbl8x.fsf@jellaby.local> <9C8B313C-A058-44DF-8673-D23B481CE312@dsl-only.net> <y9loa0ua6ge.fsf@jellaby.local> <1E9515A0-06D5-4CF9-9D29-D6FF591686F4@dsl-only.net> <y9loa0t87um.fsf@jellaby.local> <53608BFE-4653-4407-AFBE-7AB5E45AF2C1@dsl-only.net> <y9lk2b6ddx2.fsf@jellaby.local>
next in thread | previous in thread | raw e-mail | index | archive | help
To someone with appropriate background knowledge this is probably useful information. But on my level of ignorance of what things should be like I'd have to be able to compare to a register dump when it worked okay in order to have any clue what to look at. (And I'd have to find documentation to have any chance to understand anything.) I expect that with background information like that sometimes (usually?) it fails this way but other times it works and the like it should be good to submit for someone with the knowledge. 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. 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. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2016-Dec-11, at 1:15 AM, Michael Sperber <sperber at deinprogramm.de> = wrote: So I've got debug output now: Dec 10 22:14:23 kernel: awg0: <Allwinner Gigabit Ethernet> 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 (I'd also increased the retry count from 1000 to 5000, which did not help.) Enough for a PR? --=20 Regards, Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F11B7389-1EA2-4D59-AAF3-164432672343>