Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Jun 2013 13:24:29 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Hans Petter Selasky <hans.petter.selasky@bitfrost.no>
Cc:        "Sergey V. Dyatko" <sergey.dyatko@gmail.com>, "current@freebsd.org" <current@freebsd.org>
Subject:   Re: USB Keyboard not worked on current (r251681)
Message-ID:  <20130615102429.GJ91021@kib.kiev.ua>
In-Reply-To: <zarafa.51bc1923.5756.58e2067432d50c6f@eric2.bitfrost>
References:  <20130615052941.GI91021@kib.kiev.ua> <zarafa.51bc1923.5756.58e2067432d50c6f@eric2.bitfrost>

next in thread | previous in thread | raw e-mail | index | archive | help

--W13SgbpmD6bhZUTM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.

>=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 troub=
le"
> > > >=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

--W13SgbpmD6bhZUTM
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)

iQIcBAEBAgAGBQJRvEDcAAoJEJDCuSvBvK1Bg4MP/1y54HeK5wL7pKpuPL5Q9/7n
BqAUMuNYqw7vxuXqOqzyHvOWSN2lph6RNYwoihUHj9NU243nJixhztZSnEv5IGGt
FRVHFefvwLO0QNucZ13qZSPvOXbGfe8kHKkSKg3KgafDal0kJlN8rPc1uT6jRuOI
qw6FG1qZzTf+Gm3N5nooJgSwh3zvKzsw+IKv3pVGoQzATJ8844t8zpRMp/XwRnw+
Hl62lMiGAqz7rzaRsUNA4r1KF7cOAIkoq+alv6HrXjEPfda1gflYLsm8aCo3lkm4
OfhOoUaRTz4FbkxPf8MJ1yCrwgmmBb51zXDJHeTSBSEjiIMK/LZ/iFId84z20BP8
XP5Yuxv+pamg7rvTYSJr56DYShM2WfyVnfmNmNAmZsz+87gLgE8/QyggKymaC+gS
Cwpxi+7slXHRtLUozNoy/J2Zi9gNEiPWru3Nx9ZRap1qoCWl/kPKyr7nY5y6Y0Hw
yn+giJzPKj5AtFOFqWS12gb3rSfMbUtimMjt4llBv1Hrcwa8mfycla0qb7oSRlIo
GfE+QQLhDTcm67F5vNwW/xzxaMaTalQat1LCtmDdmc1RIt4pt3SvXYdOsrLq0bFv
TXMKiUqqkOm3QFCwHTPiRVlUraC/oGJzhGE2opcOW7lNsn9m74U2HuIfC6uUUHly
s17SeUodqMNvUIYY7Jxo
=pDUX
-----END PGP SIGNATURE-----

--W13SgbpmD6bhZUTM--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130615102429.GJ91021>