Date: Thu, 31 Jul 2003 00:37:48 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: John Hay <jhay@icomtek.csir.co.za> Cc: nate@root.org Subject: Re: strange umass/scsi behaviour Message-ID: <3F28C74C.5CFB7669@mindspring.com> References: <20030730055859.GA15943@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F28C74C.5CFB7669>