From owner-freebsd-usb@freebsd.org Sun Oct 18 15:08:38 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C058BA18001 for ; Sun, 18 Oct 2015 15:08:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 AD3DBF89 for ; Sun, 18 Oct 2015 15:08:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9IF8clX051577 for ; Sun, 18 Oct 2015 15:08:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 188829] [atp] atp fails on Macbook Pro 4.1 [regression] Date: Sun, 18 Oct 2015 15:08:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwbacon@tds.net X-Bugzilla-Status: In Progress X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Oct 2015 15:08:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188829 jwbacon@tds.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwbacon@tds.net --- Comment #3 from jwbacon@tds.net --- I'm seeing the same issue with my 2007 MacBook Pro in 10.2-RELEASE. Roberto's hack is no longer viable, as atp.c has changed too much since 10.0. I have src installed and would be willing to try any suggestions from an expert in the area. A diff of the two atp.c files produced way too many changes for me to track down the bug on my own: diff atp.c.10.0 atp.c | wc -l 3202 My workaround for now is restarting sysmouse every minute via crontab. Jason -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Mon Oct 19 23:05:56 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D817A18990 for ; Mon, 19 Oct 2015 23:05:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 3A36B1442 for ; Mon, 19 Oct 2015 23:05:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9JN5u3v017456 for ; Mon, 19 Oct 2015 23:05:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 201421] locking issues prevent new process creation Date: Mon, 19 Oct 2015 23:05:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2015 23:05:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201421 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-threads@FreeBSD.org |freebsd-usb@FreeBSD.org CC| |hselasky@FreeBSD.org --- Comment #3 from John Baldwin --- Adding Hans Petter to comment on USB. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Tue Oct 20 08:11:02 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED89AA1AEC2 for ; Tue, 20 Oct 2015 08:11:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 DA270185C for ; Tue, 20 Oct 2015 08:11:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9K8B2TW044707 for ; Tue, 20 Oct 2015 08:11:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 201421] locking issues prevent new process creation Date: Tue, 20 Oct 2015 08:11:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2015 08:11:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201421 --- Comment #4 from Hans Petter Selasky --- (In reply to John Baldwin from comment #3) Hi, If you run "usbconfig" as root, and if it doesn't respond, looks like it is hanging, it typically means USB is not able to detach one of the device drivers. In recent past it is know that sudden detach of USB memory sticks can cause this error, because of refcounts inside CAM / SCSI not going to zero. Also you need to ensure that any USB MIDI devices gets closed by the application when they receive a read error. Else the open file handle will block further USB enumeration. And will also lock other applications which are enumerating USB on that particular USB device. When running KGDB, you could check the backtrace of the USB explore threads. ps auxwH | grep -i usb Did you try 10-stable or 9-stable and not the release branches. From time to time bugfixes are merged to these branches. --HPS -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-usb@freebsd.org Tue Oct 20 20:18:32 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACE8DA0A207 for ; Tue, 20 Oct 2015 20:18:32 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 75A9CE4 for ; Tue, 20 Oct 2015 20:18:32 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 89EED1FE023; Tue, 20 Oct 2015 22:18:30 +0200 (CEST) Subject: Re: External USB Harddisk ZFS boot problem To: Philipp Maechler , freebsd-usb@freebsd.org References: <5622809C.7020501@gmail.com> From: Hans Petter Selasky Message-ID: <5626A1FC.9040801@selasky.org> Date: Tue, 20 Oct 2015 22:20:12 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <5622809C.7020501@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2015 20:18:32 -0000 On 10/17/15 19:08, Philipp Maechler wrote: > Good evening, > > I have a problem and a manual an nasty work around, and like to have > some hints how/where to digg deeper. > > FreeBSD 10.2 (GENERIC freshly installed) and root zfs pool on a > external usb harddisk drive. I try to boot from this zfs pool. More > details about the hardware further down. > > This zfs pool is a zfs send/receive copy of a working zfs boot setup > (but it was before an 10.1 - note to myself: never change 2 things at > the same time [duplicate]) > > The new harddisk is setup properly (boot-loader etc) and also the zpool > cache file is correctly up-to-date and the bootfs property is set. > > What happens is that the boot loader works fine, then it loads the > kernel and the kernel starts. At this time, the drive switch off and the > kernel loads further and starts to wait for root an usbus0 and usbus1 > Hi, It is not easy to say why your disk is powering down. I know the ZFS uses some more SCSI commands like SYNCHRONIZE cache which UFS doesn't in the same way. Did you try to edit sys/dev/usb/quirk/usb_quirk.c and add a UQ_MSC_NO_SYNC_CACHE for your disk? --HPS From owner-freebsd-usb@freebsd.org Wed Oct 21 08:04:45 2015 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41C23A1A04D for ; Wed, 21 Oct 2015 08:04:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 1685F1477 for ; Wed, 21 Oct 2015 08:04:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9L84iwm063742 for ; Wed, 21 Oct 2015 08:04:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 201421] locking issues prevent new process creation Date: Wed, 21 Oct 2015 08:04:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: FreeBSD@ShaneWare.Biz X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2015 08:04:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201421 --- Comment #5 from FreeBSD@ShaneWare.Biz --- I started running stable/10 back in December, sometimes building updates every couple of weeks. Expanding from my last entry - it is definitely related to the usb multi card reader that *was* attached internally. Since disconnecting that I have not had an issue, current uptime is 24 days 14 hours - best time in almost 12 months. While sometimes I had trouble mounting a usb memstick before the locking issue that prevents process creation, other times the locking happened without trying to mount a device. I wasn't sure at first if these two were related. As I always got varying uptimes from 20 minutes to 2 days, there would be a timing factor where maybe the card reader goes to sleep just as it was being scanned... I expect that is then holding the lock that causes trouble later. It also appeared to only initially affect the usb bus that the card reader was attached, as the example of failing to mount a memstick in the front case-mounted usb port while a rear usb3 port worked. Then once the locking kicked in, neither worked. The reader was installed when I got the machine, I first installed 9.0 (I think RC3) and updated to 9.1 and 9.2 without issue, then I installed 10.1 RC2 and the problems started. I get this can be hard to pin point and also hard to test as I can't reproduce the issue on cue, and as no-one else seems to have this issue it may even be this reader attached to this motherboard, I am happy to leave the reader disconnected and move on. -- You are receiving this mail because: You are the assignee for the bug.