Ethernet issue on NVIDIA Jetson

[John Klos <john%ziaspace.com@localhost>]

Hi,

Having just gotten an NVIDIA Jetson TK1, I've installed NetBSD-current on it. 
I've noticed two problems which seem to be related.

First is that re0 is sometimes not recognized on reboot. Since this will go in 
to a colocation facility, it seems to not have a problem when I peg re0 at pci2 
dev 0 function 0, but there's still some issue with hardware initialization.

Thinking that the state of the ethernet at boot time may be an issue, I decided 
to ping -f the IP of the interface while the system rebooted (since it reboots 
quickly enough that the packets will still be sent to re0's MAC for a while). 
The system paniced on boot... Hmmm... Not good.

I couldn't get a crash dump:

Waiting for DAD to complete for statically configured addresses...
Starting dhcpcd.
tegramc0: intrstatus 0x40 err 0x2000000e adr 0
panic: kernel diagnostic assertion "(sp)->refcnt > 0" failed: file 
"/usr/src/sys/netipsec/key.c", line 1221
cpu0: Begin traceback...
0x9a813d1c: netbsd:db_panic+0xc
0x9a813d34: netbsd:vpanic+0x1b4
0x9a813d4c: netbsd:__udivmoddi4
0x9a813d8c: netbsd:_key_freesp+0x184
0x9a813e64: netbsd:ip_output+0xaa0
0x9a813ebc: netbsd:ip_forward+0x1b8
0x9a813f64: netbsd:ipintr+0x1144
0x9a813fac: netbsd:softint_dispatch+0xd4
Bad frame pointer: 0x9a78ff6c
cpu0: End traceback...

dumping to dev 16,1 offset 4194303
dump Skipping crash dump on recursive panic
panic: wddump: polled command has been queued
cpu0: Begin traceback...
0x9a8139f4: netbsd:db_panic+0xc
0x9a813a0c: netbsd:vpanic+0x1b4
0x9a813a24: netbsd:snprintf
0x9a813a74: netbsd:wddump+0x29c
0x9a813c9c: netbsd:cpu_dump+0xe8
0x9a813cec: netbsd:dodumpsys+0x110
0x9a813d1c: netbsd:dumpsys+0x18
0x9a813d34: netbsd:vpanic+0x1c0
0x9a813d4c: netbsd:__udivmoddi4
0x9a813d8c: netbsd:_key_freesp+0x184
0x9a813e64: netbsd:ip_output+0xaa0
0x9a813ebc: netbsd:ip_forward+0x1b8
0x9a813f64: netbsd:ipintr+0x1144
0x9a813fac: netbsd:softint_dispatch+0xd4
Bad frame pointer: 0x9a78ff6c
cpu0: End traceback...
rebooting...


What's interesting is that, as a test, I did an ifconfig re0 down followed by a 
shutdown -r now, and u-boot then couldn't talk to the ethernet interface 
properly:

U-Boot 2014.10-rc2-g3127911 (Jun 07 2016 - 21:00:01)

TEGRA124
Board: NVIDIA Jetson TK1
I2C:   ready
DRAM:  2 GiB
MMC:   Tegra SD/MMC: 0, Tegra SD/MMC: 1
*** Warning - bad CRC, using default environment

tegra-pcie: PCI regions:
tegra-pcie:   I/O: 0x12000000-0x12010000
tegra-pcie:   non-prefetchable memory: 0x13000000-0x20000000
tegra-pcie:   prefetchable memory: 0x20000000-0x40000000
tegra-pcie: 2x1, 1x1 configuration
tegra-pcie: probing port 0, using 2 lanes
tegra-pcie: link 0 down, retrying
tegra-pcie: link 0 down, retrying
tegra-pcie: link 0 down, retrying
tegra-pcie: link 0 down, ignoring
tegra-pcie: probing port 1, using 1 lanes
tegra-pcie: link 1 down, retrying
tegra-pcie: link 1 down, retrying
tegra-pcie: link 1 down, retrying
tegra-pcie: link 1 down, ignoring
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.

In this case, the SATA couldn't be mounted:

emc at fdt0 not configured
ahcisata0 at fdt0: SATA
ahcisata0: couldn't acquire vddio-supply
ahcisata0: couldn't acquire avdd-supply
ahcisata0: interrupting on LIC irq 55
ahcisata0: AHCI revision 1.31, 2 ports, 32 slots, CAP 
0xe620ff01<PSC,SSC,PMD,ISS
=0x2=Gen2,SAL,SALP,SSNTF,SNCQ,S64A>
...
uhid6 at uhidev2 reportid 33: input=31, output=31, feature=0
ahcisata0: BSY never cleared, TD 0x80
WARNING: 3 errors while detecting hardware; check system log.
boot device: ld1
device wd0 (0x1000) not configured
root device (default ld1a):


On the next reboot, both re0 and ahcisata0 initialized and could be used :P

Thoughts? Suggestions?

John