cubietruck ethernet device / awge0 panic

[Markus Kilbinger <mk%kilbi.de@localhost>]

Hi!

I've booted an actual evbarm/CUBIETRUCK-kernel on my recently acquired
cubietruck-board which works quite fine until trying to use its
network device awge0.

In the boot message it appears to have two rgephy's (?):

NetBSD 7.99.1 (CUBIETRUCK) #0: Wed Sep 24 09:26:22 MEST 2014
        root@q:/usr/NetBSD/HEAD/src/sys/arch/evbarm/compile/CUBIETRUCK
total memory = 2048 MB
avail memory = 2022 MB
sysctl_createv: sysctl_create(machine_arch) returned 17
kern.module.path=/stand/evbarm/7.99.1/modules
mainbus0 (root)
cpu0 at mainbus0 core 0: 960 MHz Cortex-A7 r0p4 (Cortex V7A core)
cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled
[...]
awiniic0 at awinio0 port 0: Marvell TWSI controller
awiniic0: interrupting on irq 39
iic0 at awiniic0: I2C bus
axp20x0 at iic0 addr 0x34
awge0 at awinio0: Gigabit Ethernet Controller
awge0: interrupting on irq 117
awge0: Ethernet address: 02:82:07:xx:xx:xx
rgephy0 at awge0 phy 0: RTL8169S/8110S/8211 1000BASE-T media interface, rev. 5
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
rgephy1 at awge0 phy 1: RTL8169S/8110S/8211 1000BASE-T media interface, rev. 5
rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto

After setting the device 'up' it panics after serveral seconds like:

# ifconfig awge0 up
# ifconfig awge0
awge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 02:82:07:xx:xx:xx
        media: Ethernet autoselect (1000baseT full-duplex)
        status: active
        inet6 fe80::82:7ff:fexx:xxxx%awge0 prefixlen 64 scopeid 0x1
# ifconfig awge0
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
awge0: INTR status: 00000000, DMA status: 00618421
panic: enough now
Stopped in pid 0.5 (system) at  netbsd:cpu_Debugger+0x4:        bx      r14
db>

Is this a known problem / still under development?
Did I miss somehing?

Any comment appreciated!

Regards, Markus.