From owner-freebsd-usb@FreeBSD.ORG Mon Feb 16 07:33:30 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2E4B106566C for ; Mon, 16 Feb 2009 07:33:30 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id 6B5588FC1D for ; Mon, 16 Feb 2009 07:33:29 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MXw7gxVQKqGXY79tIT8aFQ==:17 a=aWuxVeRqOD4lm-H80xgA:9 a=_7SLEs5rA99ePfhjPh8A:7 a=MvFYJKm7TVK8wQKLrd3-I--pBkEA:4 a=LY0hPdMaydYA:10 Received: from [62.113.132.61] (account mc467741@c2i.net HELO laptop) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 1197397927; Mon, 16 Feb 2009 08:33:28 +0100 From: Hans Petter Selasky To: Noriyoshi Kawano Date: Mon, 16 Feb 2009 08:35:54 +0100 User-Agent: KMail/1.9.7 References: <86y6wbf2nc.wl%bowie@nrik.jp> <200902141036.54246.hselasky@c2i.net> <86d4dij1i2.wl%bowie@nrik.jp> In-Reply-To: <86d4dij1i2.wl%bowie@nrik.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902160835.55330.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: USB2 & apcupsd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 07:33:31 -0000 On Monday 16 February 2009, Noriyoshi Kawano wrote: > At Sat, 14 Feb 2009 10:36:53 +0100, > > Hans Petter Selasky wrote: > > Hi, > > > > As long as you don't see ugenX.Y attach/detach messages, it means that > > the Apcupsd daemon is doing something. Probably it is the > > "usb_link_check()" procedure that is executing and the connection is > > reset by the following code: > > > > if (my_data->fd) { > > usb_reset(my_data->fd); > > /* XXX: usb_close() not needed according to libusb0.1 refdocs */ > > usb_close(my_data->fd); > > > > Could you enable debugging in Apcupsd ? > > > > What speed is your device reported like by usbconfig ? > > > > --HPS > > Hi, > > I enabled debugging in apcupsd. > > Because the "usb_interrupt_read()" becomes the error, > the "usb_link_check()" is called. > > # apcupsd -d 500 > --- snip --- > 61.689 apcupsd: generic-usb.c:538 Timeout=539 > 62.232 apcupsd: generic-usb.c:549 usb_interrupt_read error: (-1) Operation > not permitted 62.232 apcupsd: generic-usb.c:458 link_check comm lost > 68.538 apcupsd: generic-usb.c:300 Reinitializing private structure. > 68.539 apcupsd: generic-usb.c:398 Initializing libusb > 68.539 apcupsd: generic-usb.c:403 Found 0 USB busses > 68.539 apcupsd: generic-usb.c:405 Found 0 USB devices > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen3.2 - 0000:0000 > 68.539 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen0.2 - 051d:0002 > --- snip --- > > # usbconfig -u 0 -a 2 > ugen0.2: at > usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON Does ugen0.2 have the correct permissions? usbconfig -u 0 -a 2 set_owner xxx:yyy set_perm 0660 --HPS