From owner-freebsd-current@FreeBSD.ORG  Thu Jul 31 00:39:19 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 2E62437B404
	for <current@freebsd.org>; Thu, 31 Jul 2003 00:39:19 -0700 (PDT)
Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net
	[207.217.120.218])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9BD4E43FBD
	for <current@freebsd.org>; Thu, 31 Jul 2003 00:39:18 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from user-38lc0sl.dialup.mindspring.com ([209.86.3.149]
	helo=mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)	id 19i81Y-00009v-00; Thu, 31 Jul 2003 00:38:56 -0700
Message-ID: <3F28C74C.5CFB7669@mindspring.com>
Date: Thu, 31 Jul 2003 00:37:48 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: John Hay <jhay@icomtek.csir.co.za>
References: <20030730055859.GA15943@zibbi.icomtek.csir.co.za>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4098888a8d10a37d24682a38d25c80a81350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
cc: current@freebsd.org
cc: nate@root.org
Subject: Re: strange umass/scsi behaviour
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: Thu, 31 Jul 2003 07:39:19 -0000

John Hay wrote:
> Does anyone have an idea why the umass/scsi code behave differently
> between if you boot with a device already plugged in as opposed to
> plugging it in later? In my case it is a Sandisk Cruiser. If I plug
> it in before booting, it works just great, but if I plug it in later,
> it does not want to work.
> 
> Below is the dmesg output of the various stages.
[ ... ]

I had a disk that would behave in exactly this way.

Try this:

	camcontrol debug -I -P -T -S -X -c 0:0:0
	camcontrol reset 0:0:0
	camcontrol rescan 0:0:0

Probably it will "just work" after the "reset/rescan without the
debug; the disk I had wanted an explicit bus reset after it was
connected, and that made it happy.

-- Terry