From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 23 11:06:54 2013 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA6FB5D0 for ; Mon, 23 Dec 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9666C11D6 for ; Mon, 23 Dec 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rBNB6sAf030137 for ; Mon, 23 Dec 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rBNB6sb2030135 for freebsd-scsi@FreeBSD.org; Mon, 23 Dec 2013 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Dec 2013 11:06:54 GMT Message-Id: <201312231106.rBNB6sb2030135@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Dec 2013 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/184059 scsi [mps] mps SCSI driver causes FreeBSD to hang during bo o kern/179932 scsi [ciss] ciss i/o stall problem with HP Bl Gen8 (and HP o kern/178795 scsi [mps] MSI for mps driver doesn't work under vmware o kern/165982 scsi [mpt] mpt instability, drive resets, and losses on Fre o kern/165740 scsi [cam] SCSI code must drain callbacks before free f kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c o kern/148083 scsi [aac] Strange device reporting o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 f kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus f kern/123674 scsi [ahc] ahc driver dumping o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc 15 problems total. From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 27 22:05:34 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34DB1247; Fri, 27 Dec 2013 22:05:34 +0000 (UTC) Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ED99F1343; Fri, 27 Dec 2013 22:05:33 +0000 (UTC) Received: by mail-ie0-f169.google.com with SMTP id e14so10263775iej.28 for ; Fri, 27 Dec 2013 14:05:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=Kb+WVzLejRdFF3KnhDoI/0MMdG/2BkW0FS5tAZ+KCYM=; b=K8Ejp6kK7Ym5D91OtAh4IYB15APX39Yxt2bEC1ujgngebujwKBrgjR7PaAJUmOrZXW qQa5dNShH956fZmBwvQQ7ZswkYiVokgp+QovjWFEUWKwoN/AavAOloUB35WTPxUIq3tx AYpbk4/rcS6OAKtA+sdw+2K+ZfeLpzIY/BXNf6FGUu2kci1m6mVh3NQ86tpblpnbDUWq ZcDMQ5cauIGph+7HbeZ4O8CGATM0rC6d2+K+kK5cGeABiC39izKUJbMc/0L4PAIO61Vn /2jZ05YduE/fy7DbjufRqU/E4pCI4O/96ejOptAMJQFnSYgMRXjgwS12Ws1dDUCEmBLE FiXg== X-Received: by 10.50.147.1 with SMTP id tg1mr10639870igb.32.1388181933381; Fri, 27 Dec 2013 14:05:33 -0800 (PST) Received: from charmander.home (bas2-toronto08-2925231385.dsl.bell.ca. [174.91.125.25]) by mx.google.com with ESMTPSA id l7sm44997912igx.2.2013.12.27.14.05.31 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Dec 2013 14:05:32 -0800 (PST) Sender: Mark Johnston Date: Fri, 27 Dec 2013 17:04:55 -0500 From: Mark Johnston To: freebsd-scsi@freebsd.org Subject: mfi(4) support for MegaRAID Fury cards Message-ID: <20131227220455.GA6027@charmander.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) Cc: ambrisko@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Dec 2013 22:05:34 -0000 Hello, The patch here adds mfi(4) support for my LSI 9341-4i controller, which has device ID 0x5f: http://people.freebsd.org/~markj/patches/mfi_fury.diff This diff was mostly obtained by going through the mrsas(4) code specific to Invader (DID 0x5d) and Fury (DID 0x5f) controllers. The main change is to add an end-of-list marker to scatter-gather DMA lists before handing them to the firmware. Without this, large writes to an mfi(4) volume result in a firmware crash loop, and the system needs to be reset. The diff adds code for both Invader and Fury cards, as this is what's done in mrsas(4); I haven't tested with an Invader card though, as I don't have access to one. With this patch, I'm able to boot FreeBSD 8.2 off of a RAID 1 volume on my 9341-4i. Would anyone be able to review or test this patch? I'm particularly interested if anyone could try it out with an Invader or Fury card (there shouldn't be any differences in driver behaviour with other cards). Thanks! -Mark