From owner-freebsd-current Thu Sep 14 05:56:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA09418 for current-outgoing; Thu, 14 Sep 1995 05:56:06 -0700 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA09412 ; Thu, 14 Sep 1995 05:56:01 -0700 Received: from wup-gate.UUCP (uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) with UUCP id OAA26604; Thu, 14 Sep 1995 14:55:50 +0200 Received: from wup.de by wup-gate with smtp (Smail3.1.28.1 #2) id m0stDtH-0007rLC; Thu, 14 Sep 95 14:59 MET DST Received: from sunny.wup.de by wup.de (4.1/SMI-4.1) id AA18065; Thu, 14 Sep 95 14:50:15 +0200 Received: by sunny.wup.de (5.x/SMI-SVR4) id AA10430; Thu, 14 Sep 1995 14:53:08 +0200 Date: Thu, 14 Sep 1995 14:53:08 +0200 From: Andreas Klemm Message-Id: <9509141253.AA10430@sunny.wup.de> To: larry@seminole.iag.net Subject: SCSI problems with FreeBSD 2.0.5 using AHA 2940 and Quantum Grand Prix Cc: jhk@freebsd.org, hackers@freebsd.org, current@freebsd.org Content-Type: X-sun-attachment Sender: current-owner@freebsd.org Precedence: bulk ---------- X-Sun-Data-Type: text X-Sun-Data-Description: text X-Sun-Data-Name: text X-Sun-Charset: us-ascii X-Sun-Content-Lines: 100 Subject: Re: SCSI errors 2.0.5 FreeBSD "sd0 timed out" Newsgroups: comp.periphs.scsi,comp.unix.bsd.freebsd.misc In article <42o73m$6vr@news.iag.net> you wrote: : I have an Opti based Pentium 100 Mhz motherboard with 32 : megs of RAM. The PCI controller is a 2940 and the hard : drive is a Quantum XP series 2 gig drive. The OS is Free : BSD 2.0.5. : With heavy DiskIO I see: : ahc0: target 0, lun 0, (sd0) timed out This happens to me, too, sometimes. : on the console. all diskIO is stopped, and the LED on : the SCSI host adapter and hard drive are on solid Yes ! : this happens with heavy disk IO with the configuration : supporting 10 mhz transfers rates and sync transfers : enabled My scenario: Asus P/I 55TP4XE board, P90, 256k synchr. cache, AHA 2940 BIOS V1.16, Toshiba 3601 CD-Rom, Quantum Grand Prix 4GB 7200U/min. Parity enabled on all devices, as well as 10MB synchr. My problems started with Termination pronlems. Here how I solved it, but problems remain ... The system locked up more frequently under FreeBSD and Linux, when I had the following order on the scsi bus: 2940-----------Hd-------------CD-Rom Termin. X X Putting the harddisk onto the end of the scsi bus I have much less problems: 2940-----------CD-------------HD Termin. X X Before that I tried nearly every combination of SCSI - Termination ;-) But still somethimes seems to break ... I had 4 OS on the Harddisk Slice 1 primary DOS - 250 MB DOS Slice 2 other - 3 GB FreeBSD Slice 3 Ext. Part - 500 MB Win NT 351 AS Slice 4 " - 400 MB Linux Slackware 2.3 - accessable via boot disk The FreeBSD bootmanager is _the_ boot manager on my system. So I have to take care to use this order during installation: DOS, FreeBSD partitioning, Windows NT, Linux, FreeBSD installation. When I had the disk in the middle of the scsi bus, then the Linux distrib with 1.2.12 kernel fucked up after installing about 75% of the packages. Now it works nearly flawlessly. But then after a few days again some drawbacks ... The Extended partition couldn't be accessed any more. The first warnings about a bad extended partition I received during the FreeBSD startup. After that I installed everything new ... But I left out Linux. So I have now DOS,NT,FreeBSD, to speed up installing everything again... But working for a while I get strange results again.... Under FreeBSD I noticed in /usr 1 dir and one file with control characters. When trying to boot WinNT I can't boot NT from one day to another, because ntdetect was screwed up ... I should install this file new ... Is the hardware so weak, that it can't drive 10MB/sec synchronously without loosing data ????? Or is it due to driver problems ???? The only OS, where I have no crashes in the moment is DOS/Windows 3.11. BTW: Everything is terminated properly, and I enabled Parity checking on all devices !! Hope, that -stable will help me out of this situation, if it should be a driver problem. BTW: I made a copy for thr freebsd mailinglists ... Since I'm not reading these lists currently, please write a cc: to my e-mail address, too Best regards Andreas /// -- andreas@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - ---------- X-Sun-Data-Type: default X-Sun-Data-Description: default X-Sun-Data-Name: .signature X-Sun-Charset: us-ascii X-Sun-Content-Lines: 2 andreas@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix -