From owner-freebsd-current@FreeBSD.ORG  Fri Sep 26 06:38:11 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9EBC516A4B3; Fri, 26 Sep 2003 06:38:11 -0700 (PDT)
Received: from ms-smtp-01.southeast.rr.com (ms-smtp-01.southeast.rr.com
	[24.93.67.82])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C3A184401E; Fri, 26 Sep 2003 06:38:09 -0700 (PDT)
	(envelope-from morganw@chemikals.org)
Received: from volatile.chemikals.org (cpe-024-211-116-193.sc.rr.com
	[24.211.116.193])h8QDUcA7021940;
	Fri, 26 Sep 2003 09:30:38 -0400 (EDT)
Received: from localhost (morganw@localhost [127.0.0.1])
	h8QDc69G025836;	Fri, 26 Sep 2003 09:38:08 -0400 (EDT)
	(envelope-from morganw@chemikals.org)
Date: Fri, 26 Sep 2003 09:38:06 -0400 (EDT)
From: Wesley Morgan <morganw@chemikals.org>
To: Brian Fundakowski Feldman <green@freebsd.org>
In-Reply-To: <200309260518.h8Q5I8H2029138@green.bikeshed.org>
Message-ID: <20030926093535.A96532@volatile.chemikals.org>
References: <200309260518.h8Q5I8H2029138@green.bikeshed.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: yep, umass still broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2003 13:38:11 -0000

On Fri, 26 Sep 2003, Brian Fundakowski Feldman wrote:

> I can get fdisk to read the MBR, but when I try mdir, I get this trace back
> (of course, no crash dump because those haven't worked for me in a year):
> trap 0xc
> memcpy()
> ohci_softintr()
> usb_schedsoftintr()
> ohci_intr1()
> ohci_intr()
> ithread_loop()
>
> Anyone have any clued?  I'll include my dmesg, of course.

It was unbroken for a while, but has been broken for at least a month
(seem my earlier post about it). The umass driver has been a constant
source of frustation for me and suffers from constant breakage and
neglect.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!