From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 11 12:40:56 2014 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 7CF5B71A; Mon, 11 Aug 2014 12:40:56 +0000 (UTC) Received: from sinkng.sics.se (unknown [IPv6:2001:6b0:3a:1:c654:44ff:fe45:117c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EAA672145; Mon, 11 Aug 2014 12:40:55 +0000 (UTC) Received: from P142s.sics.se (P142s.sics.se [193.10.66.127]) by sinkng.sics.se (8.14.9/8.14.9) with ESMTP id s7BCdK0b019095 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Aug 2014 14:39:20 +0200 (CEST) (envelope-from bengta@P142s.sics.se) Received: from P142s.sics.se (localhost [127.0.0.1]) by P142s.sics.se (8.14.9/8.14.9) with ESMTP id s7BCd0Xb002849; Mon, 11 Aug 2014 14:39:00 +0200 (CEST) (envelope-from bengta@P142s.sics.se) Received: (from bengta@localhost) by P142s.sics.se (8.14.9/8.14.9/Submit) id s7BCcxeT002848; Mon, 11 Aug 2014 14:38:59 +0200 (CEST) (envelope-from bengta@P142s.sics.se) From: Bengt Ahlgren To: Garrett Wollman Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers In-Reply-To: <21474.34330.572142.206098@hergotha.csail.mit.edu> (Garrett Wollman's message of "Wed, 6 Aug 2014 15:46:34 -0400") References: <21474.34330.572142.206098@hergotha.csail.mit.edu> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) Date: Mon, 11 Aug 2014 14:38:59 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2014 12:40:56 -0000 Garrett Wollman writes: > Remember about six months ago when I tested 9-stable on one of my big > NFS servers, and had it panic in the middle of the USB probe, but > ultimately bisected the problem to an update to the mps(4) driver? I > had to stop investigating and get the server working (which I did, by > installing 9.2 instead of something newer and presumably faster). I'm > at the point now where I'd like to upgrade my file servers to 9.3, and > I can't, because of this issue, so it's time to start tracking down > the bug again. > > I have two test servers now. 9.3 works just fine on one of them, and > panics on the other. The one it works on is slightly older, and has > an mpt(4) controller for the boot drives, as opposed to the system > where the panic happens, which is mps(4)-only. Both systems have two > SAS2116 controllers for external drives; the ones on the working > system have drives attached, and the ones on the non-working system > are not connected to anything (and in fact disabled in the BIOS for > now). > > Any experts want to suggest where to start (besides, obviously, > attaching a serial console, which I haven't done yet)? I saw one > change in the svn logs for 9.3 prior to the release which looked like > it might be a relevant fix, but it clearly hasn't improved anything > for my servers. I have a dual-mps (one Dell H200 and one LSI 9207) system now running 9.1 (w patched sys/kern/kern_intr.c) that I intend to upgrade to 9.3 shortly. Is it enough to boot a 9.3 memstick to provoke the issue? Bengt From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 11 13:54:19 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C734C6DE; Mon, 11 Aug 2014 13:54:19 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0682A9C; Mon, 11 Aug 2014 13:54:19 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id E829C20E7088A; Mon, 11 Aug 2014 13:54:11 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=AWL,BAYES_00,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1,HELO_NO_DOMAIN,RDNS_DYNAMIC,STOX_REPLY_TYPE autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id 233BC20E70885; Mon, 11 Aug 2014 13:54:08 +0000 (UTC) Message-ID: <4950FD3896C0468D83A599AC104E4D7A@multiplay.co.uk> From: "Steven Hartland" To: "Bengt Ahlgren" , "Garrett Wollman" References: <21474.34330.572142.206098@hergotha.csail.mit.edu> Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers Date: Mon, 11 Aug 2014 14:54:06 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2014 13:54:19 -0000 ----- Original Message ----- From: "Bengt Ahlgren" > Garrett Wollman writes: > >> Remember about six months ago when I tested 9-stable on one of my big >> NFS servers, and had it panic in the middle of the USB probe, but >> ultimately bisected the problem to an update to the mps(4) driver? I >> had to stop investigating and get the server working (which I did, by >> installing 9.2 instead of something newer and presumably faster). >> I'm >> at the point now where I'd like to upgrade my file servers to 9.3, >> and >> I can't, because of this issue, so it's time to start tracking down >> the bug again. >> >> I have two test servers now. 9.3 works just fine on one of them, and >> panics on the other. The one it works on is slightly older, and has >> an mpt(4) controller for the boot drives, as opposed to the system >> where the panic happens, which is mps(4)-only. Both systems have two >> SAS2116 controllers for external drives; the ones on the working >> system have drives attached, and the ones on the non-working system >> are not connected to anything (and in fact disabled in the BIOS for >> now). >> >> Any experts want to suggest where to start (besides, obviously, >> attaching a serial console, which I haven't done yet)? I saw one >> change in the svn logs for 9.3 prior to the release which looked like >> it might be a relevant fix, but it clearly hasn't improved anything >> for my servers. > > I have a dual-mps (one Dell H200 and one LSI 9207) system now running > 9.1 (w patched sys/kern/kern_intr.c) that I intend to upgrade to 9.3 > shortly. Is it enough to boot a 9.3 memstick to provoke the issue? I would take this thread with a pinch of salt until it can be proved its not a hardware issue. Regards Steve From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 11 20:59:55 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B70356E3; Mon, 11 Aug 2014 20:59:55 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 780912410; Mon, 11 Aug 2014 20:59:55 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s7BKxdDX037771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 11 Aug 2014 13:59:40 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s7BKxd5g037770; Mon, 11 Aug 2014 13:59:39 -0700 (PDT) (envelope-from jmg) Date: Mon, 11 Aug 2014 13:59:39 -0700 From: John-Mark Gurney To: Garrett Wollman Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers Message-ID: <20140811205939.GY83475@funkthat.com> Mail-Followup-To: Garrett Wollman , freebsd-stable@freebsd.org, freebsd-scsi@freebsd.org References: <21474.34330.572142.206098@hergotha.csail.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21474.34330.572142.206098@hergotha.csail.mit.edu> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Mon, 11 Aug 2014 13:59:40 -0700 (PDT) Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Aug 2014 20:59:55 -0000 Garrett Wollman wrote this message on Wed, Aug 06, 2014 at 15:46 -0400: > Remember about six months ago when I tested 9-stable on one of my big > NFS servers, and had it panic in the middle of the USB probe, but > ultimately bisected the problem to an update to the mps(4) driver? I > had to stop investigating and get the server working (which I did, by > installing 9.2 instead of something newer and presumably faster). I'm > at the point now where I'd like to upgrade my file servers to 9.3, and > I can't, because of this issue, so it's time to start tracking down > the bug again. > > I have two test servers now. 9.3 works just fine on one of them, and > panics on the other. The one it works on is slightly older, and has > an mpt(4) controller for the boot drives, as opposed to the system > where the panic happens, which is mps(4)-only. Both systems have two > SAS2116 controllers for external drives; the ones on the working > system have drives attached, and the ones on the non-working system > are not connected to anything (and in fact disabled in the BIOS for > now). > > Any experts want to suggest where to start (besides, obviously, > attaching a serial console, which I haven't done yet)? I saw one > change in the svn logs for 9.3 prior to the release which looked like > it might be a relevant fix, but it clearly hasn't improved anything > for my servers. One thing you could do is turn on DEBUG_MEMGUARD and DEBUG_REDZONE and see if they trigger... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 12 13:42:24 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7209D58E; Tue, 12 Aug 2014 13:42:24 +0000 (UTC) Received: from sinkng.sics.se (unknown [IPv6:2001:6b0:3a:1:c654:44ff:fe45:117c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DC6A72156; Tue, 12 Aug 2014 13:42:23 +0000 (UTC) Received: from P142s.sics.se (P142s.sics.se [193.10.66.127]) by sinkng.sics.se (8.14.9/8.14.9) with ESMTP id s7CDg86T022121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 12 Aug 2014 15:42:08 +0200 (CEST) (envelope-from bengta@P142s.sics.se) Received: from P142s.sics.se (localhost [127.0.0.1]) by P142s.sics.se (8.14.9/8.14.9) with ESMTP id s7CDfkqL002992; Tue, 12 Aug 2014 15:41:46 +0200 (CEST) (envelope-from bengta@P142s.sics.se) Received: (from bengta@localhost) by P142s.sics.se (8.14.9/8.14.9/Submit) id s7CDfjEL002991; Tue, 12 Aug 2014 15:41:45 +0200 (CEST) (envelope-from bengta@P142s.sics.se) From: Bengt Ahlgren To: "Steven Hartland" Subject: Re: 9.3-RELEASE still instapanics on multi-mps(4) servers In-Reply-To: <4950FD3896C0468D83A599AC104E4D7A@multiplay.co.uk> (Steven Hartland's message of "Mon, 11 Aug 2014 14:54:06 +0100") References: <21474.34330.572142.206098@hergotha.csail.mit.edu> <4950FD3896C0468D83A599AC104E4D7A@multiplay.co.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) Date: Tue, 12 Aug 2014 15:41:45 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org, Garrett Wollman X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 13:42:24 -0000 "Steven Hartland" writes: > ----- Original Message ----- > From: "Bengt Ahlgren" > > >> Garrett Wollman writes: >> >>> Remember about six months ago when I tested 9-stable on one of my big >>> NFS servers, and had it panic in the middle of the USB probe, but >>> ultimately bisected the problem to an update to the mps(4) driver? I >>> had to stop investigating and get the server working (which I did, by >>> installing 9.2 instead of something newer and presumably >>> faster). I'm >>> at the point now where I'd like to upgrade my file servers to 9.3, >>> and >>> I can't, because of this issue, so it's time to start tracking down >>> the bug again. >>> >>> I have two test servers now. 9.3 works just fine on one of them, and >>> panics on the other. The one it works on is slightly older, and has >>> an mpt(4) controller for the boot drives, as opposed to the system >>> where the panic happens, which is mps(4)-only. Both systems have two >>> SAS2116 controllers for external drives; the ones on the working >>> system have drives attached, and the ones on the non-working system >>> are not connected to anything (and in fact disabled in the BIOS for >>> now). >>> >>> Any experts want to suggest where to start (besides, obviously, >>> attaching a serial console, which I haven't done yet)? I saw one >>> change in the svn logs for 9.3 prior to the release which looked like >>> it might be a relevant fix, but it clearly hasn't improved anything >>> for my servers. >> >> I have a dual-mps (one Dell H200 and one LSI 9207) system now running >> 9.1 (w patched sys/kern/kern_intr.c) that I intend to upgrade to 9.3 >> shortly. Is it enough to boot a 9.3 memstick to provoke the issue? > > I would take this thread with a pinch of salt until it can be proved > its not a hardware issue. I have now tried a 9.3-REL memstick on my server (Dell PE R515). It booted just fine! Bengt From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 15 06:13:14 2014 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 E86BB4F0 for ; Fri, 15 Aug 2014 06:13:14 +0000 (UTC) Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAC352ABE for ; Fri, 15 Aug 2014 06:13:14 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id ij19so2551003vcb.39 for ; Thu, 14 Aug 2014 23:13:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=IvRrY87eHEM6T7I2eP15WtWfk8vz737qysae8phWKok=; b=gRBhlUSP6OoVhqDHMcsf+mbqMNSI0nYZLvkAu/VT67lhApDRplSq2Nh6kzzA9hhPWB xhlv3m4sWmXJn4o9iJj4JzZclljvzV0z+A9ATuV7Z8C6koS6UdjXxmvnbtjtoH8KKP4h HIwZXGwky2iaLIQKQtoUoj+Mfwzv0Hd33UTKxWAHOzxD9Viq8C4xAP9f2jcReKkAywJo drUuWlsXLCwgSoPN3FvMofzNbj8eEh4N7AOIf7aMT4vgjOywhL2NSPlDhcUz9mnmnDjL iWchMQKkjyQaP+W41QeRvBDAOBiEfBxr6Cdey4ITEMyQinGGbIU+hjAgab2dkQTDbBLm 7IRw== MIME-Version: 1.0 X-Received: by 10.220.79.68 with SMTP id o4mr7247412vck.38.1408083193466; Thu, 14 Aug 2014 23:13:13 -0700 (PDT) Received: by 10.221.65.131 with HTTP; Thu, 14 Aug 2014 23:13:13 -0700 (PDT) Date: Fri, 15 Aug 2014 02:13:13 -0400 Message-ID: Subject: CAM_REQ_CMP_ERR From: grarpamp To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2014 06:13:15 -0000 I get a lot of these. Searching doesn't say much about them. What do they mean? A user data corruption error? (Seems to happen at random locations, so I doubt this.) Can I bump the retry count somehow? (kern.cam.da.retry_count does not seem to do this.) Thanks. cam.h: CAM_REQ_CMP_ERR, /* CCB request completed with an error */ 8 STABLE r269631 kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR kernel: (da0:umass-sim0:0:0:0): Retrying command ... kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR kernel: (da0:umass-sim0:0:0:0): Error 5, Retries exhausted ugen3.2: at usbus3 umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:3:0:-1: Attached to scbus3 (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0? pass2 at umass-sim0 bus 0 scbus3 target 0 lun 0 pass2: Removable Direct Access SCSI-0 device pass2: Serial Number num pass2: 40.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: Serial Number num da0: 40.000MB/s transfers da0: sizeMB (count 512 byte sectors: 64H 32S/T sizeC) da0: quirks=0x2 da0: Delete methods: From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 15 21:31:04 2014 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 690B24B2 for ; Fri, 15 Aug 2014 21:31:04 +0000 (UTC) Received: from vsp-authed-02-02.binero.net (vsp-authed02.binero.net [195.74.38.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A86382CE7 for ; Fri, 15 Aug 2014 21:31:02 +0000 (UTC) Received: from smtp01.binero.se (unknown [195.74.38.28]) by vsp-authed-02-02.binero.net (Halon Mail Gateway) with ESMTPS; Fri, 15 Aug 2014 23:25:48 +0200 (CEST) Received: from [192.168.69.225] (c83-252-101-91.bredband.comhem.se [83.252.101.91]) (Authenticated sender: turbo@bayour.com) by smtp-08-01.atm.binero.net (Postfix) with ESMTPSA id 280583A1F9; Fri, 15 Aug 2014 23:25:42 +0200 (CEST) Subject: Re: Support for aoc-sas2lp-mv8? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Turbo Fredriksson In-Reply-To: <2D179406-C7BC-4678-B88F-F47B19B917FB@bayour.com> Date: Fri, 15 Aug 2014 23:25:07 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <09C1D204-E253-4046-B63D-F50DA996331F@bayour.com> References: <2D179406-C7BC-4678-B88F-F47B19B917FB@bayour.com> To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.1283) Cc: scsi@freebsd.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Aug 2014 21:31:04 -0000 Bumpt. No one? On Jan 31, 2014, at 3:01 PM, Turbo Fredriksson wrote: > Is there any plans on adding support for this (88SE9485) Marvell card? >=20 > I can, in some way at least, help fund this if someone have the = interest and > time to do it...