From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 8 01:36:55 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5395816A403; Sun, 8 Oct 2006 01:36:55 +0000 (UTC) (envelope-from richw@richw.org) Received: from smtp2.stanford.edu (smtp2.Stanford.EDU [171.67.20.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED8CF43D49; Sun, 8 Oct 2006 01:36:54 +0000 (GMT) (envelope-from richw@richw.org) Received: from smtp2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 11AA84C283; Sat, 7 Oct 2006 18:36:54 -0700 (PDT) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp2.stanford.edu (Postfix) with ESMTP id E801E4C11D; Sat, 7 Oct 2006 18:36:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by whodunit.richw.org (Postfix) with ESMTP id C0FA83C36D; Sat, 7 Oct 2006 18:36:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at richw.org Received: from whodunit.richw.org ([127.0.0.1]) by localhost (whodunit.richw.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C1unIggKLZCT; Sat, 7 Oct 2006 18:36:52 -0700 (PDT) Received: from [172.29.0.21] (evilempire.richw.org [172.29.0.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "evilempire.richw.org", Issuer "richw.org" (verified OK)) (Authenticated sender: richw) by whodunit.richw.org (Postfix) with ESMTP id E1CC43C36B; Sat, 7 Oct 2006 18:36:52 -0700 (PDT) Date: Sat, 07 Oct 2006 18:36:52 -0700 From: Rich Wales User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20061002065745.936D33C36B@whodunit.richw.org> In-Reply-To: <20061002065745.936D33C36B@whodunit.richw.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20061008013652.E1CC43C36B@whodunit.richw.org> Cc: freebsd-current@freebsd.org, freebsd-hardware@freebsd.org Subject: Fix to my Promise SATA timeout problems 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: Sun, 08 Oct 2006 01:36:55 -0000 Several days ago, I wrote (in -stable, -current, and -hardware) about problems I had been having with a Promise SATA300 TX4 card (PDC40718 chip). Per a suggestion from Søren, I rechecked my hardware and my BIOS settings. I eventually found that I was able to make the timeout problems disappear by disabling PCI master burst mode in the BIOS setup of my system. (For the record, I've been working with an 800-MHz original "Slot A" Athlon on a VIA VAM-0070 motherboard -- a board which appears to be a rebranded EPoX EP-7KXA.) Not surprisingly, turning off burst mode had a significant impact on the disk I/O speed of the system, but at least it's stable now, with no more timeouts or failures. I'm not sure if the primary culprit here is the Promise card or the motherboard, but it suggests to me that some systems with iffy PCI bus tolerances might require suboptimal BIOS settings in order to work properly with some Promise controllers. At least, this is something to try if you encounter problems with a Promise card. As for whether any effective steps can be taken in the driver to make it more robust against this problem, I'll have to leave that to people who are more familiar with the hardware and the code. I've updated PR 103435 with this info. Rich Wales Palo Alto, CA, USA richw@richw.org http://www.richw.org From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 00:57:54 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 010BB16A403 for ; Mon, 9 Oct 2006 00:57:54 +0000 (UTC) (envelope-from dking@ketralnis.com) Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id A538F43D45 for ; Mon, 9 Oct 2006 00:57:53 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [10.0.1.239] (ayla.wifi.int.ketralnis.com [10.0.1.239]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k990vrEj018356 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sun, 8 Oct 2006 17:57:53 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <200610052145.54292.soralx@cydem.org> References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com> <200610041939.35376.soralx@cydem.org> <0431EB40-6AF8-49A6-9F87-0B707B1DDC94@ketralnis.com> <200610052145.54292.soralx@cydem.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3ABF536B-F199-47B9-8B10-EF5A0644BC62@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Sun, 8 Oct 2006 17:57:47 -0700 To: freebsd-hardware@freebsd.org X-Mailer: Apple Mail (2.752.3) Subject: Re: Quiet computer 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, 09 Oct 2006 00:57:54 -0000 >>> You might wants to consider using a low-power 'brick'-type AC->DC >>> PSU (~90W?) and a DC-DC voltage converter that plugs directly into >>> a mainboard's power connector. This will be quite noiseless. >> Do you have any recommendations? Ideally it would mount on the case >> () like >> the current power supply does but I'm open to other options > something like this (random example): > http://www.logicsupply.com/product_info.php/products_id/596 The only types of power supplies with which I'm familiar are the ones that typically ship with most cases, so I'm a little confused by this, excuse my obvious ignorance :) What does the DC-DC converter do, if the AC-DC converter supplies DC power? What would be an example of this AC-DC converter? Could it power two 3.5" hard drives in addition to the motherboard? How does it differ from a regular power supply? From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 15:12:55 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FAF816A407 for ; Mon, 9 Oct 2006 15:12:55 +0000 (UTC) (envelope-from up@3.am) Received: from richard2.pil.net (mail.pil.net [207.7.198.3]) by mx1.FreeBSD.org (Postfix) with SMTP id A7BA643D53 for ; Mon, 9 Oct 2006 15:12:54 +0000 (GMT) (envelope-from up@3.am) Received: (qmail 79899 invoked by uid 1825); 9 Oct 2006 15:12:50 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Oct 2006 15:12:50 -0000 Date: Mon, 9 Oct 2006 11:12:50 -0400 (EDT) From: up@3.am X-X-Sender: up@richard2.pil.net To: freebsd-questions@freebsd.org, FreeBSD ISP List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: LSI SAS adapter 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, 09 Oct 2006 15:12:55 -0000 Can anyone verify that the LSI0100 PCI-X SAS RAID card will work with 6.X-STABLE? The mfi driver says it supports LSI SAS MegaRAID, but this isn't in the MegaRAID family (only does RAID 0 and 1, and I only need 1). All experiences appreciated...please reply directly as I am not subscribed. Thanks! James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 17:30:17 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E931B16A47C for ; Mon, 9 Oct 2006 17:30:17 +0000 (UTC) (envelope-from dking@ketralnis.com) Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC99243D49 for ; Mon, 9 Oct 2006 17:30:15 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [192.168.1.61] (pix.xythos.com [64.154.218.194]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k99HUEtY013887 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 9 Oct 2006 10:30:15 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com> <200610041939.35376.soralx@cydem.org> <0431EB40-6AF8-49A6-9F87-0B707B1DDC94@ketralnis.com> <200610052145.54292.soralx@cydem.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0C50F0B0-05B0-433A-8A45-D8872C916904@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Mon, 9 Oct 2006 10:29:55 -0700 To: freebsd-hardware@freebsd.org X-Mailer: Apple Mail (2.752.3) Subject: Re: Quiet computer 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, 09 Oct 2006 17:30:18 -0000 Here we are again with padlock(4) actually compiled into the kernel :) OpenSSL 0.9.8d 28 Sep 2006 built on: Thu Oct 5 14:59:49 PDT 2006 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes (partial) idea(int) blowfish(idx) compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread - D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 - fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe - mtune=i686 -march=pentiumpro -Wl,-rpath,/usr/local/lib - DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM available timing options: USE_TOD HZ=128 [sysconf value] timing function used: getrusage The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes md2 484.96k 1028.72k 1430.85k 1586.47k 1638.30k mdc2 0.00 0.00 0.00 0.00 0.00 md4 4032.03k 13842.55k 37818.93k 67152.92k 86782.76k md5 3911.84k 13584.08k 38591.74k 70378.22k 93060.09k hmac(md5) 5111.89k 16756.66k 44186.02k 74774.38k 94053.88k sha1 3254.06k 9925.14k 22536.35k 33177.25k 38443.33k rmd160 3017.47k 8466.50k 17600.37k 24115.23k 27071.74k rc4 34821.22k 38830.34k 39777.78k 40220.13k 40324.81k des cbc 10097.19k 10562.78k 10716.04k 10753.39k 10764.02k des ede3 3625.92k 3686.90k 3705.11k 3709.21k 3710.78k idea cbc 7725.38k 8227.10k 8359.48k 8391.42k 8407.62k rc2 cbc 5299.41k 5529.69k 5590.01k 5604.81k 5607.09k rc5-32/12 cbc 0.00 0.00 0.00 0.00 0.00 blowfish cbc 18280.56k 19490.41k 19746.85k 19893.62k 19916.51k cast cbc 7892.93k 8284.10k 8421.85k 8459.11k 8460.19k aes-128 cbc 10276.54k 13552.14k 14833.08k 15191.43k 15270.86k aes-192 cbc 9167.52k 11687.66k 12628.19k 12888.71k 12952.68k aes-256 cbc 8266.91k 10057.43k 10768.40k 10957.97k 11012.94k camellia-128 cbc 0.00 0.00 0.00 0.00 0.00 camellia-192 cbc 0.00 0.00 0.00 0.00 0.00 camellia-256 cbc 0.00 0.00 0.00 0.00 0.00 sha256 2098.35k 4825.75k 8423.74k 10366.23k 11114.17k sha512 484.15k 1935.12k 2858.82k 3951.34k 4447.44k sign verify sign/s verify/s rsa 512 bits 0.003200s 0.000246s 312.5 4058.6 rsa 1024 bits 0.014534s 0.000682s 68.8 1465.2 rsa 2048 bits 0.082113s 0.002226s 12.2 449.2 rsa 4096 bits 0.529857s 0.007901s 1.9 126.6 sign verify sign/s verify/s dsa 512 bits 0.002356s 0.002792s 424.5 358.2 dsa 1024 bits 0.006577s 0.007967s 152.0 125.5 dsa 2048 bits 0.021624s 0.026237s 46.2 38.1 On 06 Oct 2006, at 22:05, David King wrote: >> just do `openssl speed` >> if you see some damn large numbers, you know 'tis hw crypto >> working :) > > Okay, so I did it with /usr/bin/openssl and /usr/local/bin/openssl. > Tell me what you think: > > ----------/usr/bin/openssl---------- > To get the most accurate results, try to run this > program when this computer is idle. > Doing md2 for 3s on 16 size blocks: 95512 md2's in 2.98s > Doing md2 for 3s on 64 size blocks: 50903 md2's in 2.99s > Doing md2 for 3s on 256 size blocks: 17768 md2's in 2.99s > Doing md2 for 3s on 1024 size blocks: 4928 md2's in 2.99s > Doing md2 for 3s on 8192 size blocks: 637 md2's in 2.99s > Doing mdc2 for 3s on 16 size blocks: 218133 mdc2's in 2.98s > Doing mdc2 for 3s on 64 size blocks: 61692 mdc2's in 2.99s > Doing mdc2 for 3s on 256 size blocks: 15949 mdc2's in 2.99s > Doing mdc2 for 3s on 1024 size blocks: 4024 mdc2's in 2.99s > Doing mdc2 for 3s on 8192 size blocks: 505 mdc2's in 2.99s > Doing md4 for 3s on 16 size blocks: 810042 md4's in 2.99s > Doing md4 for 3s on 64 size blocks: 692610 md4's in 2.99s > Doing md4 for 3s on 256 size blocks: 470095 md4's in 2.99s > Doing md4 for 3s on 1024 size blocks: 204791 md4's in 2.99s > Doing md4 for 3s on 8192 size blocks: 32865 md4's in 2.99s > Doing md5 for 3s on 16 size blocks: 677259 md5's in 2.99s > Doing md5 for 3s on 64 size blocks: 558167 md5's in 2.99s > Doing md5 for 3s on 256 size blocks: 356691 md5's in 2.99s > Doing md5 for 3s on 1024 size blocks: 146187 md5's in 2.99s > Doing md5 for 3s on 8192 size blocks: 22488 md5's in 2.99s > Doing hmac(md5) for 3s on 16 size blocks: 674479 hmac(md5)'s in 2.99s > Doing hmac(md5) for 3s on 64 size blocks: 553966 hmac(md5)'s in 2.99s > Doing hmac(md5) for 3s on 256 size blocks: 356030 hmac(md5)'s in 2.99s > Doing hmac(md5) for 3s on 1024 size blocks: 146028 hmac(md5)'s in > 2.99s > Doing hmac(md5) for 3s on 8192 size blocks: 22487 hmac(md5)'s in 2.98s > Doing sha1 for 3s on 16 size blocks: 574104 sha1's in 2.99s > Doing sha1 for 3s on 64 size blocks: 398438 sha1's in 2.99s > Doing sha1 for 3s on 256 size blocks: 205800 sha1's in 2.99s > Doing sha1 for 3s on 1024 size blocks: 70157 sha1's in 2.99s > Doing sha1 for 3s on 8192 size blocks: 9810 sha1's in 2.99s > Doing rmd160 for 3s on 16 size blocks: 469010 rmd160's in 2.98s > Doing rmd160 for 3s on 64 size blocks: 311884 rmd160's in 2.99s > Doing rmd160 for 3s on 256 size blocks: 153384 rmd160's in 2.99s > Doing rmd160 for 3s on 1024 size blocks: 50539 rmd160's in 2.98s > Doing rmd160 for 3s on 8192 size blocks: 6963 rmd160's in 2.98s > Doing rc4 for 3s on 16 size blocks: 6933407 rc4's in 2.99s > Doing rc4 for 3s on 64 size blocks: 1923083 rc4's in 2.98s > Doing rc4 for 3s on 256 size blocks: 489508 rc4's in 2.96s > Doing rc4 for 3s on 1024 size blocks: 123724 rc4's in 2.97s > Doing rc4 for 3s on 8192 size blocks: 15556 rc4's in 2.97s > Doing des cbc for 3s on 16 size blocks: 2105375 des cbc's in 2.98s > Doing des cbc for 3s on 64 size blocks: 543605 des cbc's in 2.98s > Doing des cbc for 3s on 256 size blocks: 137827 des cbc's in 2.98s > Doing des cbc for 3s on 1024 size blocks: 34556 des cbc's in 2.98s > Doing des cbc for 3s on 8192 size blocks: 4323 des cbc's in 2.98s > Doing des ede3 for 3s on 16 size blocks: 756533 des ede3's in 2.98s > Doing des ede3 for 3s on 64 size blocks: 191674 des ede3's in 2.98s > Doing des ede3 for 3s on 256 size blocks: 48143 des ede3's in 2.98s > Doing des ede3 for 3s on 1024 size blocks: 12056 des ede3's in 2.99s > Doing des ede3 for 3s on 8192 size blocks: 1507 des ede3's in 2.99s > Doing aes-128 cbc for 3s on 16 size blocks: 1683023 aes-128 cbc's > in 2.98s > Doing aes-128 cbc for 3s on 64 size blocks: 428016 aes-128 cbc's in > 2.98s > Doing aes-128 cbc for 3s on 256 size blocks: 108105 aes-128 cbc's > in 2.99s > Doing aes-128 cbc for 3s on 1024 size blocks: 27079 aes-128 cbc's > in 2.98s > Doing aes-128 cbc for 3s on 8192 size blocks: 3388 aes-128 cbc's in > 2.98s > Doing aes-192 cbc for 3s on 16 size blocks: 1470225 aes-192 cbc's > in 2.98s > Doing aes-192 cbc for 3s on 64 size blocks: 373644 aes-192 cbc's in > 2.98s > Doing aes-192 cbc for 3s on 256 size blocks: 94170 aes-192 cbc's in > 2.98s > Doing aes-192 cbc for 3s on 1024 size blocks: 23586 aes-192 cbc's > in 2.98s > Doing aes-192 cbc for 3s on 8192 size blocks: 2951 aes-192 cbc's in > 2.98s > Doing aes-256 cbc for 3s on 16 size blocks: 1305813 aes-256 cbc's > in 2.98s > Doing aes-256 cbc for 3s on 64 size blocks: 331577 aes-256 cbc's in > 2.99s > Doing aes-256 cbc for 3s on 256 size blocks: 83473 aes-256 cbc's in > 2.99s > Doing aes-256 cbc for 3s on 1024 size blocks: 20912 aes-256 cbc's > in 2.99s > Doing aes-256 cbc for 3s on 8192 size blocks: 2616 aes-256 cbc's in > 2.99s > Doing rc2 cbc for 3s on 16 size blocks: 1043269 rc2 cbc's in 2.99s > Doing rc2 cbc for 3s on 64 size blocks: 271026 rc2 cbc's in 2.99s > Doing rc2 cbc for 3s on 256 size blocks: 68365 rc2 cbc's in 2.98s > Doing rc2 cbc for 3s on 1024 size blocks: 17147 rc2 cbc's in 2.99s > Doing rc2 cbc for 3s on 8192 size blocks: 2145 rc2 cbc's in 2.99s > Doing rc5-32/12 cbc for 3s on 16 size blocks: 6393672 rc5-32/12 > cbc's in 2.98s > Doing rc5-32/12 cbc for 3s on 64 size blocks: 1774376 rc5-32/12 > cbc's in 2.98s > Doing rc5-32/12 cbc for 3s on 256 size blocks: 462590 rc5-32/12 > cbc's in 2.99s > Doing rc5-32/12 cbc for 3s on 1024 size blocks: 116817 rc5-32/12 > cbc's in 2.98s > Doing rc5-32/12 cbc for 3s on 8192 size blocks: 14622 rc5-32/12 > cbc's in 2.98s > Doing blowfish cbc for 3s on 16 size blocks: 3515807 blowfish cbc's > in 2.99s > Doing blowfish cbc for 3s on 64 size blocks: 936491 blowfish cbc's > in 2.99s > Doing blowfish cbc for 3s on 256 size blocks: 237486 blowfish cbc's > in 2.99s > Doing blowfish cbc for 3s on 1024 size blocks: 59693 blowfish cbc's > in 2.99s > Doing blowfish cbc for 3s on 8192 size blocks: 7472 blowfish cbc's > in 2.99s > Doing cast cbc for 3s on 16 size blocks: 3594419 cast cbc's in 2.99s > Doing cast cbc for 3s on 64 size blocks: 950631 cast cbc's in 2.98s > Doing cast cbc for 3s on 256 size blocks: 243324 cast cbc's in 2.99s > Doing cast cbc for 3s on 1024 size blocks: 61170 cast cbc's in 2.99s > Doing cast cbc for 3s on 8192 size blocks: 7649 cast cbc's in 2.99s > Doing 512 bit private rsa's for 10s: 3567 512 bit private RSA's in > 9.95s > Doing 512 bit public rsa's for 10s: 31284 512 bit public RSA's in > 9.94s > Doing 1024 bit private rsa's for 10s: 786 1024 bit private RSA's in > 9.94s > Doing 1024 bit public rsa's for 10s: 12643 1024 bit public RSA's in > 9.94s > Doing 2048 bit private rsa's for 10s: 137 2048 bit private RSA's in > 10.02s > Doing 2048 bit public rsa's for 10s: 4089 2048 bit public RSA's in > 9.95s > Doing 4096 bit private rsa's for 10s: 21 4096 bit private RSA's in > 10.05s > Doing 4096 bit public rsa's for 10s: 1174 4096 bit public RSA's in > 9.95s > Doing 512 bit sign dsa's for 10s: 4423 512 bit DSA signs in 9.56s > Doing 512 bit verify dsa's for 10s: 3685 512 bit DSA verify in 10.00s > Doing 1024 bit sign dsa's for 10s: 1557 1024 bit DSA signs in 10.00s > Doing 1024 bit verify dsa's for 10s: 1301 1024 bit DSA verify in > 10.00s > Doing 2048 bit sign dsa's for 10s: 474 2048 bit DSA signs in 9.99s > Doing 2048 bit verify dsa's for 10s: 384 2048 bit DSA verify in 10.02s > OpenSSL 0.9.7e-p1 25 Oct 2004 > built on: Fri Sep 22 23:34:15 PDT 2006 > options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes > (partial) blowfish(idx) > compiler: cc > available timing options: USE_TOD HZ=128 [sysconf value] > timing function used: getrusage > The 'numbers' are in 1000s of bytes per second processed. > type 16 bytes 64 bytes 256 bytes 1024 bytes > 8192 bytes > md2 512.69k 1091.17k 1522.88k > 1689.62k 1745.43k > mdc2 1169.74k 1322.64k 1367.51k > 1379.38k 1383.02k > md4 4339.88k 14841.95k 40292.45k > 70247.92k 90135.45k > md5 3627.96k 11962.71k 30571.03k > 50116.72k 61675.11k > hmac(md5) 3613.31k 11871.78k 30517.83k > 50067.31k 61713.54k > sha1 3075.34k 8538.22k 17643.58k > 24059.81k 26914.86k > rmd160 2516.37k 6686.89k 13151.09k > 17339.59k 19132.95k > rc4 37157.99k 41299.57k 42307.37k > 42724.09k 42851.07k > des cbc 11291.64k 11682.42k 11826.20k > 11862.20k 11870.63k > des ede3 4055.37k 4110.76k 4129.60k > 4134.81k 4134.77k > idea cbc 0.00 0.00 0.00 > 0.00 0.00 > rc2 cbc 5588.96k 5808.52k 5865.79k > 5880.90k 5884.61k > rc5-32/12 cbc 34280.23k 38109.91k 39666.58k > 40080.87k 40200.80k > blowfish cbc 18839.66k 20068.64k 20363.22k > 20468.75k 20500.88k > cast cbc 19266.28k 20417.46k 20859.22k > 20972.79k 20977.22k > aes-128 cbc 9039.90k 9186.16k 9270.87k > 9292.88k 9298.58k > aes-192 cbc 7884.05k 8013.09k 8078.25k > 8093.83k 8099.55k > aes-256 cbc 7005.10k 7106.64k 7157.91k > 7170.89k 7173.38k > sign verify sign/s verify/s > rsa 512 bits 0.0028s 0.0003s 358.5 3147.9 > rsa 1024 bits 0.0126s 0.0008s 79.1 1272.5 > rsa 2048 bits 0.0732s 0.0024s 13.7 411.0 > rsa 4096 bits 0.4788s 0.0085s 2.1 117.9 > sign verify sign/s verify/s > dsa 512 bits 0.0022s 0.0027s 462.6 368.4 > dsa 1024 bits 0.0064s 0.0077s 155.6 130.1 > dsa 2048 bits 0.0211s 0.0261s 47.4 38.3 > > ----------/usr/local/bin/opensl---------- > > To get the most accurate results, try to run this > program when this computer is idle. > Doing md2 for 3s on 16 size blocks: 91481 md2's in 3.00s > Doing md2 for 3s on 64 size blocks: 48533 md2's in 3.00s > Doing md2 for 3s on 256 size blocks: 16878 md2's in 3.00s > Doing md2 for 3s on 1024 size blocks: 4678 md2's in 3.00s > Doing md2 for 3s on 8192 size blocks: 604 md2's in 3.00s > Doing md4 for 3s on 16 size blocks: 765870 md4's in 3.00s > Doing md4 for 3s on 64 size blocks: 650603 md4's in 3.00s > Doing md4 for 3s on 256 size blocks: 445118 md4's in 3.00s > Doing md4 for 3s on 1024 size blocks: 197393 md4's in 3.00s > Doing md4 for 3s on 8192 size blocks: 32000 md4's in 3.00s > Doing md5 for 3s on 16 size blocks: 740691 md5's in 3.00s > Doing md5 for 3s on 64 size blocks: 645494 md5's in 3.00s > Doing md5 for 3s on 256 size blocks: 454959 md5's in 3.00s > Doing md5 for 3s on 1024 size blocks: 207958 md5's in 3.00s > Doing md5 for 3s on 8192 size blocks: 34331 md5's in 3.00s > Doing hmac(md5) for 3s on 16 size blocks: 965270 hmac(md5)'s in 3.00s > Doing hmac(md5) for 3s on 64 size blocks: 791215 hmac(md5)'s in 3.00s > Doing hmac(md5) for 3s on 256 size blocks: 521572 hmac(md5)'s in 3.00s > Doing hmac(md5) for 3s on 1024 size blocks: 220635 hmac(md5)'s in > 3.00s > Doing hmac(md5) for 3s on 8192 size blocks: 34675 hmac(md5)'s in 3.00s > Doing sha1 for 3s on 16 size blocks: 617279 sha1's in 3.00s > Doing sha1 for 3s on 64 size blocks: 468049 sha1's in 3.00s > Doing sha1 for 3s on 256 size blocks: 266386 sha1's in 3.00s > Doing sha1 for 3s on 1024 size blocks: 97818 sha1's in 3.00s > Doing sha1 for 3s on 8192 size blocks: 14182 sha1's in 3.00s > Doing sha256 for 3s on 16 size blocks: 396047 sha256's in 3.00s > Doing sha256 for 3s on 64 size blocks: 227772 sha256's in 3.00s > Doing sha256 for 3s on 256 size blocks: 99380 sha256's in 3.00s > Doing sha256 for 3s on 1024 size blocks: 30573 sha256's in 3.00s > Doing sha256 for 3s on 8192 size blocks: 4098 sha256's in 3.00s > Doing sha512 for 3s on 16 size blocks: 91452 sha512's in 3.00s > Doing sha512 for 3s on 64 size blocks: 91440 sha512's in 3.00s > Doing sha512 for 3s on 256 size blocks: 33728 sha512's in 3.00s > Doing sha512 for 3s on 1024 size blocks: 11654 sha512's in 3.00s > Doing sha512 for 3s on 8192 size blocks: 1640 sha512's in 3.00s > Doing rmd160 for 3s on 16 size blocks: 567819 rmd160's in 3.00s > Doing rmd160 for 3s on 64 size blocks: 399514 rmd160's in 3.00s > Doing rmd160 for 3s on 256 size blocks: 207789 rmd160's in 3.00s > Doing rmd160 for 3s on 1024 size blocks: 71158 rmd160's in 3.00s > Doing rmd160 for 3s on 8192 size blocks: 9981 rmd160's in 3.00s > Doing rc4 for 3s on 16 size blocks: 6568769 rc4's in 3.00s > Doing rc4 for 3s on 64 size blocks: 1831119 rc4's in 3.00s > Doing rc4 for 3s on 256 size blocks: 469013 rc4's in 3.00s > Doing rc4 for 3s on 1024 size blocks: 118548 rc4's in 3.00s > Doing rc4 for 3s on 8192 size blocks: 14866 rc4's in 3.00s > Doing des cbc for 3s on 16 size blocks: 1904652 des cbc's in 3.00s > Doing des cbc for 3s on 64 size blocks: 498596 des cbc's in 3.00s > Doing des cbc for 3s on 256 size blocks: 126362 des cbc's in 3.00s > Doing des cbc for 3s on 1024 size blocks: 31699 des cbc's in 3.00s > Doing des cbc for 3s on 8192 size blocks: 3967 des cbc's in 3.00s > Doing des ede3 for 3s on 16 size blocks: 683496 des ede3's in 3.00s > Doing des ede3 for 3s on 64 size blocks: 173872 des ede3's in 3.00s > Doing des ede3 for 3s on 256 size blocks: 43687 des ede3's in 3.00s > Doing des ede3 for 3s on 1024 size blocks: 10935 des ede3's in 3.00s > Doing des ede3 for 3s on 8192 size blocks: 1368 des ede3's in 3.00s > Doing aes-128 cbc for 3s on 16 size blocks: 1938588 aes-128 cbc's > in 3.00s > Doing aes-128 cbc for 3s on 64 size blocks: 639237 aes-128 cbc's in > 3.00s > Doing aes-128 cbc for 3s on 256 size blocks: 174908 aes-128 cbc's > in 3.00s > Doing aes-128 cbc for 3s on 1024 size blocks: 44788 aes-128 cbc's > in 3.00s > Doing aes-128 cbc for 3s on 8192 size blocks: 5634 aes-128 cbc's in > 3.00s > Doing aes-192 cbc for 3s on 16 size blocks: 1729724 aes-192 cbc's > in 2.99s > Doing aes-192 cbc for 3s on 64 size blocks: 551407 aes-192 cbc's in > 3.00s > Doing aes-192 cbc for 3s on 256 size blocks: 148931 aes-192 cbc's > in 3.00s > Doing aes-192 cbc for 3s on 1024 size blocks: 37997 aes-192 cbc's > in 3.00s > Doing aes-192 cbc for 3s on 8192 size blocks: 4776 aes-192 cbc's in > 3.00s > Doing aes-256 cbc for 3s on 16 size blocks: 1559511 aes-256 cbc's > in 3.00s > Doing aes-256 cbc for 3s on 64 size blocks: 475710 aes-256 cbc's in > 3.00s > Doing aes-256 cbc for 3s on 256 size blocks: 127127 aes-256 cbc's > in 3.00s > Doing aes-256 cbc for 3s on 1024 size blocks: 32337 aes-256 cbc's > in 3.00s > Doing aes-256 cbc for 3s on 8192 size blocks: 4062 aes-256 cbc's in > 3.00s > Doing idea cbc for 3s on 16 size blocks: 1457450 idea cbc's in 3.00s > Doing idea cbc for 3s on 64 size blocks: 388023 idea cbc's in 3.00s > Doing idea cbc for 3s on 256 size blocks: 98607 idea cbc's in 3.00s > Doing idea cbc for 3s on 1024 size blocks: 24751 idea cbc's in 3.00s > Doing idea cbc for 3s on 8192 size blocks: 3098 idea cbc's in 3.00s > Doing rc2 cbc for 3s on 16 size blocks: 999725 rc2 cbc's in 3.00s > Doing rc2 cbc for 3s on 64 size blocks: 260808 rc2 cbc's in 3.00s > Doing rc2 cbc for 3s on 256 size blocks: 65924 rc2 cbc's in 3.00s > Doing rc2 cbc for 3s on 1024 size blocks: 16527 rc2 cbc's in 3.00s > Doing rc2 cbc for 3s on 8192 size blocks: 2068 rc2 cbc's in 3.00s > Doing blowfish cbc for 3s on 16 size blocks: 3453174 blowfish cbc's > in 3.00s > Doing blowfish cbc for 3s on 64 size blocks: 919800 blowfish cbc's > in 3.00s > Doing blowfish cbc for 3s on 256 size blocks: 233331 blowfish cbc's > in 3.00s > Doing blowfish cbc for 3s on 1024 size blocks: 58648 blowfish cbc's > in 3.00s > Doing blowfish cbc for 3s on 8192 size blocks: 7342 blowfish cbc's > in 3.00s > Doing cast cbc for 3s on 16 size blocks: 1489211 cast cbc's in 3.00s > Doing cast cbc for 3s on 64 size blocks: 390739 cast cbc's in 3.00s > Doing cast cbc for 3s on 256 size blocks: 99321 cast cbc's in 3.00s > Doing cast cbc for 3s on 1024 size blocks: 24935 cast cbc's in 3.00s > Doing cast cbc for 3s on 8192 size blocks: 3117 cast cbc's in 3.00s > Doing 512 bit private rsa's for 10s: 3144 512 bit private RSA's in > 10.00s > Doing 512 bit public rsa's for 10s: 40906 512 bit public RSA's in > 10.00s > Doing 1024 bit private rsa's for 10s: 693 1024 bit private RSA's in > 10.00s > Doing 1024 bit public rsa's for 10s: 14711 1024 bit public RSA's in > 10.00s > Doing 2048 bit private rsa's for 10s: 123 2048 bit private RSA's in > 10.04s > Doing 2048 bit public rsa's for 10s: 4521 2048 bit public RSA's in > 10.00s > Doing 4096 bit private rsa's for 10s: 19 4096 bit private RSA's in > 9.99s > Doing 4096 bit public rsa's for 10s: 1276 4096 bit public RSA's in > 10.00s > Doing 512 bit sign dsa's for 10s: 4276 512 bit DSA signs in 10.00s > Doing 512 bit verify dsa's for 10s: 3565 512 bit DSA verify in 10.00s > Doing 1024 bit sign dsa's for 10s: 1524 1024 bit DSA signs in 9.94s > Doing 1024 bit verify dsa's for 10s: 1210 1024 bit DSA verify in 9.61s > Doing 2048 bit sign dsa's for 10s: 466 2048 bit DSA signs in 10.00s > Doing 2048 bit verify dsa's for 10s: 385 2048 bit DSA verify in 10.01s > OpenSSL 0.9.8d 28 Sep 2006 > built on: Thu Oct 5 14:59:49 PDT 2006 > options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes > (partial) idea(int) blowfish(idx) > compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread - > D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 - > fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe - > mtune=i686 -march=pentiumpro -Wl,-rpath,/usr/local/lib - > DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM > available timing options: USE_TOD HZ=128 [sysconf value] > timing function used: getrusage > The 'numbers' are in 1000s of bytes per second processed. > type 16 bytes 64 bytes 256 bytes 1024 bytes > 8192 bytes > md2 487.74k 1035.01k 1439.70k > 1595.96k 1648.09k > mdc2 0.00 0.00 0.00 > 0.00 0.00 > md4 4084.48k 13874.63k 37969.97k > 67352.86k 87350.70k > md5 3949.20k 13765.67k 38809.49k > 70958.11k 93711.88k > hmac(md5) 5146.75k 16873.33k 44491.70k > 75283.53k 94651.38k > sha1 3291.04k 9982.17k 22723.55k > 33376.76k 38713.82k > rmd160 3027.84k 8519.94k 17725.07k > 24281.34k 27244.85k > rc4 35021.81k 39051.53k 40008.97k > 40450.15k 40579.31k > des cbc 10155.41k 10633.02k 10779.02k > 10815.92k 10827.19k > des ede3 3644.70k 3708.02k 3726.63k > 3731.14k 3732.61k > idea cbc 7772.10k 8274.88k 8411.48k > 8445.84k 8456.41k > rc2 cbc 5330.19k 5561.94k 5623.46k > 5638.97k 5643.18k > rc5-32/12 cbc 0.00 0.00 0.00 > 0.00 0.00 > blowfish cbc 18412.46k 19615.50k 19903.76k > 20011.27k 20042.36k > cast cbc 7939.92k 8332.80k 8472.38k > 8507.91k 8509.17k > aes-128 cbc 10336.74k 13632.21k 14921.12k > 15282.22k 15378.05k > aes-192 cbc 9243.95k 11759.17k 12704.51k > 12965.83k 13035.18k > aes-256 cbc 8315.79k 10144.85k 10844.33k > 11034.36k 11085.73k > camellia-128 cbc 0.00 0.00 0.00 > 0.00 0.00 > camellia-192 cbc 0.00 0.00 0.00 > 0.00 0.00 > camellia-256 cbc 0.00 0.00 0.00 > 0.00 0.00 > sha256 2111.53k 4857.49k 8477.58k > 10431.66k 11184.11k > sha512 487.68k 1950.02k 2877.14k > 3976.70k 4476.19k > sign verify sign/s verify/s > rsa 512 bits 0.003179s 0.000244s 314.5 4090.4 > rsa 1024 bits 0.014434s 0.000680s 69.3 1470.9 > rsa 2048 bits 0.081587s 0.002212s 12.3 452.0 > rsa 4096 bits 0.525871s 0.007841s 1.9 127.5 > sign verify sign/s verify/s > dsa 512 bits 0.002338s 0.002806s 427.8 356.4 > dsa 1024 bits 0.006522s 0.007944s 153.3 125.9 > dsa 2048 bits 0.021468s 0.026010s 46.6 38.4 > > _______________________________________________ > 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" -- David King Computer Programmer Ketralnis Systems From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 18:37:34 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6834A16A47E for ; Mon, 9 Oct 2006 18:37:34 +0000 (UTC) (envelope-from richw@richw.org) Received: from smtp2.stanford.edu (smtp2.Stanford.EDU [171.67.20.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3F9A43D72 for ; Mon, 9 Oct 2006 18:37:26 +0000 (GMT) (envelope-from richw@richw.org) Received: from smtp2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 798D74C438 for ; Mon, 9 Oct 2006 11:37:26 -0700 (PDT) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp2.stanford.edu (Postfix) with ESMTP id 34F984C0D9 for ; Mon, 9 Oct 2006 11:37:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by whodunit.richw.org (Postfix) with ESMTP id 00C453C4BE; Mon, 9 Oct 2006 11:37:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at richw.org Received: from whodunit.richw.org ([127.0.0.1]) by localhost (whodunit.richw.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdcsTEPi-mzU; Mon, 9 Oct 2006 11:37:25 -0700 (PDT) Received: from [171.66.139.173] (jessejames.stanford.edu [171.66.139.173]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "jessejames.richw.org", Issuer "richw.org" (verified OK)) (Authenticated sender: richw) by whodunit.richw.org (Postfix) with ESMTP id F249F3C36D; Mon, 9 Oct 2006 11:37:24 -0700 (PDT) Date: Mon, 09 Oct 2006 11:37:24 -0700 From: Rich Wales User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4525C731.1010206@spyderweb.com.au> In-Reply-To: <4525C731.1010206@spyderweb.com.au> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20061009183724.F249F3C36D@whodunit.richw.org> Subject: Re: SATA II controller 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, 09 Oct 2006 18:37:34 -0000 Tim Aslat wrote: > I'm in the market for a SATA II controller, which must be > supported under FreeBSD (6.1 or earlier). I don't need RAID > support of any kind, but it would be nice to have 4 ports to > plug in drives. Cheap is ok, provided I can access the drives > under FreeBSD and set up gmirror on the drives. You might want to consider the Promise SATA300 TX4. This is a 4-port, non-RAID card. It's supported in FreeBSD 6.1 and later, and it retails for about US$70. Two issues to be aware of w/r/t Promise SATA cards: (1) Some people (myself included) have reported problems with this and other Promise cards -- device timeouts under heavy load. Other people have no problems at all. It currently looks like these problems may be caused by iffy motherboard design and/or by Promise being overly strict about PCI bus tolerances. I was able to make the problem go away for me by downgrading the PCI bus performance in my experimental system's BIOS setup. (2) The ordering of the four SATA ports on this card (and other newer Promise cards with PDC4xxxx-series chips) is scrambled; the labelling of port numbers on the card itself is wrong. Both of the above issues have been reported by several people in numerous forums (they aren't unique to FreeBSD). A web page with a Linux discussion thread about the port enumeration problem can be found here (note that this is one big, long line, with three hyphens between "order" and the first "SATA", in case your e-mail reader insists on mangling it): http://www.nabble.com/-PATCH--sata_promise%3A-Port-enumeration-order---SATA-150-TX4%2C-SATA-300-TX4-t1184287.html Hopefully the port enumeration issue can be fixed sometime reasonably soon in the FreeBSD code, but I suspect it's probably not really a showstopper issue if you're using a mirrored configuration. Rich Wales Palo Alto, CA, USA richw@richw.org http://www.richw.org From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 20:02:23 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0510616A416 for ; Mon, 9 Oct 2006 20:02:23 +0000 (UTC) (envelope-from up@3.am) Received: from richard2.pil.net (mail.pil.net [207.7.198.3]) by mx1.FreeBSD.org (Postfix) with SMTP id CDC3743D69 for ; Mon, 9 Oct 2006 20:02:17 +0000 (GMT) (envelope-from up@3.am) Received: (qmail 339 invoked by uid 1825); 9 Oct 2006 20:02:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 Oct 2006 20:02:16 -0000 Date: Mon, 9 Oct 2006 16:02:16 -0400 (EDT) From: up@3.am X-X-Sender: up@richard2.pil.net To: freebsd-questions@freebsd.org, FreeBSD ISP List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: LSI SAS adapter 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, 09 Oct 2006 20:02:23 -0000 On Mon, 9 Oct 2006 up@3.am wrote: > > Can anyone verify that the LSI0100 PCI-X SAS RAID card will work with > 6.X-STABLE? The mfi driver says it supports LSI SAS MegaRAID, but this > isn't in the MegaRAID family (only does RAID 0 and 1, and I only need 1). > > All experiences appreciated...please reply directly as I am not > subscribed. > > Thanks! Oops, correction on the model number...the card itself is SAS3442X-R, the part number above is for the kit. TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 22:53:41 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C56F16A494 for ; Mon, 9 Oct 2006 22:53:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D95643D45 for ; Mon, 9 Oct 2006 22:53:40 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k99MrauX081356; Mon, 9 Oct 2006 18:53:36 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Mon, 9 Oct 2006 14:56:23 -0400 User-Agent: KMail/1.9.1 References: <4.2.2.20061005114011.00c0acd0@localhost> In-Reply-To: <4.2.2.20061005114011.00c0acd0@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610091456.23822.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Mon, 09 Oct 2006 18:53:36 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/2016/Mon Oct 9 12:58:54 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Joel Bradbury Subject: Re: Dell E521 won't boot FreeBSD 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, 09 Oct 2006 22:53:41 -0000 On Thursday 05 October 2006 15:42, Joel Bradbury wrote: > Well, it seemed like a good deal -- the new Dell E521 with an AMD 64 Athlon > 3200+, 1Gb memory, for $400 should make a decent, cheap server. But > FreeBSD just won't boot on it. I tried Release 6.1 (both amd64 and i386 > versions), as well as Releases 5.5 and 4.11. All give the same result when > trying to boot from the install cd: > > With the usb keyboard plugged in, the boot gets to a "panic: > ohci-add-done: addr 0x3bef1ba0 not found", and then it tries to reboot again. > With the keyboard unplugged, the ohci error never appears, but the boot > gets to a point of recognizing the SATA drive, and then just hangs. Last > message: "ad4: 152587MB at ata2-master SATA300" Did you try the 'Safe Mode' option? -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 9 22:53:42 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB74116A403; Mon, 9 Oct 2006 22:53:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38C4243D46; Mon, 9 Oct 2006 22:53:42 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k99MrauY081356; Mon, 9 Oct 2006 18:53:38 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Mon, 9 Oct 2006 15:02:53 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610091502.54225.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Mon, 09 Oct 2006 18:53:38 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/2016/Mon Oct 9 12:58:54 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00, DATE_IN_PAST_03_06 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-questions@freebsd.org, up@3.am Subject: Re: LSI SAS adapter 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, 09 Oct 2006 22:53:42 -0000 [ cc's trimmed ] On Monday 09 October 2006 11:12, up@3.am wrote: > > Can anyone verify that the LSI0100 PCI-X SAS RAID card will work with > 6.X-STABLE? The mfi driver says it supports LSI SAS MegaRAID, but this > isn't in the MegaRAID family (only does RAID 0 and 1, and I only need 1). > > All experiences appreciated...please reply directly as I am not > subscribed. The mpt(4) driver supports several of the LSI SAS HBA's (the ones that use the MPT/Fusion interface/firmware/whatever). I don't know if it specifically supports that adapter though as I can't find references to that specific adapter. If you had the PCI device ID that would be very helpful. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 10 14:25:04 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9984416A40F for ; Tue, 10 Oct 2006 14:25:04 +0000 (UTC) (envelope-from bjordan@lumeta.com) Received: from MAIL.corp.lumeta.com (h65-246-245-22.lumeta.com [65.246.245.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D80E543D78 for ; Tue, 10 Oct 2006 14:25:02 +0000 (GMT) (envelope-from bjordan@lumeta.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Oct 2006 10:25:01 -0400 Message-ID: <78ED28FACE63744386D68D8A9D1CF5D4209C5C@MAIL.corp.lumeta.com> In-Reply-To: <0C50F0B0-05B0-433A-8A45-D8872C916904@ketralnis.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Quiet computer Thread-Index: AcbryT9A5MZN61UER3C1loxVHVwt7gArjRMA From: "Bucky Jordan" To: "David King" , Cc: Subject: RE: Quiet computer 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, 10 Oct 2006 14:25:04 -0000 Hmm.. that's odd, the Woodcrest still stomps those numbers- I wonder if it's just a matter of difference in CPU speed, or intel has started adding some sort of hw crypto? Also, I'm running a stock 6.1-RELEASE amd64 kernel. - Bucky > -----Original Message----- > From: owner-freebsd-hardware@freebsd.org [mailto:owner-freebsd- > hardware@freebsd.org] On Behalf Of David King > Sent: Monday, October 09, 2006 1:30 PM > To: freebsd-hardware@freebsd.org > Subject: Re: Quiet computer >=20 > Here we are again with padlock(4) actually compiled into the kernel :) >=20 > OpenSSL 0.9.8d 28 Sep 2006 > built on: Thu Oct 5 14:59:49 PDT 2006 > options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes > (partial) idea(int) blowfish(idx) > compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread - > D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 - > fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe - > mtune=3Di686 -march=3Dpentiumpro -Wl,-rpath,/usr/local/lib - > DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM > available timing options: USE_TOD HZ=3D128 [sysconf value] > timing function used: getrusage > The 'numbers' are in 1000s of bytes per second processed. > type 16 bytes 64 bytes 256 bytes 1024 bytes > 8192 bytes > md2 484.96k 1028.72k 1430.85k 1586.47k > 1638.30k > mdc2 0.00 0.00 0.00 > 0.00 0.00 > md4 4032.03k 13842.55k 37818.93k 67152.92k > 86782.76k > md5 3911.84k 13584.08k 38591.74k 70378.22k > 93060.09k > hmac(md5) 5111.89k 16756.66k 44186.02k 74774.38k > 94053.88k > sha1 3254.06k 9925.14k 22536.35k 33177.25k > 38443.33k > rmd160 3017.47k 8466.50k 17600.37k 24115.23k > 27071.74k > rc4 34821.22k 38830.34k 39777.78k 40220.13k > 40324.81k > des cbc 10097.19k 10562.78k 10716.04k 10753.39k > 10764.02k > des ede3 3625.92k 3686.90k 3705.11k 3709.21k > 3710.78k > idea cbc 7725.38k 8227.10k 8359.48k 8391.42k > 8407.62k > rc2 cbc 5299.41k 5529.69k 5590.01k 5604.81k > 5607.09k > rc5-32/12 cbc 0.00 0.00 0.00 > 0.00 0.00 > blowfish cbc 18280.56k 19490.41k 19746.85k 19893.62k > 19916.51k > cast cbc 7892.93k 8284.10k 8421.85k 8459.11k > 8460.19k > aes-128 cbc 10276.54k 13552.14k 14833.08k 15191.43k > 15270.86k > aes-192 cbc 9167.52k 11687.66k 12628.19k 12888.71k > 12952.68k > aes-256 cbc 8266.91k 10057.43k 10768.40k 10957.97k > 11012.94k > camellia-128 cbc 0.00 0.00 0.00 > 0.00 0.00 > camellia-192 cbc 0.00 0.00 0.00 > 0.00 0.00 > camellia-256 cbc 0.00 0.00 0.00 > 0.00 0.00 > sha256 2098.35k 4825.75k 8423.74k 10366.23k > 11114.17k > sha512 484.15k 1935.12k 2858.82k 3951.34k > 4447.44k > sign verify sign/s verify/s > rsa 512 bits 0.003200s 0.000246s 312.5 4058.6 > rsa 1024 bits 0.014534s 0.000682s 68.8 1465.2 > rsa 2048 bits 0.082113s 0.002226s 12.2 449.2 > rsa 4096 bits 0.529857s 0.007901s 1.9 126.6 > sign verify sign/s verify/s > dsa 512 bits 0.002356s 0.002792s 424.5 358.2 > dsa 1024 bits 0.006577s 0.007967s 152.0 125.5 > dsa 2048 bits 0.021624s 0.026237s 46.2 38.1 >=20 >=20 > On 06 Oct 2006, at 22:05, David King wrote: >=20 > >> just do `openssl speed` > >> if you see some damn large numbers, you know 'tis hw crypto > >> working :) > > > > Okay, so I did it with /usr/bin/openssl and /usr/local/bin/openssl. > > Tell me what you think: > > > > ----------/usr/bin/openssl---------- > > To get the most accurate results, try to run this > > program when this computer is idle. > > Doing md2 for 3s on 16 size blocks: 95512 md2's in 2.98s > > Doing md2 for 3s on 64 size blocks: 50903 md2's in 2.99s > > Doing md2 for 3s on 256 size blocks: 17768 md2's in 2.99s > > Doing md2 for 3s on 1024 size blocks: 4928 md2's in 2.99s > > Doing md2 for 3s on 8192 size blocks: 637 md2's in 2.99s > > Doing mdc2 for 3s on 16 size blocks: 218133 mdc2's in 2.98s > > Doing mdc2 for 3s on 64 size blocks: 61692 mdc2's in 2.99s > > Doing mdc2 for 3s on 256 size blocks: 15949 mdc2's in 2.99s > > Doing mdc2 for 3s on 1024 size blocks: 4024 mdc2's in 2.99s > > Doing mdc2 for 3s on 8192 size blocks: 505 mdc2's in 2.99s > > Doing md4 for 3s on 16 size blocks: 810042 md4's in 2.99s > > Doing md4 for 3s on 64 size blocks: 692610 md4's in 2.99s > > Doing md4 for 3s on 256 size blocks: 470095 md4's in 2.99s > > Doing md4 for 3s on 1024 size blocks: 204791 md4's in 2.99s > > Doing md4 for 3s on 8192 size blocks: 32865 md4's in 2.99s > > Doing md5 for 3s on 16 size blocks: 677259 md5's in 2.99s > > Doing md5 for 3s on 64 size blocks: 558167 md5's in 2.99s > > Doing md5 for 3s on 256 size blocks: 356691 md5's in 2.99s > > Doing md5 for 3s on 1024 size blocks: 146187 md5's in 2.99s > > Doing md5 for 3s on 8192 size blocks: 22488 md5's in 2.99s > > Doing hmac(md5) for 3s on 16 size blocks: 674479 hmac(md5)'s in 2.99s > > Doing hmac(md5) for 3s on 64 size blocks: 553966 hmac(md5)'s in 2.99s > > Doing hmac(md5) for 3s on 256 size blocks: 356030 hmac(md5)'s in 2.99s > > Doing hmac(md5) for 3s on 1024 size blocks: 146028 hmac(md5)'s in > > 2.99s > > Doing hmac(md5) for 3s on 8192 size blocks: 22487 hmac(md5)'s in 2.98s > > Doing sha1 for 3s on 16 size blocks: 574104 sha1's in 2.99s > > Doing sha1 for 3s on 64 size blocks: 398438 sha1's in 2.99s > > Doing sha1 for 3s on 256 size blocks: 205800 sha1's in 2.99s > > Doing sha1 for 3s on 1024 size blocks: 70157 sha1's in 2.99s > > Doing sha1 for 3s on 8192 size blocks: 9810 sha1's in 2.99s > > Doing rmd160 for 3s on 16 size blocks: 469010 rmd160's in 2.98s > > Doing rmd160 for 3s on 64 size blocks: 311884 rmd160's in 2.99s > > Doing rmd160 for 3s on 256 size blocks: 153384 rmd160's in 2.99s > > Doing rmd160 for 3s on 1024 size blocks: 50539 rmd160's in 2.98s > > Doing rmd160 for 3s on 8192 size blocks: 6963 rmd160's in 2.98s > > Doing rc4 for 3s on 16 size blocks: 6933407 rc4's in 2.99s > > Doing rc4 for 3s on 64 size blocks: 1923083 rc4's in 2.98s > > Doing rc4 for 3s on 256 size blocks: 489508 rc4's in 2.96s > > Doing rc4 for 3s on 1024 size blocks: 123724 rc4's in 2.97s > > Doing rc4 for 3s on 8192 size blocks: 15556 rc4's in 2.97s > > Doing des cbc for 3s on 16 size blocks: 2105375 des cbc's in 2.98s > > Doing des cbc for 3s on 64 size blocks: 543605 des cbc's in 2.98s > > Doing des cbc for 3s on 256 size blocks: 137827 des cbc's in 2.98s > > Doing des cbc for 3s on 1024 size blocks: 34556 des cbc's in 2.98s > > Doing des cbc for 3s on 8192 size blocks: 4323 des cbc's in 2.98s > > Doing des ede3 for 3s on 16 size blocks: 756533 des ede3's in 2.98s > > Doing des ede3 for 3s on 64 size blocks: 191674 des ede3's in 2.98s > > Doing des ede3 for 3s on 256 size blocks: 48143 des ede3's in 2.98s > > Doing des ede3 for 3s on 1024 size blocks: 12056 des ede3's in 2.99s > > Doing des ede3 for 3s on 8192 size blocks: 1507 des ede3's in 2.99s > > Doing aes-128 cbc for 3s on 16 size blocks: 1683023 aes-128 cbc's > > in 2.98s > > Doing aes-128 cbc for 3s on 64 size blocks: 428016 aes-128 cbc's in > > 2.98s > > Doing aes-128 cbc for 3s on 256 size blocks: 108105 aes-128 cbc's > > in 2.99s > > Doing aes-128 cbc for 3s on 1024 size blocks: 27079 aes-128 cbc's > > in 2.98s > > Doing aes-128 cbc for 3s on 8192 size blocks: 3388 aes-128 cbc's in > > 2.98s > > Doing aes-192 cbc for 3s on 16 size blocks: 1470225 aes-192 cbc's > > in 2.98s > > Doing aes-192 cbc for 3s on 64 size blocks: 373644 aes-192 cbc's in > > 2.98s > > Doing aes-192 cbc for 3s on 256 size blocks: 94170 aes-192 cbc's in > > 2.98s > > Doing aes-192 cbc for 3s on 1024 size blocks: 23586 aes-192 cbc's > > in 2.98s > > Doing aes-192 cbc for 3s on 8192 size blocks: 2951 aes-192 cbc's in > > 2.98s > > Doing aes-256 cbc for 3s on 16 size blocks: 1305813 aes-256 cbc's > > in 2.98s > > Doing aes-256 cbc for 3s on 64 size blocks: 331577 aes-256 cbc's in > > 2.99s > > Doing aes-256 cbc for 3s on 256 size blocks: 83473 aes-256 cbc's in > > 2.99s > > Doing aes-256 cbc for 3s on 1024 size blocks: 20912 aes-256 cbc's > > in 2.99s > > Doing aes-256 cbc for 3s on 8192 size blocks: 2616 aes-256 cbc's in > > 2.99s > > Doing rc2 cbc for 3s on 16 size blocks: 1043269 rc2 cbc's in 2.99s > > Doing rc2 cbc for 3s on 64 size blocks: 271026 rc2 cbc's in 2.99s > > Doing rc2 cbc for 3s on 256 size blocks: 68365 rc2 cbc's in 2.98s > > Doing rc2 cbc for 3s on 1024 size blocks: 17147 rc2 cbc's in 2.99s > > Doing rc2 cbc for 3s on 8192 size blocks: 2145 rc2 cbc's in 2.99s > > Doing rc5-32/12 cbc for 3s on 16 size blocks: 6393672 rc5-32/12 > > cbc's in 2.98s > > Doing rc5-32/12 cbc for 3s on 64 size blocks: 1774376 rc5-32/12 > > cbc's in 2.98s > > Doing rc5-32/12 cbc for 3s on 256 size blocks: 462590 rc5-32/12 > > cbc's in 2.99s > > Doing rc5-32/12 cbc for 3s on 1024 size blocks: 116817 rc5-32/12 > > cbc's in 2.98s > > Doing rc5-32/12 cbc for 3s on 8192 size blocks: 14622 rc5-32/12 > > cbc's in 2.98s > > Doing blowfish cbc for 3s on 16 size blocks: 3515807 blowfish cbc's > > in 2.99s > > Doing blowfish cbc for 3s on 64 size blocks: 936491 blowfish cbc's > > in 2.99s > > Doing blowfish cbc for 3s on 256 size blocks: 237486 blowfish cbc's > > in 2.99s > > Doing blowfish cbc for 3s on 1024 size blocks: 59693 blowfish cbc's > > in 2.99s > > Doing blowfish cbc for 3s on 8192 size blocks: 7472 blowfish cbc's > > in 2.99s > > Doing cast cbc for 3s on 16 size blocks: 3594419 cast cbc's in 2.99s > > Doing cast cbc for 3s on 64 size blocks: 950631 cast cbc's in 2.98s > > Doing cast cbc for 3s on 256 size blocks: 243324 cast cbc's in 2.99s > > Doing cast cbc for 3s on 1024 size blocks: 61170 cast cbc's in 2.99s > > Doing cast cbc for 3s on 8192 size blocks: 7649 cast cbc's in 2.99s > > Doing 512 bit private rsa's for 10s: 3567 512 bit private RSA's in > > 9.95s > > Doing 512 bit public rsa's for 10s: 31284 512 bit public RSA's in > > 9.94s > > Doing 1024 bit private rsa's for 10s: 786 1024 bit private RSA's in > > 9.94s > > Doing 1024 bit public rsa's for 10s: 12643 1024 bit public RSA's in > > 9.94s > > Doing 2048 bit private rsa's for 10s: 137 2048 bit private RSA's in > > 10.02s > > Doing 2048 bit public rsa's for 10s: 4089 2048 bit public RSA's in > > 9.95s > > Doing 4096 bit private rsa's for 10s: 21 4096 bit private RSA's in > > 10.05s > > Doing 4096 bit public rsa's for 10s: 1174 4096 bit public RSA's in > > 9.95s > > Doing 512 bit sign dsa's for 10s: 4423 512 bit DSA signs in 9.56s > > Doing 512 bit verify dsa's for 10s: 3685 512 bit DSA verify in 10.00s > > Doing 1024 bit sign dsa's for 10s: 1557 1024 bit DSA signs in 10.00s > > Doing 1024 bit verify dsa's for 10s: 1301 1024 bit DSA verify in > > 10.00s > > Doing 2048 bit sign dsa's for 10s: 474 2048 bit DSA signs in 9.99s > > Doing 2048 bit verify dsa's for 10s: 384 2048 bit DSA verify in 10.02s > > OpenSSL 0.9.7e-p1 25 Oct 2004 > > built on: Fri Sep 22 23:34:15 PDT 2006 > > options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes > > (partial) blowfish(idx) > > compiler: cc > > available timing options: USE_TOD HZ=3D128 [sysconf value] > > timing function used: getrusage > > The 'numbers' are in 1000s of bytes per second processed. > > type 16 bytes 64 bytes 256 bytes 1024 bytes > > 8192 bytes > > md2 512.69k 1091.17k 1522.88k > > 1689.62k 1745.43k > > mdc2 1169.74k 1322.64k 1367.51k > > 1379.38k 1383.02k > > md4 4339.88k 14841.95k 40292.45k > > 70247.92k 90135.45k > > md5 3627.96k 11962.71k 30571.03k > > 50116.72k 61675.11k > > hmac(md5) 3613.31k 11871.78k 30517.83k > > 50067.31k 61713.54k > > sha1 3075.34k 8538.22k 17643.58k > > 24059.81k 26914.86k > > rmd160 2516.37k 6686.89k 13151.09k > > 17339.59k 19132.95k > > rc4 37157.99k 41299.57k 42307.37k > > 42724.09k 42851.07k > > des cbc 11291.64k 11682.42k 11826.20k > > 11862.20k 11870.63k > > des ede3 4055.37k 4110.76k 4129.60k > > 4134.81k 4134.77k > > idea cbc 0.00 0.00 0.00 > > 0.00 0.00 > > rc2 cbc 5588.96k 5808.52k 5865.79k > > 5880.90k 5884.61k > > rc5-32/12 cbc 34280.23k 38109.91k 39666.58k > > 40080.87k 40200.80k > > blowfish cbc 18839.66k 20068.64k 20363.22k > > 20468.75k 20500.88k > > cast cbc 19266.28k 20417.46k 20859.22k > > 20972.79k 20977.22k > > aes-128 cbc 9039.90k 9186.16k 9270.87k > > 9292.88k 9298.58k > > aes-192 cbc 7884.05k 8013.09k 8078.25k > > 8093.83k 8099.55k > > aes-256 cbc 7005.10k 7106.64k 7157.91k > > 7170.89k 7173.38k > > sign verify sign/s verify/s > > rsa 512 bits 0.0028s 0.0003s 358.5 3147.9 > > rsa 1024 bits 0.0126s 0.0008s 79.1 1272.5 > > rsa 2048 bits 0.0732s 0.0024s 13.7 411.0 > > rsa 4096 bits 0.4788s 0.0085s 2.1 117.9 > > sign verify sign/s verify/s > > dsa 512 bits 0.0022s 0.0027s 462.6 368.4 > > dsa 1024 bits 0.0064s 0.0077s 155.6 130.1 > > dsa 2048 bits 0.0211s 0.0261s 47.4 38.3 > > > > ----------/usr/local/bin/opensl---------- > > > > To get the most accurate results, try to run this > > program when this computer is idle. > > Doing md2 for 3s on 16 size blocks: 91481 md2's in 3.00s > > Doing md2 for 3s on 64 size blocks: 48533 md2's in 3.00s > > Doing md2 for 3s on 256 size blocks: 16878 md2's in 3.00s > > Doing md2 for 3s on 1024 size blocks: 4678 md2's in 3.00s > > Doing md2 for 3s on 8192 size blocks: 604 md2's in 3.00s > > Doing md4 for 3s on 16 size blocks: 765870 md4's in 3.00s > > Doing md4 for 3s on 64 size blocks: 650603 md4's in 3.00s > > Doing md4 for 3s on 256 size blocks: 445118 md4's in 3.00s > > Doing md4 for 3s on 1024 size blocks: 197393 md4's in 3.00s > > Doing md4 for 3s on 8192 size blocks: 32000 md4's in 3.00s > > Doing md5 for 3s on 16 size blocks: 740691 md5's in 3.00s > > Doing md5 for 3s on 64 size blocks: 645494 md5's in 3.00s > > Doing md5 for 3s on 256 size blocks: 454959 md5's in 3.00s > > Doing md5 for 3s on 1024 size blocks: 207958 md5's in 3.00s > > Doing md5 for 3s on 8192 size blocks: 34331 md5's in 3.00s > > Doing hmac(md5) for 3s on 16 size blocks: 965270 hmac(md5)'s in 3.00s > > Doing hmac(md5) for 3s on 64 size blocks: 791215 hmac(md5)'s in 3.00s > > Doing hmac(md5) for 3s on 256 size blocks: 521572 hmac(md5)'s in 3.00s > > Doing hmac(md5) for 3s on 1024 size blocks: 220635 hmac(md5)'s in > > 3.00s > > Doing hmac(md5) for 3s on 8192 size blocks: 34675 hmac(md5)'s in 3.00s > > Doing sha1 for 3s on 16 size blocks: 617279 sha1's in 3.00s > > Doing sha1 for 3s on 64 size blocks: 468049 sha1's in 3.00s > > Doing sha1 for 3s on 256 size blocks: 266386 sha1's in 3.00s > > Doing sha1 for 3s on 1024 size blocks: 97818 sha1's in 3.00s > > Doing sha1 for 3s on 8192 size blocks: 14182 sha1's in 3.00s > > Doing sha256 for 3s on 16 size blocks: 396047 sha256's in 3.00s > > Doing sha256 for 3s on 64 size blocks: 227772 sha256's in 3.00s > > Doing sha256 for 3s on 256 size blocks: 99380 sha256's in 3.00s > > Doing sha256 for 3s on 1024 size blocks: 30573 sha256's in 3.00s > > Doing sha256 for 3s on 8192 size blocks: 4098 sha256's in 3.00s > > Doing sha512 for 3s on 16 size blocks: 91452 sha512's in 3.00s > > Doing sha512 for 3s on 64 size blocks: 91440 sha512's in 3.00s > > Doing sha512 for 3s on 256 size blocks: 33728 sha512's in 3.00s > > Doing sha512 for 3s on 1024 size blocks: 11654 sha512's in 3.00s > > Doing sha512 for 3s on 8192 size blocks: 1640 sha512's in 3.00s > > Doing rmd160 for 3s on 16 size blocks: 567819 rmd160's in 3.00s > > Doing rmd160 for 3s on 64 size blocks: 399514 rmd160's in 3.00s > > Doing rmd160 for 3s on 256 size blocks: 207789 rmd160's in 3.00s > > Doing rmd160 for 3s on 1024 size blocks: 71158 rmd160's in 3.00s > > Doing rmd160 for 3s on 8192 size blocks: 9981 rmd160's in 3.00s > > Doing rc4 for 3s on 16 size blocks: 6568769 rc4's in 3.00s > > Doing rc4 for 3s on 64 size blocks: 1831119 rc4's in 3.00s > > Doing rc4 for 3s on 256 size blocks: 469013 rc4's in 3.00s > > Doing rc4 for 3s on 1024 size blocks: 118548 rc4's in 3.00s > > Doing rc4 for 3s on 8192 size blocks: 14866 rc4's in 3.00s > > Doing des cbc for 3s on 16 size blocks: 1904652 des cbc's in 3.00s > > Doing des cbc for 3s on 64 size blocks: 498596 des cbc's in 3.00s > > Doing des cbc for 3s on 256 size blocks: 126362 des cbc's in 3.00s > > Doing des cbc for 3s on 1024 size blocks: 31699 des cbc's in 3.00s > > Doing des cbc for 3s on 8192 size blocks: 3967 des cbc's in 3.00s > > Doing des ede3 for 3s on 16 size blocks: 683496 des ede3's in 3.00s > > Doing des ede3 for 3s on 64 size blocks: 173872 des ede3's in 3.00s > > Doing des ede3 for 3s on 256 size blocks: 43687 des ede3's in 3.00s > > Doing des ede3 for 3s on 1024 size blocks: 10935 des ede3's in 3.00s > > Doing des ede3 for 3s on 8192 size blocks: 1368 des ede3's in 3.00s > > Doing aes-128 cbc for 3s on 16 size blocks: 1938588 aes-128 cbc's > > in 3.00s > > Doing aes-128 cbc for 3s on 64 size blocks: 639237 aes-128 cbc's in > > 3.00s > > Doing aes-128 cbc for 3s on 256 size blocks: 174908 aes-128 cbc's > > in 3.00s > > Doing aes-128 cbc for 3s on 1024 size blocks: 44788 aes-128 cbc's > > in 3.00s > > Doing aes-128 cbc for 3s on 8192 size blocks: 5634 aes-128 cbc's in > > 3.00s > > Doing aes-192 cbc for 3s on 16 size blocks: 1729724 aes-192 cbc's > > in 2.99s > > Doing aes-192 cbc for 3s on 64 size blocks: 551407 aes-192 cbc's in > > 3.00s > > Doing aes-192 cbc for 3s on 256 size blocks: 148931 aes-192 cbc's > > in 3.00s > > Doing aes-192 cbc for 3s on 1024 size blocks: 37997 aes-192 cbc's > > in 3.00s > > Doing aes-192 cbc for 3s on 8192 size blocks: 4776 aes-192 cbc's in > > 3.00s > > Doing aes-256 cbc for 3s on 16 size blocks: 1559511 aes-256 cbc's > > in 3.00s > > Doing aes-256 cbc for 3s on 64 size blocks: 475710 aes-256 cbc's in > > 3.00s > > Doing aes-256 cbc for 3s on 256 size blocks: 127127 aes-256 cbc's > > in 3.00s > > Doing aes-256 cbc for 3s on 1024 size blocks: 32337 aes-256 cbc's > > in 3.00s > > Doing aes-256 cbc for 3s on 8192 size blocks: 4062 aes-256 cbc's in > > 3.00s > > Doing idea cbc for 3s on 16 size blocks: 1457450 idea cbc's in 3.00s > > Doing idea cbc for 3s on 64 size blocks: 388023 idea cbc's in 3.00s > > Doing idea cbc for 3s on 256 size blocks: 98607 idea cbc's in 3.00s > > Doing idea cbc for 3s on 1024 size blocks: 24751 idea cbc's in 3.00s > > Doing idea cbc for 3s on 8192 size blocks: 3098 idea cbc's in 3.00s > > Doing rc2 cbc for 3s on 16 size blocks: 999725 rc2 cbc's in 3.00s > > Doing rc2 cbc for 3s on 64 size blocks: 260808 rc2 cbc's in 3.00s > > Doing rc2 cbc for 3s on 256 size blocks: 65924 rc2 cbc's in 3.00s > > Doing rc2 cbc for 3s on 1024 size blocks: 16527 rc2 cbc's in 3.00s > > Doing rc2 cbc for 3s on 8192 size blocks: 2068 rc2 cbc's in 3.00s > > Doing blowfish cbc for 3s on 16 size blocks: 3453174 blowfish cbc's > > in 3.00s > > Doing blowfish cbc for 3s on 64 size blocks: 919800 blowfish cbc's > > in 3.00s > > Doing blowfish cbc for 3s on 256 size blocks: 233331 blowfish cbc's > > in 3.00s > > Doing blowfish cbc for 3s on 1024 size blocks: 58648 blowfish cbc's > > in 3.00s > > Doing blowfish cbc for 3s on 8192 size blocks: 7342 blowfish cbc's > > in 3.00s > > Doing cast cbc for 3s on 16 size blocks: 1489211 cast cbc's in 3.00s > > Doing cast cbc for 3s on 64 size blocks: 390739 cast cbc's in 3.00s > > Doing cast cbc for 3s on 256 size blocks: 99321 cast cbc's in 3.00s > > Doing cast cbc for 3s on 1024 size blocks: 24935 cast cbc's in 3.00s > > Doing cast cbc for 3s on 8192 size blocks: 3117 cast cbc's in 3.00s > > Doing 512 bit private rsa's for 10s: 3144 512 bit private RSA's in > > 10.00s > > Doing 512 bit public rsa's for 10s: 40906 512 bit public RSA's in > > 10.00s > > Doing 1024 bit private rsa's for 10s: 693 1024 bit private RSA's in > > 10.00s > > Doing 1024 bit public rsa's for 10s: 14711 1024 bit public RSA's in > > 10.00s > > Doing 2048 bit private rsa's for 10s: 123 2048 bit private RSA's in > > 10.04s > > Doing 2048 bit public rsa's for 10s: 4521 2048 bit public RSA's in > > 10.00s > > Doing 4096 bit private rsa's for 10s: 19 4096 bit private RSA's in > > 9.99s > > Doing 4096 bit public rsa's for 10s: 1276 4096 bit public RSA's in > > 10.00s > > Doing 512 bit sign dsa's for 10s: 4276 512 bit DSA signs in 10.00s > > Doing 512 bit verify dsa's for 10s: 3565 512 bit DSA verify in 10.00s > > Doing 1024 bit sign dsa's for 10s: 1524 1024 bit DSA signs in 9.94s > > Doing 1024 bit verify dsa's for 10s: 1210 1024 bit DSA verify in 9.61s > > Doing 2048 bit sign dsa's for 10s: 466 2048 bit DSA signs in 10.00s > > Doing 2048 bit verify dsa's for 10s: 385 2048 bit DSA verify in 10.01s > > OpenSSL 0.9.8d 28 Sep 2006 > > built on: Thu Oct 5 14:59:49 PDT 2006 > > options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes > > (partial) idea(int) blowfish(idx) > > compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread - > > D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 - > > fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe - > > mtune=3Di686 -march=3Dpentiumpro -Wl,-rpath,/usr/local/lib - > > DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM > > available timing options: USE_TOD HZ=3D128 [sysconf value] > > timing function used: getrusage > > The 'numbers' are in 1000s of bytes per second processed. > > type 16 bytes 64 bytes 256 bytes 1024 bytes > > 8192 bytes > > md2 487.74k 1035.01k 1439.70k > > 1595.96k 1648.09k > > mdc2 0.00 0.00 0.00 > > 0.00 0.00 > > md4 4084.48k 13874.63k 37969.97k > > 67352.86k 87350.70k > > md5 3949.20k 13765.67k 38809.49k > > 70958.11k 93711.88k > > hmac(md5) 5146.75k 16873.33k 44491.70k > > 75283.53k 94651.38k > > sha1 3291.04k 9982.17k 22723.55k > > 33376.76k 38713.82k > > rmd160 3027.84k 8519.94k 17725.07k > > 24281.34k 27244.85k > > rc4 35021.81k 39051.53k 40008.97k > > 40450.15k 40579.31k > > des cbc 10155.41k 10633.02k 10779.02k > > 10815.92k 10827.19k > > des ede3 3644.70k 3708.02k 3726.63k > > 3731.14k 3732.61k > > idea cbc 7772.10k 8274.88k 8411.48k > > 8445.84k 8456.41k > > rc2 cbc 5330.19k 5561.94k 5623.46k > > 5638.97k 5643.18k > > rc5-32/12 cbc 0.00 0.00 0.00 > > 0.00 0.00 > > blowfish cbc 18412.46k 19615.50k 19903.76k > > 20011.27k 20042.36k > > cast cbc 7939.92k 8332.80k 8472.38k > > 8507.91k 8509.17k > > aes-128 cbc 10336.74k 13632.21k 14921.12k > > 15282.22k 15378.05k > > aes-192 cbc 9243.95k 11759.17k 12704.51k > > 12965.83k 13035.18k > > aes-256 cbc 8315.79k 10144.85k 10844.33k > > 11034.36k 11085.73k > > camellia-128 cbc 0.00 0.00 0.00 > > 0.00 0.00 > > camellia-192 cbc 0.00 0.00 0.00 > > 0.00 0.00 > > camellia-256 cbc 0.00 0.00 0.00 > > 0.00 0.00 > > sha256 2111.53k 4857.49k 8477.58k > > 10431.66k 11184.11k > > sha512 487.68k 1950.02k 2877.14k > > 3976.70k 4476.19k > > sign verify sign/s verify/s > > rsa 512 bits 0.003179s 0.000244s 314.5 4090.4 > > rsa 1024 bits 0.014434s 0.000680s 69.3 1470.9 > > rsa 2048 bits 0.081587s 0.002212s 12.3 452.0 > > rsa 4096 bits 0.525871s 0.007841s 1.9 127.5 > > sign verify sign/s verify/s > > dsa 512 bits 0.002338s 0.002806s 427.8 356.4 > > dsa 1024 bits 0.006522s 0.007944s 153.3 125.9 > > dsa 2048 bits 0.021468s 0.026010s 46.6 38.4 > > > > _______________________________________________ > > 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" >=20 > -- > David King > Computer Programmer > Ketralnis Systems >=20 >=20 > _______________________________________________ > 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" From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 10 16:22:20 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01E6516A415 for ; Tue, 10 Oct 2006 16:22:20 +0000 (UTC) (envelope-from dking@ketralnis.com) Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03CCF43D45 for ; Tue, 10 Oct 2006 16:22:18 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [192.168.1.82] (pix.xythos.com [64.154.218.194]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9AGMC1A056072 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 10 Oct 2006 09:22:13 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209C5C@MAIL.corp.lumeta.com> References: <78ED28FACE63744386D68D8A9D1CF5D4209C5C@MAIL.corp.lumeta.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <36E6E927-AA04-43ED-928E-D06ABCE414CA@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Tue, 10 Oct 2006 09:21:58 -0700 To: freebsd-hardware@freebsd.org X-Mailer: Apple Mail (2.752.3) Subject: Re: Quiet computer 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, 10 Oct 2006 16:22:20 -0000 > Hmm.. that's odd, the Woodcrest still stomps those numbers- I > wonder if > it's just a matter of difference in CPU speed, or intel has started > adding some sort of hw crypto? Also, I'm running a stock 6.1-RELEASE > amd64 kernel. It might also be that OpenSSL isn't actually using the /dev/crypto device; I see from some postings that in order to get OpenSSL to use it, you have to give a command line switch like -engine. I played around with it a little, and while I don't know much about how OpenSSL defines engines, I did get this: ~% openssl speed -engine /dev/crypto invalid engine "/dev/crypto" 53289:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:162:filename(/dev/crypto): /dev/ crypto: read error: Input/output error 53289:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: 53289:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:450: 53289:error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:415:id=/dev/crypto 53289:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:162:filename(/dev/crypto): /dev/ crypto: read error: Input/output error 53289:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: 53289:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:450: To get the most accurate results, try to run this program when this computer is idle. [...] Does anyone with cryptographic hardware have experience with getting OpenSSL to use it? >> -----Original Message----- >> From: owner-freebsd-hardware@freebsd.org [mailto:owner-freebsd- >> hardware@freebsd.org] On Behalf Of David King >> Sent: Monday, October 09, 2006 1:30 PM >> To: freebsd-hardware@freebsd.org >> Subject: Re: Quiet computer >> >> Here we are again with padlock(4) actually compiled into the >> kernel :) >> >> OpenSSL 0.9.8d 28 Sep 2006 >> built on: Thu Oct 5 14:59:49 PDT 2006 >> options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes >> (partial) idea(int) blowfish(idx) >> compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread - >> D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 - >> fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe - >> mtune=i686 -march=pentiumpro -Wl,-rpath,/usr/local/lib - >> DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM - >> DAES_ASM >> available timing options: USE_TOD HZ=128 [sysconf value] >> timing function used: getrusage >> The 'numbers' are in 1000s of bytes per second processed. >> type 16 bytes 64 bytes 256 bytes 1024 bytes >> 8192 bytes >> md2 484.96k 1028.72k 1430.85k 1586.47k >> 1638.30k >> mdc2 0.00 0.00 0.00 >> 0.00 0.00 >> md4 4032.03k 13842.55k 37818.93k 67152.92k >> 86782.76k >> md5 3911.84k 13584.08k 38591.74k 70378.22k >> 93060.09k >> hmac(md5) 5111.89k 16756.66k 44186.02k 74774.38k >> 94053.88k >> sha1 3254.06k 9925.14k 22536.35k 33177.25k >> 38443.33k >> rmd160 3017.47k 8466.50k 17600.37k 24115.23k >> 27071.74k >> rc4 34821.22k 38830.34k 39777.78k 40220.13k >> 40324.81k >> des cbc 10097.19k 10562.78k 10716.04k 10753.39k >> 10764.02k >> des ede3 3625.92k 3686.90k 3705.11k 3709.21k >> 3710.78k >> idea cbc 7725.38k 8227.10k 8359.48k 8391.42k >> 8407.62k >> rc2 cbc 5299.41k 5529.69k 5590.01k 5604.81k >> 5607.09k >> rc5-32/12 cbc 0.00 0.00 0.00 >> 0.00 0.00 >> blowfish cbc 18280.56k 19490.41k 19746.85k 19893.62k >> 19916.51k >> cast cbc 7892.93k 8284.10k 8421.85k 8459.11k >> 8460.19k >> aes-128 cbc 10276.54k 13552.14k 14833.08k 15191.43k >> 15270.86k >> aes-192 cbc 9167.52k 11687.66k 12628.19k 12888.71k >> 12952.68k >> aes-256 cbc 8266.91k 10057.43k 10768.40k 10957.97k >> 11012.94k >> camellia-128 cbc 0.00 0.00 0.00 >> 0.00 0.00 >> camellia-192 cbc 0.00 0.00 0.00 >> 0.00 0.00 >> camellia-256 cbc 0.00 0.00 0.00 >> 0.00 0.00 >> sha256 2098.35k 4825.75k 8423.74k 10366.23k >> 11114.17k >> sha512 484.15k 1935.12k 2858.82k 3951.34k >> 4447.44k >> sign verify sign/s verify/s >> rsa 512 bits 0.003200s 0.000246s 312.5 4058.6 >> rsa 1024 bits 0.014534s 0.000682s 68.8 1465.2 >> rsa 2048 bits 0.082113s 0.002226s 12.2 449.2 >> rsa 4096 bits 0.529857s 0.007901s 1.9 126.6 >> sign verify sign/s verify/s >> dsa 512 bits 0.002356s 0.002792s 424.5 358.2 >> dsa 1024 bits 0.006577s 0.007967s 152.0 125.5 >> dsa 2048 bits 0.021624s 0.026237s 46.2 38.1 >> >> >> On 06 Oct 2006, at 22:05, David King wrote: >> >>>> just do `openssl speed` >>>> if you see some damn large numbers, you know 'tis hw crypto >>>> working :) >>> >>> Okay, so I did it with /usr/bin/openssl and /usr/local/bin/openssl. >>> Tell me what you think: >>> >>> ----------/usr/bin/openssl---------- >>> To get the most accurate results, try to run this >>> program when this computer is idle. >>> Doing md2 for 3s on 16 size blocks: 95512 md2's in 2.98s >>> Doing md2 for 3s on 64 size blocks: 50903 md2's in 2.99s >>> Doing md2 for 3s on 256 size blocks: 17768 md2's in 2.99s >>> Doing md2 for 3s on 1024 size blocks: 4928 md2's in 2.99s >>> Doing md2 for 3s on 8192 size blocks: 637 md2's in 2.99s >>> Doing mdc2 for 3s on 16 size blocks: 218133 mdc2's in 2.98s >>> Doing mdc2 for 3s on 64 size blocks: 61692 mdc2's in 2.99s >>> Doing mdc2 for 3s on 256 size blocks: 15949 mdc2's in 2.99s >>> Doing mdc2 for 3s on 1024 size blocks: 4024 mdc2's in 2.99s >>> Doing mdc2 for 3s on 8192 size blocks: 505 mdc2's in 2.99s >>> Doing md4 for 3s on 16 size blocks: 810042 md4's in 2.99s >>> Doing md4 for 3s on 64 size blocks: 692610 md4's in 2.99s >>> Doing md4 for 3s on 256 size blocks: 470095 md4's in 2.99s >>> Doing md4 for 3s on 1024 size blocks: 204791 md4's in 2.99s >>> Doing md4 for 3s on 8192 size blocks: 32865 md4's in 2.99s >>> Doing md5 for 3s on 16 size blocks: 677259 md5's in 2.99s >>> Doing md5 for 3s on 64 size blocks: 558167 md5's in 2.99s >>> Doing md5 for 3s on 256 size blocks: 356691 md5's in 2.99s >>> Doing md5 for 3s on 1024 size blocks: 146187 md5's in 2.99s >>> Doing md5 for 3s on 8192 size blocks: 22488 md5's in 2.99s >>> Doing hmac(md5) for 3s on 16 size blocks: 674479 hmac(md5)'s in > 2.99s >>> Doing hmac(md5) for 3s on 64 size blocks: 553966 hmac(md5)'s in > 2.99s >>> Doing hmac(md5) for 3s on 256 size blocks: 356030 hmac(md5)'s in > 2.99s >>> Doing hmac(md5) for 3s on 1024 size blocks: 146028 hmac(md5)'s in >>> 2.99s >>> Doing hmac(md5) for 3s on 8192 size blocks: 22487 hmac(md5)'s in > 2.98s >>> Doing sha1 for 3s on 16 size blocks: 574104 sha1's in 2.99s >>> Doing sha1 for 3s on 64 size blocks: 398438 sha1's in 2.99s >>> Doing sha1 for 3s on 256 size blocks: 205800 sha1's in 2.99s >>> Doing sha1 for 3s on 1024 size blocks: 70157 sha1's in 2.99s >>> Doing sha1 for 3s on 8192 size blocks: 9810 sha1's in 2.99s >>> Doing rmd160 for 3s on 16 size blocks: 469010 rmd160's in 2.98s >>> Doing rmd160 for 3s on 64 size blocks: 311884 rmd160's in 2.99s >>> Doing rmd160 for 3s on 256 size blocks: 153384 rmd160's in 2.99s >>> Doing rmd160 for 3s on 1024 size blocks: 50539 rmd160's in 2.98s >>> Doing rmd160 for 3s on 8192 size blocks: 6963 rmd160's in 2.98s >>> Doing rc4 for 3s on 16 size blocks: 6933407 rc4's in 2.99s >>> Doing rc4 for 3s on 64 size blocks: 1923083 rc4's in 2.98s >>> Doing rc4 for 3s on 256 size blocks: 489508 rc4's in 2.96s >>> Doing rc4 for 3s on 1024 size blocks: 123724 rc4's in 2.97s >>> Doing rc4 for 3s on 8192 size blocks: 15556 rc4's in 2.97s >>> Doing des cbc for 3s on 16 size blocks: 2105375 des cbc's in 2.98s >>> Doing des cbc for 3s on 64 size blocks: 543605 des cbc's in 2.98s >>> Doing des cbc for 3s on 256 size blocks: 137827 des cbc's in 2.98s >>> Doing des cbc for 3s on 1024 size blocks: 34556 des cbc's in 2.98s >>> Doing des cbc for 3s on 8192 size blocks: 4323 des cbc's in 2.98s >>> Doing des ede3 for 3s on 16 size blocks: 756533 des ede3's in 2.98s >>> Doing des ede3 for 3s on 64 size blocks: 191674 des ede3's in 2.98s >>> Doing des ede3 for 3s on 256 size blocks: 48143 des ede3's in 2.98s >>> Doing des ede3 for 3s on 1024 size blocks: 12056 des ede3's in 2.99s >>> Doing des ede3 for 3s on 8192 size blocks: 1507 des ede3's in 2.99s >>> Doing aes-128 cbc for 3s on 16 size blocks: 1683023 aes-128 cbc's >>> in 2.98s >>> Doing aes-128 cbc for 3s on 64 size blocks: 428016 aes-128 cbc's in >>> 2.98s >>> Doing aes-128 cbc for 3s on 256 size blocks: 108105 aes-128 cbc's >>> in 2.99s >>> Doing aes-128 cbc for 3s on 1024 size blocks: 27079 aes-128 cbc's >>> in 2.98s >>> Doing aes-128 cbc for 3s on 8192 size blocks: 3388 aes-128 cbc's in >>> 2.98s >>> Doing aes-192 cbc for 3s on 16 size blocks: 1470225 aes-192 cbc's >>> in 2.98s >>> Doing aes-192 cbc for 3s on 64 size blocks: 373644 aes-192 cbc's in >>> 2.98s >>> Doing aes-192 cbc for 3s on 256 size blocks: 94170 aes-192 cbc's in >>> 2.98s >>> Doing aes-192 cbc for 3s on 1024 size blocks: 23586 aes-192 cbc's >>> in 2.98s >>> Doing aes-192 cbc for 3s on 8192 size blocks: 2951 aes-192 cbc's in >>> 2.98s >>> Doing aes-256 cbc for 3s on 16 size blocks: 1305813 aes-256 cbc's >>> in 2.98s >>> Doing aes-256 cbc for 3s on 64 size blocks: 331577 aes-256 cbc's in >>> 2.99s >>> Doing aes-256 cbc for 3s on 256 size blocks: 83473 aes-256 cbc's in >>> 2.99s >>> Doing aes-256 cbc for 3s on 1024 size blocks: 20912 aes-256 cbc's >>> in 2.99s >>> Doing aes-256 cbc for 3s on 8192 size blocks: 2616 aes-256 cbc's in >>> 2.99s >>> Doing rc2 cbc for 3s on 16 size blocks: 1043269 rc2 cbc's in 2.99s >>> Doing rc2 cbc for 3s on 64 size blocks: 271026 rc2 cbc's in 2.99s >>> Doing rc2 cbc for 3s on 256 size blocks: 68365 rc2 cbc's in 2.98s >>> Doing rc2 cbc for 3s on 1024 size blocks: 17147 rc2 cbc's in 2.99s >>> Doing rc2 cbc for 3s on 8192 size blocks: 2145 rc2 cbc's in 2.99s >>> Doing rc5-32/12 cbc for 3s on 16 size blocks: 6393672 rc5-32/12 >>> cbc's in 2.98s >>> Doing rc5-32/12 cbc for 3s on 64 size blocks: 1774376 rc5-32/12 >>> cbc's in 2.98s >>> Doing rc5-32/12 cbc for 3s on 256 size blocks: 462590 rc5-32/12 >>> cbc's in 2.99s >>> Doing rc5-32/12 cbc for 3s on 1024 size blocks: 116817 rc5-32/12 >>> cbc's in 2.98s >>> Doing rc5-32/12 cbc for 3s on 8192 size blocks: 14622 rc5-32/12 >>> cbc's in 2.98s >>> Doing blowfish cbc for 3s on 16 size blocks: 3515807 blowfish cbc's >>> in 2.99s >>> Doing blowfish cbc for 3s on 64 size blocks: 936491 blowfish cbc's >>> in 2.99s >>> Doing blowfish cbc for 3s on 256 size blocks: 237486 blowfish cbc's >>> in 2.99s >>> Doing blowfish cbc for 3s on 1024 size blocks: 59693 blowfish cbc's >>> in 2.99s >>> Doing blowfish cbc for 3s on 8192 size blocks: 7472 blowfish cbc's >>> in 2.99s >>> Doing cast cbc for 3s on 16 size blocks: 3594419 cast cbc's in 2.99s >>> Doing cast cbc for 3s on 64 size blocks: 950631 cast cbc's in 2.98s >>> Doing cast cbc for 3s on 256 size blocks: 243324 cast cbc's in 2.99s >>> Doing cast cbc for 3s on 1024 size blocks: 61170 cast cbc's in 2.99s >>> Doing cast cbc for 3s on 8192 size blocks: 7649 cast cbc's in 2.99s >>> Doing 512 bit private rsa's for 10s: 3567 512 bit private RSA's in >>> 9.95s >>> Doing 512 bit public rsa's for 10s: 31284 512 bit public RSA's in >>> 9.94s >>> Doing 1024 bit private rsa's for 10s: 786 1024 bit private RSA's in >>> 9.94s >>> Doing 1024 bit public rsa's for 10s: 12643 1024 bit public RSA's in >>> 9.94s >>> Doing 2048 bit private rsa's for 10s: 137 2048 bit private RSA's in >>> 10.02s >>> Doing 2048 bit public rsa's for 10s: 4089 2048 bit public RSA's in >>> 9.95s >>> Doing 4096 bit private rsa's for 10s: 21 4096 bit private RSA's in >>> 10.05s >>> Doing 4096 bit public rsa's for 10s: 1174 4096 bit public RSA's in >>> 9.95s >>> Doing 512 bit sign dsa's for 10s: 4423 512 bit DSA signs in 9.56s >>> Doing 512 bit verify dsa's for 10s: 3685 512 bit DSA verify in > 10.00s >>> Doing 1024 bit sign dsa's for 10s: 1557 1024 bit DSA signs in 10.00s >>> Doing 1024 bit verify dsa's for 10s: 1301 1024 bit DSA verify in >>> 10.00s >>> Doing 2048 bit sign dsa's for 10s: 474 2048 bit DSA signs in 9.99s >>> Doing 2048 bit verify dsa's for 10s: 384 2048 bit DSA verify in > 10.02s >>> OpenSSL 0.9.7e-p1 25 Oct 2004 >>> built on: Fri Sep 22 23:34:15 PDT 2006 >>> options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes >>> (partial) blowfish(idx) >>> compiler: cc >>> available timing options: USE_TOD HZ=128 [sysconf value] >>> timing function used: getrusage >>> The 'numbers' are in 1000s of bytes per second processed. >>> type 16 bytes 64 bytes 256 bytes 1024 bytes >>> 8192 bytes >>> md2 512.69k 1091.17k 1522.88k >>> 1689.62k 1745.43k >>> mdc2 1169.74k 1322.64k 1367.51k >>> 1379.38k 1383.02k >>> md4 4339.88k 14841.95k 40292.45k >>> 70247.92k 90135.45k >>> md5 3627.96k 11962.71k 30571.03k >>> 50116.72k 61675.11k >>> hmac(md5) 3613.31k 11871.78k 30517.83k >>> 50067.31k 61713.54k >>> sha1 3075.34k 8538.22k 17643.58k >>> 24059.81k 26914.86k >>> rmd160 2516.37k 6686.89k 13151.09k >>> 17339.59k 19132.95k >>> rc4 37157.99k 41299.57k 42307.37k >>> 42724.09k 42851.07k >>> des cbc 11291.64k 11682.42k 11826.20k >>> 11862.20k 11870.63k >>> des ede3 4055.37k 4110.76k 4129.60k >>> 4134.81k 4134.77k >>> idea cbc 0.00 0.00 0.00 >>> 0.00 0.00 >>> rc2 cbc 5588.96k 5808.52k 5865.79k >>> 5880.90k 5884.61k >>> rc5-32/12 cbc 34280.23k 38109.91k 39666.58k >>> 40080.87k 40200.80k >>> blowfish cbc 18839.66k 20068.64k 20363.22k >>> 20468.75k 20500.88k >>> cast cbc 19266.28k 20417.46k 20859.22k >>> 20972.79k 20977.22k >>> aes-128 cbc 9039.90k 9186.16k 9270.87k >>> 9292.88k 9298.58k >>> aes-192 cbc 7884.05k 8013.09k 8078.25k >>> 8093.83k 8099.55k >>> aes-256 cbc 7005.10k 7106.64k 7157.91k >>> 7170.89k 7173.38k >>> sign verify sign/s verify/s >>> rsa 512 bits 0.0028s 0.0003s 358.5 3147.9 >>> rsa 1024 bits 0.0126s 0.0008s 79.1 1272.5 >>> rsa 2048 bits 0.0732s 0.0024s 13.7 411.0 >>> rsa 4096 bits 0.4788s 0.0085s 2.1 117.9 >>> sign verify sign/s verify/s >>> dsa 512 bits 0.0022s 0.0027s 462.6 368.4 >>> dsa 1024 bits 0.0064s 0.0077s 155.6 130.1 >>> dsa 2048 bits 0.0211s 0.0261s 47.4 38.3 >>> >>> ----------/usr/local/bin/opensl---------- >>> >>> To get the most accurate results, try to run this >>> program when this computer is idle. >>> Doing md2 for 3s on 16 size blocks: 91481 md2's in 3.00s >>> Doing md2 for 3s on 64 size blocks: 48533 md2's in 3.00s >>> Doing md2 for 3s on 256 size blocks: 16878 md2's in 3.00s >>> Doing md2 for 3s on 1024 size blocks: 4678 md2's in 3.00s >>> Doing md2 for 3s on 8192 size blocks: 604 md2's in 3.00s >>> Doing md4 for 3s on 16 size blocks: 765870 md4's in 3.00s >>> Doing md4 for 3s on 64 size blocks: 650603 md4's in 3.00s >>> Doing md4 for 3s on 256 size blocks: 445118 md4's in 3.00s >>> Doing md4 for 3s on 1024 size blocks: 197393 md4's in 3.00s >>> Doing md4 for 3s on 8192 size blocks: 32000 md4's in 3.00s >>> Doing md5 for 3s on 16 size blocks: 740691 md5's in 3.00s >>> Doing md5 for 3s on 64 size blocks: 645494 md5's in 3.00s >>> Doing md5 for 3s on 256 size blocks: 454959 md5's in 3.00s >>> Doing md5 for 3s on 1024 size blocks: 207958 md5's in 3.00s >>> Doing md5 for 3s on 8192 size blocks: 34331 md5's in 3.00s >>> Doing hmac(md5) for 3s on 16 size blocks: 965270 hmac(md5)'s in > 3.00s >>> Doing hmac(md5) for 3s on 64 size blocks: 791215 hmac(md5)'s in > 3.00s >>> Doing hmac(md5) for 3s on 256 size blocks: 521572 hmac(md5)'s in > 3.00s >>> Doing hmac(md5) for 3s on 1024 size blocks: 220635 hmac(md5)'s in >>> 3.00s >>> Doing hmac(md5) for 3s on 8192 size blocks: 34675 hmac(md5)'s in > 3.00s >>> Doing sha1 for 3s on 16 size blocks: 617279 sha1's in 3.00s >>> Doing sha1 for 3s on 64 size blocks: 468049 sha1's in 3.00s >>> Doing sha1 for 3s on 256 size blocks: 266386 sha1's in 3.00s >>> Doing sha1 for 3s on 1024 size blocks: 97818 sha1's in 3.00s >>> Doing sha1 for 3s on 8192 size blocks: 14182 sha1's in 3.00s >>> Doing sha256 for 3s on 16 size blocks: 396047 sha256's in 3.00s >>> Doing sha256 for 3s on 64 size blocks: 227772 sha256's in 3.00s >>> Doing sha256 for 3s on 256 size blocks: 99380 sha256's in 3.00s >>> Doing sha256 for 3s on 1024 size blocks: 30573 sha256's in 3.00s >>> Doing sha256 for 3s on 8192 size blocks: 4098 sha256's in 3.00s >>> Doing sha512 for 3s on 16 size blocks: 91452 sha512's in 3.00s >>> Doing sha512 for 3s on 64 size blocks: 91440 sha512's in 3.00s >>> Doing sha512 for 3s on 256 size blocks: 33728 sha512's in 3.00s >>> Doing sha512 for 3s on 1024 size blocks: 11654 sha512's in 3.00s >>> Doing sha512 for 3s on 8192 size blocks: 1640 sha512's in 3.00s >>> Doing rmd160 for 3s on 16 size blocks: 567819 rmd160's in 3.00s >>> Doing rmd160 for 3s on 64 size blocks: 399514 rmd160's in 3.00s >>> Doing rmd160 for 3s on 256 size blocks: 207789 rmd160's in 3.00s >>> Doing rmd160 for 3s on 1024 size blocks: 71158 rmd160's in 3.00s >>> Doing rmd160 for 3s on 8192 size blocks: 9981 rmd160's in 3.00s >>> Doing rc4 for 3s on 16 size blocks: 6568769 rc4's in 3.00s >>> Doing rc4 for 3s on 64 size blocks: 1831119 rc4's in 3.00s >>> Doing rc4 for 3s on 256 size blocks: 469013 rc4's in 3.00s >>> Doing rc4 for 3s on 1024 size blocks: 118548 rc4's in 3.00s >>> Doing rc4 for 3s on 8192 size blocks: 14866 rc4's in 3.00s >>> Doing des cbc for 3s on 16 size blocks: 1904652 des cbc's in 3.00s >>> Doing des cbc for 3s on 64 size blocks: 498596 des cbc's in 3.00s >>> Doing des cbc for 3s on 256 size blocks: 126362 des cbc's in 3.00s >>> Doing des cbc for 3s on 1024 size blocks: 31699 des cbc's in 3.00s >>> Doing des cbc for 3s on 8192 size blocks: 3967 des cbc's in 3.00s >>> Doing des ede3 for 3s on 16 size blocks: 683496 des ede3's in 3.00s >>> Doing des ede3 for 3s on 64 size blocks: 173872 des ede3's in 3.00s >>> Doing des ede3 for 3s on 256 size blocks: 43687 des ede3's in 3.00s >>> Doing des ede3 for 3s on 1024 size blocks: 10935 des ede3's in 3.00s >>> Doing des ede3 for 3s on 8192 size blocks: 1368 des ede3's in 3.00s >>> Doing aes-128 cbc for 3s on 16 size blocks: 1938588 aes-128 cbc's >>> in 3.00s >>> Doing aes-128 cbc for 3s on 64 size blocks: 639237 aes-128 cbc's in >>> 3.00s >>> Doing aes-128 cbc for 3s on 256 size blocks: 174908 aes-128 cbc's >>> in 3.00s >>> Doing aes-128 cbc for 3s on 1024 size blocks: 44788 aes-128 cbc's >>> in 3.00s >>> Doing aes-128 cbc for 3s on 8192 size blocks: 5634 aes-128 cbc's in >>> 3.00s >>> Doing aes-192 cbc for 3s on 16 size blocks: 1729724 aes-192 cbc's >>> in 2.99s >>> Doing aes-192 cbc for 3s on 64 size blocks: 551407 aes-192 cbc's in >>> 3.00s >>> Doing aes-192 cbc for 3s on 256 size blocks: 148931 aes-192 cbc's >>> in 3.00s >>> Doing aes-192 cbc for 3s on 1024 size blocks: 37997 aes-192 cbc's >>> in 3.00s >>> Doing aes-192 cbc for 3s on 8192 size blocks: 4776 aes-192 cbc's in >>> 3.00s >>> Doing aes-256 cbc for 3s on 16 size blocks: 1559511 aes-256 cbc's >>> in 3.00s >>> Doing aes-256 cbc for 3s on 64 size blocks: 475710 aes-256 cbc's in >>> 3.00s >>> Doing aes-256 cbc for 3s on 256 size blocks: 127127 aes-256 cbc's >>> in 3.00s >>> Doing aes-256 cbc for 3s on 1024 size blocks: 32337 aes-256 cbc's >>> in 3.00s >>> Doing aes-256 cbc for 3s on 8192 size blocks: 4062 aes-256 cbc's in >>> 3.00s >>> Doing idea cbc for 3s on 16 size blocks: 1457450 idea cbc's in 3.00s >>> Doing idea cbc for 3s on 64 size blocks: 388023 idea cbc's in 3.00s >>> Doing idea cbc for 3s on 256 size blocks: 98607 idea cbc's in 3.00s >>> Doing idea cbc for 3s on 1024 size blocks: 24751 idea cbc's in 3.00s >>> Doing idea cbc for 3s on 8192 size blocks: 3098 idea cbc's in 3.00s >>> Doing rc2 cbc for 3s on 16 size blocks: 999725 rc2 cbc's in 3.00s >>> Doing rc2 cbc for 3s on 64 size blocks: 260808 rc2 cbc's in 3.00s >>> Doing rc2 cbc for 3s on 256 size blocks: 65924 rc2 cbc's in 3.00s >>> Doing rc2 cbc for 3s on 1024 size blocks: 16527 rc2 cbc's in 3.00s >>> Doing rc2 cbc for 3s on 8192 size blocks: 2068 rc2 cbc's in 3.00s >>> Doing blowfish cbc for 3s on 16 size blocks: 3453174 blowfish cbc's >>> in 3.00s >>> Doing blowfish cbc for 3s on 64 size blocks: 919800 blowfish cbc's >>> in 3.00s >>> Doing blowfish cbc for 3s on 256 size blocks: 233331 blowfish cbc's >>> in 3.00s >>> Doing blowfish cbc for 3s on 1024 size blocks: 58648 blowfish cbc's >>> in 3.00s >>> Doing blowfish cbc for 3s on 8192 size blocks: 7342 blowfish cbc's >>> in 3.00s >>> Doing cast cbc for 3s on 16 size blocks: 1489211 cast cbc's in 3.00s >>> Doing cast cbc for 3s on 64 size blocks: 390739 cast cbc's in 3.00s >>> Doing cast cbc for 3s on 256 size blocks: 99321 cast cbc's in 3.00s >>> Doing cast cbc for 3s on 1024 size blocks: 24935 cast cbc's in 3.00s >>> Doing cast cbc for 3s on 8192 size blocks: 3117 cast cbc's in 3.00s >>> Doing 512 bit private rsa's for 10s: 3144 512 bit private RSA's in >>> 10.00s >>> Doing 512 bit public rsa's for 10s: 40906 512 bit public RSA's in >>> 10.00s >>> Doing 1024 bit private rsa's for 10s: 693 1024 bit private RSA's in >>> 10.00s >>> Doing 1024 bit public rsa's for 10s: 14711 1024 bit public RSA's in >>> 10.00s >>> Doing 2048 bit private rsa's for 10s: 123 2048 bit private RSA's in >>> 10.04s >>> Doing 2048 bit public rsa's for 10s: 4521 2048 bit public RSA's in >>> 10.00s >>> Doing 4096 bit private rsa's for 10s: 19 4096 bit private RSA's in >>> 9.99s >>> Doing 4096 bit public rsa's for 10s: 1276 4096 bit public RSA's in >>> 10.00s >>> Doing 512 bit sign dsa's for 10s: 4276 512 bit DSA signs in 10.00s >>> Doing 512 bit verify dsa's for 10s: 3565 512 bit DSA verify in > 10.00s >>> Doing 1024 bit sign dsa's for 10s: 1524 1024 bit DSA signs in 9.94s >>> Doing 1024 bit verify dsa's for 10s: 1210 1024 bit DSA verify in > 9.61s >>> Doing 2048 bit sign dsa's for 10s: 466 2048 bit DSA signs in 10.00s >>> Doing 2048 bit verify dsa's for 10s: 385 2048 bit DSA verify in > 10.01s >>> OpenSSL 0.9.8d 28 Sep 2006 >>> built on: Thu Oct 5 14:59:49 PDT 2006 >>> options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes >>> (partial) idea(int) blowfish(idx) >>> compiler: cc -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -pthread - >>> D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIOS -O3 - >>> fomit-frame-pointer -Wall -O2 -fno-strict-aliasing -pipe -O -pipe - >>> mtune=i686 -march=pentiumpro -Wl,-rpath,/usr/local/lib - >>> DOPENSSL_BN_ASM_PART_WORDS -DSHA1_ASM -DMD5_ASM -DRMD160_ASM > -DAES_ASM >>> available timing options: USE_TOD HZ=128 [sysconf value] >>> timing function used: getrusage >>> The 'numbers' are in 1000s of bytes per second processed. >>> type 16 bytes 64 bytes 256 bytes 1024 bytes >>> 8192 bytes >>> md2 487.74k 1035.01k 1439.70k >>> 1595.96k 1648.09k >>> mdc2 0.00 0.00 0.00 >>> 0.00 0.00 >>> md4 4084.48k 13874.63k 37969.97k >>> 67352.86k 87350.70k >>> md5 3949.20k 13765.67k 38809.49k >>> 70958.11k 93711.88k >>> hmac(md5) 5146.75k 16873.33k 44491.70k >>> 75283.53k 94651.38k >>> sha1 3291.04k 9982.17k 22723.55k >>> 33376.76k 38713.82k >>> rmd160 3027.84k 8519.94k 17725.07k >>> 24281.34k 27244.85k >>> rc4 35021.81k 39051.53k 40008.97k >>> 40450.15k 40579.31k >>> des cbc 10155.41k 10633.02k 10779.02k >>> 10815.92k 10827.19k >>> des ede3 3644.70k 3708.02k 3726.63k >>> 3731.14k 3732.61k >>> idea cbc 7772.10k 8274.88k 8411.48k >>> 8445.84k 8456.41k >>> rc2 cbc 5330.19k 5561.94k 5623.46k >>> 5638.97k 5643.18k >>> rc5-32/12 cbc 0.00 0.00 0.00 >>> 0.00 0.00 >>> blowfish cbc 18412.46k 19615.50k 19903.76k >>> 20011.27k 20042.36k >>> cast cbc 7939.92k 8332.80k 8472.38k >>> 8507.91k 8509.17k >>> aes-128 cbc 10336.74k 13632.21k 14921.12k >>> 15282.22k 15378.05k >>> aes-192 cbc 9243.95k 11759.17k 12704.51k >>> 12965.83k 13035.18k >>> aes-256 cbc 8315.79k 10144.85k 10844.33k >>> 11034.36k 11085.73k >>> camellia-128 cbc 0.00 0.00 0.00 >>> 0.00 0.00 >>> camellia-192 cbc 0.00 0.00 0.00 >>> 0.00 0.00 >>> camellia-256 cbc 0.00 0.00 0.00 >>> 0.00 0.00 >>> sha256 2111.53k 4857.49k 8477.58k >>> 10431.66k 11184.11k >>> sha512 487.68k 1950.02k 2877.14k >>> 3976.70k 4476.19k >>> sign verify sign/s verify/s >>> rsa 512 bits 0.003179s 0.000244s 314.5 4090.4 >>> rsa 1024 bits 0.014434s 0.000680s 69.3 1470.9 >>> rsa 2048 bits 0.081587s 0.002212s 12.3 452.0 >>> rsa 4096 bits 0.525871s 0.007841s 1.9 127.5 >>> sign verify sign/s verify/s >>> dsa 512 bits 0.002338s 0.002806s 427.8 356.4 >>> dsa 1024 bits 0.006522s 0.007944s 153.3 125.9 >>> dsa 2048 bits 0.021468s 0.026010s 46.6 38.4 >>> >>> _______________________________________________ >>> 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" >> >> -- >> David King >> Computer Programmer >> Ketralnis Systems >> >> >> _______________________________________________ >> 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" > _______________________________________________ > 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" -- David King Computer Programmer Ketralnis Systems From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 11 10:09:56 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7939816A49E for ; Wed, 11 Oct 2006 10:09:56 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F40D43D94 for ; Wed, 11 Oct 2006 10:09:40 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr5so.prod.shaw.ca (pd2mr5so-qfe3.prod.shaw.ca [10.0.141.8]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6Y007TDUW4FL70@l-daemon> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 04:09:40 -0600 (MDT) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd2mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6Y00MJFUW4JJR0@pd2mr5so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 04:09:40 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J6Y00KXBUW4GY90@l-daemon> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 04:09:40 -0600 (MDT) Date: Wed, 11 Oct 2006 03:09:37 -0700 From: soralx@cydem.org In-reply-to: <200610050852.58943.jhb@freebsd.org> To: freebsd-hardware@freebsd.org Message-id: <200610110309.37555.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200610050852.58943.jhb@freebsd.org> User-Agent: KMail/1.9.1 Subject: Re: ipw(4) and iwi(4): Intel's Pro Wireless [firmware licensing problems] 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, 11 Oct 2006 10:09:56 -0000 > > [...] > > For some recent information about Intel being an Open Source Fraud, > > see http://marc.theaimsgroup.com/?l=openbsd-misc&m=115960734026283&w=2. > > Probably because all you have to do is install a port and it works. :) Not for me, it doesn't :P Well, the interface does get created, but the 'no carrier' state persists no matter what I do. I blame our big uncle Intel's old habit of playing posing games for this sad state of affairs ;) No good documentation -- no well-working hardware. Simple as that. > you might want to ask Theo why he complains about Intel not giving him a > license for one binary blob (Intel wireless firmware) but complains about > Atheros providing a binary blob that he can distribute. Seems a bit of a firmware is (should be) an integral part of the device, and runs only on one CPU. Generally, noone cares about any documentation for it -- as long as it makes the device work. Thus, binary form is perfectly acceptable OTOH, the code which is intended to be executed by the OS must not be distributed in only the binary form, because for some systems it will be completely useless (even though the device itself is perfectly functional) > John Baldwin [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 11 12:45:53 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B8B716A518 for ; Wed, 11 Oct 2006 12:45:53 +0000 (UTC) (envelope-from sj@ukrintell.net) Received: from pop.ukrintell.com.ua (pop.ukrintell.com.ua [81.21.0.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 677EB43D5C for ; Wed, 11 Oct 2006 12:45:34 +0000 (GMT) (envelope-from sj@ukrintell.net) Received: from sj.ukrintell.com.ua ([192.168.40.88]) by pop.ukrintell.com.ua (8.12.6/8.12.6) with ESMTP id k9BCreuf031410 for ; Wed, 11 Oct 2006 15:53:41 +0300 (EEST) (envelope-from sj@ukrintell.net) From: Alexey Bobok Organization: IntellCom To: freebsd-hardware@freebsd.org Date: Wed, 11 Oct 2006 15:45:20 +0000 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610111545.20981.sj@ukrintell.net> Subject: Intell Wireless 3945 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: Wed, 11 Oct 2006 12:45:53 -0000 Hello. I have bought a laptop Dell Latitude d820 with Intel Wireless Pro 3945 card. I've tried to install /usr/ports/net/ipw-firmware and then kldload -v if_ipw ipwcontrol -i ipw0 -f /boot/firmware/ipw.fw and get the error: ipwcontrol: Can't load /boot/firmware/ipw.fw to driver: Device not configured the problem is that I even don't see any messages about this device in dmesg. is there any solution? ) thanks From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 11 13:19:48 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C109216A403 for ; Wed, 11 Oct 2006 13:19:48 +0000 (UTC) (envelope-from weldon@excelsus.com) Received: from mx0.excelsus.net (volt.excelsus.com [206.246.199.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAA8743D55 for ; Wed, 11 Oct 2006 13:19:43 +0000 (GMT) (envelope-from weldon@excelsus.com) Received: (qmail 33751 invoked by uid 89); 11 Oct 2006 13:19:43 -0000 Received: from unknown (HELO volt.excelsus.com) (206.246.199.18) by volt.excelsus.com with SMTP; 11 Oct 2006 13:19:43 -0000 Date: Wed, 11 Oct 2006 09:19:43 -0400 (EDT) From: Weldon S Godfrey 3 To: freebsd-hardware@freebsd.org Message-ID: <20061011091218.G73418@volt.excelsus.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: New FreeBSD server box 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, 11 Oct 2006 13:19:48 -0000 Hello, I am about to build a new FreeBSD box. In the past I built my own or gone towards Dell (but I haven't been happy with their support this year and I have heard problems with FreeBSD and their newer computers). I am looking at a bare-bones Supermicro, specifically the SuperServer 6015X-TV(or TB) and was wondering if anyone had any experience with them. Normally, I just look at the hardware notes on FreeBSD site, but I am not 100% sure that the SATA Intel ESB2 RAID controller is supported under the Intel driver. I have tried searching and I could not find a definite answer. Please forgive me, I am sure I am being thick and not seeing it. Thanks in advance! Weldon From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 11 22:30:27 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80C5916A47C for ; Wed, 11 Oct 2006 22:30:27 +0000 (UTC) (envelope-from listacct@tulsaconnect.com) Received: from cgpro2.tulsaconnect.com (pop3.tulsaconnect.com [65.38.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26A5C43D86 for ; Wed, 11 Oct 2006 22:30:26 +0000 (GMT) (envelope-from listacct@tulsaconnect.com) Received: from [65.38.0.2] (HELO [192.168.30.3]) by cgpro2.tulsaconnect.com (CommuniGate Pro SMTP 4.3.8) with ESMTPS id 217809410 for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 17:30:26 -0500 Message-ID: <452D708D.6090303@tulsaconnect.com> Date: Wed, 11 Oct 2006 17:30:37 -0500 From: TCIS List Acct User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Best supported Fibre Channel HBA for FreeBSD 6.x? 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, 11 Oct 2006 22:30:27 -0000 Hi all, I'm getting ready to deploy a group of new FreeBSD 6.x machines for use as a mail server cluster and need to know what the "best supported" / stable 2GB Fibre Channel HBA is (for use in connecting to a Infortrend SATA RAID array). QLogic and LSI Logic are brands I've used in the past, but any suggestions are welcome. PCI-X or PCI-E are my choices as far as interface goes.. TIA. --Mike From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 12 03:08:45 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7257916A407 for ; Thu, 12 Oct 2006 03:08:45 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DC3143D45 for ; Thu, 12 Oct 2006 03:08:45 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr6so.prod.shaw.ca (pd2mr6so-qfe3.prod.shaw.ca [10.0.141.9]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7000BST62LBZD0@l-daemon> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 21:08:45 -0600 (MDT) Received: from pn2ml9so.prod.shaw.ca ([10.0.121.7]) by pd2mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J70000FP62L4G80@pd2mr6so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 21:08:45 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7000I0862LD960@l-daemon> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 21:08:45 -0600 (MDT) Date: Wed, 11 Oct 2006 20:08:43 -0700 From: soralx@cydem.org In-reply-to: <36E6E927-AA04-43ED-928E-D06ABCE414CA@ketralnis.com> To: freebsd-hardware@freebsd.org Message-id: <200610112008.43586.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <78ED28FACE63744386D68D8A9D1CF5D4209C5C@MAIL.corp.lumeta.com> <36E6E927-AA04-43ED-928E-D06ABCE414CA@ketralnis.com> User-Agent: KMail/1.9.1 Subject: Re: Quiet computer 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, 12 Oct 2006 03:08:45 -0000 > > Hmm.. that's odd, the Woodcrest still stomps those numbers- I > > wonder if > > it's just a matter of difference in CPU speed, or intel has started > > adding some sort of hw crypto? Also, I'm running a stock 6.1-RELEASE > > amd64 kernel. > > It might also be that OpenSSL isn't actually using the /dev/crypto > device; I see from some postings that in order to get OpenSSL to use > it, you have to give a command line switch like -engine. I played > around with it a little, and while I don't know much about how > OpenSSL defines engines, I did get this: > > ~% openssl speed -engine /dev/crypto > invalid engine "/dev/crypto" like it says, engine name '/dev/crypto' is not valid try `openssl speed -engine padlock` also, try to test the speed of the true random number generator (I don't know how to access it; maybe just dd /dev/urandom?) [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 12 03:42:23 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AD316A412 for ; Thu, 12 Oct 2006 03:42:23 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A39443D53 for ; Thu, 12 Oct 2006 03:42:19 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr7so.prod.shaw.ca (pd2mr7so-qfe3.prod.shaw.ca [10.0.141.10]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J700026G7MKSD90@l-daemon> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 21:42:20 -0600 (MDT) Received: from pn2ml9so.prod.shaw.ca ([10.0.121.7]) by pd2mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7000GIP7MJYVO0@pd2mr7so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 21:42:20 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7000I0W7MJD680@l-daemon> for freebsd-hardware@freebsd.org; Wed, 11 Oct 2006 21:42:19 -0600 (MDT) Date: Wed, 11 Oct 2006 20:42:14 -0700 From: soralx@cydem.org In-reply-to: <3ABF536B-F199-47B9-8B10-EF5A0644BC62@ketralnis.com> To: freebsd-hardware@freebsd.org Message-id: <200610112042.14698.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <3692C07B-CCCC-4756-9B33-6DA724481FF2@ketralnis.com> <200610052145.54292.soralx@cydem.org> <3ABF536B-F199-47B9-8B10-EF5A0644BC62@ketralnis.com> User-Agent: KMail/1.9.1 Subject: Re: Quiet computer 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, 12 Oct 2006 03:42:23 -0000 > >>> You might wants to consider using a low-power 'brick'-type AC->DC > >>> PSU (~90W?) and a DC-DC voltage converter that plugs directly into > >>> a mainboard's power connector. This will be quite noiseless. > >> Do you have any recommendations? Ideally it would mount on the case > >> () like > >> the current power supply does but I'm open to other options > > something like this (random example): > > http://www.logicsupply.com/product_info.php/products_id/596 > > The only types of power supplies with which I'm familiar are the ones > that typically ship with most cases, so I'm a little confused by > this, excuse my obvious ignorance :) > > What does the DC-DC converter do, if the AC-DC converter supplies DC > power? it converts the single supplied DC voltage (that is sometimes allowed to range as much as 6Vdc to 20Vdc) to multiple DC voltages required by the mainboard and other devices (+12V, +5V, +3.3V, -5V, etc) > What would be an example of this AC-DC converter? just any AC->DC power supply that's output is within a DC->DC converter's input range; e.g., a laptop power adapter > Could it power two > 3.5" hard drives in addition to the motherboard? depends on the DC->DC converter you use 3.5" hard drive sucks a lot of juice at 12V line, so the converter must be able to supply that; any converter destined to be used in Intel Pentium4 system _probably_ will work (typical model name for such a beast would look something like '120W', versus '60W' that can supply little power at 12V) note, however, that if you use a good, well filtered AC->DC power supply that produces 12V, you can feed this voltage directly to the hard drives (I think you can; I'm not sure if the groud loop will affect anything) Also, I believe that the more powerful version of DC->DC is more efficient at the same load level than less powerful (i.e., 120W vs 60W) > How does it differ from a regular power supply? much smaller in size, _theoretically_ longer life before {failure because of old age} (assume same temperature), less wires, supposedly more efficient and lower power. The latter, in particular, means that the whole AC->DC->DC system will generate little heat, and thus won't require active cooling (you can even keep the AC->DC PSU outside of case so it doesn't heat up its interior & take up space). Of course, a regular ATX PSU won't dissipate a lot of heat either, yet just disconnecting the fan is hardly a solution. One advantage of such a power source is that realizing uninterruptible power is rather easy: just connect a battery :) This way, you can easily replace a failing AC->DC PSU without sending the server down, too. [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 12 04:36:51 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09C5A16A403 for ; Thu, 12 Oct 2006 04:36:51 +0000 (UTC) (envelope-from dking@ketralnis.com) Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9160843D53 for ; Thu, 12 Oct 2006 04:36:50 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [10.0.1.239] (ayla.wifi.int.ketralnis.com [10.0.1.239]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9C4anus041977 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 11 Oct 2006 21:36:50 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <200610112008.43586.soralx@cydem.org> References: <78ED28FACE63744386D68D8A9D1CF5D4209C5C@MAIL.corp.lumeta.com> <36E6E927-AA04-43ED-928E-D06ABCE414CA@ketralnis.com> <200610112008.43586.soralx@cydem.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David King Date: Wed, 11 Oct 2006 21:36:45 -0700 To: freebsd-hardware@freebsd.org X-Mailer: Apple Mail (2.752.3) Subject: Re: Quiet computer 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, 12 Oct 2006 04:36:51 -0000 >> ~% openssl speed -engine /dev/crypto >> invalid engine "/dev/crypto" > like it says, engine name '/dev/crypto' is not valid > try `openssl speed -engine padlock` ~% openssl speed -engine padlock invalid engine "padlock" 35459:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:162:filename(/usr/local/lib/engines/ libpadlock.so): Cannot open "/usr/local/lib/engines/libpadlock.so" 35459:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: 35459:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:450: 35459:error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:415:id=padlock 35459:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:162:filename(libpadlock.so): Shared object "libpadlock.so" not found, required by "openssl" 35459:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: 35459:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:450: To get the most accurate results, try to run this program when this computer is idle. Doing md2 for 3s on 16 size blocks: ^C Looking above, it says: Cannot open "/usr/local/lib/engines/ libpadlock.so" So in /usr/local/lib/engines I have: lib4758cca.so libaep.so libatalla.so libchil.so libcswift.so libgmp.so libnuron.so libsureware.so libubsec.so I don't have a /usr/lib/engines. However, trying to use any of these produces: ~% openssl speed -engine aep can't use that engine 36919:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:162:filename(libaep.so): Shared object "libaep.so" not found, required by "openssl" 36919:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: 36919:error:8006706F:lib(128):AEP_INIT:not loaded:e_aep.c:452: 36919:error:260B806D:engine routines:ENGINE_TABLE_REGISTER:init failed:eng_table.c:161: To get the most accurate results, try to run this program when this computer is idle. Doing md2 for 3s on 16 size blocks: ^C I get that same output (more or less) for all of the engines listed above. It appears to fail because of "ENGINE_TABLE_REGISTER:init failed:eng_table.c:161". In /usr/src/crypto/openssl/crypto/engine, I have a file called hw_cryptodev.c, and eng_padlock.c. Ah hah! So /usr/bin/openssl has the padlock engine and /usr/local/bin/openssl doesn't! Unfortunately, most everything in ports refers to /usr/local/bin/ openssl, and even for things that do refer to openssl in /usr/lib, I can't see a way to make padlock a default engine, especially when the library isn't called from the command line but from a function. That means that things like OpenSSH and Apache aren't using the Padlock engine. Here it is with -engine padlock: OpenSSL 0.9.7e-p1 25 Oct 2004 built on: Fri Sep 22 23:34:15 PDT 2006 options:bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) aes (partial) blowfish(idx) compiler: cc available timing options: USE_TOD HZ=128 [sysconf value] timing function used: getrusage The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes md2 478.07k 1013.94k 1414.92k 1563.02k 1614.53k mdc2 1087.24k 1247.60k 1289.48k 1300.31k 1303.37k md4 4085.98k 13914.48k 37820.24k 66161.31k 84992.27k md5 3425.82k 11281.29k 28884.29k 47276.54k 58183.54k hmac(md5) 3465.96k 11174.26k 28685.23k 47078.91k 58150.01k sha1 2896.99k 8055.26k 16638.74k 22677.07k 25370.87k rmd160 2372.33k 6305.41k 12401.84k 16350.08k 18040.21k rc4 35023.95k 38905.13k 39856.06k 40250.13k 39823.03k des cbc 10468.62k 10862.20k 10964.68k 11032.56k 11067.82k des ede3 3820.33k 3872.99k 3890.84k 3894.02k 3896.33k idea cbc 0.00 0.00 0.00 0.00 0.00 rc2 cbc 5264.44k 5471.87k 5524.67k 5541.18k 5545.20k rc5-32/12 cbc 32327.09k 35910.48k 37377.89k 37766.02k 37881.53k blowfish cbc 17753.08k 18908.57k 19186.99k 19288.36k 19315.04k cast cbc 18161.59k 19238.40k 19653.59k 19760.83k 19789.47k aes-128 cbc 8494.74k 8654.30k 8735.18k 8756.07k 8756.60k aes-192 cbc 7427.82k 7550.84k 7612.49k 7627.53k 7632.40k aes-256 cbc 6601.20k 6696.66k 6744.59k 6756.72k 6754.67k sign verify sign/s verify/s rsa 512 bits 0.0030s 0.0003s 338.3 2979.0 rsa 1024 bits 0.0134s 0.0008s 74.6 1193.6 rsa 2048 bits 0.0776s 0.0026s 12.9 387.8 rsa 4096 bits 0.5079s 0.0090s 2.0 111.1 sign verify sign/s verify/s dsa 512 bits 0.0023s 0.0027s 443.7 367.5 dsa 1024 bits 0.0064s 0.0078s 155.6 128.3 dsa 2048 bits 0.0211s 0.0256s 47.4 39.1 The system wasn't totally idle during that test, but I think it was close enough. > also, try to test the speed of the true random number generator > (I don't know how to access it; maybe just dd /dev/urandom?) Here's one: ~% time dd if=/dev/urandom bs=1024 count=10240 of=/dev/null 10240+0 records in 10240+0 records out 10485760 bytes transferred in 15.957354 secs (657111 bytes/sec) dd if=/dev/urandom bs=1024 count=10240 of=/dev/null 0.00s user 15.85s system 99% cpu 15.970 total ~% time dd if=/dev/random bs=1024 count=10240 of=/dev/null 10240+0 records in 10240+0 records out 10485760 bytes transferred in 15.967514 secs (656693 bytes/sec) dd if=/dev/random bs=1024 count=10240 of=/dev/null 0.01s user 15.85s system 99% cpu 15.976 total From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 12 13:40:48 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3819C16A403 for ; Thu, 12 Oct 2006 13:40:48 +0000 (UTC) (envelope-from bjordan@lumeta.com) Received: from MAIL.corp.lumeta.com (h65-246-245-22.lumeta.com [65.246.245.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAE1C43D67 for ; Thu, 12 Oct 2006 13:40:45 +0000 (GMT) (envelope-from bjordan@lumeta.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 12 Oct 2006 09:40:43 -0400 Message-ID: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Quiet computer Thread-Index: AcbtuCQSsC2SdMH5SSW3E5pvkj6zUQASxSJw From: "Bucky Jordan" To: "David King" , Cc: Subject: RE: Quiet computer 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, 12 Oct 2006 13:40:48 -0000 > > also, try to test the speed of the true random number generator > > (I don't know how to access it; maybe just dd /dev/urandom?) >=20 > Here's one: >=20 > ~% time dd if=3D/dev/urandom bs=3D1024 count=3D10240 of=3D/dev/null > 10240+0 records in > 10240+0 records out > 10485760 bytes transferred in 15.957354 secs (657111 bytes/sec) > dd if=3D/dev/urandom bs=3D1024 count=3D10240 of=3D/dev/null 0.00s = user > 15.85s system 99% cpu 15.970 total >=20 > ~% time dd if=3D/dev/random bs=3D1024 count=3D10240 of=3D/dev/null > 10240+0 records in > 10240+0 records out > 10485760 bytes transferred in 15.967514 secs (656693 bytes/sec) > dd if=3D/dev/random bs=3D1024 count=3D10240 of=3D/dev/null 0.01s user = 15.85s > system 99% cpu 15.976 total >=20 I'm also going to be doing a lot of SSL on a Poweredge 2950. So the above is purely a memory/cpu test correct? (not like doing IO tests where you want the size of the test data to be at least twice physical ram). Here's results for the Woodcrest- I assume this is only on a single core. Yes, I realize that the woodcrest is faster than above mentioned cpu, but a 100x speed difference? That doesn't seem realistic to me (although if those are valid results, I'd be pretty happy with that)... bash-2.05b$ time dd if=3D/dev/urandom bs=3D1024 count=3D10240 = of=3D/dev/null 10240+0 records in 10240+0 records out 10485760 bytes transferred in 0.154649 secs (67803598 bytes/sec) bash-2.05b$ time dd if=3D/dev/urandom bs=3D8k count=3D10240 = of=3D/dev/null 10240+0 records in 10240+0 records out 83886080 bytes transferred in 1.165706 secs (71961615 bytes/sec) Thanks, Bucky From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 12 14:53:44 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 305CC16A492 for ; Thu, 12 Oct 2006 14:53:44 +0000 (UTC) (envelope-from ketralnis@ketralnis.com) Received: from ketralnis.com (melchoir.ketralnis.com [68.183.67.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0D9F43DA6 for ; Thu, 12 Oct 2006 14:52:16 +0000 (GMT) (envelope-from ketralnis@ketralnis.com) Received: from ketralnis.com (localhost [127.0.0.1]) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9CEqGbD006596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Oct 2006 07:52:16 -0700 (PDT) (envelope-from ketralnis@ketralnis.com) Received: from localhost (ketralnis@localhost) by ketralnis.com (8.13.6/8.13.6/Submit) with ESMTP id k9CEqDNc006560; Thu, 12 Oct 2006 07:52:15 -0700 (PDT) (envelope-from ketralnis@ketralnis.com) Date: Thu, 12 Oct 2006 07:52:13 -0700 (PDT) From: David King To: Bucky Jordan In-Reply-To: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> Message-ID: <20061012075101.Y5008@ketralnis.com> References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: David King , freebsd-hardware@freebsd.org Subject: RE: Quiet computer 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, 12 Oct 2006 14:53:44 -0000 >> ~% time dd if=/dev/urandom bs=1024 count=10240 of=/dev/null >> 10240+0 records in >> 10240+0 records out >> 10485760 bytes transferred in 15.957354 secs (657111 bytes/sec) >> dd if=/dev/urandom bs=1024 count=10240 of=/dev/null 0.00s user >> 15.85s system 99% cpu 15.970 total > I'm also going to be doing a lot of SSL on a Poweredge 2950. So the > above is purely a memory/cpu test correct? (not like doing IO tests > where you want the size of the test data to be at least twice physical > ram). Here's results for the Woodcrest- I assume this is only on a > single core. Yes, I realize that the woodcrest is faster than above > mentioned cpu, but a 100x speed difference? That doesn't seem realistic > to me (although if those are valid results, I'd be pretty happy with > that)... Well, the Via Padlock has a hardware random-number generator, so the idea was to test that. It doesn't claim to be fast, just to be truly random > > bash-2.05b$ time dd if=/dev/urandom bs=1024 count=10240 of=/dev/null > 10240+0 records in > 10240+0 records out > 10485760 bytes transferred in 0.154649 secs (67803598 bytes/sec) > > bash-2.05b$ time dd if=/dev/urandom bs=8k count=10240 of=/dev/null > 10240+0 records in > 10240+0 records out > 83886080 bytes transferred in 1.165706 secs (71961615 bytes/sec) From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 12 21:24:30 2006 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.org Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B22E16A403 for ; Thu, 12 Oct 2006 21:24:30 +0000 (UTC) (envelope-from jrhett@svcolo.com) Received: from kininvie.sv.svcolo.com (kininvie.sv.svcolo.com [64.13.135.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA4A843D49 for ; Thu, 12 Oct 2006 21:24:29 +0000 (GMT) (envelope-from jrhett@svcolo.com) Received: from [127.0.0.1] (covad-jrhett.meer.net [209.157.140.144]) (authenticated bits=0) by kininvie.sv.svcolo.com (8.13.8/8.13.4) with ESMTP id k9CLORZ4042843; Thu, 12 Oct 2006 14:24:27 -0700 (PDT) (envelope-from jrhett@svcolo.com) Message-ID: <452EB286.8000503@svcolo.com> Date: Thu, 12 Oct 2006 14:24:22 -0700 From: Jo Rhett Organization: Silicon Valley Colocation User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Bruce Evans References: <20060721000018.GA99237@svcolo.com> <20060721001607.GA64376@megan.kiwi-computer.com> <20060721004731.GC8868@svcolo.com> <20060724154856.I58894@delplex.bde.org> In-Reply-To: <20060724154856.I58894@delplex.bde.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Bayes-Prob: 0.0001 (Score 0) X-Spam-Score: 1.60 (*) [Tag at 3.50] J_CHICKENPOX_22,PIPE_OBFUSCATION X-CanItPRO-Stream: default X-Canit-Stats-ID: 3888 - 0501bc79b0d2 X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.135.12 Cc: "Rick C. Petty" , freebsd-hardware@FreeBSD.org Subject: Bounty offered to fix sio device lock problem 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, 12 Oct 2006 21:24:30 -0000 Bruce -- who owns getting this fixed? Or who should own it? Or who will take on getting it fixed if we offer a bounty on it? Replication scenario: Modem on sio0 (or sio1 or any normal i386 serial port) /etc/ttys has port enabled with "dialup" qpage (from ports, unchanged) uses modem for dialout ** or just write a script that periodically dials out using tip Within a day and often within a few hours, the serial port will go awol. You can't talk to the modem any more. Modem is just fine. Rebooting the system solves the problem. Rebooting the modem does not solve it. 100% replicable, and sooner versus later if you call out more often. Bruce Evans wrote: > On Thu, 20 Jul 2006, Jo Rhett wrote: > >> Thanks for the super-quick reply! Responses are inline... >> >> On Thu, Jul 20, 2006 at 07:16:07PM -0500, Rick C. Petty wrote: >>>> root@scapa 47# fstat /dev/ttyd0 >>>> USER CMD PID FD MOUNT INUM MODE SZ|DV >>>> R/W NAME >>> >>> What about "fstat /dev/cuad0" ? Anyway, I've found that fstat is >>> useless, >>> try using sysutils/lsof instead. > > This is related to a longstanding (design) bug in vfs > (first-open/last-close > semantics). vfs counts devices as being open when it calls the device > open routine, despite devices not actually being open until the device > open routine returns successfully, which may happen much later (or not > at all in the case of failure, but this doesn't cause any additional > problems). This causes the device close routine to not be called in > some cases where it should be. For bidirectional serial devices, not > calling the device close routine results in "callin" devices that are > sleeping in open being treated the same as "callin" devices that have > successfully completed the open. The former shouldn't give EBUSY for > opens of the corresponding "callout" device, but the latter should and > do. > > FreeBSD-1 has a hack to vfs to work around the bug, but the hack was > lost in FreeBSD-2. I still use the hack locally. Startting with about > FreeBSD-4, there is a D_TRACKCLOSE device flag that can be used to fix > the problem less hackishly (but still not in the right way, since it > requires individual drivers to do generic things). I haven't got around > to using it to fix sio even locally. D_TRACKCLOSE is mostly unused and > mostly used bogusly when it is used. > > The bug rarely causes problems since it is only activated by doing > something like the following: > > thread1: "open" /dev/ttyd0. Actually, block in open waiting for > carrier. > thread2: open /dev/ttyd0 using O_NONBLOCK to prevent blocking. > thread2: perhaps actually use /dev/ttyd0 > thread2: "close" /dev/ttyd0. Actually, don't complete the close due to > the bogus vfs close. > thread1: remain blocked in open through all the above. > thread3: try to open /dev/cuaa^Hd0. Get EBUSY because the non-open by > thread1 is seen as an open. > > Starting with about FreeBSD-5, there may be additional problems from races. > First-open/last-close semantics basically require opens to be synchronous. > Sleeping in open for serial device drivers gives large race windows in > which to open may race open/close of the same device in other threads. > Prempting the kernel gives small race windows. In practice, Giant locking > limits problems. For serial drivers, open/close should still be Giant- > locked since the whole tty subsystem is still Giant-locked. (Note that > all vfs locks are dropped before calling device open/close. The bogus vfs > count provides some psuedo-locking.) > > Rearrangement of serial drivers in -current may have enlarged the bug, > but I can't see any enlargement except that from more serial drivers > now supporting bidirectional devices. > >> Sorry, yes. Same results. And if lsof shows things that fstat doesn't, >> then this is a bug in FreeBSD. >> >> But anyway, >> root@scapa 63# lsof /dev/cuad0 >> root@scapa 64# lsof /dev/ttyd0 >> >> Nada. > > I think fstat and lsof can't see threads sleeping in open since the open > hasn't really completed -- the open has completed enough to confuse vfs > but not for vfs to report its confusion to userland. It should be possible > to see threads sleeping in open using "ps -lax | grep ttydcd" ("ttydcd" is > the string for -current; the string for sio used to be "siodcd". Grep for > "tty" and "dcd" too). This won't distinguish between threads sleeping > normally in open (ttyopen) and ones that are in a bogus state due to a > missing close. > >> Also note that this system is pretty bone stock. Standard install, plus >> mysql and apache. Nothing else would be using the port. It's something >> that left it locked, and really only "login" could be the culprit. > > Quite likely, but login doesn't use O_NONBLOCK so I don't know how it > could trigger the bug. Maybe nopise on DCD cound do it. The easiest > way to trigger the bug is "stty -f /dev/ttyd0" while there is a login > blocked in open on ttyd0. > >>>> No locks? No processes using it. Okay, this is uncool. >>>> And yet "ktrace tip com1" and "kdump -f ktrace.out" clearly show: >>>> >>>> 50461 tip CALL open(0x8059030,0x6,0) >>>> 50461 tip NAMI "/dev/cuad0" >>>> 50461 tip RET open -1 errno 16 Device busy >>> >>> This isn't very useful. A ktrace on the process that's locking the file >>> would be. :-P >> >> See above. I can't find it. :-( > > You might need to start ktracing very early to locate the original > problematic open/open/close sequence. > >>>> NOTE: at this time I am suspecting that CD is being misread (it's not >>>> present - I have a break out box on the line) and that this problem is >>>> somehow tied to that. This problem appears at random after login has >>>> exerted itself on the system. I've disabled the getty on ttyd0 and >>>> login >>>> has timed out, but it continues to show "device busy". >>> >>> How did you disable the getty? Was this prior to or after a >>> restart? It >>> sounds like /etc/ttys is maybe running a process on it. You need to >>> "killall -HUP init" after changing /etc/ttys. But you probably already >>> know that. >> >> Yes, I change "on" to "off" in /etc/ttys and "kill -1 1" :-) > > Killing all processes sleeping in serial device open unwedges the port for > the bug that I know about (provided the close doesn't hang). This and > making the open succeed by raising DCD in hardware are the only ways that > I know of to unwedge the port once the open gets stuck. > > Bruce -- Jo Rhett senior geek Silicon Valley Colocation From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 05:56:04 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECCF516A407 for ; Fri, 13 Oct 2006 05:56:04 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1FC943D70 for ; Fri, 13 Oct 2006 05:55:59 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd4mr6so.prod.shaw.ca (pd4mr6so-qfe3.prod.shaw.ca [10.0.141.69]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J72007ML8HBK070@l-daemon> for freebsd-hardware@freebsd.org; Thu, 12 Oct 2006 23:55:59 -0600 (MDT) Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147]) by pd4mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7200M5P8HBUUK0@pd4mr6so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Thu, 12 Oct 2006 23:55:59 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7200LDO8HBYWT0@l-daemon> for freebsd-hardware@freebsd.org; Thu, 12 Oct 2006 23:55:59 -0600 (MDT) Date: Thu, 12 Oct 2006 22:55:57 -0700 From: soralx@cydem.org To: freebsd-hardware@freebsd.org Message-id: <200610122255.57752.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline User-Agent: KMail/1.9.1 Subject: iwi: 'no carrier' 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, 13 Oct 2006 05:56:05 -0000 had anyone ever encounterd a problem with Intel 2200BG wireless card, when the iwi driver seems to work normaly, but in reality it never associates with an access point (i.e., 'no carrier' no matter what)? the driver and firmware were all installed from ports, on 6.2-BETA2 [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 06:22:33 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1197D16A407 for ; Fri, 13 Oct 2006 06:22:33 +0000 (UTC) (envelope-from sob@academ.com) Received: from bdr.academ.com (BDR.ACADEM.COM [198.137.249.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F7EA43D6A for ; Fri, 13 Oct 2006 06:22:32 +0000 (GMT) (envelope-from sob@academ.com) Received: from [198.137.249.114] (PASSER-BY.ACADEM.COM [198.137.249.114]) (authenticated bits=0) by bdr.academ.com (8.13.4/8.13.4) with ESMTP id k9D6MTsI079569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Oct 2006 01:22:30 -0500 (CDT) (envelope-from sob@academ.com) Message-ID: <452F30A4.8040103@academ.com> Date: Fri, 13 Oct 2006 01:22:28 -0500 From: Stan Barber User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bdr.academ.com Subject: FreeBSD 6.1 and Prism-based wireless cards 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, 13 Oct 2006 06:22:33 -0000 I just upgraded my Compaq E500 from 5.4 to 6.1. Everything works fine except the Prism-based wireless card. It worked fine under 5.4. I verified the card didn't blow up under XP and Linux. I have even tried a different card that was working fine in the Linux laptop. Right now, it looks like it must be something about FreeBSD 6.1 (I have all the updates to p10 installed as well). Here is the error when either Prism-based card gets plugged in: wi0: timeout in wi_cmd 0x0000: event status 0x8000 :init failed device_attach: wi0 attach returned 6 By the way, the driver does correctly identify each card from the cis data. From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 06:31:55 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D09D416A407 for ; Fri, 13 Oct 2006 06:31:55 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2-3.pacific.net.au [61.8.2.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50F9343D45 for ; Fri, 13 Oct 2006 06:31:54 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout2.pacific.net.au (Postfix) with ESMTP id B94C41111D7; Fri, 13 Oct 2006 16:31:52 +1000 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (Postfix) with ESMTP id BAD368C37; Fri, 13 Oct 2006 16:31:51 +1000 (EST) Date: Fri, 13 Oct 2006 16:31:45 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Jo Rhett In-Reply-To: <452EB286.8000503@svcolo.com> Message-ID: <20061013152714.Y49451@delplex.bde.org> References: <20060721000018.GA99237@svcolo.com> <20060721001607.GA64376@megan.kiwi-computer.com> <20060721004731.GC8868@svcolo.com> <20060724154856.I58894@delplex.bde.org> <452EB286.8000503@svcolo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Rick C. Petty" , freebsd-hardware@freebsd.org Subject: Re: Bounty offered to fix sio device lock problem 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, 13 Oct 2006 06:31:55 -0000 On Thu, 12 Oct 2006, Jo Rhett wrote: > Bruce -- who owns getting this fixed? Or who should own it? Or who will > take on getting it fixed if we offer a bounty on it? > > Replication scenario: > Modem on sio0 (or sio1 or any normal i386 serial port) > /etc/ttys has port enabled with "dialup" > qpage (from ports, unchanged) uses modem for dialout > ** or just write a script that periodically dials out using tip > > Within a day and often within a few hours, the serial port will go awol. You > can't talk to the modem any more. Modem is just fine. > Rebooting the system solves the problem. Rebooting the modem does not solve > it. > > 100% replicable, and sooner versus later if you call out more often. [context lost to top posting] I mentioned an old vfs refcounting bug. New ones turned up a week or two ago. They cause leaked pty masters and worse. The pty leak is caused by last-close sometimes not being called. For pty masters, the leak is permanent since reopening of the master is not permitted for security reasons so there is no way to reach the device close, but for sio devices it should be possible to fix up the problem by reopening and closing the device relevant device after ensuring that it is not already open: - for cua*, simply stty -f'ing it or just using it should be enough. I guess this is not your problem, since the fix is almost automatic. - for tty*, it may be necessary to disable getty on the port and kill the current getty, since the old vfs refcounting bug normally prevents reaching last-close if any process is sleeping in open, so if you don't disable getty on the port then you have to race with the new getty to complete the open/last-close before the new getty sleeps in open. Many nearby vfs bugs will be fixed in 6.2-RELEASE, but no fix is in sight for the main refcounting ones. Bruce From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 07:00:16 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B65316A403 for ; Fri, 13 Oct 2006 07:00:16 +0000 (UTC) (envelope-from sob@academ.com) Received: from bdr.academ.com (BDR.ACADEM.COM [198.137.249.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B95F43D6D for ; Fri, 13 Oct 2006 07:00:03 +0000 (GMT) (envelope-from sob@academ.com) Received: from [198.137.249.114] (PASSER-BY.ACADEM.COM [198.137.249.114]) (authenticated bits=0) by bdr.academ.com (8.13.4/8.13.4) with ESMTP id k9D6xcub080065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 13 Oct 2006 01:59:39 -0500 (CDT) (envelope-from sob@academ.com) Message-ID: <452F3959.5080206@academ.com> Date: Fri, 13 Oct 2006 01:59:37 -0500 From: Stan Barber User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <452F30A4.8040103@academ.com> In-Reply-To: <452F30A4.8040103@academ.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on bdr.academ.com Subject: Re: FreeBSD 6.1 and Prism-based wireless cards 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, 13 Oct 2006 07:00:16 -0000 This appears to be the acpi interacting with the card in some bad way. I have disabled apci in and now it will do the right thing. I have not yet had a chance to debug this further, but will report back when I do. I also tested this with a Aeronet (now Cisco) card and it would get into some kind of infinite wait state (it was not hung as I could remove the card, the driver would abort, and thing came back to normal). From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 08:07:54 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8F5B16A4AB for ; Fri, 13 Oct 2006 08:07:54 +0000 (UTC) (envelope-from vicknesan@bigfoot.com) Received: from mail1.ilik.net (mail1.ilik.net [192.71.20.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3711443D46 for ; Fri, 13 Oct 2006 08:07:54 +0000 (GMT) (envelope-from vicknesan@bigfoot.com) Received: from localhost (localhost.ilik.net [127.0.0.1]) by mail1.ilik.net (Postfix) with ESMTP id 8D54E2C3560; Fri, 13 Oct 2006 09:59:09 +0200 (CEST) X-Virus-Scanned: by amavisd-new at ilik.net Received: from mail1.ilik.net ([127.0.0.1]) by localhost (mail1.ilik.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bH4AwFjS6FRG; Fri, 13 Oct 2006 09:58:58 +0200 (CEST) Received: from ark (138.206.216.81.static.nvik.siw.siwnet.net [81.216.206.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail1.ilik.net (Postfix) with ESMTP id D9B782C34E5; Fri, 13 Oct 2006 09:58:57 +0200 (CEST) Date: Fri, 13 Oct 2006 10:07:40 +0200 (CEST) From: Vicknesan AYADURAI X-X-Sender: vick@apu To: Stan Barber In-Reply-To: <452F30A4.8040103@academ.com> Message-ID: <20061013095806.R5916@apu> References: <452F30A4.8040103@academ.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD-hardware Subject: Re: FreeBSD 6.1 and Prism-based wireless cards 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, 13 Oct 2006 08:07:54 -0000 On Fri, 13 Oct 2006, Stan Barber wrote: > I just upgraded my Compaq E500 from 5.4 to 6.1. Everything works fine except > the Prism-based wireless card. It worked fine under 5.4. I verified the card > didn't blow up under XP and Linux. I have even tried a different card that > was working fine in the Linux laptop. > > Right now, it looks like it must be something about FreeBSD 6.1 (I have all > the updates to p10 installed as well). > > Here is the error when either Prism-based card gets plugged in: > > wi0: timeout in wi_cmd 0x0000: event status 0x8000 > :init failed > device_attach: wi0 attach returned 6 > > By the way, the driver does correctly identify each card from the cis data. Hi Stan, This reminds me of the problem I had with my 3Com Etherlink PCMCIA ethernet card (battle-tested, working solidly since FBSD-2.2.8R) which ceased to work when I went from 5.4R-->6.1R on my Thinkpad. The general problem seems to be the 'magical' IRQ allocation upon card insertion/detection, and subsequently some kind of collision with ACPI. The card was assigned IRQ 9 with 5.4R, but IRQ 10 with 6.1R, which was also used for ACPI-stuff. The trick, which fixed my problem at least, was to force a different IRQ assigment (from 10) for 6.1R. I posted what worked for me at: http://lists.freebsd.org/pipermail/freebsd-hardware/2006-September/003781.html Hope this helps, vick From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 09:12:29 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3ABDC16A40F for ; Fri, 13 Oct 2006 09:12:29 +0000 (UTC) (envelope-from jrhett@svcolo.com) Received: from kininvie.sv.svcolo.com (kininvie.sv.svcolo.com [64.13.135.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9014043D49 for ; Fri, 13 Oct 2006 09:12:28 +0000 (GMT) (envelope-from jrhett@svcolo.com) Received: from [172.16.12.22] (covad-jrhett.meer.net [209.157.140.144]) (authenticated bits=0) by kininvie.sv.svcolo.com (8.13.8/8.13.4) with ESMTP id k9D9CRA5053453; Fri, 13 Oct 2006 02:12:27 -0700 (PDT) (envelope-from jrhett@svcolo.com) Message-ID: <452F587F.4080108@svcolo.com> Date: Fri, 13 Oct 2006 02:12:31 -0700 From: Jo Rhett Organization: Silicon Valley Colocation User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Bruce Evans References: <20060721000018.GA99237@svcolo.com> <20060721001607.GA64376@megan.kiwi-computer.com> <20060721004731.GC8868@svcolo.com> <20060724154856.I58894@delplex.bde.org> <452EB286.8000503@svcolo.com> <20061013152714.Y49451@delplex.bde.org> In-Reply-To: <20061013152714.Y49451@delplex.bde.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Bayes-Prob: 0.0001 (Score 0) X-Spam-Score: 0.00 () [Tag at 3.50] X-CanItPRO-Stream: default X-Canit-Stats-ID: 4087 - ce14857022cf X-Scanned-By: CanIt (www . roaringpenguin . com) on 64.13.135.12 Cc: "Rick C. Petty" , freebsd-hardware@freebsd.org Subject: Re: Bounty offered to fix sio device lock problem 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, 13 Oct 2006 09:12:29 -0000 Bruce Evans wrote: > On Thu, 12 Oct 2006, Jo Rhett wrote: > >> Bruce -- who owns getting this fixed? Or who should own it? Or who >> will take on getting it fixed if we offer a bounty on it? >> >> Replication scenario: >> Modem on sio0 (or sio1 or any normal i386 serial port) >> /etc/ttys has port enabled with "dialup" >> qpage (from ports, unchanged) uses modem for dialout >> ** or just write a script that periodically dials out using tip >> >> Within a day and often within a few hours, the serial port will go >> awol. You can't talk to the modem any more. Modem is just fine. >> Rebooting the system solves the problem. Rebooting the modem does >> not solve it. >> >> 100% replicable, and sooner versus later if you call out more often. > > [context lost to top posting] > > I mentioned an old vfs refcounting bug. New ones turned up a week or > two ago. They cause leaked pty masters and worse. The pty leak is > caused by last-close sometimes not being called. For pty masters, the > leak is permanent since reopening of the master is not permitted for > security reasons so there is no way to reach the device close, but for > sio devices it should be possible to fix up the problem by reopening > and closing the device relevant device after ensuring that it is not > already open: > - for cua*, simply stty -f'ing it or just using it should be enough. > I guess this is not your problem, since the fix is almost automatic. > - for tty*, it may be necessary to disable getty on the port and kill > the current getty, since the old vfs refcounting bug normally prevents > reaching last-close if any process is sleeping in open, so if you don't > disable getty on the port then you have to race with the new getty to > complete the open/last-close before the new getty sleeps in open. > > Many nearby vfs bugs will be fixed in 6.2-RELEASE, but no fix is in > sight for the main refcounting ones. So these problems are all in 6.0-REL, not 6.1 or CURRENT. (I assume they persist, but new ones may be newer than this) On one system, I've disabled getty for over a month and ... well, waiting for schedule downtime for the host. Still can't use the device. I'd be happy to give you any debug or any information you need to diagnose. And we'd be happy to give you money to adjust your priorities too :-) It's a fairly serious annoyance for us, causing our emergency out of band pagers to missing crucial messages. From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 13 11:01:22 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8C8716A407 for ; Fri, 13 Oct 2006 11:01:22 +0000 (UTC) (envelope-from phil@primeradesigns.com) Received: from amazing.commonservers.com (amazing.commonservers.com [70.85.42.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90B7B43D6A for ; Fri, 13 Oct 2006 11:01:20 +0000 (GMT) (envelope-from phil@primeradesigns.com) Received: from 194-247-235-60.dynamic.dsl.as9105.com ([194.247.235.60] helo=sled10.27sjcr) by amazing.commonservers.com with esmtpa (Exim 4.52) id 1GYKmt-0003lh-Ip for freebsd-hardware@freebsd.org; Fri, 13 Oct 2006 11:01:12 +0000 From: Philip M Brown To: freebsd-hardware@freebsd.org Content-Type: text/plain Organization: Primera Designs Limited Date: Fri, 13 Oct 2006 12:04:00 +0100 Message-Id: <1160737440.15042.9.camel@sled10.27sjcr> Mime-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - amazing.commonservers.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - primeradesigns.com X-Source: X-Source-Args: X-Source-Dir: Subject: moxa multiport serial cards X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: phil@primeradesigns.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 11:01:23 -0000 hi, I am a long time user of freebsd but have no -NO knowledge of moxa multiport cards. I see there is great support for moxa on freebsd so I put my question forth. i have acquired Moxa Model cp-114 and am trying to figure out its usages. The CP-114 Series of multiport serial boards is designed for RS-232 and RS-422/485 industrial communication. The CP-114 Series has 2 ports for RS-232 or RS-422/485, selectable by jumper, and 2 ports for RS-422/485, with each RS-422/485 port able to control up to 32 devices in a multidrop environment. so does this mean I can wire up one of the rs-232 ports to a patch panel and then split that into 32 rj=45 connectors which would in turn be connected to various serial devices (pc/router/switchers). or do i need another box that translates these signals. I assumed the card did all the processing. thanks for any input From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 04:21:30 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1F7E16A407 for ; Sat, 14 Oct 2006 04:21:30 +0000 (UTC) (envelope-from aharrison@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4702743D49 for ; Sat, 14 Oct 2006 04:21:30 +0000 (GMT) (envelope-from aharrison@gmail.com) Received: by nf-out-0910.google.com with SMTP id p77so1211992nfc for ; Fri, 13 Oct 2006 21:21:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=OH32aLOM3tPg0aeROi35x1WD+mq6zVEvxVgFa25i5hCrwkhea1yB+HRtnwV9rB83TxHdaZ4+RZgPOqm7avwHn79jdek110BwLSyeiKuigBynjX0R4Zrbob+IinzSlUSw2XBPGHk4jraWKq6WOCFZsGJoL2/AFErMWpgGRM7002I= Received: by 10.78.90.10 with SMTP id n10mr4659413hub; Fri, 13 Oct 2006 21:21:28 -0700 (PDT) Received: by 10.78.176.14 with HTTP; Fri, 13 Oct 2006 21:21:28 -0700 (PDT) Message-ID: Date: Sat, 14 Oct 2006 00:21:28 -0400 From: "Andy Harrison" To: "soralx@cydem.org" In-Reply-To: <200610122255.57752.soralx@cydem.org> MIME-Version: 1.0 References: <200610122255.57752.soralx@cydem.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: iwi: 'no carrier' 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, 14 Oct 2006 04:21:31 -0000 On 10/13/06, soralx@cydem.org wrote: > > > had anyone ever encounterd a problem with Intel 2200BG wireless card, > when the iwi driver seems to work normaly, but in reality it never > associates with an access point (i.e., 'no carrier' no matter what)? > the driver and firmware were all installed from ports, on 6.2-BETA2 Here's how I got mine working. I have my wap configured to use tkip. You probably won't need all of these options if you're using a simpler configuration. First, make sure your internal nic is not enabled. Here are the lines from my rc.conf hostname="example" bfe_enable="NO" iwi_enable="YES" ifconfig_iwi0="ssid MySSIDstring authmode wpa inet 192.168.66.66 netmask 255.255.255.0" wlan_acl_enable="YES" wlan_wep_enable="YES" wlan_ccmp="YES" wlan_tkip="YES" 192.168.66.66 is a bogus ip, it just doesn't seem to want to work right if you try to turn on dhcp at this point. Here are the lines from my loader.conf if_iwi_load="YES" wlan_acl_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wlan_xauth_load="YES" When the machine boots, it will show my iwi0 interface status as "associated" by the time I log in a look at it with ifconfig. Then I just run: # wpa_supplicant -B -q -i iwi0 -c /etc/wpa_supplicant.conf My wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 network={ ssid="MySSIDstring" scan_ssid=1 key_mgmt=WPA-PSK pairwise=TKIP psk="my passphrase string" } Then I'm ready for a real ip: # dhclient iwi0 If you have trouble associating with your wap, run the wpa_supplicant in debug mode: # wpa_supplicant -d -i iwi0 -c /etc/wpa_supplicant.conf The wpa_cli command might also be useful for further troubleshooting. -- Andy Harrison From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 05:56:07 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41B7F16A403 for ; Sat, 14 Oct 2006 05:56:07 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd2mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7ED143D81 for ; Sat, 14 Oct 2006 05:56:01 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-qfe3.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J74008XR31VJ740@l-daemon> for freebsd-hardware@freebsd.org; Fri, 13 Oct 2006 23:53:56 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd3mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J74004MZ31VG191@pd3mr2so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Fri, 13 Oct 2006 23:53:55 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7400ITF31VYDD0@l-daemon> for freebsd-hardware@freebsd.org; Fri, 13 Oct 2006 23:53:55 -0600 (MDT) Date: Fri, 13 Oct 2006 22:53:53 -0700 From: soralx@cydem.org In-reply-to: To: Undisclosed.Recipients: ; Cc: freebsd-hardware@freebsd.org Message-id: <200610132253.53765.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 7bit Content-disposition: inline References: <200610122255.57752.soralx@cydem.org> User-Agent: KMail/1.9.1 Subject: Re: iwi: 'no carrier' 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, 14 Oct 2006 05:56:07 -0000 > > had anyone ever encounterd a problem with Intel 2200BG wireless card, > > when the iwi driver seems to work normaly, but in reality it never > > associates with an access point (i.e., 'no carrier' no matter what)? > > the driver and firmware were all installed from ports, on 6.2-BETA2 > > Here's how I got mine working. I have my wap configured to use tkip. You > [...] > When the machine boots, it will show my iwi0 interface status as > "associated" by the time I log in a look at it with ifconfig. Then I just > run: > [...] Well, this was a quite useful how-to on configuring a working card, but it doesn't apply in my case :P My adapter sees no access points at all (`ifconfig iwi0 list scan` returns nothing), so it can't associate no matter what the settings are, and ifconfig always shows it's status as 'no carrier'. I tried configuring an IP# & netmask and then starting dhclient, but observed no diefference. BTW, why did you need to disable the built-in NIC? [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 10:08:03 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BA7316A40F for ; Sat, 14 Oct 2006 10:08:03 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A5A443D53 for ; Sat, 14 Oct 2006 10:08:02 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-qfe3.prod.shaw.ca [10.0.141.178]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J74005XTETFMZ20@l-daemon> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:08:03 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd3mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J74006DUETF3YM1@pd3mr2so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:08:03 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7400IPDETEY1D0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:08:03 -0600 (MDT) Date: Sat, 14 Oct 2006 03:07:59 -0700 From: soralx@cydem.org In-reply-to: <20061012075101.Y5008@ketralnis.com> To: freebsd-hardware@freebsd.org Message-id: <200610140308.00451.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> <20061012075101.Y5008@ketralnis.com> User-Agent: KMail/1.9.1 Subject: Re: Quiet computer 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, 14 Oct 2006 10:08:03 -0000 > > mentioned cpu, but a 100x speed difference? That doesn't seem realistic > > to me (although if those are valid results, I'd be pretty happy with > > that)... > > Well, the Via Padlock has a hardware random-number generator, so the > idea was to test that. It doesn't claim to be fast, just to be truly random Precisely. However, speed of the crypto engine should be directly proportional to a peak speed of the RNG, so I thought that it's slow speed might confirm that the engine is being used, and is simply slow. Also, we didn't really test where are those random bits coming from :P Is the TRNG used by default, or some tinkering's in order to make it work? BTW... `ubench`? :) [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 10:46:24 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF3A616A407 for ; Sat, 14 Oct 2006 10:46:24 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd3mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F4EF43D49 for ; Sat, 14 Oct 2006 10:46:24 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr3so.prod.shaw.ca (pd2mr3so-qfe3.prod.shaw.ca [10.0.141.108]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J74003FWGLCQ680@l-daemon> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:46:25 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd2mr3so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7400J2SGLCDPU0@pd2mr3so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:46:24 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7400IUCGLCYVD0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 14 Oct 2006 04:46:24 -0600 (MDT) Date: Sat, 14 Oct 2006 03:46:22 -0700 From: soralx@cydem.org In-reply-to: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> To: freebsd-hardware@freebsd.org Message-id: <200610140346.22554.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> User-Agent: KMail/1.9.1 Subject: Re: Quiet computer 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, 14 Oct 2006 10:46:24 -0000 > single core. Yes, I realize that the woodcrest is faster than above > mentioned cpu, but a 100x speed difference? That doesn't seem realistic > to me (although if those are valid results, I'd be pretty happy with > that)... Even if VIA's true RNG is actually being used, then I see how this could be realistic. The pseudo-RNG in you machine constitutes a mathematical algorithm with an initial random seed (yarrow, if I'm not mistaken). You have a fast CPU, and it crunches numbers rapidly; thus, you get that impressive speed. For a true RNG, every bit provided is original, random (not a result of some transformation). So, if the hardware portion has limited bandwith (randomness 'regenerates' slowly -- bits don't change fast enough), or there's delay along the path, then RNG device speed will be limited -- and therefore encryption speed as well (if I'm not mistaken). But if the randomness source is slow, it's not a big problem. For example, a chip can be used that's meant to transform, or 'dilute', the truly random stream somewhat to increase speed. Hmm... OTOH, noone yet complained about quantum processes being too slow, so I suppose /dev/urandom is not what we want to test. When we see some performance data for the VIA CPU, then we'll determine whether it's TRNG spitting out the random bits or is it the yarrow that's increasing entropy :) BTW, David, test (if you have enough time for curiosity) /dev/urandom (or wherever the generator is) with different values of 'bs', from very small to large (1 byte, 512, 4k, 16k, 64k) to see how much it depends on block size. > bash-2.05b$ time dd if=/dev/urandom bs=1024 count=10240 of=/dev/null > 10240+0 records in > 10240+0 records out > 10485760 bytes transferred in 0.154649 secs (67803598 bytes/sec) >Bucky [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 14:04:09 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D38E216A47B for ; Sat, 14 Oct 2006 14:04:09 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE6CF43DAA for ; Sat, 14 Oct 2006 14:03:49 +0000 (GMT) (envelope-from lgusenet@be-well.ilk.org) Received: (qmail 14815 invoked from network); 14 Oct 2006 14:03:49 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Oct 2006 14:03:49 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id D0E722842E; Sat, 14 Oct 2006 10:03:48 -0400 (EDT) To: soralx@cydem.org References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> <20061012075101.Y5008@ketralnis.com> <200610140308.00451.soralx@cydem.org> From: Lowell Gilbert Date: Sat, 14 Oct 2006 10:03:48 -0400 In-Reply-To: <200610140308.00451.soralx@cydem.org> (soralx@cydem.org's message of "Sat, 14 Oct 2006 03:07:59 -0700") Message-ID: <44wt738057.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-hardware@freebsd.org Subject: Re: Quiet computer 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, 14 Oct 2006 14:04:09 -0000 soralx@cydem.org writes: >> > mentioned cpu, but a 100x speed difference? That doesn't seem realistic >> > to me (although if those are valid results, I'd be pretty happy with >> > that)... >> >> Well, the Via Padlock has a hardware random-number generator, so the >> idea was to test that. It doesn't claim to be fast, just to be truly random > > Precisely. However, speed of the crypto engine should be directly > proportional to a peak speed of the RNG, That statement makes no sense to me. Why would the RNG be relevant after the session keys are established? > so I thought that it's > slow speed might confirm that the engine is being used, and is > simply slow. I don't really care how fast the crypto engine is on my Via system. I just care that it offloads the ALU. I haven't gotten around to proving whether (and by how much) it does so. > Also, we didn't really test where are those random bits coming from :P > Is the TRNG used by default, or some tinkering's in order to make it work? > > BTW... `ubench`? :) Not impressive. From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 19:56:11 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8A1316A407 for ; Sat, 14 Oct 2006 19:56:11 +0000 (UTC) (envelope-from aharrison@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F00343D58 for ; Sat, 14 Oct 2006 19:56:11 +0000 (GMT) (envelope-from aharrison@gmail.com) Received: by nf-out-0910.google.com with SMTP id p77so1375518nfc for ; Sat, 14 Oct 2006 12:56:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=c06CMmt4KOi4Neuo1uH9Dqg4XqIUc+XmTvvClLLyENEjihsEZt89RMvc6h19Cdb9FYV6tyAmPGKCy2rGGBLZq7vmJWuLAYmkPzs/4CNbG7X7whxy4guxLD9k1ZpvRe8kiCFLbY/LH3VylyryYW2qMJWWZxXyOTBsK6m9O8UDZVA= Received: by 10.78.201.2 with SMTP id y2mr5523670huf; Sat, 14 Oct 2006 12:56:09 -0700 (PDT) Received: by 10.78.176.14 with HTTP; Sat, 14 Oct 2006 12:56:09 -0700 (PDT) Message-ID: Date: Sat, 14 Oct 2006 15:56:09 -0400 From: "Andy Harrison" To: "soralx@cydem.org" In-Reply-To: <200610132253.53765.soralx@cydem.org> MIME-Version: 1.0 References: <200610122255.57752.soralx@cydem.org> <200610132253.53765.soralx@cydem.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: iwi: 'no carrier' 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, 14 Oct 2006 19:56:12 -0000 On 10/14/06, soralx@cydem.org wrote: > > Well, this was a quite useful how-to on configuring a working card, but > it doesn't apply in my case :P My adapter sees no access points at all > (`ifconfig iwi0 list scan` returns nothing), so it can't associate no > matter what the settings are, and ifconfig always shows it's status > as 'no carrier'. I tried configuring an IP# & netmask and then starting > dhclient, but observed no diefference. I would run the wpa_supplicant in debug mode anyway, at least you'll be able to see what it's doing while it's scanning. It might show some useful info. BTW, why did you need to disable the built-in NIC? > Not sure why, I just know I can't get the iwi interface to work at all if the bfe is up. I couldn't even get it to associate with the wap at all. The only reason I thought to disable the bfe is because a co-worker is running fedora on his laptop (same make/model as mine) and he couldn't get his iwi to work until he disabled the bfe. -- Andy Harrison