On Sat, Feb 9, 2019 at 8:18 AM Rin Okuyama <rokuyama...@gmail.com> wrote: > > Hi, > > On 2019/02/08 23:16, sc dying wrote: > > On 2019/01/31 05:51, Rin Okuyama wrote: > >> By the way, I find that the system hangs silently by > >> "ifconfig mueN down" or detaching LAN7500 from USB port when > >> multiple outstanding requests are enabled. This does not occur > >> when MUE_TX_LIST_CNT = MUE_RX_LIST_CNT = 1. Do you have any ideas > >> to fix it? > > > > My axen dongle locks up if AXEN_RX_LIST_CNT > 1 > > when ifconfig down on amd64 8.99.34. > > > > db{0}> bt > > breakpoint() at netbsd:breakpoint+0x5 > > comintr() at netbsd:comintr+0x861 > > Xhandle_ioapic_edge4() at netbsd:Xhandle_ioapic_edge4+0x66 > > --- interrupt --- > > xhci_device_bulk_abort() at netbsd:xhci_device_bulk_abort+0x1c > > usbd_ar_pipe() at netbsd:usbd_ar_pipe+0x1e9 > > usbd_abort_pipe() at netbsd:usbd_abort_pipe+0x27 > > axen_stop() at netbsd:axen_stop+0xc4 > > axen_ioctl() at netbsd:axen_ioctl+0x1d9 > > doifioctl() at netbsd:doifioctl+0xa99 > > sys_ioctl() at netbsd:sys_ioctl+0x11c > > syscall() at netbsd:syscall+0xb4 > > --- syscall (number 54) --- > > 732731d1a88a: > > > > Looks like kernel goes infinite loop in usbd_ar_pipe by some reason. > > It tries to abort NOT_STARTED xfers. > > Can you tell me how to reproduce this failure? > "ifconfig down" works for me on RPI3B+.
I tested on intel 3000 series CPU + Ivebridge with kernel from my local tree. But I found it does not happen with the lastest kernel from https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/amd64/binary/kernel/netbsd-GENERIC.gz.