From owner-freebsd-hardware@FreeBSD.ORG Mon Apr 16 11:07:18 2012 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A28ED1065674 for ; Mon, 16 Apr 2012 11:07:18 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 710518FC08 for ; Mon, 16 Apr 2012 11:07:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3GB7IxO022395 for ; Mon, 16 Apr 2012 11:07:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3GB7H6R022393 for freebsd-hardware@FreeBSD.org; Mon, 16 Apr 2012 11:07:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 16 Apr 2012 11:07:17 GMT Message-Id: <201204161107.q3GB7H6R022393@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-hardware@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-hardware@FreeBSD.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Apr 2012 11:07:18 -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/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total. From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 17 03:07:54 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B95F0106564A for ; Tue, 17 Apr 2012 03:07:54 +0000 (UTC) (envelope-from bvowk@ualberta.ca) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6D48FC08 for ; Tue, 17 Apr 2012 03:07:54 +0000 (UTC) Received: by obqv19 with SMTP id v19so7565508obq.13 for ; Mon, 16 Apr 2012 20:07:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=voruvODKrBFYqaGYL464n8LpJlL4NhYfqiPwgyd2l0k=; b=bCZ7suf9Yh2+in4FH0TE7ANSINryiUDS+S5aCg+oXJQkiVKev4sKVfROT/sRwQKMlP sYJB61PlzZTSXNgzkOKJ+HDZygPncEJjrM7ZFVmpICz9HTP3UVwyDZjd0UtV8lP1qVEx bUUo50Pp68PxTqgy72feV1+rttc+LOTEZwGAYQ04+qzmgJijPj0ZDfpB/Yk0Vlyz7vP2 +0IyPsIsAA5qUR1BiP5x1tlXl3SSzhEz5Hs4qX9KdS7ZGCbJKAlnzfGUGxHKV8y183yL UyF4hUiz+lXdwiIgroeskLgXsjGp/0x10gBGqHSZVVgciYzMwgi8ZUj/YSWgDZ9lw/zF LAag== MIME-Version: 1.0 Received: by 10.182.136.104 with SMTP id pz8mr19237332obb.37.1334632073934; Mon, 16 Apr 2012 20:07:53 -0700 (PDT) Received: by 10.60.124.199 with HTTP; Mon, 16 Apr 2012 20:07:53 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Apr 2012 20:07:53 -0700 Message-ID: From: Barkley Vowk To: Tom Evans Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl+V6i0J72XiveM+lsn8Ks31enZEFEm2+v/9oALBb/KZy3L+dvCstz3ZW0/52JM1SRluNI4 Cc: freebsd-hardware@freebsd.org Subject: Re: Highpoint 2760A / Marvell 88SE9485 SAS HBA Drivers? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 03:07:54 -0000 There's a couple problems with the driver from HighPoint. It's giant locked, it's for 8.0, and it doesn't actually work. There are also no plans to update it according to Highpoint. On Fri, Apr 13, 2012 at 6:32 AM, Tom Evans wrote: > On Thu, Apr 12, 2012 at 6:14 PM, Barkley Vowk wrote: >> I've got a Highpoint 2760A card that I'd like a FreeBSD driver for, >> I've got a machine and disks available if someone wants to tackle >> that. >> >> Thanks! > > Highpoint do make their own FreeBSD drivers as well: > > http://www.highpoint-tech.com/BIOS_Driver/RR276x/freebsd/v1.0.10.0908/rr276x-bsd-8.0-v1.0.10.0908.tgz > > Cheers > > Tom > From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 17 11:06:42 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7C721065670 for ; Tue, 17 Apr 2012 11:06:42 +0000 (UTC) (envelope-from mw@emile.cs.uni-saarland.de) Received: from triton.rz.uni-saarland.de (triton.rz.uni-saarland.de [134.96.7.25]) by mx1.freebsd.org (Postfix) with ESMTP id 22E508FC1F for ; Tue, 17 Apr 2012 11:06:41 +0000 (UTC) Received: from mail.uni-sb.de (mail.uni-sb.de [134.96.7.230]) by triton.rz.uni-saarland.de (8.14.1/8.14.0) with ESMTP id q3HB6Ya3019711 for ; Tue, 17 Apr 2012 13:06:35 +0200 Received: from mail.cs.uni-saarland.de (mail.cs.uni-saarland.de [134.96.254.200]) by uni-sb.de (8.14.5/2011051800) with ESMTP id q3HB6S2e007651 for ; Tue, 17 Apr 2012 13:06:28 +0200 (CEST) Received: from dennis.cs.uni-saarland.de (dennis.cs.uni-saarland.de [134.96.243.128]) by mail.cs.uni-saarland.de (8.14.5/2011051800) with ESMTP id q3HB6RQ8023981 for ; Tue, 17 Apr 2012 13:06:27 +0200 (CEST) Received: from emile.cs.uni-saarland.de ([134.96.243.162]) by dennis.cs.uni-saarland.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SK6Et-0007By-La for freebsd-hardware@freebsd.org; Tue, 17 Apr 2012 13:06:27 +0200 Received: from mw by emile.cs.uni-saarland.de with local (Exim 4.76) (envelope-from ) id 1SK6Et-0007ww-Ep for freebsd-hardware@freebsd.org; Tue, 17 Apr 2012 13:06:27 +0200 Date: Tue, 17 Apr 2012 13:06:27 +0200 From: Moritz Wilhelmy To: freebsd-hardware@freebsd.org Message-ID: <20120417110627.GE22863@emile.cs.uni-saarland.de> References: <20120409203219.155060@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20120409203219.155060@gmx.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-DCC-wuwien-Metrics: mail.cs.uni-saarland.de; whitelist X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (triton.rz.uni-saarland.de [134.96.7.25]); Tue, 17 Apr 2012 13:06:35 +0200 (CEST) X-AntiVirus: checked by AntiVir MailGate (version: 2.1.2-14; AVE: 7.9.10.48; VDF: 7.11.27.198; host: AntiVir3) Subject: Re: PCI-X SATA (non HW-RAID) controller recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 11:06:42 -0000 Hi again, First off, sorry for the huge delay. On Mon, Apr 09, 2012 at 16:32:17 -0400, Dieter BSD wrote: > Moritz writes: > >> Can you (or someone else for that matter) recommend any decent PCI-X > >> controller for use in "serious environments" > > >> I heard Silicon Image cards are supposed to be good? > > > Just wondering, do you (or anyone else) know whether there are PCI-X > > SATA controllers with only 4 Ports with less issues than the ones > > already mentioned? :-) > > > > Maybe 4 are enough after all... > > What do you mean by "serious environments"? > > speed? reliability? harsh environment? support? other? Reliability sounds good.. So having SMART work is probably a good idea too :-) I won't hotplug disks all the time, so rebooting once in a while when a disk dies should not be an issue. This is going to be the SATA controller for an NFS Server which stores E-Mails and User home directories. Since network will probably be the bottleneck, speed is not as important as reliability. Vendor-Support is not that important, as long as the card is well-supported by FreeBSD. I also found Exys EX-3403, which is an 8-port SATA PCI-X card with a Marvell MV88SX6081 for about 100€, but the Exys apparently only Supports Windows - which shouldn't matter if at least the Chip is supported by FreeBSD, no? According to earlier posts to this list (Hello Stephane :-), this Chip works at least on 7.2. Can someone tell me more about it? > I have the Silicon Image 3132 which is PCIe-x1 with 2 sata ports. > Not as fast as it should be but fast enough for my needs. > Works well with FreeBSD siis(4), which provides NCQ. > Works well with the 3726 port multiplier. Talks to recent > 600MB/s drives at 300MB/s, unlike JMB363 which doesn't like > 600MB/s drives, even with the sata rev hint set. 300MB/s should be enough. > Look into the 3124 which has 4 ports and is IIRC PCI-X. > Said to be faster than the 3132. I'll take another look around. > You probably want to avoid the first generation Silicon Image > sata chips. They are very slow and word is that FreeBSD doesn't > support them very well. (NetBSD does have good support, but they > are still very slow.) Noted, thanks for the hint. > If you don't need ueber speed on multiple ports at once, > port multipliers are a good way to get more ports. Sounds useful, thanks. > Issue: if a port has a problem (flaky disk or whatever), siis(4) may > do a bunch of DELAY(big number) which interferes with other hardware > doing real-time data logging, causing data to be lost. Unacceptable. > Does not require power cycle though. I don't recall it even needing > a reboot. That doesn't sound good, but I guess somebody can tell me the issues of any controller or driver that comes up in this discussion. If you're OK with siis despite this, I should too. Sorry for being quite verbose on this list, but I believe in ruling out bad choices before actually buying hardware ;) Thanks, Moritz From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 17 23:01:36 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E233C106564A for ; Tue, 17 Apr 2012 23:01:36 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id 87FF98FC08 for ; Tue, 17 Apr 2012 23:01:36 +0000 (UTC) Received: (qmail 23228 invoked by uid 0); 17 Apr 2012 23:01:30 -0000 Received: from 67.206.184.108 by rms-us014.v300.gmx.net with HTTP Content-Type: text/plain; charset="utf-8" Date: Tue, 17 Apr 2012 19:01:28 -0400 From: "Dieter BSD" Message-ID: <20120417230129.155080@gmx.com> MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: HpP/b/Bd3zOlNR3dAHAhFQF+IGRvbwA3 Subject: Re: PCI-X SATA (non HW-RAID) controller recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 23:01:37 -0000 > having SMART work is probably a good idea Note that some (most?) of the USB-to-SATA bridges do not provide access to SMART, at least not on FreeBSD. Also can't turn off the write buffer, and no NCQ, and pathetically slow. >> I have the Silicon Image 3132 which is PCIe-x1 with 2 sata ports. >> Not as fast as it should be but fast enough for my needs. >> Works well with FreeBSD siis(4), which provides NCQ. >> Works well with the 3726 port multiplier. Talks to recent >> 600MB/s drives at 300MB/s, unlike JMB363 which doesn't like >> 600MB/s drives, even with the sata rev hint set. > > 300MB/s should be enough. With vanilla rotating drives even 150 is enough. Speed-wise, NCQ is far more important than 300 or 600. Problem is that recent drives are 600 and don't work with JMB363. Drives used to have a jumper to pretend to only talk 150, for controllers that didn't deal well with 300. But as far as I know there isn't any way to get the 600 drives to pretend to be only 150 or 300. >> Issue: if a port has a problem (flaky disk or whatever), siis(4) may >> do a bunch of DELAY(big number) which interferes with other hardware >> doing real-time data logging, causing data to be lost. Unacceptable. >> Does not require power cycle though. I don't recall it even needing >> a reboot. > > That doesn't sound good, but I guess somebody can tell me the issues of > any controller or driver that comes up in this discussion. If you're OK > with siis despite this, I should too. It isn't acceptable, but I've had similar/identical problems with ata(4) and ahci(4). For all I know maybe all the disk drivers do it. I think the problem is keeping interrupts off for too long. From owner-freebsd-hardware@FreeBSD.ORG Thu Apr 19 07:30:03 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D88AF106566B; Thu, 19 Apr 2012 07:30:03 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) by mx1.freebsd.org (Postfix) with ESMTP id B33F38FC14; Thu, 19 Apr 2012 07:30:03 +0000 (UTC) Received: from delta.delphij.net (unknown [IPv6:2001:470:83bf:0:221:5cff:fe6a:37bb]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 13514F5EE; Thu, 19 Apr 2012 00:30:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1334820603; bh=SthX9g9LAIITLYliDYHeM8d8LapIQuZAJRfTFx549oU=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=Ci0GbxGiknvgQLMS7Fm7iuUeLTV2a5cJ/XM8VhyJ43AwiKCj4LlS7M18BeDkvRhK2 cacJsiOKsB8HB/0w0LJb51t2OtigTztikyYPhWYoUzP4tHXn7hv4LrteHH6VMRHXcu sw2en6ycamNUMs2Knyzf9+yZYOWhcbz5JdpkxtlY= Message-ID: <4F8FBEEC.6060509@delphij.net> Date: Thu, 19 Apr 2012 00:29:48 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Barkley Vowk References: In-Reply-To: X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, d@delphij.net, freebsd-hardware@freebsd.org Subject: Re: Highpoint 2760A / Marvell 88SE9485 SAS HBA Drivers? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2012 07:30:04 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 04/12/12 10:14, Barkley Vowk wrote: > I've got a Highpoint 2760A card that I'd like a FreeBSD driver > for, I've got a machine and disks available if someone wants to > tackle that. Please try loading 'hpt27xx.ko' on boot. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPj77sAAoJEG80Jeu8UPuzoW4H/2KsdmWsV/HEERSkyPY/XX/B jJtEAZFFI6X4aYYqANyPXWWBA6mRy586GkZZNlClCw2v4cBxXAnWBWL49tcuJ0UP wURQt9/HU6P+EqbRSVZ98KhvufjvecjLavr9x6wCJ+L8pvc7trnD25l/Z0hTA96Y hIpwTcK/m0IXYopmC0WioPfyZWJx2Uu+DgrUUV6mXOZc9oDDf53v10rbGpQoNUZg GvKfL2Ql0rHZ13EJkjZdURcUj94Nas7pBgumGwedrsKs0NGnjRNmMlYSRzonqe0Z uBaWzqEiB01qNThfCpt0tnAS55wYU+QWmvF9hVSApSwmeCsrneluhyUjf9QJ8M8= =gUd0 -----END PGP SIGNATURE----- From owner-freebsd-hardware@FreeBSD.ORG Fri Apr 20 13:45:00 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 448251065672 for ; Fri, 20 Apr 2012 13:45:00 +0000 (UTC) (envelope-from VaNs9@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 646C38FC15 for ; Fri, 20 Apr 2012 13:44:59 +0000 (UTC) Received: from web7f.yandex.ru (web7f.yandex.ru [95.108.130.104]) by forward13.mail.yandex.net (Yandex) with ESMTP id 0D9FA1425E5 for ; Fri, 20 Apr 2012 17:44:58 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1334929498; bh=GP7emZJP0JRJIMmqJavJMOGFCgKpf8a2o5HpHrb9z2I=; h=From:To:Subject:MIME-Version:Message-Id:Date: Content-Transfer-Encoding:Content-Type; b=uwZlm0rRKTVFAwUBvzAe9wa3keYmuEGXaOprdONL3GYLOMm0AglliSryHbfVyGSnC sqx9wxcNXq5er27HhZf/Ada47JTUODKebWpfzPzAKc8xt5uU5ZtHkF2Vy0oxjRVCgS M5lHlBiwyA5nqef9smY7bhLMzn9+yw8xLJlEqEfg= Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web7f.yandex.ru (Yandex) with ESMTP id D0283CE0044; Fri, 20 Apr 2012 17:44:57 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1334929497; bh=GP7emZJP0JRJIMmqJavJMOGFCgKpf8a2o5HpHrb9z2I=; h=From:To:Subject:MIME-Version:Message-Id:Date: Content-Transfer-Encoding:Content-Type; b=L8E7/wPds/oGufd+ozqiey8JYd1gYX9yANBEeUWBB8zfmd92v3Gm/YHjnhTK0z9U1 EXYYAEZTAHBpMmJZUjNFFVUng1U2C21e3f+kRaCP95YSeOTM2LpHJ2OEySIIjkg39g TreUfJOGtYj0XMNusm5PPeFylh1VPZa0Enj4hYgk= Received: from 95-24-86-181.broadband.corbina.ru (95-24-86-181.broadband.corbina.ru [95.24.86.181]) by web7f.yandex.ru with HTTP; Fri, 20 Apr 2012 17:44:56 +0400 From: N V To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Message-Id: <729541334929496@web7f.yandex.ru> Date: Fri, 20 Apr 2012 17:44:56 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Subject: AMD FX 4100, hwpstate0, powerd X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 13:45:00 -0000 Hi. I've got AMD FX-4100, ASUS M5A97, FreeBSD amd 9.0-RELEASE. I've set hint.acpi_throttle.0.disabled="1" debug.hwpstate_verbose="1" in /boot/loader.conf to eliminate acpi_throttle issues and to home more verbose output. Also, I have performance_cx_lowest="LOW" economy_cx_lowest="LOW" in /etc/rc.conf If I try to enable powerd (via rc.conf) I get (parts of dmesg here): Copyright (c) 1992-2012 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 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: AMD FX(tm)-4100 Quad-Core Processor (3612.16-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x600f12 Family = 15 Model = 1 Stepping = 2 Features=0x178bfbff Features2=0x1698220b AMD Features=0x2e500800 AMD Features2=0x1c9bfff,> TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8158220288 (7780 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 16 cpu1 (AP): APIC ID: 17 cpu2 (AP): APIC ID: 18 cpu3 (AP): APIC ID: 19 ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20110527/tbfadt-586) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392) ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380) acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 450 Event timer "HPET2" frequency 14318180 Hz quality 450 .. attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: cannot reserve I/O port range hwpstate0: going to fetch info from acpi_perf hwpstate0: on cpu0 Timecounters tick every 1.000 msec .. Configuring syscons: keymap blanktime. Starting cron. Starting inetd. .. hwpstate0: setting P1-state on cpu0 hwpstate0: result P0-state on cpu0 hwpstate0: error: loop is not enough. hwpstate0: setting P1-state on cpu1 hwpstate0: result P1-state on cpu1 hwpstate0: setting P1-state on cpu2 hwpstate0: result P1-state on cpu2 hwpstate0: setting P1-state on cpu3 hwpstate0: result P1-state on cpu3 hwpstate0: set freq failed, err 6 hwpstate0: setting P1-state on cpu0 hwpstate0: result P1-state on cpu0 hwpstate0: setting P1-state on cpu1 hwpstate0: result P1-state on cpu1 hwpstate0: setting P1-state on cpu2 hwpstate0: result P1-state on cpu2 hwpstate0: setting P1-state on cpu3 hwpstate0: result P1-state on cpu3 hwpstate0: setting P2-state on cpu0 hwpstate0: result P1-state on cpu0 hwpstate0: error: loop is not enough. hwpstate0: setting P2-state on cpu1 hwpstate0: result P2-state on cpu1 hwpstate0: setting P2-state on cpu2 hwpstate0: result P2-state on cpu2 hwpstate0: setting P2-state on cpu3 hwpstate0: result P2-state on cpu3 hwpstate0: set freq failed, err 6 hwpstate0: setting P2-state on cpu0 hwpstate0: result P2-state on cpu0 hwpstate0: setting P2-state on cpu1 hwpstate0: result P2-state on cpu1 hwpstate0: setting P2-state on cpu2 hwpstate0: result P2-state on cpu2 hwpstate0: setting P2-state on cpu3 hwpstate0: result P2-state on cpu3 hwpstate0: setting P0-state on cpu0 hwpstate0: result P0-state on cpu0 hwpstate0: setting P0-state on cpu1 hwpstate0: result P0-state on cpu1 hwpstate0: setting P0-state on cpu2 hwpstate0: result P0-state on cpu2 hwpstate0: setting P0-state on cpu3 hwpstate0: result P0-state on cpu3 Or if I manually launch powerd: # powerd -v -n hadp powerd: unable to determine AC line status load 76%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 32%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 43%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 38%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 39%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 39%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 37%, current freq 3600 MHz ( 0), wanted freq 7200 MHz load 20%, current freq 3600 MHz ( 0), wanted freq 6975 MHz load 63%, current freq 3600 MHz ( 0), wanted freq 7200 MHz ^Ctotal joules used: 47.205 Is it something with BIOS and I can switch on/off something there, or is it something in FreeBSD and I can tune it, or is it something else? Regards, Vans. From owner-freebsd-hardware@FreeBSD.ORG Fri Apr 20 20:03:10 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9755F106566C for ; Fri, 20 Apr 2012 20:03:10 +0000 (UTC) (envelope-from gijsje@heteigenwijsje.nl) Received: from mail.heteigenwijsje.nl (156-49-223.ftth.xms.internl.net [85.223.49.156]) by mx1.freebsd.org (Postfix) with ESMTP id 2392E8FC12 for ; Fri, 20 Apr 2012 20:03:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.heteigenwijsje.nl (Postfix) with ESMTP id AAFE816117 for ; Fri, 20 Apr 2012 22:03:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=heteigenwijsje.nl; s=dkim; t=1334952188; bh=iGmt/DtO5TDVBjAccfVNxL/V2u6wTVudF9coZIaNOAg=; h=Date:From:To:Subject; b=bpl4k3wQF1PkRExf2uoh97ea7k9NKab+AwlfrZiFBq1USmKJfRbQp7sOyToMXZ9C5 K9uxc2XR0LKC0U7Su+UljNauhxXmL4khhyBqq4GtdxeqGjKzwXakabvmGWN/jg9eRA ne6qeVmaWOYh7espFx9Rwcp8UufjUrM6zm4rCdQQ= Received: from mail.heteigenwijsje.nl ([127.0.0.1]) by localhost (mail.heteigenwijsje.nl [127.0.0.1]) (maiad, port 10024) with ESMTP id 01957-03 for ; Fri, 20 Apr 2012 22:03:06 +0200 (CEST) Received: from [192.168.0.55] (unknown [192.168.0.55]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gijsje@heteigenwijsje.nl) by mail.heteigenwijsje.nl (Postfix) with ESMTPSA id 75DF716112 for ; Fri, 20 Apr 2012 22:03:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=heteigenwijsje.nl; s=dkim; t=1334952186; bh=iGmt/DtO5TDVBjAccfVNxL/V2u6wTVudF9coZIaNOAg=; h=Date:From:To:Subject; b=MezC8NSByhg50nkoMpEaYBN8tUsSwVyMIK3tRcdZ2P7N97893Xjv/ZkcZSFuNQCgY bQ0SXOcYJmBJwGoFJWstZaqYXJgkkZqmbrsNBPq+MyQjqdJyNM9B5ZpHc/gF99spXV y0sXWdd+VXe41gC19gBdcU6awBl5P3+bPiTKF14I= Message-ID: <4F91C0FC.9040000@heteigenwijsje.nl> Date: Fri, 20 Apr 2012 22:03:08 +0200 From: Gijs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.3 Subject: AHCI Time-outs while doing scrub or sysctl off line tests X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Apr 2012 20:03:10 -0000 Hey all, I'm running 9-Stable with a zfs pool containing 2 sets of 3 disks in raidz1. I added the second set of disks (3 times 1,5 samsung F2EG) after my first 3 got filled up (3x1tb only 50G left, it's baaad I know). After adding the second set of disks I noticed that during scrubs (wich would basicly be the highest load the system receives besides some bittorrent traffic and file serving) I would start receiving AHCI timeouts on ports 3-5, the newly added disks. Together with that scrub performance is increadibly bad, it dropped to below 900kb/s. This might be a result however of zfs fragmentation due to the first set being filled up way above the adviced 80% as well as it being filled up by torrent clients. After a port starts sending AHCI errors connection will be dropped after some time. If this happens I have to physically disconnect and reconnect the drive or do a full system halt (reboot/reset does not help) to get the functionality back. Motherboard is an Asus M4A89GTD Pro wich has an 890GX northbridge and an SB850 southbridge. I've been searching around a lot and did not find anything conclusive how to permanently fix this problem. Some posts seem to suggest that a "cheap" controller like the onboard one might suffer from the strain put on it by the heavy ZFS workloads, and thus start randomly dropping connections. Some posts suggest that the problem is in AHCI/NCQ and that disabling those results in resolution of the problems. During boot time the drives are indeed configured with NCQ turned on, camcontrol shows both NCQ and tagged queuing turned on for the 3 samsung drives wich fail, minimum tagged queue depth for tagged queueing is set at 32. Indeed disabling AHCI resulted in the disappearance of the AHCI time-outs, unfortunately of course also in a performance drop and loss of hot swap capabilities. The samsung F3EG drives had problems with NCQ in combination together with the SB850 southbridge, so this migh also be a cause into the problem, unfortunately seagate did not yet respond to my support question. As a loss of AHCI functionality is kinda big, I would like to see if toggling NCQ per drive is possible, and if it does resolve the problem. Any advice on this ? Cheers, Gijs From owner-freebsd-hardware@FreeBSD.ORG Sat Apr 21 00:16:43 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A16CE106564A for ; Sat, 21 Apr 2012 00:16:43 +0000 (UTC) (envelope-from bvowk@ualberta.ca) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 60B878FC08 for ; Sat, 21 Apr 2012 00:16:43 +0000 (UTC) Received: by obqv19 with SMTP id v19so14840411obq.13 for ; Fri, 20 Apr 2012 17:16:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=Oz71FcTBkLD/oiDt19Ai+YLrvaMjENV8/POUYu/9KrQ=; b=FL28pm6pKRS5NvtNoejuYQNdD/xBP7z3KlzhCfJHRf8yCMbeKGEf0dg9F8YQXsXR9S 5O5Dcxez6FnZyEsY/vtx4049NwaHJLJOHW8Jy4mpz6BZv7fpurURBOnbnBJgE6ar62vw myoqNOaM38aMzOTMJugUWXqNWOaTV5mUwZHWfB5e+6VnKyQ7PKDqIt9yq8TujI0fDpMP ty3cbet0gRhwKRdrvrS66Rzj6eF1eBptwlOPhK5kdj/gTChg+19Zm5sQs3HqcA76yk2v d0VK8GTaQUSRS3+whDs+kvorLVG0anrDzEW+1k6h5MWSB881KZNDSXSul+AGKe3mkWPg IzmQ== MIME-Version: 1.0 Received: by 10.60.18.137 with SMTP id w9mr11452854oed.7.1334967402932; Fri, 20 Apr 2012 17:16:42 -0700 (PDT) Received: by 10.60.124.199 with HTTP; Fri, 20 Apr 2012 17:16:42 -0700 (PDT) In-Reply-To: <4F8FBEEC.6060509@delphij.net> References: <4F8FBEEC.6060509@delphij.net> Date: Fri, 20 Apr 2012 17:16:42 -0700 Message-ID: From: Barkley Vowk To: d@delphij.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnsAeXZ88Ie34VuejdNYt9+bEzkhXFFHLPbe1DIkp/qWVx7cRAuA5d611NIpd9eWWhtOXav Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Highpoint 2760A / Marvell 88SE9485 SAS HBA Drivers? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2012 00:16:43 -0000 It doesn't seem to work. I've got 22 2.0TB SATA disks, and a 120GB Intel SSD attached, I get these messages, and the drives all show in dmesg and /dev. But if I try writing to any of them, the process just hangs. Anyone reported success with the 2760A? hpt27xx: RocketRAID 27xx controller driver v1.0 (Apr 19 2012 11:02:42) hpt27xx: Attached device index 00 (Path 00 | Target 00 | E0/Sff) 500c5020e= 95b8d hpt27xx: Attached device index 01 (Path 01 | Target 00 | E0/Sff) 500c5020e= 96089 hpt27xx: Attached device index 02 (Path 02 | Target 00 | E0/Sff) 500c50104= 39cd5 hpt27xx: Attached device index 03 (Path 03 | Target 00 | E0/Sff) 500c5020c= 75ac1 hpt27xx: Attached device index 00 (Path 00 | Target 00 | E0/Sff) 500c5020e= 9918d hpt27xx: Attached device index 01 (Path 01 | Target 00 | E0/Sff) 500c5020e= 987f9 hpt27xx: Attached device index 02 (Path 02 | Target 00 | E0/Sff) 500c5020d= 1add hpt27xx: Attached device index 03 (Path 03 | Target 00 | E0/Sff) 500c5020e= 2205d hpt27xx: Attached device index 40 (Path 04 | Target 00 | E0/Sff) 500c5020e= 387f1 hpt27xx: Attached device index 41 (Path 05 | Target 00 | E0/Sff) 500c5020e= 4eadd hpt27xx: Attached device index 42 (Path 06 | Target 00 | E0/Sff) 500c5020e= 47ff1 hpt27xx: Attached device index 43 (Path 07 | Target 00 | E0/Sff) 500c5020e= 4ec91 hpt27xx: Attached device index 40 (Path 04 | Target 00 | E0/Sff) 500c5020e= 9607d hpt27xx: Attached device index 41 (Path 05 | Target 00 | E0/Sff) 500c5020e= 4801 hpt27xx: Attached device index 42 (Path 06 | Target 00 | E0/Sff) 500c5020e= 4e7f1 hpt27xx: Attached device index 43 (Path 07 | Target 00 | E0/Sff) 500c5020d= 0ec39 hpt27xx: Attached device index 00 (Path 00 | Target 00 | E0/Sff) 500c5020e= 95b91 hpt27xx: Attached device index 01 (Path 01 | Target 00 | E0/Sff) 00000000 hpt27xx: Attached device index 02 (Path 02 | Target 00 | E0/Sff) 500c5020e= 96359 hpt27xx: Attached device index 03 (Path 03 | Target 00 | E0/Sff) 500c5020e= 4e629 hpt27xx: Attached device index 40 (Path 04 | Target 00 | E0/Sff) 500c5020d= 2d69d hpt27xx: Attached device index 41 (Path 05 | Target 00 | E0/Sff) 500c5020e= 95b11 hpt27xx: Attached device index 42 (Path 06 | Target 00 | E0/Sff) 500c5020e= a1219 hpt27xx2: [GIANT-LOCKED] hpt27xx2: [ITHREAD] hpt27xx1: [GIANT-LOCKED] hpt27xx1: [ITHREAD] hpt27xx0: [GIANT-LOCKED] hpt27xx0: [ITHREAD] da0 at hpt27xx0 bus 0 scbus8 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da1 at hpt27xx0 bus 0 scbus8 target 1 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da2 at hpt27xx0 bus 0 scbus8 target 2 lun 0 da2: Fixed Direct Access SCSI-0 device da2: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da3 at hpt27xx0 bus 0 scbus8 target 3 lun 0 da3: Fixed Direct Access SCSI-0 device da3: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da4 at hpt27xx0 bus 0 scbus8 target 4 lun 0 da4: Fixed Direct Access SCSI-0 device da4: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da5 at hpt27xx0 bus 0 scbus8 target 5 lun 0 da5: Fixed Direct Access SCSI-0 device da5: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da6 at hpt27xx0 bus 0 scbus8 target 6 lun 0 da6: Fixed Direct Access SCSI-0 device da6: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da7 at hpt27xx0 bus 0 scbus8 target 7 lun 0 da7: Fixed Direct Access SCSI-0 device da7: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da8 at hpt27xx0 bus 0 scbus8 target 8 lun 0 da8: Fixed Direct Access SCSI-0 device da8: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da9 at hpt27xx0 bus 0 scbus8 target 9 lun 0 da9: Fixed Direct Access SCSI-0 device da9: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da10 at hpt27xx0 bus 0 scbus8 target 10 lun 0 da10: Fixed Direct Access SCSI-0 device da10: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da11 at hpt27xx0 bus 0 scbus8 target 11 lun 0 da11: Fixed Direct Access SCSI-0 device da11: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da12 at hpt27xx0 bus 0 scbus8 target 12 lun 0 da12: Fixed Direct Access SCSI-0 device da12: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da13 at hpt27xx0 bus 0 scbus8 target 13 lun 0 da13: Fixed Direct Access SCSI-0 device da13: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da14 at hpt27xx0 bus 0 scbus8 target 14 lun 0 da14: Fixed Direct Access SCSI-0 device da14: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da15 at hpt27xx0 bus 0 scbus8 target 15 lun 0 da15: Fixed Direct Access SCSI-0 device da15: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da16 at hpt27xx0 bus 0 scbus8 target 16 lun 0 da16: Fixed Direct Access SCSI-0 device da16: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) da17 at hpt27xx0 bus 0 scbus8 target 17 lun 0 da17: Fixed Direct Access SCSI-0 device da17: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da18 at hpt27xx0 bus 0 scbus8 target 18 lun 0 da18: Fixed Direct Access SCSI-0 device da18: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da19 at hpt27xx0 bus 0 scbus8 target 19 lun 0 da19: Fixed Direct Access SCSI-0 device da19: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da20 at hpt27xx0 bus 0 scbus8 target 20 lun 0 da20: Fixed Direct Access SCSI-0 device da20: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da21 at hpt27xx0 bus 0 scbus8 target 21 lun 0 da21: Fixed Direct Access SCSI-0 device da21: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da22 at hpt27xx0 bus 0 scbus8 target 22 lun 0 da22: Fixed Direct Access SCSI-0 device da22: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) On Thu, Apr 19, 2012 at 12:29 AM, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On 04/12/12 10:14, Barkley Vowk wrote: >> I've got a Highpoint 2760A card that I'd like a FreeBSD driver >> for, I've got a machine and disks available if someone wants to >> tackle that. > > Please try loading 'hpt27xx.ko' on boot. > > Cheers, > - -- > Xin LI =A0 =A0https://www.delphij.net/ > FreeBSD - The Power to Serve! =A0 =A0 =A0 =A0 =A0 Live free or die > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (FreeBSD) > > iQEcBAEBCAAGBQJPj77sAAoJEG80Jeu8UPuzoW4H/2KsdmWsV/HEERSkyPY/XX/B > jJtEAZFFI6X4aYYqANyPXWWBA6mRy586GkZZNlClCw2v4cBxXAnWBWL49tcuJ0UP > wURQt9/HU6P+EqbRSVZ98KhvufjvecjLavr9x6wCJ+L8pvc7trnD25l/Z0hTA96Y > hIpwTcK/m0IXYopmC0WioPfyZWJx2Uu+DgrUUV6mXOZc9oDDf53v10rbGpQoNUZg > GvKfL2Ql0rHZ13EJkjZdURcUj94Nas7pBgumGwedrsKs0NGnjRNmMlYSRzonqe0Z > uBaWzqEiB01qNThfCpt0tnAS55wYU+QWmvF9hVSApSwmeCsrneluhyUjf9QJ8M8=3D > =3DgUd0 > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.or= g" > From owner-freebsd-hardware@FreeBSD.ORG Sat Apr 21 00:22:45 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F15711065670; Sat, 21 Apr 2012 00:22:45 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [64.62.153.212]) by mx1.freebsd.org (Postfix) with ESMTP id D16568FC12; Sat, 21 Apr 2012 00:22:45 +0000 (UTC) Received: from delta.delphij.net (drawbridge.ixsystems.com [206.40.55.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 2358EF397; Fri, 20 Apr 2012 17:22:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=delphij.net; s=anubis; t=1334967759; bh=BhDwmrf23lopWQaBqa+7qhQQI487kMZA+SED/rmZ14s=; h=Date:From:Reply-To:To:CC:Subject:References:In-Reply-To; b=WPRYZR/fHJlws5sITcAV/pjO01VoT9qsVUhpqoJxZjt5Ej1bidw8LQdsGylMYTWwv LaAFFpUcmkHWiXwIgb1JrQvdyspzQqBJ+3ji84Bo25MvJNZGtXBrdSUiYpnpb/TSFc tiAKJ3BkNOb5a0jQtYt2adG+jPgdwIUTOMQTfKJk= Message-ID: <4F91FDCE.7020600@delphij.net> Date: Fri, 20 Apr 2012 17:22:38 -0700 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: Barkley Vowk References: <4F8FBEEC.6060509@delphij.net> In-Reply-To: X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, d@delphij.net, freebsd-hardware@freebsd.org Subject: Re: Highpoint 2760A / Marvell 88SE9485 SAS HBA Drivers? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2012 00:22:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, On 04/20/12 17:16, Barkley Vowk wrote: > It doesn't seem to work. I've got 22 2.0TB SATA disks, and a 120GB > Intel SSD attached, I get these messages, and the drives all show > in dmesg and /dev. > > But if I try writing to any of them, the process just hangs. What does Ctrl+T says when it hangs? Also, it would be helpful if you can obtain a 'procstat -kk -a' output (please run as root). > Anyone reported success with the 2760A? > > > hpt27xx: RocketRAID 27xx controller driver v1.0 (Apr 19 2012 > 11:02:42) hpt27xx: Attached device index 00 (Path 00 | Target 00 | > E0/Sff) 500c5020e95b8d hpt27xx: Attached device index 01 (Path 01 > | Target 00 | E0/Sff) 500c5020e96089 hpt27xx: Attached device > index 02 (Path 02 | Target 00 | E0/Sff) 500c5010439cd5 hpt27xx: > Attached device index 03 (Path 03 | Target 00 | E0/Sff) > 500c5020c75ac1 hpt27xx: Attached device index 00 (Path 00 | Target > 00 | E0/Sff) 500c5020e9918d hpt27xx: Attached device index 01 > (Path 01 | Target 00 | E0/Sff) 500c5020e987f9 hpt27xx: Attached > device index 02 (Path 02 | Target 00 | E0/Sff) 500c5020d1add > hpt27xx: Attached device index 03 (Path 03 | Target 00 | E0/Sff) > 500c5020e2205d hpt27xx: Attached device index 40 (Path 04 | Target > 00 | E0/Sff) 500c5020e387f1 hpt27xx: Attached device index 41 > (Path 05 | Target 00 | E0/Sff) 500c5020e4eadd hpt27xx: Attached > device index 42 (Path 06 | Target 00 | E0/Sff) 500c5020e47ff1 > hpt27xx: Attached device index 43 (Path 07 | Target 00 | E0/Sff) > 500c5020e4ec91 hpt27xx: Attached device index 40 (Path 04 | Target > 00 | E0/Sff) 500c5020e9607d hpt27xx: Attached device index 41 > (Path 05 | Target 00 | E0/Sff) 500c5020e4801 hpt27xx: Attached > device index 42 (Path 06 | Target 00 | E0/Sff) 500c5020e4e7f1 > hpt27xx: Attached device index 43 (Path 07 | Target 00 | E0/Sff) > 500c5020d0ec39 hpt27xx: Attached device index 00 (Path 00 | Target > 00 | E0/Sff) 500c5020e95b91 hpt27xx: Attached device index 01 > (Path 01 | Target 00 | E0/Sff) 00000000 hpt27xx: Attached device > index 02 (Path 02 | Target 00 | E0/Sff) 500c5020e96359 hpt27xx: > Attached device index 03 (Path 03 | Target 00 | E0/Sff) > 500c5020e4e629 hpt27xx: Attached device index 40 (Path 04 | Target > 00 | E0/Sff) 500c5020d2d69d hpt27xx: Attached device index 41 > (Path 05 | Target 00 | E0/Sff) 500c5020e95b11 hpt27xx: Attached > device index 42 (Path 06 | Target 00 | E0/Sff) 500c5020ea1219 > hpt27xx2: [GIANT-LOCKED] hpt27xx2: [ITHREAD] hpt27xx1: > [GIANT-LOCKED] hpt27xx1: [ITHREAD] hpt27xx0: [GIANT-LOCKED] > hpt27xx0: [ITHREAD] > > > da0 at hpt27xx0 bus 0 scbus8 target 0 lun 0 da0: 4.00> Fixed Direct Access SCSI-0 device da0: 1907729MB (3907029168 > 512 byte sectors: 255H 63S/T 243201C) da1 at hpt27xx0 bus 0 scbus8 > target 1 lun 0 da1: Fixed Direct Access SCSI-0 > device da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T > 243201C) da2 at hpt27xx0 bus 0 scbus8 target 2 lun 0 da2: 0_2 4.00> Fixed Direct Access SCSI-0 device da2: 1907729MB > (3907029168 512 byte sectors: 255H 63S/T 243201C) da3 at hpt27xx0 > bus 0 scbus8 target 3 lun 0 da3: Fixed Direct > Access SCSI-0 device da3: 1907729MB (3907029168 512 byte sectors: > 255H 63S/T 243201C) da4 at hpt27xx0 bus 0 scbus8 target 4 lun 0 > da4: Fixed Direct Access SCSI-0 device da4: > 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da5 at > hpt27xx0 bus 0 scbus8 target 5 lun 0 da5: Fixed > Direct Access SCSI-0 device da5: 1907729MB (3907029168 512 byte > sectors: 255H 63S/T 243201C) da6 at hpt27xx0 bus 0 scbus8 target 6 > lun 0 da6: Fixed Direct Access SCSI-0 device > da6: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) > da7 at hpt27xx0 bus 0 scbus8 target 7 lun 0 da7: 4.00> Fixed Direct Access SCSI-0 device da7: 1907729MB (3907029168 > 512 byte sectors: 255H 63S/T 243201C) da8 at hpt27xx0 bus 0 scbus8 > target 8 lun 0 da8: Fixed Direct Access SCSI-0 > device da8: 1907729MB (3907029168 512 byte sectors: 255H 63S/T > 243201C) da9 at hpt27xx0 bus 0 scbus8 target 9 lun 0 da9: 0_9 4.00> Fixed Direct Access SCSI-0 device da9: 1907729MB > (3907029168 512 byte sectors: 255H 63S/T 243201C) da10 at hpt27xx0 > bus 0 scbus8 target 10 lun 0 da10: Fixed > Direct Access SCSI-0 device da10: 1907729MB (3907029168 512 byte > sectors: 255H 63S/T 243201C) da11 at hpt27xx0 bus 0 scbus8 target > 11 lun 0 da11: Fixed Direct Access SCSI-0 > device da11: 1907729MB (3907029168 512 byte sectors: 255H 63S/T > 243201C) da12 at hpt27xx0 bus 0 scbus8 target 12 lun 0 da12: DISK 0_12 4.00> Fixed Direct Access SCSI-0 device da12: 1907729MB > (3907029168 512 byte sectors: 255H 63S/T 243201C) da13 at hpt27xx0 > bus 0 scbus8 target 13 lun 0 da13: Fixed > Direct Access SCSI-0 device da13: 1907729MB (3907029168 512 byte > sectors: 255H 63S/T 243201C) da14 at hpt27xx0 bus 0 scbus8 target > 14 lun 0 da14: Fixed Direct Access SCSI-0 > device da14: 1907729MB (3907029168 512 byte sectors: 255H 63S/T > 243201C) da15 at hpt27xx0 bus 0 scbus8 target 15 lun 0 da15: DISK 0_15 4.00> Fixed Direct Access SCSI-0 device da15: 1907729MB > (3907029168 512 byte sectors: 255H 63S/T 243201C) da16 at hpt27xx0 > bus 0 scbus8 target 16 lun 0 da16: Fixed > Direct Access SCSI-0 device da16: 114473MB (234441648 512 byte > sectors: 255H 63S/T 14593C) da17 at hpt27xx0 bus 0 scbus8 target 17 > lun 0 da17: Fixed Direct Access SCSI-0 device > da17: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) > da18 at hpt27xx0 bus 0 scbus8 target 18 lun 0 da18: 4.00> Fixed Direct Access SCSI-0 device da18: 1907729MB (3907029168 > 512 byte sectors: 255H 63S/T 243201C) da19 at hpt27xx0 bus 0 scbus8 > target 19 lun 0 da19: Fixed Direct Access > SCSI-0 device da19: 1907729MB (3907029168 512 byte sectors: 255H > 63S/T 243201C) da20 at hpt27xx0 bus 0 scbus8 target 20 lun 0 da20: > Fixed Direct Access SCSI-0 device da20: > 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C) da21 at > hpt27xx0 bus 0 scbus8 target 21 lun 0 da21: > Fixed Direct Access SCSI-0 device da21: 1907729MB (3907029168 512 > byte sectors: 255H 63S/T 243201C) da22 at hpt27xx0 bus 0 scbus8 > target 22 lun 0 da22: Fixed Direct Access > SCSI-0 device da22: 1907729MB (3907029168 512 byte sectors: 255H > 63S/T 243201C) > > > On Thu, Apr 19, 2012 at 12:29 AM, Xin Li > wrote: On 04/12/12 10:14, Barkley Vowk wrote: >>>> I've got a Highpoint 2760A card that I'd like a FreeBSD >>>> driver for, I've got a machine and disks available if someone >>>> wants to tackle that. > > Please try loading 'hpt27xx.ko' on boot. > > Cheers, >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To >> unsubscribe, send any mail to >> "freebsd-hardware-unsubscribe@freebsd.org" >> - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJPkf3OAAoJEG80Jeu8UPuzAzcH/1GqBOF9QAx8DtSD8wpO3bAo ryS5hUgdr6wCuFvPZqIIel3eS8+U1nL/sVDuOdI2Z52S/PTXg56nDLaR6+HKns3v Bv/rrftLlMouQDawfB53Qa0dHLjZiU0oiQ+k5Ocol7Y57+PTLYpUxRfhti6mFMSg bdsQGpmY+jmshhTWki8PF5W8tDu8ucaSrGwUG4yOuXZZ7oZvMsT4K4Sz+LkGFg6s XAOTVNhYRuRoY9o7rTazMH3PATu9K7oxLRnR0WQcKMAcjpI+Df4QNgguVOMhPYMj j+MId0x8iZQe8JdkAx1UjNUWOjDJvQgqJfhYvC6FQ4iHdTuaea+vKTpw0dK8U1A= =mPEE -----END PGP SIGNATURE-----