From owner-freebsd-scsi Sun Oct 4 00:02:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24687 for freebsd-scsi-outgoing; Sun, 4 Oct 1998 00:02:01 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles144.castles.com [208.214.165.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA24668; Sun, 4 Oct 1998 00:01:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA02436; Sun, 4 Oct 1998 00:06:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810040706.AAA02436@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: mike@smith.net.au, Don.Lewis@tsc.tdk.com, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, gibbs@plutotech.com, tlambert@primenet.com Subject: Re: filesystem safety and SCSI disk write caching In-reply-to: Your message of "Sun, 04 Oct 1998 16:16:24 +1000." <199810040616.QAA26536@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Oct 1998 00:06:15 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> Yes, the default configuration may be much slower than mine. > > > >I can definitely back your basic point ('make world' is CPU bound) up. > >On a 4-way Xeon system with slow disks we were still able to get down > >around 40 minutes. > > Er, that shows that it is i/o bound on systems with so much CPU. I > got it down to 75 minutes on 1-way K6-233 with 1 IDE disk before it > was bloated by perl5 and transition to elf. Moving to an MFS only saved about 15% of the build time. My point was that a faster CPU let you go faster. If the build was I/O bound, it wouldn't. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 4 03:33:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15490 for freebsd-scsi-outgoing; Sun, 4 Oct 1998 03:33:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15457; Sun, 4 Oct 1998 03:32:45 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from [158.152.46.40] (helo=ragnet.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.03 #1) id 0zPlSe-0003Yz-00; Sun, 4 Oct 1998 10:32:20 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0zPlSW-0006jk-00; Sun, 4 Oct 1998 11:32:12 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199810040616.QAA26536@godzilla.zeta.org.au> Date: Sun, 04 Oct 1998 11:32:12 +0100 (BST) From: Duncan Barclay To: Bruce Evans Subject: Re: filesystem safety and SCSI disk write caching Cc: tlambert@primenet.com, gibbs@plutotech.com, freebsd-scsi@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG, Don.Lewis@tsc.tdk.com, mike@smith.net.au Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 04-Oct-98 Bruce Evans wrote: >>> Yes, the default configuration may be much slower than mine. >> >>I can definitely back your basic point ('make world' is CPU bound) up. >>On a 4-way Xeon system with slow disks we were still able to get down >>around 40 minutes. > > Er, that shows that it is i/o bound on systems with so much CPU. I > got it down to 75 minutes on 1-way K6-233 with 1 IDE disk before it > was bloated by perl5 and transition to elf. > > Bruce I would agree, my AMD K6-233 did a make -j 4 in jst over an hour with src on IDE mounted async and obj on SCSI mounted async (this was upgrading from 2.2.6). I haven't tried it under -3.0 and softupdates yet. Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 4 06:26:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08958 for freebsd-scsi-outgoing; Sun, 4 Oct 1998 06:26:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08953; Sun, 4 Oct 1998 06:26:01 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id PAA07587; Sun, 4 Oct 1998 15:25:32 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA00898; Sun, 4 Oct 1998 15:25:29 +0200 (MET DST) Message-ID: <19981004152528.12252@follo.net> Date: Sun, 4 Oct 1998 15:25:28 +0200 From: Eivind Eklund To: Mike Smith , Bruce Evans Cc: Don.Lewis@tsc.tdk.com, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, gibbs@plutotech.com, tlambert@primenet.com Subject: Re: filesystem safety and SCSI disk write caching References: <199810040616.QAA26536@godzilla.zeta.org.au> <199810040706.AAA02436@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810040706.AAA02436@dingo.cdrom.com>; from Mike Smith on Sun, Oct 04, 1998 at 12:06:15AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Oct 04, 1998 at 12:06:15AM -0700, Mike Smith wrote: > > >> Yes, the default configuration may be much slower than mine. > > > > > >I can definitely back your basic point ('make world' is CPU bound) up. > > >On a 4-way Xeon system with slow disks we were still able to get down > > >around 40 minutes. > > > > Er, that shows that it is i/o bound on systems with so much CPU. I > > got it down to 75 minutes on 1-way K6-233 with 1 IDE disk before it > > was bloated by perl5 and transition to elf. > > Moving to an MFS only saved about 15% of the build time. My point was > that a faster CPU let you go faster. If the build was I/O bound, it > wouldn't. My hypothesis is that for the high end boxes, 'make world' is mostly bound by memory bandwidth. This is what seems to best match the speed patterns people have been reporting. Unfortunately, I can only think of a single way of verifying this: Running a PPro build in 64-bit mode and 128-bit mode, with the same amount of the same speed memory. It would require a motherboard that had 128-bit support; AFAIK, this is only present in the early Intel boards :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 4 09:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21659 for freebsd-scsi-outgoing; Sun, 4 Oct 1998 09:02:16 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21652 for ; Sun, 4 Oct 1998 09:02:09 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id SAA02050 for freebsd-scsi@freebsd.org; Sun, 4 Oct 1998 18:01:45 +0200 (SAT) From: John Hay Message-Id: <199810041601.SAA02050@zibbi.mikom.csir.co.za> Subject: cam panic... probably tag related To: freebsd-scsi@FreeBSD.ORG Date: Sun, 4 Oct 1998 18:01:45 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org System is a dual 266MHz PII with Asus motherboard with Adaptec 7880 on board and a Seagate ST34572N as drive 0 and a Conner CFP4207S as drive 2. Everything is on the Seagate except /usr/obj which is symlinked to the Conner. It is running a very up to date -current and using softupdates on all partitions. The machine will panic sometimes during a "make world" especially with a high -j value, but it panics in such a way that it does not leave a dump. What is strange to me is that it seems that the cam code catches the problem and try to recover from it, but the machine still panic. Should cam be able to recover from it? The panic is in acquire_lock() in the softupdate code (I have added a piece of "nm -aout kernel" at the end of this email), but I don't really think it is to blame for the panic. I have build a quirk entry for the Conner drive to limit the tags to max 24 and have now successfully done more than 20 "make world -j24"s without a panic, where previously it would panic within about 3. I have added a diff for the quirk entry at the end. About the minimum number of tags I just took a random number smaller than the max. :-) I'm not sure what it should be. Here is the output on the serial console preceding the panic and also the probe info during the reboot afterwards, with unrelated things here and there removed, just incase it is usefull to someone. The first 3 lines come fairly quickly after I start a make world. I understand them and just left them in for completeness. --------------------------------------------------------------------------- (da1:ahc0:0:2:0): tagged openings now 32 (da1:ahc0:0:2:0): tagged openings now 31 (da0:ahc0:0:0:0): tagged openings now 63 ... Long delay depending on how long it takes to get it to panic ... (da1:ahc0:0:2:0): SCB 0x2d - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0x9 SSTAT1 == 0xa (da1:ahc0:0:2:0): Queuing a BDR SCB (da1:ahc0:0:2:0): Bus Device Reset Message Sent (da1:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:2. 31 SCBs aborted (da1:ahc0:0:2:0): tagged openings now 32 Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0192468 stack pointer = 0x10:0xff804ca8 frame pointer = 0x10:0xff804cac code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... Fatal trap 12: page fault while in kernel mode mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0192468 stack pointer = 0x10:0xff804a8c frame pointer = 0x10:0xff804a90 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 dumping to dev 20401, offset 557056 dump Fatal trap 12: page fault while in kernel mode mp_lock = 01000004; cpuid = 1; lapic.id = 00000000 fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0192468 stack pointer = 0x10:0xff804594 frame pointer = 0x10:0xff804598 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000004; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 dumping to dev 20401, offset 557056 dump device not ready Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock for BSP cpu_reset_proxy: Stopped CPU 1 ... >> FreeBSD BOOT @ 0x10000: 640/65472 k of memory, serial console Boot default: 0:sd(0,a)kernel ... total=0x23a0d4 entry point=0x100000 Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #9: Fri Oct 2 16:16:08 SAST 1998 jhay@beast.mikom.csir.co.za:/usr/src/sys/compile/BEAST Timecounter "i8254" frequency 1193561 Hz cost 3246 ns CPU: Pentium II (686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80fbff real memory = 134217728 (131072K bytes) avail memory = 128409600 (125400K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 chip3: rev 0x01 int d irq 9 on pci0.4.2 chip4: rev 0x01 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x04 int a irq 18 on pci0.10.0 fxp0: Ethernet address 00:a0:c9:8d:7c:5f fxp1: rev 0x04 int a irq 17 on pci0.11.0 fxp1: Ethernet address 00:a0:c9:8d:74:dd vga0: rev 0x01 int a irq 16 on pci0.12.0 Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 8) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) changing root device to da0s1a ... (da0:ahc0:0:0:0): tagged openings now 64 (da0:ahc0:0:0:0): tagged openings now 63 --------------------------------------------------------------------------- Here is the "nm -aout kernel" part around the panic. --------------------------------------------------------------------------- f0192370 F ffs_softdep.o f0192370 F ffs_softdep_stub.o f0192424 t _acquire_lock f0192498 t _free_lock f019251c t _acquire_lock_interlocked f0192590 t _free_lock_interlocked --------------------------------------------------------------------------- --------------------------------------------------------------------------- Index: sys/cam/cam_xpt.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_xpt.c,v retrieving revision 1.15 diff -u -r1.15 cam_xpt.c --- cam_xpt.c 1998/10/02 21:00:50 1.15 +++ cam_xpt.c 1998/10/04 06:47:44 @@ -233,12 +233,18 @@ #endif }; +static const char conner[] = "CONNER"; static const char quantum[] = "QUANTUM"; static const char sony[] = "SONY"; static const char west_digital[] = "WDIGTL"; static struct xpt_quirk_entry xpt_quirk_table[] = { + { + /* Sometimes gets stuck */ + { T_DIRECT, SIP_MEDIA_FIXED, conner, "CFP4207S*", "*" }, + /*quirks*/0, /*mintags*/8, /*maxtags*/24 + }, { /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100*", "*" }, John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 4 09:32:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24692 for freebsd-scsi-outgoing; Sun, 4 Oct 1998 09:32:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles320.castles.com [208.214.167.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24673 for ; Sun, 4 Oct 1998 09:32:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA05273; Sun, 4 Oct 1998 09:37:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810041637.JAA05273@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related In-reply-to: Your message of "Sat, 04 Oct 1998 18:01:45 +0200." <199810041601.SAA02050@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Oct 1998 09:37:06 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (... describes perhaps a problem with a drive that doesn't do TCQ properly ...) If it were feasible, I think it might be a good idea to disable tagged commands if FAILSAFE is defined. It would, at least, be in keeping with the spirit of the define. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 4 20:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24228 for freebsd-scsi-outgoing; Sun, 4 Oct 1998 20:58:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24146; Sun, 4 Oct 1998 20:58:24 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id VAA05121; Sun, 4 Oct 1998 21:57:52 -0600 (MDT) Message-Id: <199810050357.VAA05121@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: gibbs@plutotech.com (Justin T. Gibbs), julian@whistle.com, Don.Lewis@tsc.tdk.com, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: filesystem safety and SCSI disk write caching In-reply-to: Your message of "Sat, 03 Oct 1998 01:08:48 -0000." <199810030108.SAA02581@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Oct 1998 21:51:23 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> >I told you so. >> >> You told me some things that were in-correct and some things that >> I already knew. Par for the course. > >Feel free to make his setup work with SCSI write caching enabled. I gave the recipe for this on freebsd-alpha near the end of september. 1) Use a UPS. 2) Use a drive with non-bogus firmware. Recent Seagate and IBM drives should work just fine. I haven't validated any Quantum drives in this regard yet. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 5 10:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21897 for freebsd-scsi-outgoing; Mon, 5 Oct 1998 10:57:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21879; Mon, 5 Oct 1998 10:57:42 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id KAA28142; Mon, 5 Oct 1998 10:57:17 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd028058; Mon Oct 5 10:57:08 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id KAA20911; Mon, 5 Oct 1998 10:57:02 -0700 (MST) From: Terry Lambert Message-Id: <199810051757.KAA20911@usr01.primenet.com> Subject: Re: filesystem safety and SCSI disk write caching To: gibbs@plutotech.com (Justin T. Gibbs) Date: Mon, 5 Oct 1998 17:57:01 +0000 (GMT) Cc: tlambert@primenet.com, gibbs@plutotech.com, julian@whistle.com, Don.Lewis@tsc.tdk.com, freebsd-fs@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199810050357.VAA05121@pluto.plutotech.com> from "Justin T. Gibbs" at Oct 4, 98 09:51:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I gave the recipe for this on freebsd-alpha near the end of september. > > 1) Use a UPS. > > 2) Use a drive with non-bogus firmware. Recent Seagate and IBM > drives should work just fine. I haven't validated any Quantum > drives in this regard yet. I think the base assumption should be that the firmware is bogus, unless proven otherwise. You could have a "known good" table; I think a "known rogues" table would be too large. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Oct 5 17:25:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14159 for freebsd-scsi-outgoing; Mon, 5 Oct 1998 17:25:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from amber.eaznet.com (amber.eaznet.com [216.19.20.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13465 for ; Mon, 5 Oct 1998 17:23:16 -0700 (PDT) (envelope-from eddie@eaznet.com) Received: from eaznet.com (admin.eaznet.com [216.19.20.16]) by amber.eaznet.com (8.8.7/8.8.5) with ESMTP id RAA12024 for ; Mon, 5 Oct 1998 17:23:35 -0700 (MST) Message-ID: <36196345.8E16893F@eaznet.com> Date: Mon, 05 Oct 1998 17:24:37 -0700 From: Eddie Fry X-Mailer: Mozilla 4.06 [en] (Win95; U) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: SCSI Differential controllers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What "differential" SCSI controllers are supported by FreeBSD? Please reply directly, I'm not on this list. Thanks!! -- Eddie Fry EAZNet Internet Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 01:06:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27770 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 01:06:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www.in-design.com (www.in-design.com [206.210.93.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27762; Tue, 6 Oct 1998 01:06:20 -0700 (PDT) (envelope-from nero@in-design.com) Received: from www.in-design.com (nero@www.in-design.com [206.210.93.16]) by www.in-design.com (8.8.7/8.8.5) with SMTP id EAA06308; Tue, 6 Oct 1998 04:06:18 -0400 (EDT) Date: Tue, 6 Oct 1998 04:06:18 -0400 (EDT) From: God To: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Question about NCR driver / SCSI Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all; I have an NCR SDMS V3.0 PCI SCSI adaptor. This is a wide deffrential adaptor it is connected to a 9 gig Seagate Barracuda ST19171WD drive The SCSI card bois notices the drive, but then when fbsd loads up, the following error messages are generated: ncr0: script cmd = 72060000 ncr0: regdump: da 00 80 03 47 00 0d 07 31 08 0c 00 80 00 09 02. ncr0: have to clear fifos. (ncr0:13:0): 8 parity error(s), fallback. (ncr0:13:0): COMMAND FAILED (ff 62) @f2593c00. ncr0:0: ERROR (81:1) (8-0-8000) (0/3) @ (mem 340c28:00000000). ncr0: regdump: da 00 c0 03 47 00 0d 07 31 08 0c 00 80 00 09 02. This error message is repeated about 20 times. First I was wondering if there is a way I can fix this? And ofcourse how to fix it? Thanks alot in advance. Cheers Tamer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 04:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01425 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 04:39:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01415 for ; Tue, 6 Oct 1998 04:39:53 -0700 (PDT) (envelope-from Emmanuel.Coulon@lip6.fr) Received: from asim.lip6.fr (asim.lip6.fr [132.227.60.20]) by isis.lip6.fr (8.8.8/jtpda-5.2.9.1+lip6) with ESMTP id NAA01692 for ; Tue, 6 Oct 1998 13:39:49 +0200 (MET DST) Received: from asim.lip6.fr (asim.lip6.fr [132.227.63.8]) by asim.lip6.fr (SMI-8.6/jtpda-5.2) with SMTP id NAA05309 for ; Tue, 6 Oct 1998 13:39:46 +0200 Date: Tue, 6 Oct 1998 13:39:46 +0200 (MET DST) From: Emmanuel COULON To: freebsd-scsi@FreeBSD.ORG Subject: AIC-7890 driver in 2.2.5 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I still _need_ 2.2.5 on my PC with Asus P2B-DS MB (with 1 CPU). Is there any way to insert the AIC-7890 driver src from a CAM-snapshot in my 2.2.5-release /sys ? (like the Ethernet XL driver @ www.freebsd.org/~wpaul/3Com that I successfully installed) Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 08:43:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09636 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 08:43:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09631 for ; Tue, 6 Oct 1998 08:43:19 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id JAA03521; Tue, 6 Oct 1998 09:43:06 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199810061543.JAA03521@panzer.plutotech.com> Subject: Re: AIC-7890 driver in 2.2.5 In-Reply-To: from Emmanuel COULON at "Oct 6, 98 01:39:46 pm" To: Emmanuel.Coulon@lip6.fr (Emmanuel COULON) Date: Tue, 6 Oct 1998 09:43:06 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Emmanuel COULON wrote... > I still _need_ 2.2.5 on my PC with Asus P2B-DS MB (with 1 CPU). > Is there any way to insert the AIC-7890 driver src > from a CAM-snapshot in my 2.2.5-release /sys ? > (like the Ethernet XL driver @ www.freebsd.org/~wpaul/3Com > that I successfully installed) I suppose it's theoretically possible, but it would be very difficult for someone who doesn't know what they're doing. (It might be doable if you know what you're doing.) I think a better use of your time would be to get a Rev. A 2940 and not worry about making CAM work on 2.2.5. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 10:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27004 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 10:01:15 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26985 for ; Tue, 6 Oct 1998 10:01:10 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA16092; Tue, 6 Oct 1998 19:00:41 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (VMailer, from userid 101) id 384031458; Tue, 6 Oct 1998 08:25:58 +0200 (CEST) Date: Tue, 6 Oct 1998 08:25:58 +0200 From: Ollivier Robert To: Eddie Fry , scsi@FreeBSD.ORG Subject: Re: SCSI Differential controllers Message-ID: <19981006082558.A23553@keltia.freenix.fr> Mail-Followup-To: Eddie Fry , scsi@FreeBSD.ORG References: <36196345.8E16893F@eaznet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.4i In-Reply-To: <36196345.8E16893F@eaznet.com>; from Eddie Fry on Mon, Oct 05, 1998 at 05:24:37PM -0700 X-Operating-System: FreeBSD 3.0-BETA/ELF ctm#4704 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Eddie Fry: > What "differential" SCSI controllers are supported by FreeBSD? I had good results with the 2944UW from Adaptec. Really undistinguishable from a regular 2940UW... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-BETA #2: Sat Oct 3 11:34:55 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 10:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29927 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 10:27:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA29903 for ; Tue, 6 Oct 1998 10:26:59 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 19381 invoked by uid 1000); 6 Oct 1998 18:30:29 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36196345.8E16893F@eaznet.com> Date: Tue, 06 Oct 1998 14:30:29 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Eddie Fry Subject: RE: SCSI Differential controllers Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eddie Fry, On 06-Oct-98 you wrote: > What "differential" SCSI controllers are supported by FreeBSD? > > Please reply directly, I'm not on this list. Differential vs. Single-Ended is a cable electrical signal issue, no a softwae issue. Any controller which the vendor build in differentical as well as single ended will work. Some new controllers use what is known as ``low voltage differential'' with means the controller (correct name is HBA) will ``talk'' differential to differential devices, single-ended to SE devices. Most DPT (http://www.dpt.com) controllers are available either way, with the PM3335UDW giving you RAID and 3 SCSI busses in a single PCI slot. > > Thanks!! > > -- > Eddie Fry > EAZNet Internet Services > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 12:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21281 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 12:07:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21255 for ; Tue, 6 Oct 1998 12:07:23 -0700 (PDT) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.1/8.8.8) id PAA23649; Tue, 6 Oct 1998 15:04:35 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 6 Oct 1998 15:04:34 -0400 (EDT) To: shimon@simon-shapiro.org Cc: Eddie Fry , scsi@FreeBSD.ORG Subject: RE: SCSI Differential controllers In-Reply-To: References: <36196345.8E16893F@eaznet.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13850.26489.731677.71836@tbuswell.ne.mediaone.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon Shapiro writes: > Eddie Fry, On 06-Oct-98 you wrote: > > What "differential" SCSI controllers are supported by FreeBSD? > Differential vs. Single-Ended is a cable electrical signal issue, no a [..] > Most DPT (http://www.dpt.com) controllers are available either way, with > the PM3335UDW giving you RAID and 3 SCSI busses in a single PCI slot. Or moving to the opposite end of the price [and performance] spectrum, cheap used (Symbios) NCR-8251D (uses 53C825) seem to be available; in the past 2 months I've bought two in the $40-$100 range and they work great. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Oct 6 18:09:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18171 for freebsd-scsi-outgoing; Tue, 6 Oct 1998 18:09:41 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17998 for ; Tue, 6 Oct 1998 18:08:57 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA09313; Wed, 7 Oct 1998 10:38:26 +0930 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 07 Oct 1998 10:38:25 +0930 (CST) From: "Daniel O'Connor" To: Emmanuel COULON Subject: RE: AIC-7890 driver in 2.2.5 Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 06-Oct-98 Emmanuel COULON wrote: > I still _need_ 2.2.5 on my PC with Asus P2B-DS MB (with 1 CPU). > Is there any way to insert the AIC-7890 driver src > from a CAM-snapshot in my 2.2.5-release /sys ? > (like the Ethernet XL driver @ www.freebsd.org/~wpaul/3Com > that I successfully installed) Urgh.. Any reason you can't just use the CAM patches? They seem to work fine for me.. (With the exception of some problems reading cd audio, and writing CD's) --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 7 07:06:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24851 for freebsd-scsi-outgoing; Wed, 7 Oct 1998 07:06:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www.in-design.com (www.in-design.com [206.210.93.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24840; Wed, 7 Oct 1998 07:06:41 -0700 (PDT) (envelope-from archive@in-design.com) Received: from www.in-design.com (archive@www.in-design.com [206.210.93.16]) by www.in-design.com (8.8.7/8.8.5) with SMTP id KAA13414; Wed, 7 Oct 1998 10:06:32 -0400 (EDT) Date: Wed, 7 Oct 1998 10:06:32 -0400 (EDT) From: Intuitive Design Archive To: freebsd-question@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: NCR 53c825 and diffrential drives. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all; I am trying to build a machine with fbsd 2.2.7-RELEASE with a NCR 53c825 scsi card and a ST19171WD seagate baracuda drive. The card notices the drive during boot time. When freebsd boots the following errors come up: ncr0 rev 2 int a irq 9 on pci0:10:0 ncr0 waiting for scsi devices to settle new ccb @f0dc8800. (ncr0:0:0): "SEAGATE ST19171W HP06" type 0 fixed SCSI 2 sd1(ncr0:0:0): Direct-Access sd1(ncr0:0:0): WIDE SCSI (16 bit) enabled sd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 8) sd1(ncr0:0:0): NOT READY asc:4,0 sd1(ncr0:0:0): Logical unit not ready, cause not reportable field replaceable unit: 2 , retries:4 The above 4 lines repeat several times until: sd1: could not get size finally it claims: sd1 could not mode sense (4). Using fictitious geometry 0MB (0 512 byte sectors) And that is where I am. Is there any way that I can fix this problem, or is there something wrong with the drive? Thanks alot in advance. Tamer Ziady Intuitive Design http://www.in-design.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 7 08:42:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14285 for freebsd-scsi-outgoing; Wed, 7 Oct 1998 08:42:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14224; Wed, 7 Oct 1998 08:42:03 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00486; Wed, 7 Oct 1998 08:46:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810071546.IAA00486@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Intuitive Design Archive cc: freebsd-question@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: NCR 53c825 and diffrential drives. In-reply-to: Your message of "Wed, 07 Oct 1998 10:06:32 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Oct 1998 08:46:40 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello all; > > I am trying to build a machine with fbsd 2.2.7-RELEASE with a > NCR 53c825 scsi card and a ST19171WD seagate baracuda drive. The card > notices the drive during boot time. When freebsd boots the following > errors come up: > > ncr0 rev 2 int a irq 9 on pci0:10:0 > ncr0 waiting for scsi devices to settle > new ccb @f0dc8800. > (ncr0:0:0): "SEAGATE ST19171W HP06" type 0 fixed SCSI 2 > sd1(ncr0:0:0): Direct-Access > sd1(ncr0:0:0): WIDE SCSI (16 bit) enabled > sd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 8) > > sd1(ncr0:0:0): NOT READY asc:4,0 > sd1(ncr0:0:0): Logical unit not ready, cause not reportable field > replaceable unit: 2 > , retries:4 > > The above 4 lines repeat several times until: > > sd1: could not get size > > finally it claims: > > sd1 could not mode sense (4). Using fictitious geometry > 0MB (0 512 byte sectors) > > And that is where I am. Is there any way that I can fix this problem, or > is there something wrong with the drive? Does the drive spin up OK? It certainly looks like it's dead from the above. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Oct 7 23:20:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01511 for freebsd-scsi-outgoing; Wed, 7 Oct 1998 23:20:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01475 for ; Wed, 7 Oct 1998 23:20:46 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA24775 for freebsd-scsi@FreeBSD.org; Thu, 8 Oct 1998 08:20:33 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id IAA02307; Thu, 8 Oct 1998 08:05:30 +0200 (MET DST) (envelope-from j) Message-ID: <19981008080530.60854@uriah.heep.sax.de> Date: Thu, 8 Oct 1998 08:05:30 +0200 From: J Wunsch To: FreeBSD SCSI list Subject: Re: SCSI Differential controllers Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 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 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon asked me to post this clarification to the mailinglist as well: -----Forwarded message from Simon Shapiro ----- Message-ID: Date: Wed, 07 Oct 1998 20:45:30 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Joerg Wunsch Subject: Re: SCSI Differential controllers J Wunsch, On 07-Oct-98 you wrote: > As Simon Shapiro wrote: > > > Some new controllers use what is known as > > ``low voltage differential'' with means the controller (correct name is > > HBA) will ``talk'' differential to differential devices, single-ended > > to SE > > devices. > > I thought a single SE device will degrade the entire bus to SE? I > can't imagine otherwise, since this SE device grounds one half of all > the `return' signal lines on the bus. I think you are right. I only deal with these things on the HBA-Bay leg. All the bays I use are SE inside and diff outside. There is nothing on the Diff side except for boxes and DPTs. The box has this dual capacity. The DPTs are simply differential. I think the i2o (5th generation) DPTs are dual mode. > So far, i've only browsed a little through the SCSI-3 working group > documents, they speak that only devices with active (?) negation are > guaranteed to co-operate correctly with LVD, while older SE devices > might cause damage to the LVD output stages. If i understood it > correctly, all differential output stages are required to use the > DIFFSENSE line on the bus in order to detect whether an SE device has > accidentally been connected to the bus (so they can turn off their > output drivers), i assume that's also the way LVD decides in which > mode to operate. Again, you are correct. I suggest you post this to the SCSI list, so others can benefit. My rule is: Check each device, never mix modes, check each device again, then buy the disk bays from reputable source, with the disks. Solvs lots of problems :-) Simon -----End of forwarded message----- -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- 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-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 8 15:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00927 for freebsd-scsi-outgoing; Thu, 8 Oct 1998 15:08:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA00799 for ; Thu, 8 Oct 1998 15:06:27 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 16198 invoked by uid 1000); 8 Oct 1998 23:10:21 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 08 Oct 1998 19:10:21 -0400 (EDT) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: freebsd-current@FreeBSD.ORG Subject: Give a Hand of Appreciation to the CAM Team Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I would like to stand, tip my hat off and give a big, warm compliment to the CAM team. It is small secret that I was not all happy and in agreement with the way the project developed, but, in the end, I was proven wrong. They did an impressive job. What follows are some notes on this matter. I was just done with some stress, load, and performance testing on the DPT driver, in the CAM kernel for 3.0. * Work was based on a 3.0-current kernel from 4-Oct-1998. * We tested on two platforms, nomis and lead-100. * Nomis is a Super Micro P6DNH2 motherboard with 2 P6-200 processors, 384MB or DRAM, 2 DPT PM3334UDW, each with 64MB of ECC cache, and three SCSI busses. There are some 35 disk drives attached, all in some RAID array arrangement or another. Testing was done on a 19GB RAID-0 partition (6 Barracuda Ultra Wide with striping factor of 32KB). * Lead-100 is a test machine with a nasty ASUS motherboard having some 128MB or SDRAM and a single single bus PM3334UW attached to 3 Cheetah drives arranged in a RAID-5 with 64K stripes. We use a 1.8GB partitions for testing. * For testing we use a modified nasty.sh which forks 256 instances at a time. Each instance runs st.c, in read-only,4KB records. St.c simply reads random records from the given disk. It is NOT a file-system test, but an I/O engine test; All access was made to raw partitions. * these are available form ftp://simon-shapiro.org/crash/tools. * Test configuration is designed to stress the DPT firmware, The device driver, the O/S kernel, etc. Not to yield the maximum quotable megabytes per second. * As a benchmark, we used tests done on a pre-CAM kernel, in a similar arrangement to that on nomis. * Successive runs of nasty.sh are initiated until he system dies or until 1,024 instances of st.c are running. * The pre-CAM tests included internal measurements of latencies in the interrupt handler code, the DPT firmware, the driver internals, and the O/S stack. These were not available in the CAM version. they were taken out and not put back in again (my fault). * Briefly, the pre-CAM kernel, UP, on a P6-200 achieved 1,943 transfers per second. This is on 1,024 instances. Keyboard response was excellent, and IDE access was usable. Interactive access to anything hooked up to the DPT was experiencing 6minutes response time. Reliability was excellent; the test would run for 24-48 hours and then manually terminated without any signs of failure. Running intensive NFS work in parallel, dod not seem to change the overall throughput. I published similar tests on these lists before. * Disk utilization (the observed load on the physical disks, as compared to load on the controller) seems to be around 30-50%. SCSI bus utilization seems to be around 50-75%. controller utilization seems to be around 90% visible, and about 99% of theoretical limits. Now to the CAM results: * P6-200 SMP: 128 processes LA = 50.51, 1,671 tps (Transfers/Sec.) 256 processes LA = 158-188, 1329-1898 tps 320 processes LA = 199-240, 162-1904 tps We could not get much higher than that, the system simply dies. No crashes, but no response to anything is visible. Current processes seemed to still be running. * P-II- 350 UP: 256 processes LA = 59-67, 1,536-1,738 tps 512 Processes LA = 250-270, 569-1248 tps. We could not scale any higher. Same symptoms as SMP at around 320 processes. * We could not perform any NFS tests, as at these loads, the network code times out on anything we try. Summary: * These are, by no means, conclusive results. Neither the methods nor the reporting are scientifically, or even statistically valid. But some behavior patters are rather visible. * From I/O performance perspective, SMP on FreeBSD seems like a net loss. I do not think there are any news here. * The CAM code, IRT disks (we did not test any tape nor CD devices), seems rather robust. The systems boot significantly faster, and correctly, and we experienced no failures attributable to CAM. * Peak performance, on a DPT controller, seems about 5% slower than previous code. This does NOT necessarily mean that the CAM code is slower. It only means, that when viewed as a whole, the CAM solution is somewhat slower. * Scalability seems distinctly poorer. Where the pre-CAM code scaled linearly to its peak, we see the CAM code peak around 128-256 concurrent processes, with erratic behavior in the 320-500 processes, coupled with clear and distinct decline in throughput. * Caveat; While sharing major pieces of code, the DPT pre-CAM and CAM drivers are very different creatures. We had not put in the time and effort yet to study the old driver architecture under CAM. Conclusion: A CAM/DPT based solution is probably production grade. It is very unlikely that most users will approach the loads described here. Even under severe loads, the code holds together, with fewer quirks in the driver, to allow for reliable operation. OTOH, there is much room for improvement in scalability and some room for peak performance. We will not be bored, but busy. Again, Thanx to Justin and Ken for all their excellent work! Sincerely Yours, Shimon@Simon-Shapiro.ORG 770.265.7340 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Oct 8 16:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18023 for freebsd-scsi-outgoing; Thu, 8 Oct 1998 16:26:59 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17903 for ; Thu, 8 Oct 1998 16:26:20 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id RAA25702; Thu, 8 Oct 1998 17:19:27 -0600 (MDT) Date: Thu, 8 Oct 1998 17:19:27 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199810082319.RAA25702@narnia.plutotech.com> To: shimon@simon-shapiro.org cc: scsi@FreeBSD.ORG Subject: Re: Give a Hand of Appreciation to the CAM Team Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: ... > Now to the CAM results: > > * P6-200 SMP: 128 processes LA = 50.51, 1,671 tps (Transfers/Sec.) > 256 processes LA = 158-188, 1329-1898 tps > 320 processes LA = 199-240, 162-1904 tps > We could not get much higher than that, the system simply dies. No > crashes, but no response to anything is visible. Current processes > seemed to still be running. > > * P-II- 350 UP: 256 processes LA = 59-67, 1,536-1,738 tps > 512 Processes LA = 250-270, 569-1248 tps. > We could not scale any higher. Same symptoms as SMP at around 320 > processes. Can you elaborate on 'the system simply dies'? Does I/O stop? Can you get into the debugger? We can analyze and correct any performance bottlenecks in the system after 3.0R ships, but I need to know more about your symptoms so I can tell if this is a showstopper for 3.0. Thanks, Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message