From owner-freebsd-usb@FreeBSD.ORG Sat Dec 15 22:58:33 2007 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 85A8F16A417 for ; Sat, 15 Dec 2007 22:58:33 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail5out.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) by mx1.freebsd.org (Postfix) with ESMTP id 513EA13C4E1 for ; Sat, 15 Dec 2007 22:58:33 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail5out.barnet.com.au (Postfix, from userid 1001) id 9828A2218A79; Sun, 16 Dec 2007 09:58:32 +1100 (EST) X-Viruscan-Id: <47645C18000083ECA67AC0@BarNet> Received: from mail5auth.barnet.com.au (mail5.barnet.com.au [202.83.178.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail5auth.barnet.com.au", Issuer "*.barnet.com.au" (verified OK)) by mail5.barnet.com.au (Postfix) with ESMTP id 5BF5721B18C0; Sun, 16 Dec 2007 09:58:32 +1100 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail5auth.barnet.com.au (Postfix) with ESMTP id 111C12218A75; Sun, 16 Dec 2007 09:58:32 +1100 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id E937226C; Sun, 16 Dec 2007 09:58:31 +1100 (EST) Date: Sun, 16 Dec 2007 09:58:31 +1100 From: Edwin Groothuis To: Hans Petter Selasky Message-ID: <20071215225831.GO40967@k7.mavetju> References: <20071215125514.GA33989@k7.mavetju> <200712151408.00440.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200712151408.00440.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-usb@freebsd.org Subject: Re: Huawei E220 USB modem 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: Sat, 15 Dec 2007 22:58:33 -0000 On Sat, Dec 15, 2007 at 02:07:59PM +0100, Hans Petter Selasky wrote: > > I admit that this is not the worlds best option, because it gives > > this in the kernel: > > Did you add your latest patch to the PR system ? Not yet, I was trying to find a way to do it cleaner, but twenty reboots (why can't I remove ucom even when I loaded ubsa myself?) and seven kernel panics later (I don't know what happens if I get a panic while the system is doing a fsck on a dirty filesystem so I don't try) I decided to go to bed and to try it again on this glorious sunday where I got woken up at 07:15 by a little boy who exclaimed "Papa, I have made a mess!" which is an indicator that the glorious sunday is starting way too early and in not in the way you had hoped for it. Besides, there is no way to stop it if the approach in the patch doesn't work and the interrupt is still not found, in that case it will keep going on forever and forever. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/