From owner-freebsd-usb@FreeBSD.ORG Mon Apr 21 15:30:01 2014 Return-Path: Delivered-To: freebsd-usb@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B04D823A for ; Mon, 21 Apr 2014 15:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 916981341 for ; Mon, 21 Apr 2014 15:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3LFU1YB071670 for ; Mon, 21 Apr 2014 15:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3LFU1B0071669; Mon, 21 Apr 2014 15:30:01 GMT (envelope-from gnats) Date: Mon, 21 Apr 2014 15:30:01 GMT Message-Id: <201404211530.s3LFU1B0071669@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org Cc: From: Roberto de Iriarte Subject: Re: usb/188829: atp fails on Macbook Pro 4.1 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Roberto de Iriarte List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2014 15:30:01 -0000 The following reply was made to PR usb/188829; it has been noted by GNATS. From: Roberto de Iriarte To: Hans Petter Selasky , freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: usb/188829: atp fails on Macbook Pro 4.1 Date: Mon, 21 Apr 2014 12:15:10 -0300 On 04/20/14 13:35, Hans Petter Selasky wrote: > On 04/20/14 18:01, Roberto de Iriarte wrote: >> >>> Number: 188829 >>> Category: usb >>> Synopsis: atp fails on Macbook Pro 4.1 >>> Confidential: no >>> Severity: non-critical >>> Priority: low >>> Responsible: freebsd-usb >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: sw-bug >>> Submitter-Id: current-users >>> Arrival-Date: Sun Apr 20 16:10:00 UTC 2014 >>> Closed-Date: >>> Last-Modified: >>> Originator: Roberto de Iriarte >>> Release: 10.0-STABLE >>> Organization: >> De Iriarte >>> Environment: >> FreeBSD mbp 10.0-STABLE FreeBSD 10.0-STABLE #13 r264692M: Sun Apr 20 >> 12:14:28 CLST 2014 root@mbp:/usr/obj/usr/src/sys/GENERIC amd64 >>> Description: >> On my Macbook Pro 4.1, after upgrading from 10.0-RELEASE to >> 10.0-STABLE, the atp touchpad driver becomes unresponsive after a few >> minutes under high I/O load, until it stalls completely. The device >> never unstalls, regardless of system load. >> >> Closing and opening /dev/atp0 (i.e. restarting moused) restores >> responsiveness for a couple of minutes, then it fails in the same >> manner. >> >> Reverting back /usr/src/sys/dev/usb/input/atp.c from rev. 263063 to >> rev. 233774 (as shipped with FreeBSD 10.0-RELEASE) solves the problem >> completely on my machine. >> >> Unfortunately, i am not versed in the workings of the atp driver in >> order to debug the new driver any further. >>> How-To-Repeat: >> Use the trackpad under high I/O load >>> Fix: >> Hack: Revert back to /usr/src/sys/dev/usb/input/atp.c as shipped with >> 10.0-RELEASE (r. 233774) >> >>> Release-Note: >>> Audit-Trail: >>> Unformatted: >> _______________________________________________ > > Hi, > > Can you send output from: > > usbconfig dump_device_desc > > which is relevant for your device. > The relevant device is ugen5.3: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (40mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x05ac idProduct = 0x021a bcdDevice = 0x0018 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 > What happens if you add to /boot/loader.conf > > wsp_load=YES > > And re-boot? > > --HPS > I tried the following configurations on /boot/loader.conf atp_load=YES wsp_load=YES Same effect as with atp_load only, device gets dected as atp0, fails as described wsp_load=YES only Device gets detected as usm0, using the ums driver, it works but no touchpad features are recognized) Thanks a lot! Roberto