From owner-freebsd-usb@FreeBSD.ORG  Fri Apr  1 19:34:09 2005
Return-Path: <owner-freebsd-usb@FreeBSD.ORG>
Delivered-To: freebsd-usb@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CF50116A4CE
	for <freebsd-usb@freebsd.org>; Fri,  1 Apr 2005 19:34:09 +0000 (GMT)
Received: from swip.net (mailfe04.swip.net [212.247.154.97])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DF4D343D54
	for <freebsd-usb@freebsd.org>; Fri,  1 Apr 2005 19:34:08 +0000 (GMT)
	(envelope-from hselasky@c2i.net)
X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ==
Received: from mp-217-229-134.daxnet.no ([193.217.229.134] verified)
  by mailfe04.swip.net (CommuniGate Pro SMTP 4.2.9)
  with ESMTP id 333054779; Fri, 01 Apr 2005 21:34:06 +0200
From: Hans Petter Selasky <hselasky@c2i.net>
To: Mike Tancsa <mike@sentex.net>
Date: Fri, 1 Apr 2005 21:35:06 +0200
User-Agent: KMail/1.7
References: <6.2.1.2.0.20050329222822.04f7c500@64.7.153.2>
	<200504011631.51760.hselasky@c2i.net>
	<6.2.1.2.0.20050401093603.03253ad0@64.7.153.2>
In-Reply-To: <6.2.1.2.0.20050401093603.03253ad0@64.7.153.2>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200504012135.07798.hselasky@c2i.net>
cc: freebsd-usb@freebsd.org
Subject: Re: panic: uhci_abort_xfer: not in process context (was Re: uplcom
	/ ucom problems on RELENG_5)
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: hselasky@c2i.net
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
	<mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2005 19:34:09 -0000

On Friday 01 April 2005 16:50, Mike Tancsa wrote:
> At 09:31 AM 01/04/2005, Hans Petter Selasky wrote:
> >What dmsg appears when you attach your device? If "ugen", then make sure
> > you have got "device ucom" and "device uplcom", in the kernel config
> > file. If you are loading "ucom"/"uplcom" from modules, make sure that
> > those modules are re-compiled. Else try to enable debugging and see what
> > happens:
>
> Hi,
>          It was showing up as a ucom device.  Also, the patches no longer
> apply cleanly after the MFCs that were done yesterday afternoon.  I also
> have a CURRENT box I can test against if thats easier to try against. Do
> you know if the patches apply cleanly on it ?
>

Some patches will fail, but that is OK until further. I am not sure if the 
driver will install cleanly with 6-current. Last time I checked was in 
February.

Yours
--HPS