Date: Wed, 30 Oct 1996 17:42:34 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Johann Visagie <jvisagie@insight.co.za> Cc: questions@freebsd.org Subject: Re: df crashes 2.1.0-R (?!) Message-ID: <Pine.BSI.3.94.961030174129.1988C-100000@gdi.uoregon.edu> In-Reply-To: <m0vIW1q-000vCVC@asterix.insight.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 30 Oct 1996, Johann Visagie wrote: > I'm running 2.1.0-R on a Compaq Prosignia 300 (it wasn't my idea! :) I'm surprised the ncr even probed. Compaqs have a proven broken PCI impelmentation. > I'm using the machine's on-board SCSI host adapter (NCR chipset), and I've > been experiencing intermittent problems for some time now. At apparently > random times, the SCSI subsystem would just appear to enter an unstable > state, resulting in the following sort of messages flooding to the logs: > > Oct 29 11:00:38 asterix /kernel: ncr0: have to clear fifos. > Oct 29 11:00:38 asterix /kernel: ncr0: restart (fatal error). > Oct 29 11:00:38 asterix /kernel: sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f0e7d000. > Oct 29 11:00:38 asterix /kernel: NOT READY asc:4,1 > Oct 29 11:00:39 asterix /kernel: sd0(ncr0:0:0): Logical unit is in process of becoming ready > Oct 29 11:00:39 asterix /kernel: , FAILURE I would say that the adapter is bad or you have termination / cable problems. Wrong termination has been known to cause screwier problems. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.94.961030174129.1988C-100000>