From owner-freebsd-scsi Fri Dec 8 22:38:57 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA29729 for freebsd-scsi-outgoing; Fri, 8 Dec 1995 22:38:57 -0800 (PST) Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA29724 for ; Fri, 8 Dec 1995 22:38:53 -0800 (PST) Received: (from rmallory@localhost) by wiley.csusb.edu (8.6.11/8.6.11) id WAA08263; Fri, 8 Dec 1995 22:43:24 -0800 From: Rob Mallory Message-Id: <199512090643.WAA08263@wiley.csusb.edu> Subject: Re: Check back Re: Problem with IBM 2 gig To: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 8 Dec 1995 22:43:24 -0800 (PST) Cc: scsi@FreeBSD.org In-Reply-To: <199512081523.AA26892@Sysiphos> from "Stefan Esser" at Dec 8, 95 04:23:21 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk > } looks like a power glitch.. are those devices in an external cabinet? > } OR > } possibly the ncd drive detected a hang and reset the scsi bus.. > } > } what do you think stefan? > } julian > > Thanks for forwarding the message ... > > It is quite funny to see this (and the other messages) > appear twice ... Never observed that before ... syslog... [from syslog.conf, which is the same in -current] *.err root *.notice;auth.debug root *.alert root both an err and an alert? ...I also get dual 'root login on...':) 'think I'll quiet it up tonight..:) [..excellent man(9) material omited..] [[man-9 material is the (understandably) commonly omited 'vaporware' pages where the authors and gurus describe their internals of their drivers:]] > } > Dec 3 22:56:05 kickme /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred I usualy look first to termination/cable problems when I see this. but this bus is all on one ribbon. (6 devices, 2 or 3 of which are moving to my new 810 (see next message:)) > The same in text form ... > > I'm a little confused about the two identical error messages. > The commands in question are one and the same (as the @f0aa8a00 > command control block address proves). > > > If this remains a single case, thaen I'd say it most likely was > a glitch. The driver was in an consistent state, and the NCR > seems to have missed the fact, that the bus was ready for the > requested command transfer, according to the SCSI control lines > printed in the error message. > I'll keep my eye out, and pull out the dvm the next time,, the machine is(has been) on a smartUPS, so my roommate's room heater only flickers my lights now;) > The timeout lead to a SCSI bus reset, but the generic SCSI code > should have resent the command to the hard disk, and if the > CDROM did not lock up internally, then it should have been able > to continue normal operation as well. > > Or did the system crash as a result ??? nope. the plextor was hung hard, with the orange and green lights on. the scsi bus was ok, and the disk sync'd right after. manual reboot soon followed. [new scsi bus described in next message] thanks! -rob > > > Regards, STefan > > -- > Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 > Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 > ============================================================================== > http://www.zpr.uni-koeln.de/~se >