From owner-freebsd-scsi Sun Feb 14 01:15:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05768 for freebsd-scsi-outgoing; Sun, 14 Feb 1999 01:15:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles301.castles.com [208.214.167.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05763 for ; Sun, 14 Feb 1999 01:15:13 -0800 (PST) (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 BAA01928; Sun, 14 Feb 1999 01:10:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902140910.BAA01928@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: rohrbach@nacamar.net cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AMI MegaRAID In-reply-to: Your message of "Sun, 14 Feb 1999 05:22:53 +0100." <19990214052253.A7448@nacamar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Feb 1999 01:10:50 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > is somebody else working on an ami megaraid scsi driver? just curious. I poked them at Comdex this year, asking them for documentation so I could send it to anyone interested. No response yet. -- \\ 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 Feb 14 03:51:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19456 for freebsd-scsi-outgoing; Sun, 14 Feb 1999 03:51:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19451 for ; Sun, 14 Feb 1999 03:51:36 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id DAA23255; Sun, 14 Feb 1999 03:51:31 -0800 (PST) (envelope-from ulf) Message-ID: <19990214035131.A16037@TelcoSucks.org> Date: Sun, 14 Feb 1999 03:51:31 -0800 From: Ulf Zimmermann To: Mike Smith , rohrbach@nacamar.net Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AMI MegaRAID Reply-To: ulf@Alameda.net References: <19990214052253.A7448@nacamar.net> <199902140910.BAA01928@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902140910.BAA01928@dingo.cdrom.com>; from Mike Smith on Sun, Feb 14, 1999 at 01:10:50AM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Feb 14, 1999 at 01:10:50AM -0800, Mike Smith wrote: > > is somebody else working on an ami megaraid scsi driver? just curious. > > I poked them at Comdex this year, asking them for documentation so I > could send it to anyone interested. No response yet. About 6 months ago, I tried very hard to get anything from AMI. After like 3 weeks they said No. If anyone gets docs, I have a 428 controller with 3 channels here. > > -- > \\ 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 -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 14 10:25:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22197 for freebsd-scsi-outgoing; Sun, 14 Feb 1999 10:25:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22184 for ; Sun, 14 Feb 1999 10:25:38 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id KAA27173; Sun, 14 Feb 1999 10:25:14 -0800 Date: Sun, 14 Feb 1999 10:25:13 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Andreas Klemm cc: "Kenneth D. Merry" , ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: <19990213114641.B6068@titan.klemm.gtn.com> 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 > But if write performance is poor, but actually doesn't eat up > that much CPU performance. Why is the FreeBSD machine so much > "in-responsive". It means I merely can login on a second console, > I have to wait 10-15 seconds for a login. And the execution of > commands lags lags lags. This kind of blockage is often a VM/Buffer Cache type of issue- the same problem applies in Linux. If you don't put some hysteresis into you're bdelwri queue, you end up swamping the system writing out to one spindle. This whole area of system performance, including whether or not using the maximum number of tags you can, needs to be really thought through and *metrics* used to prove or disprove cases. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 15 01:33:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07285 for freebsd-scsi-outgoing; Mon, 15 Feb 1999 01:33:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bayer2.bayer-ag.de (bayer2.bayer-ag.de [194.120.191.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA07279 for ; Mon, 15 Feb 1999 01:32:57 -0800 (PST) (envelope-from ANDREAS.KLEMM.AK@bayer-ag.de) From: ANDREAS.KLEMM.AK@bayer-ag.de Received: by bayer2.bayer-ag.de id KAA06260 (SMTP Gateway 3.0 for scsi@freebsd.org); Mon, 15 Feb 1999 10:32:42 +0100 Received: by bayer2.bayer-ag.de (Internal Mail Agent-2); Mon, 15 Feb 1999 10:32:42 +0100 Received: by bayer2.bayer-ag.de (Internal Mail Agent-1); Mon, 15 Feb 1999 10:32:42 +0100 To: " - (052)mjacob(a)feral.com" Cc: " - (052)scsi(a)FreeBSD.ORG" Subject: Antwort: Re: It%s not the write cache on 3.0-STABLE and not Message-Id: <0006800008749198000002L082*@MHS> Date: Mon, 15 Feb 1999 10:32:33 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA07281 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! Well, but why especially with this kind of hardware / harddisk ??? I doesn*%t have any problems with my machine at home and get with 5200 U/min narrow SCSI harddisks (IBM DORS 32160) more write throughput, than with this ultra scsi device. And what is astonishing: in 2.2.7 you can solve the problem by disabling tagged queuing ! When I disabled tagged queuing in 3.0-STABLE, it still had this write performance / slowness on console problem. Well, I*%d loved to investigate this problem further, but the timescale to install the system is over and I had to install 2.2.7 :-/ Is there perhaps somebody other with this Seagate drive for further testing ??? It looks for me like a race condition in our SCSI driver in combination with that special firmware. Have no other idea what could cause this ... Especially because only 2.2.7 without tagged solves the problem.... But not CAM without tagged. BTW, when I reduce the min/max number of tags for that drive under 3.0-STABLE (from 990210) min = 8, max=16, I got SCSI Errors on the console. I think it were aborted SCB*%s or such ... Well then I had to give up and install 2.2.7 .... Andreas /// mjacob@feral.com on 14.02.99 19:25:45 Bitte antworten an mjacob@feral.com @ INTERNET An: andreas@klemm.gtn.com @ INTERNET Kopie: scsi@FreeBSD.ORG @ INTERNET, Andreas Klemm@BAYERNOTES, ken@plutotech.com @ INTERNET Thema: Re: It%s not the write cache on 3.0-STABLE and not tagged co > But if write performance is poor, but actually doesn't eat up > that much CPU performance. Why is the FreeBSD machine so much > "in-responsive". It means I merely can login on a second console, > I have to wait 10-15 seconds for a login. And the execution of > commands lags lags lags. This kind of blockage is often a VM/Buffer Cache type of issue- the same problem applies in Linux. If you don't put some hysteresis into you're bdelwri queue, you end up swamping the system writing out to one spindle. This whole area of system performance, including whether or not using the maximum number of tags you can, needs to be really thought through and *metrics* used to prove or disprove cases. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 15 07:31:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18897 for freebsd-scsi-outgoing; Mon, 15 Feb 1999 07:31:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18892 for ; Mon, 15 Feb 1999 07:31:16 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: (from rohrbach@localhost) by mail.nacamar.de (8.8.7/8.8.8MB-19980212) id QAA02447; Mon, 15 Feb 1999 16:30:23 +0100 (CET) Message-ID: <19990215163021.B269@nacamar.net> Date: Mon, 15 Feb 1999 16:30:22 +0100 From: "Karsten W. Rohrbach" To: ulf@Alameda.net, Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AMI MegaRAID Reply-To: rohrbach@nacamar.net References: <19990214052253.A7448@nacamar.net> <199902140910.BAA01928@dingo.cdrom.com> <19990214035131.A16037@TelcoSucks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <19990214035131.A16037@TelcoSucks.org>; from Ulf Zimmermann on Sun, Feb 14, 1999 at 03:51:31AM -0800 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org okay, so iīll poke them in the ribs, letīs see what happens next :> excerpt from linux-2.2.1īs drivers/scsi/megaraid.c: * Linux MegaRAID device driver * * Copyright 1998 American Megatrends Inc. * * This program is free software; you can redistribute it and/or * modify it under the terms of the GNU General Public License * as published by the Free Software Foundation; either version * 2 of the License, or (at your option) any later version. * * Version : 0.92 * * Description: Linux device driver for AMI MegaRAID controller * maybe they insist on implementing it themselves? /k Ulf Zimmermann (ulf@Alameda.net) @ Sun, Feb 14, 1999 at 03:51:31AM -0800: > On Sun, Feb 14, 1999 at 01:10:50AM -0800, Mike Smith wrote: > > > is somebody else working on an ami megaraid scsi driver? just curious. > > > > I poked them at Comdex this year, asking them for documentation so I > > could send it to anyone interested. No response yet. > > About 6 months ago, I tried very hard to get anything from AMI. After like > 3 weeks they said No. If anyone gets docs, I have a 428 controller with > 3 channels here. > > > > > -- > > \\ 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 > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- "The path of excess leads to the tower of wisdom." -- W. Blake http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net PGP Key fingerprint = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 16 17:25:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from remler.nas.nasa.gov (remler.nas.nasa.gov [129.99.50.44]) by hub.freebsd.org (Postfix) with ESMTP id 6184A1135E for ; Tue, 16 Feb 1999 17:25:23 -0800 (PST) (envelope-from mjacob@nas.nasa.gov) Received: from localhost (mjacob@localhost) by remler.nas.nasa.gov (8.8.8/8.8.8) with SMTP id RAA25544 for ; Tue, 16 Feb 1999 17:25:23 -0800 X-Authentication-Warning: remler.nas.nasa.gov: mjacob owned process doing -bs Date: Tue, 16 Feb 1999 17:25:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-scsi@freebsd.org Subject: Simple 2944 not handled? 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'm having a heckuva a time with the the Adaptec driver- this is with kernels from 3.0 to today. The hardware is a SuperMicro P6DLH- or some such- single 300Mhz Pentium 2, two PCI busses, etc...I've had 1 through 4 Adaptec 2944 cards (differential 2940AU variants) installed in this box. What happens, whether there's something attached to the cards or not, is that during probetime commands time out. I can't figure out what and where and why, so here's a boot verbose transcript and maybe someone else can figure out what's up.... I was going to go back and try and do some large filesystem testing, but if I can't get mass storage going, that's a problem (I *could* round up some more Qlogic differential cards, but I wanted to avoid questions over why I'm not using a 'mainstream' HBA...) The case below has an adaptec unit attached- but the same errors occur even if nothing else is attached. The adaptec unit is seen fine from the BIOS control page. I don't remember whether I've tried alternate drivers and OS's on this particular machine. -matt Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Tue Feb 16 16:00:37 PST 1999 mjacob@ds3.nas.nasa.gov:/usr/src/sys/compile/DS1 Calibrating clock(s) ... TSC clock: 334128285 Hz, i8254 clock: 1193316 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183fbff> real memory = 536870912 (524288K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002f1000 - 0x1ffebfff, 533704704 bytes (130299 pages) avail memory = 520339456 (508144K bytes) Programming 24 pins in IOAPIC #0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Found BIOS32 Service Directory header at 0xf00fdb60 Entry = 0xfdb70 (0xf00fdb70) Rev = 0 Len = 1 PCI BIOS entry at 0xdb91 DMI header at 0xf00f6970 Version 0.0 Table at 0xf6a53, 33 entries, 1019 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7950 Preloaded elf kernel "kernel.new" at 0xf02e1000. ccd0-3: Concatenated disk drivers Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x80003b40 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71808086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7180, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base f8000000, size 26 chip0: rev 0x03 on pci0.0.0 found-> vendor=0x8086, dev=0x7181, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x03 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.7.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 ide_pci0: rev 0x01 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000ffa2 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000ffaa Freeing (NOT implemented) redirected ISA irq 0. found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=2 map[0]: type 4, range 32, base 0000ef80, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip3: rev 0x01 on pci0.7.3 found-> vendor=0x8086, dev=0x0960, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=1 subordinatebus=2 secondarybus=2 chip4: rev 0x03 on pci0.13.0 Freeing (NOT implemented) redirected ISA irq 9. found-> vendor=0x8086, dev=0x1960, revid=0x03 class=05-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[0]: type 3, range 32, base febff000, size 12 Freeing (NOT implemented) redirected ISA irq 5. found-> vendor=0x120f, dev=0x0001, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 1, range 32, base ffafe000, size 12 Freeing (NOT implemented) redirected ISA irq 9. found-> vendor=0x1011, dev=0x0009, revid=0x22 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[0]: type 4, range 32, base 0000e880, size 7 map[1]: type 1, range 32, base ffafdf80, size 7 de0: rev 0x22 int a irq 17 on pci0.16.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:43:08:cb bpf: de0 attached Freeing (NOT implemented) redirected ISA irq 11. found-> vendor=0x9004, dev=0x8478, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[0]: type 4, range 32, base 0000ec00, size 8 map[1]: type 1, range 32, base ffaff000, size 12 ahc0: rev 0x01 int a irq 18 on pci0.18.0 ahc0: io_port 0xec00 vaddr 0 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 413 instructions downloaded Probing for devices on PCI bus 1: Probing for devices on PCI bus 2: Freeing (NOT implemented) redirected ISA irq 5. found-> vendor=0x120f, dev=0x0001, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 1, range 32, base ff9ff000, size 12 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 10 03 3c psm: status 10 03 3c psm: status 10 03 3c psm: status 10 00 64 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0407 wdc1 not found at 0x170 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. imasks: bio c8004040, tty c300101a, net c6020000 SMP: enabled INTs: 1, 3, 4, 6, 12, 14, 17, 18, apic_imen: 0x00f9afa5 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 bpf: tun0 attached bpf: lo0 attached de0 XXX: driver didn't set ifq_maxlen lo0 XXX: driver didn't set ifq_maxlen Waiting 2 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. de0: enabling Full Duplex 100baseTX port (probe0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 15 SCBs aborted (probe1:ahc0:0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 15 SCBs aborted ahc0: Selection Timeout on A:2. 1 SCBs aborted (probe3:ahc0:0:3:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe4:ahc0:0:4:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe5:ahc0:0:5:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): Queuing a BDR SCB (probe5:ahc0:0:5:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe7:ahc0:0:8:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe7:ahc0:0:8:0): Queuing a BDR SCB (probe7:ahc0:0:8:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe7:ahc0:0:8:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe8:ahc0:0:9:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe8:ahc0:0:9:0): Queuing a BDR SCB (probe8:ahc0:0:9:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe8:ahc0:0:9:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe9:ahc0:0:10:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe9:ahc0:0:10:0): Queuing a BDR SCB (probe9:ahc0:0:10:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe9:ahc0:0:10:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted (probe10:ahc0:0:11:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe10:ahc0:0:11:0): Queuing a BDR SCB (probe10:ahc0:0:11:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe10:ahc0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): Queuing a BDR SCB (probe13:ahc0:0:14:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 12 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): Queuing a BDR SCB (probe14:ahc0:0:15:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 12 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 12 SCBs aborted ahc0: Selection Timeout on A:1. 1 SCBs aborted (probe3:ahc0:0:3:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 11 SCBs aborted (probe4:ahc0:0:4:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 11 SCBs aborted (probe5:ahc0:0:5:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): Queuing a BDR SCB (probe5:ahc0:0:5:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 11 SCBs aborted (probe6:ahc0:0:6:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 11 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted (probe9:ahc0:0:10:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe9:ahc0:0:10:0): Queuing a BDR SCB (probe9:ahc0:0:10:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe9:ahc0:0:10:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe10:ahc0:0:11:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe10:ahc0:0:11:0): Queuing a BDR SCB (probe10:ahc0:0:11:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe10:ahc0:0:11:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe13:ahc0:0:14:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): Queuing a BDR SCB (probe13:ahc0:0:14:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe14:ahc0:0:15:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): Queuing a BDR SCB (probe14:ahc0:0:15:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe0:ahc0:0:0:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe3:ahc0:0:3:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe4:ahc0:0:4:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe5:ahc0:0:5:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): Queuing a BDR SCB (probe5:ahc0:0:5:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe6:ahc0:0:6:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): Queuing a BDR SCB (probe13:ahc0:0:14:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 7 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): Queuing a BDR SCB (probe14:ahc0:0:15:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 7 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 7 SCBs aborted (probe3:ahc0:0:3:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 7 SCBs aborted ahc0: Selection Timeout on A:4. 1 SCBs aborted (probe5:ahc0:0:5:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): Queuing a BDR SCB (probe5:ahc0:0:5:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe5:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted (probe13:ahc0:0:14:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): Queuing a BDR SCB (probe13:ahc0:0:14:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe3:ahc0:0:3:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted (probe13:ahc0:0:14:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): Queuing a BDR SCB (probe13:ahc0:0:14:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 63, end = 16515071, size 16515009 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 16 19:33:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id A5B0510F90 for ; Tue, 16 Feb 1999 19:33:14 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (doconnor@lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA22405; Wed, 17 Feb 1999 14:02:00 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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, 17 Feb 1999 14:02:00 +1030 (CST) From: "Daniel O'Connor" To: mjacob@feral.com Subject: RE: Simple 2944 not handled? Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 17-Feb-99 Matthew Jacob wrote: > I'm having a heckuva a time with the the Adaptec driver- this is with > kernels from 3.0 to today. Is there any possibility of trying a 4.0 kernel? I had this problem on a spam box at work.. 3.0 doesn't like the CDR at all.. I get bus timeouts and sometimes the machine hangs :-/ I upgraded to 4.0 and it works find. This is a P6SBS which is a PII mobo with a AIC7895 on board (dual UW) Maybe worth a cvs diff on the AHC code between 3.0 and 4.0? --- 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 Tue Feb 16 19:46:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CC0DE10FD8 for ; Tue, 16 Feb 1999 19:46:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id TAA05272; Tue, 16 Feb 1999 19:45:37 -0800 Date: Tue, 16 Feb 1999 19:45:36 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Daniel O'Connor" Cc: freebsd-scsi@freebsd.org Subject: RE: Simple 2944 not handled? In-Reply-To: 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'm running 4.0. It's a kernel from today's sources. Too bad- I'd hope it was dif! On Wed, 17 Feb 1999, Daniel O'Connor wrote: > > On 17-Feb-99 Matthew Jacob wrote: > > I'm having a heckuva a time with the the Adaptec driver- this is with > > kernels from 3.0 to today. > Is there any possibility of trying a 4.0 kernel? > I had this problem on a spam box at work.. 3.0 doesn't like the CDR at all.. I get bus > timeouts and sometimes the machine hangs :-/ > > I upgraded to 4.0 and it works find. This is a P6SBS which is a PII mobo with a AIC7895 > on board (dual UW) > > Maybe worth a cvs diff on the AHC code between 3.0 and 4.0? > > --- > 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 Tue Feb 16 22:59:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hero.clerk.leon.fl.us (hero.clerk.leon.fl.us [199.44.225.3]) by hub.freebsd.org (Postfix) with ESMTP id 96C1A10E5B; Tue, 16 Feb 1999 22:59:18 -0800 (PST) (envelope-from khang@hero.clerk.leon.fl.us) Received: from localhost (khang@localhost) by hero.clerk.leon.fl.us (8.9.1/8.9.1) with ESMTP id BAA02155; Wed, 17 Feb 1999 01:59:52 GMT (envelope-from khang@hero.clerk.leon.fl.us) Date: Wed, 17 Feb 1999 01:59:52 +0000 (GMT) From: Khang Trang To: freebsd-scsi@freebsd.org Cc: freebsd-questions@freebsd.org Subject: trouble with a seagate ST39140N 1206 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 help! i'm having some problems with an adaptec 2940 and two seagate ST39140N 1206 drives running on a ppro200 with fbsd 3.0-release. history: the machine was formerly a redhat 5.1 linux machine and the two seagate drives were formatted ext2fs. switched to fbsd 3.0 ... formatted the 8 gig ibm ide drive and installed fbsd 3.0. fbsd loads up and runs great. everything worked great. i was able to mount_ext2fs the two scsi seagate drives, but then the system got rebooted a few times (without my knowledge) and the seagate drives got corrupt (superblock was missing). tried fsck -b with an alternate superblock to no avail. i figured might as well format and setup the hds as fbsd drives so i do: camcontrol cmd -v -n da -u 0 -c "4 0 0 0 0 0" following the examples from a post to the fbsd mail archives. when i ran camcontrol it gave some sort of error saying could not send command or soemthing to that extent. no biggie i figured. look through the fbsd handbook and found: dd if=/dev/zero of=/dev/foo bs=1K count=1 disklabel etc etc etc tried that but got this error message: dd: /dev/rda0: Input/output error checking dmesg there are these errors: (da0:ahc0:0:0:0): READ(06). CDB: 8 0 0 0 1 0 (da0:ahc0:0:0:0): MEDIUM ERROR asc:31,0 (da0:ahc0:0:0:0): Medium format corrupted da0: error reading primary partition table reading fsbn 0 now i can't fdisk, fsck, disklabel, or anything on that drive. camcontrol devlist shows the following: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,cd0) at scbus0 target 3 lun 0 (pass2,cd1) at scbus0 target 4 lun 0 (pass3,da1) HELP! i'm not worried about losing the data (ha! that's probably already done) but from what i've managed to find out from teh mail archives i'm under the impression that i'm screwed. i haven't tried looking at the firmware in the scsi controller (suggested to me) or a low level format (can someone tell me how in fbsd 3.0?). any help would be appreciated. as long as teh drives aren't now paperweigths i'm happy. would it help if i took the drives out, put them in a dos machine and format them, then put them back in and mount_msdos them? i'm considering this route if it works. if you need more info please email me back. (btw the machine is up and running with fbsd 3.0 just don't have the two drives mounted which i really really would like to do. so PLEASE DON'T TELL ME THE DRIVES ARE PAPERWEIGHTS AND I SHOULD BUY NEW ONES :(.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 16 23:24:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 91CD210EE7; Tue, 16 Feb 1999 23:24:14 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id AAA67341; Wed, 17 Feb 1999 00:24:10 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902170724.AAA67341@panzer.plutotech.com> Subject: Re: trouble with a seagate ST39140N 1206 In-Reply-To: from Khang Trang at "Feb 17, 1999 1:59:52 am" To: khang@hero.clerk.leon.fl.us (Khang Trang) Date: Wed, 17 Feb 1999 00:24:10 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Khang Trang wrote... > > help! > > i'm having some problems with an adaptec 2940 and two seagate ST39140N > 1206 drives running on a ppro200 with fbsd 3.0-release. > > history: > the machine was formerly a redhat 5.1 linux machine and the two seagate > drives were formatted ext2fs. switched to fbsd 3.0 ... formatted the 8 gig > ibm ide drive and installed fbsd 3.0. fbsd loads up and runs great. > > everything worked great. i was able to mount_ext2fs the two scsi seagate > drives, but then the system got rebooted a few times (without my > knowledge) and the seagate drives got corrupt (superblock was missing). > tried fsck -b with an alternate superblock to no avail. i figured might > as well format and setup the hds as fbsd drives so i do: > > camcontrol cmd -v -n da -u 0 -c "4 0 0 0 0 0" > > following the examples from a post to the fbsd mail archives. Well, there's just one problem with that... > when i ran camcontrol it gave some sort of error saying could not send > command or soemthing to that extent. no biggie i figured. What probably happened is that the command timed out. Low-level formatting generally takes a long time to complete. (up to a couple of hours) Here's how to specify a timeout in seconds: camcontrol cmd -v -t 10800 -n da -u 0 -c "4 0 0 0 0 0" That sets the timeout to 3 hours. It's generally *not* a good idea to low-level format a drive as your first resort. The things you're trying below are much better. It's much better to just to disklabel the disk, newfs it, etc. > look through > the fbsd handbook and found: > > dd if=/dev/zero of=/dev/foo bs=1K count=1 > disklabel etc etc etc > > tried that but got this error message: > > dd: /dev/rda0: Input/output error > > checking dmesg there are these errors: > > (da0:ahc0:0:0:0): READ(06). CDB: 8 0 0 0 1 0 > (da0:ahc0:0:0:0): MEDIUM ERROR asc:31,0 > (da0:ahc0:0:0:0): Medium format corrupted > da0: error reading primary partition table reading fsbn 0 > > now i can't fdisk, fsck, disklabel, or anything on that drive. What has most likely happened is that since the format was stopped when it was only partially completed, the disk has more or less lost its brain. > camcontrol devlist shows the following: > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,cd0) > at scbus0 target 3 lun 0 (pass2,cd1) > at scbus0 target 4 lun 0 (pass3,da1) > > HELP! > i'm not worried about losing the data (ha! that's probably already done) > but from what i've managed to find out from teh mail archives i'm under > the impression that i'm screwed. i haven't tried looking at the firmware > in the scsi controller (suggested to me) or a low level format (can > someone tell me how in fbsd 3.0?). any help would be appreciated. as > long as teh drives aren't now paperweigths i'm happy. > > would it help if i took the drives out, put them in a dos machine and > format them, then put them back in and mount_msdos them? i'm considering > this route if it works. > > if you need more info please email me back. (btw the machine is up > and running with fbsd 3.0 just don't have the two drives mounted which i > really really would like to do. so PLEASE DON'T TELL ME THE DRIVES ARE > PAPERWEIGHTS AND I SHOULD BUY NEW ONES :(.) I don't think they're paperweights at all. The "Medium format corrupted" errors can generally be fixed by low-level formatting the disk. This is one of the few instances where low-level formatting is actually the right thing to do. As I mentioned above, here's how to low-level format da0: camcontrol cmd -v -t 10800 -n da -u 0 -c "4 0 0 0 0 0" I think 3 hours should be enough, but I haven't low-level formatted a drive in a couple of years. If you don't think 3 hours will be enough, you can increase the timeout. (If you get a timeout type error, you'll know to increase the timeout.) Good luck, 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 Feb 16 23:33: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 6DFD010FB6 for ; Tue, 16 Feb 1999 23:33:00 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA09470 for freebsd-scsi@FreeBSD.ORG; Wed, 17 Feb 1999 08:32:57 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 69C6A1516; Wed, 17 Feb 1999 08:11:51 +0100 (CET) Date: Wed, 17 Feb 1999 08:11:51 +0100 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: Simple 2944 not handled? Message-ID: <19990217081151.A2993@keltia.freenix.fr> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Matthew Jacob on Tue, Feb 16, 1999 at 07:45:36PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5026 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Matthew Jacob: > I'm running 4.0. It's a kernel from today's sources. Too bad- I'd hope it > was dif! I have an HP Vectra XU (P6/200) at work with the internal 7880-based controller (no wide) and a 2944 which use 2 UW drives. I have no problem with it... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 17 0:32:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 13C7510E69 for ; Wed, 17 Feb 1999 00:32:43 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id AAA06218; Wed, 17 Feb 1999 00:32:22 -0800 Date: Wed, 17 Feb 1999 00:32:21 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Ollivier Robert Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Simple 2944 not handled? In-Reply-To: <19990217081151.A2993@keltia.freenix.fr> 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 Yes- and I have other 2940's that're fine... it's just these- but I have swapped them around... On Wed, 17 Feb 1999, Ollivier Robert wrote: > According to Matthew Jacob: > > I'm running 4.0. It's a kernel from today's sources. Too bad- I'd hope it > > was dif! > > I have an HP Vectra XU (P6/200) at work with the internal 7880-based > controller (no wide) and a 2944 which use 2 UW drives. I have no problem > with it... > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 17 11: 1:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 12B3C114A4 for ; Wed, 17 Feb 1999 11:01:43 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id LAA03331; Wed, 17 Feb 1999 11:52:54 -0700 (MST) Date: Wed, 17 Feb 1999 11:52:54 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199902171852.LAA03331@narnia.plutotech.com> To: mjacob@feral.com Cc: scsi@FreeBSD.org Subject: Re: Simple 2944 not handled? X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > I'm having a heckuva a time with the the Adaptec driver- this is with > kernels from 3.0 to today. > > The hardware is a SuperMicro P6DLH- or some such- single 300Mhz Pentium 2, > two PCI busses, etc...I've had 1 through 4 Adaptec 2944 cards > (differential 2940AU variants) installed in this box. My guess is that we've somehow messed up the external transceiver setup. Unfortunately I've never had access to either a 2944 or an HVD peripheral, so I've never tested the driver myself in this kind of configuration. I do have some ideas of things you can try: 1) Try clearing ACTNEGEN in the SXFRCTL1. You can do this in sys/dev/aic7xxx/aic7xxx.c:ahc_init(). The data book is unclear on what effect this feature has in a differential setting and it could be confusing the external HVD transceivers. 2) In ahc_pci.c, take a peek at the DEVCONFIG pci configuration space register. My guess would be that bit 0 is set (DIFACTNEGEN). If it's not set, try setting it. If it is set, try clearing it. Other than those two bits, I can't find any other bits that are specific to differential configurations. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 17 11: 4:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1422211233 for ; Wed, 17 Feb 1999 11:04:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id LAA08327; Wed, 17 Feb 1999 11:03:52 -0800 Date: Wed, 17 Feb 1999 11:03:52 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Simple 2944 not handled? In-Reply-To: <199902171852.LAA03331@narnia.plutotech.com> 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 Thanks! I'll give this a try! On Wed, 17 Feb 1999, Justin T. Gibbs wrote: > In article you wrote: > > > > I'm having a heckuva a time with the the Adaptec driver- this is with > > kernels from 3.0 to today. > > > > The hardware is a SuperMicro P6DLH- or some such- single 300Mhz Pentium 2, > > two PCI busses, etc...I've had 1 through 4 Adaptec 2944 cards > > (differential 2940AU variants) installed in this box. > > My guess is that we've somehow messed up the external transceiver setup. > Unfortunately I've never had access to either a 2944 or an HVD peripheral, > so I've never tested the driver myself in this kind of configuration. I > do have some ideas of things you can try: > > 1) Try clearing ACTNEGEN in the SXFRCTL1. You can do this in > sys/dev/aic7xxx/aic7xxx.c:ahc_init(). The data book is unclear > on what effect this feature has in a differential setting > and it could be confusing the external HVD transceivers. > > 2) In ahc_pci.c, take a peek at the DEVCONFIG pci configuration space > register. My guess would be that bit 0 is set (DIFACTNEGEN). If it's > not set, try setting it. If it is set, try clearing it. > > Other than those two bits, I can't find any other bits that are specific > to differential configurations. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 17 13:25: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id BD9851160C for ; Wed, 17 Feb 1999 13:24:39 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id WAA12860 for ; Wed, 17 Feb 1999 22:24:35 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id WAA81389 for scsi@FreeBSD.ORG; Wed, 17 Feb 1999 22:23:56 +0100 (CET) (envelope-from andreas) Date: Wed, 17 Feb 1999 22:23:56 +0100 From: Andreas Klemm To: scsi@FreeBSD.ORG Subject: 3.0-STABLE: Two AHA 2940 (PCI Slot 4 and 5), hangs during boot Message-ID: <19990217222355.A70160@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.1-STABLE SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi ! I'm trying to find a way to insert my ISA and PCI cards in a way. so that it runs on Win95 and FreeBSD. If I find something, that runs on Win95, it doesn't work in FreeBSD and vice versa. 1. PCI Graphic Card (Matrox Millenium) 2. PCI ELSA ISDN CARD (PCI Version) 3. PCI SOUND CARD (Soundblaster Life) 4. PCI AHA 2940 5. PCI AHA 2940U 6. free 7. WD8013 ISA Network Card Works under Win95, hangs under FreeBSD. IRQ sharing of both AHA controller should work as I heard from Stefan Esser. My board: tyan titan pro S1668 (SMP) SMP kernel... I removed the soundcard .... and have now: 1. PCI ELSA ISDN CARD (PCI Version) 2. PCI Graphic Card (Matrox Millenium) 3. PCI AHA 2940 4. PCI AHA 2940U 5. free 6. free 7. WD8013 ISA Network Card Any ideas ?! Andreas /// Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #0: Tue Feb 16 23:34:00 CET 1999 root@titan.klemm.gtn.com:/home/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 100663296 (98304K bytes) avail memory = 94363648 (92152K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02ed000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ahc0: rev 0x00 int a irq 19 on pci0.11.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x03 int a irq 18 on pci0.12.0 ahc1: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0x01 int a irq 18 on pci0.13.0 isic0: rev 0x01 int a irq 16 on pci0.14.0 isic0: IPAC PSB2115 Version 1.1 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A 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 lpt-265915724: this driver is deprecated; use ppbus instead. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached ccd0-3: Concatenated disk drivers DUMMYNET initialized (980901) -- size dn_pkt 48 Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) da3 at ahc0 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 1006MB (2061108 512 byte sectors: 64H 32S/T 1006C) cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.0MB/s transfers (10.0MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) WARNING: / was not properly dismounted ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 i4b: unit 0, assigned TEI = 99 = 0x63 (da0:ahc0:0:0:0): tagged openings now 32 (da1:ahc1:0:1:0): tagged openings now 32 (da2:ahc1:0:2:0): tagged openings now 32 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 17 19:43:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (Postfix) with ESMTP id E638110E67 for ; Wed, 17 Feb 1999 19:43:26 -0800 (PST) (envelope-from fredriks@Mercury.mcs.net) Received: from Mercury.mcs.net (fredriks@Mercury.mcs.net [192.160.127.80]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id VAA26807; Wed, 17 Feb 1999 21:43:25 -0600 (CST) Received: (from fredriks@localhost) by Mercury.mcs.net (8.8.7/8.8.2) id VAA62712; Wed, 17 Feb 1999 21:43:25 -0600 (CST) From: Lars Fredriksen Message-Id: <199902180343.VAA62712@Mercury.mcs.net> Subject: Re: Simple 2944 not handled? To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Wed, 17 Feb 1999 21:43:25 -0600 (CST) Cc: mjacob@feral.com, scsi@FreeBSD.ORG In-Reply-To: <199902171852.LAA03331@narnia.plutotech.com> from "Justin T. Gibbs" at Feb 17, 99 11:52:54 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have not had any trouble with the 2944 under FreeBSD. I have been following current for a long time and haven't seen any of the problems mentioned here. This is on a SuperMicro P6DNE PP, dmesg says: ahc0: rev 0x03 int a irq 16 on pci0.19.0 Now, it is not clear to me if you had it working and it just broke, or if you never got it working. If it is the latter, there might be something with multiple 2944s. One problem that I have is that the MP table seems to set up a lot of shared interrupts. It isn't clear to me if this is a BIOS bug or if FreeBSD doesn't understand all the ways the Mp table can be configured. Lars Justin T. Gibbs writes: > > In article you wrote: > > > > I'm having a heckuva a time with the the Adaptec driver- this is with > > kernels from 3.0 to today. > > > > The hardware is a SuperMicro P6DLH- or some such- single 300Mhz Pentium 2, > > two PCI busses, etc...I've had 1 through 4 Adaptec 2944 cards > > (differential 2940AU variants) installed in this box. > > My guess is that we've somehow messed up the external transceiver setup. > Unfortunately I've never had access to either a 2944 or an HVD peripheral, > so I've never tested the driver myself in this kind of configuration. I > do have some ideas of things you can try: > > 1) Try clearing ACTNEGEN in the SXFRCTL1. You can do this in > sys/dev/aic7xxx/aic7xxx.c:ahc_init(). The data book is unclear > on what effect this feature has in a differential setting > and it could be confusing the external HVD transceivers. > > 2) In ahc_pci.c, take a peek at the DEVCONFIG pci configuration space > register. My guess would be that bit 0 is set (DIFACTNEGEN). If it's > not set, try setting it. If it is set, try clearing it. > > Other than those two bits, I can't find any other bits that are specific > to differential configurations. > > -- > Justin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@odin-corporation.com (home-home) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 17 20:18:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 86FCE10EBC for ; Wed, 17 Feb 1999 20:18:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id UAA20452; Wed, 17 Feb 1999 20:18:24 -0800 Date: Wed, 17 Feb 1999 20:18:24 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Lars Fredriksen Cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Simple 2944 not handled? In-Reply-To: <199902180343.VAA62712@Mercury.mcs.net> 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 Now this is interesting- Ken Merry said that he wondered why I was using an MP kernel on a single processor system. I didn't actually check the interrupt mapping, but I suppose it's conceivable then that this is just a symptom of interrupts not getting through. This is indeed a Supermicro board. I use SMP definitions a lot so that (presumably) interrupt distribution works more sanely- but if it's broken here then this could have the same effect (albeit the same system with 4 Qlogic's in it hasn't got this problem- so you'd think that ......)- but it's definitely something to try. In fact, I'll risk trying it remotely (the place this system is at is 40 miles away and I won't physically be back there until the end of next week....) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 6:51:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from digistar.digistar.com (digistar.com [12.14.241.201]) by hub.freebsd.org (Postfix) with ESMTP id 29F2910EAD; Thu, 18 Feb 1999 06:51:53 -0800 (PST) (envelope-from freebsd@digistar.com) Received: from localhost (freebsd@localhost) by digistar.digistar.com (8.9.3/8.9.3/jsb) with ESMTP id IAA01754; Thu, 18 Feb 1999 08:51:53 -0600 Date: Thu, 18 Feb 1999 08:51:53 -0600 (CST) From: freebsd@digistar.com To: Undisclosed recipients: ; Subject: data buffers, disk i/o jsb 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 hi, Is there a compile-time option that I can compile into the kernel to improve disk caching/buffering? I'm new to the list; if I'm in the wrong list, my apologies. My concern/question is I have recently put together a 2.2.8 test server and noticed that disk access is not up to expectations and I am looking for a way to remedy it. For example, when doing a du or a find across a single slice, the disk is physically accessed every time I du or find. I had expected the first find or du access to read and buffer the first pass, and the second find or du to read from the disk cache or buffer. It seems like there's a lot of wasted disk i/o when it could be avoided by reading from the disk cache. Also, if I boot from the boot floppy for installtion and install the ports collection, the install moves at a much faster pace, like 15K/s. If I install the ports collection after the install is completed (booting from the hard disk) the install takes FOREVER, like 2K/s and there is a HUGE amount of disk access. Is there a compile-time option that I can compile into the kernel to improve disk caching/buffering? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 10: 8:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.michweb.net (ns2.michweb.net [208.246.108.3]) by hub.freebsd.org (Postfix) with SMTP id 31D03115E0 for ; Thu, 18 Feb 1999 10:08:32 -0800 (PST) (envelope-from matt@ns2.michweb.net) Received: (qmail 9005 invoked by uid 101); 18 Feb 1999 18:08:31 -0000 Date: Thu, 18 Feb 1999 13:08:31 -0500 (EST) From: Matt Simerson Reply-To: Matt Simerson To: freebsd-scsi@freebsd.org Subject: Adaptec 2940U2W & FreeBSD 3.x-anything. 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've just got a new machine in and noticed (much to my chagrin) that it's got a 2940U2W card on board. I didn't think much of it as I popped in my 3.1-current floppy to install. It booted up just fine and I let it install last night. However, this morning after rebooting it fails to boot off the hard drive. :-( It begins the boot process and hangs at the "Waiting 15 seconds for SCSI devices to settle" message. Once there it requires a hard reboot. I've done some searching of the mailing list archives to find related details and it looks like CAM support is what I need, so: What version(s) of FreeBSD will work in this config? I'd much rather be tracking the STABLE tree than the CURRENT one but I do need to be using a version that supports this card and drive(s). Oddly enough, I reinstalled a "minimum" install from the 3.1-RELEASE tree again and now it boots. :-P The kernel's are exactly the same size but the old one didn't boot. So, should this always work and the hanging problem an isolated incident? TIA, Matt `````````````````````````````````````````````````````````````````` Matt Simerson http://users.michweb.net/~matt MichWeb Inc. - President http://www.michweb.net The Art Farm - Technical Wizard http://www.theartfarm.com ISP/C - Treasurer http://www.ispc.org The chief danger in life is that you may take too many precautions. - Alfred Adler `````````````````````````````````````````````````````````````````` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 15: 6:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id AF94811BDE for ; Thu, 18 Feb 1999 15:06:04 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id AAA09867; Fri, 19 Feb 1999 00:05:53 +0100 (CET) (envelope-from des) To: scsi@freebsd.org Subject: indefinite wait buffer From: Dag-Erling Smorgrav Date: 19 Feb 1999 00:05:45 +0100 Message-ID: Lines: 20 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 'dd if=/dev/zero of=/dev/da0 bs=65536' (to force the drive to remap bad sectors) caused the following error messages: Feb 19 00:00:20 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 Feb 19 00:01:00 flood last message repeated 2 times Feb 19 00:03:00 flood last message repeated 6 times Feb 19 00:03:05 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 256, size: 4096 Feb 19 00:03:20 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 Feb 19 00:03:25 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 256, size: 4096 Feb 19 00:03:40 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 Feb 19 00:03:45 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 256, size: 4096 Feb 19 00:04:00 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 They keep coming every 5-15 seconds. The box is running FreeBSD 3.1-STABLE (post-RELEASE) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 15:35:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 227A8118C6 for ; Thu, 18 Feb 1999 15:35:18 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id QAA04655; Thu, 18 Feb 1999 16:35:12 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902182335.QAA04655@panzer.plutotech.com> Subject: Re: indefinite wait buffer In-Reply-To: from Dag-Erling Smorgrav at "Feb 19, 1999 0: 5:45 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Thu, 18 Feb 1999 16:35:12 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Dag-Erling Smorgrav wrote... > 'dd if=/dev/zero of=/dev/da0 bs=65536' (to force the drive to remap > bad sectors) caused the following error messages: > > Feb 19 00:00:20 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 > Feb 19 00:01:00 flood last message repeated 2 times > Feb 19 00:03:00 flood last message repeated 6 times > Feb 19 00:03:05 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 256, size: 4096 > Feb 19 00:03:20 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 > Feb 19 00:03:25 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 256, size: 4096 > Feb 19 00:03:40 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 > Feb 19 00:03:45 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 256, size: 4096 > Feb 19 00:04:00 flood /kernel: swap_pager: indefinite wait buffer: device: 0x401, blkno: 1064, size: 20480 > > They keep coming every 5-15 seconds. > > The box is running FreeBSD 3.1-STABLE (post-RELEASE) That generally happens when the disk stops responding for some reason. What disk is your swap on? I assume you aren't doing the dd to a disk that you're actually using... Did you see any SCSI-type errors around the time of the indefinite wait buffer error message? 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 Thu Feb 18 15:41:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 79A3A11BF9 for ; Thu, 18 Feb 1999 15:40:31 -0800 (PST) (envelope-from r3cgm@pike.cdrom.com) Received: (from r3cgm@localhost) by pike.cdrom.com (8.9.1a/8.9.1) id PAA07564 for freebsd-scsi@freebsd.org; Thu, 18 Feb 1999 15:41:19 -0800 (PST) Date: Thu, 18 Feb 1999 15:41:19 -0800 From: "Christopher G. Mann" To: freebsd-scsi@freebsd.org Subject: Unusual CAM Error w/FreeBSD 3.1 (tosha) Message-ID: <19990218154119.A7504@cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings FreeBSD SCSI Team, Two days ago, I installed FreeBSD 3.1 from CDROM (we get them 2 weeks earlier than anyone else, neener neener). :) I immediately set up cvsup for my /ports and /src tree to run daily. Yesterday I installed tosha from /ports. Some time ago I wrote a utility to rip audio tracks and encode them, and I parse "tosha -i" output to determine how many songs there are. Recently I purchased a "slot-in" Pioneer CDROM drive... 32x SCSI. It didn't work with my old system at all (which was originally installed as 2.2.5 and make world'ed every week or so until I finally nuked it). I would frequently get fatal SCSI read errors with it that eventually would make the system unstable enough so that I would have to reboot. The CAM support in 3.x seems to have solved that problem. I can mount the cdrom drive, I can dd images from it, I can even use workman to play tunes like a pro, but the simple act of using tosha to get info from any audio CD generates weird cam errors. [beacon.cdrom.com : r3cgm] ~ - tosha -i tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied [beacon.cdrom.com : r3cgm] ~ - ls -l /usr/local/bin/tosha -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 /usr/local/bin/tosha [beacon.cdrom.com : r3cgm] ~ - su -m Password: %tosha -i tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied %tosha -i -d /dev/cd0a tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied %tosha -i -d /dev/cd0c tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied %tosha -i -d /dev/cd1a tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied %tosha -i -d /dev/cd1c tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied %ls -l /dev/x* crw------- 1 root operator 104, 0 Feb 16 16:56 /dev/xpt0 crw------- 1 root operator 104, 1 Feb 16 16:56 /dev/xpt1 %ls -l /dev/pas* crw------- 1 root operator 31, 0 Feb 16 16:56 /dev/pass0 crw------- 1 root operator 31, 1 Feb 16 16:56 /dev/pass1 crw------- 1 root operator 31, 2 Feb 16 16:56 /dev/pass2 crw------- 1 root operator 31, 3 Feb 16 16:56 /dev/pass3 %fgrep "pass" /usr/src/sys/i386/conf/BEACON device pass0 I have tried rebooting, but the behavior is the same. Here is my dmesg VERBOSE output. Please let me know if you can think of anything to try. vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000e800, size 4 found-> vendor=0x102b, dev=0x051a, revid=0x03 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base fb800000, size 23 map[1]: type 1, range 32, base fa800000, size 14 map[2]: type 1, range 32, base fa000000, size 23 vga0: rev 0x03 int a irq 9 on pci0.10.0 found-> vendor=0x1011, dev=0x0009, revid=0x20 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[0]: type 4, range 32, base 0000e000, size 7 map[1]: type 1, range 32, base f9800000, size 7 de0: rev 0x20 int a irq 12 on pci0.11.0 de0: 21140A [10-100Mb/s] pass 2.0 de0: address 00:80:c8:3e:34:08 bpf: de0 attached found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000d800, size 8 map[1]: type 1, range 32, base f9000000, size 12 ahc0: rev 0x00 int a irq 10 on pci0.12.0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable is present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 413 instructions downloaded Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: current command byte:0067 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in scd0 not found at 0x230 ppc0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 181818181 bytes/sec bzero() bandwidth = 96283458 bytes/sec sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: imasks: bio c0080040, tty c003001a, net c0061000 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: lo0 attached Waiting 7 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:3. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted (probe2:ahc0:0:2:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe2:ahc0:0:2:0): ILLEGAL REQUEST asc:24,0 (probe2:ahc0:0:2:0): Invalid field in CDB (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0 (probe4:ahc0:0:4:0): Invalid field in CDB ahc0: target 2 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0x8 ahc0: target 6 synchronous at 10.0MHz, offset = 0xf ahc0: target 1 synchronous at 10.0MHz, offset = 0xf pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 5U0F7361 pass0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number 03010448 pass1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 0 pass2: Removable CD-ROM SCSI-2 device pass2: 20.0MB/s transfers (20.0MHz, offset 15) pass3 at ahc0 bus 0 target 4 lun 0 pass3: Removable CD-ROM SCSI-2 device pass3: 3.300MB/s transfers pass4 at ahc0 bus 0 target 6 lun 0 pass4: Fixed Direct Access SCSI-2 device pass4: Serial Number EF94LBD pass4: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.0MB/s transfers (20.0MHz, offset 15) cd0: cd present [269544 x 2048 byte records] da2 at ahc0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number EF94LBD da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number 03010448 da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s1a (cd1:ahc0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc0:0:4:0): NOT READY asc:3a,0 (cd1:ahc0:0:4:0): Medium not present cd1 at ahc0 bus 0 target 4 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 5U0F7361 da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0s1: type 0xa5, start 63, end = 4225094, size 4225032 : OK da2s1: type 0xa5, start 63, end = 4192964, size 4192902 : OK Linux-ELF exec handler installed splash: image decoder found: logo_saver (da0:ahc0:0:0:0): tagged openings now 32 -- Christopher G. Mann - IT Manager, Webmaster Walnut Creek CDROM (www.cdrom.com) The FreeBSD Mall (www.freebsdmall.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 15:45:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 55A1A11C3D for ; Thu, 18 Feb 1999 15:45:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id AAA11231; Fri, 19 Feb 1999 00:45:18 +0100 (CET) (envelope-from des) To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: indefinite wait buffer References: <199902182335.QAA04655@panzer.plutotech.com> From: Dag-Erling Smorgrav Date: 19 Feb 1999 00:45:18 +0100 In-Reply-To: "Kenneth D. Merry"'s message of "Thu, 18 Feb 1999 16:35:12 -0700 (MST)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > That generally happens when the disk stops responding for some reason. > > What disk is your swap on? I assume you aren't doing the dd to a disk that > you're actually using... Uh-oh, I forgot about that :) Fortunately the box isn't swapping at all - yet :) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 15:48:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 29ADD11C58 for ; Thu, 18 Feb 1999 15:48:19 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id QAA04769; Thu, 18 Feb 1999 16:48:12 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902182348.QAA04769@panzer.plutotech.com> Subject: Re: indefinite wait buffer In-Reply-To: from Dag-Erling Smorgrav at "Feb 19, 1999 0:45:18 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Thu, 18 Feb 1999 16:48:12 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Dag-Erling Smorgrav wrote... > "Kenneth D. Merry" writes: > > That generally happens when the disk stops responding for some reason. > > > > What disk is your swap on? I assume you aren't doing the dd to a disk that > > you're actually using... > > Uh-oh, I forgot about that :) Fortunately the box isn't swapping at > all - yet :) It was trying to, that's why you got the error messages from the swap pager. :) 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 Thu Feb 18 15:56:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 6CE8C11836 for ; Thu, 18 Feb 1999 15:56:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id AAA00601; Fri, 19 Feb 1999 00:56:20 +0100 (CET) (envelope-from des) To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: indefinite wait buffer References: <199902182348.QAA04769@panzer.plutotech.com> From: Dag-Erling Smorgrav Date: 19 Feb 1999 00:56:19 +0100 In-Reply-To: "Kenneth D. Merry"'s message of "Thu, 18 Feb 1999 16:48:12 -0700 (MST)" Message-ID: Lines: 17 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > Dag-Erling Smorgrav wrote... > > "Kenneth D. Merry" writes: > > > What disk is your swap on? I assume you aren't doing the dd to a disk that > > > you're actually using... > > Uh-oh, I forgot about that :) Fortunately the box isn't swapping at > > all - yet :) > It was trying to, that's why you got the error messages from the swap > pager. :) Yeah. I removed that line from /etc/fstab and rebooted. (so *that's* why sendmail kept SIGSEGVing - lol) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 16:40:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F9011BAE for ; Thu, 18 Feb 1999 16:40:10 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id RAA05032; Thu, 18 Feb 1999 17:40:02 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902190040.RAA05032@panzer.plutotech.com> Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) In-Reply-To: <19990218154119.A7504@cdrom.com> from "Christopher G. Mann" at "Feb 18, 1999 3:41:19 pm" To: r3cgm@cdrom.com (Christopher G. Mann) Date: Thu, 18 Feb 1999 17:40:02 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Christopher G. Mann wrote... > Greetings FreeBSD SCSI Team, > > Two days ago, I installed FreeBSD 3.1 from CDROM (we get them 2 weeks > earlier than anyone else, neener neener). :) I immediately set up > cvsup for my /ports and /src tree to run daily. Yesterday I installed > tosha from /ports. Some time ago I wrote a utility to rip audio tracks > and encode them, and I parse "tosha -i" output to determine how many > songs there are. > > Recently I purchased a "slot-in" Pioneer CDROM drive... 32x SCSI. It > didn't work with my old system at all (which was originally installed as > 2.2.5 and make world'ed every week or so until I finally nuked it). I > would frequently get fatal SCSI read errors with it that eventually > would make the system unstable enough so that I would have to reboot. > The CAM support in 3.x seems to have solved that problem. > > I can mount the cdrom drive, I can dd images from it, I can even use > workman to play tunes like a pro, but the simple act of using tosha to > get info from any audio CD generates weird cam errors. I must say I'm quite perplexed by this one. > [beacon.cdrom.com : r3cgm] ~ - tosha -i > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > > [beacon.cdrom.com : r3cgm] ~ - ls -l /usr/local/bin/tosha > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 /usr/local/bin/tosha > > [beacon.cdrom.com : r3cgm] ~ - su -m > Password: > > %tosha -i > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > > %tosha -i -d /dev/cd0a > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > %tosha -i -d /dev/cd0c > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > %tosha -i -d /dev/cd1a > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > %tosha -i -d /dev/cd1c > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > > %ls -l /dev/x* > crw------- 1 root operator 104, 0 Feb 16 16:56 /dev/xpt0 > crw------- 1 root operator 104, 1 Feb 16 16:56 /dev/xpt1 > %ls -l /dev/pas* > crw------- 1 root operator 31, 0 Feb 16 16:56 /dev/pass0 > crw------- 1 root operator 31, 1 Feb 16 16:56 /dev/pass1 > crw------- 1 root operator 31, 2 Feb 16 16:56 /dev/pass2 > crw------- 1 root operator 31, 3 Feb 16 16:56 /dev/pass3 > > %fgrep "pass" /usr/src/sys/i386/conf/BEACON > device pass0 > > I have tried rebooting, but the behavior is the same. Here is my dmesg > VERBOSE output. Please let me know if you can think of anything to try. Can you try the following: camcontrol devlist camcontrol tur -n cd -u 0 -v Do you have your securelevel set to anything non-standard? (i.e., have you set the kern.securelevel sysctl variable at all?) As far as I can tell, there's nothing in the XPT device open routine that could return EACCES (i.e. Permission denied). Hopefully the camcontrol commands above will help us diagnose the problem a little more... 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 Thu Feb 18 16:45:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 91DF411721 for ; Thu, 18 Feb 1999 16:45:39 -0800 (PST) (envelope-from r3cgm@pike.cdrom.com) Received: (from r3cgm@localhost) by pike.cdrom.com (8.9.1a/8.9.1) id QAA08755; Thu, 18 Feb 1999 16:45:55 -0800 (PST) Date: Thu, 18 Feb 1999 16:45:54 -0800 From: "Christopher G. Mann" To: "Kenneth D. Merry" Cc: freebsd-scsi@freebsd.org Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) Message-ID: <19990218164554.B7822@cdrom.com> References: <19990218154119.A7504@cdrom.com> <199902190040.RAA05032@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902190040.RAA05032@panzer.plutotech.com>; from Kenneth D. Merry on Thu, Feb 18, 1999 at 05:40:02PM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : Can you try the following: : : camcontrol devlist : camcontrol tur -n cd -u 0 -v : : Do you have your securelevel set to anything non-standard? (i.e., have you : set the kern.securelevel sysctl variable at all?) : : As far as I can tell, there's nothing in the XPT device open routine that : could return EACCES (i.e. Permission denied). : : Hopefully the camcontrol commands above will help us diagnose the problem a : little more... : : Ken : -- : Kenneth Merry : ken@plutotech.com %camcontrol devlist < > at scbus-1 target -1 lun -1 (xpt0) at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,cd0) at scbus0 target 4 lun 0 (pass3,cd1) at scbus0 target 6 lun 0 (pass4,da2) < > at scbus0 target -1 lun -1 () %camcontrol tur -n cd -u 0 -v Unit is ready I haven't tickled the securelevel settings at all. : ----------------------------- Kenneth D. Merry : Christopher G. Mann wrote... : > Greetings FreeBSD SCSI Team, : > : > Two days ago, I installed FreeBSD 3.1 from CDROM (we get them 2 weeks : > earlier than anyone else, neener neener). :) I immediately set up : > cvsup for my /ports and /src tree to run daily. Yesterday I installed : > tosha from /ports. Some time ago I wrote a utility to rip audio tracks : > and encode them, and I parse "tosha -i" output to determine how many : > songs there are. : > : > Recently I purchased a "slot-in" Pioneer CDROM drive... 32x SCSI. It : > didn't work with my old system at all (which was originally installed as : > 2.2.5 and make world'ed every week or so until I finally nuked it). I : > would frequently get fatal SCSI read errors with it that eventually : > would make the system unstable enough so that I would have to reboot. : > The CAM support in 3.x seems to have solved that problem. : > : > I can mount the cdrom drive, I can dd images from it, I can even use : > workman to play tunes like a pro, but the simple act of using tosha to : > get info from any audio CD generates weird cam errors. : : I must say I'm quite perplexed by this one. : : : > [beacon.cdrom.com : r3cgm] ~ - tosha -i : > tosha: cam_lookup_pass: couldn't open /dev/xpt0 : > cam_lookup_pass: Permission denied : > : > [beacon.cdrom.com : r3cgm] ~ - ls -l /usr/local/bin/tosha : > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 /usr/local/bin/tosha : > : > [beacon.cdrom.com : r3cgm] ~ - su -m : > Password: : > : > %tosha -i : > tosha: cam_lookup_pass: couldn't open /dev/xpt0 : > cam_lookup_pass: Permission denied : > : > %tosha -i -d /dev/cd0a : > tosha: cam_lookup_pass: couldn't open /dev/xpt0 : > cam_lookup_pass: Permission denied : > %tosha -i -d /dev/cd0c : > tosha: cam_lookup_pass: couldn't open /dev/xpt0 : > cam_lookup_pass: Permission denied : > %tosha -i -d /dev/cd1a : > tosha: cam_lookup_pass: couldn't open /dev/xpt0 : > cam_lookup_pass: Permission denied : > %tosha -i -d /dev/cd1c : > tosha: cam_lookup_pass: couldn't open /dev/xpt0 : > cam_lookup_pass: Permission denied : > : > %ls -l /dev/x* : > crw------- 1 root operator 104, 0 Feb 16 16:56 /dev/xpt0 : > crw------- 1 root operator 104, 1 Feb 16 16:56 /dev/xpt1 : > %ls -l /dev/pas* : > crw------- 1 root operator 31, 0 Feb 16 16:56 /dev/pass0 : > crw------- 1 root operator 31, 1 Feb 16 16:56 /dev/pass1 : > crw------- 1 root operator 31, 2 Feb 16 16:56 /dev/pass2 : > crw------- 1 root operator 31, 3 Feb 16 16:56 /dev/pass3 : > : > %fgrep "pass" /usr/src/sys/i386/conf/BEACON : > device pass0 : > : > I have tried rebooting, but the behavior is the same. Here is my dmesg : > VERBOSE output. Please let me know if you can think of anything to try. : -- Christopher G. Mann - IT Manager, Webmaster Walnut Creek CDROM (www.cdrom.com) The FreeBSD Mall (www.freebsdmall.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 16:53: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F84311649 for ; Thu, 18 Feb 1999 16:52:48 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id RAA05099; Thu, 18 Feb 1999 17:52:30 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902190052.RAA05099@panzer.plutotech.com> Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) In-Reply-To: <19990218164554.B7822@cdrom.com> from "Christopher G. Mann" at "Feb 18, 1999 4:45:54 pm" To: r3cgm@cdrom.com (Christopher G. Mann) Date: Thu, 18 Feb 1999 17:52:30 -0700 (MST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (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 Christopher G. Mann wrote... > : Can you try the following: > : > : camcontrol devlist > : camcontrol tur -n cd -u 0 -v > : > : Do you have your securelevel set to anything non-standard? (i.e., have you > : set the kern.securelevel sysctl variable at all?) > : > : As far as I can tell, there's nothing in the XPT device open routine that > : could return EACCES (i.e. Permission denied). > : > : Hopefully the camcontrol commands above will help us diagnose the problem a > : little more... > : > : Ken > : -- > : Kenneth Merry > : ken@plutotech.com > > %camcontrol devlist > < > at scbus-1 target -1 lun -1 (xpt0) > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,cd0) > at scbus0 target 4 lun 0 (pass3,cd1) > at scbus0 target 6 lun 0 (pass4,da2) > < > at scbus0 target -1 lun -1 () > %camcontrol tur -n cd -u 0 -v > Unit is ready > > I haven't tickled the securelevel settings at all. We're getting somewhere now, but this is still very odd. Your xpt device is obviously working properly, otherwise you would get no output from camcontrol devlist. Just for grins, could you try disabling the setuid bit on tosha, and then running tosha -i as root? 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 Thu Feb 18 17:33:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 76FA011B04 for ; Thu, 18 Feb 1999 17:32:29 -0800 (PST) (envelope-from r3cgm@pike.cdrom.com) Received: (from r3cgm@localhost) by pike.cdrom.com (8.9.1a/8.9.1) id RAA09490; Thu, 18 Feb 1999 17:32:46 -0800 (PST) Date: Thu, 18 Feb 1999 17:32:45 -0800 From: "Christopher G. Mann" To: "Kenneth D. Merry" Cc: freebsd-scsi@freebsd.org Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) Message-ID: <19990218173245.C7822@cdrom.com> References: <19990218164554.B7822@cdrom.com> <199902190052.RAA05099@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902190052.RAA05099@panzer.plutotech.com>; from Kenneth D. Merry on Thu, Feb 18, 1999 at 05:52:30PM -0700 X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Arg! %ls -l tosha -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha %chmod 755 tosha %ls -l tosha -rwxr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha %./tosha -i Device: /dev/cd0c -- "PIONEER" "CD-ROM DR-U16S" "1.01" track playing start end raw size mp3 size # of track number time sector sector in bytes 128 kbps frames type --------------------------------------------------------------------- 1 1:08'50 0 5149 12112800 1099501 2629 audio 2 4:30'71 5150 25470 47794992 4335981 10373 audio 3 6:23'47 25471 54242 67671744 6138861 14686 audio 4 6:16'68 54243 82510 66486336 6031341 14429 audio 5 5:20'68 82511 106578 56607936 5135341 12285 audio 6 6:04'34 106579 133912 64289568 5832088 13952 audio 7 4:39'41 133913 154878 49312032 4473581 10702 audio 8 7:45'59 154879 189812 82164768 7453421 17831 audio 9 7:32'22 189813 223734 79784544 7237528 17315 audio 10 10:10'59 223735 269543 107742768 9773421 23382 audio --------------------------------------------------------------------- total 59:53'69 269544 sectors 633967488 57586311 137580 %chmod 4755 tosha %./tosha -i tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied [beacon : r3cgm] ~ - tosha -i tosha: cam_lookup_pass: couldn't open /dev/xpt0 cam_lookup_pass: Permission denied What the heck? Well, my problem appears to be partially solved, but I'm not so certain the answer helps the "cause" much. I can't seem to run "tosha -i" as a normal user without getting the CAM error, and I can't seem to suid the utility as root to get around it. Thoughts? : ----------------------------- Kenneth D. Merry : Christopher G. Mann wrote... : > : Can you try the following: : > : : > : camcontrol devlist : > : camcontrol tur -n cd -u 0 -v : > : : > : Do you have your securelevel set to anything non-standard? (i.e., have you : > : set the kern.securelevel sysctl variable at all?) : > : : > : As far as I can tell, there's nothing in the XPT device open routine that : > : could return EACCES (i.e. Permission denied). : > : : > : Hopefully the camcontrol commands above will help us diagnose the problem a : > : little more... : > : : > : Ken : > : -- : > : Kenneth Merry : > : ken@plutotech.com : > : > %camcontrol devlist : > < > at scbus-1 target -1 lun -1 (xpt0) : > at scbus0 target 0 lun 0 (pass0,da0) : > at scbus0 target 1 lun 0 (pass1,da1) : > at scbus0 target 2 lun 0 (pass2,cd0) : > at scbus0 target 4 lun 0 (pass3,cd1) : > at scbus0 target 6 lun 0 (pass4,da2) : > < > at scbus0 target -1 lun -1 () : > %camcontrol tur -n cd -u 0 -v : > Unit is ready : > : > I haven't tickled the securelevel settings at all. : : We're getting somewhere now, but this is still very odd. Your xpt device : is obviously working properly, otherwise you would get no output from : camcontrol devlist. : : Just for grins, could you try disabling the setuid bit on tosha, and then : running tosha -i as root? : : Ken : -- : Kenneth Merry : ken@plutotech.com -- Christopher G. Mann - IT Manager, Webmaster Walnut Creek CDROM (www.cdrom.com) The FreeBSD Mall (www.freebsdmall.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 17:53:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FF9211CF7 for ; Thu, 18 Feb 1999 17:52:29 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id SAA05557; Thu, 18 Feb 1999 18:52:24 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902190152.SAA05557@panzer.plutotech.com> Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) In-Reply-To: <19990218173245.C7822@cdrom.com> from "Christopher G. Mann" at "Feb 18, 1999 5:32:45 pm" To: r3cgm@cdrom.com (Christopher G. Mann) Date: Thu, 18 Feb 1999 18:52:24 -0700 (MST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (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 Christopher G. Mann wrote... > Arg! > > %ls -l tosha > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha > > %chmod 755 tosha > > %ls -l tosha > -rwxr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha > > %./tosha -i > Device: /dev/cd0c -- "PIONEER" "CD-ROM DR-U16S" "1.01" > > track playing start end raw size mp3 size # of track > number time sector sector in bytes 128 kbps frames type > --------------------------------------------------------------------- > 1 1:08'50 0 5149 12112800 1099501 2629 audio > 2 4:30'71 5150 25470 47794992 4335981 10373 audio > 3 6:23'47 25471 54242 67671744 6138861 14686 audio > 4 6:16'68 54243 82510 66486336 6031341 14429 audio > 5 5:20'68 82511 106578 56607936 5135341 12285 audio > 6 6:04'34 106579 133912 64289568 5832088 13952 audio > 7 4:39'41 133913 154878 49312032 4473581 10702 audio > 8 7:45'59 154879 189812 82164768 7453421 17831 audio > 9 7:32'22 189813 223734 79784544 7237528 17315 audio > 10 10:10'59 223735 269543 107742768 9773421 23382 audio > --------------------------------------------------------------------- > total 59:53'69 269544 sectors 633967488 57586311 137580 > > %chmod 4755 tosha > > %./tosha -i > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > > [beacon : r3cgm] ~ - tosha -i > tosha: cam_lookup_pass: couldn't open /dev/xpt0 > cam_lookup_pass: Permission denied > > What the heck? Well, my problem appears to be partially solved, but I'm > not so certain the answer helps the "cause" much. I can't seem to run > "tosha -i" as a normal user without getting the CAM error, and I can't > seem to suid the utility as root to get around it. > > Thoughts? Do you have any mount options on the filesystem that contains /usr/local? Can you send the output of 'mount'? Another alternative is putting the xpt and pass devices in a particular group that you're also in, and then chmod them 660. That's what I generally do. I'm in the operator group, so this works for me: {panzer:/usr/home/ken:4:0} ls -la /dev/xpt* /dev/pass* crw-rw---- 1 root operator 31, 0 Sep 20 00:15 /dev/pass0 crw-rw---- 1 root operator 31, 1 Sep 20 00:15 /dev/pass1 crw-rw---- 1 root operator 31, 2 Sep 20 00:15 /dev/pass2 crw-rw---- 1 root operator 31, 3 Sep 20 00:15 /dev/pass3 crw-rw---- 1 root operator 31, 4 Sep 20 00:15 /dev/pass4 crw-rw---- 1 root operator 31, 5 Sep 20 00:15 /dev/pass5 crw-rw---- 1 root operator 31, 6 Sep 20 00:15 /dev/pass6 crw-rw---- 1 root operator 31, 7 Sep 20 00:15 /dev/pass7 crw-rw---- 1 root operator 104, 0 Sep 20 00:15 /dev/xpt0 crw-rw---- 1 root operator 104, 1 Sep 20 00:15 /dev/xpt1 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 Thu Feb 18 20: 1:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (Postfix) with ESMTP id 5465610E92 for ; Thu, 18 Feb 1999 20:01:41 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id WAA07997 for ; Thu, 18 Feb 1999 22:01:35 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id VAA23291; Thu, 18 Feb 1999 21:57:22 -0600 Message-ID: <19990218215721.55546@right.PCS> Date: Thu, 18 Feb 1999 21:57:21 -0600 From: Jonathan Lemon To: freebsd-scsi@freebsd.org Subject: slow disk performance Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a system with the following: ahc0: rev 0x01 int a irq 11 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Basically, an ASUS motherboard with an onboard Adaptec, along with two 7200 rpm disks. However, I can't seem to get more than 6MB/sec out of the drives, when doing sequential reads or writes: dd if=/dev/rda1 of=/dev/null bs=64k & dd if=/dev/rda0 of=/dev/null bs=64k & iostat 1 tty fd0 da0 da1 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 77 0.00 0 0.00 64.00 115 7.17 64.00 103 6.42 0 0 1 1 98 0 76 0.00 0 0.00 64.00 102 6.37 64.00 100 6.25 0 0 1 1 98 0 76 0.00 0 0.00 64.00 118 7.36 64.00 103 6.44 0 0 5 0 95 Is this the maximum I can expect to get from the drives? I get the same speeds when doing sequential writes as well; I would think it can do etter than this. There are no "tagged opening" messages in the logfile, so this is with 64 tags. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 18 22:43:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F2BB11077; Thu, 18 Feb 1999 22:43:44 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id HAA02311; Fri, 19 Feb 1999 07:43:41 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id HAA36231; Fri, 19 Feb 1999 07:12:09 +0100 (CET) (envelope-from andreas) Date: Fri, 19 Feb 1999 07:12:09 +0100 From: Andreas Klemm To: Paul van der Zwan Cc: freebsd-current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Slow seq. write on Seagate ST36530N Message-ID: <19990219071209.B35927@titan.klemm.gtn.com> References: <199902182224.XAA00605@trantor.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199902182224.XAA00605@trantor.xs4all.nl>; from Paul van der Zwan on Thu, Feb 18, 1999 at 11:24:21PM +0100 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.1-STABLE SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sounds familiar to me. I had trouble with a Seagate Wide scsi harddisk in a HP Kajak. First thought it's the NCR. Repllaces it with a AHA 2940UW. Nothing helps. Installed FreeBSD 2.2.7. With 2.2.7 the disk maxed at about 12 MB/sec write and write. When I enabled tagged command queuing in 2.2.7, the write performance went down to 2 MB/sec. Using 3.0/3.1 disabling tagged command queuing didn't help. When only reducing the number of tags from 64 (which the drive supported/CAM reported) to 8/16 (min/max) I got a SCSI race condition, error messages of SCSI bus. Well, now I'm using 2.2.8-STABLE :-) Had loved to use 3.1, but no way ... This is now the 2nd problem ... Perhaps our scsi gurus have to look at it ?! I can't send my drive to Kenneth or Justin, sorry. Andreas /// On Thu, Feb 18, 1999 at 11:24:21PM +0100, Paul van der Zwan wrote: > > I am having some performance problems on my -current ( update last weekend) > I hooked up a new Seagate ST36530N yesterday ( connected to an Adaptec 2940U) > and sequential write is very slow. > Compared to an IBM DORS-32160 connected to the same controller ( even the same > cable) it is half as fast. > Iozone auto shows the following : > > Seagate > IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) > By Bill Norcott > > Operating System: FreeBSD 2.x -- using fsync() > > IOZONE: auto-test mode > > MB reclen bytes/sec written bytes/sec read > 1 512 5835553 22369621 > 1 1024 3627506 33554432 > 1 2048 3441480 44739242 > 1 4096 4329604 44739242 > 1 8192 3121342 67108864 > 2 512 3627506 22369621 > 2 1024 4260880 44739242 > 2 2048 3273603 38347922 > 2 4096 4067203 67108864 > 2 8192 4067203 67108864 > 4 512 4161790 21474836 > 4 1024 2354696 35791394 > 4 2048 2418337 38347922 > 4 4096 2418337 59652323 > 4 8192 1988410 53687091 > 8 512 2863311 20259279 > 8 1024 1565221 37025580 > 8 2048 1470879 31580641 > 8 4096 1514445 48806446 > 8 8192 1337162 56512727 > 16 512 2041334 14412641 > 16 1024 1536111 27531841 > 16 2048 1476948 43826196 > 16 4096 1410961 48806446 > 16 8192 1432610 52377649 > > IBM > MB reclen bytes/sec written bytes/sec read > 1 512 3728270 22369621 > 1 1024 4067203 26843545 > 1 2048 3947580 67108864 > 1 4096 3728270 44739242 > 1 8192 3834792 67108864 > 2 512 4549753 13421772 > 2 1024 4194304 44739242 > 2 2048 3890368 53687091 > 2 4096 4400581 67108864 > 2 8192 3677198 67108864 > 4 512 4129776 21474836 > 4 1024 3532045 44739242 > 4 2048 2451465 53687091 > 4 4096 3016128 59652323 > 4 8192 2870967 53687091 > 8 512 2396745 21053761 > 8 1024 2894182 37025580 > 8 2048 2587329 42949672 > 8 4096 2526451 51130563 > 8 8192 2520520 56512727 > 16 512 3067833 20069940 > 16 1024 2701237 34087042 > 16 2048 3591109 43826196 > 16 4096 2306641 42949672 > 16 8192 3121342 52377649 > > Bonnie shows the following: > Seagate > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 100 3251 44.0 1307 4.0 2285 11.5 5006 69.0 8644 23.0 115.1 4.2 > IBM > 100 3333 45.0 2533 8.8 1878 10.1 4244 58.2 5140 19.7 76.4 3.3 > > If I interpret it correctly the Seagate is faster in everything but sequential > writes. > dmesg shows the following : > > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da1: 6208MB (12715920 512 byte sectors: 255H 63S/T 791C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > > Anybody an idea ?? > > Paul > > -- > Paul van der Zwan paulz @ trantor.xs4all.nl > "I think I'll move to theory, everything works in theory..." > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 2: 5:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 285F81141D for ; Fri, 19 Feb 1999 02:05:43 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 18944 invoked by uid 1001); 19 Feb 1999 10:05:41 +0000 (GMT) To: jlemon@americantv.com Cc: freebsd-scsi@freebsd.org Subject: Re: slow disk performance From: sthaug@nethelp.no In-Reply-To: Your message of "Thu, 18 Feb 1999 21:57:21 -0600" References: <19990218215721.55546@right.PCS> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 19 Feb 1999 11:05:41 +0100 Message-ID: <18942.919418741@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a system with the following: > > ahc0: rev 0x01 int a irq 11 on pci0.6.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > > > Basically, an ASUS motherboard with an onboard Adaptec, along with > two 7200 rpm disks. The DCAS-34330W is a 5400 RPM disk. > However, I can't seem to get more than 6MB/sec > out of the drives, when doing sequential reads or writes: I get around 7.5 MB/s reading from the raw device on my DCAS-34330W, using an NCR875 based controller (Tekram). Somewhat less when writing. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 4:20:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 0523D10E7B for ; Fri, 19 Feb 1999 04:19:11 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 19 Feb 99 12:18:52 +0000 (GMT) To: "Kenneth D. Merry" Cc: "Christopher G. Mann" , freebsd-scsi@freebsd.org Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) In-reply-to: Your message of "Thu, 18 Feb 1999 18:52:24 MST." <199902190152.SAA05557@panzer.plutotech.com> X-Request-Do: Date: Fri, 19 Feb 1999 12:18:51 +0000 From: David Malone Message-ID: <9902191218.aa16968@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > %ls -l tosha > > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha Surely suid bin isn't going to be very useful to tosha? Shouldn't it be suid root or sgid operator or something? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 4:34:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (Postfix) with ESMTP id 47197117AC for ; Fri, 19 Feb 1999 04:29:51 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: (from rohrbach@localhost) by mail.nacamar.de (8.8.7/8.8.8MB-19980212) id NAA06446; Fri, 19 Feb 1999 13:27:49 +0100 (CET) Message-ID: <19990219132746.A4754@nacamar.net> Date: Fri, 19 Feb 1999 13:27:46 +0100 From: "Karsten W. Rohrbach" To: David Malone , "Kenneth D. Merry" Cc: "Christopher G. Mann" , freebsd-scsi@FreeBSD.ORG Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) Reply-To: rohrbach@nacamar.net Mail-Followup-To: David Malone , "Kenneth D. Merry" , "Christopher G. Mann" , freebsd-scsi@FreeBSD.ORG References: <199902190152.SAA05557@panzer.plutotech.com> <9902191218.aa16968@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <9902191218.aa16968@salmon.maths.tcd.ie>; from David Malone on Fri, Feb 19, 1999 at 12:18:51PM +0000 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org definately, but also some of the "hook-devs" in /dev like xpt? for example should be root.operator and mode 660 or root.wheel or whatever. if theres no standardization in the next time, a lot of audio/multimedia packages will grow wild with suid executables where we wont need/want them i guess - and theres no harder pain in the ass than defect hardware and suid binaries. /k David Malone (dwmalone@maths.tcd.ie) @ Fri, Feb 19, 1999 at 12:18:51PM +0000: > > > %ls -l tosha > > > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha > > Surely suid bin isn't going to be very useful to tosha? > Shouldn't it be suid root or sgid operator or something? > > David. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- "The path of excess leads to the tower of wisdom." -- W. Blake http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net PGP Key fingerprint = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 9:59:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 98CD111628 for ; Fri, 19 Feb 1999 09:59:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id KAA03342; Fri, 19 Feb 1999 10:58:45 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902191758.KAA03342@panzer.plutotech.com> Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) In-Reply-To: <19990219132746.A4754@nacamar.net> from "Karsten W. Rohrbach" at "Feb 19, 1999 1:27:46 pm" To: rohrbach@nacamar.net Date: Fri, 19 Feb 1999 10:58:45 -0700 (MST) Cc: dwmalone@maths.tcd.ie, ken@plutotech.com, r3cgm@cdrom.com, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Karsten W. Rohrbach wrote... > definately, but also some of the "hook-devs" in /dev like xpt? for example > should be root.operator and mode 660 or root.wheel or whatever. if theres no > standardization in the next time, a lot of audio/multimedia packages will > grow wild with suid executables where we wont need/want them i guess - and > theres no harder pain in the ass than defect hardware and suid binaries. The xpt and pass devices are owned by root.operator, just like disk devices. They are quite intentionally chmoded 600 by default. The reason for that is that you can use the pass device at least to reformat hard disks and things like that, so it should default to being very secure, and sysadmins can selectively reduce the security if they want. For my own machines, I chmod the xpt and pass devices 660, and put myself in the operator group. So I can use camcontrol, tosha, etc., without having to su or make the binaries setuid. I can sympathize with the desire to make things easier for Joe User to use the xpt/pass devices, but I would rather not compromise security to do it. As far as I know, none of the applications that currently use the xpt/pass devices are installed setuid. So access policies are determined by how the system administrator chmods the files in /dev. > David Malone (dwmalone@maths.tcd.ie) @ Fri, Feb 19, 1999 at 12:18:51PM +0000: > > > > %ls -l tosha > > > > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha > > > > Surely suid bin isn't going to be very useful to tosha? > > Shouldn't it be suid root or sgid operator or something? > > Argh!! I didn't see that! Christopher, that's your problem. The binary was setuid bin, but /dev/xpt* and /dev/pass* are owned by root. So setuid bin won't do you any good. 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 Fri Feb 19 10: 1:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id A4B2A1195D for ; Fri, 19 Feb 1999 10:01:04 -0800 (PST) (envelope-from r3cgm@pike.cdrom.com) Received: (from r3cgm@localhost) by pike.cdrom.com (8.9.1a/8.9.1) id KAA02672 for freebsd-scsi@FreeBSD.ORG; Fri, 19 Feb 1999 10:01:54 -0800 (PST) Date: Fri, 19 Feb 1999 10:01:54 -0800 From: "Christopher G. Mann" To: freebsd-scsi@FreeBSD.ORG Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) Message-ID: <19990219100154.I7822@cdrom.com> References: <199902190152.SAA05557@panzer.plutotech.com> <9902191218.aa16968@salmon.maths.tcd.ie> <19990219132746.A4754@nacamar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990219132746.A4754@nacamar.net>; from Karsten W. Rohrbach on Fri, Feb 19, 1999 at 01:27:46PM +0100 X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : definately, but also some of the "hook-devs" in /dev like xpt? for example : should be root.operator and mode 660 or root.wheel or whatever. if theres no : standardization in the next time, a lot of audio/multimedia packages will : grow wild with suid executables where we wont need/want them i guess - and : theres no harder pain in the ass than defect hardware and suid binaries. : %ls -alF tosha -rwxr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha* %chown bin:operator tosha %chmod 2755 tosha %ls -alF tosha -rwxr-sr-x 1 bin operator 21304 Feb 18 03:07 tosha* %exit [beacon : r3cgm] ~ - fgrep operator /etc/group operator:*:5:root,r3cgm [beacon : r3cgm] /usr/local/bin - ls -l /dev/xpt* /dev/pass* crw-rw---- 1 root operator 31, 0 Feb 16 16:56 /dev/pass0 crw-rw---- 1 root operator 31, 1 Feb 16 16:56 /dev/pass1 crw-rw---- 1 root operator 31, 2 Feb 16 16:56 /dev/pass2 crw-rw---- 1 root operator 31, 3 Feb 16 16:56 /dev/pass3 crw-rw---- 1 root operator 104, 0 Feb 16 16:56 /dev/xpt0 crw-rw---- 1 root operator 104, 1 Feb 16 16:56 /dev/xpt1 [beacon : r3cgm] ~ - tosha -i Device: /dev/cd0c -- "PIONEER" "CD-ROM DR-U16S" "1.01" track playing start end raw size mp3 size # of track number time sector sector in bytes 128 kbps frames type --------------------------------------------------------------------- 1 6:03'42 0 27266 64131984 5817795 13918 audio 2 7:05'27 27267 59168 75033504 6806595 16284 audio 3 3:17'62 59169 74005 34896624 3166061 7574 audio 4 4:43'11 74006 95241 49947072 4531181 10840 audio 5 3:39'25 95242 111691 38690400 3510168 8397 audio 6 6:37'61 111692 141527 70174272 6365848 15229 audio 7 5:19'65 141528 165517 56424480 5118701 12245 audio 8 2:54'69 165518 178636 30855888 2799555 6697 audio 9 8:48'10 178637 218246 93162720 8450968 20218 audio 10 5:28'12 218247 242858 57887424 5251395 12563 audio 11 6:53'24 242859 273857 72909648 6613955 15823 audio 12 7:38'38 273858 308245 80880576 7336941 17553 audio 13 5:27'07 308246 332777 57699264 5234328 12522 audio --------------------------------------------------------------------- total 73:57'03 332778 sectors 782693856 71076231 169856 Yay! I think we're good to go now. I'll email the /port maintainer for tosha and see if I get the Makefile changed a bit. Thank you for helping me with this! -- Christopher G. Mann - IT Manager, Webmaster Walnut Creek CDROM (www.cdrom.com) The FreeBSD Mall (www.freebsdmall.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 12:43:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from moe.nycrc.net (gabriel.nycrc.net [209.73.202.6]) by hub.freebsd.org (Postfix) with SMTP id 428DB11812 for ; Fri, 19 Feb 1999 12:43:56 -0800 (PST) (envelope-from vince@nycrc.net) Received: (qmail 1155 invoked by uid 1000); 19 Feb 1999 20:44:31 -0000 Message-ID: <19990219154431.A1142@nycrc.net> Date: Fri, 19 Feb 1999 15:44:31 -0500 From: Vince Gonzalez To: freebsd-scsi@freebsd.org Subject: NCR810 and Sony CDU 926 troubles Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm having troubles with this combo and 3.0-RELEASE. The dmesg output should be pretty self-explanatory; on boot the system has difficulty with the Sony CD-R and eventually times out. This drive and controller are both known to work under other OSes (Linux,OpenBSD,Win98). Here's my dmesg output: (Note that this also happened under the generic kernel - I tried recompiling, to no avail). Can anyone direct me on how to proceed? 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-RELEASE #1: Thu Feb 18 19:41:32 EST 1999 root@moe.nycrc.net:/usr/src/sys/compile/MOE Timecounter "i8254" frequency 1193182 Hz cost 3188 ns Timecounter "TSC" frequency 300682855 Hz cost 166 ns CPU: Pentium II (quarter-micron) (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 67108864 (65536K bytes) avail memory = 62877696 (61404K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 int d irq 255 on pci0.7.2 chip4: rev 0x02 on pci0.7.3 fxp0: rev 0x05 int a irq 12 on pci0.11.0 fxp0: Ethernet address 00:a0:c9:e8:1d:51 ncr0: rev 0x02 int a irq 10 on pci0.13.0 Probing for devices on PCI bus 1: vga0: rev 0x21 int a irq 11 on pci1.0.0 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 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 psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 4884MB (10003392 sectors), 9924 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordy wcd0: 2067Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 on motherboard npx0: INT 16 interface Waiting 2 seconds for SCSI devices to settle ncr0: SCSI phase error fixup: CCB already dequeued (0xf0862a00) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860a00 (skip) ncr0: timeout nccb=0xf0860a00 (skip) ncr0: timeout nccb=0xf0860a00 (skip) ncr0: timeout nccb=0xf0860a00 (skip) ncr0: timeout nccb=0xf0860a00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) changing root device to wd1s1a ncr0: timeout nccb=0xf0865600 (skip) ncr0: timeout nccb=0xf0865600 (skip) (cd0:ncr0:0:6:0): got CAM status 0x4b (cd0:ncr0:0:6:0): fatal error, failed to attach to device(cd0:ncr0:0:6:0): removing device entry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 13: 3:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 2252C11894 for ; Fri, 19 Feb 1999 13:03:14 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id OAA03963; Fri, 19 Feb 1999 14:03:05 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902192103.OAA03963@panzer.plutotech.com> Subject: Re: NCR810 and Sony CDU 926 troubles In-Reply-To: <19990219154431.A1142@nycrc.net> from Vince Gonzalez at "Feb 19, 1999 3:44:31 pm" To: vince@nycrc.net (Vince Gonzalez) Date: Fri, 19 Feb 1999 14:03:05 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Vince Gonzalez wrote... > Hi, > > I'm having troubles with this combo and 3.0-RELEASE. The dmesg output should be > pretty self-explanatory; on boot the system has difficulty with the Sony CD-R > and eventually times out. This drive and controller are both known to work > under other OSes (Linux,OpenBSD,Win98). Here's my dmesg output: (Note that this > also happened under the generic kernel - I tried recompiling, to no avail). > Can anyone direct me on how to proceed? Can you try booting a 3.1-RELEASE floppy and see if that works? There are some problems with Sony CD drives that have been fixed since 3.0 came out. (mainly to do with multi-lun probing, I think) 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 Fri Feb 19 13:19: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from moe.nycrc.net (gabriel.nycrc.net [209.73.202.6]) by hub.freebsd.org (Postfix) with SMTP id 124C411735 for ; Fri, 19 Feb 1999 13:18:51 -0800 (PST) (envelope-from vince@nycrc.net) Received: (qmail 1595 invoked by uid 1000); 19 Feb 1999 21:19:25 -0000 Message-ID: <19990219161925.A1498@nycrc.net> Date: Fri, 19 Feb 1999 16:19:25 -0500 From: Vince Gonzalez To: "Kenneth D. Merry" Cc: freebsd-scsi@freebsd.org Subject: Re: NCR810 and Sony CDU 926 troubles References: <19990219154431.A1142@nycrc.net> <199902192103.OAA03963@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902192103.OAA03963@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Feb 19, 1999 at 02:03:05PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 19, 1999 at 02:03:05PM -0700, Kenneth D. Merry wrote: > Vince Gonzalez wrote... > > > Can anyone direct me on how to proceed? > > Can you try booting a 3.1-RELEASE floppy and see if that works? There are > some problems with Sony CD drives that have been fixed since 3.0 came out. > (mainly to do with multi-lun probing, I think) Thanks, I'll give it a shot, and post the results. --vince To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 13:30:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id D3CA31187E for ; Fri, 19 Feb 1999 13:30:41 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id OAA04122; Fri, 19 Feb 1999 14:30:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902192130.OAA04122@panzer.plutotech.com> Subject: Re: slow disk performance In-Reply-To: <19990218215721.55546@right.PCS> from Jonathan Lemon at "Feb 18, 1999 9:57:21 pm" To: jlemon@americantv.com (Jonathan Lemon) Date: Fri, 19 Feb 1999 14:30:32 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Jonathan Lemon wrote... > I have a system with the following: > > ahc0: rev 0x01 int a irq 11 on pci0.6.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > > > Basically, an ASUS motherboard with an onboard Adaptec, along with > two 7200 rpm disks. However, I can't seem to get more than 6MB/sec > out of the drives, when doing sequential reads or writes: > > dd if=/dev/rda1 of=/dev/null bs=64k & > dd if=/dev/rda0 of=/dev/null bs=64k & > iostat 1 > > tty fd0 da0 da1 cpu > tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id > 0 77 0.00 0 0.00 64.00 115 7.17 64.00 103 6.42 0 0 1 1 98 > 0 76 0.00 0 0.00 64.00 102 6.37 64.00 100 6.25 0 0 1 1 98 > 0 76 0.00 0 0.00 64.00 118 7.36 64.00 103 6.44 0 0 5 0 95 > > > Is this the maximum I can expect to get from the drives? I get the same > speeds when doing sequential writes as well; I would think it can do > etter than this. There are no "tagged opening" messages in the logfile, > so this is with 64 tags. As Steinar Haug pointed out, that may be about all you're going to get from those disks (he got similar results from his IBM DCAS). The Atlas I was a decent performer in its day, and I don't think the numbers you're getting from it are really out of line. I used to have a 4G Atlas I around, but it died a year and a half ago. (Quantum was kind enough to replace it with a 9G Atlas II.) But, I do have a number of Atlas II's kicking around. Running your dd test, I get roughly 9-9.5MB/sec from my two Atlas II's: fd0 da0 da1 cd0 KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s 0.00 0 0.00 63.18 150 9.27 64.00 149 9.33 0.00 0 0.00 0.00 0 0.00 63.57 147 9.11 64.00 149 9.29 0.00 0 0.00 0.00 0 0.00 64.00 150 9.35 64.00 148 9.22 0.00 0 0.00 0.00 0 0.00 64.00 149 9.34 64.00 149 9.34 0.00 0 0.00 0.00 0 0.00 64.00 150 9.41 64.00 149 9.28 0.00 0 0.00 0.00 0 0.00 64.00 149 9.28 64.00 149 9.28 0.00 0 0.00 0.00 0 0.00 64.00 149 9.34 64.00 149 9.28 0.00 0 0.00 0.00 0 0.00 64.00 150 9.41 64.00 149 9.28 0.00 0 0.00 0.00 0 0.00 63.58 149 9.27 64.00 146 9.14 0.00 0 0.00 0.00 0 0.00 58.77 131 7.51 64.00 149 9.30 0.00 0 0.00 I get similar results from an Atlas II on another machine that is by itself on a 7880. I would expect the Atlas I to be somewhat slower for any number of reasons. (Lower media density being a major culprit.) 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 Fri Feb 19 14:14:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from moe.nycrc.net (gabriel.nycrc.net [209.73.202.6]) by hub.freebsd.org (Postfix) with SMTP id 7B719119E8 for ; Fri, 19 Feb 1999 14:14:31 -0800 (PST) (envelope-from vince@nycrc.net) Received: (qmail 282 invoked by uid 1000); 19 Feb 1999 22:15:02 -0000 Message-ID: <19990219171502.A277@nycrc.net> Date: Fri, 19 Feb 1999 17:15:02 -0500 From: Vince Gonzalez To: freebsd-scsi@freebsd.org Subject: Re: NCR810 and Sony CDU 926 troubles References: <19990219154431.A1142@nycrc.net> <199902192103.OAA03963@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902192103.OAA03963@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Feb 19, 1999 at 02:03:05PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 19, 1999 at 02:03:05PM -0700, Kenneth D. Merry wrote: > Can you try booting a 3.1-RELEASE floppy and see if that works? There are > some problems with Sony CD drives that have been fixed since 3.0 came out. > (mainly to do with multi-lun probing, I think) OK, I tried the 3.1 boot floppy, and still no go. The messages were pretty much the same as in my previous post, with the timeouts and whatever. Any more suggestions? --vince To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 14:39:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 56311117EE for ; Fri, 19 Feb 1999 14:39:07 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id OAA29113; Fri, 19 Feb 1999 14:38:52 -0800 Date: Fri, 19 Feb 1999 14:38:52 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Simple 2944 not handled? In-Reply-To: <199902171852.LAA03331@narnia.plutotech.com> 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 Sorry- it turns out that none of the below makes a difference. On Wed, 17 Feb 1999, Justin T. Gibbs wrote: > In article you wrote: > > > > I'm having a heckuva a time with the the Adaptec driver- this is with > > kernels from 3.0 to today. > > > > The hardware is a SuperMicro P6DLH- or some such- single 300Mhz Pentium 2, > > two PCI busses, etc...I've had 1 through 4 Adaptec 2944 cards > > (differential 2940AU variants) installed in this box. > > My guess is that we've somehow messed up the external transceiver setup. > Unfortunately I've never had access to either a 2944 or an HVD peripheral, > so I've never tested the driver myself in this kind of configuration. I > do have some ideas of things you can try: > > 1) Try clearing ACTNEGEN in the SXFRCTL1. You can do this in > sys/dev/aic7xxx/aic7xxx.c:ahc_init(). The data book is unclear > on what effect this feature has in a differential setting > and it could be confusing the external HVD transceivers. > > 2) In ahc_pci.c, take a peek at the DEVCONFIG pci configuration space > register. My guess would be that bit 0 is set (DIFACTNEGEN). If it's > not set, try setting it. If it is set, try clearing it. > > Other than those two bits, I can't find any other bits that are specific > to differential configurations. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 14:48:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id B9A9111B57 for ; Fri, 19 Feb 1999 14:47:32 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id PAA16303; Fri, 19 Feb 1999 15:47:30 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199902192247.PAA16303@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Simple 2944 not handled? In-reply-to: Your message of "Fri, 19 Feb 1999 14:38:52 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Feb 1999 15:38:47 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Sorry- it turns out that none of the below makes a difference. > Is ahc_intr ever called for the errant cards. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 14:51:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4078E119E0 for ; Fri, 19 Feb 1999 14:51:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id OAA29171; Fri, 19 Feb 1999 14:50:54 -0800 Date: Fri, 19 Feb 1999 14:50:54 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Simple 2944 not handled? In-Reply-To: <199902192247.PAA16303@pluto.plutotech.com> 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 Good question- I'll check that. On Fri, 19 Feb 1999, Justin T. Gibbs wrote: > > > >Sorry- it turns out that none of the below makes a difference. > > > > Is ahc_intr ever called for the errant cards. > > -- > Justin > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 15:13:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 88AAE11412 for ; Fri, 19 Feb 1999 15:13:40 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id QAA05091; Fri, 19 Feb 1999 16:13:36 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902192313.QAA05091@panzer.plutotech.com> Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) In-Reply-To: <19990219100154.I7822@cdrom.com> from "Christopher G. Mann" at "Feb 19, 1999 10: 1:54 am" To: r3cgm@cdrom.com (Christopher G. Mann) Date: Fri, 19 Feb 1999 16:13:36 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Christopher G. Mann wrote... > : definately, but also some of the "hook-devs" in /dev like xpt? for example > : should be root.operator and mode 660 or root.wheel or whatever. if theres no > : standardization in the next time, a lot of audio/multimedia packages will > : grow wild with suid executables where we wont need/want them i guess - and > : theres no harder pain in the ass than defect hardware and suid binaries. > : > %ls -alF tosha > -rwxr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha* > > %chown bin:operator tosha > %chmod 2755 tosha > > %ls -alF tosha > -rwxr-sr-x 1 bin operator 21304 Feb 18 03:07 tosha* > %exit > > [beacon : r3cgm] ~ - fgrep operator /etc/group > operator:*:5:root,r3cgm Having tosha setgid is not necessary, since you're already in the operator group. In fact, it could represent a security risk if tosha is somehow exploitable. > [beacon : r3cgm] /usr/local/bin - ls -l /dev/xpt* /dev/pass* > crw-rw---- 1 root operator 31, 0 Feb 16 16:56 /dev/pass0 > crw-rw---- 1 root operator 31, 1 Feb 16 16:56 /dev/pass1 > crw-rw---- 1 root operator 31, 2 Feb 16 16:56 /dev/pass2 > crw-rw---- 1 root operator 31, 3 Feb 16 16:56 /dev/pass3 > crw-rw---- 1 root operator 104, 0 Feb 16 16:56 /dev/xpt0 > crw-rw---- 1 root operator 104, 1 Feb 16 16:56 /dev/xpt1 > > [beacon : r3cgm] ~ - tosha -i > Device: /dev/cd0c -- "PIONEER" "CD-ROM DR-U16S" "1.01" [ ... ] > Yay! I think we're good to go now. I'll email the /port maintainer > for tosha and see if I get the Makefile changed a bit. I would recommend against changing things. The tosha port works as-is, without modification. The default security policy should be: - binaries are not setuid or setgid - devices are chmoded 600 System administrators can then use group permissions on device nodes to control access to certain SCSI devices, or all SCSI devices. 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 Fri Feb 19 16:35:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B4DAA10E54 for ; Fri, 19 Feb 1999 16:35:41 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA29438; Fri, 19 Feb 1999 16:35:26 -0800 Date: Fri, 19 Feb 1999 16:35:26 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Simple 2944 not handled? In-Reply-To: <199902192247.PAA16303@pluto.plutotech.com> 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 > > > >Sorry- it turns out that none of the below makes a difference. > > > > Is ahc_intr ever called for the errant cards. > yes. 99.9999% with an intstat of zero- one with SCSIINT set. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 19 17:45: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 4DE8F11544 for ; Fri, 19 Feb 1999 17:45:02 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id CAA10261 for freebsd-scsi@FreeBSD.ORG; Sat, 20 Feb 1999 02:45:01 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id AE7311516; Fri, 19 Feb 1999 20:15:46 +0100 (CET) Date: Fri, 19 Feb 1999 20:15:46 +0100 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: slow disk performance Message-ID: <19990219201546.A18865@keltia.freenix.fr> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <19990218215721.55546@right.PCS> <18942.919418741@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <18942.919418741@verdi.nethelp.no>; from sthaug@nethelp.no on Fri, Feb 19, 1999 at 11:05:41AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#5026 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to sthaug@nethelp.no: > I get around 7.5 MB/s reading from the raw device on my DCAS-34330W, using > an NCR875 based controller (Tekram). Somewhat less when writing. I'm surprised. When I got my first DCAS-34330W, also on a NCR-875 card, I got a bit more than 8 MB/s... I get 13 MB/s on the Viking II/AHA-7880UW on my second machine. DCAS-34330W (5400 rpm): 262144000 bytes transferred in 32.113711 secs (8162993 bytes/sec) Viking II (7200 rpm): 262144000 bytes transferred in 19.191250 secs (13659558 bytes/sec) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 20 0:26:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 7BEB0115F2 for ; Sat, 20 Feb 1999 00:26:37 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 11248 invoked by uid 1001); 20 Feb 1999 08:26:35 +0000 (GMT) To: roberto@keltia.freenix.fr Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: slow disk performance From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 19 Feb 1999 20:15:46 +0100" References: <19990219201546.A18865@keltia.freenix.fr> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 20 Feb 1999 09:26:35 +0100 Message-ID: <11246.919499195@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > According to sthaug@nethelp.no: > > I get around 7.5 MB/s reading from the raw device on my DCAS-34330W, using > > an NCR875 based controller (Tekram). Somewhat less when writing. > > I'm surprised. When I got my first DCAS-34330W, also on a NCR-875 card, I > got a bit more than 8 MB/s... I get 13 MB/s on the Viking II/AHA-7880UW on > my second machine. > > DCAS-34330W (5400 rpm): > 262144000 bytes transferred in 32.113711 secs (8162993 bytes/sec) Our times are definitely comparable. I was using M=1048576, and being a bit conservative :-) Here are two runs from today: 268435456 bytes transferred in 32.948539 secs (8147113 bytes/sec) 268435456 bytes transferred in 33.194596 secs (8086722 bytes/sec) Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 20 1:59:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (Postfix) with ESMTP id 6296C11793 for ; Sat, 20 Feb 1999 01:59:21 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.2/8.9.1) id BAA66962 for scsi@FreeBSD.org; Sat, 20 Feb 1999 01:59:37 -0800 (PST) (envelope-from ulf) Message-ID: <19990220015937.A6413@TelcoSucks.org> Date: Sat, 20 Feb 1999 01:59:37 -0800 From: Ulf Zimmermann To: scsi@FreeBSD.org Subject: Amanda and ARCHIVE Python 28849-XXX ? Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.1-19990218-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any here with an Archive Python 28849-XXX ? And is using it with Amanda under FreeBSD 3.x or above ? If so, would it be possible to get a copy of your config files ? -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 20 5:47:31 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 812DF10E6B for ; Sat, 20 Feb 1999 05:47:30 -0800 (PST) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id BEA2325B; Sat, 20 Feb 1999 08:47:29 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with SMTP id ADD25258 for ; Sat, 20 Feb 1999 08:47:29 -0500 (EST) Date: Sat, 20 Feb 1999 08:47:29 -0500 (EST) From: David Miller To: freebsd-scsi@freebsd.org Subject: IOCTL question 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'm struggling to bring up a scsi based mpeg2 decoder on 2.2.7. Right now I'm trying to kick start it with the "scsi" command. In order to write to it I'm using: alex# dd if=test.mpg bs=64k count=1 | ./scsi -f /dev/uk0 -c "2A 0 0 0 80 0" -o 65536 "-" 1+0 records in 1+0 records out 65536 bytes transferred in 0.008196 secs (7996099 bytes/sec) SCIOCCOMMAND ioctl: Input/output error Since I certainly can talk to the board (identification inquiry, color bars, soft reset) this is not a general communications problem. Is this a case of ioctl not wanting to issue this command to uk0? If so, how do I tweak uk() so as to write to it? If not, what is it telling me? Thanks, --- David Miller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 20 8: 8: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A84211371 for ; Sat, 20 Feb 1999 08:07:55 -0800 (PST) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id <1PTHLF78>; Sat, 20 Feb 1999 11:06:58 -0500 Message-ID: From: tcobb@staff.circle.net To: ulf@Alameda.net, scsi@FreeBSD.org Subject: RE: Amanda and ARCHIVE Python 28849-XXX ? Date: Sat, 20 Feb 1999 11:06:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Which configs do you need? I have it working with a customized tape-changer script. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Ulf Zimmermann [mailto:ulf@Alameda.net] > Sent: Saturday, February 20, 1999 5:00 AM > To: scsi@FreeBSD.org > Subject: Amanda and ARCHIVE Python 28849-XXX ? > > > Any here with an Archive Python 28849-XXX ? And is using it > with Amanda > under FreeBSD 3.x or above ? If so, would it be possible to > get a copy of > your config files ? > > -- > Regards, Ulf. > > ------------------------------------------------------------ > --------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: > 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: > 510-521-5073 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 20 10:42:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 79A2C111CF for ; Sat, 20 Feb 1999 10:42:21 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id LAA13528; Sat, 20 Feb 1999 11:42:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902201842.LAA13528@panzer.plutotech.com> Subject: Re: IOCTL question In-Reply-To: from David Miller at "Feb 20, 1999 8:47:29 am" To: dmiller@search.sparks.net (David Miller) Date: Sat, 20 Feb 1999 11:42:07 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 David Miller wrote... > Hello all:) > > I'm struggling to bring up a scsi based mpeg2 decoder on 2.2.7. Right now > I'm trying to kick start it with the "scsi" command. In order to write to > it I'm using: > > alex# dd if=test.mpg bs=64k count=1 | ./scsi -f /dev/uk0 -c "2A 0 0 0 80 > 0" -o 65536 "-" > 1+0 records in > 1+0 records out > 65536 bytes transferred in 0.008196 secs (7996099 bytes/sec) > SCIOCCOMMAND ioctl: Input/output error > > > Since I certainly can talk to the board (identification inquiry, color > bars, soft reset) this is not a general communications problem. > > Is this a case of ioctl not wanting to issue this command to uk0? If so, > how do I tweak uk() so as to write to it? If not, what is it telling me? There are several things wrong with the above command. - the CDB length is wrong - you either have not specified the length of the command, or if the '80' above is part of the length, it doesn't match up with the length you gave to the scsi command on the command line. Try something like: ./scsi -f /dev/uk0 -c "2A 0 0 0 0 0 0 ff ff 0" -o 65535 "-" That will hopefully write 65535 bytes at address 0. What kind of device is this, any way? I mean, what device type does it probe as? 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 Sat Feb 20 13:18:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 17DEE119B2 for ; Sat, 20 Feb 1999 13:18:22 -0800 (PST) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id B844725B; Sat, 20 Feb 1999 16:18:15 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with SMTP id A673824F; Sat, 20 Feb 1999 16:18:15 -0500 (EST) Date: Sat, 20 Feb 1999 16:18:15 -0500 (EST) From: David Miller To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL question In-Reply-To: <199902201842.LAA13528@panzer.plutotech.com> 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 On Sat, 20 Feb 1999, Kenneth D. Merry wrote: > David Miller wrote... > > Hello all:) > > > > I'm struggling to bring up a scsi based mpeg2 decoder on 2.2.7. Right now > > I'm trying to kick start it with the "scsi" command. In order to write to > > it I'm using: > > > > alex# dd if=test.mpg bs=64k count=1 | ./scsi -f /dev/uk0 -c "2A 0 0 0 80 > > 0" -o 65536 "-" > > 1+0 records in > > 1+0 records out > > 65536 bytes transferred in 0.008196 secs (7996099 bytes/sec) > > SCIOCCOMMAND ioctl: Input/output error > > > > > > Since I certainly can talk to the board (identification inquiry, color > > bars, soft reset) this is not a general communications problem. > > > > Is this a case of ioctl not wanting to issue this command to uk0? If so, > > how do I tweak uk() so as to write to it? If not, what is it telling me? > > There are several things wrong with the above command. > > - the CDB length is wrong Bingo! I saw that while reading the doc's for the tenth time this morning:) I mistakenly changed the 0a to 2a without adding the other fields in the CDB:( > - you either have not specified the length of the command, or if the '80' > above is part of the length, it doesn't match up with the length you gave > to the scsi command on the command line. The 80 is correct in this case. Length is specified for this device as the number of 512 byte blocks. Not that there was any way for you to know an idiosynchrasy (sp) like this:) > Try something like: > > ./scsi -f /dev/uk0 -c "2A 0 0 0 0 0 0 ff ff 0" -o 65535 "-" > > That will hopefully write 65535 bytes at address 0. > > What kind of device is this, any way? I mean, what device type does it > probe as? It's a Vela Research scsi-2 mpeg-2 decoder, and probes as device type 12. Any words of wisdom on how to create a device type vl (as opposed to st, uk, pt, etc:) ? I'd like to clean things up a little. OTOH, I should probably do this under 3.1Stable, and the scsi system is all changed. Is it easier/harder under CAM? Thanks Ken! --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 20 14:52:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id C9A1F119C0 for ; Sat, 20 Feb 1999 14:52:51 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id PAA14683; Sat, 20 Feb 1999 15:52:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902202252.PAA14683@panzer.plutotech.com> Subject: Re: IOCTL question In-Reply-To: from David Miller at "Feb 20, 1999 4:18:15 pm" To: dmiller@search.sparks.net (David Miller) Date: Sat, 20 Feb 1999 15:52:48 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 David Miller wrote... > On Sat, 20 Feb 1999, Kenneth D. Merry wrote: > > > David Miller wrote... > > > Hello all:) > > > > > > I'm struggling to bring up a scsi based mpeg2 decoder on 2.2.7. Right now > > > I'm trying to kick start it with the "scsi" command. In order to write to > > > it I'm using: > > > > > > alex# dd if=test.mpg bs=64k count=1 | ./scsi -f /dev/uk0 -c "2A 0 0 0 80 > > > 0" -o 65536 "-" > > > 1+0 records in > > > 1+0 records out > > > 65536 bytes transferred in 0.008196 secs (7996099 bytes/sec) > > > SCIOCCOMMAND ioctl: Input/output error > > > > > > > > > Since I certainly can talk to the board (identification inquiry, color > > > bars, soft reset) this is not a general communications problem. > > > > > > Is this a case of ioctl not wanting to issue this command to uk0? If so, > > > how do I tweak uk() so as to write to it? If not, what is it telling me? > > > > There are several things wrong with the above command. > > > > - the CDB length is wrong > > Bingo! I saw that while reading the doc's for the tenth time this > morning:) I mistakenly changed the 0a to 2a without adding the other > fields in the CDB:( Oops. > > - you either have not specified the length of the command, or if the '80' > > above is part of the length, it doesn't match up with the length you gave > > to the scsi command on the command line. > > The 80 is correct in this case. Length is specified for this device as the > number of 512 byte blocks. Not that there was any way for you to know an > idiosynchrasy (sp) like this:) Yeah, I wouldn't have guessed. :) > > Try something like: > > > > ./scsi -f /dev/uk0 -c "2A 0 0 0 0 0 0 ff ff 0" -o 65535 "-" > > > > That will hopefully write 65535 bytes at address 0. > > > > What kind of device is this, any way? I mean, what device type does it > > probe as? > > It's a Vela Research scsi-2 mpeg-2 decoder, and probes as device type 12. 12?? That's the code for a storage array! I would expect it perhaps to be 10 or 11 or something, but probably not 12. Unless you mean 0x12, and then that's a 'reserved' device type, according to the SCSI 2 and SCSI 3 specs. > Any words of wisdom on how to create a device type vl (as opposed to st, > uk, pt, etc:) ? I'd like to clean things up a little. > > OTOH, I should probably do this under 3.1Stable, and the scsi system is > all changed. Is it easier/harder under CAM? I would suggest doing it under CAM. I'll at least be able to give you some advice/help if you use CAM. I don't know nearly as much about the old SCSI layer, though, so you'd be dependent on other folks to help out. It should be pretty easy to do a peripheral driver for it under CAM. You'll probably want to give it a read-write interface. That would probably make things go a lot easier. My guess is that that thing has a fairly non-standard interface. So in the probe routine for the peripheral driver you'll want to make sure that it only attaches to that particular device. (You'd look at the device type number, as well as the inquiry data.) If you don't want to write a driver for it, you can do the same tricks with camcontrol(8) that you're doing with scsi(8) now. Or you can write a userland application that uses the pass(4) driver to talk to the device. Depending on the interface, though, I think it would be easier to just write a driver, so you can read and write to the thing. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message