From owner-freebsd-current Sun Apr 29 2:20: 7 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 58DAD37B423 for ; Sun, 29 Apr 2001 02:20:04 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA18631 for freebsd-current@freebsd.org; Sun, 29 Apr 2001 11:20:03 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3T8q2K75150; Sun, 29 Apr 2001 10:52:02 +0200 (MET DST) (envelope-from j) Date: Sun, 29 Apr 2001 10:52:02 +0200 (MET DST) Message-Id: <200104290852.f3T8q2K75150@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: camcontrol stop / restart broken X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomi Vainio - Sun Finland - wrote: > My source disk is quite noisy so normally I stop it after building the > world and restart it once a week. Couple weeks this restart hasn't > worked as before. Oh, now that you mention it, i've seen that before, too. I didn't pay too much attention then since i initially thought that particular disk wasn't quite OK together with my new controller (the Tekram BIOS also has problems if the drive isn't spun-up at boot time). But now that i've seen the same kind of behaviour for other devices (like a scanner that has been power-cycled), i see the correlation to the CAM error handling changes here as well. If you don't get a reply here, please repost to freebsd-scsi@freebsd.org. If you look into the archives of that list, you can see some other discussions about the new error handling. Note that it's most likely not the rewritten error handling itself, but rather that the rewrite uncovered bugs in the top-layer SCSI drivers. > Only way to start disk again is reboot. Disconnecting (or powering off the drive), "camcontrol rescan", reconnect, "camcontrol rescan" would probably work as well. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message