Date: Sat, 15 Jun 2013 13:40:40 +0200 From: =?utf-8?Q?Hans_Petter_Selasky?= <hans.petter.selasky@bitfrost.no> To: =?utf-8?Q?Konstantin_Belousov?= <kostikbel@gmail.com> Cc: =?utf-8?Q?Sergey_V=2E_Dyatko?= <sergey.dyatko@gmail.com>, =?utf-8?Q?current=40freebsd=2Eorg?= <current@freebsd.org> Subject: RE: USB Keyboard not worked on current (r251681) Message-ID: <zarafa.51bc52b8.6e6e.3b548383311b11d1@eric2.bitfrost> In-Reply-To: <20130615102429.GJ91021@kib.kiev.ua> References: <20130615102429.GJ91021@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, sys/dev/usb/usb_busdma.c Just add error printf() there in all cases. Should be trivial. Probably also something is printed by: sysctl hw.usb.debug=3D15 --HPS =20 -----Original message----- > From:Konstantin Belousov <kostikbel@gmail.com> > Sent: Saturday 15th June 2013 12:24 > To: Hans Petter Selasky <hans.petter.selasky@bitfrost.no> > Cc: Sergey V. Dyatko <sergey.dyatko@gmail.com>; current@freebsd.org > Subject: Re: USB Keyboard not worked on current (r251681) >=20 > 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. >=20 > 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. >=20 > >=20 > > --HPS=20 > > =20 > > -----Original message----- > > > From:Konstantin Belousov <kostikbel@gmail.com> > > > Sent: Saturday 15th June 2013 7:29 > > > To: Sergey V. Dyatko <sergey.dyatko@gmail.com> > > > Cc: kib@freebsd.org; current@freebsd.org > > > Subject: Re: USB Keyboard not worked on current (r251681) > > >=20 > > > 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@bitfrost.no> wrote: > > > >=20 > > > > > See this thread and solution "Supermicro 6027R-N3RF+head, usb trouble" > > > > >=20 > > > > It was 'fixed' by r251282, but I see r251681 on subject :) > > > > added kib@ to Cc > > >=20 > > > 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. > > >=20 > > > 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. > > >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zarafa.51bc52b8.6e6e.3b548383311b11d1>