On Sat, Jun 15, 2013 at 09:34:59AM +0200, Hans Petter Selasky wrote: > It is some error code from busdma. This is not helpful, obviously. We need to know exactly what call failed, with what parameters together with the values from the tag. Then the hypothesis about the system state could be made and corresponding information requested. > > --HPS > > -----Original message----- > > From:Konstantin Belousov <kostikbel_at_gmail.com> > > Sent: Saturday 15th June 2013 7:29 > > To: Sergey V. Dyatko <sergey.dyatko_at_gmail.com> > > Cc: kib_at_freebsd.org; current_at_freebsd.org > > Subject: Re: USB Keyboard not worked on current (r251681) > > > > On Fri, Jun 14, 2013 at 12:41:28PM +0300, Sergey V. Dyatko wrote: > > > On Fri, 14 Jun 2013 11:36:56 +0200 > > > Hans Petter Selasky <hps_at_bitfrost.no> wrote: > > > > > > > See this thread and solution "Supermicro 6027R-N3RF+head, usb trouble" > > > > > > > It was 'fixed' by r251282, but I see r251681 on subject :) > > > added kib_at_ to Cc > > > > It was not 'fixed', I reacted on something which was wrong on its own, > > and which was accidentally reported to somehow cover/fix the USB issue. > > > > You have to trace does the real cause of the USB failure, in particular, > > to find the place where USB_ERR_NOMEM comes from. But, the error from > > the usbd_ctrl_transfer_setup: 'could not setup default USB transfer' > > comes before ENOMEM and its cause is lost in the USB code. > >
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:38 UTC