From owner-freebsd-scsi Mon Nov 25 01:29:52 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA20238 for freebsd-scsi-outgoing; Mon, 25 Nov 1996 01:29:52 -0800 (PST) Received: from vcgate3.mei.co.jp (vcgate3.mei.co.jp [202.32.14.53]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA20231; Mon, 25 Nov 1996 01:29:38 -0800 (PST) Received: by vcgate3.mei.co.jp (5.65mei1.2g/5.9:4.9:vcgate0:961113) id AA18288; Mon, 25 Nov 96 18:25:09 +0900 Received: by vcmei.vanc.mei.co.jp (5.65mei1.1/5.9:4.9:vcmei:961120) id AA14142; Mon, 25 Nov 96 18:25:19 +0900 Received: by kmegate.kme.mei.co.jp (4.1/5.5:4.6:kmegate:961122) id AA14112; Mon, 25 Nov 96 18:25:04 JST Date: Mon, 25 Nov 96 18:25:04 JST From: akiyama@kme.mei.co.jp (Shunsuke Akiyama) Message-Id: <9611250925.AA14112@kmegate.kme.mei.co.jp> To: tsbarry@nortel.ca Cc: freebsd-scsi@freebsd.org, hackers@freebsd.org, joerg_wunsch@uriah.heep.sax.de, peter@taronga.com In-Reply-To: <9611221846.AA03508@vcgate1.mei.co.jp> (tsbarry@nortel.ca) Subject: Re: Drive with 1024 byte logical blocks Mime-Version: 1.0 (generated by tm-edit 7.93) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk b a writes: > The changes that John Gumb and I came up with modify > far less code then this patch. Is this patch fixing > extra problems that we missed? That was my version of UFS with 512/1024/2048 byte/sector media patch. It's support VM fix using mmapped access, but not support DOS-FS. > Further you have not patched fdisk or newfs that seem to > be critical to getting a ufs file system onto a disk. I'm only using /sbin/disklabel, but never got a problem. /sbin/fdisk ..., humm, it's not worked for 1024/2048 byte/sector media. -- Shunsuke Akiyama Kyushu Matsushita Electric Co., Ltd. Fukuoka, Japan. akiyama@kme.mei.co.jp From owner-freebsd-scsi Tue Nov 26 15:18:55 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA03738 for freebsd-scsi-outgoing; Tue, 26 Nov 1996 14:36:38 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA03670; Tue, 26 Nov 1996 14:36:22 -0800 (PST) Received: from bnr.ca (x400gate.nortel.ca [192.58.194.73]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id LAA12932 ; Tue, 26 Nov 1996 11:47:41 -0800 (PST) Message-Id: <199611261947.LAA12932@who.cdrom.com> Received: from bcarsfba by bnr.ca id <19961126160657-1@bnr.ca>; Tue, 26 Nov 1996 11:07:43 -0500 Received: from bnr.ca by bcarsfba.bnr.ca id <29339-0@bcarsfba.bnr.ca>; Tue, 26 Nov 1996 11:01:17 -0500 Date: 26 Nov 1996 10:43 EST To: akiyama@kme.mei.co.jp Cc: freebsd-scsi@FreeBSD.org, hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de, peter@taronga.com From: "barry (b.a.) scott" Subject: Re: Drive with 1024 byte logical blocks Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'm only using /sbin/disklabel, but never got a problem. > /sbin/fdisk ..., humm, it's not worked for 1024/2048 byte/sector > media. newfs has tests that the last sector on the new file system can be written. It writes a 512 byte sector to do this test. If this works then you cannot have reliable error checking in your code. It is an error to attempt to write to 1/2 of a sector. BArry From owner-freebsd-scsi Fri Nov 29 14:18:01 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10657 for freebsd-scsi-outgoing; Fri, 29 Nov 1996 14:18:01 -0800 (PST) Received: from ghost.mep.ruhr-uni-bochum.de (ghost.mep.ruhr-uni-bochum.de [134.147.6.16]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA10651 for ; Fri, 29 Nov 1996 14:17:55 -0800 (PST) Received: (from roberte@localhost) by ghost.mep.ruhr-uni-bochum.de (8.7.5/8.7.3) id XAA01440 for scsi@freebsd.org; Fri, 29 Nov 1996 23:17:43 +0100 (MET) From: Robert Eckardt Message-Id: <199611292217.XAA01440@ghost.mep.ruhr-uni-bochum.de> Subject: CACHE TEST FAILED: script execution failed. To: scsi@freebsd.org Date: Fri, 29 Nov 1996 23:17:41 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi All, after experimenting around for a while I'm clue-less how to solve the following problem. The machine is a Pentium-133, 32MB RAM, ASUS-Board (don't know the model-id right now) with 2 NCR controllers, 2GB IBM disk, hp DAT, 7 Teac CDROMs running 2.1.5-RELEASE. I generated a kernel with firewall enabled, superfluous devices disabled and some params tuned (I can send the config file on request). After the problem occurred I tried different combinations but to no avail. When I boot it finds the 1st NCR, all the devices, the 2nd NCR, the error message and goes on with the ISA devices. Nov 27 19:26:07 bug /kernel1: Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 vga0 rev 83 int a irq 15 on pci0:10 ncr0 rev 1 int a irq 9 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:0:0): "IBM DORS-32160 S82C" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 2063MB (4226725 512 byte sectors) sd0(ncr0:0:0): with 6703 cyls, 5 heads, and an average 126 sectors/track (ncr0:2:0): "TEAC CD-ROM CD-56S 1.0B" type 5 removable SCSI 2 cd0(ncr0:2:0): CD-ROM cd0(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. cd present.[319277 x 2048 byte records] (ncr0:3:0): "TEAC CD-ROM CD-56S 1.0B" type 5 removable SCSI 2 cd1(ncr0:3:0): CD-ROM cd1(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. cd1(ncr0:3:0): NOT READY asc:3a,0 Medium not present can't get the size (ncr0:6:0): "HP HP35480A T503" type 1 removable SCSI 2 st0(ncr0:6:0): Sequential-Access st0(ncr0:6:0): 200ns (5 Mb/sec) offset 8. density code 0x13, drive empty ncr1 rev 2 int a irq 12 on pci0:12 CACHE TEST FAILED: script execution failed. CACHE INCORRECTLY CONFIGURED. Probing for devices on the ISA bus: The GENERIC kernel correctly continues: Nov 18 17:09:21 bug /kernel.GENERIC: ncr1 rev 2 int a irq 12 on pci0:12 ncr1 waiting for scsi devices to settle (ncr1:2:0): "TEAC CD-ROM CD-56S 1.0B" type 5 removable SCSI 2 cd2(ncr1:2:0): CD-ROM [....] In the beginning I found that the CACHE TEST FAILED appeared when SCSI_DELAY=15 was NOT in. After putting this option in it detected all devices on the second SCSI bus, however it panicked after `changing root device to sd0a'. I further reduced the configuration and now I get CACHE TEST FAILED with SCSI_DELAY=15 included! (What cache, what script ???) Since I know for sure that the provided information is not what is needed and the important information is missing, any response that helps me to find out what goes wrong is appreciated. Thanks, Robert -- Robert Eckardt \\ FreeBSD -- solutions for a large universe.(tm) RobertE@MEP.Ruhr-Uni-Bochum.de \\ What do you want to boot tomorrow ?(tm) http://WWW.MEP.Ruhr-Uni-Bochum.de/~roberte For PGP-key finger roberte@gluon.MEP.Ruhr-Uni-Bochum.de From owner-freebsd-scsi Sat Nov 30 10:12:28 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28662 for freebsd-scsi-outgoing; Sat, 30 Nov 1996 10:12:28 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28649 for ; Sat, 30 Nov 1996 10:12:19 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA00323 (5.67b/IDA-1.5 for ); Sat, 30 Nov 1996 19:12:10 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.3/8.6.9) id QAA01069; Sat, 30 Nov 1996 16:57:28 +0100 (CET) Message-Id: Date: Sat, 30 Nov 1996 16:56:07 +0100 From: se@freebsd.org (Stefan Esser) To: roberte@mep.ruhr-uni-bochum.de (Robert Eckardt) Cc: scsi@freebsd.org Subject: Re: CACHE TEST FAILED: script execution failed. References: <199611292217.XAA01440@ghost.mep.ruhr-uni-bochum.de> X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: <199611292217.XAA01440@ghost.mep.ruhr-uni-bochum.de>; from Robert Eckardt on Nov 29, 1996 23:17:41 +0100 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Nov 29, roberte@mep.ruhr-uni-bochum.de (Robert Eckardt) wrote: > Hi All, > > after experimenting around for a while I'm clue-less how to solve > the following problem. > > The machine is a Pentium-133, 32MB RAM, ASUS-Board (don't know the model-id > right now) with 2 NCR controllers, 2GB IBM disk, hp DAT, 7 Teac CDROMs > running 2.1.5-RELEASE. > I generated a kernel with firewall enabled, superfluous devices disabled > and some params tuned (I can send the config file on request). > After the problem occurred I tried different combinations but to no avail. > > When I boot it finds the 1st NCR, all the devices, the 2nd NCR, the > error message and goes on with the ISA devices. > > Nov 27 19:26:07 bug /kernel1: > Probing for devices on PCI bus 0: > ncr0 rev 1 int a irq 9 on pci0:11 > ncr1 rev 2 int a irq 12 on pci0:12 > CACHE TEST FAILED: script execution failed. The code for this is at the end of the NCR driver (/sys/pci/ncr.c). Look for the function ncr_snooptest() ... It tries to make the NCR execute a very simple program, which in fact only reads and writes some variables in the host systems memory space. The code waits a few hundred microseconds for the NCR chip to reach an INT instruction. If there is no interrupt in time, then the NCR appears to not be able to execute any instructions at all ... If the NCR fails to complete this simple test program within a few tens of microseconds, then there is no chance it will later be able to execute the "microcode" that makes it perform SCSI transactions. > The GENERIC kernel correctly continues: > Nov 18 17:09:21 bug /kernel.GENERIC: > ncr1 rev 2 int a irq 12 on pci0:12 > ncr1 waiting for scsi devices to settle > (ncr1:2:0): "TEAC CD-ROM CD-56S 1.0B" type 5 removable SCSI 2 > cd2(ncr1:2:0): CD-ROM > [....] > > > In the beginning I found that the CACHE TEST FAILED appeared when > SCSI_DELAY=15 was NOT in. After putting this option in it detected > all devices on the second SCSI bus, however it panicked after > `changing root device to sd0a'. Hmmm, that's really strange ... Did you try swapping controller cards ??? > I further reduced the configuration and now I get CACHE TEST FAILED > with SCSI_DELAY=15 included! > (What cache, what script ???) See above. I can send you my phone number, if you want to discuss further details and ways to test this ... > Since I know for sure that the provided information is not what is needed > and the important information is missing, any response that helps me to > find out what goes wrong is appreciated. I actually don't understand what is failing. But we might get it narrowed down with some tests. For example, I'd need to know, whether the second NCR chip does execute any instructions at all, or whether it can't be activated. The GENERIC kernel should have been built with FAILSAVE #defined. But I do not see how that might make a difference for the early probe phase that is causing you problems. You may try a custom kernel with "options FAILSAFE" anyway ... Regards, STefan From owner-freebsd-scsi Sat Nov 30 18:33:40 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA26717 for freebsd-scsi-outgoing; Sat, 30 Nov 1996 18:33:40 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA26712; Sat, 30 Nov 1996 18:33:37 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id TAA03299; Sat, 30 Nov 1996 19:33:37 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id TAA05070; Sat, 30 Nov 1996 19:32:28 -0700 (MST) Date: Sat, 30 Nov 1996 19:32:28 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: hardware@freebsd.org cc: scsi@freebsd.org, Greg Skafte Subject: Re: Tekram 390U and Seagate hawk ST32151N In-Reply-To: <57pc97$hcm@news.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [Sent to hardware and scsi; unless you have a reason, please followup to only one list. scsi is probably better, since it is dealing with freebsd drivers now.] Nickolay's suggestion worked, so now we can get past the BIOS probing stage. However, FreeBSD still won't boot. I am using -stable with the NCR driver (ncr.c and ncrregs.h) from -current dropped in. A 300 meg drive will work fine, but when it tries to probe the 2 gig hawk we get something like: sd0(ncr0:4:0): COMMAND failed (9 ff) @[address] sd0 could not get size error ncr0: aborting job ERROR (90:0) (0-21-15) (0/13) @ (418:43000060) script cmd = 878b0000 reg : [deleted] ncr0: restart failed That is not exact and doesn't include some of the important stuff for debugging it, but I don't have a copy of the full message right now. Booting with a 2.2-ALPHA disk works fine, so either I missed something from the NCR stuff between stable and current or there was another change that fixed this. Anyone have any ideas about what it could be? Nothing stood out in the CVS logs as being obvious. If all else fails, we just have to move to 2.2 which won't kill us, but we would prefer not to for this machine. On 30 Nov 1996, Nickolay N. Dudorov wrote: > Marc Slemko wrote: > > Anyone have any trouble making a Tekram 390U SCSI controller work with > > certain disks? What we are seeing is that it hangs on probing the disks > > after the SCSI bios is installed, but if you go into the bios setup it can > > probe them, scan them, etc. with no problems. It works fine with tape > > drives and an old 300 meg drive we tried. > > > Tried lowering the SCSI bus speed, disabling things that could cause > > problems, etc. See the same thing when we try it with a different type of > > Seagate. Yes, the bus is properly terminated and we have tried multiple > > cables. > > > No, the question isn't really freebsd specific but there has been some > > discussion of the Tekram here a while back.... > > Last week I also encounter a problem with Tekram DC-390F > controller and CONNER CFP2105S disk (which also has some Seagate > name on it ;). This disk was previously used with NCR 53c810-based > controller AND was Dangerously Dedicated to FreeBSD. Tekram's > BIOS hangs on identifing the disk, but successfully sees it when > in it's setup. I solve my problem by re-fdisking disk to non-DD > mode with old controller. > This is definitely Tekram BIOS bug - if it does'nt like > DD disk it can just skip it and not hung forever ;-). > > P.S. Are there any plans/shedules to support extened features > of 53c875-based controllers in ncr-driver ? > (It'll be very good ULTRA WIDE SCSI controller for ~150$ > here in Siberia) > > N.Dudorov >