Jetson TK1 issues, 8.0 and -current

[Jeff Rizzo <riz%tastylime.net@localhost>]

Trying to get my Jetson TK1 into a more-usable state;  it was running a 
7.99.23 kernel with 7.0 userland relatively well, but not being one to 
leave well enough alone, I decided to upgrade to 8.0, figuring that 
would be, you know, better.  :)


I managed to get an 8.0 kernel (the one from ftp.n.o) running; however, 
the USB3 hub i had been using stopped working. (It had worked, albeit in 
USB2 mode, under the 7.99.23 kernel)  At a suggestion from jmcneill@, I 
installed the nvidia driver binaries in /libdata/firmware - once I did 
that, I still wasn't able to boot with the USB hub connected, but once 
it booted, when I plug the hub in, I see the uhub4 through uhub6 attach, 
but none of the devices:

uhub4 at uhub2 port 1: VIA Labs, Inc. (0x2109) USB3.0 Hub (0x813), class 
9/0, rev 3.00/90.01, addr 1
uhub5 at uhub4 port 1: VIA Labs, Inc. (0x2109) USB3.0 Hub (0x813), class 
9/0, rev 3.00/90.01, addr 2
uhub6 at uhub4 port 4: VIA Labs, Inc. (0x2109) USB3.0 Hub (0x813), class 
9/0, rev 3.00/90.01, addr 3


My keyboard works OK if I plug directly into the one on-board USB port, 
but I kinda like using a hub.  :)


In order to see if this is a fixed issue, I then tried booting a 
-current image from SD card;  this was a little tricky to get booted due 
to u-boot issues, but I did eventually get it to boot a kernel (I had to 
set ${soc} and ${fdtfile} in u-boot manually). Booting this kernel shows 
a few problems with the tegrai2c* driver (times out eventually), but 
then crashes in drm:


[   1.0000630] tegradrm0 at simplebus0
[   1.0000630] kern info: [drm] Supports vblank timestamp caching Rev 2 
(21.10.2013).
[   1.0000630] kern info: [drm] No driver support for vblank timestamp 
query.

[   1.0000630] uvm_fault(0x819e6ba8, 0, 1) -> e
[   1.0000630] Fatal kernel mode data abort: 'Translation Fault (S)'
[   1.0000630] trapframe: 0x81a33a20
[   1.0000630] FSR=00000005, FAR=00000110, spsr=20000153
[   1.0000630] r0 =00000110, r1 =00000000, r2 =00000000, r3 =817e3b58
[   1.0000630] r4 =9188bf88, r5 =9188bf88, r6 =00000110, r7 =00000000
[   1.0000630] r8 =8165d144, r9 =9153e448, r10=81a33ba0, r11=81a33adc
[   1.0000630] r12=81a33ae0, ssp=81a33a70, slr=8126f31c, pc =81389270

Stopped in pid 0.1 (system) at  netbsd:mutex_enter+0x14: ldr     r3, [r0]

db{0}>bt

0x81a33adc: netbsd:mutex_enter+0xc
0x81a33b04: netbsd:drm_fb_helper_single_add_all_connectors+0x3c
0x81a33b24: netbsd:tegra_drm_fb_init+0x60
0x81a33b3c: netbsd:tegra_drm_load+0x24
0x81a33b5c: netbsd:drm_dev_register+0x98
0x81a33bcc: netbsd:tegra_drm_attach+0x310
0x81a33c04: netbsd:config_attach_loc+0x1b4
0x81a33c34: netbsd:config_found_sm_loc+0x54
0x81a33dbc: netbsd:fdt_scan+0x190
0x81a33df4: netbsd:fdt_attach+0xd8
0x81a33e2c: netbsd:config_attach_loc+0x1b4
0x81a33e5c: netbsd:config_found_sm_loc+0x54
0x81a33e74: netbsd:config_found+0x28
0x81a33eac: netbsd:arm_fdt_attach+0x68
0x81a33ee4: netbsd:config_attach_loc+0x1b4
0x81a33f0c: netbsd:config_rootfound+0x48
0x81a33f2c: netbsd:cpu_configure+0x58
0x81a33f9c: netbsd:main+0x2e8
0x81a33fac: netbsd:kernel_text+0x50
db{0}>


In case it helps, the specific kernel which crashes is:

[   1.0000000] NetBSD 8.99.25 (TEGRA) #0: Sat Sep 22 05:24:22 UTC 2018
[   1.0000000] 
mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/evbarm/compile/TEGRA