On 2017/04/22 12:57, Gary Duzan wrote: > Booting from the installer image, I noticed a couple of USB related > issues. First, the boot menu wouldn't recognize my USB keyboard; > I had to hit ENTER on my PS/2 keyboard to get the boot to continue. > Then the boot process stopped after probing usb1 (see dmesg below), > only continuing after I pressed a key on the PS/2 keyboard. It > seemed like my USB devices worked after that, but I didn't do any > additional testing. > > Is there anything I can do to help diagnose the problem?
I saw similar problem on RPi2 w/ netbsd-7/earmv6hf. sdhc0: SD Host Specification 3.0, rev.153 sdhc0: using DMA transfer sdmmc0 at sdhc0 slot 0 uhub0 at usb0: DWC2 root hub, class 9/0, rev 2.00/1.00, addr 1 ld0 at sdmmc0: <0x9e:0x4245: :0x02:0xba00016e:0x107> ld0: 7639 MB, 3880 cyl, 64 head, 63 sec, 512 bytes/sect x 15644672 sectors ld0: 4-bit width, bus clock 50.000 MHz (stops here) Suspicious thread is configintr. 0 40 3 3 200 bacf2e20 configintr usbdly db{0}> bt/a bacf2e20 trace: pid 0 lid 40 at 0xbacc7d5c 0xbacc7d5c: netbsd:mi_switch+0x10 0xbacc7d8c: netbsd:sleepq_block+0x16c 0xbacc7dcc: netbsd:kpause+0x134 0xbacc7e5c: netbsd:uhub_attach+0x664 0xbacc7e94: netbsd:config_attach_loc+0x1b4 0xbacc7eac: netbsd:config_found_ia+0x24 0xbacc7f04: netbsd:usbd_attach_roothub+0x80 0xbacc7f64: netbsd:usbd_new_device+0xec8 0xbacc7f94: netbsd:usb_doattach+0xc4 0xbacc7fac: netbsd:config_interrupts_thread+0x4c This problem resembles the problem on amd64 in the point of that the each configintr thread of root hub for usb bus kpause's at usbd_delay_ms in uhub_attach or usbd_new_device, and won't wake up. Not sure who does not wake up kpause.