From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 19 14:22:22 2009 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 57DC1106564A for ; Mon, 19 Jan 2009 14:22:22 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 126FB8FC19 for ; Mon, 19 Jan 2009 14:22:21 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LOujl-0008Ny-AT for freebsd-hardware@freebsd.org; Mon, 19 Jan 2009 17:04:21 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 127FDC6F2 for ; Mon, 19 Jan 2009 17:04:25 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 0F09817033; Mon, 19 Jan 2009 17:04:25 +0300 (MSK) Date: Mon, 19 Jan 2009 17:04:24 +0300 From: Dmitry Marakasov To: freebsd-hardware@freebsd.org Message-ID: <20090119140424.GA56409@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: ASUS mobo for desktop 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, 19 Jan 2009 14:22:22 -0000 Hi! I'm planning to upgrade my desktop to C2D and am picking motherboard for it. I prefer ASUS and I guess P5Q model line is actual now, but there are quite a bunch of specific models, so it's hard enough to pick. Are there any positive experience with those mobos (I.e. no problems with onboard NIC, ATA/SATA controllers and other stuff)? I'm planning to install 7.1 i386. Also I'm planning to install 4GB RAM there - I'll just get my 3.25 or 3.5, right (I think I've heard of some freezes with 4GB)? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 19 15:01:18 2009 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 393FC106564A for ; Mon, 19 Jan 2009 15:01:18 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id E72D48FC1F for ; Mon, 19 Jan 2009 15:01:17 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LOvcs-0001kf-Rj for freebsd-hardware@freebsd.org; Mon, 19 Jan 2009 18:01:19 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id BF614C835 for ; Mon, 19 Jan 2009 18:01:23 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id CA79917034; Mon, 19 Jan 2009 18:01:24 +0300 (MSK) Date: Mon, 19 Jan 2009 18:01:24 +0300 From: Dmitry Marakasov To: freebsd-hardware@freebsd.org Message-ID: <20090119150124.GB56409@hades.panopticon> References: <20090119140424.GA56409@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090119140424.GA56409@hades.panopticon> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: ASUS mobo for desktop 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, 19 Jan 2009 15:01:18 -0000 * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > I'm planning to upgrade my desktop to C2D and am picking motherboard > for it. I prefer ASUS and I guess P5Q model line is actual now, but > there are quite a bunch of specific models, so it's hard enough to > pick. Are there any positive experience with those mobos (I.e. no > problems with onboard NIC, ATA/SATA controllers and other stuff)? > I'm planning to install 7.1 i386. Also I'm planning to install 4GB > RAM there - I'll just get my 3.25 or 3.5, right (I think I've heard > of some freezes with 4GB)? I think I've narrowed to P5QL-E vs. P5Q SE/R vs. P5Q now. The main question is about ATA/SATA controllers support: - JMicron JMB363 - Marvell 88SE6102-NNC1 - Marvell 88SE6111-NAA1 - Silicon image Sil5723CNU -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 19 15:26:29 2009 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 3671F1065678 for ; Mon, 19 Jan 2009 15:26:29 +0000 (UTC) (envelope-from darcsis@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id 0386A8FC0A for ; Mon, 19 Jan 2009 15:26:28 +0000 (UTC) (envelope-from darcsis@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2774814rvf.43 for ; Mon, 19 Jan 2009 07:26:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:x-envelope-to:to:cc:subject :in-reply-to:user-agent:references:from:organization :mail-followup-to:date:message-id:mime-version:content-type; bh=VZF9EjAksH7bH1cmBKqv9WmXokqAV4XUPE8mJszi7HU=; b=VUru+Ter95sCkxG/ZpmB0CTY6+Y+UvFIBbde6Mr5zVlENgOOrfl6z9ZJy/414sHwkZ PjoYWtVqQfFaC87hoC4tWJkxsoKW+0HqGWfG5yy3LrlNvcgdMPNd9TzSmw4pv8n3FkLR SnkWv7mgZvGFE/G/FUkfdKxodKCED0dSUQWq4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-envelope-to:to:cc:subject:in-reply-to:user-agent:references:from :organization:mail-followup-to:date:message-id:mime-version :content-type; b=ay0ytjXHZJyXznX/yyexhv9Iki/je7/W4yY1p1w3QyhatjJokkKCL6qctUgfcCgl4A XRIs1Y6bn/jkwU5+N6GvthtJmFHC32tGCGPKoLhnnZfLgpeJw+BDUi4Jf1kSznBKjSUA zUM9xwagKTvPXStT+9HKf2UH6RFl0UhJkV0T0= Received: by 10.141.129.14 with SMTP id g14mr1536922rvn.8.1232377044592; Mon, 19 Jan 2009 06:57:24 -0800 (PST) Received: from pluton.xbsd.name ([123.117.53.216]) by mx.google.com with ESMTPS id k41sm4501597rvb.3.2009.01.19.06.57.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Jan 2009 06:57:23 -0800 (PST) X-Envelope-To: amdmi3@amdmi3.ru To: Dmitry Marakasov In-Reply-To: <20090119140424.GA56409@hades.panopticon> (Dmitry Marakasov's message of "Mon\, 19 Jan 2009 17\:04\:24 +0300") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) References: <20090119140424.GA56409@hades.panopticon> From: darcsis@gmail.com (Denise H. G.) Organization: Terra Firma Mail-Followup-To: Dmitry Marakasov , freebsd-hardware@freebsd.org Date: Mon, 19 Jan 2009 22:57:39 +0800 Message-ID: <86d4ejcpi4.fsf@pluton.xbsd.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-hardware@freebsd.org Subject: Re: ASUS mobo for desktop 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, 19 Jan 2009 15:26:29 -0000 Dmitry Marakasov writes: > Hi! > > I'm planning to upgrade my desktop to C2D and am picking motherboard > for it. I prefer ASUS and I guess P5Q model line is actual now, but > there are quite a bunch of specific models, so it's hard enough to > pick. Are there any positive experience with those mobos (I.e. no > problems with onboard NIC, ATA/SATA controllers and other stuff)? > I'm planning to install 7.1 i386. Also I'm planning to install 4GB > RAM there - I'll just get my 3.25 or 3.5, right (I think I've heard > of some freezes with 4GB)? I'be been running FreeBSD 7.x on Asus M2A VM for some time. Nearly everything is OK after I upgraded the BIOS to the latest version. If you install 4GB memory on this board without latest BIOS, something weird would happen... -- darcsis ZAI gmail DIAN com From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 06:40:33 2009 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 9EC5B1065690; Wed, 21 Jan 2009 06:40:33 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id 4ADA48FC29; Wed, 21 Jan 2009 06:40:33 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPWlK-000DZu-7o; Wed, 21 Jan 2009 16:40:32 +1000 Message-ID: <4976C370.4030406@dannysplace.net> Date: Wed, 21 Jan 2009 16:40:48 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Koen Smits References: <20081031033208.GA21220@icarus.home.lan> <4920E1DD.7000101@dannysplace.net> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2009-01-21 16:40:30 X-Connected-IP: 203.206.171.212:3036 X-Message-Linecount: 83 X-Body-Linecount: 68 X-Message-Size: 3048 X-Body-Size: 1958 X-Received-Count: 1 X-Recipient-Count: 4 X-Local-Recipient-Count: 4 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: kgysmits@gmail.com, koitsu@freebsd.org, freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=ALL_TRUSTED, AWL, DEAR_SOMETHING, TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 06:40:34 -0000 Koen Smits wrote: > Please let us know what Areca says about the caching. > If you ask me, these results definitely are cached. > Sorry for the delay. Areca got back to me. It took a few days but I got someone who seemed to know what they were talking about. >From what I can gather the cache is always on. You can configure it to be writeback or writethrough in some situations but when that is not an option, writethrough is the default. I could not get any information about read caching although I might send an email to see what happens. Here is the transcript of the conversation: Me: I have a rather simple question about the 1231 controller. Can you please explain the difference between using disks in JBOD mode and using disks in passthrough mode. I have a feeling that the controller uses it's onboard cache when in passthrough mode. Is this the case? Also, are both read and write operations cached? Areca Support: Dear Sir, the only difference is in JBOD mode, controller configure all drives as passthrough disk. in RAID mode, you have to configure passthrough disk by yourself in RAID mode in other words, you can use raid with passthrough disks at saem time in RAID mode but JBOD mode not. Me: So does that mean if I use passthrough, I am not protected by the cache/battery backup? I ask because there is an option for cache mode when creating a passthrough disk. i.e. Write-Back or Write-Through Areca Support: Dear Sir, in JBOD mode, the default setting writeback mode. with writeback mode, you will need a battery module to protect the data remain in cache in case you got a power failure problem. Me: And so in Passthrough mode I am still protected with the battery backup? So JBOD = WriteBack Cache with protection of the battery backup. Passthrough = WriteBack or WriteThrough also with protection of the battery backup. Is this correct? Areca Support: Dear Sir, if you have battery module attached, yes. From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 09:16:08 2009 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 EEA231065698; Wed, 21 Jan 2009 09:16:08 +0000 (UTC) (envelope-from kgysmits@gmail.com) Received: from mail-fx0-f11.google.com (mail-fx0-f11.google.com [209.85.220.11]) by mx1.freebsd.org (Postfix) with ESMTP id 08A1B8FC16; Wed, 21 Jan 2009 09:16:07 +0000 (UTC) (envelope-from kgysmits@gmail.com) Received: by fxm4 with SMTP id 4so867902fxm.19 for ; Wed, 21 Jan 2009 01:16:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=yZ4uEtJCAnaEibAnFddhJ+v4r4kGXxmUCEPUXAM2mjA=; b=MoMPe0se1U50ovxCW4hNRWX/1+Ha0SU5Yc5ieSnIq2PAqkQuQA6oYcLoaWL2CF8JBn BaYX8z68gTYenmY2Yuy7pNqy88aUAjpHjaA8lcVKaahXcWnQaJ9nmojJBfE+W9GHSnYa M6oh0Ce0PMDvWul18x7N4teedsOqnZY8NUb9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IZ8NTaaIRk8q4IFgiMPjBHxjyxc/Rl18c2ezu3OpGukSw3tUFOykLW76tfy5YJsF3r ROOMWApNuStqpi2S9hMxOuaZvnvElsoNBo97+picO5pgWSsYsZERnodStPT1WvXLM5M3 QXTBYqIYsiW/YRp6+HiCEYEqDNMgi2PxVTxr0= MIME-Version: 1.0 Received: by 10.223.110.3 with SMTP id l3mr3299522fap.48.1232529366886; Wed, 21 Jan 2009 01:16:06 -0800 (PST) In-Reply-To: <4976C370.4030406@dannysplace.net> References: <20081031033208.GA21220@icarus.home.lan> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> <4976C370.4030406@dannysplace.net> Date: Wed, 21 Jan 2009 10:16:06 +0100 Message-ID: From: Koen Smits To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Jeremy Chadwick , freebsd-hardware@freebsd.org Subject: Re: Areca vs. ZFS performance testing. 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: Wed, 21 Jan 2009 09:16:09 -0000 > > Areca Support: > Dear Sir, > the only difference is > in JBOD mode, controller configure all drives as passthrough disk. > in RAID mode, you have to configure passthrough disk by yourself in RAID > mode > > in other words, you can use raid with passthrough disks at saem time in > RAID mode but JBOD mode not. > > Me: > So does that mean if I use passthrough, I am not protected by the > cache/battery backup? I ask because there is an option for cache mode > when creating a passthrough disk. i.e. Write-Back or Write-Through missed my 'reply to all' button, here goes the 2nd try. So 'passthrough' means that the controller lets the OS see the physical disks just as they are, but with an invisible cache in between that buffers operations. This way there is no advantage of the onboard XOR engine, but you do profit from the intelligent cache, which is the most important anyway imho. JBOD mode is at a disadvantage because in this mode the OS sees one large drive, and is not able to stripe the data to multiple disks, not taking advantage of the fact that you have multple spindles available. Makes sense to me :). I must admit, I do like these results. Very promising. Further tests would be using an SSD for the ZIL, testing linux and NT, etc. But let's not go there ;). From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 12:45:46 2009 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 BD78F10656F9 for ; Wed, 21 Jan 2009 12:45:46 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from smtp.timeweb.ru (smtp.timeweb.ru [217.170.79.85]) by mx1.freebsd.org (Postfix) with ESMTP id 770A38FC1C for ; Wed, 21 Jan 2009 12:45:45 +0000 (UTC) (envelope-from amdmi3@amdmi3.ru) Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1LPcSo-00021c-Ig for freebsd-hardware@freebsd.org; Wed, 21 Jan 2009 15:45:46 +0300 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 895381020F for ; Wed, 21 Jan 2009 15:45:54 +0300 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 5D96E1702D; Wed, 21 Jan 2009 15:45:55 +0300 (MSK) Date: Wed, 21 Jan 2009 15:45:55 +0300 From: Dmitry Marakasov To: freebsd-hardware@freebsd.org Message-ID: <20090121124555.GA99191@hades.panopticon> References: <20090119140424.GA56409@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20090119140424.GA56409@hades.panopticon> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: ASUS mobo for desktop 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: Wed, 21 Jan 2009 12:45:47 -0000 * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > I'm planning to upgrade my desktop to C2D and am picking motherboard > for it. I prefer ASUS and I guess P5Q model line is actual now, but > there are quite a bunch of specific models, so it's hard enough to > pick. Are there any positive experience with those mobos (I.e. no > problems with onboard NIC, ATA/SATA controllers and other stuff)? > I'm planning to install 7.1 i386. Also I'm planning to install 4GB > RAM there - I'll just get my 3.25 or 3.5, right (I think I've heard > of some freezes with 4GB)? I've bought Asus P5Q. For now I've just tested it with my bootable flash (-CURRENT from around September) - onboard Ethernet (Atheros) and PATA controller (Marvell) didn't work. However, after updating kernel to recent CURRENT Ethernet worked and PATA hard drive was detected). Now I'll check whether I really need CURRENT there (or 7.1 would suffice), move my desktop to that box, test it for a while and report some more info. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 13:15:19 2009 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 490C61065850; Wed, 21 Jan 2009 13:15:19 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [213.133.54.210]) by mx1.freebsd.org (Postfix) with ESMTP id EA1998FC3A; Wed, 21 Jan 2009 13:15:18 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from 203-206-171-212.perm.iinet.net.au ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPcvI-000MOa-EZ; Wed, 21 Jan 2009 23:15:18 +1000 Message-ID: <49771FEE.1070606@dannysplace.net> Date: Wed, 21 Jan 2009 23:15:26 +1000 From: Danny Carroll User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Koen Smits , freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org References: <20081031033208.GA21220@icarus.home.lan> <20081117070818.GA22231@icarus.home.lan> <496549D9.7010003@dannysplace.net> <4966B6B1.8020502@dannysplace.net> <496712A2.4020800@dannysplace.net> <4976C370.4030406@dannysplace.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 08-Jul-2008 08:59:40) X-Date: 2009-01-21 23:15:13 X-Connected-IP: 203.206.171.212:3576 X-Message-Linecount: 65 X-Body-Linecount: 51 X-Message-Size: 3088 X-Body-Size: 2027 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: kgysmits@gmail.com, freebsd-hardware@freebsd.org, freebsd-fs@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: ** X-Spam-Status: No, score=2.2 required=8.0 tests=ALL_TRUSTED, AWL, DEAR_SOMETHING, TVD_RCVD_IP autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: Subject: Re: Areca vs. ZFS performance testing. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2009 13:15:20 -0000 Koen Smits wrote: > Areca Support: > Dear Sir, > the only difference is > in JBOD mode, controller configure all drives as passthrough disk. > in RAID mode, you have to configure passthrough disk by yourself in RAID > mode > > in other words, you can use raid with passthrough disks at saem time in > RAID mode but JBOD mode not. > > Me: > So does that mean if I use passthrough, I am not protected by the > cache/battery backup? I ask because there is an option for cache mode > when creating a passthrough disk. i.e. Write-Back or Write-Through > > > So 'passthrough' means that the controller lets the OS see the physical > disks just as they are, but with an invisible cache in between that > buffers operations. This way there is no advantage of the onboard XOR > engine, but you do profit from the intelligent cache, which is the most > important anyway imho. Not exactly. In JBOD mode ALL disks are passed through to the OS. You cannot have RAID. The cache is set to Write-Back. In RAID mode, you can mix raid5, raid6 and Passthrough (which are like JBOD but allow writethrough or writeback cache at your discretion). > JBOD mode is at a disadvantage because in this mode the OS sees one > large drive, and is not able to stripe the data to multiple disks, not > taking advantage of the fact that you have multple spindles available. > Makes sense to me :). No, in JBOD, the OS sees all disks individually. What you are talking about is a concatenated disk set which I don't think has a raid level. > I must admit, I do like these results. Very promising. Me too, although I am not sure if I like the idea of turning off the cache flushes in ZFS. I'd be a lot happier if the Areca card would tell me how 'full' the cache was. I'd also love to know if there was a way for the disk to tell me what the status if it's own cache is. > Further tests would be using an SSD for the ZIL, testing linux and NT, > etc. But let's not go there ;). Nope :-) -D From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 20:10:52 2009 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE07110657D3 for ; Wed, 21 Jan 2009 20:10:52 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from mail.anduin.net (mail.anduin.net [213.225.74.249]) by mx1.freebsd.org (Postfix) with ESMTP id B12E58FC2A for ; Wed, 21 Jan 2009 20:10:52 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from [212.62.248.146] (helo=[192.168.2.176]) by mail.anduin.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPj90-0000Yg-HP for hardware@freebsd.org; Wed, 21 Jan 2009 20:53:46 +0100 Message-Id: <91C5342C-A23F-4185-9D50-7BA4698CA393@anduin.net> From: =?ISO-8859-1?Q?Eirik_=D8verby?= To: hardware@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 21 Jan 2009 20:53:47 +0100 X-Mailer: Apple Mail (2.930.3) Cc: Subject: Areca 1200 controller panics 7.1 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: Wed, 21 Jan 2009 20:10:53 -0000 Hi folks, see attached screenshot for panic screen. This happens when booting from 7.1-release CD. The box is a Sun X2200 M2, the controller is a 2- port SATA-II controller with 128mb cache memory. One drive is set as single drive (RAID-0), another as passthrough (to get hold of some data from pre-areca times). Another Areca controller in another box (different controller model (4- chan sata) and box (tyan transport)) works just fine. Input welcome. /Eirik From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 20:18:40 2009 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 11EA41065687 for ; Wed, 21 Jan 2009 20:18:40 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id D2CCB8FC21 for ; Wed, 21 Jan 2009 20:18:39 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LPjX4-0000z1-Tw for freebsd-hardware@freebsd.org; Wed, 21 Jan 2009 12:18:38 -0800 Message-ID: <21591376.post@talk.nabble.com> Date: Wed, 21 Jan 2009 12:18:38 -0800 (PST) From: ThinkDifferently To: freebsd-hardware@freebsd.org In-Reply-To: <1d6d20bc0901170310k59673885t70ad7c2f6e7be2b9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: Jeremy@FutureCIS.com References: <21506446.post@talk.nabble.com> <1d6d20bc0901170310k59673885t70ad7c2f6e7be2b9@mail.gmail.com> Subject: Closure: Is it possible to make a bootable RAID on AMD 700 series chipset? Answer: No 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: Wed, 21 Jan 2009 20:18:41 -0000 Jia-Shiun Li wrote: > > ataraid(4) does not have any info about ATI chipsets, and nor does > dmraid of Linux. Supposingly ATI did not release info about software > RAID metadata format so there is little the community can do. > > Since AMD released GPU info after acquiring ATI, maybe they need a > poke about chipsets? > Indeed. In my research and unwitting trials with this particular motherboard (Gigabyte GA-MA78G-DS3H), I found that, while it is generally well tolerated by FreeBSD 7.1-RELEASE, the onboard RAID is completely incompatible. Even when a RocketRAID 3120 card was used, the RAID could be built, but the ar0 device thus created, did not survive a reboot. Also, a software RAID was attempted -- after a minimal install from CD, the atacontrol command was used to create RAID ar0, then (without rebooting) exiting back to the installer, the OS was loaded onto it; however, upon reboot, ar0 could not be found. In other words, it could not boot from any RAID, whether by software in FreeBSD or by hardware on RocketRAID. The problem stems from the board's Southbridge SB700 chipset (the infamous 700 series). This chipset is not (yet?) supported in FreeBSD. Other notes on this board include the following: -Generic VGA worked. -The onboard LAN (chipset 8111C) worked in 7.1-RELEASE, but not 7.0. -If the SATA ports are put into AHCI or Native IDE modes, individual disks were recognized, but in RAID mode, neither the RAID nor individual disks could be seen. -- View this message in context: http://www.nabble.com/Is-it-possible-to-make-a-bootable-RAID-on-AMD-700-series-chipset--tp21506446p21591376.html Sent from the freebsd-hardware mailing list archive at Nabble.com. From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 21 22:09:32 2009 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED3E71065693 for ; Wed, 21 Jan 2009 22:09:31 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from mail.anduin.net (mail.anduin.net [213.225.74.249]) by mx1.freebsd.org (Postfix) with ESMTP id 902AB8FC19 for ; Wed, 21 Jan 2009 22:09:31 +0000 (UTC) (envelope-from ltning@anduin.net) Received: from [212.62.248.146] (helo=[192.168.2.176]) by mail.anduin.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LPlGI-0006IR-EA for hardware@freebsd.org; Wed, 21 Jan 2009 23:09:26 +0100 Message-Id: <93782012-B86F-423A-81A7-8996DF9BB9AC@anduin.net> From: =?ISO-8859-1?Q?Eirik_=D8verby?= To: hardware@freebsd.org In-Reply-To: <91C5342C-A23F-4185-9D50-7BA4698CA393@anduin.net> Mime-Version: 1.0 (Apple Message framework v930.3) Date: Wed, 21 Jan 2009 23:09:28 +0100 References: <91C5342C-A23F-4185-9D50-7BA4698CA393@anduin.net> X-Mailer: Apple Mail (2.930.3) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Areca 1200 controller panics 7.1 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: Wed, 21 Jan 2009 22:09:32 -0000 Attachment not getting throuh. Panic transcribed below. /Eirik On Jan 21, 2009, at 20:53, Eirik =D8verby wrote: > Hi folks, > > see attached screenshot for panic screen. This happens when booting =20= > from 7.1-release CD. The box is a Sun X2200 M2, the controller is a =20= > 2-port SATA-II controller with 128mb cache memory. One drive is set =20= > as single drive (RAID-0), another as passthrough (to get hold of =20 > some data from pre-areca times). > > Another Areca controller in another box (different controller model =20= > (4-chan sata) and box (tyan transport)) works just fine. > > Input welcome. > > /Eirik (probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step arcmsr0: isr get an illegal srb command doneacb=3D=B40xffffffff8124e000=B4= =20 srb=3D0xffff ffffaeb6c420=B4 srbacb=3D=B40xffffffff8124e000=B4 =20 startdone=3D0x3c3csrboutstandingcount=3D-1 Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x34be2988 fault code =3D supervisor read data, page not present instruction pointer =3D 0x8:0xffffffff807914c3 stack pointer =3D 0x10:0xffffffffaecaab60 frame pointer =3D 0x10:0xffffffff8124e000 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 36 (irq17: arcmsr0) trap number =3D 12 panic: page fault From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 19:50:09 2009 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 BAF711065674 for ; Thu, 22 Jan 2009 19:50:09 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id A60148FC12 for ; Thu, 22 Jan 2009 19:50:09 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA08.emeryville.ca.mail.comcast.net with comcast id 6cny1b00516AWCUA8jqAlX; Thu, 22 Jan 2009 19:50:10 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id 6jpw1b00a4Mx3R28SjpzY0; Thu, 22 Jan 2009 19:50:08 +0000 Message-ID: <4978CDE3.4040700@comcast.net> Date: Thu, 22 Jan 2009 14:49:55 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, Mike Tancsa , scottl@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: amr driver issues in 7.1-RELEASE 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: Thu, 22 Jan 2009 19:50:10 -0000 We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, PERC4/DC, amr driver). After recently upgrading two of them from 6.3 to 7.1, we have begun to see the following errors in our logs during heavy use in both systems: amr0: Too many retries on command 0xffffffff80a4da58. Controller is likely dead amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is likely dead amr0: Too many retries on command 0xffffffff80a497a0. Controller is likely dead amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is likely dead However, the system continues working and the volumes remain accessible. This happens on the PERC4/DC controllers in both systems. Firmware version is 352D. MegaCLI reports no problems. Has anyone else seen these messages? A google search turns up nothing but results in the driver code. Is this something we should be worried about? We won't be moving any other systems to 7.1 until we can clear this up. Thanks! -Steve Polyack From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 20:28:20 2009 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 4F4BC106567C; Thu, 22 Jan 2009 20:28:20 +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 C0C938FC19; Thu, 22 Jan 2009 20:28:19 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from [10.92.110.42] (mobile-032-158-094-188.mycingular.net [32.158.94.188] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MJqP11053693; Thu, 22 Jan 2009 12:52:35 -0700 (MST) (envelope-from scottl@samsco.org) References: <4978CDE3.4040700@comcast.net> Message-Id: <55889FEE-0F42-4D40-8E90-447A2AFF70A6@samsco.org> From: Scott Long To: Steve Polyack In-Reply-To: <4978CDE3.4040700@comcast.net> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5G77) Mime-Version: 1.0 (iPhone Mail 5G77) Date: Thu, 22 Jan 2009 12:52:15 -0700 X-Spam-Status: No, score=-2.6 required=3.8 tests=BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "scottl@freebsd.org" , Mike Tancsa , "freebsd-hardware@freebsd.org" Subject: Re: amr driver issues in 7.1-RELEASE 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: Thu, 22 Jan 2009 20:28:21 -0000 I might have a fix for this, let me check and get back to you. Scott Sent from my iPhone On Jan 22, 2009, at 12:49 PM, Steve Polyack wrote: > We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, > PERC4/DC, amr driver). After recently upgrading two of them from > 6.3 to 7.1, we have begun to see the following errors in our logs > during heavy use in both systems: > amr0: Too many retries on command 0xffffffff80a4da58. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a497a0. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > > However, the system continues working and the volumes remain > accessible. This happens on the PERC4/DC controllers in both > systems. Firmware version is 352D. MegaCLI reports no problems. > > Has anyone else seen these messages? A google search turns up > nothing but results in the driver code. Is this something we should > be worried about? We won't be moving any other systems to 7.1 until > we can clear this up. > > Thanks! > > -Steve Polyack From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 21:15:53 2009 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 6A07A1065673; Thu, 22 Jan 2009 21:15:53 +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 1E2BD8FC25; Thu, 22 Jan 2009 21:15:52 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MLFkFK054146; Thu, 22 Jan 2009 14:15:47 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4978E202.70408@samsco.org> Date: Thu, 22 Jan 2009 14:15:46 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Steve Polyack References: <4978CDE3.4040700@comcast.net> In-Reply-To: <4978CDE3.4040700@comcast.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 7.1-RELEASE 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: Thu, 22 Jan 2009 21:15:53 -0000 Steve Polyack wrote: > We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, > PERC4/DC, amr driver). After recently upgrading two of them from 6.3 to > 7.1, we have begun to see the following errors in our logs during heavy > use in both systems: > amr0: Too many retries on command 0xffffffff80a4da58. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a497a0. Controller is > likely dead > amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is > likely dead > > However, the system continues working and the volumes remain > accessible. This happens on the PERC4/DC controllers in both systems. > Firmware version is 352D. MegaCLI reports no problems. > > Has anyone else seen these messages? A google search turns up nothing > but results in the driver code. Is this something we should be worried > about? We won't be moving any other systems to 7.1 until we can clear > this up. > The fix for this that I was thinking of is already in 7.1. There might still be a driver bug, but I'm leaning more towards the controller simply being busy. Do you have a reproducible test case that I could try? Scott From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 21:27:23 2009 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 02404106571A for ; Thu, 22 Jan 2009 21:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB188FC1E for ; Thu, 22 Jan 2009 21:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA03.westchester.pa.mail.comcast.net with comcast id 6k7H1b0120ldTLk53lTNs1; Thu, 22 Jan 2009 21:27:23 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA04.westchester.pa.mail.comcast.net with comcast id 6lT71b00P4Mx3R23QlTAdt; Thu, 22 Jan 2009 21:27:18 +0000 Message-ID: <4978E4AA.8050601@comcast.net> Date: Thu, 22 Jan 2009 16:27:06 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Scott Long References: <4978CDE3.4040700@comcast.net> <4978E202.70408@samsco.org> In-Reply-To: <4978E202.70408@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 7.1-RELEASE 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: Thu, 22 Jan 2009 21:27:24 -0000 Scott Long wrote: > The fix for this that I was thinking of is already in 7.1. There > might still be a driver bug, but I'm leaning more towards the > controller simply being busy. Do you have a reproducible test case > that I could > try? > > Scott > We saw this one while backups wrote from an array on the PERC4/DC to a tape drive (on a separate controller). amr1: Too many retries on command 0xffffffff80a6d060. Controller is likely dead The other four which I noted came during writes to the array attached to the PERC4/DC (external Dell PowerVault). I want to say they showed up while writing a 30G junkfile (/dev/random) to the array which we were using to test the tape access; either that, or while we wrote that file out to the tape drive. If it matters, we also use ports/sysutils/linux-megacli2 to periodically check the status of our arrays. It's possible that this happened during one of these long writes/reads. I'm not having any luck reproducing at the moment, but if I come across a reproducible test, I will let you know. Thanks! Steve Polyack From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 21:49:05 2009 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 B6A58106568A; Thu, 22 Jan 2009 21:49:05 +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 683168FC22; Thu, 22 Jan 2009 21:49:05 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MLmwOW054263; Thu, 22 Jan 2009 14:48:58 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4978E9CA.8040908@samsco.org> Date: Thu, 22 Jan 2009 14:48:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Steve Polyack References: <4978CDE3.4040700@comcast.net> <4978E202.70408@samsco.org> <4978E4AA.8050601@comcast.net> In-Reply-To: <4978E4AA.8050601@comcast.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 7.1-RELEASE 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: Thu, 22 Jan 2009 21:49:06 -0000 Steve Polyack wrote: > Scott Long wrote: >> The fix for this that I was thinking of is already in 7.1. There >> might still be a driver bug, but I'm leaning more towards the >> controller simply being busy. Do you have a reproducible test case >> that I could >> try? >> >> Scott >> > We saw this one while backups wrote from an array on the PERC4/DC to a > tape drive (on a separate controller). > amr1: Too many retries on command 0xffffffff80a6d060. Controller is > likely dead > > The other four which I noted came during writes to the array attached to > the PERC4/DC (external Dell PowerVault). I want to say they showed up > while writing a 30G junkfile (/dev/random) to the array which we were > using to test the tape access; either that, or while we wrote that file > out to the tape drive. > > If it matters, we also use ports/sysutils/linux-megacli2 to periodically > check the status of our arrays. It's possible that this happened during > one of these long writes/reads. I'm not having any luck reproducing at > the moment, but if I come across a reproducible test, I will let you know. > I don't know too much about the internals of the AMR firmware, but I imagine that it could be possible that a management command from megacli could stall the firmware and make this warning pop up. I'll see if I can reproduce it. The warning is harmless, though, even if it is strongly worded. Scott From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 23 21:36:35 2009 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 439671065672 for ; Fri, 23 Jan 2009 21:36:35 +0000 (UTC) (envelope-from gpagnoni@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 04C5B8FC1B for ; Fri, 23 Jan 2009 21:36:34 +0000 (UTC) (envelope-from gpagnoni@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so2048233ywe.13 for ; Fri, 23 Jan 2009 13:36:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=Y3VEVcDXBm1rYSWCA7BvHPuHoeEH8puVqg8TneYjpxo=; b=vE/9HwZZKj6azxFLmgS5/pvRFKEcRa/JgYDVTZ2i+E6pwUxdu5aR71yo+fqvbZcC+T 46nG37H7ack7IWFHzWKxiEDQJ6VpMtquE5okpFZLcgmy92LBqnTFHUj6qJx1/Ry6h7iQ lRfxYqXV1eleOux+QkZPfElSPEX/3JPM3rf0s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=pjqD68iQGwCupUXF27pl58dP7XSnA6LlOyLPCeLodMACA6m3bS3L9cjGNyO/YMCQmu guPmIweXkEGiqhwsqp12TA8KXxt1VCMroxV5veD+1zeYcw5LtV1KHxhQOGH626QzX04f m4vracOS7yvuaSADCjtNERgHUI+zvRenQcVAw= MIME-Version: 1.0 Received: by 10.65.93.12 with SMTP id v12mr1460650qbl.108.1232746594073; Fri, 23 Jan 2009 13:36:34 -0800 (PST) Date: Fri, 23 Jan 2009 22:36:34 +0100 Message-ID: <92056ebc0901231336x188b4d81l9c6d804e8aa437de@mail.gmail.com> From: Giuseppe Pagnoni To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Atheros AR821 (Asus P5Q Pro) and 'ale' driver 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, 23 Jan 2009 21:36:35 -0000 Dear all, I am running freebsd 7.1 rel on an Asus p5q pro motherboard with an onboard ethernet chip Atheros AR8121. I am using the "ale" driver, which generally seems to work, although I noticed that when connecting via ssh to the machine, I get disconnected with "corrupted MAC on input" a little too often. Does anybody know if this may be an issue related to the ethernet driver, or is it likely to be something totally unrelated? (I don't get the same behavior, though, when the machine is booted in Ubuntu). thank you very much for any suggestions giuseppe From owner-freebsd-hardware@FreeBSD.ORG Sat Jan 24 05:46:27 2009 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 9CA52106566B for ; Sat, 24 Jan 2009 05:46:27 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-71-117-207-61.ptldor.fios.verizon.net [71.117.207.61]) by mx1.freebsd.org (Postfix) with ESMTP id C8B998FC0A for ; Sat, 24 Jan 2009 05:46:25 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 9AFC9B64F; Fri, 23 Jan 2009 21:41:26 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id FAA21539; Sat, 24 Jan 2009 05:23:26 GMT Message-Id: <200901240523.FAA21539@sopwith.solgatos.com> To: freebsd-drivers@freebsd.org, freebsd-hardware@freebsd.org Date: Fri, 23 Jan 2009 21:23:26 +0000 From: Dieter Cc: Subject: Dealing with Seagate's problematic 7200.11 firmware. X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@sopwith.solgatos.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jan 2009 05:46:27 -0000 Most of you have read about the problems with Seagate's 7200.11 disks. For those of you that haven't, the firmware on many of these drives is buggy, and can "brick" the drive when powering up or rebooting the system. Thus far, Seagate's response has been less than wonderful. We need a FLOSS solution. Goals: 1) Ability to read the number of log entries. 2) Ability to change the number of log entries. 3) Ability to install new firmware from Unix. We need for this to work with any flavor of Unix, on any CPU arch, without reboot or power cycle. We need for this to work on one drive without affecting other drives. I don't expect to be able to write FLOSS firmware for the drives, so this isn't listed as a goal. If you think you can, please feel free. The problem: "IF the drive is powered down when there are 320 entries in this journal or log, then when it is powered back up, the drive errors out on init and won't boot properly - to the point that it won't even report it's information to the BIOS." Maxtorman, slashdot discussion [2] If Maxtorman is correct, then once the drive has been operating awhile, we have a 1 in 320 chance that the circular log is at entry 320. We want to be able to find out how many log entries the disk currently has, and we want to be able to change the number of log entries away from 320, while we wait for Seagate to get its act together and release firmware that works properly. Since Seagate's solution will require attaching the drive to an x86 system and booting a FreeDOS ISO from CD, if the log is at 320 that boot will brick the drive. There are other firmware problems with the 7200.11 series, but this is the biggie. Once Seagate releases working firmware, we want to be able to install it from Unix, on any CPU arch. Seagate's release can only install on x86 using FreeDOS. *ATA Commands that may be useful: command name command code in hex page [1] pdf page [1] Read Log Ext 0x2F 27 33 S.M.A.R.T. Read Log Sector 0xB0 / 0xD5 28,34 34,40 S.M.A.R.T. Write Log Sector 0xB0 / 0xD6 28,34 34.40 Write Log Extended 0x3F 28 34 Download Microcode 0x92 27 33 Questions: Is Maxtorman correct about the 320 log entries? Are the commands listed above the ones we need? What is the difference between the "Log Extended" and the S.M.A.R.T. Log Sector? Is "Microcode" the same as "firmware"? (Seagate uses the term firmware elsewhere in the manual, but I don't find any sort of "write firmware" command.) Where can we get more detailed info about these commands and how to use them? References: [1] Seagate Barracuda 7200.11 Serial ATA Product Manual rev C August 2008 http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.11/100507013c.pdf [2] http://it.slashdot.org/article.pl?sid=09/01/21/0052236