From owner-freebsd-usb@FreeBSD.ORG  Wed Dec  1 03:11:18 2004
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 5ABBE16A4CE
	for <freebsd-usb@freebsd.org>; Wed,  1 Dec 2004 03:11:18 +0000 (GMT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id A098543D41
	for <freebsd-usb@freebsd.org>; Wed,  1 Dec 2004 03:11:17 +0000 (GMT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa44210@salmon>; 1 Dec 2004 03:11:16 +0000 (GMT)
To: Mike Holcomb <mike.holcomb@gmail.com>
In-Reply-To: Your message of "Tue, 30 Nov 2004 08:58:05 PST."
             <f78e7b3f04113008586b29826e@mail.gmail.com> 
Date: Wed, 01 Dec 2004 03:11:16 +0000
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID: <200412010311.aa44210@salmon.maths.tcd.ie>
cc: freebsd-usb@freebsd.org
Subject: Re: kern/71491: [usb] [panic] printing under usb printer causes a
	kernel panic 
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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: Wed, 01 Dec 2004 03:11:18 -0000

In message <f78e7b3f04113008586b29826e@mail.gmail.com>, Mike Holcomb writes:
>I was wondering if this fix is going to go into -STABLE?
>
>If so, any ideas on a time estimate?

I've just MFC'd most of the recent USB framework and host controller
changes to RELENG_5, and Julian has merged many changes into RELENG_4.
Could you check to see if you can reproduce the problem with a
recent -STABLE?

Ian