From owner-freebsd-current@FreeBSD.ORG Mon Aug 25 15:02:37 2003 Return-Path: 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 A64A416A4BF for ; Mon, 25 Aug 2003 15:02:37 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E6C243FAF for ; Mon, 25 Aug 2003 15:02:37 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 18654 invoked by uid 1000); 25 Aug 2003 22:02:38 -0000 Date: Mon, 25 Aug 2003 15:02:38 -0700 (PDT) From: Nate Lawson To: Lars Eggert In-Reply-To: <3F4A8446.30504@isi.edu> Message-ID: <20030825150135.C18645@root.org> References: <20030825141234.Q18452@root.org> <3F4A8446.30504@isi.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: panic with CF drive + USB reader X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 25 Aug 2003 22:02:37 -0000 On Mon, 25 Aug 2003, Lars Eggert wrote: > Nate Lawson wrote: > >>this happens with an IBM MicroDrive mounted on a USB CF reader, -current > > > >>from 8/19/03. I couldn't get a coredump: > > > >>umass0: BBB reset failed, STALLED > >>(da2:umass-sim0:0:0:0): AutoSense Failed > >>umass0: BBB reset failed, STALLED > >>(da2:umass-sim0:0:0:0): AutoSense Failed > >>panic: softdep_setup_freeblocks: inode busy > >>da2 at umass-sim0 bus 0 target 0 lun 0 > >>da2: Removable Direct Access SCSI-2 device > >>da2: 1.000MB/s transfers > >>da2: 1027MB (2104705 512 byte sectors: 255H 63S/T 131C) > > > > Your microdrive may need some USB quirks. Try RS_NO_CLEAR_UA (see > > /sys/dev/usb/umass.c for examples). > > Thanks, I'll try that. It also complains during boot about not > supporting Get Max Lun, so that's a quirk also. No, that's likely not a quirk. Complaining is ok if it doesn't cause actual problems (i.e. can't mount partition). Try one quirk at a time until it works. > Do you have any guesses what combination to use for the wire and command > protocol fields for this device? Copy a BBB line most likely. -Nate