Can't get 11.0-RELEASE to boot on Banana PI M3
Mark Millard
markmi at dsl-only.net
Sun Dec 11 09:47:30 UTC 2016
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.
===
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?
--
Regards,
Mike
More information about the freebsd-arm
mailing list