From owner-freebsd-scsi Sun Jan 11 01:23:47 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05378 for freebsd-scsi-outgoing; Sun, 11 Jan 1998 01:23:47 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA05359 for ; Sun, 11 Jan 1998 01:23:42 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id CAA14533; Sun, 11 Jan 1998 02:21:12 -0700 (MST) Date: Sun, 11 Jan 1998 02:21:12 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801110921.CAA14533@narnia.plutotech.com> To: Ollivier Robert cc: scsi@FreeBSD.org Subject: Re: ncr CAM code Newsgroups: pluto.freebsd.scsi In-Reply-To: <19980110150728.28270@keltia.freenix.fr> <199801102121.OAA13426@narnia.plutotech.com> <19980111013507.02400@keltia.freenix.fr> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Another point, my HP 35480A DAT is not recogized at boot time. It generates > an error at the beginning and the driver doesn't initialize it. I'll be the first to point out that I know very little about how the NCR driver works. The main point of my porting it to CAM was to get the driver far enough along to where Stefan can polish it up. I don't know how any of my changes could make it so the second NCR card is no longer probed (I didn't touch the probe code). > ncr0: restart (scsi reset). > ncr1: restart (scsi reset). > ncr1: SCSI phase error fixup: CCB address mismatch (0xf07e1400 != 0x00000000) np > ->nccb = 0xf07e5400 > (probe1:ncr1:0:2:0): phase change 6-7 5@004eb5d8 resid=1. \ Conner > (probe1:ncr1:0:2:0): MSG_MESSAGE_REJECT received (2:8). / CFP-1080S > (probe1:ncr1:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 \ > (probe1:ncr1:0:5:0): ILLEGAL REQUEST asc:49,0 | HP 35480A DAT > (probe1:ncr1:0:5:0): Invalid message error / > (probe1:ncr1:0:6:0): MSG_MESSAGE_REJECT received (6:8). - Sony CDU-415 It seems that I broke outgoing messages for the 810. It could very well be that I broke some alignment constraint for one of the data structures that only affects the 810. The interaction between the script and objects in kernel memory is not explicitly documented with the data structures so this wouldn't surprise me at all. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Thu Jan 8 00:49:00 CET 1998 -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations =========================================== From owner-freebsd-scsi Sun Jan 11 03:14:42 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA13057 for freebsd-scsi-outgoing; Sun, 11 Jan 1998 03:14:42 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id DAA13039; Sun, 11 Jan 1998 03:14:38 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by iafnl.es.iaf.nl with UUCP id AA28035 (5.67b/IDA-1.5); Sun, 11 Jan 1998 12:08:39 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id TAA15580; Sat, 10 Jan 1998 19:30:34 +0100 (MET) From: Wilko Bulte Message-Id: <199801101830.TAA15580@yedi.iaf.nl> Subject: Re: SCSI/Tape problem? To: grog@lemis.com (Greg Lehey) Date: Sat, 10 Jan 1998 19:30:34 +0100 (MET) Cc: steve@news.cioe.com, freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <19980110184222.53552@lemis.com> from "Greg Lehey" at Jan 10, 98 06:42:22 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote... > On Fri, Jan 09, 1998 at 11:32:47PM -0500, Steven Ames wrote: > >>> Hrm... I was unclear. The 'mt erase' is obviously only a > >>> symptom. The backup process still causes my machine to lockup... > >> > >> OK, that is obviously wrong. My 2.2.5R box performs dumps just fine on the > >> 8200, as said without doing an mt erase. I do not use Amanda though > > > > Correct. I do not _have_ to do the 'mt erase'. In fact I never do. > > However... 'mt erase' does not work... and my backup locks up. These > > are seperate but related issues. Bottom line is _it don't work_. > > > > I have tried just about every termination I can think to try. Different > > cables, different controller (still a 2940) and a different > > tape drive. It still doesn't work. So something is wrong. Options > > anyone? > > What else do you have connected to the string? If there's something > else, and you obviously have access to a second controller, try using > both controllers, with only the tape connected to the one controller. This is a good one. > If that doesn't work, consider your drive options. This was an > Exabyte 8505, wasn't it? Exabytes used to have millions of drive More exactly: millions of firmware revisions. The one I have in my 8200 was advised to me by an Exabyte engineer. He advised against using the latest rev ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- From owner-freebsd-scsi Sun Jan 11 03:15:26 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA13254 for freebsd-scsi-outgoing; Sun, 11 Jan 1998 03:15:26 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA13232 for ; Sun, 11 Jan 1998 03:15:22 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id MAA15343; Sun, 11 Jan 1998 12:15:19 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id MAA27778; Sun, 11 Jan 1998 12:12:12 +0100 (MET) Message-ID: <19980111121211.42324@uriah.heep.sax.de> Date: Sun, 11 Jan 1998 12:12:11 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Carl.Makin@aipo.gov.au Subject: Re: seagate.c kernel compile error and sea device problems. Reply-To: Joerg Wunsch References: <4A256589.001DDBEF.00@notes.aipo.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <4A256589.001DDBEF.00@notes.aipo.gov.au>; from Carl.Makin@aipo.gov.au on Sun, Jan 11, 1998 at 03:23:13PM +1000 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Carl.Makin@aipo.gov.au wrote: > Under FreeBSD 2.2.5-RELEASE, > > I get the following error from seagate.c when I compile a kernel. They are not errors, but warnings. You wouldn't have got a kernel at all otherwise. ;) > ../../i386/isa/seagate.c ../../i386/isa/seagate.c:581: warning: no previous > prototype for `seaintr' ../../i386/isa/seagate.c: In function (Your mailer clobbers long lines.) That's sloppyness, but unless the functions are being used differently than defined, it's totally benign. > `sea_data_output': ../../i386/isa/seagate.c:1111: warning: assignment > discards `volatile' from pointer target type ../../i386/isa/seagate.c: In > function `sea_data_input': ../../i386/isa/seagate.c:1181: warning: > assignment discards `volatile' from pointer target type sh The argument p_data should probably be spelled with `volatile' consistently throughout the driver. gcc is not likely to optimize accesses away on an x86 CPU outside of functions, however. ;-) > I uncommented the "BLINDTRANSFERS" option and tried again with the > autodetect sea0 config line and the errors started again. There's probably nobody around anymore understanding the code better than you do these days. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Jan 14 14:19:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04331 for freebsd-scsi-outgoing; Wed, 14 Jan 1998 14:19:01 -0800 (PST) (envelope-from owner-freebsd-freebsd-scsi@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04100; Wed, 14 Jan 1998 14:17:30 -0800 (PST) (envelope-from seb@erix.ericsson.se) Received: from super.du.etx.ericsson.se (root@super.du.etx.ericsson.se [150.236.14.16]) by penguin.wise.edt.ericsson.se (8.7.5/8.7.3/glacier-1.12) with ESMTP id XAA03310; Wed, 14 Jan 1998 23:17:25 +0100 (MET) Received: from scotch.du.etx.ericsson.se (seb@scotch.du.etx.ericsson.se [150.236.14.76]) by super.du.etx.ericsson.se (8.8.8/8.8.8/erix-1.1) with ESMTP id XAA15083; Wed, 14 Jan 1998 23:17:24 +0100 (MET) Received: by scotch.du.etx.ericsson.se (8.8.5/client-1.4) id XAA07158; Wed, 14 Jan 1998 23:17:23 +0100 (CET) Date: Wed, 14 Jan 1998 23:17:23 +0100 (CET) Message-Id: <199801142217.XAA07158@scotch.du.etx.ericsson.se> From: Sebastian Strollo To: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: running 2.2.5-RELEASE on a ASUS P2L97-S Sender: owner-freebsd-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi everyone! I am having trouble with a newly purchased machine that I have put together. Below is the specs. At first the system would completely lock up (i.e. only respond to the Mighty Big Reset Button) when putting load on the SCSI disk. By load I mean e.g. trying to install the system on it or running "bonnie" on it. So I have been trying some different combinations: * removing the CDROM - no difference, still locks up. * removing all SCSI devices - no lockups, but I want to use SCSI :-( * disabling the L2 cache - no difference, still locks up. * disabling Ultra in the SCSI bios - no difference, still locks up. * putting a 100MB SCSI disk on the 50pin bus, and writing to files on that one - this locks up the machine as well. * Installed WinCrap95 on a partition on the SCSI disk, it worked but after a while the whole machine started to act flaky, crashing left and right. * back to FreeBSD, and now the machine is starting to fall all over the place. "Fatal trap 12: page fault while in kernel mode" and "Double Fault" (what is this?). Please help me with suggestions on what might be wrong, or new things to try out. Eagerly awaiting your input, -- Sebastian ---------------------------------------------------------------------- FreeBSD version: 2.2.5-RELEASE Hardware: Motherboard/CPU: ASUS P2L97-S (has a 440LX, PIIX4 and AIC7880 onboard) with an Intel Pentium II 233MHz 1 (one) 64MB SDRAM 100MHz module IDE disk: IBM Deskstar 8.4GB, IBM-DHEA-38451 SCSI disk: 4,5GB U2W FUJITSU MAB3045SP 0105 SCSI CDROM: NEC CD-ROM DRIVE:464 1.04 Ethernet card: 3COM 3C905 Fast Etherlink XL PCI graphics board: ATI Video Boost (2MB, Mach64) I have terminated the SCSI bus accordingly (T meaning termination): +---+ +----+ T=| A |=========|FUJ.|=T========|- +-------+ | I | | HD | |- (external connector) T=| CDROM |=========| C |=========| |=T========|- +-------+ +---+ +----+ Info on the system: (One thing which I don't understand is why the ethernet card, the adaptec chip (and the USB chip) gets the same irq 11? This is done by the BIOS(?) - I tried to wire the PCI slot which the ethernet card sits in to a different irq, which just lead to that all three devices that were previously mapped to irq 11 now got mapped to the new irq) # dmesg Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.5-RELEASE #2: Wed Jan 14 21:13:02 GMT 1998 root@fatburen.du.etx.ericsson.se:/usr/src/sys/compile/FATBUREN Calibrating clock(s) ... i586 clock: 233866561 Hz, i8254 clock: 1193196 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method CPU: Pentium Pro (233.86-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00241000 - 0x03ffdfff, 64737280 bytes (15805 pages) avail memory = 62484480 (61020K bytes) pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x8000005c pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=71808086) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. chip0 rev 3 on pci0:0 mapreg[10] type=0 addr=e4000000 size=4000000. chip1 rev 3 on pci0:1 bridge from pci0 to pci1 through 1. mapping regs: io:22a0d0e0 mem:e3e0e3f0 pmem:e3f0e400 chip2 rev 1 on pci0:4:0 pci0:4:1: Intel Corporation, device=0x7111, class=storage (ide) [no driver assigned] map(20): io(d800) pci0:4:2: Intel Corporation, device=0x7112, class=0x0c, subclass=0x03 int d irq 11 [no driver assigned] map(20): io(d400) chip3 rev 1 on pci0:4:3 ahc0 rev 0 int a irq 11 on pci0:6 mapreg[10] type=1 addr=0000d000 size=0100. mapreg[14] type=0 addr=e3000000 size=1000. reg16: ioaddr=0xd000 size=0x100 ahc0: Reading SEEPROM...done. low byte termination disabled, high byte termination enabled ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: Resetting Channel A ahc0: Downloading Sequencer Program...ahc0: 366 instructions downloaded Done ahc0: Probing channel A ahc0 waiting for scsi devices to settle ahc0: target 0 using 16Bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 (ahc0:0:0): "FUJITSU MAB3045SP 0105" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4343MB (8895370 512 byte sectors) sd0(ahc0:0:0): with 8491 cyls, 5 heads, and an average 209 sectors/track ahc0: target 4 synchronous at 10.0MHz, offset = 0xf (ahc0:4:0): "NEC CD-ROM DRIVE:464 1.04" type 5 removable SCSI 2 cd0(ahc0:4:0): CD-ROM can't get the size probe0(ahc0:9:0): scsi_cmd probe0(ahc0:9:0): scsi_done (ahc0:9:0): command: 0,0,0,0,0,0-[0 bytes] probe0(ahc0:9:0): scsi_cmd probe0(ahc0:9:0): scsi_done (ahc0:9:0): command: 12,0,0,0,2c,0-[44 bytes] ------------------------------ 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 032: 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------ vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 11 on pci0:9 mapreg[10] type=1 addr=0000b800 size=0040. mii[*mii*]: disable 'auto select' with DOS util! address 00:60:08:68:c4:11 using shared irq 11. vga0 rev 64 on pci0:11 mapreg[10] type=0 addr=e2000000 size=1000000. mapreg[14] type=1 addr=0000b400 size=0100. pci0: uses 83890176 bytes of memory from e2000000 upto e7ffffff. pci0: uses 576 bytes of I/O space from b400 upto dfff. pci0: subordinate busses from 1 upto 1. Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 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 sc0: video mode:24 sc0: VGA registers 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 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 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: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm0: status after reset 00 02 64 psm: status 00 00 64 (get_mouse_buttons) psm0: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0, 2 buttons 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: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S npx0 flags 0x1 on motherboard npx0: INT 16 interface apm0: disabled, not probed. imasks: bio c0004840, tty c003109a, net c0020800 BIOS Geometries: 0:03fe0f3f 0..1022=1023 cylinders, 0..15=16 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Considering FFS root f/s. configure() finished. new masks: bio c0004840, tty c003109a, net c003189a wd0s1: type 0xa5, start 63, end = 16514063, size 16514001 : OK sd0s1: type 0x6, start 63, end = 417689, size 417627 : OK sd0s2: type 0xa5, start 417690, end = 8883944, size 8466255 : OK sd0s1: type 0x6, start 63, end = 417689, size 417627 : OK sd0s2: type 0xa5, start 417690, end = 8883944, size 8466255 : OK sd0s1: type 0x6, start 63, end = 417689, size 417627 : OK sd0s2: type 0xa5, start 417690, end = 8883944, size 8466255 : OK # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/wd0s1b none swap sw 0 0 /dev/wd0a / ufs rw 1 1 /dev/wd0s1f /usr ufs rw 2 2 /dev/wd0s1e /var ufs rw 2 2 proc /proc procfs rw 0 0 /dev/sd0s2e /test1 ufs rw 2 2 /dev/sd0s2f /test2 ufs rw 2 2 # cat /sys/i386/conf/FATBUREN # # FATBUREN # machine "i386" cpu "I686_CPU" ident FATBUREN maxusers 16 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options "CD9660" #ISO 9660 Filesystem options QUOTA #enable disk quotas options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=4 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor # MAXMEM specifies the amount of RAM on the machine; if this is not # specified, FreeBSD will read the amount of memory from the CMOS RAM, # so the amount of memory will be limited to 64MB or 16MB depending on # the BIOS. The amount is in kilobytes, so for a machine with 128MB of # RAM, it would be 131072 (128 * 1024). options MAXMEM=131072 options DDB config kernel root on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 options SCSIDEBUG # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ahc0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable # Advanced Power Management options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device vx0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device ppp 1 pseudo-device vn 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. (Needed by X11?) # options SYSVSHM options SYSVSEM options SYSVMSG From owner-freebsd-scsi Wed Jan 14 23:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07462 for freebsd-scsi-outgoing; Wed, 14 Jan 1998 23:17:23 -0800 (PST) (envelope-from owner-freebsd-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07310 for ; Wed, 14 Jan 1998 23:15:22 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id RAA00983 for ; Thu, 15 Jan 1998 17:45:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id RAA00626 for freebsd-scsi@freebsd.org; Thu, 15 Jan 1998 17:45:10 +1030 (CST) (envelope-from grog) Message-ID: <19980113161052.30019@lemis.com> Date: Tue, 13 Jan 1998 16:10:52 +1030 From: Greg Lehey To: FreeBSD SCSI Mailing List Subject: ABORTED COMMAND: Initiator detected error message received Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84e Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've just been doing some system rebuilding (swapping drives between two systems), and have run into a large number of the following messages: Jan 13 16:04:27 daemon /kernel: sd0(aha0:0:0): ABORTED COMMAND asc:48,0 Jan 13 16:04:27 daemon /kernel: sd0(aha0:0:0): Initiator detected error message received Jan 13 16:04:27 daemon /kernel: , retries:4 This is with a somewhat flaky Micropolis drive: Jan 11 19:11:23 freebie /kernel: scbus1 at ahc1 bus 0 Jan 11 19:11:23 freebie /kernel: scbus1 target 0 lun 0: type 0 fixed SCSI 2 Jan 11 19:11:23 freebie /kernel: sd1 at scbus1 target 0 lun 0 Jan 11 19:11:23 freebie /kernel: sd1: Direct-Access 1001MB (2051615 512 byte sectors) Jan 11 19:11:23 freebie /kernel: sd1: with 1760 cyls, 15 heads, and an average 77 sectors/track The drive has a habit of spinning down and then up again, which confuses the CD-ROM driver sufficiently for me to require a reboot before the problem goes away (thus the swap), but I didn't get this message before on freebie with an ahc (2940) (running -CURRENT for years). daemon is running 2.2.5 with an aha (1542B). The problem doesn't seem to do much harm: the drive still works, but when it's working hard, I'll get a message every 2 or 3 seconds. I'm guessing it might be something to do with the bus (I also have four old 5¼" SCSI drives and an old CD-ROM on the chain). Any suggestions? Greg From owner-freebsd-scsi Thu Jan 15 05:06:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16597 for freebsd-scsi-outgoing; Thu, 15 Jan 1998 05:06:05 -0800 (PST) (envelope-from owner-freebsd-freebsd-scsi@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16577 for ; Thu, 15 Jan 1998 05:05:27 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from pacific.jrc.it by mrelay.jrc.it (LMC5688) with SMTP id OAA21233; Thu, 15 Jan 1998 14:04:19 +0100 (MET) Received: from ross.jrc.it by pacific.jrc.it (4.1/IRSA-ME_1.3m) id AA04073; Thu, 15 Jan 98 14:04:20 +0100 Posted-Date: Thu, 15 Jan 1998 14:04:19 +0100 (MET) Date: Thu, 15 Jan 1998 14:04:19 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@ross.jrc.it Reply-To: Nick Hibma To: freebsd-scsi@FreeBSD.ORG Cc: grog@lemis.com Subject: Re: ABORTED COMMAND: Initiator detected error message received (fwd) Message-Id: Reply-Path: Nick.Hibma@jrc.it Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id FAA16584 Sender: owner-freebsd-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a slight hint, dunno if it is any use. Nick ME-SAI, Joint Research Centre, Italy building: 69 tel.: +39 332 78 9943 fax.: +39 332 78 9648 ---------- Forwarded message ---------- Date: Thu, 15 Jan 1998 14:00:06 +0100 From: Neil Corlett To: Nick Hibma Subject: Re: ABORTED COMMAND: Initiator detected error message received (fwd) Was 1991AV series... That lad should set the jumper on the drive so it does not spin down when idle (its a setting). The jumper block will normally be next to the 50pin SCSI connector. Nick Hibma wrote: > Wasn't this what you were talking about lately, Microlpolis drives screwing > up when they are very busy? If you could get an answer, that would > probably useful. > > Send it back and I'll post it. > > Nick. > > ---------- Forwarded message ---------- > Date: Tue, 13 Jan 1998 16:10:52 +1030 > From: Greg Lehey > To: FreeBSD SCSI Mailing List > Subject: ABORTED COMMAND: Initiator detected error message received > > I've just been doing some system rebuilding (swapping drives between > two systems), and have run into a large number of the following > messages: > > Jan 13 16:04:27 daemon /kernel: sd0(aha0:0:0): ABORTED COMMAND asc:48,0 > Jan 13 16:04:27 daemon /kernel: sd0(aha0:0:0): Initiator detected error message received > Jan 13 16:04:27 daemon /kernel: , retries:4 > > This is with a somewhat flaky Micropolis drive: > > Jan 11 19:11:23 freebie /kernel: scbus1 at ahc1 bus 0 > Jan 11 19:11:23 freebie /kernel: scbus1 target 0 lun 0: type 0 fixed SCSI 2 > Jan 11 19:11:23 freebie /kernel: sd1 at scbus1 target 0 lun 0 > Jan 11 19:11:23 freebie /kernel: sd1: Direct-Access 1001MB (2051615 512 byte sectors) > Jan 11 19:11:23 freebie /kernel: sd1: with 1760 cyls, 15 heads, and an average 77 sectors/track > > The drive has a habit of spinning down and then up again, which > confuses the CD-ROM driver sufficiently for me to require a reboot > before the problem goes away (thus the swap), but I didn't get this > message before on freebie with an ahc (2940) (running -CURRENT for > years). daemon is running 2.2.5 with an aha (1542B). > > The problem doesn't seem to do much harm: the drive still works, but > when it's working hard, I'll get a message every 2 or 3 seconds. I'm > guessing it might be something to do with the bus (I also have four > old 5¼" SCSI drives and an old CD-ROM on the chain). Any suggestions? > > Greg -- email : neil.corlett@jrc.it phone : +39 332 785279 fax : +39 332 789074 From owner-freebsd-scsi Thu Jan 15 06:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24298 for freebsd-scsi-outgoing; Thu, 15 Jan 1998 06:28:15 -0800 (PST) (envelope-from owner-freebsd-freebsd-scsi@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24258; Thu, 15 Jan 1998 06:28:00 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id GAA15382; Thu, 15 Jan 1998 06:31:12 -0800 (PST) Message-Id: <199801151431.GAA15382@implode.root.com> To: Sebastian Strollo cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: running 2.2.5-RELEASE on a ASUS P2L97-S In-reply-to: Your message of "Wed, 14 Jan 1998 23:17:23 +0100." <199801142217.XAA07158@scotch.du.etx.ericsson.se> From: David Greenman Reply-To: dg@root.com Date: Thu, 15 Jan 1998 06:31:12 -0800 Sender: owner-freebsd-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I am having trouble with a newly purchased machine that I have put >together. Below is the specs. At first the system would completely >lock up (i.e. only respond to the Mighty Big Reset Button) when ... > 1 (one) 64MB SDRAM 100MHz module Probably a defective or incompatible SDRAM module. I've heard a lot of reports about problems with SDRAM (as well as having my own bad experiance). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-scsi Thu Jan 15 07:57:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04465 for freebsd-scsi-outgoing; Thu, 15 Jan 1998 07:57:45 -0800 (PST) (envelope-from owner-freebsd-freebsd-scsi@FreeBSD.ORG) Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04444; Thu, 15 Jan 1998 07:57:32 -0800 (PST) (envelope-from ksmm@cybercom.net) Received: from localhost (ksmm@localhost) by kalypso.cybercom.net (8.8.7/8.8.7) with SMTP id KAA25546; Thu, 15 Jan 1998 10:56:01 -0500 (EST) Date: Thu, 15 Jan 1998 10:55:58 -0500 (EST) From: The Classiest Man Alive X-Sender: ksmm@kalypso.cybercom.net To: Sebastian Strollo cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: running 2.2.5-RELEASE on a ASUS P2L97-S In-Reply-To: <199801142217.XAA07158@scotch.du.etx.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Based on the limited information you provided, the only thing that I find particularly suspect is the IRQ conflict with the ethernet card and the SCSI controller. Have you tried this test without the ethernet card present? K.S. On Wed, 14 Jan 1998, Sebastian Strollo wrote: : [ lots of detail omitted... ] : : Info on the system: : : (One thing which I don't understand is why the ethernet card, the : adaptec chip (and the USB chip) gets the same irq 11? This is done by : the BIOS(?) - I tried to wire the PCI slot which the ethernet card : sits in to a different irq, which just lead to that all three devices : that were previously mapped to irq 11 now got mapped to the new irq) : : [ even more detail omitted... ] From owner-freebsd-scsi Thu Jan 15 08:21:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06840 for freebsd-scsi-outgoing; Thu, 15 Jan 1998 08:21:51 -0800 (PST) (envelope-from owner-freebsd-freebsd-scsi@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06768; Thu, 15 Jan 1998 08:21:35 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id JAA08398; Thu, 15 Jan 1998 09:21:21 -0700 (MST) Message-Id: <199801151621.JAA08398@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: dg@root.com cc: Sebastian Strollo , freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: running 2.2.5-RELEASE on a ASUS P2L97-S In-reply-to: Your message of "Thu, 15 Jan 1998 06:31:12 PST." <199801151431.GAA15382@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Jan 1998 09:21:21 -0700 Sender: owner-freebsd-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, ASUS specifies the "low chip count" memory parts, your DIMMs may have too many chips on them to drive properly... When I put 64MB DIMMs on my L97 I had to pay more for the DIMMs with the high-density chips to avoid this. Before you ask, I don't know the max number, and couldn't find it in the manual. I trusted my vendor to spec the right parts... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-scsi Thu Jan 15 15:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24203 for freebsd-scsi-outgoing; Thu, 15 Jan 1998 15:30:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24106 for ; Thu, 15 Jan 1998 15:29:53 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id JAA00476; Fri, 16 Jan 1998 09:59:48 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id JAA04007; Fri, 16 Jan 1998 09:59:48 +1030 (CST) (envelope-from grog) Message-ID: <19980116095948.32283@lemis.com> Date: Fri, 16 Jan 1998 09:59:48 +1030 From: Greg Lehey To: Nick Hibma Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ABORTED COMMAND: Initiator detected error message received (fwd) References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.84e In-Reply-To: ; from Nick Hibma on Thu, Jan 15, 1998 at 02:04:19PM +0100 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jan 15, 1998 at 02:04:19PM +0100, Nick Hibma wrote: > > Just a slight hint, dunno if it is any use. Thanks. The drive is not configured to power down, and these things happen too frequently for that to be the cause. Justin Gibbs gave me an answer which sounds reasonable: cabling problems. Greg > ---------- Forwarded message ---------- > Date: Thu, 15 Jan 1998 14:00:06 +0100 > From: Neil Corlett > To: Nick Hibma > Subject: Re: ABORTED COMMAND: Initiator detected error message received (fwd) > > Was 1991AV series... That lad should set the jumper on the drive so > it does not spin down when idle (its a setting). The jumper block > will normally be next to the 50pin SCSI connector. > Nick Hibma wrote: > >> Wasn't this what you were talking about lately, Microlpolis drives screwing >> up when they are very busy? If you could get an answer, that would >> probably useful. >> >> Send it back and I'll post it. >> >> Nick. >> >> ---------- Forwarded message ---------- >> Date: Tue, 13 Jan 1998 16:10:52 +1030 >> From: Greg Lehey >> To: FreeBSD SCSI Mailing List >> Subject: ABORTED COMMAND: Initiator detected error message received >> >> I've just been doing some system rebuilding (swapping drives between >> two systems), and have run into a large number of the following >> messages: >> >> Jan 13 16:04:27 daemon /kernel: sd0(aha0:0:0): ABORTED COMMAND asc:48,0 >> Jan 13 16:04:27 daemon /kernel: sd0(aha0:0:0): Initiator detected error message received >> Jan 13 16:04:27 daemon /kernel: , retries:4 >> >> This is with a somewhat flaky Micropolis drive: >> >> Jan 11 19:11:23 freebie /kernel: scbus1 at ahc1 bus 0 >> Jan 11 19:11:23 freebie /kernel: scbus1 target 0 lun 0: type 0 fixed SCSI 2 >> Jan 11 19:11:23 freebie /kernel: sd1 at scbus1 target 0 lun 0 >> Jan 11 19:11:23 freebie /kernel: sd1: Direct-Access 1001MB (2051615 512 byte sectors) >> Jan 11 19:11:23 freebie /kernel: sd1: with 1760 cyls, 15 heads, and an average 77 sectors/track >> >> The drive has a habit of spinning down and then up again, which >> confuses the CD-ROM driver sufficiently for me to require a reboot >> before the problem goes away (thus the swap), but I didn't get this >> message before on freebie with an ahc (2940) (running -CURRENT for >> years). daemon is running 2.2.5 with an aha (1542B). >> >> The problem doesn't seem to do much harm: the drive still works, but >> when it's working hard, I'll get a message every 2 or 3 seconds. I'm >> guessing it might be something to do with the bus (I also have four >> old 5¼" SCSI drives and an old CD-ROM on the chain). Any suggestions? >> >> Greg > > > > -- > email : neil.corlett@jrc.it > phone : +39 332 785279 > fax : +39 332 789074 > > > > -- Greg Lehey LEMIS grog@lemis.com PO Box 460 Tel: +61-8-8388-8286 Echunga SA 5153 Fax: +61-8-8388-8725 Australia -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2i mQCNAzGpfDEAAAEEAMh6rH1c9+oKgazwGLitshrIFKFSGelccTK1fwnMw2O6SrK8 r0ttvRO42fZa8WXvlsSF1JIAqOJoaBP8HJNv6G/RA1NcKgqQKLc4RmTNnu6MoPe0 a25w25wyKOfzefJTS9dsQhWg2XJlyRo4YMtbSxDOZldq7kmga0Sj8+byVwABAAUR tBNDQyA8Y2NAbWFyY2FkZS5jb20+tAZDb250cm8= =FJvY -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-scsi Sun Jan 18 06:14:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06742 for freebsd-scsi-outgoing; Sun, 18 Jan 1998 06:07:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sinbin.demos.su (sinbin.demos.su [194.87.5.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA06706 for ; Sun, 18 Jan 1998 06:06:57 -0800 (PST) (envelope-from skraldespand.demos.su!mishania@sinbin.demos.su) Received: from skraldespand.demos.su by sinbin.demos.su with ESMTP id RAA08794; (8.6.12/D) Sun, 18 Jan 1998 17:01:39 +0300 Received: (from mishania@localhost) by skraldespand.demos.su (8.8.8/D) id RAA09158; Sun, 18 Jan 1998 17:00:37 +0300 (MSK) Posted-Date: Sun, 18 Jan 1998 17:00:37 +0300 (MSK) Message-ID: <19980118170032.05352@demos.su> Date: Sun, 18 Jan 1998 17:00:33 +0300 From: "Mikhail A. Sokolov" To: scsi@freebsd.org Cc: "Alex G. Bulushev" , ache@nagual.pp.ru Subject: uhm. help me with error message, please? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk X-Loop: FreeBSD.org Hello, people. Could any of you please explain what does this error messsage stand for? Thanks in advance. ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 15 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 14 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 13 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 12 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 11 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 10 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 9 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 8 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 7 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 6 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 5 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 4 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 3 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 2 ahc0: WARNING no command for scb 3 (cmdcmplt) QOUTCNT == 1 sd1: RECOVERED ERROR info:0x134d37 asc:18,1 sd1: Recovered data with error correction & retries applied field replaceable u nit: ea sks:80,1, retries:4 -- -mishania From owner-freebsd-scsi Mon Jan 19 03:10:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16764 for freebsd-scsi-outgoing; Mon, 19 Jan 1998 03:10:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16684; Mon, 19 Jan 1998 03:09:49 -0800 (PST) (envelope-from seb@erix.ericsson.se) Received: from super.du.etx.ericsson.se (root@super.du.etx.ericsson.se [150.236.14.16]) by penguin.wise.edt.ericsson.se (8.7.5/8.7.3/glacier-1.12) with ESMTP id MAA04813; Mon, 19 Jan 1998 12:09:46 +0100 (MET) Received: from scotch.du.etx.ericsson.se (seb@scotch.du.etx.ericsson.se [150.236.14.76]) by super.du.etx.ericsson.se (8.8.8/8.8.8/erix-1.1) with ESMTP id MAA06378; Mon, 19 Jan 1998 12:09:46 +0100 (MET) Received: by scotch.du.etx.ericsson.se (8.8.5/client-1.4) id MAA17451; Mon, 19 Jan 1998 12:09:45 +0100 (CET) Date: Mon, 19 Jan 1998 12:09:45 +0100 (CET) Message-Id: <199801191109.MAA17451@scotch.du.etx.ericsson.se> From: Sebastian Strollo To: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: running 2.2.5-RELEASE on a ASUS P2L97-S Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi again Earlier I wrote: > I am having trouble with a newly purchased machine that I have put > together. Below is the specs. At first the system would completely > lock up (i.e. only respond to the Mighty Big Reset Button) when > putting load on the SCSI disk. >... [lengthy description of the machine and the problem omitted] Thank you for all your suggestions! I tried a couple of new combinations of memory chips and cards, but ended up replacing the motherboard, and whaddayanow, now the machine runs like a charm! Hardware errors like these are scary. ;-( David Greenman , wrote: > ... > > 1 (one) 64MB SDRAM 100MHz module > > Probably a defective or incompatible SDRAM module. I've heard a lot of > reports about problems with SDRAM (as well as having my own bad experiance). and Steve Passe wrote: > > ASUS specifies the "low chip count" memory parts, your DIMMs may have too > many chips on them to drive properly... When I put 64MB DIMMs on my L97 > I had to pay more for the DIMMs with the high-density chips to avoid this. > Before you ask, I don't know the max number, and couldn't find it in > the manual. I trusted my vendor to spec the right parts... Which got me to suspect the 64MB module, which is one of these "double height" thingies with a lot of chips on them. (A FOAF also suggested that these were actually non standard, since the leads to the chips got too long.) However I also had two 32MB SDRAM modules, and when I used those the machine froze as well. The Classiest Man Alive , wrote: > > Based on the limited information you provided, the only thing that I find > particularly suspect is the IRQ conflict with the ethernet card and the > SCSI controller. Have you tried this test without the ethernet card > present? No, I hadn't at first. The conflict got me suspicious as well, and after reading the motherboard manual a bit more carefully I found in a small footnote: "PCI slot 4 share the same interrupt number as the onboard SCSI so PCI slot 4 card must be able to share an INT# or make sure that it does not use an INT# at all". This is the slot I had the ethernet card in, now I don't. However I got curious when we replaced the motherboard so I did put the ethernet card in there to try it out, and it seems to work ok to share the interrupt. I ran a couple of "bonnie" (on the SCSI disks) at the same time as transferring the contents of a CDROM (also on SCSI) to another host on the network, without any crashes or lockups. From owner-freebsd-scsi Tue Jan 20 18:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03721 for freebsd-scsi-outgoing; Tue, 20 Jan 1998 18:57:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03716 for ; Tue, 20 Jan 1998 18:57:15 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id SAA08634; Tue, 20 Jan 1998 18:57:06 -0800 (PST) Date: Tue, 20 Jan 1998 18:57:06 -0800 (PST) From: Jaye Mathisen To: salyzyn@dpt.com cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RAID on FreeBSD In-Reply-To: <9712122209.AA20739@bohica.bohica.dpt.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 While I realize this is an old message, it's answers like this that make me glad I keep on buying DPT. I appreciate DPT's efforts in making their board work with just about everything. On Fri, 12 Dec 1997, Mark Salyzyn wrote: > In article <3.0.32.19971211155601.0092e580@gw1.tesys.com>, you wrote: > >At 03:04 PM 12/11/97 -0800, Tom wrote: > >>On Thu, 11 Dec 1997, Wilko Bulte wrote: > >>> > 9 drives in an uncomfortable number for RAID5. Probably better to go > >>> Why would 9 drives be uncomfartable? > >> Well, if you are going to making one arrray of 9 drives, write > >>performance will bad. If you are going to making 3 arrays of 3 > >>drives each, you will end up with a lot of overhead. > >> RAID5 arrays of 5 drives is kinda of nice sweet spot. If you go much > >>bigger, just use RAID0 over multiple RAID5. > >Please note that dual RAID support (dpt based) is not available under > >FreeBSD(there are few other OS's which do support it), as per my > >information.. Can someone verify that.. > > Software RAID is not available for the current driver by Simon. > > However, we have supplied Simon sources to a RAID-0 subsystem that he > may add to the driver in the future. > > There is nothing preventing an OS RAID-0 from being set up, the > only disadvantages are that it is not integrated into the DPT management > solutions and you can not boot off of a dual level RAID device utilizing > the second level within an OS driver. > > Sincerely -- Mark Salyzyn > From owner-freebsd-scsi Wed Jan 21 09:24:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13301 for freebsd-scsi-outgoing; Wed, 21 Jan 1998 09:24:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA13295 for ; Wed, 21 Jan 1998 09:24:16 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 26825 invoked by uid 1000); 21 Jan 1998 17:28:39 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [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, 21 Jan 1998 09:28:39 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Jaye Mathisen Subject: Re: RAID on FreeBSD Cc: freebsd-scsi@FreeBSD.ORG, salyzyn@dpt.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 21-Jan-98 Jaye Mathisen wrote: > > While I realize this is an old message, it's answers like this that make > me glad I keep on buying DPT. > > I appreciate DPT's efforts in making their board work with just about > everything. > > On Fri, 12 Dec 1997, Mark Salyzyn wrote: > >> In article <3.0.32.19971211155601.0092e580@gw1.tesys.com>, you wrote: >> >At 03:04 PM 12/11/97 -0800, Tom wrote: >> >>On Thu, 11 Dec 1997, Wilko Bulte wrote: >> >>> > 9 drives in an uncomfortable number for RAID5. Probably better >> >>> > to go >> >>> Why would 9 drives be uncomfartable? >> >> Well, if you are going to making one arrray of 9 drives, write >> >>performance will bad. If you are going to making 3 arrays of 3 >> >>drives each, you will end up with a lot of overhead. >> >> RAID5 arrays of 5 drives is kinda of nice sweet spot. If you go >> >> much >> >>bigger, just use RAID0 over multiple RAID5. >> >Please note that dual RAID support (dpt based) is not available under >> >FreeBSD(there are few other OS's which do support it), as per my >> >information.. Can someone verify that.. >> >> Software RAID is not available for the current driver by Simon. Hi Mark! This is true. Time, simply no time. >> However, we have supplied Simon sources to a RAID-0 subsystem that he >> may add to the driver in the future. Once we get the multi-initiator code to work, we will look at the in-kernel RAID-0. >> There is nothing preventing an OS RAID-0 from being set up, the >> only disadvantages are that it is not integrated into the DPT management >> solutions and you can not boot off of a dual level RAID device utilizing >> the second level within an OS driver. While I totally agree that an integrated solution is better, the ccd driver in FreeBSD does a fine job for most. The only thing it does not do is allow you to boot from a RAID-0 conposed of several RAID-{1,5}. And yes, Unlike some other HBA manufacturers, DPT actually helps and encourages use of its products in a non-M$ non-NDA environment. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-scsi Wed Jan 21 10:29:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18574 for freebsd-scsi-outgoing; Wed, 21 Jan 1998 10:29:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from interlock2.lexmark.com (interlock2.lexmark.com [192.146.101.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18570 for ; Wed, 21 Jan 1998 10:29:39 -0800 (PST) (envelope-from emking@lexmark.com) From: emking@lexmark.com Received: by interlock2.lexmark.com id AA21192 (InterLock SMTP Gateway 3.0 for freebsd-scsi@FreeBSD.ORG); Wed, 21 Jan 1998 13:29:36 -0500 Message-Id: <199801211829.AA21192@interlock2.lexmark.com> Received: by interlock2.lexmark.com (Protected-side Proxy Mail Agent-1); Wed, 21 Jan 1998 13:29:36 -0500 X-Lotus-Fromdomain: LEXMARK@LEXMTA To: freebsd-scsi@FreeBSD.ORG Date: Wed, 21 Jan 1998 13:27:58 -0500 Subject: Target mode support Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org To: freebsd-scsi%FreeBSD.ORG@interlock.lexmark.com@LEXMTA cc: From: Matt King @ LEXMARK@LEXMTA Extension: X-6907 Date: 01/21/98 01:27:58 PM Subject: Target mode support Can anyone point me at any info on target mode support on any of the SCSI drivers for Free-BSD, if it exists. I found a nugget that indicated some support for the Adaptec 1542B. I also understand that the CAM interface is architected to support target mode and that it may eventually be supported in the new drivers that are being developed. I would kill for a snip if sample code. Many Thanks, Matt King Regards, Matt Matt King All opinions are my own and in Staff Engineer general are completely different Lexmark International, Inc. from those around me! emking @ lexmark.com From owner-freebsd-scsi Wed Jan 21 13:02:42 1998 Return-Path: Received: (from majordom@localhost) by catfish.freebsd.org (8.8.8/8.8.8) id NAA22186 for freebsd-scsi-outgoing; Wed, 21 Jan 1998 13:02:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by catfish.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22181 for ; Wed, 21 Jan 1998 13:02:41 -0800 (PST) (envelope-from owner-majordomo@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA27593 for ; Wed, 21 Jan 1998 13:02:34 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 23459 invoked by uid 1000); 21 Jan 1998 20:39:53 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-011998 [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: <199801211829.AA21192@interlock2.lexmark.com> Date: Wed, 21 Jan 1998 12:39:53 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: emking@lexmark.com Subject: RE: Target mode support Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am working on adding it to the DPT driver, as part of the DLM and DIO options for FreeBSD. On 21-Jan-98 emking@lexmark.com wrote: > > > > > To: freebsd-scsi%FreeBSD.ORG@interlock.lexmark.com@LEXMTA > cc: > From: Matt King @ LEXMARK@LEXMTA > Extension: X-6907 > Date: 01/21/98 01:27:58 PM > Subject: Target mode support > > Can anyone point me at any info on target mode support on any of the SCSI > drivers for Free-BSD, if it exists. I found a nugget that indicated some > support for the Adaptec 1542B. I also understand that the CAM interface > is > architected to support target mode and that it may eventually be > supported > in the new drivers that are being developed. I would kill for a snip if > sample code. > > Many Thanks, > Matt King > > Regards, > Matt > > Matt King All opinions are my own and in > Staff Engineer general are completely different > Lexmark International, Inc. from those around me! > emking @ lexmark.com > > ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-scsi Wed Jan 21 15:17:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08297 for freebsd-scsi-outgoing; Wed, 21 Jan 1998 15:17:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08291 for ; Wed, 21 Jan 1998 15:17:13 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id PAA09022; Wed, 21 Jan 1998 15:56:00 -0700 (MST) Date: Wed, 21 Jan 1998 15:56:00 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801212256.PAA09022@narnia.plutotech.com> To: emking@lexmark.com cc: scsi@FreeBSD.ORG Subject: Re: Target mode support Newsgroups: pluto.freebsd.scsi In-Reply-To: <199801211829.AA21192@interlock2.lexmark.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can anyone point me at any info on target mode support on any of the SCSI > drivers for Free-BSD, if it exists. I found a nugget that indicated some > support for the Adaptec 1542B. I also understand that the CAM interface is > architected to support target mode and that it may eventually be supported > in the new drivers that are being developed. I would kill for a snip if > sample code. The aic7xxx driver available in the snapshots of the new CAM SCSI layer has the beginnings of target mode support in it. It's by no means complete, and, as I've been pulled onto another project for the next 4-6 months, I don't anticipate getting back to it soon. It will be completed later this year though as it is still in my employer's interest to have the aic7xxx driver support target mode. > Matt King All opinions are my own and in > Staff Engineer general are completely different > Lexmark International, Inc. from those around me! > emking @ lexmark.com -- Justin From owner-freebsd-scsi Fri Jan 23 01:07:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA14516 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 01:07:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA14506; Fri, 23 Jan 1998 01:07:25 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.8/D) id MAA28675; Fri, 23 Jan 1998 12:06:06 +0300 (MSK) Posted-Date: Fri, 23 Jan 1998 12:06:06 +0300 (MSK) Message-ID: <19980123120606.31963@demos.su> Date: Fri, 23 Jan 1998 12:06:06 +0300 From: "Mikhail A. Sokolov" To: gibbs@FreeBSD.ORG Cc: scsi@FreeBSD.ORG, ache@FreeBSD.ORG Subject: Infortrend's drivers/help needed, please. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, could you please help us with the following: we have IFT controller, which allows us to create several (up to 64) logical units, which are routed to scsi channels with one (different for each channel, though) id and different lun's. There are no problems when you create two logical units and each of them is connected to different channel (hence, different id's). Both channels are connected to one scsi bus as different devices: term---+----+---------2940uw | | id1 id2 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8683MB (17783104 512 byte sectors) sd1 at scbus0 target 2 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 8683MB (17783104 512 byte sectors) In case the same devices are connected to the same channel (hence, getting the same id with different lun's) - sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8683MB (17783104 512 byte sectors) sd1 at scbus0 target 1 lun 1 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 8683MB (17783104 512 byte sectors) While working with separate device everything goes ok then; when you ccd those, errors like the below described start to appear: sd1: SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1: SCB 0: Immediate reset. Flags = 0x1 sd1: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 What we think here: it's hardly IFT's (i.e. hardware problem), it can work with different lun's (we checked on two different IFT devices), it's neither aic7880's trouble (it works with several lun's, doesn't it?), - might be some error in ahc driver. Likely, it isn't a typical case when fast devices like sd get one id and different lun's and isn't tested ok. This situation is the very same for -stable as well as for -current. Some details: 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-CURRENT #0: Tue Jan 20 12:54:29 MSK 1998 bag@dt.demos.su:/usr/src/sys/compile/RT CPU: Pentium (165.79-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30785536 (30064K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 fxp0: rev 0x01 int a irq 5 on pci0.6.0 fxp0: Ethernet address 00:a0:c9:1d:b2:aa vga0: rev 0x03 on pci0.7.0 ahc0: rev 0x01 int a irq 11 on pci0.8.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8683MB (17783104 512 byte sectors) sd1 at scbus0 target 2 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 8683MB (17783104 512 byte sectors) chip1: rev 0x02 on pci0.15.0 ide_pci0: rev 0x02 on pci0.15.1 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 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 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: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S npx0 flags 0x1 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround ccd0-3: Concatenated disk drivers ^^^^^^ There're no errors, when sd0/sd1 have different ids. 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-CURRENT #0: Tue Jan 20 12:54:29 MSK 1998 bag@dt.demos.su:/usr/src/sys/compile/RT CPU: Pentium (165.79-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30785536 (30064K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 fxp0: rev 0x01 int a irq 5 on pci0.6.0 fxp0: Ethernet address 00:a0:c9:1d:b2:aa vga0: rev 0x03 on pci0.7.0 ahc0: rev 0x01 int a irq 11 on pci0.8.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8683MB (17783104 512 byte sectors) sd1 at scbus0 target 1 lun 1 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 8683MB (17783104 512 byte sectors) chip1: rev 0x02 on pci0.15.0 ide_pci0: rev 0x02 on pci0.15.1 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 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 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: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S npx0 flags 0x1 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround ccd0-3: Concatenated disk drivers ^^^^^ There are errors, when sd0/sd1 have one id and different luns: sd1: SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1: SCB 0: Immediate reset. Flags = 0x1 sd1: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:4 sd1: SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1: SCB 2: Immediate reset. Flags = 0x1 sd1: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:3 sd0: SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd0: SCB 3: Immediate reset. Flags = 0x1 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:1 sd0: SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd0: SCB 2: Immediate reset. Flags = 0x1 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:3 sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 sd1: SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1: SCB 2: Immediate reset. Flags = 0x1 sd1: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:4 sd1: SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1: SCB 0: Immediate reset. Flags = 0x1 sd1: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd1: UNIT ATTENTION asc:29,0 sd1: Power on, reset, or bus device reset occurred , retries:3 sd0: SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd0: SCB 3: Immediate reset. Flags = 0x1 sd0: no longer in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted sd0: UNIT ATTENTION asc:29,0 sd0: Power on, reset, or bus device reset occurred , retries:3 You help will be appreciated a lot. -- -mishania From owner-freebsd-scsi Fri Jan 23 08:24:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15439 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 08:24:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gw2.leirianet.pt (gw2-e0.leirianet.pt [195.23.92.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15433 for ; Fri, 23 Jan 1998 08:24:43 -0800 (PST) (envelope-from jm@pluriproj.pt) Received: from antares.leirianet.pt (antares.leirianet.pt [195.23.92.195]) by gw2.leirianet.pt (8.8.8/8.8.8) with SMTP id QAA11259 for ; Fri, 23 Jan 1998 16:26:00 GMT From: jm@pluriproj.pt (Jose' Monteiro) To: freebsd-scsi@FreeBSD.ORG Subject: Flashpoint LW SCSI host adapter Date: Fri, 23 Jan 1998 16:24:22 GMT X-PGP-Key-Fingerprint: 2.6.3ia: 4289 7864 7C6F 06C6 BB1E 299E 8FFA DC61 - 5.0: B698 9856 F7DD C74B 657E 0122 9392 9164 F2EE A48B Organization: Leiri@net Reply-To: "Jose' Monteiro" Message-ID: <34cdc261.9945780@mail.pluriproj.pt> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA15435 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm installing FreeBSD 2.2.5 on a Pentium II with Barracuda SCSI disk controled by a Flashpoint LW PCI to SCSI Host Adapter (Mylex). When booting from the CD, the generic kernel recognizes the adapter as beeing a Buslogic SCSI Adapter on IRQ 10, but specifies that there is no driver assigned. What support is there in FreeBSD 2.2.5 to this kind of SCSI controller? Tnx Jose Monteiro From owner-freebsd-scsi Fri Jan 23 09:04:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19446 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 09:04:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19403; Fri, 23 Jan 1998 09:03:56 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id KAA06806; Fri, 23 Jan 1998 10:03:32 -0700 (MST) Message-Id: <199801231703.KAA06806@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: "Mikhail A. Sokolov" cc: gibbs@FreeBSD.ORG, scsi@FreeBSD.ORG, ache@FreeBSD.ORG Subject: Re: Infortrend's drivers/help needed, please. In-reply-to: Your message of "Fri, 23 Jan 1998 12:06:06 +0300." <19980123120606.31963@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Jan 1998 10:01:03 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >In case the same devices are connected to the same channel (hence, getting >the same id with different lun's) - > >sd0 at scbus0 target 1 lun 0 >sd0: type 0 fixed SCSI 2 >sd0: Direct-Access 8683MB (17783104 512 byte sectors) >sd1 at scbus0 target 1 lun 1 >sd1: type 0 fixed SCSI 2 >sd1: Direct-Access 8683MB (17783104 512 byte sectors) Yes, this is a long standing bug having to do with multi-lun devices in the aic7xxx driver. It has been corrected in the CAM version of the driver, but the changes are too invasive to attempt to port them into the driver in either current or stable. Since this kinds of devices that trigger this problem are rare, it seldom causes problems. Yours is the first bug report I've seen about this issue. -- Justin From owner-freebsd-scsi Fri Jan 23 09:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24023 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 09:58:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gw2.leirianet.pt (gw2-e0.leirianet.pt [195.23.92.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23969 for ; Fri, 23 Jan 1998 09:57:30 -0800 (PST) (envelope-from jm@pluriproj.pt) Received: from antares.leirianet.pt (antares.leirianet.pt [195.23.92.195]) by gw2.leirianet.pt (8.8.8/8.8.8) with SMTP id RAA12121 for ; Fri, 23 Jan 1998 17:58:44 GMT From: jm@pluriproj.pt (Jose' Monteiro) To: scsi@FreeBSD.ORG Subject: (fwd) Re: FreeBSD support of Flashpoint LW Date: Fri, 23 Jan 1998 17:57:06 GMT X-PGP-Key-Fingerprint: 2.6.3ia: 4289 7864 7C6F 06C6 BB1E 299E 8FFA DC61 - 5.0: B698 9856 F7DD C74B 657E 0122 9392 9164 F2EE A48B Organization: Leiri@net Reply-To: "Jose' Monteiro" Message-ID: <34d2d8d9.15698304@mail.pluriproj.pt> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA24017 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I wrote to mylex technical support regarding FreeBSD support of FlashPoint LW SCSI Host Adapter. This was their answer. I think it will interest the FreeBSD SCSI development Team. Jose Monteiro On Fri, 23 Jan 1998 09:48:08 -0800, "Technical Support" wrote: >Dear Sir: I know of no FlashPoint driver for FreeBSD, but this is a >question you should ask of the FreeBSD programming group - we do not >write the Free Software/GPL drivers in-house. The FlashPoint is fully >supported in Linux. > >Regards, >Jo Kellner >Mylex Technical Support >510-608-2400 >510-745-7715 (fax) >http://www.mylex.com/support/techsupp.html > >------------------------------------------------------------------- >Jose' Monteiro wrote: >> >> Hi, >> >> We recently acquired a new server featuring a Pentium II and a >> Barracuda HD controlled by a FlashPoint LW SCSI Host Adapter. >> >> We only work with FreeBSD, when it comes to Internet Servers. So, I >> started the instalation and verified that there's no driver support >> for this SCSI Adapter in FreeBSD's generic kernel. >> >> Before I start hacking a new kernel with the driver included, I would >> like to know if this driver exists. >> >> If it doesn't, what should I do know with my brand new SCSI Adapter. >> >> Thanks in advance, >> >> Jose Monteiro >> SysAdmin - Leiri@net - Portugal *---------Jose Monteiro ---------* |Pluriproj Lda.- Redes e Sistemas de Comunicacoes | |Agente IP em Leiria - http://www.pluriproj.pt | |Tel: +351 44 829980 - Fax: +351 44 829981 | |PGP Keys: www.pluriproj.pt/~admin/keys.html | |Fingerprints: X Headers | *------------------UIN: 3965786------------------* From owner-freebsd-scsi Fri Jan 23 12:31:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09298 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 12:31:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09293 for ; Fri, 23 Jan 1998 12:31:05 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id NAA14829; Fri, 23 Jan 1998 13:28:17 -0700 (MST) Date: Fri, 23 Jan 1998 13:28:17 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801232028.NAA14829@narnia.plutotech.com> To: "Jose' Monteiro" cc: scsi@FreeBSD.ORG Subject: Re: Flashpoint LW SCSI host adapter In-Reply-To: <34d0c9d3.11852059@mail.pluriproj.pt> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I'm installing FreeBSD 2.2.5 on a Pentium II with Barracuda SCSI disk > controled by a Flashpoint LW PCI to SCSI Host Adapter (Mylex). > > When booting from the CD, the generic kernel recognizes the adapter as > beeing a Buslogic SCSI Adapter on IRQ 10, but specifies that there is > no driver assigned. > > What support is there in FreeBSD 2.2.5 to this kind of SCSI > controller? None. I plan on writing a driver for current, but I cannot anticipate when that driver will be complete. > Tnx > > Jose Monteiro -- Justin From owner-freebsd-scsi Fri Jan 23 16:35:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03353 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 16:35:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA03348 for ; Fri, 23 Jan 1998 16:35:43 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xvtJO-0003wR-00; Fri, 23 Jan 1998 16:19:02 -0800 Date: Fri, 23 Jan 1998 16:19:00 -0800 (PST) From: Tom To: "Jose' Monteiro" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Flashpoint LW SCSI host adapter In-Reply-To: <34cdc261.9945780@mail.pluriproj.pt> 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 Fri, 23 Jan 1998, Jose' Monteiro wrote: > What support is there in FreeBSD 2.2.5 to this kind of SCSI > controller? None. FreeBSD-current will get a driver someday, but it won't be ready for real production work for a while. Of course, an onboard AIC 7880 will run circles around the Flashpoint and is ready for production work now. The same can be said of NCR-750 based cards, although they aren't quite as good on command overhead as AIC 7880 (Adaptec) controllers. > Tnx > > Jose Monteiro > > Tom From owner-freebsd-scsi Fri Jan 23 23:07:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12935 for freebsd-scsi-outgoing; Fri, 23 Jan 1998 23:07:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bob.tri-lakes.net (BOB.tri-lakes.net [207.3.81.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA12924 for ; Fri, 23 Jan 1998 23:07:02 -0800 (PST) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.155] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id qa439962 for ; Sat, 24 Jan 1998 00:29:59 -0600 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 24 Jan 1998 00:06:59 -0600 (CST) From: Chris Dillon To: freebsd-scsi@FreeBSD.ORG Subject: Minor annoyances with ZIP Plus Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just got a IOMega ZIP Plus and am using it with an Adaptec 1522 (AIC6360, aic0). It works fine in Win95, and fine in FreeBSD for the most part, other than some rather annoying error messages when trying to use it for various things. Any time I mount/umount a disk, change it, and do the same again (or even use mtools). You'll notice an error when probing the drive attached to aic0 and all the errors at the bottom (which occur when I try to use it after changing disks): Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.5-STABLE #0: Fri Jan 23 00:53:37 CST 1998 root@cheetah.inter-linc.net:/usr/src/sys/compile/CHEETAH CPU: Pentium (165.76-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 83886080 (81920K bytes) avail memory = 78475264 (76636K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 vga0 rev 1 int a irq 12 on pci0:10 ncr0 rev 3 int a irq 10 on pci0:12 ncr0 waiting for scsi devices to settle (ncr0:0:0): WIDE SCSI (16 bit) enabled(ncr0:0:0): 10.0 MB/s (200 ns, offset 15) (ncr0:0:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) (ncr0:1:0): WIDE SCSI (16 bit) enabled(ncr0:1:0): 10.0 MB/s (200 ns, offset 15) (ncr0:1:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15) 4134MB (8467200 512 byte sectors) 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 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 9 on isa sio2: 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 flags 0xff080ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 520MB (1065456 sectors), 1057 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy wcd0: 1376Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:6:0): "IOMEGA ZIP 100 PLUS J.66" type 0 removable SCSI 2 sd2(aic0:6:0): Direct-Access sd2(aic0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry sd2(aic0:6:0): NOT READY asc:3a,0 Medium not present sd2: could not get size 0MB (0 512 byte sectors) npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround ccd0-3: Concatenated disk drivers IP packet filtering initialized, divert disabled, logging limited to 100 packets/entry OSS/FreeBSD loading, address = f52d8020 sd2(aic0:6:0): UNIT ATTENTION asc:28,0 sd2(aic0:6:0): Not ready to ready transition, medium may have changed sd2(aic0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry sd2(aic0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry sd2(aic0:6:0): UNIT ATTENTION asc:28,0 sd2(aic0:6:0): Not ready to ready transition, medium may have changed sd2(aic0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry sd2(aic0:6:0): UNIT ATTENTION asc:28,0 sd2(aic0:6:0): Not ready to ready transition, medium may have changed sd2(aic0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry sd2(aic0:6:0): UNIT ATTENTION asc:28,0 sd2(aic0:6:0): Not ready to ready transition, medium may have changed sd2(aic0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd2 could not mode sense (4). Using ficticious geometry ...[many many more of these omitted].... Is this a problem with a firmware change (as I have been hearing about with the problems with the ppbus driver)? As you can tell from the output above, i'm running a very recent -STABLE system (kernel was compiled just recently, but the whole thing is no more than a week old). Other than these errors, everything seems to work prefectly. I can scsiformat(8) the disks, disklabel, newfs, mount and throw stuff on them and read it back, without problem. mtools can also read the FAT filesystem disks just fine. If someone tells me what they want me to look for, i can put SCSIDEBUG in the kernel and do some playing around, if that would be required. --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers. ---- (http://www.freebsd.org) From owner-freebsd-scsi Sat Jan 24 18:38:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04148 for freebsd-scsi-outgoing; Sat, 24 Jan 1998 18:38:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-112-213.la.inreach.net [206.18.112.213]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04143 for ; Sat, 24 Jan 1998 18:38:54 -0800 (PST) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.7/8.8.7) id SAA10985; Sat, 24 Jan 1998 18:39:05 -0800 (PST) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 24 Jan 1998 18:32:06 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: Chris Dillon Subject: RE: Minor annoyances with ZIP Plus Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 24-Jan-98, Chris Dillon wrote: >I just got a IOMega ZIP Plus and am using it with an Adaptec 1522 >(AIC6360, >aic0). It works fine in Win95, and fine in FreeBSD for the most part, >other >than some rather annoying error messages when trying to use it for >various >things. Any time I mount/umount a disk, change it, and do the same again >(or >even use mtools). You'll notice an error when probing the drive attached >to >aic0 and all the errors at the bottom (which occur when I try to use it >after >changing disks): Don't worry; these errors are "normal". Well, as "normal" as Iomega SCSI devices get, anyway. Apparently Iomega subscribes to some "weird", non-standard variant of SCSI, in that their devices do not support certain SCSI commands mandated by the SCSI specification, specifically, those SCSI commansd that ask a device to specify its geometry (size, # heads/sectors/etc.). When presented with this anomalous behavior, the FreeBSD driver guesses the device's geometry, and so everything still works. I see the same behavior with my Iomega Jaz drive, and with a prevous Zip drive I used to own. My advice is not to worry about it, shake your head sadly at Iomega's lack of direction, and move on with life. :) - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNMqlw/jpixuAwagxAQGIHQQAjXiI5Y4uxTr4U7zwNfqUPabyeapuFaYm LclIeYYw5cG/xObKrp92PyhINemmwrSjRkmG4K58FBfA0+wQ4Ns4WPaIYs93EpFB dr+juBYGDyzECg5s09lzdKotz49dCVNCWr8C4n02hgrYEVKQxks+tJOBSu7YeEz8 Xqo/YjZHne4= =AjXE -----END PGP SIGNATURE----- From owner-freebsd-scsi Sat Jan 24 22:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19179 for freebsd-scsi-outgoing; Sat, 24 Jan 1998 22:58:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19174 for ; Sat, 24 Jan 1998 22:58:48 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA23323; Sat, 24 Jan 1998 23:56:08 -0700 (MST) Date: Sat, 24 Jan 1998 23:56:08 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801250656.XAA23323@narnia.plutotech.com> To: Donald Burr cc: scsi@FreeBSD.ORG Subject: Re: Minor annoyances with ZIP Plus Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>I just got a IOMega ZIP Plus and am using it with an Adaptec 1522(AIC6360, >>aic0). It works fine in Win95, and fine in FreeBSD for the most part, >>other than some rather annoying error messages when trying to use it for >>various things. Any time I mount/umount a disk, change it, and do the >>same again (or even use mtools). You'll notice an error when probing the >>drive attached to aic0 and all the errors at the bottom (which occur when >>I try to use it after changing disks): > > Don't worry; these errors are "normal". Well, as "normal" as Iomega SCSI > devices get, anyway. Apparently Iomega subscribes to some "weird", > non-standard variant of SCSI, in that their devices do not support certain > SCSI commands mandated by the SCSI specification, specifically, those SCSI > commansd that ask a device to specify its geometry (size, # > heads/sectors/etc.). When presented with this anomalous behavior, the > FreeBSD driver guesses the device's geometry, and so everything still > works. This isn't the case. FreeBSD was being silly in asking for the optional, rigid geometry page, which the IOMega guys chose not to implement. Since FreeBSD stopped using physical geometry to "optimize" disk I/O (which doesn't work on the ZBR drives of today), asking for the rigid geometry wasn't buying us anything and the code was recently changed to use the information returned by the Read Capacity command instead. -- Justin