From owner-freebsd-current@FreeBSD.ORG Sat Jun 15 07:35:16 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 53C8069D; Sat, 15 Jun 2013 07:35:16 +0000 (UTC) (envelope-from hans.petter.selasky@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 17D1E1CC3; Sat, 15 Jun 2013 07:35:15 +0000 (UTC) Received: from mail.bitfrost.no (mail.bitfrost.no [46.29.221.36]) by mta.bitpro.no (Postfix) with ESMTP id 886F67A1CD; Sat, 15 Jun 2013 09:35:13 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at bitfrost.no Subject: RE: USB Keyboard not worked on current (r251681) From: =?utf-8?Q?Hans_Petter_Selasky?= To: =?utf-8?Q?Sergey_V=2E_Dyatko?= , =?utf-8?Q?Konstantin_Belousov?= Date: Sat, 15 Jun 2013 09:34:59 +0200 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit In-Reply-To: <20130615052941.GI91021@kib.kiev.ua> References: <20130615052941.GI91021@kib.kiev.ua> X-Priority: 3 (Normal) Message-Id: X-Mailman-Approved-At: Sat, 15 Jun 2013 14:03:00 +0000 Cc: =?utf-8?Q?kib=40freebsd=2Eorg?= , =?utf-8?Q?current=40freebsd=2Eorg?= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jun 2013 07:35:16 -0000 It is some error code from busdma. --HPS -----Original message----- > From:Konstantin Belousov > Sent: Saturday 15th June 2013 7:29 > To: Sergey V. Dyatko > Cc: kib@freebsd.org; current@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 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@ 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. >