From owner-freebsd-scsi Sun Nov 1 03:01:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA13763 for freebsd-scsi-outgoing; Sun, 1 Nov 1998 03:01:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA13756 for ; Sun, 1 Nov 1998 03:01:41 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id NAA09245; Sun, 1 Nov 1998 13:01:34 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id NAA20747; Sun, 1 Nov 1998 13:01:35 +0200 (EET) (envelope-from vallo) Message-ID: <19981101130135.A20727@matti.ee> Date: Sun, 1 Nov 1998 13:01:35 +0200 From: Vallo Kallaste To: dg@root.com, "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7895 and 20.0MB/s transfers Reply-To: vallo@matti.ee References: <199811010225.TAA27464@panzer.plutotech.com> <199811010415.UAA02212@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811010415.UAA02212@implode.root.com>; from David Greenman on Sat, Oct 31, 1998 at 08:15:17PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Greenman wrote: > >Vallo Kallaste wrote... > >> I purchased new motherboard recently which have onboard AIC-7895P > >> chip. All is well but dmesg says that I have 20MB/s transfers only. > >> When working with old ncr controller I have 40MB/s transfers. Some > >> bits from dmesg: > ... > >Well, I'll ask the obvious question: Is support for Ultra SCSI speeds > >enabled in the Adaptec BIOS? (ctrl-A when you boot the machine) > > Hi, Ken. I'm having the same problem here with a new Tyan 1836DLUAN. > Same deal - 7895 chip on the motherboard and an Ultra-2 (LVD) Seagate > Cheetah is probing at 10Mhz rather than 40Mhz. On boot -v, it reports: *** I purchased exactly same motherboard, Tyan 1836DLUAN. FYI. Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 1 03:32:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19984 for freebsd-scsi-outgoing; Sun, 1 Nov 1998 03:32:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19969 for ; Sun, 1 Nov 1998 03:32:34 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id NAA10184; Sun, 1 Nov 1998 13:32:27 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id NAA00272; Sun, 1 Nov 1998 13:32:28 +0200 (EET) (envelope-from vallo) Message-ID: <19981101133228.A259@matti.ee> Date: Sun, 1 Nov 1998 13:32:28 +0200 From: Vallo Kallaste To: dg@root.com, "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7895 and 20.0MB/s transfers Reply-To: vallo@matti.ee References: <199811010225.TAA27464@panzer.plutotech.com> <199811010415.UAA02212@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811010415.UAA02212@implode.root.com>; from David Greenman on Sat, Oct 31, 1998 at 08:15:17PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Greenman wrote: > Hi, Ken. I'm having the same problem here with a new Tyan 1836DLUAN. > Same deal - 7895 chip on the motherboard and an Ultra-2 (LVD) Seagate > Cheetah is probing at 10Mhz rather than 40Mhz. On boot -v, it reports: > > (ahc0 scrolled out of the message buffer, but is identical to ahc1) Here is my boot -v. 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: Sun Nov 1 13:21:53 EET 1998 root@myhakas.matti.ee:/usr/src/sys/compile/Myhakas_SMP Calibrating clock(s) ... TSC clock: 400868891 Hz, i8254 clock: 1193062 Hz Press a key on the console to abort clock calibration Calibrating clock(s) ... TSC clock: 400871046 Hz, i8254 clock: 1193069 Hz Timecounter "i8254" frequency 1193062 Hz CPU: Pentium II (quarter-micron) (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002a1000 - 0x03ff5fff, 64311296 bytes (15701 pages) avail memory = 62533632 (61068K 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 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Found BIOS32 Service Directory header at 0xf00fdb50 Entry = 0xfdb60 (0xf00fdb60) Rev = 0 Len = 1 PCI BIOS entry at 0xdb81 SMIBIOS header at 0xf00f0080 Version 2.1 Table at 0xf0770, 33 entries, 1068 bytes, largest entry 75 bytes DMI header at 0xf00f0090 Version 2.1 Table at 0xf0770, 33 entries, 1068 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7540 SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x71a0, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base f8000000, size 26 chip0: rev 0x00 on pci0.0.0 found-> vendor=0x8086, dev=0x71a1, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x00 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x02 on pci0.7.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=255 chip3: rev 0x01 int d irq 255 on pci0.7.2 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip4: rev 0x02 on pci0.7.3 found-> vendor=0x1011, dev=0x0024, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2 secondarybus=2 chip5: rev 0x03 on pci0.16.0 Freeing (NOT implemented) redirected ISA irq 11. found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[0]: type 3, range 32, base fc4ff000, size 12 map[1]: type 4, range 32, base 0000ef40, size 5 map[2]: type 1, range 32, base fea00000, size 20 fxp0: rev 0x05 int a irq 19 on pci0.17.0 fxp0: Ethernet address 00:e0:81:10:18:e0 bpf: fxp0 attached Freeing (NOT implemented) redirected ISA irq 10. found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 4, range 32, base 0000e000, size 8 map[1]: type 1, range 32, base febfd000, size 12 ahc0: rev 0x04 int a irq 16 on pci0.18.0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable not present, internal 68 cable not present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: High byte termination Enabled ahc0: Low byte termination Enabled ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Resetting Channel A ahc0: Downloading Sequencer Program... 384 instructions downloaded Freeing (NOT implemented) redirected ISA irq 10. found-> vendor=0x9004, dev=0x7895, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=16 map[0]: type 4, range 32, base 0000e400, size 8 map[1]: type 1, range 32, base febfe000, size 12 ahc1: rev 0x04 int b irq 16 on pci0.18.1 using shared irq16. ahc1: Reading SEEPROM...done. ahc1: internal 50 cable not present, internal 68 cable not present ahc1: external cable not present ahc1: BIOS eeprom is present ahc1: High byte termination Enabled ahc1: Low byte termination Enabled ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: Resetting Channel B ahc1: Downloading Sequencer Program... 384 instructions downloaded Freeing (NOT implemented) redirected ISA irq 10. found-> vendor=0x1000, dev=0x000f, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 4, range 32, base 0000ee00, size 8 map[1]: type 1, range 32, base febfcf00, size 8 map[2]: type 1, range 32, base febfb000, size 12 ncr0: rev 0x03 int a irq 16 on pci0.19.0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM found-> vendor=0x1002, dev=0x4755, revid=0x9a class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base fd000000, size 24 map[1]: type 4, range 32, base 0000e800, size 8 map[2]: type 1, range 32, base febff000, size 12 vga0: rev 0x9a on pci0.20.0 Probing for devices on PCI bus 1: Probing for devices on PCI bus 2: Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x00000001, type 0xf0008c0e Called nullpnp_probe with tag 0x00000001, type 0x2fb0d041 port 0x0220 0x0330 0x0388 0x0000 irq 5:0 drq 1:3 en 1 port 0x0220 0x0330 0x0388 0x0000 irq 5:0 drq 1:3 en 1 pcm1 (SB16pnp sn 0xffffffff) at 0x220-0x22f irq 5 drq 1 flags 0x13 on isa Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0xf9 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c06cc, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 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 sc0: the current keyboard controller command byte 0065 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles, flags=0x0> psm0: current command byte:0065 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 90 03 3c psm: status 90 03 3c psm: status 90 03 3c psm: status 00 00 0a psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard 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 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) device at 0x220 already attached as unit 1 pcm0 not found ppc: parallel port found at 0x378 ppc0: EPP SPP ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface imasks: bio c8000040, tty c30010ba, net c6080000 SMP: enabled INTs: 1, 3, 4, 5, 6, 7, 12, 16, 19, apic_imen: 0x00f6ef05 BIOS Geometries: 0:0229fe3f 0..553=554 cylinders, 0..254=255 heads, 1..63=63 sectors 1:0229fe3f 0..553=554 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 bpf: tun0 attached bpf: tun1 attached bpf: lo0 attached Waiting 8 seconds for SCSI devices to settle (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. ncr0: restart (scsi reset). SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff ahc0: Selection Timeout on A:0. 1 SCBs aborted ahc1: Selection Timeout on A:0. 1 SCBs aborted ahc0: Selection Timeout on A:1. 1 SCBs aborted ahc1: Selection Timeout on A:1. 1 SCBs aborted ahc0: Selection Timeout on A:2. 1 SCBs aborted ahc1: Selection Timeout on A:2. 1 SCBs aborted ahc0: Selection Timeout on A:3. 1 SCBs aborted ahc1: Selection Timeout on A:3. 1 SCBs aborted ahc0: Selection Timeout on A:4. 1 SCBs aborted ahc1: Selection Timeout on A:4. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc1: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc1: Selection Timeout on A:8. 1 SCBs aborted (probe30:ncr0:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe30:ncr0:0:0:0): ILLEGAL REQUEST asc:24,0 (probe30:ncr0:0:0:0): Invalid field in CDB sks:c8,1 ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc1: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc1: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc1: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc1: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc1: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc1: Selection Timeout on A:14. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted ahc1: Selection Timeout on A:15. 1 SCBs aborted ahc0: target 6 using 16bit transfers ahc1: target 6 using 16bit transfers ahc0: target 6 synchronous at 10.0MHz, offset = 0x8 ahc1: target 6 synchronous at 10.0MHz, offset = 0x8 pass0 at ahc0 bus 0 target 6 lun 0 pass0: Fixed Direct Access SCSI2 device pass0: Serial Number 194803610366 pass0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled pass1 at ahc1 bus 0 target 6 lun 0 pass1: Fixed Direct Access SCSI2 device pass1: Serial Number 194803611856 pass1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled pass2 at ncr0 bus 0 target 0 lun 0 pass2: Removable CD-ROM SCSI2 device pass2: 10.0MB/s transfers (10.0MHz, offset 16) da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number 194803610366 da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc1 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number 194803611856 da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) Considering FFS root f/s. changing root device to da0s1a (cd0:ncr0:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ncr0:0:0:0): NOT READY asc:3a,0 (cd0:ncr0:0:0:0): Medium not present cd0 at ncr0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present da0s1: type 0xa5, start 63, end = 8905868, size 8905806 : OK da1s1: type 0xa5, start 63, end = 8905868, size 8905806 : OK da1s1: type 0xa5, start 63, end = 8905868, size 8905806 : OK da1s1: type 0xa5, start 63, end = 8905868, size 8905806 : OK Why the ahc probe says that I don't have either type of cables present ? Surely I have two of them :-) Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 1 05:43:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08761 for freebsd-scsi-outgoing; Sun, 1 Nov 1998 05:43:30 -0800 (PST) (envelope-from owner-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 FAA08753 for ; Sun, 1 Nov 1998 05:43:27 -0800 (PST) (envelope-from xroot@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 FAA09108; Sun, 1 Nov 1998 05:44:32 -0800 (PST) Message-Id: <199811011344.FAA09108@implode.root.com> To: vallo@matti.ee cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7895 and 20.0MB/s transfers In-reply-to: Your message of "Sun, 01 Nov 1998 05:09:49 +0200." <19981101050949.A291@matti.ee> From: David Greenman Reply-To: dg@root.com Date: Sun, 01 Nov 1998 05:44:32 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I purchased new motherboard recently which have onboard AIC-7895P >chip. All is well but dmesg says that I have 20MB/s transfers only. >When working with old ncr controller I have 40MB/s transfers. Some >bits from dmesg: BTW, I just changed the Adaptec BIOS setting for the maximum negotiation speed to 20MB/sec, rebooted, and then changed it back to 40MB/sec, and now FreeBSD sees the drive okay at 40MB/sec. Strange. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 1 08:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28364 for freebsd-scsi-outgoing; Sun, 1 Nov 1998 08:27:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28351 for ; Sun, 1 Nov 1998 08:27:44 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id SAA19703; Sun, 1 Nov 1998 18:27:37 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id SAA00276; Sun, 1 Nov 1998 18:27:37 +0200 (EET) (envelope-from vallo) Message-ID: <19981101182737.A259@matti.ee> Date: Sun, 1 Nov 1998 18:27:37 +0200 From: Vallo Kallaste To: dg@root.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC-7895 and 20.0MB/s transfers Reply-To: vallo@matti.ee References: <19981101050949.A291@matti.ee> <199811011344.FAA09108@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811011344.FAA09108@implode.root.com>; from David Greenman on Sun, Nov 01, 1998 at 05:44:32AM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Greenman wrote: > BTW, I just changed the Adaptec BIOS setting for the maximum negotiation > speed to 20MB/sec, rebooted, and then changed it back to 40MB/sec, and now > FreeBSD sees the drive okay at 40MB/sec. Strange. Well, I see the same results as you. Thanks for the note. Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 1 15:32:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25319 for freebsd-scsi-outgoing; Sun, 1 Nov 1998 15:32:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA25314 for ; Sun, 1 Nov 1998 15:32:43 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0za6z1-0001pm-00; Sun, 1 Nov 1998 16:32:31 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id QAA07044; Sun, 1 Nov 1998 16:32:49 -0700 (MST) Message-Id: <199811012332.QAA07044@harmony.village.org> To: Joao Carlos Mendes Luis Subject: Re: CAM: aha at 0x334 -> not found Cc: scsi@FreeBSD.ORG In-reply-to: Your message of "Sat, 31 Oct 1998 12:53:45 -0200." <199810311453.MAA09850@roma.coe.ufrj.br> References: <199810311453.MAA09850@roma.coe.ufrj.br> Date: Sun, 01 Nov 1998 16:32:48 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199810311453.MAA09850@roma.coe.ufrj.br> Joao Carlos Mendes Luis writes: : I could solve this by rearranging the order of valid isa addresses : at the aha driver. The code seems to need them in reverse numeric : order. : : struct aha_isa_port aha_isa_ports[] = : { : { 0x334, 0 }, : { 0x330, 0 }, : { 0x234, 0 }, : { 0x230, 0 }, : { 0x134, 0 }, : { 0x130, 0 } : }; Hmmm. Looks like a problem to me. I'll commit the change. Looks like bt.c (at least in my copy) suffers from the same problem. Not surprising because I stole most of the code for aha from bt. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 2 06:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22182 for freebsd-scsi-outgoing; Mon, 2 Nov 1998 06:46:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www.whyy.org (www.whyy.org [207.245.67.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA22108 for ; Mon, 2 Nov 1998 06:46:08 -0800 (PST) (envelope-from jeffe@gccomm.net) Received: from console-1 (tvmaster1.whyy.org [207.245.66.48]) by www.whyy.org (8.8.5/8.7.3) with SMTP id JAA24293 for ; Mon, 2 Nov 1998 09:46:00 -0500 (EST) Message-ID: <001101be066f$81c39e50$3042f5cf@console-1.whyy.org> From: "jeff" To: "freebsd scsi" Subject: adaptec 1522 port Date: Mon, 2 Nov 1998 09:45:58 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello All, Before I start porting the driver code for the 1522, has anyone done it yet. And is there someone willing to keep me sane during the process, as I haven't done any porting YET. Thanks Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 2 07:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24511 for freebsd-scsi-outgoing; Mon, 2 Nov 1998 07:03:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www.whyy.org (www.whyy.org [207.245.67.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24505 for ; Mon, 2 Nov 1998 07:03:17 -0800 (PST) (envelope-from jeffe@gccomm.net) Received: from console-1 (tvmaster1.whyy.org [207.245.66.48]) by www.whyy.org (8.8.5/8.7.3) with SMTP id KAA24501 for ; Mon, 2 Nov 1998 10:03:10 -0500 (EST) Message-ID: <001a01be0671$e7fa1530$3042f5cf@console-1.whyy.org> From: "jeff" To: "freebsd scsi" Subject: Re: adaptec 1522 port Date: Mon, 2 Nov 1998 10:03:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Already it is a bad day.. This port would be four 3.0 -----Original Message----- From: jeff To: freebsd scsi Date: Monday, November 02, 1998 9:55 AM Subject: adaptec 1522 port Hello All, Before I start porting the driver code for the 1522, has anyone done it yet. And is there someone willing to keep me sane during the process, as I haven't done any porting YET. Thanks Jeff 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 Mon Nov 2 11:33:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22501 for freebsd-scsi-outgoing; Mon, 2 Nov 1998 11:33:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Relay.Romania.EU.net (main.RO.EU.net [193.226.128.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22491 for ; Mon, 2 Nov 1998 11:33:33 -0800 (PST) (envelope-from Liviu.Ionescu@Romania.EU.net) Received: from ilg-mobile (ilg-home.RO.EU.net [193.226.149.3]) by Relay.Romania.EU.net (8.9.1/8.9.1/EUI_RO-AntiSpam) with SMTP id VAA22492 for ; Mon, 2 Nov 1998 21:32:39 +0200 (EET) Reply-To: From: "Liviu Ionescu" To: Subject: BIOS inits? (was RE: AIC-7895 and 20.0MB/s transfers) Date: Mon, 2 Nov 1998 21:32:44 +0200 Message-ID: <000001be0697$9198ef60$0395e2c1@ilg-mobile> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199811011344.FAA09108@implode.root.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > BTW, I just changed the Adaptec BIOS setting for the > maximum negotiation > speed to 20MB/sec, rebooted, and then changed it back to > 40MB/sec, and now > FreeBSD sees the drive okay at 40MB/sec. Strange. (not as a contribution to this thread, but more as a general issue) what do you think, is it safe to rely on BIOS inits/board-status for IO device settings? wouldn't it be better to completely ignore them and set everything at driver init time or, when necessary, at rc startup time? in this case everything will be under our control, and subtle interactions with BIOS or even other operating systems running accidentally on the same machine will be minimized. as a side effect remote administration will also be improved (our servers have 'faceless' serial consoles only, and I would really like not to have to plug in any monitor/keyboard to configure them...) regards, Liviu Ionescu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 2 11:42:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23402 for freebsd-scsi-outgoing; Mon, 2 Nov 1998 11:42:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23397 for ; Mon, 2 Nov 1998 11:42:35 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id MAA06020; Mon, 2 Nov 1998 12:41:57 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811021941.MAA06020@panzer.plutotech.com> Subject: Re: adaptec 1522 port In-Reply-To: <001101be066f$81c39e50$3042f5cf@console-1.whyy.org> from jeff at "Nov 2, 98 09:45:58 am" To: jeffe@gccomm.net (jeff) Date: Mon, 2 Nov 1998 12:41:57 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org jeff wrote... > Hello All, > Before I start porting the driver code for the 1522, has anyone done it yet. > And is there someone willing to keep me sane during the process, as I > haven't done any porting YET. Thanks Jeff You should talk to Brian Beattie . He has been working on a CAM version of the aic6260/6360 driver, although I'm not sure what state the driver is in right now. 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 Mon Nov 2 13:06:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04334 for freebsd-scsi-outgoing; Mon, 2 Nov 1998 13:06:17 -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 NAA04324 for ; Mon, 2 Nov 1998 13:06:14 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id NAA14899; Mon, 2 Nov 1998 13:59:11 -0700 (MST) Date: Mon, 2 Nov 1998 13:59:11 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811022059.NAA14899@narnia.plutotech.com> To: cc: scsi@FreeBSD.ORG Subject: Re: BIOS inits? (was RE: AIC-7895 and 20.0MB/s transfers) X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <000001be0697$9198ef60$0395e2c1@ilg-mobile> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <000001be0697$9198ef60$0395e2c1@ilg-mobile> you wrote: >> BTW, I just changed the Adaptec BIOS setting for the >> maximum negotiation >> speed to 20MB/sec, rebooted, and then changed it back to >> 40MB/sec, and now >> FreeBSD sees the drive okay at 40MB/sec. Strange. > > (not as a contribution to this thread, but more as a general issue) > > what do you think, is it safe to rely on BIOS inits/board-status for IO > device settings? wouldn't it be better to completely ignore them and set > everything at driver init time or, when necessary, at rc startup time? In this case, we are talking about a serial eeprom. I would not expect the values in the eeprom to change unless the user enters SCSI-Select again. Unfortunately, since I do not have a serial eeprom dump with the state of the eeprom before and after this change, I cannot determine exactly what was wrong initially. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 3 00:36:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07491 for freebsd-scsi-outgoing; Tue, 3 Nov 1998 00:36:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07486 for ; Tue, 3 Nov 1998 00:36:27 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (vallo@myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id KAA18503 for ; Tue, 3 Nov 1998 10:36:13 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id KAA03501 for freebsd-scsi@freebsd.org; Tue, 3 Nov 1998 10:36:19 +0200 (EET) (envelope-from vallo) Message-ID: <19981103103619.C3354@matti.ee> Date: Tue, 3 Nov 1998 10:36:19 +0200 From: Vallo Kallaste To: freebsd-scsi@FreeBSD.ORG Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 03:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07753 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 03:47:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07748 for ; Wed, 4 Nov 1998 03:47:09 -0800 (PST) (envelope-from jorn-morten.innselset@telia.no) Received: from d1o201.telia.com (root@d1o201.telia.com [195.204.216.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id MAA02040 for ; Wed, 4 Nov 1998 12:46:55 +0100 (CET) Received: from 192.168.0.2 (pc172s117r1.jancomulti.com [195.139.117.172]) by d1o201.telia.com (8.8.8/8.8.5) with SMTP id MAA24708 for ; Wed, 4 Nov 1998 12:46:49 +0100 (MET) Date: Wed, 4 Nov 1998 12:45:56 +0100 From: vibes@hipdrome.org Subject: 3.0-CURRENT + ccd To: freebsd-scsi@FreeBSD.ORG Message-ID: In-Reply-To: <001101be066f$81c39e50$3042f5cf_console-1.whyy.org@ns.sol.net> X-Mailer: MicroPlanet Gravity v2.10 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are there any known problems with ccd in current? All seems dandy until I try to newfs the ccd-volume - then it just stops after 4 or 5 steps in the news-process - and hangs the machine. Tried with SMP and no- SMP configured kernels. I have tried this on three, two and just one disk - on two separate Adaptec controllers. I could provide more information for diagnostics, but if there are known problems with ccd at this stage I'd rather just wait for an update. -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 06:03:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27009 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 06:03:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26993 for ; Wed, 4 Nov 1998 06:03:37 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA03002; Wed, 4 Nov 1998 09:03:00 -0500 (EST) Date: Wed, 4 Nov 1998 09:03:00 -0500 (EST) From: John Fieber To: John Hay cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related In-Reply-To: <199810041601.SAA02050@zibbi.mikom.csir.co.za> 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 Sun, 4 Oct 1998, John Hay wrote: > System is a dual 266MHz PII with Asus motherboard with Adaptec 7880 on > board and a Seagate ST34572N as drive 0 and a Conner CFP4207S as drive 2. > Everything is on the Seagate except /usr/obj which is symlinked to the > Conner. It is running a very up to date -current and using softupdates > on all partitions. > > The machine will panic sometimes during a "make world" especially with a > high -j value, but it panics in such a way that it does not leave a dump. I encounter similar problems, though not specifically through "make world" disk activity. > da1: Fixed Direct Access SCSI2 device Mine is , on an ASUS SC200 (ncr) controller. System is 3.0-RELEASE plus a kernel from around Nov1. Your patch seems to do the trick for my system well and should probably be committed. I'm just curious how you arrived at 8 and 24 for the tags? -john > --------------------------------------------------------------------------- > Index: sys/cam/cam_xpt.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/cam_xpt.c,v > retrieving revision 1.15 > diff -u -r1.15 cam_xpt.c > --- cam_xpt.c 1998/10/02 21:00:50 1.15 > +++ cam_xpt.c 1998/10/04 06:47:44 > @@ -233,12 +233,18 @@ > #endif > }; > > +static const char conner[] = "CONNER"; > static const char quantum[] = "QUANTUM"; > static const char sony[] = "SONY"; > static const char west_digital[] = "WDIGTL"; > > static struct xpt_quirk_entry xpt_quirk_table[] = > { > + { > + /* Sometimes gets stuck */ > + { T_DIRECT, SIP_MEDIA_FIXED, conner, "CFP4207S*", "*" }, > + /*quirks*/0, /*mintags*/8, /*maxtags*/24 > + }, > { > /* Reports QUEUE FULL for temporary resource shortages */ > { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100*", "*" }, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 09:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23366 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 09:02:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from elit.cinet.cn.ua (elit.cinet.cn.ua [193.125.84.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23245 for ; Wed, 4 Nov 1998 09:01:41 -0800 (PST) (envelope-from dodo@elit.cinet.cn.ua) Received: (from root@localhost) by elit.cinet.cn.ua (8.8.8/8.8.8) id TAA22486 for freebsd-scsi@freebsd.org; Wed, 4 Nov 1998 19:01:10 +0200 (EET) To: freebsd-scsi@FreeBSD.ORG Message-ID: Organization: Joint Stock Company ISP "CINET" From: "Vsevolod V. Denisenko" Date: Wed, 4 Nov 98 19:01:10 +0200 X-Mailer: BML [UNIX Beauty Mail v.1.39] Content-Type: text/plain: charset=koi8-r Subject: 3.0 Release and SCSI installatin problem Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Would you like to be so kind to explain something? Today I have tried to install FreeBSD 3.0 on my jade :) with AMD-K5-PR100/100 Mhz/RAM 16M and SCSI-controller NCR 53C810 and simple Seagate 500Mb hard drive (SCSI of course). I have exploited 2.2.6 Release before without any problems. There were no problems during installation of 2.2.6 Release. But this time 3.0 Release brought me some surprise:( I see all my hardware correctly after boot, even SCSI-controller, "ncr0: rev 0x02 int a irq 14 on pci0.13.0" but then receive the following messages: "Waiting 15 seconds for SCSI devices to settle" "ncr0: SCSI phase error fixup: CCB already dequeued (0xf05f2200)" My jade still wait and die. So, what's your comments and advises? Best regards, Vsevolod Denisenko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 09:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24906 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 09:10:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from elit.cinet.cn.ua (elit.cinet.cn.ua [193.125.84.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24863 for ; Wed, 4 Nov 1998 09:10:11 -0800 (PST) (envelope-from dodo@elit.cinet.cn.ua) Received: (from root@localhost) by elit.cinet.cn.ua (8.8.8/8.8.8) id TAA22661 for freebsd-scsi@freebsd.org; Wed, 4 Nov 1998 19:08:28 +0200 (EET) To: freebsd-scsi@FreeBSD.ORG Message-ID: Organization: Joint Stock Company ISP "CINET" From: "Vsevolod V. Denisenko" Date: Wed, 4 Nov 98 19:08:28 +0200 X-Mailer: BML [UNIX Beauty Mail v.1.39] Content-Type: text/plain: charset=koi8-r Subject: 3.0 Release and SCSI installation problem Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Excuse me for misprint. Previous message contain string: "simple Seagate 500Mb hard drive (SCSI of course)." See corrected message below.... Would you like to be so kind to explain something? Today I have tried to install FreeBSD 3.0 on my jade :) with AMD-K5-PR100/100 Mhz/RAM 16M and SCSI-controller NCR 53C810 and simple Quantum 500Mb hard drive (SCSI of course). I have exploited 2.2.6 Release before without any problems. There were no problems during installation of 2.2.6 Release. But this time 3.0 Release brought me some surprise:( I see all my hardware correctly after boot, even SCSI-controller, "ncr0: rev 0x02 int a irq 14 on pci0.13.0" but then receive the following messages: "Waiting 15 seconds for SCSI devices to settle" "ncr0: SCSI phase error fixup: CCB already dequeued (0xf05f2200)" My jade still wait and die. So, what's your comments and advises? Best regards, Vsevolod Denisenko. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 10:05:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03968 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 10:05:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03947; Wed, 4 Nov 1998 10:05:09 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id NAA05164; Wed, 4 Nov 1998 13:04:00 -0500 (EST) (envelope-from larry) Date: Wed, 4 Nov 1998 13:04:00 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: 3.0-Release breaks pt0 (scanner) working under Aug. current Message-ID: <19981104130400.A5152@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just upgraded from an August 3.0-current (non-CAMed) to 3.0-Release (CAMed). I run xvscan to operate my HP ScanJet 6100C using the /dev/pt0 driver, which works great on the August 3.0-current system. However, on 3.0-Release, the software doesn't recognize the scanner on /dev/pt0. I'm jumping back and froth between the new and old kernels. Here are my log entries while booting up. Is this a known problem? What other information can I provide to track this down? Thank you. Non-CAM'd August 3.0-current: Nov 4 12:53:35 lsmarso /kernel.old: pt0 at scbus0 target 5 lun 0 Nov 4 12:53:35 lsmarso /kernel.old: pt0: type 3 fixed SCSI 2 Nov 4 12:53:35 lsmarso /kernel.old: pt0: Processor ////////////// CAM'd 3.0-release: Nov 4 12:10:39 lsmarso /kernel: pt0 at ahc0 bus 0 target 5 lun 0 Nov 4 12:10:39 lsmarso /kernel: pt0: Fixed Processor SCSI2 device Nov 4 12:10:39 lsmarso /kernel: pt0: 3.300MB/s transfers Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 10:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09057 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 10:44:22 -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 KAA09051 for ; Wed, 4 Nov 1998 10:44:21 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id LAA24907; Wed, 4 Nov 1998 11:37:16 -0700 (MST) Date: Wed, 4 Nov 1998 11:37:16 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811041837.LAA24907@narnia.plutotech.com> To: "Larry S. Marso" cc: scsi@FreeBSD.ORG Subject: Re: 3.0-Release breaks pt0 (scanner) working under Aug. current X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19981104130400.A5152@marso.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19981104130400.A5152@marso.com> you wrote: > I just upgraded from an August 3.0-current (non-CAMed) to 3.0-Release > (CAMed). > > I run xvscan to operate my HP ScanJet 6100C using the /dev/pt0 driver, > which works great on the August 3.0-current system. > > However, on 3.0-Release, the software doesn't recognize the scanner on > /dev/pt0. What does, "doesn't recognize" mean? It can't open the device? I/O to the device fails? The software interface to /dev/pt0 did not change with CAM, but several other interfaces of the SCSI subsystem did change and perhaps xvscan needs to be taught about these changes. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 13:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04844 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 13:06:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04839 for ; Wed, 4 Nov 1998 13:06:04 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id QAA05966; Wed, 4 Nov 1998 16:06:23 -0500 (EST) (envelope-from larry) Date: Wed, 4 Nov 1998 16:06:23 -0500 From: "Larry S. Marso" To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0-Release breaks pt0 (scanner) working under Aug. current Message-ID: <19981104160622.B5920@marso.com> References: <19981104130400.A5152@marso.com> <199811041837.LAA24907@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.94.13i In-Reply-To: <199811041837.LAA24907@narnia.plutotech.com>; from Justin T. Gibbs on Wed, Nov 04, 1998 at 11:37:16AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From the manual, configuring xvscan involves the following: //////// The FreeBSD version of XVScan uses the `pt' (processor type) device driver in your kernel. XVScan looks for the scanner on /dev/scanjet. On FreeBSD systems, this should be a copy of the appropriate /dev/pt[0-9] device: Note: FreeBSD SYSTEMS ONLY freebsd# ls -l /dev/pt[0-9] crw------- 1 root wheel 61, 0 Jan 13 10:48 /dev/pt0 crw------- 2 root wheel 61, 1 Jan 13 10:48 /dev/pt1 crw------- 1 root wheel 61, 2 Jan 13 10:48 /dev/pt2 freebsd# mknod /dev/scanjet c 61 0 freebsd# chmod 666 /dev/scanjet freebsd# ls -l /dev/scanjet crw-rw-rw- 1 root wheel 61, 1 Jan 13 10:48 scanjet Note that the /dev/scanjet device is readable and writable by everyone. Scanner users will require read and write permissions to this device file. /////// this done, pre-CAM, you get the following output from the Install script: ////// This ScanJet device file already exists... not created /dev/scanjet: Vendor: 'HP ' Product: 'C2520A' Type: 3 (Scanner) Successfully opened scanner device '/dev/pt0' /dev/pt0: Vendor: 'HP ' Product: 'C2520A' Type: 3 (Scanner) ////// After installing 3.0-release, I get: ////// Device on '/dev/scanjet' is not an HP. Found ' |Ø¿ï'. Scanner device disabled to prevent possible overwrite. /dev/scanjet: Vendor: '' Product: '|Ø¿ï' Type: 2 *** Device file was NOT created ////// On Wed, Nov 04, 1998 at 11:37:16AM -0700, Justin T. Gibbs wrote: > In article <19981104130400.A5152@marso.com> you wrote: > > I just upgraded from an August 3.0-current (non-CAMed) to 3.0-Release > > (CAMed). > > > > I run xvscan to operate my HP ScanJet 6100C using the /dev/pt0 driver, > > which works great on the August 3.0-current system. > > > > However, on 3.0-Release, the software doesn't recognize the scanner on > > /dev/pt0. > > What does, "doesn't recognize" mean? It can't open the device? I/O > to the device fails? > > The software interface to /dev/pt0 did not change with CAM, but several > other interfaces of the SCSI subsystem did change and perhaps xvscan > needs to be taught about these changes. > > -- > Justin > > 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 Nov 4 13:23:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07858 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 13:23:35 -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 NAA07849 for ; Wed, 4 Nov 1998 13:23: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.8.7/8.8.5) with ESMTP id OAA12771; Wed, 4 Nov 1998 14:23:18 -0700 (MST) Message-Id: <199811042123.OAA12771@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Larry S. Marso" cc: "Justin T. Gibbs" , freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0-Release breaks pt0 (scanner) working under Aug. current In-reply-to: Your message of "Wed, 04 Nov 1998 16:06:23 EST." <19981104160622.B5920@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 04 Nov 1998 14:16:30 -0700 From: "Justin T. Gibbs" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA07854 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >this done, pre-CAM, you get the following output from the Install script: > >////// > This ScanJet device file already exists... not created > /dev/scanjet: Vendor: 'HP ' Product: 'C2520A' Type: 3 (Scanner) > Successfully opened scanner device '/dev/pt0' > /dev/pt0: Vendor: 'HP ' Product: 'C2520A' Type: 3 (Scanner) It looks like XVScan uses the old pass-thru driver interface. This has been completely changed for CAM and the software will have to be modified to deal with this change. If you have access to the source, you can use the 3.0CAM cdrecord and xmcd ports as a guide for how to use the new interface. I also believe that SANE has been ported to CAM which is another scanner package. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 17:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22536 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 17:50:44 -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 RAA22529 for ; Wed, 4 Nov 1998 17:50:40 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA06113; Thu, 5 Nov 1998 12:20:29 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA06871; Thu, 5 Nov 1998 12:20:29 +1030 (CST) Message-ID: <19981105122029.A784@freebie.lemis.com> Date: Thu, 5 Nov 1998 12:20:29 +1030 From: Greg Lehey To: John Fieber , John Hay Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related References: <199810041601.SAA02050@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Fieber on Wed, Nov 04, 1998 at 09:03:00AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 4 November 1998 at 9:03:00 -0500, John Fieber wrote: > On Sun, 4 Oct 1998, John Hay wrote: > >> System is a dual 266MHz PII with Asus motherboard with Adaptec 7880 on >> board and a Seagate ST34572N as drive 0 and a Conner CFP4207S as drive 2. >> Everything is on the Seagate except /usr/obj which is symlinked to the >> Conner. It is running a very up to date -current and using softupdates >> on all partitions. >> >> The machine will panic sometimes during a "make world" especially with a >> high -j value, but it panics in such a way that it does not leave a dump. > > I encounter similar problems, though not specifically through > "make world" disk activity. > >> da1: Fixed Direct Access SCSI2 device > > Mine is , on an ASUS SC200 (ncr) > controller. System is 3.0-RELEASE plus a kernel from around > Nov1. Your patch seems to do the trick for my system well and > should probably be committed. Interesting. I have: da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 3.300MB/s transfers, Tagged Queueing Enabled (See, John, mine's bigger than yours again :-) I haven't had any problems at all with this drive, though I haven't used it to make world. Does anybody think I should? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 18:38:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00463 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 18:38:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00416 for ; Wed, 4 Nov 1998 18:37:59 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id VAA14843; Wed, 4 Nov 1998 21:37:25 -0500 (EST) Date: Wed, 4 Nov 1998 21:37:25 -0500 (EST) From: John Fieber To: Greg Lehey cc: John Hay , freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related In-Reply-To: <19981105122029.A784@freebie.lemis.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 Thu, 5 Nov 1998, Greg Lehey wrote: > On Wednesday, 4 November 1998 at 9:03:00 -0500, John Fieber wrote: > > On Sun, 4 Oct 1998, John Hay wrote: > >> The machine will panic sometimes during a "make world" especially with a > >> high -j value, but it panics in such a way that it does not leave a dump. > > > > I encounter similar problems, though not specifically through > > "make world" disk activity. > > > >> da1: Fixed Direct Access SCSI2 device > > > > Mine is , on an ASUS SC200 (ncr) > > Interesting. I have: > > da1: Fixed Direct Access SCSI2 device > > I haven't had any problems at all with this drive, though I haven't > used it to make world. Does anybody think I should? If you can hammer really hard on the drive for a long time without any ill effects, then maybe they fixed the bug by the time 2847 came around. In that case the patch should be tweaked. Alas, we don't know exactly what revision the fix came in at. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 4 22:11:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20652 for freebsd-scsi-outgoing; Wed, 4 Nov 1998 22:11:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20647 for ; Wed, 4 Nov 1998 22:11:52 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id IAA00245; Thu, 5 Nov 1998 08:11:22 +0200 (SAT) From: John Hay Message-Id: <199811050611.IAA00245@zibbi.mikom.csir.co.za> Subject: Re: cam panic... probably tag related In-Reply-To: from John Fieber at "Nov 4, 98 09:03:00 am" To: jfieber@indiana.edu (John Fieber) Date: Thu, 5 Nov 1998 08:11:22 +0200 (SAT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sun, 4 Oct 1998, John Hay wrote: > > > System is a dual 266MHz PII with Asus motherboard with Adaptec 7880 on > > board and a Seagate ST34572N as drive 0 and a Conner CFP4207S as drive 2. > > Everything is on the Seagate except /usr/obj which is symlinked to the > > Conner. It is running a very up to date -current and using softupdates > > on all partitions. > > > > The machine will panic sometimes during a "make world" especially with a > > high -j value, but it panics in such a way that it does not leave a dump. > > I encounter similar problems, though not specifically through > "make world" disk activity. > > > da1: Fixed Direct Access SCSI2 device > > Mine is , on an ASUS SC200 (ncr) > controller. System is 3.0-RELEASE plus a kernel from around > Nov1. Your patch seems to do the trick for my system well and > should probably be committed. I'm just curious how you arrived > at 8 and 24 for the tags? > Well I just chose them after seeing that cam would report the "tagged openings" for that drive down to 31, so I just chose it a little smaller. I did get the problem again once and now I'm using 16 instead of 24 and haven't had a problem again. I did 36 "make -j26 world"s in a loop with max tags set to 16 and it seems to be ok. I have also done my usual stuff and haven't had a problem after taking it down to 16. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 5 00:58:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07684 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 00:58:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns.wan (trltech.demon.co.uk [194.222.7.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07662 for ; Thu, 5 Nov 1998 00:58:05 -0800 (PST) (envelope-from richard@jezebel.demon.co.uk) Received: from jezebel.demon.co.uk (rdls.dhcp.sw.wan [192.9.201.75]) by ns.wan (8.8.8/8.8.8) with ESMTP id IAA20822 for ; Thu, 5 Nov 1998 08:57:50 GMT (envelope-from richard@jezebel.demon.co.uk) Message-ID: <3641689A.72B245FB@jezebel.demon.co.uk> Date: Thu, 05 Nov 1998 08:58:02 +0000 From: Richard Smith Organization: http://www.trltech.co.uk X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: ncr0: timeout ccb=0xf0533400 (skip) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [this question was originally posted to -questions] I have a symbios logic v4.0 pci scsi bios pci rev 2.0,2.1 pci-4.03.00 53c875 fast20 wide scsi [which has subsequently been upgraded to 4.11] and a fujitsu M2949E-512 HDD (about 8.5 Gbytes). I am running FreeBSD 2.2.7R and NT 4.0 on the same machine. The disk is split so that NT occupies the lower 4G and FreeBSD occupies the upper 4G (as this was the only way I could get NT to boot), and using your boot manager to switch between the two. Under FreeBSD, the system keeps falling over with a single ncr0: timeout error, nothing else gets written to the screen, and nothing gets written to the message log (as it's on the same disk). The problem usually needs two power cycles to rectify, as the first falls over again during fsck. The problem appears to be pattern sensitive: If I try to tar my mail directory it falls over every time, while othertimes it may stay up all day. Needless to say NT never fails. I have played with cables, checked terminators, searched the mailing lists. I want to advocate FreeBSD for my next project, and I'm prepared to specify different hardware for that project and for my desktop (such as the Adaptec 2940UW - which appears to be popular). What I would like from you is some guidance as to why I appear to be having these problems with the current configuration. I hope you can help, and I hope the I haven't violated too many rules by posting this question here :-) _______________________________________________________________________ Richard Smith Assistant Chief Engineer TRL Technology Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 5 07:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24216 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 07:27:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24207 for ; Thu, 5 Nov 1998 07:27:19 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395301.student.utwente.nl ([130.89.235.121]:13572 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <8187-3477>; Thu, 5 Nov 1998 16:25:18 +0100 Message-ID: <000b01be08d0$4efa5140$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: Subject: .... Illegal request asc:20,0 .... Date: Thu, 5 Nov 1998 16:23:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When I reboot (or halt) my 3.0-RELEASE system, I get the following message: Syncing... 4 4 (da0:ahc0:0:0:0): SYNCHRONIZE CACHE CDB: 35 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:20,0 (da0:ahc0:0:0:0): Invalid command operation code field replaceable unit: 14 System halted... I searched the mailing list archives but I couldn't find anything about the asc:20,0 error (there's plenty about asc:24,0 errors). Can anyone tell me what's up?? Attached below is my dmesg output, please let me know if you need more information... Cheers, Jeroen --------------------------------------------- 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 #8: Thu Nov 5 10:48:54 CET 1998 gelderen@:/usr/src/sys/compile/SERVIX Timecounter "i8254" frequency 1193182 Hz cost 2684 ns Timecounter "TSC" frequency 99716539 Hz cost 153 ns CPU: Pentium/P54C (99.72-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 63041536 (61564K bytes) Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ahc0: rev 0x01 int a irq 5 on pci0.13.0 ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs vga0: rev 0x54 int a irq 11 on pci0.15.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:20:18:72:93:4e, type NE2000 (16 bit) fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround Waiting 10 seconds for SCSI devices to settle da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 1526MB (3125408 512 byte sectors: 255H 63S/T 194C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) --------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 5 13:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02489 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 13:11:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02474 for ; Thu, 5 Nov 1998 13:11:20 -0800 (PST) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id QAA26388; Thu, 5 Nov 1998 16:11:05 -0500 (EST) To: freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0-Release breaks pt0 (scanner) working under Aug. current References: <199811042123.OAA12771@pluto.plutotech.com> X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 05 Nov 1998 16:11:04 -0500 In-Reply-To: "Justin T. Gibbs"'s message of "Wed, 04 Nov 1998 14:16:30 -0700" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" writes: > I also believe that SANE has been ported to CAM which is >another scanner package. Sane 1.0 is in testing now. The changes for CAM have been included, so it should pretty much just work. If you need to get it up and running before 1.0 shows up, I have diffs for 0.74. +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 5 14:29:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11343 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 14:29:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11337 for ; Thu, 5 Nov 1998 14:29:30 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA26636; Thu, 5 Nov 1998 15:29:13 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811052229.PAA26636@panzer.plutotech.com> Subject: Re: .... Illegal request asc:20,0 .... In-Reply-To: <000b01be08d0$4efa5140$1400000a@deskfix.local> from "Jeroen C. van Gelderen" at "Nov 5, 98 04:23:58 pm" To: gelderen@mediaport.org (Jeroen C. van Gelderen) Date: Thu, 5 Nov 1998 15:29:13 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM910304953-26578-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM910304953-26578-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Jeroen C. van Gelderen wrote... > When I reboot (or halt) my 3.0-RELEASE system, I get the following message: > > Syncing... 4 4 > (da0:ahc0:0:0:0): SYNCHRONIZE CACHE CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:ahc0:0:0:0): ILLEGAL REQUEST asc:20,0 > (da0:ahc0:0:0:0): Invalid command operation code field replaceable unit: 14 > System halted... > > I searched the mailing list archives but I couldn't find anything about the > asc:20,0 error (there's plenty about asc:24,0 errors). Can anyone tell me > what's up?? Attached below is my dmesg output, please let me know if you > need more information... [ ... ] > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled > da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) It's a harmless error message. I'm not sure why you're seeing it, though. I've got code in the routine in question (dashutdown()) that explicitly disables printing sense information if the sense key is illegal request. Could you try the attached patch? (for src/sys/cam/scsi/scsi_da.c) It's against -current, but hopefully it'll apply okay to your version of scsi_da.c. Basically, what I want to try to do is get some idea of where the above error message is coming from... If the error message is coming from where it shouldn't be coming from, you'll see something like this before the above error message: dashutdown: printing error message Thanks, Ken -- Kenneth Merry ken@plutotech.com --ELM910304953-26578-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=scsi_da.c.shutdown_test.110598 Content-Description: scsi_da.c.shutdown_test.110598 Content-Transfer-Encoding: 7bit ==== //depot/cam/sys/cam/scsi/scsi_da.c#89 - /usr/home/ken/perforce/cam/sys/cam/scsi/scsi_da.c ==== *** /tmp/tmp.27124.0 Thu Nov 5 15:24:21 1998 --- /usr/home/ken/perforce/cam/sys/cam/scsi/scsi_da.c Thu Nov 5 15:23:45 1998 *************** *** 1537,1544 **** &error_code, &sense_key, &asc, &ascq); ! if (sense_key != SSD_KEY_ILLEGAL_REQUEST) scsi_sense_print(&ccb.csio); } else { xpt_print_path(periph->path); printf("Synchronize cache failed, status " --- 1537,1547 ---- &error_code, &sense_key, &asc, &ascq); ! if (sense_key != SSD_KEY_ILLEGAL_REQUEST) { ! printf("dashutdown: printing error " ! "message\n"); scsi_sense_print(&ccb.csio); + } } else { xpt_print_path(periph->path); printf("Synchronize cache failed, status " --ELM910304953-26578-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 5 14:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13410 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 14:50:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from terra.milkyway.stdio.com (terra.milkyway.stdio.com [204.152.115.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13344 for ; Thu, 5 Nov 1998 14:50:00 -0800 (PST) (envelope-from wilhelm@milkyway.stdio.com) Received: (from wilhelm@localhost) by terra.milkyway.stdio.com (8.9.1/8.9.1) id RAA09611 for freebsd-scsi@freebsd.org; Thu, 5 Nov 1998 17:49:43 -0500 (EST) (envelope-from wilhelm) From: Nick Wilhelm-Olsen Message-Id: <199811052249.RAA09611@terra.milkyway.stdio.com> Subject: SDT-7000 density woes To: freebsd-scsi@FreeBSD.ORG Date: Thu, 5 Nov 1998 17:49:43 -0500 (EST) 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 Hello, I posted this yesterday to freebsd-questions and have gotten no answers and a couple of 'me too's. So I'm reposting here in the hopes that someone will look at this. This same problem has also been seen on a friends system w/ an Archive Python running 3.0-current. I didn't mention it originally, but I am using 120m tapes. I also didn't mention that this worked great with the old non-CAM st tape driver. I am running 3.0-RELEASE on Compaq EISA box with a fairly stock kernel, using an Adaptec 2742 (ahc) for SCSI. I have a Sony SDT-7000 DDS-2 4mm tape drive attached to the system that properly shows up as sa0. ...... ahc0: at 0x4c00-0x4cff irq 11 on eisa0 slot 4 ahc0: aic7770 >= Rev E, Twin Channel, A SCSI Id=7, B SCSI Id=7, primary A, 4/255 SCBs ..... Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 10.0MB/s transfers (10.0MHz, offset 15) My first attempt at dumping to the tape device worked ok, except for the fact that I ran out of tape well before I should have, before writing 2G to the device. I immediately smacked myself for forgeting to set the density to DDS-2 and enable compression (mode 0x24 from mt(1)): # mt -f /dev/nrsa0 density 0x24 mt: /dev/nrsa0: density: invalid argument (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list sks:8f,4 Sure enough, I check the densities that the device thinks that it supports and 0x24 is not listed: # mt -f /dev/nrsa0 status Mode Density Blocksize bpi Compression Current: X3B5/88-185A 512 bytes 61000 DCLZ ---------available modes--------- 0: X3B5/88-185A 512 bytes 61000 DCLZ 1: X3B5/88-185A 512 bytes 61000 DCLZ 2: X3B5/88-185A 512 bytes 61000 DCLZ 3: X3B5/88-185A 512 bytes 61000 DCLZ What?!? Why does the sa device only think that DDS is supported? What is wrong here? Is this a fundamental user error or something else? Please help as I am now officially quite confused. --Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 5 15:34:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19742 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 15:34:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19735 for ; Thu, 5 Nov 1998 15:34:30 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA27028; Thu, 5 Nov 1998 16:34:10 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811052334.QAA27028@panzer.plutotech.com> Subject: Re: ncr0: timeout ccb=0xf0533400 (skip) In-Reply-To: <3641689A.72B245FB@jezebel.demon.co.uk> from Richard Smith at "Nov 5, 98 08:58:02 am" To: richard@jezebel.demon.co.uk (Richard Smith) Date: Thu, 5 Nov 1998 16:34:10 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Richard Smith wrote... > [this question was originally posted to -questions] > > I have a symbios logic v4.0 pci scsi bios pci rev 2.0,2.1 pci-4.03.00 > 53c875 fast20 wide scsi [which has subsequently been upgraded to 4.11] > and a fujitsu M2949E-512 HDD (about 8.5 Gbytes). > > I am running FreeBSD 2.2.7R and NT 4.0 on the same machine. The disk is > split so that NT occupies the lower 4G and FreeBSD occupies the upper 4G > (as this was the only way I could get NT to boot), and using your boot > manager to switch between the two. > > Under FreeBSD, the system keeps falling over with a single ncr0: timeout > error, nothing else gets written to the screen, and nothing gets written > to the message log (as it's on the same disk). The problem usually needs > two power cycles to rectify, as the first falls over again during fsck. > > The problem appears to be pattern sensitive: If I try to tar my mail > directory it falls over every time, while othertimes it may stay up all > day. Needless to say NT never fails. > I have played with cables, checked terminators, searched the mailing > lists. > > I want to advocate FreeBSD for my next project, and I'm prepared to > specify different hardware for that project and for my desktop (such > as the Adaptec 2940UW - which appears to be popular). What I would like > from you is some guidance as to why I appear to be having these problems > with the current configuration. There are any number of reasons why this could be happening. It could be that your drive is "going out to lunch" and not coming back. The timeout message you see may be because of a command that was sent to the drive but not returned before the command timeout expired. If that's the case it could be a drive firmware bug. It could also be some other problem. (i.e. I don't know exactly what the problem is) There are a couple of courses of action I'd suggest: - Try installing FreeBSD 3.0. The SCSI layer in 3.0 has been completely re-written. The NCR driver is very similar to the one in 2.2.7, but the difference is that we can do more to help you fix the problem under 3.0 than we can under 2.2.7. - get an Adaptec 2940UW. In general, the Adaptec boards are among the best supported SCSI cards for FreeBSD. If you want to stay with 2.2.7, you should make sure that you get the regular 2940UW (which has a 7880 on board), and *not* the 2940U2W (which has a 7890 on board), since the Ultra-2 boards are only supported under FreeBSD 3.0. Even if your problem is a drive firmware bug, the above two courses of action will help us get a little more information on the problem. I would also suggest using Seagate or IBM disks. They generally have much better firmware than the other drive manufacturers. 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 Nov 5 15:46:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20987 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 15:46:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20971 for ; Thu, 5 Nov 1998 15:46:47 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA27077; Thu, 5 Nov 1998 16:46:26 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811052346.QAA27077@panzer.plutotech.com> Subject: Re: SDT-7000 density woes In-Reply-To: <199811052249.RAA09611@terra.milkyway.stdio.com> from Nick Wilhelm-Olsen at "Nov 5, 98 05:49:43 pm" To: wilhelm@milkyway.stdio.com (Nick Wilhelm-Olsen) Date: Thu, 5 Nov 1998 16:46:26 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nick Wilhelm-Olsen wrote... > > Hello, > > I posted this yesterday to freebsd-questions and have gotten > no answers and a couple of 'me too's. So I'm reposting here > in the hopes that someone will look at this. This same > problem has also been seen on a friends system w/ an > Archive Python running 3.0-current. > > I didn't mention it originally, but I am using 120m tapes. > I also didn't mention that this worked great with the old > non-CAM st tape driver. > > I am running 3.0-RELEASE on Compaq EISA box with a fairly > stock kernel, using an Adaptec 2742 (ahc) for SCSI. I have > a Sony SDT-7000 DDS-2 4mm tape drive attached to the system > that properly shows up as sa0. > > ...... > ahc0: at 0x4c00-0x4cff irq 11 on eisa0 slot 4 > ahc0: aic7770 >= Rev E, Twin Channel, A SCSI Id=7, B SCSI Id=7, primary A, 4/255 SCBs > ..... > Waiting 15 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI2 device > sa0: 10.0MB/s transfers (10.0MHz, offset 15) > > My first attempt at dumping to the tape device worked ok, > except for the fact that I ran out of tape well before I > should have, before writing 2G to the device. I immediately > smacked myself for forgeting to set the density to DDS-2 and > enable compression (mode 0x24 from mt(1)): > > # mt -f /dev/nrsa0 density 0x24 > mt: /dev/nrsa0: density: invalid argument > (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 > (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 > (sa0:ahc0:0:4:0): Invalid field in parameter list sks:8f,4 This means that the drive doesn't like the density you're trying to set. Most likely, it means that the tape you've got in the drive isn't recognized as a DDS-2 (120 meter) tape. Or maybe you don't have media in the drive. For instance on my SDT-5000, when I don't have any media in the drive, I get the following when I try the above command: (sa0:ahc0:0:5:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ahc0:0:5:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:5:0): Invalid field in parameter list sks:8d,4 i.e., similar error. > Sure enough, I check the densities that the device thinks that > it supports and 0x24 is not listed: > > # mt -f /dev/nrsa0 status > Mode Density Blocksize bpi Compression > Current: X3B5/88-185A 512 bytes 61000 DCLZ > ---------available modes--------- > 0: X3B5/88-185A 512 bytes 61000 DCLZ > 1: X3B5/88-185A 512 bytes 61000 DCLZ > 2: X3B5/88-185A 512 bytes 61000 DCLZ > 3: X3B5/88-185A 512 bytes 61000 DCLZ > > What?!? Why does the sa device only think that DDS is supported? > What is wrong here? Is this a fundamental user error or something > else? > > Please help as I am now officially quite confused. Well, the mt(1) command in CAM works a little differently than it did under the old SCSI layer. The "available modes" are bogus. The stuff that's printed out is basically just a summary of the current status of the drive. And it's printed out 5 times. :) Try putting a 120 meter tape in the drive and do an mt status. It should detect that you've got a 120 meter tape in, and the density should show up as DDS-2. If the density doesn't show up as DDS-2 with a tape in, then try setting the density to 0x24. Let me know how it goes. 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 Nov 5 23:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00435 for freebsd-scsi-outgoing; Thu, 5 Nov 1998 23:59:54 -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 XAA00417 for ; Thu, 5 Nov 1998 23:59:49 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id SAA11809; Fri, 6 Nov 1998 18:29:15 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA02523; Fri, 6 Nov 1998 18:29:08 +1030 (CST) Message-ID: <19981106182907.B2331@freebie.lemis.com> Date: Fri, 6 Nov 1998 18:29:07 +1030 From: Greg Lehey To: John Fieber Cc: John Hay , freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related References: <19981105122029.A784@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Fieber on Wed, Nov 04, 1998 at 09:37:25PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 4 November 1998 at 21:37:25 -0500, John Fieber wrote: > On Thu, 5 Nov 1998, Greg Lehey wrote: > >> On Wednesday, 4 November 1998 at 9:03:00 -0500, John Fieber wrote: >>> On Sun, 4 Oct 1998, John Hay wrote: >>>> The machine will panic sometimes during a "make world" especially with a >>>> high -j value, but it panics in such a way that it does not leave a dump. >>> >>> I encounter similar problems, though not specifically through >>> "make world" disk activity. >>> >>>> da1: Fixed Direct Access SCSI2 device >>> >>> Mine is , on an ASUS SC200 (ncr) >> >> Interesting. I have: >> >> da1: Fixed Direct Access SCSI2 device >> >> I haven't had any problems at all with this drive, though I haven't >> used it to make world. Does anybody think I should? > > If you can hammer really hard on the drive for a long time > without any ill effects, then maybe they fixed the bug by the > time 2847 came around. In that case the patch should be tweaked. > Alas, we don't know exactly what revision the fix came in at. Well, quite the contrary. I've had this disk in my machine since new (when's that? 3 years?), and I never had any trouble. Yesterday, after I built a new kernel, it started giving me trouble. No panics, just hangs from which it wouldn't recover with a bus reset. I rebuilt the kernel with the quirk entry suggested (sorry, forget who did it), and since then I haven't had any trouble. So: what caused it? Could be, of course, that it was a complete coincidence. But doesn't that make you wonder when it suddenly happens to a lot of people at the same time? Must be a virus. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 07:10:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09004 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 07:10:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08993 for ; Fri, 6 Nov 1998 07:10:06 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id KAA24530; Fri, 6 Nov 1998 10:08:37 -0500 (EST) Date: Fri, 6 Nov 1998 10:08:36 -0500 (EST) From: John Fieber To: Greg Lehey cc: John Hay , freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related In-Reply-To: <19981106182907.B2331@freebie.lemis.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 Fri, 6 Nov 1998, Greg Lehey wrote: > >>>> da1: Fixed Direct Access SCSI2 device > >>> Mine is , on an ASUS SC200 (ncr) > >> da1: Fixed Direct Access SCSI2 device > > Well, quite the contrary. I've had this disk in my machine since new > (when's that? 3 years?), and I never had any trouble. Yesterday, > after I built a new kernel, it started giving me trouble. No panics, > just hangs from which it wouldn't recover with a bus reset. I rebuilt > the kernel with the quirk entry suggested (sorry, forget who did it), > and since then I haven't had any trouble. The plot thickens.... Exactly what (when?) was your old kernel and the new one with problems? I've been running a 3.0-CURRENT kernel as of about a week ago and am having problems with daemons (inetd, sendmail, apache mostly) dying right and left. Very disconcerting. I'm about to go back to a 3.0-RELEASE kernel... Oh, and I got the drive in question just in the last week two (it is temporary acquisition; it goes away in another week or so). -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 10:16:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06748 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 10:16:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06742 for ; Fri, 6 Nov 1998 10:16:34 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id KAA03585; Fri, 6 Nov 1998 10:16:09 -0800 Date: Fri, 6 Nov 1998 10:16:08 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: CAMDEBUG change to mull over... 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 When I've been trying to debug TRACE a particular target, I found that I was just being completely overrun by the CAM_DEBUG_PRINT stuff for tracing in cam_xpt.c. What do you think about CAM_DEBUG_XPT flag that will allow this to be traced separate from other tracing? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 10:29:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08722 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 10:29:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from livarot.noc.fr.clara.net (livarot.noc.fr.clara.net [212.43.195.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08715 for ; Fri, 6 Nov 1998 10:29:47 -0800 (PST) (envelope-from erwan@livarot.noc.fr.clara.net) Received: (from erwan@localhost) by livarot.noc.fr.clara.net (8.8.8/8.8.8) id TAA08710; Fri, 6 Nov 1998 19:29:34 +0100 (CET) (envelope-from erwan) Message-ID: <19981106192934.A8701@noc.fr.clara.net> Date: Fri, 6 Nov 1998 19:29:34 +0100 From: Erwan Lerale To: freebsd-scsi@FreeBSD.ORG Subject: Weird prob with 2940u2w 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, We are using several machines with 'FreeBSD 2.2CAM-19980716-SNAP', 2940u2w SCSI controllers and 7 IBM SCSI hard-drives. Same configuration, same OS version ... One of them is working allright but the others simply panic and reboot when we try to make a 'newfs' on the last disk. I obtain the following message : 'Data-path parity error at seqaddr=0x60' Any ideas ? Cheers Erwan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 11:39:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18213 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 11:39:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from eagle.aitken.com (eagle.aitken.com [209.249.97.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18208 for ; Fri, 6 Nov 1998 11:39:07 -0800 (PST) (envelope-from jaitken@aitken.com) Received: (from jaitken@localhost) by eagle.aitken.com (8.9.1a/8.9.1) id OAA00171 for freebsd-scsi@freebsd.org; Fri, 6 Nov 1998 14:38:54 -0500 From: Jeff Aitken Message-Id: <199811061938.OAA00171@eagle.aitken.com> Subject: 2.2.8: CAM + 789x? To: freebsd-scsi@FreeBSD.ORG Date: Fri, 6 Nov 1998 14:38:53 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL26 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I sent this to -questions a few days ago and received only one response, which was someone looking for the answer as well. ;-) There are apparently a a set of patches to/snapshots of 2.2.x that included CAM support (ftp.freebsd.org/pub/FreeBSD/development/cam). However, the README mentions "questions" regarding support for 7890/1 controllers built in to some motherboards (such as the ASUS P2B-S). My question is will CAM/789x support be included in 2.2.8, or will it remain a 3.x thing? I've been extremely happy with a couple of 2.2.x boxes, and would rather wait until 3.1 if possible instead of jumping to 3.0. Please cc me on any response. TIA!! -- Jeff Aitken jaitken@aitken.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 12:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22526 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 12:02:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22505 for ; Fri, 6 Nov 1998 12:02:42 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA01969; Fri, 6 Nov 1998 13:02:24 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811062002.NAA01969@panzer.plutotech.com> Subject: Re: 2.2.8: CAM + 789x? In-Reply-To: <199811061938.OAA00171@eagle.aitken.com> from Jeff Aitken at "Nov 6, 98 02:38:53 pm" To: jaitken@aitken.com (Jeff Aitken) Date: Fri, 6 Nov 1998 13:02:24 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeff Aitken wrote... > I sent this to -questions a few days ago and received only one > response, which was someone looking for the answer as well. ;-) You're not likely to get a response on SCSI questions by mailing the questions list, since most of the "people with a clue" about SCSI don't read -questions. :) > There are apparently a a set of patches to/snapshots of 2.2.x that > included CAM support (ftp.freebsd.org/pub/FreeBSD/development/cam). > However, the README mentions "questions" regarding support for > 7890/1 controllers built in to some motherboards (such as the ASUS > P2B-S). Those controllers should work fine. In fact, I think Justin has an ASUS motherboard with a builtin 7890. > My question is will CAM/789x support be included in 2.2.8, or will > it remain a 3.x thing? I've been extremely happy with a couple of > 2.2.x boxes, and would rather wait until 3.1 if possible instead of > jumping to 3.0. CAM will never be included in the 2.2.x tree. We will, however, be releasing another snapshot for the 2.2-stable tree at some point. I'm not sure when that will be, since both Justin and I are very busy with "real work" at the moment. Hopefully it'll happen within a couple of weeks, but that's not a promise or guarantee. 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 Nov 6 12:06:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23335 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 12:06:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23269 for ; Fri, 6 Nov 1998 12:06:10 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA01995; Fri, 6 Nov 1998 13:05:50 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811062005.NAA01995@panzer.plutotech.com> Subject: Re: CAMDEBUG change to mull over... In-Reply-To: from Matthew Jacob at "Nov 6, 98 10:16:08 am" To: mjacob@feral.com Date: Fri, 6 Nov 1998 13:05:50 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > When I've been trying to debug TRACE a particular target, I found that > I was just being completely overrun by the CAM_DEBUG_PRINT stuff > for tracing in cam_xpt.c. That's not surprising at all. :) > What do you think about CAM_DEBUG_XPT flag that will allow this > to be traced separate from other tracing? Well, we could do that, but I'd rather have a little more generic solution that would allow turning on/off tracing for various modules or drivers. I.e., have something that would let you just turn on tracing for the sa driver, or just for the transport layer, or just for the error recovery code in cam_periph.c/scsi_all.c, or for all modules... 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 Nov 6 12:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24359 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 12:10:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24352 for ; Fri, 6 Nov 1998 12:10:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00497; Fri, 6 Nov 1998 12:09:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811062009.MAA00497@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jeff Aitken cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 2.2.8: CAM + 789x? In-reply-to: Your message of "Fri, 06 Nov 1998 14:38:53 EST." <199811061938.OAA00171@eagle.aitken.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Nov 1998 12:09:50 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I sent this to -questions a few days ago and received only one > response, which was someone looking for the answer as well. ;-) > > There are apparently a a set of patches to/snapshots of 2.2.x that > included CAM support (ftp.freebsd.org/pub/FreeBSD/development/cam). > However, the README mentions "questions" regarding support for > 7890/1 controllers built in to some motherboards (such as the ASUS > P2B-S). > > My question is will CAM/789x support be included in 2.2.8, or will > it remain a 3.x thing? I've been extremely happy with a couple of > 2.2.x boxes, and would rather wait until 3.1 if possible instead of > jumping to 3.0. > > Please cc me on any response. TIA!! CAM _will_not_ be in 2.2.8. The CAM code is being actively maintained in the 3.0 branch, and there are not enough developer resources to actively maintain it in parallel for 2.2.x. -- \\ 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 Fri Nov 6 12:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25207 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 12:15:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25200 for ; Fri, 6 Nov 1998 12:15:35 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id MAA03989; Fri, 6 Nov 1998 12:15:13 -0800 Date: Fri, 6 Nov 1998 12:15:12 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAMDEBUG change to mull over... In-Reply-To: <199811062005.NAA01995@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 Fri, 6 Nov 1998, Kenneth D. Merry wrote: > That's not surprising at all. :) > > > What do you think about CAM_DEBUG_XPT flag that will allow this > > to be traced separate from other tracing? > > Well, we could do that, but I'd rather have a little more generic solution > that would allow turning on/off tracing for various modules or drivers. > > I.e., have something that would let you just turn on tracing for the sa > driver, or just for the transport layer, or just for the error recovery > code in cam_periph.c/scsi_all.c, or for all modules... Well- if this is the case, let's nuke CAM_DEBUG_PRINT (at least as it is currently used in cam_xpt.c- it really has to be used only sparingly or you'll never be able to find this debugging any use at all) and allow a set of arbitrary cam paths to used for debugging being enabled. The xpt layer itself has a path (CAM_XPT_PATH_ID). -matt p.s.: I seem to have been unsubscribed from a number of lists (again), so if I've missed anything important on freebsd-scsi, let me know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 13:58:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08859 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 13:58:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA08827 for ; Fri, 6 Nov 1998 13:58:37 -0800 (PST) (envelope-from dmiter@sci-nnov.ru) Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id AAA27194 for ; Sat, 7 Nov 1998 00:58:12 +0300 (MSK) Message-ID: <00e701be09d0$6bedd9b0$0200000a@winhome.sci-nnov.ru> Reply-To: "Dmitry Eremin" From: "Dmitry Eremin" To: Subject: amd0: Date: Sat, 7 Nov 1998 00:57:15 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, After insert CAM layer amd0 (amd 53c974 scsi) have been corrupt. Will be it device support again? Best regards, Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 14:17:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11332 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 14:17:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11327 for ; Fri, 6 Nov 1998 14:17:39 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA02973; Fri, 6 Nov 1998 15:17:09 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811062217.PAA02973@panzer.plutotech.com> Subject: Re: amd0: In-Reply-To: <00e701be09d0$6bedd9b0$0200000a@winhome.sci-nnov.ru> from Dmitry Eremin at "Nov 7, 98 00:57:15 am" To: dmiter@sci-nnov.ru Date: Fri, 6 Nov 1998 15:17:09 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dmitry Eremin wrote... > Hello all, > > After insert CAM layer amd0 (amd 53c974 scsi) have been corrupt. > Will be it device support again? It won't be supported unless someone writes a driver for it. As far as I know, there's no work underway on a driver for that chip. So, I'd suggest either getting another SCSI card, or starting work on porting the amd driver to CAM. 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 Nov 6 14:27:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13012 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 14:27:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13007 for ; Fri, 6 Nov 1998 14:27:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01593; Fri, 6 Nov 1998 14:26:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811062226.OAA01593@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Dmitry Eremin" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: amd0: In-reply-to: Your message of "Sat, 07 Nov 1998 00:57:15 +0300." <00e701be09d0$6bedd9b0$0200000a@winhome.sci-nnov.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Nov 1998 14:26:00 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello all, > > After insert CAM layer amd0 (amd 53c974 scsi) have been corrupt. > Will be it device support again? There doesn't appear to be anyone working on a new 53c974 driver, no. We need someone that has one, and an interest in making it happen. -- \\ 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 Fri Nov 6 14:49:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15533 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 14:49:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15487 for ; Fri, 6 Nov 1998 14:48:51 -0800 (PST) (envelope-from dmiter@sci-nnov.ru) Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id BAA28998; Sat, 7 Nov 1998 01:47:30 +0300 (MSK) Message-ID: <011401be09d7$51573180$0200000a@winhome.sci-nnov.ru> Reply-To: "Dmitry Eremin" From: "Dmitry Eremin" To: "Mike Smith" Cc: Subject: Re: amd0: Date: Sat, 7 Nov 1998 01:46:34 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> After insert CAM layer amd0 (amd 53c974 scsi) have been corrupt. >> Will be it device support again? > >There doesn't appear to be anyone working on a new 53c974 driver, no. > >We need someone that has one, and an interest in making it happen. I have one. I have Hewlett Packard Vectra XU 5/90C and this chip into it. I will be happy to help you rewrite this driver. I am ready to test it and any thing else. I don’t have enough experience to rewrite it myself. Can you help me? Best regards, Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 15:06:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17996 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 15:06:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17991 for ; Fri, 6 Nov 1998 15:06:03 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-19.ix.netcom.com [205.186.213.19]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA15971; Fri, 6 Nov 1998 15:05:49 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA10056; Fri, 6 Nov 1998 15:05:45 -0800 (PST) Date: Fri, 6 Nov 1998 15:05:45 -0800 (PST) Message-Id: <199811062305.PAA10056@silvia.hip.berkeley.edu> To: vibes@hipdrome.org CC: freebsd-scsi@FreeBSD.ORG In-reply-to: (vibes@hipdrome.org) Subject: Re: 3.0-CURRENT + ccd From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Are there any known problems with ccd in current? All seems dandy * until I try to newfs the ccd-volume - then it just stops after 4 or 5 * steps in the news-process - and hangs the machine. Tried with SMP and no- * SMP configured kernels. Have you tried newfs'ing the character device ("rccd0c") or the block device ("ccd0c")? The latter used to cause hangs for me too. * I have tried this on three, two and just one disk - on two separate * Adaptec controllers. I could provide more information for diagnostics, * but if there are known problems with ccd at this stage I'd rather just * wait for an update. Does it work if you use one disk not as a ccd? Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 15:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24278 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 15:54:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24273 for ; Fri, 6 Nov 1998 15:54:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA03708; Fri, 6 Nov 1998 16:53:57 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811062353.QAA03708@panzer.plutotech.com> Subject: Re: CAMDEBUG change to mull over... In-Reply-To: from Matthew Jacob at "Nov 6, 98 12:15:12 pm" To: mjacob@feral.com Date: Fri, 6 Nov 1998 16:53:57 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > On Fri, 6 Nov 1998, Kenneth D. Merry wrote: > > That's not surprising at all. :) > > > > > What do you think about CAM_DEBUG_XPT flag that will allow this > > > to be traced separate from other tracing? > > > > Well, we could do that, but I'd rather have a little more generic solution > > that would allow turning on/off tracing for various modules or drivers. > > > > I.e., have something that would let you just turn on tracing for the sa > > driver, or just for the transport layer, or just for the error recovery > > code in cam_periph.c/scsi_all.c, or for all modules... > > > Well- if this is the case, let's nuke CAM_DEBUG_PRINT (at least as it is > currently used in cam_xpt.c- it really has to be used only sparingly or > you'll never be able to find this debugging any use at all) and allow a > set of arbitrary cam paths to used for debugging being enabled. The xpt > layer itself has a path (CAM_XPT_PATH_ID). I think it's fine to trim down the number of CAM_DEBUG_PRINT statements in cam_xpt.c. The transport layer path is -1, which is also used to turn on debugging for all busses. I'd rather come up with something separate from cam_path statements to specify which files/modules you want debugging info from. 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 Nov 6 15:57:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24607 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 15:57:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24601 for ; Fri, 6 Nov 1998 15:57:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id PAA04700; Fri, 6 Nov 1998 15:57:35 -0800 Date: Fri, 6 Nov 1998 15:57:35 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAMDEBUG change to mull over... In-Reply-To: <199811062353.QAA03708@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 > > Well- if this is the case, let's nuke CAM_DEBUG_PRINT (at least as it is > > currently used in cam_xpt.c- it really has to be used only sparingly or > > you'll never be able to find this debugging any use at all) and allow a > > set of arbitrary cam paths to used for debugging being enabled. The xpt > > layer itself has a path (CAM_XPT_PATH_ID). > > I think it's fine to trim down the number of CAM_DEBUG_PRINT statements in > cam_xpt.c. > > The transport layer path is -1, which is also used to turn on debugging for > all busses. > > I'd rather come up with something separate from cam_path statements to > specify which files/modules you want debugging info from. > There are two things desired: one is files/modules. There is per-device. Well, we can discuss it until the cows come home. Why don't I hack for a while and if something seems of general use, I'll propose it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 15:59:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24806 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 15:59:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24794 for ; Fri, 6 Nov 1998 15:59:48 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA03771; Fri, 6 Nov 1998 16:59:34 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811062359.QAA03771@panzer.plutotech.com> Subject: Re: CAMDEBUG change to mull over... In-Reply-To: from Matthew Jacob at "Nov 6, 98 03:57:35 pm" To: mjacob@feral.com Date: Fri, 6 Nov 1998 16:59:34 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > > > Well- if this is the case, let's nuke CAM_DEBUG_PRINT (at least as it is > > > currently used in cam_xpt.c- it really has to be used only sparingly or > > > you'll never be able to find this debugging any use at all) and allow a > > > set of arbitrary cam paths to used for debugging being enabled. The xpt > > > layer itself has a path (CAM_XPT_PATH_ID). > > > > I think it's fine to trim down the number of CAM_DEBUG_PRINT statements in > > cam_xpt.c. > > > > The transport layer path is -1, which is also used to turn on debugging for > > all busses. > > > > I'd rather come up with something separate from cam_path statements to > > specify which files/modules you want debugging info from. > > > > There are two things desired: one is files/modules. There is per-device. > Well, we can discuss it until the cows come home. Why don't I hack for > a while and if something seems of general use, I'll propose it? Sounds good, give it a shot. :) 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 Nov 6 21:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25422 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 21:05:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from k6n1.znh.org (dialup5.gaffaneys.com [208.155.161.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25407 for ; Fri, 6 Nov 1998 21:05:25 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id FAA06820 for freebsd-scsi@FreeBSD.ORG; Sat, 7 Nov 1998 05:06:31 GMT (envelope-from zach) Message-ID: <19981106230631.A6726@znh.org> Date: Fri, 6 Nov 1998 23:06:31 -0600 From: Zach Heilig To: freebsd-scsi@FreeBSD.ORG Subject: acceptable SCSI cable geometry? Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just received an external 7-bay SCSI case, and am a bit uneasy about the way the internal cable connects. I ask because I need to order a SCSI-II to SCSI-II external cable, and if there might be a problem with this sort of configuration, I might as well get a different internal cable for the case at the same time. [the case was cheap enough, so buying another cable is not a real big deal]. [ this will only have fast scsi devices (cdroms/cd-writer/jazz) ] It looks like: ^ C | | | |<------- 4 feet --------> 20 inches +------+--+--+--+--+--+--+ | | \ / | | 5 inches v C Is that significantly worse than (for example): <--------- 4.5 feet ---------> C--------+--+--+--+--+--+--+-T \ / \ / 6 inches 3 inches + == device connector. C == external connector. T == terminator. -- Zach Heilig If it looks like a duck, and quacks like a duck, we have to at least consider the possibility that we have a small aquatic bird of the family Anatidæ on our hands (Douglas Adams -- Dirk Gently's Holistic Detective Agency) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 21:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27181 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 21:29:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hyper.activeisp.com (hyper.activeisp.com [195.18.159.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27176 for ; Fri, 6 Nov 1998 21:29:20 -0800 (PST) (envelope-from erik@habatech.no) Received: from smtp.activeisp.com (inter-2.activeisp.com [10.0.2.1]) by hyper.activeisp.com (2.5 Build 2639 (Berkeley 8.8.6)/8.8.4) with ESMTP id GAA00734 for ; Sat, 07 Nov 1998 06:31:34 +0100 Received: from erik ([194.54.100.139]) by smtp.activeisp.com with Microsoft SMTPSVC(5.5.1875.185.18); Sat, 7 Nov 1998 06:25:34 +0100 From: "Erik Haugen Bakke" To: "Erwan Lerale" , Subject: SV: Weird prob with 2940u2w Date: Sat, 7 Nov 1998 04:29:48 +0100 Message-ID: <01be09fe$df24b2e0$0301a8c0@erik> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id VAA27177 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I obtain the following message : 'Data-path parity error at seqaddr=0x60' > I was getting a lot of these messages on my system a while ago, 2940U2W controller and Seagate Cheetah drives, but running 3.0 CURRENT. It seemed like the U2W cable was receiving interference from the computers PSU. When I routed the cable more carefully, the problem disappeared. Just my 0x02 cents worth. --- Erik H. Bakke Habatech AS erik@habatech.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 6 23:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06439 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 23:52:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles131.castles.com [208.214.165.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06434 for ; Fri, 6 Nov 1998 23:52:08 -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 XAA00467; Fri, 6 Nov 1998 23:51:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811070751.XAA00467@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Zach Heilig cc: freebsd-scsi@FreeBSD.ORG Subject: Re: acceptable SCSI cable geometry? In-reply-to: Your message of "Fri, 06 Nov 1998 23:06:31 CST." <19981106230631.A6726@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 06 Nov 1998 23:51:21 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA06435 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I just received an external 7-bay SCSI case, and am a bit uneasy about the way > the internal cable connects. > > I ask because I need to order a SCSI-II to SCSI-II external cable, and if > there might be a problem with this sort of configuration, I might as well get > a different internal cable for the case at the same time. [the case was cheap > enough, so buying another cable is not a real big deal]. > > [ this will only have fast scsi devices (cdroms/cd-writer/jazz) ] > > It looks like: > > ^ C > | | > | |<------- 4 feet --------> > 20 inches +------+--+--+--+--+--+--+ > | | \ / > | | 5 inches > v C > > Is that significantly worse than (for example): > > <--------- 4.5 feet ---------> > C--------+--+--+--+--+--+--+-T > \ / \ / > 6 inches 3 inches > > + == device connector. > C == external connector. > T == terminator. Yes. The person responsible for that cable should be shot. A 4' stub is in no way compatible with the SCSI bus. -- \\ 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 Fri Nov 6 23:55:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06718 for freebsd-scsi-outgoing; Fri, 6 Nov 1998 23:55:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles131.castles.com [208.214.165.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06711 for ; Fri, 6 Nov 1998 23:55:38 -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 XAA00499; Fri, 6 Nov 1998 23:54:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811070754.XAA00499@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Dmitry Eremin" cc: "Mike Smith" , freebsd-scsi@FreeBSD.ORG Subject: Re: amd0: In-reply-to: Your message of "Sat, 07 Nov 1998 01:46:34 +0300." <011401be09d7$51573180$0200000a@winhome.sci-nnov.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 06 Nov 1998 23:54:35 -0800 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA06713 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >> After insert CAM layer amd0 (amd 53c974 scsi) have been corrupt. > >> Will be it device support again? > > > >There doesn't appear to be anyone working on a new 53c974 driver, no. > > > >We need someone that has one, and an interest in making it happen. > > I have one. I have Hewlett Packard Vectra XU 5/90C and this chip into it. > I will be happy to help you rewrite this driver. I am ready to test it and > any thing else. > I don’t have enough experience to rewrite it myself. Can you help me? No, I can't. You may wish to contact Tekram, who were kind enough to supply the last driver. -- \\ 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 Sat Nov 7 11:18:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29930 for freebsd-scsi-outgoing; Sat, 7 Nov 1998 11:18:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29915 for ; Sat, 7 Nov 1998 11:18:43 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from nospam.hiwaay.net (tnt1-132.HiWAAY.net [208.147.147.132]) by mail.HiWAAY.net (8.9.0/8.9.0) with ESMTP id NAA05482; Sat, 7 Nov 1998 13:18:29 -0600 (CST) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.8) with ESMTP id LAA03578; Sat, 7 Nov 1998 11:53:33 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199811071753.LAA03578@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Zach Heilig cc: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: acceptable SCSI cable geometry? In-reply-to: Message from Zach Heilig of "Fri, 06 Nov 1998 23:06:31 CST." <19981106230631.A6726@znh.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sat, 07 Nov 1998 11:53:33 -0600 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA29920 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Zach Heilig writes: > It looks like: > > ^ C > | | > | |<------- 4 feet --------> > 20 inches +------+--+--+--+--+--+--+ > | | \ / > | | 5 inches > v C > > Is that significantly worse than (for example): Its terrible! Just asking for trouble. Even if you terminate the last device on the internal 4' length. > <--------- 4.5 feet ---------> > C--------+--+--+--+--+--+--+-T > \ / \ / > 6 inches 3 inches > > + == device connector. > C == external connector. > T == terminator. Ideally your internal cable should have two external connectors, one at each end. And whatever internal stuff in between. But if you are dealing with a box with 7 narrow SCSI devices there is no point in having a 2nd external connector and the later above cable is perfectly correct. A pair of scissors could trim off one of the 20" legs, then put a terminated drive on the end of the 4' length and you'll be OK. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message