From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 11:08:35 2006 Return-Path: X-Original-To: freebsd-scsi@FreeBSD.org Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3DD016A47C for ; Mon, 23 Oct 2006 11:08:35 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8885E43D4C for ; Mon, 23 Oct 2006 11:08:35 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k9NB8Z4q027802 for ; Mon, 23 Oct 2006 11:08:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k9NB8Yjl027798 for freebsd-scsi@FreeBSD.org; Mon, 23 Oct 2006 11:08:34 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Oct 2006 11:08:34 GMT Message-Id: <200610231108.k9NB8Yjl027798@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 11:08:36 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/27059 scsi [sym] SCSI subsystem hangs under heavy load on (Server o kern/28508 scsi problems with backup to Tandberg SLR40 strimmer o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/40895 scsi wierd kernel / device driver bug o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/60598 scsi wire down of scsi devices conflicts with config o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 o kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceProbeInfo comm o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/93128 scsi [sym] FreeBSD 6.1 BETA 1 has problems with Symbios/LSI o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/99954 scsi [ahc] reading from DVD failes on 6.x (regression) 16 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/23314 scsi aic driver fails to detect Adaptec 1520B unless PnP is o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [feature request] DPT PM2012B/90 doesn't work o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/96133 scsi [scsi] [patch] add scsi quirk for joyfly 128mb flash u o kern/103702 scsi [cam] [patch] ChipsBnk: Unsupported USB memory stick 7 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 13:09:31 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7931216A47C for ; Mon, 23 Oct 2006 13:09:31 +0000 (UTC) (envelope-from supportsobaka@mail.ru) Received: from relay.peterstar.ru (relay.peterstar.ru [217.195.65.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38DB743D5D for ; Mon, 23 Oct 2006 13:09:29 +0000 (GMT) (envelope-from supportsobaka@mail.ru) Received: from c.mshome.net ([84.204.4.2]) by relay.peterstar.ru (8.13.8/8.11.4) with ESMTP id k9ND9Q0m049851 for ; Mon, 23 Oct 2006 17:09:27 +0400 (MSD) Date: Mon, 23 Oct 2006 17:07:39 +0400 From: supportsobaka@mail.ru X-Mailer: The Bat! (v3.85.03) Professional Organization: supportsobaka@mail.ru X-Priority: 3 (Normal) Message-ID: <1378533299.20061023170739@mail.ru> To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 385 [Oct 20 2006] X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0242], KAS30/Release Subject: SR1500 + 5000PAL + SAS backplane - no RAID support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: supportsobaka@mail.ru List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 13:09:31 -0000 Hello Sorry for bad English Dose anybody play with SR1500 + 5000PAL + SAS backplane ? In system BIOS I set SATA and PATA controller - Disable {it is controllers on motherboard 5000PAL} Mass storage controllers menu SAS controller - Enable {it is controller on backplane} SAS configure as SW RAID - Enable RAID was build in controller's BIOS (CTRL+E during boot). But in FreeBSD I have separated devices, no raid, and no way to build it in FreeBSD Releng_6 DMESG: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #0: Fri Oct 20 21:04:52 MSD 2006 root@servertests.ru:/usr/home/obj/usr/src/sys/SERVERTESTS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3191.88-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe43d,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 2143289344 (2044 MB) avail memory = 2090569728 (1993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 cpu2: on acpi0 acpi_throttle2: on cpu2 acpi_throttle2: failed to attach P_CNT device_attach: acpi_throttle2 attach returned 6 cpu3: on acpi0 acpi_throttle3: on cpu3 acpi_throttle3: failed to attach P_CNT device_attach: acpi_throttle3 attach returned 6 cpu4: on acpi0 acpi_throttle4: on cpu4 acpi_throttle4: failed to attach P_CNT device_attach: acpi_throttle4 attach returned 6 cpu5: on acpi0 acpi_throttle5: on cpu5 acpi_throttle5: failed to attach P_CNT device_attach: acpi_throttle5 attach returned 6 cpu6: on acpi0 acpi_throttle6: on cpu6 acpi_throttle6: failed to attach P_CNT device_attach: acpi_throttle6 attach returned 6 cpu7: on acpi0 acpi_throttle7: on cpu7 acpi_throttle7: failed to attach P_CNT device_attach: acpi_throttle7 attach returned 6 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 mpt0: port 0x3000-0x30ff mem 0xb8910000-0xb8913fff,0xb8900000-0xb890ffff irq 16 at device 0.0 on pci3 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.13.0 mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). pcib4: irq 16 at device 1.0 on pci2 pci4: on pcib4 pcib5: irq 16 at device 2.0 on pci2 pci5: on pcib5 em0: port 0x2020-0x203f mem 0xb8820000-0xb883ffff,0xb8400000-0xb87fffff irq 18 at device 0.0 on pci5 em0: Ethernet address: 00:04:23:cf:79:50 em0: [FAST] em1: port 0x2000-0x201f mem 0xb8800000-0xb881ffff,0xb8000000-0xb83fffff irq 19 at device 0.1 on pci5 em1: Ethernet address: 00:04:23:cf:79:51 em1: [FAST] pcib6: at device 0.3 on pci1 pci6: on pcib6 pcib7: at device 3.0 on pci0 pci7: on pcib7 pcib8: at device 4.0 on pci0 pci8: on pcib8 pcib9: at device 5.0 on pci0 pci9: on pcib9 pcib10: at device 6.0 on pci0 pci10: on pcib10 pcib11: at device 7.0 on pci0 pci11: on pcib11 pci0: at device 8.0 (no driver attached) pcib12: at device 30.0 on pci0 pci12: on pcib12 pci12: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 pci0: at device 31.3 (no driver attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio1: type 16550A, console atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xd07ff,0xd0800-0xd17ff,0xd1800-0xd27ff on isa0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). ses0 at mpt0 bus 0 target 4 lun 0 ses0: Fixed Enclosure Services SCSI-3 device ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 239372MB (490234752 512 byte sectors: 255H 63S/T 30515C) da1 at mpt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 300.000MB/s transfers, Tagged Queueing Enabled da1: 70136MB (143638992 512 byte sectors: 255H 63S/T 8941C) da2 at mpt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 300.000MB/s transfers, Tagged Queueing Enabled da2: 70136MB (143638992 512 byte sectors: 255H 63S/T 8941C) lapic3: Forcing LINT1 to edge trigger SMP: AP CPU #3 Launched! lapic1: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! lapic6: Forcing LINT1 to edge trigger SMP: AP CPU #6 Launched! lapic2: Forcing LINT1 to edge trigger SMP: AP CPU #2 Launched! lapic7: Forcing LINT1 to edge trigger SMP: AP CPU #7 Launched! lapic4: Forcing LINT1 to edge trigger SMP: AP CPU #4 Launched! lapic5: Forcing LINT1 to edge trigger SMP: AP CPU #5 Launched! Trying to mount root from ufs:/dev/da0s1a em0: link state changed to UP ===== Not mfi, not iir helped. Which driver must be used? Or FreeBSD just not supported LSISAS1054E with integrated RAID ? (http://www.lsi.com/storage_home/products_home/standard_product_ics/sas_ics/lsisas1064e/index.html) Also what about mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). Is it danger on production server? Thank you From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 13:44:58 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A0FD16A565 for ; Mon, 23 Oct 2006 13:44:58 +0000 (UTC) (envelope-from Johannes.Kruger@nokia.com) Received: from mgw-ext12.nokia.com (mgw-ext12.nokia.com [131.228.20.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEBCA44129 for ; Mon, 23 Oct 2006 13:26:17 +0000 (GMT) (envelope-from Johannes.Kruger@nokia.com) Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9NDQ8pQ002843; Mon, 23 Oct 2006 16:26:15 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 16:26:09 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 08:25:56 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 23 Oct 2006 08:25:54 -0500 Message-ID: In-Reply-To: <1378533299.20061023170739@mail.ru> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SR1500 + 5000PAL + SAS backplane - no RAID support Thread-Index: Acb2pNMtoJknCrEpQDSahzHwtao2NQAAPuKQ From: To: , X-OriginalArrivalTime: 23 Oct 2006 13:25:56.0829 (UTC) FILETIME=[C5B008D0:01C6F6A6] Cc: Subject: RE: SR1500 + 5000PAL + SAS backplane - no RAID support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 13:44:58 -0000 #define MPI_EVENT_SAS_PHY_LINK_STATUS (0x00000012) #define MPI_EVENT_SAS_DISCOVERY_ERROR (0x00000013) #define MPI_EVENT_IR_RESYNC_UPDATE (0x00000014) #define MPI_EVENT_IR2 (0x00000015) #define MPI_EVENT_SAS_DISCOVERY (0x00000016) Event 0x16 just means that the card is probing for devices attached to the PHY's=20 In your case 0x12 means a device have been seen on a PHY P.S. If you get time and want to do me a favor, configure 2 drives on the controller in a RAID-1 configuration. Then do a disk test on the RAID-1 volume, say with iozone or any other method, and tell me your performance. I get slow RAID-1 performance, still cannot figure this out, ~5 Mbytse/sec instead of ~ 30 Mbytes/sec with no volume. With NCQ enabled it goes up to 15, but it' still not 30. I can get faster RAID-1 performance by implementing this in software doing parallel writes. Johan -----Original Message----- From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd-scsi@freebsd.org]=20 Sent: Monday, October 23, 2006 9:08 AM To: freebsd-scsi@freebsd.org Subject: SR1500 + 5000PAL + SAS backplane - no RAID support Hello Sorry for bad English Dose anybody play with SR1500 + 5000PAL + SAS backplane ? In system BIOS I set SATA and PATA controller - Disable {it is controllers on motherboard 5000PAL} Mass storage controllers menu SAS controller - Enable {it is controller on backplane} SAS configure as SW RAID - Enable RAID was build in controller's BIOS (CTRL+E during boot). But in FreeBSD I have separated devices, no raid, and no way to build it in FreeBSD Releng_6 DMESG: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #0: Fri Oct 20 21:04:52 MSD 2006 root@servertests.ru:/usr/home/obj/usr/src/sys/SERVERTESTS Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3191.88-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf64 Stepping =3D 4 =20 Features=3D0xbfebfbff Features2=3D0xe43d,> AMD Features=3D0x20100000 AMD Features2=3D0x1 Cores per package: 2 Logical CPUs per core: 2 real memory =3D 2143289344 (2044 MB) avail memory =3D 2090569728 (1993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 cpu2: on acpi0 acpi_throttle2: on cpu2 acpi_throttle2: failed to attach P_CNT device_attach: acpi_throttle2 attach returned 6 cpu3: on acpi0 acpi_throttle3: on cpu3 acpi_throttle3: failed to attach P_CNT device_attach: acpi_throttle3 attach returned 6 cpu4: on acpi0 acpi_throttle4: on cpu4 acpi_throttle4: failed to attach P_CNT device_attach: acpi_throttle4 attach returned 6 cpu5: on acpi0 acpi_throttle5: on cpu5 acpi_throttle5: failed to attach P_CNT device_attach: acpi_throttle5 attach returned 6 cpu6: on acpi0 acpi_throttle6: on cpu6 acpi_throttle6: failed to attach P_CNT device_attach: acpi_throttle6 attach returned 6 cpu7: on acpi0 acpi_throttle7: on cpu7 acpi_throttle7: failed to attach P_CNT device_attach: acpi_throttle7 attach returned 6 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 mpt0: port 0x3000-0x30ff mem 0xb8910000-0xb8913fff,0xb8900000-0xb890ffff irq 16 at device 0.0 on pci3 mpt0: [GIANT-LOCKED] mpt0: MPI Version=3D1.5.13.0 mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). pcib4: irq 16 at device 1.0 on pci2 pci4: on pcib4 pcib5: irq 16 at device 2.0 on pci2 pci5: on pcib5 em0: port 0x2020-0x203f mem 0xb8820000-0xb883ffff,0xb8400000-0xb87fffff irq 18 at device 0.0 on pci5 em0: Ethernet address: 00:04:23:cf:79:50 em0: [FAST] em1: port 0x2000-0x201f mem 0xb8800000-0xb881ffff,0xb8000000-0xb83fffff irq 19 at device 0.1 on pci5 em1: Ethernet address: 00:04:23:cf:79:51 em1: [FAST] pcib6: at device 0.3 on pci1 pci6: on pcib6 pcib7: at device 3.0 on pci0 pci7: on pcib7 pcib8: at device 4.0 on pci0 pci8: on pcib8 pcib9: at device 5.0 on pci0 pci9: on pcib9 pcib10: at device 6.0 on pci0 pci10: on pcib10 pcib11: at device 7.0 on pci0 pci11: on pcib11 pci0: at device 8.0 (no driver attached) pcib12: at device 30.0 on pci0 pci12: on pcib12 pci12: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 pci0: at device 31.3 (no driver attached) sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio1: type 16550A, console atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xd07ff,0xd0800-0xd17ff,0xd1800-0xd27ff on isa0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). ses0 at mpt0 bus 0 target 4 lun 0 ses0: Fixed Enclosure Services SCSI-3 device=20 ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device=20 da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 239372MB (490234752 512 byte sectors: 255H 63S/T 30515C) da1 at mpt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device=20 da1: 300.000MB/s transfers, Tagged Queueing Enabled da1: 70136MB (143638992 512 byte sectors: 255H 63S/T 8941C) da2 at mpt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device=20 da2: 300.000MB/s transfers, Tagged Queueing Enabled da2: 70136MB (143638992 512 byte sectors: 255H 63S/T 8941C) lapic3: Forcing LINT1 to edge trigger SMP: AP CPU #3 Launched! lapic1: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! lapic6: Forcing LINT1 to edge trigger SMP: AP CPU #6 Launched! lapic2: Forcing LINT1 to edge trigger SMP: AP CPU #2 Launched! lapic7: Forcing LINT1 to edge trigger SMP: AP CPU #7 Launched! lapic4: Forcing LINT1 to edge trigger SMP: AP CPU #4 Launched! lapic5: Forcing LINT1 to edge trigger SMP: AP CPU #5 Launched! Trying to mount root from ufs:/dev/da0s1a em0: link state changed to UP =3D=3D=3D=3D=3D Not mfi, not iir helped. Which driver must be used? Or FreeBSD just not supported LSISAS1054E with integrated RAID ? (http://www.lsi.com/storage_home/products_home/standard_product_ics/sas_ ics/lsisas1064e/index.html) Also what about mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). Is it danger on production server? Thank you _______________________________________________ freebsd-scsi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-scsi To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 14:12:29 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84E8416A40F for ; Mon, 23 Oct 2006 14:12:29 +0000 (UTC) (envelope-from supportsobaka@mail.ru) Received: from relay.peterstar.ru (relay.peterstar.ru [217.195.65.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC60443D76 for ; Mon, 23 Oct 2006 14:12:28 +0000 (GMT) (envelope-from supportsobaka@mail.ru) Received: from [84.204.167.252] ([84.204.167.252]) by relay.peterstar.ru (8.13.8/8.11.4) with ESMTP id k9NECFkL016681 for ; Mon, 23 Oct 2006 18:12:26 +0400 (MSD) Date: Mon, 23 Oct 2006 18:11:55 +0400 From: supportsobaka@mail.ru X-Mailer: The Bat! (v3.85.03) Professional Organization: supportsobaka@mail.ru X-Priority: 3 (Normal) Message-ID: <1159634324.20061023181155@mail.ru> To: freebsd-scsi@freebsd.org References: 1378533299.20061023170739@mail.ru MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 385 [Oct 20 2006] X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0242], KAS30/Release Subject: SR1500 + 5000PAL + SAS backplane - no RAID support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: supportsobaka@mail.ru List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 14:12:29 -0000 -----Original Message----- #define MPI_EVENT_SAS_PHY_LINK_STATUS (0x00000012) #define MPI_EVENT_SAS_DISCOVERY_ERROR (0x00000013) #define MPI_EVENT_IR_RESYNC_UPDATE (0x00000014) #define MPI_EVENT_IR2 (0x00000015) #define MPI_EVENT_SAS_DISCOVERY (0x00000016) Event 0x16 just means that the card is probing for devices attached to the PHY's In your case 0x12 means a device have been seen on a PHY P.S. If you get time and want to do me a favor, configure 2 drives on the controller in a RAID-1 configuration. Then do a disk test on the RAID-1 volume, say with iozone or any other method, and tell me your performance. I get slow RAID-1 performance, still cannot figure this out, ~5 Mbytse/sec instead of ~ 30 Mbytes/sec with no volume. With NCQ enabled it goes up to 15, but it' still not 30. I can get faster RAID-1 performance by implementing this in software doing parallel writes. Johan -----Original Message----- How I can test it... First of all FreeBSD should see RAID, but it only see separated HDD (da*) This is the problem that I described From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 14:25:36 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69E9F16A407 for ; Mon, 23 Oct 2006 14:25:36 +0000 (UTC) (envelope-from Johannes.Kruger@nokia.com) Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 321D243D55 for ; Mon, 23 Oct 2006 14:25:29 +0000 (GMT) (envelope-from Johannes.Kruger@nokia.com) Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9NEPS38005272; Mon, 23 Oct 2006 17:25:28 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 17:25:28 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 09:25:27 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 23 Oct 2006 09:25:25 -0500 Message-ID: In-Reply-To: <1159634324.20061023181155@mail.ru> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SR1500 + 5000PAL + SAS backplane - no RAID support Thread-Index: Acb2rbIOtv+oYd6/TIuq43w7D5DT/QAAOlhw From: To: , X-OriginalArrivalTime: 23 Oct 2006 14:25:27.0696 (UTC) FILETIME=[16171900:01C6F6AF] Cc: Subject: RE: SR1500 + 5000PAL + SAS backplane - no RAID support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 14:25:36 -0000 You have to setup the RAID-1 volume in the LSI BIOS. The normal motherboard BIOS is supposed to execute the bootrom in the LSI card, which will allow you to enter the LSI BIOS. If I remember correctly it's "control-C" on bootup, instead of "DEL". Then you select new IM volume (Integrated mirroring)=20 You can migrate your main disk to the volume, and your second disk will then be synchronized to look like the first disk. Johan -----Original Message----- From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd-scsi@freebsd.org]=20 Sent: Monday, October 23, 2006 10:12 AM To: freebsd-scsi@freebsd.org Subject: SR1500 + 5000PAL + SAS backplane - no RAID support -----Original Message----- #define MPI_EVENT_SAS_PHY_LINK_STATUS (0x00000012) #define MPI_EVENT_SAS_DISCOVERY_ERROR (0x00000013) #define MPI_EVENT_IR_RESYNC_UPDATE (0x00000014) #define MPI_EVENT_IR2 (0x00000015) #define MPI_EVENT_SAS_DISCOVERY (0x00000016) Event 0x16 just means that the card is probing for devices attached to the PHY's=20 In your case 0x12 means a device have been seen on a PHY P.S. If you get time and want to do me a favor, configure 2 drives on the controller in a RAID-1 configuration. Then do a disk test on the RAID-1 volume, say with iozone or any other method, and tell me your performance. I get slow RAID-1 performance, still cannot figure this out, ~5 Mbytse/sec instead of ~ 30 Mbytes/sec with no volume. With NCQ enabled it goes up to 15, but it' still not 30. I can get faster RAID-1 performance by implementing this in software doing parallel writes. Johan -----Original Message----- How I can test it... First of all FreeBSD should see RAID, but it only see separated HDD (da*) This is the problem that I described _______________________________________________ freebsd-scsi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-scsi To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 16:57:44 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C178F16A412 for ; Mon, 23 Oct 2006 16:57:44 +0000 (UTC) (envelope-from supportsobaka@mail.ru) Received: from relay.peterstar.ru (relay.peterstar.ru [217.195.65.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A654D43DF4 for ; Mon, 23 Oct 2006 16:53:57 +0000 (GMT) (envelope-from supportsobaka@mail.ru) Received: from [84.204.167.252] ([84.204.167.252]) by relay.peterstar.ru (8.13.8/8.11.4) with ESMTP id k9NGrgV6021209; Mon, 23 Oct 2006 20:53:44 +0400 (MSD) Date: Mon, 23 Oct 2006 20:53:22 +0400 From: supportsobaka@mail.ru X-Mailer: The Bat! (v3.85.03) Professional Organization: supportsobaka@mail.ru X-Priority: 3 (Normal) Message-ID: <1461378224.20061023205322@mail.ru> To: Johannes.Kruger@nokia.com In-Reply-To: References: <1159634324.20061023181155@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 387 [Oct 23 2006] X-SpamTest-Method: none X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0242], KAS30/Release Cc: freebsd-scsi@freebsd.org Subject: Re[2]: SR1500 + 5000PAL + SAS backplane - no RAID support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: supportsobaka@mail.ru List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 16:57:44 -0000 JKnc> You have to setup the RAID-1 volume in the LSI BIOS. JKnc> The normal motherboard BIOS is supposed to execute the bootrom in the JKnc> LSI card, which will allow you to enter the LSI BIOS. JKnc> If I remember correctly it's "control-C" on bootup, instead of "DEL". JKnc> Then you select new IM volume (Integrated mirroring) JKnc> You can migrate your main disk to the volume, and your second disk will JKnc> then be synchronized to look like the first disk. I described in my first message, that RAID was setup in BIOS, but FreeBSD can't see it's raid. It is main problem! ...not "event 0x16" problem Once again: --- In system BIOS I set Mass storage controllers menu SAS controller - Enable SAS configure as SW RAID - Enable RAID was build in controller's BIOS (CTRL+E during boot). --- We talking about Intel 5000PAL + SAS backplane There is LSISAS1054E chip and 3 SAS Ports 1U Active Backplane and Intel Embedded Server Raid Technology II for RAID setup (CTRL+E during boot) FreeBSD can't see raid JKnc> Johan JKnc> -----Original Message----- JKnc> From: owner-freebsd-scsi@freebsd.org JKnc> [mailto:owner-freebsd-scsi@freebsd.org] JKnc> Sent: Monday, October 23, 2006 10:12 AM JKnc> To: freebsd-scsi@freebsd.org JKnc> Subject: SR1500 + 5000PAL + SAS backplane - no RAID support JKnc> -----Original Message----- JKnc> #define MPI_EVENT_SAS_PHY_LINK_STATUS (0x00000012) JKnc> #define MPI_EVENT_SAS_DISCOVERY_ERROR (0x00000013) JKnc> #define MPI_EVENT_IR_RESYNC_UPDATE (0x00000014) JKnc> #define MPI_EVENT_IR2 (0x00000015) JKnc> #define MPI_EVENT_SAS_DISCOVERY (0x00000016) JKnc> Event 0x16 just means that the card is probing for devices attached to JKnc> the PHY's JKnc> In your case 0x12 means a device have been seen on a PHY JKnc> P.S. If you get time and want to do me a favor, configure 2 drives on JKnc> the controller in a RAID-1 configuration. JKnc> Then do a disk test on the RAID-1 volume, say with iozone or any other JKnc> method, and tell me your performance. JKnc> I get slow RAID-1 performance, still cannot figure this out, ~5 JKnc> Mbytse/sec instead of ~ 30 Mbytes/sec with no volume. JKnc> With NCQ enabled it goes up to 15, but it' still not 30. JKnc> I can get faster RAID-1 performance by implementing this in software JKnc> doing parallel writes. JKnc> Johan JKnc> -----Original Message----- JKnc> How I can test it... JKnc> First of all FreeBSD should see RAID, but it only see separated HDD JKnc> (da*) JKnc> This is the problem that I described JKnc> _______________________________________________ JKnc> freebsd-scsi@freebsd.org mailing list JKnc> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi JKnc> To unsubscribe, send any mail to JKnc> "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Mon Oct 23 21:05:30 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83EB116A40F for ; Mon, 23 Oct 2006 21:05:30 +0000 (UTC) (envelope-from Johannes.Kruger@nokia.com) Received: from mgw-ext12.nokia.com (mgw-ext12.nokia.com [131.228.20.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EA8A43DEB for ; Mon, 23 Oct 2006 21:04:27 +0000 (GMT) (envelope-from Johannes.Kruger@nokia.com) Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext12.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9NL4Gjr009224; Tue, 24 Oct 2006 00:04:18 +0300 Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 00:04:20 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Oct 2006 16:04:17 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 23 Oct 2006 16:04:15 -0500 Message-ID: In-Reply-To: <1461378224.20061023205322@mail.ru> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re[2]: SR1500 + 5000PAL + SAS backplane - no RAID support Thread-Index: Acb2xBj7KdvEVqN4Rou23fr3bl2YWQAIMWgw From: To: X-OriginalArrivalTime: 23 Oct 2006 21:04:17.0612 (UTC) FILETIME=[CD6E80C0:01C6F6E6] Cc: freebsd-scsi@freebsd.org Subject: RE: Re[2]: SR1500 + 5000PAL + SAS backplane - no RAID support X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2006 21:05:30 -0000 Hmmm, maybe you have the same problem I have with the LSI-1064E . I was able to see a disk though, even though the RAID did not come up. I had to enable the port otherwise the IOC page 2 did not indicate max disks of non-zero, and also not valid RAID info. It also did not help when I executed (enabled the port) afterwards ... strange, you might ask Matthew's opinion on this , I just recently ported his driver to FreeBSD 2.2.X (including required CAM code) for a project I am working on, I did not develop it. In the file mpt.c (location /usr/src/sys/dev/mpt/mpt.c) I had to make a change to enable the port, otherwise the RAID will not get probed because the pages do not contain valid info. Go to function mpt_enable_ioc. Scroll down until you see this snippet: ------------------------- snippet ---------------------------------------- /* * Enable the port if asked. This is only done if we're resetting * the IOC after initial startup. */ //if (portenable) { if (1) { /* * Enable asynchronous event reporting */ //jjk moved it down a bit ? //mpt_send_event_request(mpt, 1); if (mpt_send_port_enable(mpt, 0) !=3D MPT_OK) { printf("failed to enable port 0\n"); return (ENXIO); } mpt_send_event_request(mpt, 1); //jjkhack=20 } return (MPT_OK); -------------------------- snippet --------------------------------------- Change from: if (portenable) { change to: if (1) { You will se I moved down the mpt_send_event_request, but you do not need to do that. Johan . -----Original Message----- From: ext supportsobaka@mail.ru [mailto:supportsobaka@mail.ru]=20 Sent: Monday, October 23, 2006 12:53 PM To: Kruger Johannes (Nokia-ES/Boston) Cc: freebsd-scsi@freebsd.org Subject: Re[2]: SR1500 + 5000PAL + SAS backplane - no RAID support JKnc> You have to setup the RAID-1 volume in the LSI BIOS. JKnc> The normal motherboard BIOS is supposed to execute the bootrom in the JKnc> LSI card, which will allow you to enter the LSI BIOS. JKnc> If I remember correctly it's "control-C" on bootup, instead of "DEL". JKnc> Then you select new IM volume (Integrated mirroring)=20 JKnc> You can migrate your main disk to the volume, and your second disk will JKnc> then be synchronized to look like the first disk. I described in my first message, that RAID was setup in BIOS, but FreeBSD can't see it's raid. It is main problem! ...not "event 0x16" problem Once again: --- In system BIOS I set Mass storage controllers menu SAS controller - Enable SAS configure as SW RAID - Enable RAID was build in controller's BIOS (CTRL+E during boot). --- We talking about Intel 5000PAL + SAS backplane There is LSISAS1054E chip and 3 SAS Ports 1U Active Backplane and Intel Embedded Server Raid Technology II for RAID setup (CTRL+E during boot) FreeBSD can't see raid JKnc> Johan JKnc> -----Original Message----- JKnc> From: owner-freebsd-scsi@freebsd.org JKnc> [mailto:owner-freebsd-scsi@freebsd.org]=20 JKnc> Sent: Monday, October 23, 2006 10:12 AM JKnc> To: freebsd-scsi@freebsd.org JKnc> Subject: SR1500 + 5000PAL + SAS backplane - no RAID support JKnc> -----Original Message----- JKnc> #define MPI_EVENT_SAS_PHY_LINK_STATUS (0x00000012) JKnc> #define MPI_EVENT_SAS_DISCOVERY_ERROR (0x00000013) JKnc> #define MPI_EVENT_IR_RESYNC_UPDATE (0x00000014) JKnc> #define MPI_EVENT_IR2 (0x00000015) JKnc> #define MPI_EVENT_SAS_DISCOVERY (0x00000016) JKnc> Event 0x16 just means that the card is probing for devices attached to JKnc> the PHY's=20 JKnc> In your case 0x12 means a device have been seen on a PHY JKnc> P.S. If you get time and want to do me a favor, configure 2 drives on JKnc> the controller in a RAID-1 configuration. JKnc> Then do a disk test on the RAID-1 volume, say with iozone or any other JKnc> method, and tell me your performance. JKnc> I get slow RAID-1 performance, still cannot figure this out, ~5 JKnc> Mbytse/sec instead of ~ 30 Mbytes/sec with no volume. JKnc> With NCQ enabled it goes up to 15, but it' still not 30. JKnc> I can get faster RAID-1 performance by implementing this in software JKnc> doing parallel writes. JKnc> Johan JKnc> -----Original Message----- JKnc> How I can test it... JKnc> First of all FreeBSD should see RAID, but it only see separated HDD JKnc> (da*) JKnc> This is the problem that I described JKnc> _______________________________________________ JKnc> freebsd-scsi@freebsd.org mailing list JKnc> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi JKnc> To unsubscribe, send any mail to JKnc> "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Tue Oct 24 06:13:47 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BD7816A407 for ; Tue, 24 Oct 2006 06:13:47 +0000 (UTC) (envelope-from hakmi@rogers.com) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 94FAF43D6A for ; Tue, 24 Oct 2006 06:13:39 +0000 (GMT) (envelope-from hakmi@rogers.com) Received: (qmail 14066 invoked from network); 24 Oct 2006 06:13:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-MimeOLE:Thread-Index; b=2m6R0S8bFJ7az3Dmywbs9eimz1f9g0ZdNqVAk+CDFzg+EbFTKBxgOE/AY/12oN4jFf2rZw1N9ybvVL9eVWEJlNpSyfhyGh+zWIG4OcP7MGzH54iH7nedxM6nGAbt/j3/04qh3WVeY3ATW/Ug1reB+ChbJUzSSOKolY8nx2MPFlg= ; Received: from unknown (HELO tamouh) (hakmi@rogers.com@70.27.160.99 with login) by smtp103.rog.mail.re2.yahoo.com with SMTP; 24 Oct 2006 06:13:28 -0000 From: "Tamouh H." To: Date: Tue, 24 Oct 2006 02:13:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: Acb3M4t0a57DQIaGT1yKRmhY/OlKng== Message-Id: <20061024061339.94FAF43D6A@mx1.FreeBSD.org> X-Mailman-Approved-At: Tue, 24 Oct 2006 11:09:12 +0000 Subject: SCB timeout and other errors + system hang with adaptec/seagate X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2006 06:13:47 -0000 Hi, Just stumbled upon this thread, though its been long time. Just thought = to share this with everyone here. Seagate SCSI 147GB U320 Model: = ST3146707LC with older firmware has major issues with some Adaptec cards = and other RAID cards that could possibly lead to the loss of the whole = RAID array. This is the Seagate Advisory: http://www.seagate.com/support/disc/u320_firmware.html http://adaptec-tic.adaptec.com/cgi-bin/adaptec_tic.cfg/php/enduser/std_ad= p.php?p_faqid=3D10047&p_created=3D1063959041&p_sid=3D-oUECTki&p_lva=3D&p_= sp=3DcF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MSZwX3Byb2Rz= PTAmcF9jYXRzPTAmcF9wdj0mcF9jdj0mcF9zZWFyY2hfdHlwZT1hbnN3ZXJzLnNlYXJjaF9ub= CZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PXNlYWdhdGUgdGltZSBvdXQ*&p_li=3D&p_topview= =3D1 Best, Tamouh Hakmi From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 25 08:10:59 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A104A16A412; Wed, 25 Oct 2006 08:10:59 +0000 (UTC) (envelope-from geoffb@chuggalug.clues.com) Received: from chuggalug.clues.com (chuggalug2.demon.co.uk [83.104.169.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85E2243D6B; Wed, 25 Oct 2006 08:10:55 +0000 (GMT) (envelope-from geoffb@chuggalug.clues.com) Received: from chuggalug.clues.com (localhost [127.0.0.1]) by chuggalug.clues.com (8.12.10/8.12.10) with ESMTP id k9P8AZKP034931; Wed, 25 Oct 2006 08:10:35 GMT (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.12.10/8.12.10/Submit) id k9P8AYtj034921; Wed, 25 Oct 2006 08:10:34 GMT (envelope-from geoffb) Date: Wed, 25 Oct 2006 08:10:34 +0000 From: Geoff Buckingham To: Ulf Zimmermann Message-ID: <20061025081034.GA26833@chuggalug.clues.com> References: <8753F8EA457BFF4A9707CADA143C8F6801C75434@LONSMSXM04.emea.ime.reuters.com> <20061020192711.GQ98520@evil.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061020192711.GQ98520@evil.alameda.net> User-Agent: Mutt/1.4.1i Cc: freebsd-scsi@freebsd.org, freebsd-proliant@freebsd.org, Geoff Buckingham Subject: Re: ProLiant DL360 G4p: ciss(4) boottime oddity X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2006 08:10:59 -0000 As another data point, a colleage has informed me the delay does not occur on new Proliants with the SAS versions of the ciss controller. (This is with the same kernel that gives us delays on the U320 versions.) From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 25 08:35:14 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C1116A47C; Wed, 25 Oct 2006 08:35:14 +0000 (UTC) (envelope-from ulf@alameda.net) Received: from mail.alameda.net (mail.alameda.net [64.81.53.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CFD843D58; Wed, 25 Oct 2006 08:35:14 +0000 (GMT) (envelope-from ulf@alameda.net) Received: by mail.alameda.net (Postfix, from userid 1000) id 9939233C9A; Wed, 25 Oct 2006 01:35:10 -0700 (PDT) Date: Wed, 25 Oct 2006 01:35:10 -0700 From: Ulf Zimmermann To: Geoff Buckingham Message-ID: <20061025083510.GS98520@evil.alameda.net> References: <8753F8EA457BFF4A9707CADA143C8F6801C75434@LONSMSXM04.emea.ime.reuters.com> <20061020192711.GQ98520@evil.alameda.net> <20061025081034.GA26833@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061025081034.GA26833@chuggalug.clues.com> User-Agent: Mutt/1.4.2.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 5.3-STABLE X-ANI-MailScanner-Information: Please contact the ISP for more information X-ANI-MailScanner: Found to be clean X-ANI-MailScanner-From: ulf@alameda.net Cc: freebsd-scsi@freebsd.org, Ulf Zimmermann , Geoff Buckingham , freebsd-proliant@freebsd.org Subject: Re: ProLiant DL360 G4p: ciss(4) boottime oddity X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ulf@Alameda.net List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2006 08:35:14 -0000 On Wed, Oct 25, 2006 at 08:10:34AM +0000, Geoff Buckingham wrote: > As another data point, a colleage has informed me the delay does not occur > on new Proliants with the SAS versions of the ciss controller. > (This is with the same kernel that gives us delays on the U320 versions.) Might be of interest to hear which SAS controller he has which doesn't have the delay. There are several different controllers. E200 is the cheap low end version available, both as PCI-E and module for servers such as DL360 g5, DL380 g5, etc. It also comes in at least 2 versions 64MB Cache or 128MB Battery Backed Write Cache. Then there is the P400, again as PCI-E or module. Again with 2 cache versions, 256MB and 512MB with Battery Backed Write Cache. And then there is the P600, which is PCIX, also in either 256MB or 512MB, both Battery Backed Write Cache. The E200/64MB supports only RAID 0/1, E200/128MB does RAID 0/1/5, while the P400 and P600 do RAID 0/1/5/6. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://seven.Alameda.net/~ulf/resume.html From owner-freebsd-scsi@FreeBSD.ORG Thu Oct 26 18:11:13 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDC3E16A407 for ; Thu, 26 Oct 2006 18:11:13 +0000 (UTC) (envelope-from herron@sonatabio.com) Received: from smtp.wizwire.com (smtp.wizwire.com [209.218.100.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E8BE43D4C for ; Thu, 26 Oct 2006 18:11:13 +0000 (GMT) (envelope-from herron@sonatabio.com) Received: from Camel (209.218.101.53.bvi2.wizwire.com [209.218.101.53]) by smtp.wizwire.com (8.13.1/8.13.1) with ESMTP id k9QI9DBZ032311 for ; Thu, 26 Oct 2006 11:09:13 -0700 Message-Id: <200610261809.k9QI9DBZ032311@smtp.wizwire.com> From: "Kevin Herron" To: Date: Thu, 26 Oct 2006 11:09:54 -0700 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Acb5Ke/0C0k61TAtQKiPC4vKn9X6pA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-WizWire-MailScanner-Information: Please contact the ISP for more information X-WizWire-MailScanner: Found to be clean X-MailScanner-From: herron@sonatabio.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: LSI SCSI 1030 mpt error X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2006 18:11:14 -0000 I'm having trouble booting on a LSI 1030 SCSI card. We've had intermittent problems booting off of it in the past. The system started out using 6.1R-p10. We've tried the patch in this thread, http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065622.htm l, as well us upgrading to 6.2 pre-release. The error message follows: Unhandled Event Notify Frame. Event 0xe3966ca8 (ACK not required). It then times out and resets the controller. This cycle repeats until it's manually rebooted. The issue is definitely with the controller and not the drives, as we put in an LSI sym card (LSIU160) and everything works fine. Does anybody have any suggestions? Thanks, Kevin From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 16:10:44 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 928D916A415 for ; Fri, 27 Oct 2006 16:10:44 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 998AC43D67 for ; Fri, 27 Oct 2006 16:10:43 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9RGAhNo060566 for ; Fri, 27 Oct 2006 09:10:43 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9RGAhrK060563 for ; Fri, 27 Oct 2006 09:10:43 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 27 Oct 2006 09:10:43 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-scsi@freebsd.org Message-ID: <20061027090957.V60559@ns1.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 16:10:44 -0000 Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the bullet now and move ahead? From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 16:58:41 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83D9C16A403; Fri, 27 Oct 2006 16:58:41 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E967543D67; Fri, 27 Oct 2006 16:58:40 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([165.236.175.187]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9RGwY1E011025; Fri, 27 Oct 2006 10:58:39 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <45423AB5.3020503@samsco.org> Date: Fri, 27 Oct 2006 10:58:29 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mjacob@freebsd.org References: <20061027090957.V60559@ns1.feral.com> In-Reply-To: <20061027090957.V60559@ns1.feral.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 16:58:41 -0000 mjacob@freebsd.org wrote: > > Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the > bullet now and move ahead? > I have no objection against it. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 18:15:19 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2012916A47E for ; Fri, 27 Oct 2006 18:15:19 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 393A643D70 for ; Fri, 27 Oct 2006 18:15:06 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9RIEual061401 for ; Fri, 27 Oct 2006 11:14:56 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9RIEuE2061398 for ; Fri, 27 Oct 2006 11:14:56 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 27 Oct 2006 11:14:56 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-scsi@freebsd.org In-Reply-To: <45423AB5.3020503@samsco.org> Message-ID: <20061027111434.E61368@ns1.feral.com> References: <20061027090957.V60559@ns1.feral.com> <45423AB5.3020503@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 18:15:19 -0000 I can take on most of the work. > mjacob@freebsd.org wrote: >> >> Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the >> bullet now and move ahead? >> > > I have no objection against it. > > Scott > From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 18:32:37 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 705CB16A407; Fri, 27 Oct 2006 18:32:37 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD39543D55; Fri, 27 Oct 2006 18:32:36 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id k9RIWZgq070316; Fri, 27 Oct 2006 12:32:35 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id k9RIWZtB070315; Fri, 27 Oct 2006 12:32:35 -0600 (MDT) (envelope-from ken) Date: Fri, 27 Oct 2006 12:32:35 -0600 From: "Kenneth D. Merry" To: mjacob@freebsd.org Message-ID: <20061027183235.GA70290@nargothrond.kdm.org> References: <20061027090957.V60559@ns1.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061027090957.V60559@ns1.feral.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2126/Fri Oct 27 07:48:55 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 18:32:37 -0000 On Fri, Oct 27, 2006 at 09:10:43 -0700, mjacob@freebsd.org wrote: > > Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the > bullet now and move ahead? I think it's a good idea. We'll need to figure out how to handle the drivers that haven't had the code implemented for them yet. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 18:39:47 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2A3716A415 for ; Fri, 27 Oct 2006 18:39:47 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6105543D5D for ; Fri, 27 Oct 2006 18:39:47 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9RIdldJ061501; Fri, 27 Oct 2006 11:39:47 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9RIdluG061498; Fri, 27 Oct 2006 11:39:47 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 27 Oct 2006 11:39:47 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: "Kenneth D. Merry" In-Reply-To: <20061027183235.GA70290@nargothrond.kdm.org> Message-ID: <20061027113922.M61368@ns1.feral.com> References: <20061027090957.V60559@ns1.feral.com> <20061027183235.GA70290@nargothrond.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 18:39:48 -0000 > On Fri, Oct 27, 2006 at 09:10:43 -0700, mjacob@freebsd.org wrote: >> >> Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the >> bullet now and move ahead? > > I think it's a good idea. We'll need to figure out how to handle the > drivers that haven't had the code implemented for them yet. > I was going to at least handle the in-tree ones. From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 18:41:44 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71CE716A403; Fri, 27 Oct 2006 18:41:44 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id E565843D77; Fri, 27 Oct 2006 18:41:43 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id k9RIfhbV070798; Fri, 27 Oct 2006 12:41:43 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id k9RIfhqR070797; Fri, 27 Oct 2006 12:41:43 -0600 (MDT) (envelope-from ken) Date: Fri, 27 Oct 2006 12:41:43 -0600 From: "Kenneth D. Merry" To: mjacob@freebsd.org Message-ID: <20061027184143.GA70768@nargothrond.kdm.org> References: <20061027090957.V60559@ns1.feral.com> <20061027183235.GA70290@nargothrond.kdm.org> <20061027113922.M61368@ns1.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061027113922.M61368@ns1.feral.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2126/Fri Oct 27 07:48:55 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 18:41:44 -0000 On Fri, Oct 27, 2006 at 11:39:47 -0700, mjacob@freebsd.org wrote: > > > >On Fri, Oct 27, 2006 at 09:10:43 -0700, mjacob@freebsd.org wrote: > >> > >>Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the > >>bullet now and move ahead? > > > >I think it's a good idea. We'll need to figure out how to handle the > >drivers that haven't had the code implemented for them yet. > > > > I was going to at least handle the in-tree ones. Great! Thanks for being willing to take it on! Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 21:40:24 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FB5A16A415 for ; Fri, 27 Oct 2006 21:40:24 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3C3343D62 for ; Fri, 27 Oct 2006 21:40:23 +0000 (GMT) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k9RLeMDx087083 for ; Fri, 27 Oct 2006 23:40:22 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.13.8/8.13.8/Submit) id k9RLeMdW087082 for freebsd-scsi@freebsd.org; Fri, 27 Oct 2006 17:40:22 -0400 (EDT) (envelope-from cracauer) Date: Fri, 27 Oct 2006 17:40:22 -0400 From: Martin Cracauer To: freebsd-scsi@freebsd.org Message-ID: <20061027214011.GB86642@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: Why is SCSI so much faster with the write cache off (than ATA)? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 21:40:24 -0000 I have observed it several times and I am missing one bit of knowledge here: why is SCSI so much faster when you turn off the write cache than P-ATA and SATA? P-ATA and SATA crumble to about 1/10th of the speed (just writing one file with 8k blocks linear), whereas SCSI just loses 10-20%, for me. I have observed that 10 years ago with some 8 GB ATA IBM disk on the BX chipset versus some 4 GB Quantum Atlas, and now I see it again with Seagate 7200.7s and .8s versus a 10K Compaq labled 36 GB drive. Personally I don't see why a linear write should be slow at all. Surely the computer delivers the data fast enough for sectors to be filled as they pass under the head. Maybe the ATA disks lose one rotation per sector or per filesystem block written anyway? Then why don't SCSI disks lose the same way given they are not allowed to cache anything either? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 21:56:49 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 815B516A415 for ; Fri, 27 Oct 2006 21:56:49 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14B6B43D7C for ; Fri, 27 Oct 2006 21:56:48 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([165.236.175.187]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9RLucLR012836; Fri, 27 Oct 2006 15:56:44 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <45428091.9030208@samsco.org> Date: Fri, 27 Oct 2006 15:56:33 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <20061027214011.GB86642@cons.org> In-Reply-To: <20061027214011.GB86642@cons.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: Why is SCSI so much faster with the write cache off (than ATA)? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 21:56:49 -0000 Martin Cracauer wrote: > I have observed it several times and I am missing one bit of knowledge > here: > > why is SCSI so much faster when you turn off the write cache than > P-ATA and SATA? > > P-ATA and SATA crumble to about 1/10th of the speed (just writing one > file with 8k blocks linear), whereas SCSI just loses 10-20%, for me. > I have observed that 10 years ago with some 8 GB ATA IBM disk on the > BX chipset versus some 4 GB Quantum Atlas, and now I see it again with > Seagate 7200.7s and .8s versus a 10K Compaq labled 36 GB drive. > > Personally I don't see why a linear write should be slow at all. > Surely the computer delivers the data fast enough for sectors to be > filled as they pass under the head. Maybe the ATA disks lose one > rotation per sector or per filesystem block written anyway? Then why > don't SCSI disks lose the same way given they are not allowed to cache > anything either? > > Martin The answer: Tagged Queueing The drive can collect a bunch of I/O requests, sort them for optimal layout, then stream their data in all at once. This is not the same thing as buffering through the write cache, but it has a similar performance benefit. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 22:04:56 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4C7416A415 for ; Fri, 27 Oct 2006 22:04:56 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C8A843D4C for ; Fri, 27 Oct 2006 22:04:54 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id k9RM4pjn079299; Fri, 27 Oct 2006 16:04:51 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id k9RM4pVj079298; Fri, 27 Oct 2006 16:04:51 -0600 (MDT) (envelope-from ken) Date: Fri, 27 Oct 2006 16:04:50 -0600 From: "Kenneth D. Merry" To: Martin Cracauer Message-ID: <20061027220450.GA78909@nargothrond.kdm.org> References: <20061027214011.GB86642@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061027214011.GB86642@cons.org> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2126/Fri Oct 27 07:48:55 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: Why is SCSI so much faster with the write cache off (than ATA)? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 22:04:57 -0000 On Fri, Oct 27, 2006 at 17:40:22 -0400, Martin Cracauer wrote: > I have observed it several times and I am missing one bit of knowledge > here: > > why is SCSI so much faster when you turn off the write cache than > P-ATA and SATA? > > P-ATA and SATA crumble to about 1/10th of the speed (just writing one > file with 8k blocks linear), whereas SCSI just loses 10-20%, for me. > I have observed that 10 years ago with some 8 GB ATA IBM disk on the > BX chipset versus some 4 GB Quantum Atlas, and now I see it again with > Seagate 7200.7s and .8s versus a 10K Compaq labled 36 GB drive. > > Personally I don't see why a linear write should be slow at all. > Surely the computer delivers the data fast enough for sectors to be > filled as they pass under the head. Maybe the ATA disks lose one > rotation per sector or per filesystem block written anyway? Then why > don't SCSI disks lose the same way given they are not allowed to cache > anything either? I would probably look at the tagged queueing behavior on both drives for an answer. With write caching turned off, the only way to get more than one transaction down onto the disk is tagged queueing. 10 years ago, ATA disks didn't do tagged queueing, but SCSI disks did. So if you have enough commands outstanding, the drive can maintain decent throughput putting them out on the disk. Without it, you have to wait for the head to get into position and the sector to come around to start writing. Once you're done writing, you have to wait for the initiator to send another request down. Now, SATA disks have tagged queueing and also NCQ. In theory those should work well. Is tagged queueing enabled on the ATA disks you're testing? Is it the old-style queueing or NCQ? Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 22:23:54 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B337616A403 for ; Fri, 27 Oct 2006 22:23:54 +0000 (UTC) (envelope-from asstec@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA96543D53 for ; Fri, 27 Oct 2006 22:23:53 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id k9RMNpex033298; Fri, 27 Oct 2006 19:23:51 -0300 (BRT) (envelope-from asstec@matik.com.br) From: AT Matik Organization: Infomatik To: freebsd-scsi@freebsd.org, "Kenneth D. Merry" Date: Fri, 27 Oct 2006 19:25:36 -0300 User-Agent: KMail/1.9.4 References: <20061027214011.GB86642@cons.org> <20061027220450.GA78909@nargothrond.kdm.org> In-Reply-To: <20061027220450.GA78909@nargothrond.kdm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200610271925.37069.asstec@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: Why is SCSI so much faster with the write cache off (than ATA)? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 22:23:54 -0000 On Friday 27 October 2006 19:04, Kenneth D. Merry wrote: > work well. =A0Is tagged queueing enabled on the ATA disks you're testing?= =A0Is > it the old-style queueing or NCQ? hi since it seems you're into this can you give further info how NCQ is relate= d=20 to the OS? how we can manage NCQ on OS level? Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 27 22:31:25 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D15C16A403; Fri, 27 Oct 2006 22:31:25 +0000 (UTC) (envelope-from Johannes.Kruger@nokia.com) Received: from mgw-ext13.nokia.com (mgw-ext13.nokia.com [131.228.20.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C3D143D45; Fri, 27 Oct 2006 22:31:24 +0000 (GMT) (envelope-from Johannes.Kruger@nokia.com) Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.10) with ESMTP id k9RMVIPn031373; Sat, 28 Oct 2006 01:31:22 +0300 Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Oct 2006 01:30:55 +0300 Received: from daebe102.NOE.Nokia.com ([10.241.35.115]) by daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 27 Oct 2006 17:30:52 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 27 Oct 2006 17:30:52 -0500 Message-ID: In-Reply-To: <20061027111434.E61368@ns1.feral.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: CAM_NEW_TRAN Thread-Index: Acb5/hoYxESEZOImQZqhF+h26wUNXgAEbNCg From: To: , X-OriginalArrivalTime: 27 Oct 2006 22:30:52.0318 (UTC) FILETIME=[8F5EBBE0:01C6FA17] X-Nokia-AV: Clean Cc: Johannes.Kruger@nokia.com Subject: RE: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 22:31:25 -0000 Hi Matthew. Seeing you guys talking about the CAM_NEW_TRAN, I just want to mention that I got the LSI1064 and LSI1064E to work with the mpt driver .. and yes, I used the NEW CAM code. So the background is that I took the mpt driver and ported it to a OS that is the equivalent of FreeBSD-2.X.X with some alterations. To make a long story short our OS needed more recent CAM code to work with mpt. So this is what I needed to do to make it (mpt) work (remember RAID-1 was slow in FreeBSD and the OS I was working on). These are just hacks to give you some data: 1) In order for the RAID-1 volume to be probed in IOC Page 2, I had to force the port to on first, otherwise the RAID personality would not successfully probe the RAID-1 volume. In the file mpt.c I changed: if (portenable) { to if (1) { 2) Some changes in the Firmware: - Port numbers in the PHY's was all 0 for Wide configs, so I made PHY0 a 0 and changed PHY1 from 0 to 1, Port setting in SAS IO Unit Page 1 - RAID Volume Page 0, IM VolumeSettings set to 0x5, IS VolumeSettings = =3D 0x1 - ResyncRate set low =3D 0x2 - IOC Page 1 (Think these are needed for speed increase) from 15 MB/s to 32 MB/s - Doubled Coalescing Depth from 0x4 to 0x8 - Halfed the CoalecingTimeout from 0x10 to 0x8 - Enabled NCQ (made a bit difference) - Also, in one of the registers there is a setting to specify if it's via expander or directly attached. Changed this to "directly attached" via the SATA/SAS cables. 3) Works fine for SATA, then I tested SAS. I got 50-52 MB/s for SAS drives running 7200rpm versus 30 MB/s for SATA at 4500rpm It's small laptop size drives. But ... when I remove the drives, and I re-insert it, I would get "Invalidating pack" messages from the CAM code. Turns out that the SAS drives takes a while to spin up. It actually sounds like it's changing gears or something :-), distinctive sound difference in a multistep spinup ... interesting. Have to go read what the powerup sequence for SAS drives are. So, for now I added a delay of 10 seconds if the volume flags indicates failure and now the re-insert is fine. I Might change this to a poll ... but I see there is some settings regarding spinup delay and IOC report time before indicating the drive presence, thant might work. In function mpt_refresh_raid_data ----------------------- snippet ----------------------- . . CONFIG_PAGE_RAID_VOL_0 *vol_pg; size_t len; int rv; int i; int settle =3D 10; <############# ADDED THIS #######> u_int nonopt_volumes; . . . . if (vol_pg->VolumeStatus.State !=3D MPI_RAIDVOL0_STATUS_STATE_OPTIMAL) nonopt_volumes++; if ((mpt_vol->flags & MPT_RVF_UP2DATE) !=3D 0) continue; ################> ADDED PARTS BETWEEN IFDEF and defined it <####################### #ifdef SAS_SLOW_START if (mpt_vol->config_page->VolumeStatus.State =3D=3D MPI_RAIDVOL0_STATUS_STATE_FAILED) { printf("Waiting %d seconds for device to settle ", =20 settle); while (settle) { settle--; DELAY(1000000); printf("."); } printf("\n"); mpt->raid_nonopt_volumes =3D nonopt_volumes; return (0); } #endif mpt_vol->flags |=3D MPT_RVF_UP2DATE; ----------------------- snippet ----------------------- Anyway, this is just some more data that can help, because I want this to work well on FreeBSD. Johan -----Original Message----- From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd-scsi@freebsd.org]=20 Sent: Friday, October 27, 2006 2:15 PM To: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN I can take on most of the work. > mjacob@freebsd.org wrote: >>=20 >> Is there any reason to *not* proceed with CAM_NEW_TRAN and just bite the=20 >> bullet now and move ahead? >>=20 > > I have no objection against it. > > Scott > _______________________________________________ freebsd-scsi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-scsi To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 01:54:06 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60AA516A407 for ; Sat, 28 Oct 2006 01:54:06 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2F3E43D45 for ; Sat, 28 Oct 2006 01:54:05 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9S1rx5g014280; Fri, 27 Oct 2006 19:54:04 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4542B836.8090304@samsco.org> Date: Fri, 27 Oct 2006 19:53:58 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 MIME-Version: 1.0 To: AT Matik References: <20061027214011.GB86642@cons.org> <20061027220450.GA78909@nargothrond.kdm.org> <200610271925.37069.asstec@matik.com.br> In-Reply-To: <200610271925.37069.asstec@matik.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org, "Kenneth D. Merry" Subject: Re: Why is SCSI so much faster with the write cache off (than ATA)? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 01:54:06 -0000 AT Matik wrote: > On Friday 27 October 2006 19:04, Kenneth D. Merry wrote: >> work well. Is tagged queueing enabled on the ATA disks you're testing? Is >> it the old-style queueing or NCQ? > > > hi > > since it seems you're into this can you give further info how NCQ is related > to the OS? how we can manage NCQ on OS level? > > Joćo > > FreeBSD doesn't support either form of ATA/SATA tagged queueing, yet. Scott From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 02:03:08 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D89FA16A403 for ; Sat, 28 Oct 2006 02:03:08 +0000 (UTC) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4983743D4C for ; Sat, 28 Oct 2006 02:03:07 +0000 (GMT) (envelope-from cracauer@koef.zs64.net) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k9S236vl093677; Sat, 28 Oct 2006 04:03:06 +0200 (CEST) (envelope-from cracauer@koef.zs64.net) Received: (from cracauer@localhost) by koef.zs64.net (8.13.8/8.13.8/Submit) id k9S236bg093676; Fri, 27 Oct 2006 22:03:06 -0400 (EDT) (envelope-from cracauer) Date: Fri, 27 Oct 2006 22:03:06 -0400 From: Martin Cracauer To: "Kenneth D. Merry" Message-ID: <20061028020306.GA93408@cons.org> References: <20061027214011.GB86642@cons.org> <20061027220450.GA78909@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061027220450.GA78909@nargothrond.kdm.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-scsi@freebsd.org, Martin Cracauer Subject: Re: Why is SCSI so much faster with the write cache off (than ATA)? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 02:03:08 -0000 Kenneth D. Merry wrote on Fri, Oct 27, 2006 at 04:04:50PM -0600: > 10 years ago, ATA disks didn't do tagged queueing, but SCSI disks did. I actually had used some of the rare IBM drives and the Intel 440BX chipset that did support it at the time. But some bit must have been missing. > Now, SATA disks have tagged queueing and also NCQ. In theory those should > work well. Is tagged queueing enabled on the ATA disks you're testing? Is > it the old-style queueing or NCQ? I was done on an NVidia SATA controller, so neither would be available. Very interesting. Now that I think about it all makes sense. Thanks, guys. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 13:41:24 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED33F16A412 for ; Sat, 28 Oct 2006 13:41:24 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87FB443D5D for ; Sat, 28 Oct 2006 13:41:24 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1GdoR8-0007SG-Re; Sat, 28 Oct 2006 15:41:22 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Scott Long In-reply-to: Your message of Fri, 27 Oct 2006 10:58:29 -0600 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 28 Oct 2006 15:41:22 +0200 From: Danny Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 13:41:25 -0000 some questions: - appart from the source, is there some document? - how does/will this affect my iSCSI driver? cheers, danny From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 16:08:19 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F38D916A403 for ; Sat, 28 Oct 2006 16:08:18 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E4143D6D for ; Sat, 28 Oct 2006 16:08:18 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9SG8IIY069039 for ; Sat, 28 Oct 2006 09:08:18 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9SG8IAp069036 for ; Sat, 28 Oct 2006 09:08:18 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Sat, 28 Oct 2006 09:08:17 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-scsi@freebsd.org In-Reply-To: <20061027184143.GA70768@nargothrond.kdm.org> Message-ID: <20061028090155.R69020@ns1.feral.com> References: <20061027090957.V60559@ns1.feral.com> <20061027183235.GA70290@nargothrond.kdm.org> <20061027113922.M61368@ns1.feral.com> <20061027184143.GA70768@nargothrond.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 16:08:19 -0000 There a number of SIMs that need changes for the CAM_NEW_TRAN code- I can't test them all, but it's a pretty straightforward exercise to do this. My plan is to add all of the changes so that LINT+CAM_NEW_TRAN_CODE compiles and otherwise test what I have h/w for and check that in. Once that's done, I'll send an announcement out about a cutover date in -current to the CAM_NEW_TRAN_CODE which is going to be the only way to actually get this in place and actually tested, and either remove the non-CAM_NEW_TRAN_CODE or change the definition so we have CAM_OLD_TRAN_CODE. Questions: a) If anyone wants reviews of the changes, please say so now. I'll try and send diffs to all and sundry as I go along, but I may forget. Again, the changes are expected relatively small b) Should I retain the old code? I would think not. I mean, this stuff has been around for years and it just clutters up the screen for the old stuff. -matt From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 18:04:39 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83C8F16A4D8; Sat, 28 Oct 2006 18:04:39 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D719543D78; Sat, 28 Oct 2006 18:04:04 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([165.236.175.187]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k9SI3s0L020276; Sat, 28 Oct 2006 12:04:00 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <45439B85.5010808@samsco.org> Date: Sat, 28 Oct 2006 12:03:49 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mjacob@freebsd.org References: <20061027090957.V60559@ns1.feral.com> <20061027183235.GA70290@nargothrond.kdm.org> <20061027113922.M61368@ns1.feral.com> <20061027184143.GA70768@nargothrond.kdm.org> <20061028090155.R69020@ns1.feral.com> In-Reply-To: <20061028090155.R69020@ns1.feral.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: CAM_NEW_TRAN X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 18:04:39 -0000 mjacob@freebsd.org wrote: > > There a number of SIMs that need changes for the CAM_NEW_TRAN code- I > can't test them all, but it's a pretty straightforward exercise to do this. > > My plan is to add all of the changes so that LINT+CAM_NEW_TRAN_CODE > compiles and otherwise test what I have h/w for and check that in. > > Once that's done, I'll send an announcement out about a cutover date in > -current to the CAM_NEW_TRAN_CODE which is going to be the only way to > actually get this in place and actually tested, and either remove the > non-CAM_NEW_TRAN_CODE or change the definition so we have > CAM_OLD_TRAN_CODE. > > Questions: > > a) If anyone wants reviews of the changes, please say so now. I'll try > and send diffs to all and sundry as I go along, but I may forget. Again, > the changes are expected relatively small > Yes, I need to consider it for locking. > b) Should I retain the old code? I would think not. I mean, this stuff > has been around for years and it just clutters up the screen for the old > stuff. No need to retain the old code. There are API changes coming for locking, anyways. Scott From owner-freebsd-scsi@FreeBSD.ORG Sat Oct 28 23:20:57 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E64916A40F; Sat, 28 Oct 2006 23:20:57 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACBC843D5F; Sat, 28 Oct 2006 23:20:53 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id k9SNKrs4077378; Sat, 28 Oct 2006 16:20:53 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id k9SNKrwd077375; Sat, 28 Oct 2006 16:20:53 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Sat, 28 Oct 2006 16:20:53 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Message-ID: <20061028161915.D77338@ns1.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: 'ncr' driver users? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2006 23:20:57 -0000 Does anyone out there *have* to have the old NCR driver for -current FreeBSD? -matt