Re: Panic in usbd_create_xfer

[Yorick Hardy <yorickhardy%gmail.com@localhost>]

Dear matthew,

On 2021-01-03, matthew green wrote:
> Yorick Hardy writes:
> > Dear current-users,
> >
> > Happy new year!
> 
> happy new year yorick! and everyone.
> 
> > [   659.839003] usbd_create_xfer() at netbsd:usbd_create_xfer+0x186
> > [   659.849001] usbd_open_pipe_intr() at netbsd:usbd_open_pipe_intr+0x74
> > [   659.849001] uhidev_open() at netbsd:uhidev_open+0x21c
> 
> can you find out what lines in the source these are? 
> espcially usbd_create_xfer+0x186, the other ones are
> most likely obvious only the single callers - eg,
> usbd_open_pipe_intr() calls usbd_create_xfer() once.
> 
> thanks.
> 
> 
> .mrg.

In the disassembly (I guess due to inlining) it happens at a call to
usb_allocmem, which I think is line sys/dev/usb/usbdi.c:606, i.e. the
call to usbd_alloc_buffer.

I am current trying to trigger the panic with all of the USB_DEBUG and
{U,O,E}HCI_DEBUG options enabled but it has not happened yet (I was sure
I would be able to panic the kernel by now, maybe the _DEBUG options
worka round the panic somehow?).

-- 
Kind regards,

Yorick Hardy