From owner-freebsd-current@FreeBSD.ORG Mon Dec 15 18:24:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4ECCE106564A for ; Mon, 15 Dec 2008 18:24:30 +0000 (UTC) (envelope-from dgerow@afflictions.org) Received: from relay1-v.mail.gandi.net (relay1-v.mail.gandi.net [217.70.178.75]) by mx1.freebsd.org (Postfix) with ESMTP id 110FB8FC1E for ; Mon, 15 Dec 2008 18:24:29 +0000 (UTC) (envelope-from dgerow@afflictions.org) Received: from plebeian.afflictions.org (CPE0021296fd1ec-CM0019475d4056.cpe.net.cable.rogers.com [99.241.164.229]) by relay1-v.mail.gandi.net (Postfix) with ESMTP id 2D20C362B9 for ; Mon, 15 Dec 2008 19:24:28 +0100 (CET) Received: by plebeian.afflictions.org (Postfix, from userid 1001) id 0D5BF71AB; Mon, 15 Dec 2008 13:24:24 -0500 (EST) Date: Mon, 15 Dec 2008 13:24:24 -0500 From: Damian Gerow To: freebsd-current@freebsd.org Message-ID: <20081215182424.GA44202@plebeian.afflictions.org> References: <20081212054137.GA42087@plebeian.afflictions.org> <20081215051245.GA58909@plebeian.afflictions.org> <3c1674c90812142117m71a6c67dkf6f7dda02a6aa411@mail.gmail.com> <3a142e750812150432l1d59b6e0icc070935d569ec87@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a142e750812150432l1d59b6e0icc070935d569ec87@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: ural(4) hits usb/124758 (Was: Panic while using ural(4) with wpa_supplicant) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 15 Dec 2008 18:24:30 -0000 Paul B. Mahol wrote: : On 12/15/08, Kip Macy wrote: : > I reliably hit panics with ural(4) as well - they appear to be locking : > related. : : Correct, this PR is same as one from me - but mine is for rum driver. : using kern.smp.disabled=1 is workaround. : usb2_wlan_rum from usb2 doesnt have that problem - I do not use old : usb stack any more. I've checked out a new source, and replaced the old USB stack with the new in an otherwise-GENERIC kernel, and I've been running with the ural device for a few hours now, no panic. Ordinarly, I would have paniced a handful of times by now. USB2 fixed it for me, too.