From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 15 02:10:46 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 1E3F916A403 for ; Sun, 15 Oct 2006 02:10:46 +0000 (UTC) (envelope-from donnex@donnex.net) Received: from donnex.net (donnex.net [82.96.44.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 3E98543D45 for ; Sun, 15 Oct 2006 02:10:45 +0000 (GMT) (envelope-from donnex@donnex.net) Received: (qmail 14228 invoked from network); 15 Oct 2006 02:08:09 -0000 Received: from unknown (HELO ?192.168.1.40?) (192.168.1.40) by mail.donnex.net with SMTP; 15 Oct 2006 02:08:09 -0000 Message-ID: <453198AF.90604@donnex.net> Date: Sun, 15 Oct 2006 04:10:55 +0200 From: Daniel Johansson 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: SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly 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, 15 Oct 2006 02:10:46 -0000 Hello, I recently bought a Promise SATA300 TX4 SATA controller and two Seagate 320 GB drives. I haven't used the disks very much until today when I moved a bunch of backups to one of the disks and noticed these messages in my dmesg. ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=97160544 The controller is recognized as atapci0: port 0xc400-0xc47f,0xc000-0xc0ff mem 0xfab00000-0xfab00fff,0xfaa00000-0xfaa1ffff irq 17 at device 12.0 on pci0 Is this something I should worry about? Anything wrong with my disks or is it the SATA controller? Bug in freebsd driver maybe? Is it safe to continue to use the drives, everything seems to be working fine. I'm running FreeBSD 6.1 RELEASE amd64. -- Daniel Johansson - From owner-freebsd-hardware@FreeBSD.ORG Sun Oct 15 07:42:02 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 9CC0F16A403 for ; Sun, 15 Oct 2006 07:42:02 +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 46C8543D46 for ; Sun, 15 Oct 2006 07:42:01 +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 <0J7600HZR2Q22770@l-daemon> for freebsd-hardware@freebsd.org; Sun, 15 Oct 2006 01:42:02 -0600 (MDT) Received: from pn2ml7so.prod.shaw.ca ([10.0.121.151]) by pd2mr6so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7600N9X2Q258Y1@pd2mr6so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sun, 15 Oct 2006 01:42:02 -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 <0J76003UY2Q1AJR0@l-daemon> for freebsd-hardware@freebsd.org; Sun, 15 Oct 2006 01:42:02 -0600 (MDT) Date: Sun, 15 Oct 2006 00:41:59 -0700 From: soralx@cydem.org In-reply-to: <44wt738057.fsf@be-well.ilk.org> To: Undisclosed.Recipients: ; Cc: freebsd-hardware@freebsd.org Message-id: <200610150041.59870.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> <200610140308.00451.soralx@cydem.org> <44wt738057.fsf@be-well.ilk.org> 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: Sun, 15 Oct 2006 07:42:02 -0000 > > 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? okay, so I was wrong sure way to quickly find out if your idea is wrong: say it on a maillist :) (I thought for some reason that new random string needs to be generated for every block that's being encrypted) > I don't really care how fast the crypto engine is on my Via system. neither do I care how fast it is on someone else's system :p, but I'm just curious whether the speed VIA claims, 25Gbps(!) peak is achievable > I just care that it offloads the ALU. I haven't gotten around to > proving whether (and by how much) it does so. did you get to the point that you're sure it's being used? > > BTW... `ubench`? :) > > Not impressive. you're using the same board as OP? [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 07:06:00 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 E3E3216A40F for ; Mon, 16 Oct 2006 07:05:59 +0000 (UTC) (envelope-from richw@richw.org) Received: from smtp3.stanford.edu (smtp3.Stanford.EDU [171.67.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id D838D43D5E for ; Mon, 16 Oct 2006 07:05:57 +0000 (GMT) (envelope-from richw@richw.org) Received: from smtp3.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id F35634BFD5 for ; Mon, 16 Oct 2006 00:05:56 -0700 (PDT) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp3.stanford.edu (Postfix) with ESMTP id C63E74BDC2 for ; Mon, 16 Oct 2006 00:05:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by whodunit.richw.org (Postfix) with ESMTP id 834123C36D; Mon, 16 Oct 2006 00:05:56 -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 Mfxs4ktW8w3q; Mon, 16 Oct 2006 00:05:53 -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 4801A3C36B; Mon, 16 Oct 2006 00:05:53 -0700 (PDT) Date: Mon, 16 Oct 2006 00:05:52 -0700 From: Rich Wales User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <453198AF.90604@donnex.net> In-Reply-To: <453198AF.90604@donnex.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20061016070553.4801A3C36B@whodunit.richw.org> Subject: Re: SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 07:06:00 -0000 Daniel Johansson wrote: > Hello, I recently bought a Promise SATA300 TX4 SATA controller and two > Seagate 320 GB drives. I haven't used the disks very much until today > when I moved a bunch of backups to one of the disks and noticed these > messages in my dmesg. . . . > > Is this something I should worry about? Definitely yes. IMO, you need to do something about it ASAP. > Anything wrong with my disks or is it the SATA controller? See some recent discussion threads on this list with "SATA" in the subject line. The problem seems to be caused by a combination of iffy PCI implementations in some motherboards and aggressive, close-to-the- edge behaviour in some Promise chip designs. Your disks are probably OK -- though you should certainly set up "smartd" to monitor them in any case. Your first suspect should probably be your motherboard. If you have any BIOS setup options relating to the PCI bus -- controlling things like latency time, wait states, or burst mode -- you might want to try less aggressive settings and see if this helps. In an experimental system of mine (using an old "Slot A" Athlon motherboard), I was able to make problems similar to yours go away by disabling PCI master burst mode; this slowed down disk I/O significantly, but at least the system became rock-solid stable after I made that change. Another thing to do would be to ensure that your Promise card is not sharing an interrupt line with any other device in your system. Look at the output of "dmesg", checking particularly for device probing and the IRQ assignments. If your Promise card doesn't have its very own, dedicated IRQ, you might need to put it in a different PCI slot, and/or go into your BIOS setup and free up some IRQ's by disabling some things that you aren't using (such as serial or parallel ports, or on-board sound card functionality if this is a server rather than a desktop). What kind of CPU and motherboard are you using? What sorts of setup options related to PCI performance can you find in your BIOS? What other devices are you using in your system? > Bug in freebsd driver maybe? It doesn't seem at all clear whether this problem can be solved in the driver or not. People have been talking about it sporadically, for a long time, in Linux and NetBSD discussion lists and groups, as well as the FreeBSD lists, but so far no one seems to have come up with any ideas for improving their drivers to help the issue any. > Is it safe to continue to use the drives, everything seems to be > working fine. I would say no, not until/unless you can make the problem go away 100%. In some cases, I've seen timeout warnings like the ones you reported progress to actual I/O failures if the system is heavily enough loaded. Even if you don't get any failures, you'll have significantly degraded system performance when timeouts occur. Rich Wales Palo Alto, CA, USA richw@richw.org http://www.richw.org From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 12:05: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 8750E16A4D4 for ; Mon, 16 Oct 2006 12:05:04 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E90B43D90 for ; Mon, 16 Oct 2006 12:01:38 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (jylqnu@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k9GC1BHJ003197; Mon, 16 Oct 2006 14:01:16 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k9GC17ol003191; Mon, 16 Oct 2006 14:01:07 +0200 (CEST) (envelope-from olli) Date: Mon, 16 Oct 2006 14:01:07 +0200 (CEST) Message-Id: <200610161201.k9GC17ol003191@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG, soralx@cydem.org In-Reply-To: <200610150041.59870.soralx@cydem.org> X-Newsgroups: list.freebsd-hardware User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 16 Oct 2006 14:01:20 +0200 (CEST) Cc: Subject: Re: Quiet computer X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hardware@FreeBSD.ORG, soralx@cydem.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 12:05:04 -0000 soralx@cydem.org wrote: > > neither do I care how fast it is on someone else's system :p, but I'm > just curious whether the speed VIA claims, 25Gbps(!) peak is achievable Note that that number is just the "raw" rate at which the circuit can produce bits. You still have some processing overhead in the kernel and in the userland application that uses the random device. There's no "zero-copy random device" yet. ;-) I also think that 25 Gbit/s is overly optimistic. I guess it can only achieved for a short period ("burst"), hence they call it peak. It's certainly not designed to keep that data rate for a longer sustained period. > > I just care that it offloads the ALU. I haven't gotten around to > > proving whether (and by how much) it does so. > > did you get to the point that you're sure it's being used? Now that's easy. Just type "sysctl kern.random". If you get a bunch of lines talking about "yarrow" and "harvest", then the kernel's software PRNG is used. If you get an error message "unknown oid 'kern.random'", then a hardware generator is being used. Best regards Oliver ("VIA C3 Nehemiah+RNG+AES ") -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 14:09: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 52AD916A494 for ; Mon, 16 Oct 2006 14:09:22 +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 DC28043D4C for ; Mon, 16 Oct 2006 14:09:21 +0000 (GMT) (envelope-from lgusenet@be-well.ilk.org) Received: (qmail 13917 invoked from network); 16 Oct 2006 14:09:21 -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 ; 16 Oct 2006 14:09:21 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 1328F2842E; Mon, 16 Oct 2006 10:09:19 -0400 (EDT) To: freebsd-hardware@freebsd.org References: <44wt738057.fsf@be-well.ilk.org> <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> <200610140308.00451.soralx@cydem.org> <200610150041.59870.soralx@cydem.org> From: Lowell Gilbert Date: Mon, 16 Oct 2006 10:09:19 -0400 In-Reply-To: <200610150041.59870.soralx@cydem.org> (soralx@cydem.org's message of "Sun, 15 Oct 2006 00:41:59 -0700") Message-ID: <44u0241hf4.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 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, 16 Oct 2006 14:09:22 -0000 soralx@cydem.org writes: >> I don't really care how fast the crypto engine is on my Via system. > > neither do I care how fast it is on someone else's system :p, but I'm Fair enough. Its speed on your own system may matter less to you than you think, as well. ;-) > just curious whether the speed VIA claims, 25Gbps(!) peak is achievable Peak rate is a useless number. If it were sustainable, it wouldn't be quoted as a "peak" rate; and if it's not sustainable, it doesn't affect the perceived performance. >> I just care that it offloads the ALU. I haven't gotten around to >> proving whether (and by how much) it does so. > > did you get to the point that you're sure it's being used? Yes. it is. >> > BTW... `ubench`? :) >> >> Not impressive. > > you're using the same board as OP? No, not at all; I didn't mean to imply I was. I have the slowest (and lowest powered) Via chips I could get. The ubench numbers are slightly lower than the Pentium II system it replaced, at a similar clock rate. Note that I didn't mean the numbers were bad, either... From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 16:59: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 71BB416A412 for ; Mon, 16 Oct 2006 16:59:53 +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 5E63F43D5F for ; Mon, 16 Oct 2006 16:59:52 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [192.168.1.87] (pix.xythos.com [64.154.218.194]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9GGxpFM009323 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 16 Oct 2006 09:59:51 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <200610140308.00451.soralx@cydem.org> References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> <20061012075101.Y5008@ketralnis.com> <200610140308.00451.soralx@cydem.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David King Date: Mon, 16 Oct 2006 09:59:38 -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, 16 Oct 2006 16:59:53 -0000 > 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? Well, sysctl kern.random says: ~% sysctl kern.random sysctl: unknown oid 'kern.random' and according to a previous post this means that it's in use > BTW... `ubench`? :) here are two runs, neither in single-user mode but the system should have been idle: FreeBSD 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #10: Tue Oct 10 20:06:09 PDT 2006 root@hostname:/usr/obj/usr/src/sys/KERNEL i386 Ubench CPU: 38798 Ubench MEM: 45654 -------------------- Ubench AVG: 42226 Ubench CPU: 38869 Ubench MEM: 46149 -------------------- Ubench AVG: 42509 From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 17:14: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 AAED616A403 for ; Mon, 16 Oct 2006 17:14:09 +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 5F12A43D45 for ; Mon, 16 Oct 2006 17:14:09 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [192.168.1.87] (pix.xythos.com [64.154.218.194]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9GHE8ns018044 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 16 Oct 2006 10:14:08 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <200610140346.22554.soralx@cydem.org> References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> <200610140346.22554.soralx@cydem.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <301DDDB6-A47E-448F-A145-7B2087599598@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Mon, 16 Oct 2006 10:14:02 -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, 16 Oct 2006 17:14:09 -0000 > 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) ~% cat test_rand_block.sh #!/usr/local/bin/bash for BS in 1 512 $(expr 1024 \* 4) $(expr 1024 \* 16) $(expr 1024 \* 64); do COUNT=$(expr $(expr 1024 \* 64) / $BS) BYTES=$(expr $COUNT \* $BS) echo bs=$BS count=$COUNT bytes=$BYTES dd if=/dev/random of=/dev/null bs=$BS count=$COUNT echo ------; done ~% sh test_rand_block.sh bs=1 count=65536 bytes=65536 65536+0 records in 65536+0 records out 65536 bytes transferred in 25.599306 secs (2560 bytes/sec) ------ bs=512 count=128 bytes=65536 128+0 records in 128+0 records out 65536 bytes transferred in 0.099902 secs (656003 bytes/sec) ------ bs=4096 count=16 bytes=65536 16+0 records in 16+0 records out 65536 bytes transferred in 0.100660 secs (651062 bytes/sec) ------ bs=16384 count=4 bytes=65536 4+0 records in 4+0 records out 65536 bytes transferred in 0.099324 secs (659820 bytes/sec) ------ bs=65536 count=1 bytes=65536 1+0 records in 1+0 records out 65536 bytes transferred in 0.099681 secs (657458 bytes/sec) ------ From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 17:15: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 00A2416A412; Mon, 16 Oct 2006 17:15:33 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAF3243D53; Mon, 16 Oct 2006 17:15:28 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA08731; Mon, 16 Oct 2006 20:15:26 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4533BE2E.4080005@icyb.net.ua> Date: Mon, 16 Oct 2006 20:15:26 +0300 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 17:15:33 -0000 In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. However, the driver doesn't currently work on all hardware that it is to support. The problem is with choosing proper BAR registers, which, as it seems, might be different for different chipsets/SMB controllers. If you have a system based on NForce2/3/4, could you please share the following information: 1. find out pci handle of your SMB controller: $ pciconf -l | fgrep 0x0c0500 and also note chip field value, it should match 00(64|84|d4|e4|52)10de. E.g.: nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de rev=0xa2 hdr=0x00 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like follows: $ pciconf -r pci0:1:1 0x20 $ pciconf -r pci0:1:1 0x24 $ pciconf -r pci0:1:1 0x50 $ pciconf -r pci0:1:1 0x54 using your pci handle instead of pci0:1:1, e.g.: $ pciconf -r pci0:1:1 0x20 00000000 $ pciconf -r pci0:1:1 0x24 00000000 $ pciconf -r pci0:1:1 0x50 00001001 $ pciconf -r pci0:1:1 0x54 00001041 3. send chip id and register values here. Thank you very much in advance. -- Andriy Gapon From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 17:56:21 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 DFE8316A407; Mon, 16 Oct 2006 17:56:21 +0000 (UTC) (envelope-from amason@rackspace.com) Received: from mx.sat.rackspace.com (mx.sat.rackspace.com [64.39.1.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B7CA43D60; Mon, 16 Oct 2006 17:56:17 +0000 (GMT) (envelope-from amason@rackspace.com) Received: from mail.rackspace.com (mail.rackspace.com [64.39.2.181]) by mx.sat.rackspace.com (8.13.6.20060614/8.13.6) with ESMTP id k9GHuGCM006982; Mon, 16 Oct 2006 12:56:17 -0500 (envelope-from amason@rackspace.com) Received: from mizar.rackspace.com (office105-56.sat4.rackspace.com [10.6.105.56]) by mail.rackspace.com (8.13.1/8.13.1) with ESMTP id k9GHu5LC004317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Oct 2006 12:56:05 -0500 From: Art Mason Organization: Rackspace Managed Hosting To: freebsd-hardware@freebsd.org Date: Mon, 16 Oct 2006 12:59:31 -0500 User-Agent: KMail/1.9.4 References: <4533BE2E.4080005@icyb.net.ua> In-Reply-To: <4533BE2E.4080005@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610161259.31567.amason@rackspace.com> Cc: freebsd-stable@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 17:56:22 -0000 On Monday 16 October 2006 12:15, Andriy Gapon wrote: > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. > However, the driver doesn't currently work on all hardware that it is to > support. The problem is with choosing proper BAR registers, which, as it > seems, might be different for different chipsets/SMB controllers. > > If you have a system based on NForce2/3/4, could you please share the > following information: > > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de. > E.g.: > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00 > > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 > using your pci handle instead of pci0:1:1, e.g.: > $ pciconf -r pci0:1:1 0x20 > 00000000 > $ pciconf -r pci0:1:1 0x24 > 00000000 > $ pciconf -r pci0:1:1 0x50 > 00001001 > $ pciconf -r pci0:1:1 0x54 > 00001041 > > 3. send chip id and register values here. > > Thank you very much in advance. Hope this helps. Motherboard is an Asus A8N (non-SLI) Socket 939 part w/ an nForce 4 chipset: 6.1-RELEASE FreeBSD 6.1-RELEASE #0 (GENERIC) pciconf -l | fgrep 0x0c0500 none1@pci0:1:1: class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2 hdr=0x00 pciconf -r pci0:1:1 0x20 00004c01 pciconf -r pci0:1:1 0x24 00004c41 pciconf -r pci0:1:1 0x50 00004c01 pciconf -r pci0:1:1 0x54 00004c41 Let me know if I can provide any additional information, or correct information if I did this wrong, ha! Cheers, -- Art Mason amason@rackspace.com Intensive Network Security Rackspace Managed Hosting (800) 961-4454 ext. 4290 From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 17:58:25 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 36D7816A40F; Mon, 16 Oct 2006 17:58:25 +0000 (UTC) (envelope-from zakharov_vv@bk.ru) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E5EE43D5C; Mon, 16 Oct 2006 17:58:23 +0000 (GMT) (envelope-from zakharov_vv@bk.ru) Received: from [83.237.96.19] (port=35025 helo=darkstar.bsd) by mx2.mail.ru with esmtp id 1GZWjG-000KYR-00; Mon, 16 Oct 2006 21:58:22 +0400 Received: from darkstar.bsd (localhost [127.0.0.1]) by darkstar.bsd (8.13.8/8.13.4) with ESMTP id k9GHwFad001095; Mon, 16 Oct 2006 21:58:15 +0400 (MSD) (envelope-from zakharov_vv@bk.ru) Received: (from vovka@localhost) by darkstar.bsd (8.13.8/8.13.4/Submit) id k9GHwFa7001094; Mon, 16 Oct 2006 21:58:15 +0400 (MSD) (envelope-from zakharov_vv@bk.ru) X-Authentication-Warning: darkstar.bsd: vovka set sender to zakharov_vv@bk.ru using -f Date: Mon, 16 Oct 2006 21:58:15 +0400 From: Zakharov Vladimir To: Andriy Gapon Message-ID: <20061016175815.GA951@darkstar.bsd> Mail-Followup-To: Andriy Gapon , freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org References: <4533BE2E.4080005@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4533BE2E.4080005@icyb.net.ua> X-Operating-System: FreeBSD 6.2-PRERELEASE i386 User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 17:58:25 -0000 On Mon, Oct 16, 2006, Andriy Gapon wrote: > 1. find out pci handle of your SMB controller: # pciconf -lv | fgrep 0x0c0500 -A 4 nfsmb0@pci0:1:1: class=0x0c0500 card=0x0c111043 chip=0x006410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP-T? SMBus Controller' class = serial bus subclass = SMBus > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 # pciconf -r pci0:1:1: 0x20 00000000 # pciconf -r pci0:1:1: 0x24 00000000 # pciconf -r pci0:1:1: 0x50 00005001 # pciconf -r pci0:1:1: 0x54 00005501 > 3. send chip id and register values here. # uname -a FreeBSD 6.2-PRERELEASE Mon Oct 16 21:31:17 MSD 2006 i386 From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 18:32:12 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 8F4CB16A4F0; Mon, 16 Oct 2006 18:32:12 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB88A43DF4; Mon, 16 Oct 2006 18:31:32 +0000 (GMT) (envelope-from stefan.lambrev@sun-fish.com) Received: from sun-fish.com (localhost.cmotd.com [127.0.0.1]) by sun-fish.com (Postfix) with ESMTP id 0CC0E38575; Mon, 16 Oct 2006 20:31:29 +0200 (CEST) Received: from [192.168.25.18] (unknown [192.168.25.18]) by sun-fish.com (Postfix) with ESMTP id B16623855A; Mon, 16 Oct 2006 20:31:28 +0200 (CEST) Message-ID: <4533D000.3020902@sun-fish.com> Date: Mon, 16 Oct 2006 21:31:28 +0300 From: Cheffo User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4533BE2E.4080005@icyb.net.ua> In-Reply-To: <4533BE2E.4080005@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV Cc: freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 18:32:12 -0000 Andriy Gapon wrote: > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. > However, the driver doesn't currently work on all hardware that it is to > support. The problem is with choosing proper BAR registers, which, as it > seems, might be different for different chipsets/SMB controllers. > > If you have a system based on NForce2/3/4, could you please share the > following information: > > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de. > E.g.: > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00 > > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 > using your pci handle instead of pci0:1:1, e.g.: > $ pciconf -r pci0:1:1 0x20 > 00000000 > $ pciconf -r pci0:1:1 0x24 > 00000000 > $ pciconf -r pci0:1:1 0x50 > 00001001 > $ pciconf -r pci0:1:1 0x54 > 00001041 > > 3. send chip id and register values here. > > Thank you very much in advance. > > none1@pci0:1:1: class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2 hdr=0x00 pciconf -r pci0:1:1 0x20 00004c01 pciconf -r pci0:1:1 0x24 00004c41pciconf -r pci0:1:1 0x50 00004c01 pciconf -r pci0:1:1 0x54 00004c41 FreeBSD cheffo.freebsd-bg.org 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #10: Sun Oct 8 20:01:14 EEST 2006 From owner-freebsd-hardware@FreeBSD.ORG Mon Oct 16 19:02: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 DBF0116A416 for ; Mon, 16 Oct 2006 19:02:42 +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 D642C43FF6 for ; Mon, 16 Oct 2006 18:55:03 +0000 (GMT) (envelope-from dking@ketralnis.com) Received: from [192.168.1.87] (pix.xythos.com [64.154.218.194]) (authenticated bits=0) by ketralnis.com (8.13.6/8.13.6) with ESMTP id k9GIsLqO030593 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 16 Oct 2006 11:54:21 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <301DDDB6-A47E-448F-A145-7B2087599598@ketralnis.com> References: <78ED28FACE63744386D68D8A9D1CF5D4209C94@MAIL.corp.lumeta.com> <200610140346.22554.soralx@cydem.org> <301DDDB6-A47E-448F-A145-7B2087599598@ketralnis.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4ADE9CE4-089C-483D-B1C2-02230B045D01@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Mon, 16 Oct 2006 11:54:15 -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, 16 Oct 2006 19:02:42 -0000 Here's another run that doesn't have a constant number of bytes, so the bytes/sec might be a little more accurate ~% for BS in 1 512 $(expr 1024 \* 4) $(expr 1024 \* 16) $(expr 1024 \* 64); do dd if=/dev/random of=/dev/null bs=$BS count=1024; done 1024+0 records in 1024+0 records out 1024 bytes transferred in 0.395678 secs (2588 bytes/sec) 1024+0 records in 1024+0 records out 524288 bytes transferred in 0.791416 secs (662468 bytes/sec) 1024+0 records in 1024+0 records out 4194304 bytes transferred in 6.415680 secs (653758 bytes/sec) 1024+0 records in 1024+0 records out 16777216 bytes transferred in 25.814593 secs (649912 bytes/sec) 1024+0 records in 1024+0 records out 67108864 bytes transferred in 102.280978 secs (656123 bytes/sec) On 16 Oct 2006, at 10:14, David King wrote: >> 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) > > > ~% cat test_rand_block.sh > #!/usr/local/bin/bash > > for BS in 1 512 $(expr 1024 \* 4) $(expr 1024 \* 16) $(expr 1024 \* > 64); do > COUNT=$(expr $(expr 1024 \* 64) / $BS) > BYTES=$(expr $COUNT \* $BS) > > echo bs=$BS count=$COUNT bytes=$BYTES > > dd if=/dev/random of=/dev/null bs=$BS count=$COUNT > > echo ------; > done > ~% sh test_rand_block.sh > bs=1 count=65536 bytes=65536 > 65536+0 records in > 65536+0 records out > 65536 bytes transferred in 25.599306 secs (2560 bytes/sec) > ------ > bs=512 count=128 bytes=65536 > 128+0 records in > 128+0 records out > 65536 bytes transferred in 0.099902 secs (656003 bytes/sec) > ------ > bs=4096 count=16 bytes=65536 > 16+0 records in > 16+0 records out > 65536 bytes transferred in 0.100660 secs (651062 bytes/sec) > ------ > bs=16384 count=4 bytes=65536 > 4+0 records in > 4+0 records out > 65536 bytes transferred in 0.099324 secs (659820 bytes/sec) > ------ > bs=65536 count=1 bytes=65536 > 1+0 records in > 1+0 records out > 65536 bytes transferred in 0.099681 secs (657458 bytes/sec) > ------ > > _______________________________________________ > 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 16 20:28: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 40B4A16A417; Mon, 16 Oct 2006 20:28:03 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.ipt.ru (mail.ipt.ru [80.253.10.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97A9743D5D; Mon, 16 Oct 2006 20:28:00 +0000 (GMT) (envelope-from bsam@ipt.ru) Received: from doc.sem.ipt.ru ([192.168.12.1] helo=ipt.ru) by mail.ipt.ru with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1GZZ3y-0008pt-SO; Tue, 17 Oct 2006 00:27:54 +0400 Received: from bsam by ipt.ru with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GZZ5D-00075r-QC; Tue, 17 Oct 2006 00:29:11 +0400 To: Andriy Gapon References: <4533BE2E.4080005@icyb.net.ua> From: Boris Samorodov Date: Tue, 17 Oct 2006 00:29:11 +0400 In-Reply-To: <4533BE2E.4080005@icyb.net.ua> (Andriy Gapon's message of "Mon, 16 Oct 2006 20:15:26 +0300") Message-ID: <01402184@srv.sem.ipt.ru> 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-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Oct 2006 20:28:03 -0000 On Mon, 16 Oct 2006 20:15:26 +0300 Andriy Gapon wrote: > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. > However, the driver doesn't currently work on all hardware that it is to > support. The problem is with choosing proper BAR registers, which, as it > seems, might be different for different chipsets/SMB controllers. > If you have a system based on NForce2/3/4, could you please share the > following information: > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 %pciconf -lv | fgrep 0x0c0500 -A3 none9@pci0:10:1: class=0x0c0500 card=0x1b571019 chip=0x026410de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' class = serial bus subclass = SMBus > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 # pciconf -r pci0:10:1 0x20 00001c01 # pciconf -r pci0:10:1 0x24 00001c41 # pciconf -r pci0:10:1 0x50 00000000 # pciconf -r pci0:10:1 00000000 WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 17 00:08: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 D21F816A412 for ; Tue, 17 Oct 2006 00:08:42 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from omta03sl.mx.bigpond.com (omta03sl.mx.bigpond.com [144.140.92.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED80C43D6B for ; Tue, 17 Oct 2006 00:08:41 +0000 (GMT) (envelope-from andrew@areilly.bpa.nu) Received: from areilly.bpa.nu ([141.168.2.3]) by omta03sl.mx.bigpond.com with ESMTP id <20061017000840.VWSF8785.omta03sl.mx.bigpond.com@areilly.bpa.nu> for ; Tue, 17 Oct 2006 00:08:40 +0000 Received: (qmail 38862 invoked by uid 501); 17 Oct 2006 00:06:44 -0000 Date: Tue, 17 Oct 2006 10:06:44 +1000 From: Andrew Reilly To: Andriy Gapon Message-ID: <20061017000644.GB38613@duncan.reilly.home> References: <4533BE2E.4080005@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4533BE2E.4080005@icyb.net.ua> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 00:08:42 -0000 $ sudo pciconf -l | fgrep 0x0c0500 none1@pci0:1:1: class=0x0c0500 card=0x0c111458 chip=0x005210de rev=0xa2 hdr=0x00 $ sudo pciconf -r pci0:1:1 0x20 00001c01 $ sudo pciconf -r pci0:1:1 0x24 00001c41 $ sudo pciconf -r pci0:1:1 0x50 00001c01 $ sudo pciconf -r pci0:1:1 0x54 00001c41 This is on an nForce 4/AMD64-X2 system. Hope this helps. Cheers, -- Andrew From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 17 00:41:43 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 5E5A416A403; Tue, 17 Oct 2006 00:41:43 +0000 (UTC) (envelope-from fbsdlist@stormbringer.clara.co.uk) Received: from relay3.mail.uk.clara.net (relay3.mail.uk.clara.net [80.168.70.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id C041143D55; Tue, 17 Oct 2006 00:41:42 +0000 (GMT) (envelope-from fbsdlist@stormbringer.clara.co.uk) Received: from strategydsl.claranet.co.uk ([80.168.135.171] helo=storm.lan) by relay3.mail.uk.clara.net with esmtp (Exim 4.46) id 1GZd1Y-0002gg-FD; Tue, 17 Oct 2006 01:41:40 +0100 From: Dan To: freebsd-stable@freebsd.org Date: Tue, 17 Oct 2006 01:41:41 +0100 User-Agent: KMail/1.9.1 References: <4533BE2E.4080005@icyb.net.ua> In-Reply-To: <4533BE2E.4080005@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610170141.41902.fbsdlist@stormbringer.clara.co.uk> Cc: Andriy Gapon , freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 00:41:43 -0000 On Monday 16 October 2006 18:15, Andriy Gapon wrote: > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan > Ermilov. However, the driver doesn't currently work on all hardware > that it is to support. The problem is with choosing proper BAR > registers, which, as it seems, might be different for different > chipsets/SMB controllers. > > If you have a system based on NForce2/3/4, could you please share the > following information: > > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de. > E.g.: > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00 (root)# uname -a FreeBSD storm 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon May 22 23:55:36 BST 2006 root@storm:/usr/obj/usr/src/sys/GENERIC i386 (root)# pciconf -lv | fgrep 0x0c0500 -A 4 none1@pci0:1:1: class=0x0c0500 card=0x0c111458 chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class = serial bus subclass = SMBus > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 (root)# pciconf -r pci0:1:1 0x20 00001c01 (root)# pciconf -r pci0:1:1 0x24 00001c41 (root)# pciconf -r pci0:1:1 0x50 00001c01 (root)# pciconf -r pci0:1:1 0x54 00001c41 From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 17 10:03: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 5658616A416; Tue, 17 Oct 2006 10:03:17 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BB1243D53; Tue, 17 Oct 2006 10:03:15 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA02057; Tue, 17 Oct 2006 13:03:12 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4534AA60.1080205@icyb.net.ua> Date: Tue, 17 Oct 2006 13:03:12 +0300 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.7 (X11/20061017) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4533BE2E.4080005@icyb.net.ua> <200610170141.41902.fbsdlist@stormbringer.clara.co.uk> In-Reply-To: <200610170141.41902.fbsdlist@stormbringer.clara.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 10:03:17 -0000 Big thanks to everybody who responded! It would be great to get more information about the following chip ids for which we haven't got any reports yet: 00d410de "nVidia Corporation nForce3 Pro150 SMBus (MCP)" 003410de "nVidia Corporation nForce4 SMBus (MCP-04)" 036810de "nVidia Corporation nForce4 SMBus (MCP55)" Thank you. -- Andriy Gapon From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 17 12:48:26 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 017C416A415; Tue, 17 Oct 2006 12:48:26 +0000 (UTC) (envelope-from freebsd@orchid.homeunix.org) Received: from orchid.homeunix.org (ats117.neoplus.adsl.tpnet.pl [83.27.0.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE07D43D5A; Tue, 17 Oct 2006 12:48:22 +0000 (GMT) (envelope-from freebsd@orchid.homeunix.org) Received: from [192.168.1.66] (blackacidevil.orchid.homeunix.org [192.168.1.66]) (authenticated bits=0) by orchid.homeunix.org (8.13.6/8.13.6) with ESMTP id k9HCmEsZ087352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 Oct 2006 14:48:20 +0200 (CEST) (envelope-from freebsd@orchid.homeunix.org) Message-ID: <4534D107.8070000@orchid.homeunix.org> Date: Tue, 17 Oct 2006 14:48:07 +0200 From: Karol Kwiatkowski User-Agent: Thunderbird 1.5.0.7 (X11/20061011) MIME-Version: 1.0 To: Andriy Gapon References: <4533BE2E.4080005@icyb.net.ua> In-Reply-To: <4533BE2E.4080005@icyb.net.ua> X-Enigmail-Version: 0.94.1.0 OpenPGP: id=06E09309; url=http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigBF20459BE2E68E94567E488C" X-Virus-Scanned: ClamAV 0.88.5/2038/Tue Oct 17 00:48:19 2006 on orchid.homeunix.org X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@orchid.homeunix.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 12:48:26 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBF20459BE2E68E94567E488C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 16/10/2006 19:15, Andriy Gapon wrote: > If you have a system based on NForce2/3/4, could you please share the > following information: >=20 > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de.= > E.g.: > nfsmb0@pci0:1:1: class=3D0x0c0500 card=3D0x1c02147b chip=3D0x006= 410de > rev=3D0xa2 hdr=3D0x00 # uname -srp FreeBSD 6.2-PRERELEASE i386 # pciconf -lv | fgrep 0x0c0500 -A 4 nfsmb0@pci0:1:1: class=3D0x0c0500 card=3D0x00841849 chip=3D0x00841= 0de rev=3D0xa1 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' device =3D 'nForce MCP2S PCI System Management' class =3D serial bus subclass =3D SMBus > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 # pciconf -r pci0:1:1 0x20 00000000 # pciconf -r pci0:1:1 0x24 00000000 # pciconf -r pci0:1:1 0x50 00004301 # pciconf -r pci0:1:1 0x54 00004301 Cheers, Karol --=20 Karol Kwiatkowski OpenPGP: http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc --------------enigBF20459BE2E68E94567E488C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFNNENezeoPAwGIYsRCMwtAJ9HrcLjGsmw+gO7MNbDg5Ta1D9NKwCeIUUw kpD4Ry2ysqZ9SiKQDcoQAGU= =s4mh -----END PGP SIGNATURE----- --------------enigBF20459BE2E68E94567E488C-- From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 17 15:14: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 4F3AA16A415 for ; Tue, 17 Oct 2006 15:14:17 +0000 (UTC) (envelope-from scorp@scorp.sk) Received: from pavol.slovenska.sk (t0uch.slovenska.sk [212.5.219.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A1543D62 for ; Tue, 17 Oct 2006 15:14:15 +0000 (GMT) (envelope-from scorp@scorp.sk) Received: (qmail 91518 invoked by uid 98); 17 Oct 2006 15:14:10 -0000 Received: from 87.244.196.58 by pavol.slovenska.sk (envelope-from , uid 82) with qmail-scanner-1.25 (uvscan: v4.4.00/v4786. spamassassin: 3.0.2. Clear:RC:0(87.244.196.58):. Processed in 1.028931 secs); 17 Oct 2006 15:14:10 -0000 X-Qmail-Scanner-Mail-From: scorp@scorp.sk via pavol.slovenska.sk X-Qmail-Scanner: 1.25 (Clear:RC:0(87.244.196.58):. Processed in 1.028931 secs) Received: from unknown (HELO miriam-in.slovenska.sk) (scorp@87.244.196.58) by ns.slovenska.sk with AES256-SHA encrypted SMTP; 17 Oct 2006 15:14:09 -0000 Date: Tue, 17 Oct 2006 17:14:09 +0200 From: =?Windows-1250?Q?Pavol_=C8ierny?= X-Mailer: The Bat! (v3.5.30) Professional Organization: WEBY.SLOVENSKA.SK X-Priority: 3 (Normal) Message-ID: <1975261722.20061017171409@cierny.sk> To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=Windows-1250 Content-Transfer-Encoding: 8bit Subject: Sun Fire X2200 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 15:14:17 -0000 Hello, Is anybody runing FreeBSD on the X2200 or X2100 ? I have problems with the lights-out management (Sun calls it LOM) The machine has 2 broadcom NIC ports and 2 nvidia... One of the broadcoms is for LOM. FreeBSD detects both broadcoms and the LOM stops working. It doesn't detect the nvidia NICs. Has anyone been solving this? Is there a possibility to prevent FreeBSD to detect the second broadcom? device.hints doesn't help. Thank you --- Best regards Pavol Èierny From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 17 22:25: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 24E8B16A407 for ; Tue, 17 Oct 2006 22:25:07 +0000 (UTC) (envelope-from jbq@caraldi.com) Received: from caraldi.com (195-13-58-165.oxyd.net [195.13.58.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE6743D6A for ; Tue, 17 Oct 2006 22:25:06 +0000 (GMT) (envelope-from jbq@caraldi.com) Received: from zoupla.cottages (laf31-2-82-224-106-41.fbx.proxad.net [82.224.106.41]) by caraldi.com (Postfix) with ESMTP id E2BFD622E for ; Wed, 18 Oct 2006 00:25:04 +0200 (CEST) Received: by zoupla.cottages (Postfix, from userid 1001) id A29502E274; Wed, 18 Oct 2006 00:25:04 +0200 (CEST) Date: Wed, 18 Oct 2006 00:25:04 +0200 From: Jean-Baptiste Quenot To: freebsd-hardware@freebsd.org Message-ID: <20061017222503.GA9416@zoupla.cottages> Mail-Followup-To: Jean-Baptiste Quenot , freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: <200610091456.23822.jhb@freebsd.org> User-Agent: mutt-ng/devel-r804 (FreeBSD) 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: Tue, 17 Oct 2006 22:25:16 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Hi, Your suggestion to try the 'Safe Mode' was very good indeed, as it allowed to pass the disk mounting stage. I found a more long-term solution by setting hint.apic.0.disabled=1 in /boot/loader.conf. But this is not sufficient to make FreeBSD boot, I also have to: * disable the front USB panel, and one of the two rear USB panels in the BIOS otherwise the keyboard and mouse do not work * unplug the mouse during the boot, otherwise keyboard and mouse do not work. I plug it in again once entering user-land Other useful info: * For the graphics card, I'm satisfied with the "vesa" driver. * I was lucky with the netword card as "bfe0" was detected right on install Things that are not working: * No sound * No CD/DVD support I also have a very annoying problem: when I run Xorg, the mouse freezes every 5 minutes, I have to unplug it. As soon as I plug it in again, mouse moves freely. I tried with another mouse, same problem. Restarting Xorg does not help. Restarting moused either. Any idea to solve the USB mouse problem would be more than helpful. You will find attached the dmesg output, just in case. I've heard about a [1]USB patch, do you think it can be useful for my problem? Note: I was using FreeBSD 6.1-RELEASE, and upgraded to 6.2-PRERELEASE (checked out from RELENG_6) but that didn't change anything. Thanks in advance, -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/ [1] http://people.freebsd.org/~iedowse/usb.diff --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=utf-8 Content-Disposition: attachment; filename="dmesg.today" Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #0: Sat Oct 14 18:12:52 CEST 2006 jbq@zoupla.cottages:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3800+ (2405.03-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40ff2 Stepping = 2 Features=0x78bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1d,,CR8> real memory = 1005453312 (958 MB) avail memory = 959361024 (914 MB) kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 15 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff irq 7 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered atapci0: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 11 at device 14.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xcc00-0xcc0f mem 0xfe02c000-0xfe02cfff irq 10 at device 15.0 on pci0 ata4: on atapci1 ata5: on atapci1 pcib4: at device 16.0 on pci0 pci4: on pcib4 bfe0: mem 0xfdbfe000-0xfdbfffff irq 5 at device 7.0 on pci4 miibus0: on bfe0 bmtphy0: on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:13:72:33:1e:42 pci0: at device 16.1 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 uhub0: device problem (SET_ADDR_FAILED), disabling port 4 Timecounter "TSC" frequency 2405033974 Hz quality 800 Timecounters tick every 1.000 msec ad4: 238418MB at ata2-master SATA300 Trying to mount root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...8 5 5 3 1 0 0 done All buffers synced. Uptime: 28s acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Powering system off using ACPI Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #0: Sat Oct 14 18:12:52 CEST 2006 jbq@zoupla.cottages:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3800+ (2405.03-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40ff2 Stepping = 2 Features=0x78bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1d,,CR8> real memory = 1005453312 (958 MB) avail memory = 959361024 (914 MB) kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 15 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff irq 7 at device 11.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered atapci0: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 11 at device 14.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xcc00-0xcc0f mem 0xfe02c000-0xfe02cfff irq 10 at device 15.0 on pci0 ata4: on atapci1 ata5: on atapci1 pcib4: at device 16.0 on pci0 pci4: on pcib4 bfe0: mem 0xfdbfe000-0xfdbfffff irq 5 at device 7.0 on pci4 miibus0: on bfe0 bmtphy0: on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:13:72:33:1e:42 pci0: at device 16.1 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: DELL DELL USB Keyboard, rev 1.10/1.05, addr 2, iclass 3/1 kbd0 at ukbd0 Timecounter "TSC" frequency 2405031978 Hz quality 800 Timecounters tick every 1.000 msec ad4: 238418MB at ata2-master SATA300 Trying to mount root from ufs:/dev/ad4s1a WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. pid 2289 (muttng), uid 1001: exited on signal 11 (core dumped) ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. pid 2262 (gaim), uid 1001: exited on signal 6 (core dumped) ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...4 2 3 1 0 0 done All buffers synced. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #0: Sun Oct 15 22:48:24 CEST 2006 jbq@zoupla.cottages:/usr/obj/usr/src/sys/ZOUPLA Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3800+ (2405.03-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40ff2 Stepping = 2 Features=0x78bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1d,,CR8> real memory = 1005453312 (958 MB) avail memory = 958681088 (914 MB) kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 15 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pci0: at device 11.1 (no driver attached) atapci0: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 11 at device 14.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xcc00-0xcc0f mem 0xfe02c000-0xfe02cfff irq 10 at device 15.0 on pci0 ata4: on atapci1 ata5: on atapci1 pcib4: at device 16.0 on pci0 pci4: on pcib4 bfe0: mem 0xfdbfe000-0xfdbfffff irq 5 at device 7.0 on pci4 miibus0: on bfe0 bmtphy0: on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:13:72:33:1e:42 pci0: at device 16.1 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 uhub0: device problem (SET_ADDR_FAILED), disabling port 4 Timecounter "TSC" frequency 2405029908 Hz quality 800 Timecounters tick every 1.000 msec ad4: 238418MB at ata2-master SATA300 Trying to mount root from ufs:/dev/ad4s1a Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...8 5 4 3 2 0 0 done All buffers synced. Uptime: 24s acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Powering system off using ACPI Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #0: Sun Oct 15 22:48:24 CEST 2006 jbq@zoupla.cottages:/usr/obj/usr/src/sys/ZOUPLA Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3800+ (2405.03-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40ff2 Stepping = 2 Features=0x78bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1d,,CR8> real memory = 1005453312 (958 MB) avail memory = 958681088 (914 MB) kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 3.0 on pci0 pci2: on pcib2 pcib3: at device 4.0 on pci0 pci3: on pcib3 pci0: at device 5.0 (no driver attached) pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 15 at device 11.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pci0: at device 11.1 (no driver attached) atapci0: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xe000-0xe00f mem 0xfe02d000-0xfe02dfff irq 11 at device 14.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xcc00-0xcc0f mem 0xfe02c000-0xfe02cfff irq 10 at device 15.0 on pci0 ata4: on atapci1 ata5: on atapci1 pcib4: at device 16.0 on pci0 pci4: on pcib4 bfe0: mem 0xfdbfe000-0xfdbfffff irq 5 at device 7.0 on pci4 miibus0: on bfe0 bmtphy0: on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: Ethernet address: 00:13:72:33:1e:42 pci0: at device 16.1 (no driver attached) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 device_attach: atkbd0 attach returned 6 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: DELL DELL USB Keyboard, rev 1.10/1.05, addr 2, iclass 3/1 kbd0 at ukbd0 Timecounter "TSC" frequency 2405028042 Hz quality 800 Timecounters tick every 1.000 msec ad4: 238418MB at ata2-master SATA300 Trying to mount root from ufs:/dev/ad4s1a ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. pid 1664 (gaim), uid 1001: exited on signal 6 (core dumped) ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. stray irq7 ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. stray irq7 ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech M4848, rev 1.00/5.00, addr 3, iclass 3/1 ums0: 1 buttons. ums0: at uhub0 port 3 (addr 3) disconnected ums0: detached ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. too many stray irq 7's: not logging anymore --lrZ03NoBR/3+SXJZ-- From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 18 01:26:37 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 4EF1716A519; Wed, 18 Oct 2006 01:26:37 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from mail.digitalfreaks.org (arbitor.digitalfreaks.org [216.151.95.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 116A943E04; Wed, 18 Oct 2006 01:26:00 +0000 (GMT) (envelope-from lavalamp@spiritual-machines.org) Received: by mail.digitalfreaks.org (Postfix, from userid 1022) id 5BA4D17EDD; Tue, 17 Oct 2006 21:25:52 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.digitalfreaks.org (Postfix) with ESMTP id 539F617ED2; Tue, 17 Oct 2006 21:25:52 -0400 (EDT) Date: Tue, 17 Oct 2006 21:25:52 -0400 (EDT) From: "Brian A. Seklecki" X-X-Sender: lavalamp@arbitor.digitalfreaks.org To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= In-Reply-To: <86sljvli0m.fsf@xps.des.no> Message-ID: <20061017205906.U63561@arbitor.digitalfreaks.org> References: <44E040CF.9080205@alphaque.com> <44E05598.20004@alphaque.com> <20060816123731.GE45370@cdnetworks.co.kr> <44E4073C.9010008@alphaque.com> <86sljvli0m.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2019366847-1161133148=:63561" Content-ID: <20061017210143.J63561@arbitor.digitalfreaks.org> Cc: pyunyh@gmail.com, freebsd-hackers@freebsd.org, yamt@netbsd.org, wpaul@freebsd.org, freebsd-hardware@freebsd.org, Dinesh Nair Subject: Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2006 01:26:37 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-2019366847-1161133148=:63561 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: <20061017205919.G63561@arbitor.digitalfreaks.org> Dinesh et al: Did this problem ever get resolved? I'm tracking down a very similar bug with an SBC - An Axiomtek SBC83672 Ver.C13.10.0. Dinish: What platform are you using? You said you had a 4x re(4) SBC, but never posted full dmesg(8). Mine is a Via C3/Samuel inside an OEM network appliance. URL below. My platform is netbsd-3, but I just tried -current to see if recent rtl8169.c changes fix it. No dice. No dice with NetBSD -current either. FreeBSD 6.1 panics at probe of re0 as you've posted. With NetBSD, re0 probes then fails the diagnostic function, then detatches. re1, re2, re3 all then sucsessfully probe on my system, but then they show no media status and tcpdump(8)/arp(8) show no activity. They're dead in the water. There has also been some mention of the errors below on NetBSD and OpenBSD probably because of the bitrot/driver drift: http://marc.theaimsgroup.com/?t=111658040100001&r=1&w=2 http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=26025 I'm gonna grab a FreeBSD 7-current snapshot boot only ISO and give it a go. I see a 8139C+ fix was commited 5 weeks ago by yongar@. Based on some other threads I've been reading on "8139C+ Watchdog Timeouts" and "Diag failed, failing to attach" related messages, I imagine FreeBSD has this covered. re0 at pci0 dev 16 function 0: RealTek 8139C+ 10/100BaseTX re0: interrupting at irq 5 re0: Ethernet address 00:60:e0:e1:3e:31 re0: using 64 tx descriptors ukphy0 at re0 phy 0: Generic IEEE 802.3u media interface ukphy0: OUI 0x000000, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re: diagnostic failed, failed to receive packet in loopback mode re0: attach aborted due to hardware diag failure ukphy0 detached ----- Full dmesg(8): NetBSD 3.1_RC3 (CFRDMDROOT.MPACPI-$Revision: 1.21.4.5 $) #9: Sat Oct 14 21:19:14 EDT 2006 root@thunderwing:/home/nbsd/obj.i386/temp/sys/arch/i386/compile/CFRDMDROOT.MPACPI total memory = 189 MB avail memory = 166 MB BIOS32 rev. 0 found at 0xfb570 mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: VIA C3 Samuel 2/Ezra (686-class), 800.11 MHz, id 0x673 cpu0: features 80803035 cpu0: features 80803035 cpu0: features 80803035<3DNOW> cpu0: "VIA Samuel 2" cpu0: I-cache 64 KB 32B/line 4-way, D-cache 64 KB 32B/line 4-way cpu0: L2 cache 64 KB 32B/line 4-way cpu0: ITLB 128 4 KB entries 8-way cpu0: DTLB 128 4 KB entries 8-way cpu0: 4 page colors acpi0 at mainbus0 acpi0: using Intel ACPI CA subsystem version 20040211 acpi0: X/RSDT: OemId , AslId acpi0: SCI interrupting at int 9 acpi0: fixed-feature power button present ACPI Object Type 'Processor' (0x0c) at acpi0 not configured acpibut0 at acpi0 (PNP0C0C): ACPI Power Button PNP0C01 [System Board] at acpi0 not configured PNP0A03 [PCI Bus] at acpi0 not configured PNP0C0F [PCI interrupt link device] at acpi0 not configured PNP0C0F [PCI interrupt link device] at acpi0 not configured PNP0C0F [PCI interrupt link device] at acpi0 not configured PNP0C0F [PCI interrupt link device] at acpi0 not configured PNP0C02 [Plug and Play motherboard register resources] at acpi0 not configured PNP0000 [AT Interrupt Controller] at acpi0 not configured PNP0200 [AT DMA Controller] at acpi0 not configured PNP0100 [AT Timer] at acpi0 not configured PNP0B00 [AT Real-Time Clock] at acpi0 not configured PNP0800 [AT-style speaker sound] at acpi0 not configured npx1 at acpi0 (PNP0C04) npx1: io 0xf0-0xff irq 13 npx1: using exception 16 fdc0 at acpi0 (PNP0700) fdc0: io 0x3f0-0x3f5,0x3f7 irq 6 drq 2 com0 at acpi0 (PNP0501-1) com0: io 0x3f8-0x3ff irq 4 com0: ns16550a, working fifo com1 at acpi0 (PNP0501-2) com1: io 0x2f8-0x2ff irq 3 com1: ns16550a, working fifo lpt0 at acpi0 (PNP0400-1) lpt0: io 0x378-0x37f irq 7 pci0 at mainbus0 bus 0: configuration mode 1 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok pchb0 at pci0 dev 0 function 0 pchb0: VIA Technologies product 0x0601 (rev. 0x05) agp0 at pchb0: aperture at 0xe8000000, size 0x10000000 ppb0 at pci0 dev 1 function 0: VIA Technologies product 0x8601 (rev. 0x00) pci1 at ppb0 bus 1 pci1: i/o space, memory space enabled vga0 at pci1 dev 0 function 0: Trident Microsystems product 0x8500 (rev. 0x6a) wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation) wsmux1: connecting to wsdisplay0 pcib0 at pci0 dev 7 function 0 pcib0: VIA Technologies VT82C686A PCI-ISA Bridge (rev. 0x40) viaide0 at pci0 dev 7 function 1 viaide0: VIA Technologies VT82C686A (Apollo KX133) ATA100 controller viaide0: bus-master DMA support present viaide0: primary channel configured to compatibility mode viaide0: primary channel interrupting at irq 14 atabus0 at viaide0 channel 0 viaide0: secondary channel configured to compatibility mode viaide0: secondary channel interrupting at irq 15 atabus1 at viaide0 channel 1 uhci0 at pci0 dev 7 function 2: VIA Technologies VT83C572 USB Controller (rev. 0x1a) uhci0: interrupting at irq 10 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 7 function 3: VIA Technologies VT83C572 USB Controller (rev. 0x1a) uhci1: interrupting at irq 10 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered VIA Technologies VT82C686A SMBus Controller (miscellaneous bridge, revision 0x40) at pci0 dev 7 function 4 not configured re0 at pci0 dev 16 function 0: RealTek 8139C+ 10/100BaseTX re0: interrupting at irq 5 re0: Ethernet address 00:60:e0:e1:3e:31 re0: using 64 tx descriptors ukphy0 at re0 phy 0: Generic IEEE 802.3u media interface ukphy0: OUI 0x000000, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re: diagnostic failed, failed to receive packet in loopback mode re0: attach aborted due to hardware diag failure ukphy0 detached re1 at pci0 dev 17 function 0: RealTek 8139C+ 10/100BaseTX re1: interrupting at irq 12 re1: Ethernet address 00:60:e0:e1:3e:30 re1: using 64 tx descriptors ukphy0 at re1 phy 0: Generic IEEE 802.3u media interface ukphy0: OUI 0x000000, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re2 at pci0 dev 18 function 0: RealTek 8139C+ 10/100BaseTX re2: interrupting at irq 10 re2: Ethernet address 00:60:e0:e1:3e:2f re2: using 64 tx descriptors ukphy1 at re2 phy 0: Generic IEEE 802.3u media interface ukphy1: OUI 0x000000, model 0x0000, rev. 0 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto re3 at pci0 dev 19 function 0: RealTek 8139C+ 10/100BaseTX re3: interrupting at irq 11 re3: Ethernet address 00:60:e0:e1:3e:2e re3: using 64 tx descriptors ukphy2 at re3 phy 0: Generic IEEE 802.3u media interface ukphy2: OUI 0x000000, model 0x0000, rev. 0 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isa0 at pcib0 pcppi0 at isa0 port 0x61 sysbeep0 at pcppi0 isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support isapnp0: no ISA Plug 'n Play devices found md0: internal 10500 KB image area IPsec: Initialized Security Association Processing. uhidev0 at uhub0 port 1 configuration 1 interface 0 uhidev0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 2, iclass 3/1 ukbd0 at uhidev0 wskbd0 at ukbd0 mux 1 wskbd0: connecting to wsdisplay0 wd0 at atabus0 drive 0: wd0: drive supports 4-sector PIO transfers, LBA addressing wd0: 1953 MB, 3970 cyl, 16 head, 63 sec, 512 bytes/sect x 4001760 sectors wd0: 32-bit data port wd0: drive supports PIO mode 4, DMA mode 2 wd0(viaide0:0:0): using PIO mode 4, DMA mode 2 (using DMA) atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 1: cdrom removable cd0: 32-bit data port cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33) cd0(viaide0:1:1): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA) boot device: wd0 root on md0a dumps on md0b root file system type: ffs wsdisplay0: screen 1 added (80x25, vt100 emulation) wsdisplay0: screen 2 added (80x25, vt100 emulation) wsdisplay0: screen 3 added (80x25, vt100 emulation) wsdisplay0: screen 4 added (80x25, vt100 emulation) On Thu, 17 Aug 2006, Dag-Erling Smørgrav wrote: > Dinesh Nair writes: >> i never got re(4) working, and the patch i'm currently using forces >> the use of rl(4) instead of using re(4). using rl(4) still shows >> media as none, but it works the way it should with packets going in >> and out. i've yet to try dag-erling's suggestion of disabling rx and >> tx checksums. i'll also try with the patch you sent it to see if >> that works. > > If you can receive but not transmit (as I understood from other posts > in the thread, though you never answered my question about tcpdump), > disabling tx checksum offloading should be the *first* thing to try, > especially as there is a known bug in some RealTek chipsets which will > cause tx checksums to be computed incorrectly for short packets (such > as ICMP echo replies, or TCP handshake frames). > > DES > -- > Dag-Erling Smørgrav - des@des.no > _______________________________________________ > 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" > l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." --0-2019366847-1161133148=:63561-- From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 18 01:57:08 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 17FA516A40F for ; Wed, 18 Oct 2006 01:57:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC48443DA9 for ; Wed, 18 Oct 2006 01:56:41 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so137614pye for ; Tue, 17 Oct 2006 18:56:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=N1d9S8ARzp7BaKQj+EtM7zvKNGEVlHUkmMZjopdNfqTm5FFQZWyrkR83RSWiZo5Uzjg71WqzU4zq/Fjr7oWeH1oCOs2tyswKBM7rZp2Cas2FnVEb1Imvcujsz8ENi73wLjwOlkuT6qMOQp1W2gNBD5r03lQYq0ASRkXzDU0/k9Q= Received: by 10.35.8.13 with SMTP id l13mr16592214pyi; Tue, 17 Oct 2006 18:56:07 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 16sm279706nzo.2006.10.17.18.56.05; Tue, 17 Oct 2006 18:56:07 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k9I1tIFQ002289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Oct 2006 10:55:18 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k9I1tDZK002288; Wed, 18 Oct 2006 10:55:13 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 18 Oct 2006 10:55:11 +0900 From: Pyun YongHyeon To: "Brian A. Seklecki" Message-ID: <20061018015511.GC1756@cdnetworks.co.kr> References: <44E040CF.9080205@alphaque.com> <44E05598.20004@alphaque.com> <20060816123731.GE45370@cdnetworks.co.kr> <44E4073C.9010008@alphaque.com> <86sljvli0m.fsf@xps.des.no> <20061017205906.U63561@arbitor.digitalfreaks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061017205906.U63561@arbitor.digitalfreaks.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, yamt@netbsd.org, wpaul@freebsd.org, freebsd-hardware@freebsd.org, Dinesh Nair , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2006 01:57:08 -0000 On Tue, Oct 17, 2006 at 09:25:52PM -0400, Brian A. Seklecki wrote: > > Dinesh et al: > > Did this problem ever get resolved? I'm tracking down a very similar bug > with an SBC - An Axiomtek SBC83672 Ver.C13.10.0. > > Dinish: What platform are you using? You said you had a 4x re(4) SBC, but > never posted full dmesg(8). Mine is a Via C3/Samuel inside an OEM network > appliance. URL below. My platform is netbsd-3, but I just tried -current > to see if recent rtl8169.c changes fix it. No dice. > > No dice with NetBSD -current either. > > FreeBSD 6.1 panics at probe of re0 as you've posted. With NetBSD, re0 > probes then fails the diagnostic function, then detatches. re1, re2, > re3 all then sucsessfully probe on my system, but then they show no > media status and tcpdump(8)/arp(8) show no activity. They're dead in > the water. > > There has also been some mention of the errors below on NetBSD and OpenBSD > probably because of the bitrot/driver drift: > > http://marc.theaimsgroup.com/?t=111658040100001&r=1&w=2 > http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=26025 > > I'm gonna grab a FreeBSD 7-current snapshot boot only ISO and give it a > go. I see a 8139C+ fix was commited 5 weeks ago by yongar@. Based on > some other threads I've been reading on "8139C+ Watchdog Timeouts" and > "Diag failed, failing to attach" related messages, I imagine FreeBSD has > this covered. > > re0 at pci0 dev 16 function 0: RealTek 8139C+ 10/100BaseTX > re0: interrupting at irq 5 > re0: Ethernet address 00:60:e0:e1:3e:31 > re0: using 64 tx descriptors > ukphy0 at re0 phy 0: Generic IEEE 802.3u media interface > ukphy0: OUI 0x000000, model 0x0000, rev. 0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > re: diagnostic failed, failed to receive packet in loopback mode > re0: attach aborted due to hardware diag failure > ukphy0 detached > Long ago re_diag() code was disabled by default(rev 1.68). So I think you should never see the "diagnostic failed" message on FreeBSD. The other odd thing I see from your demsg output is ukphy(4) attachment. If you boot system with bootverbose mode ukphy(4) would have printed PHY OID and model number. Please let me know the OID/model number. I guess it should use rlphy(4). (If you should use NetBSD you may need to define MIIVERBOSE to active verbose message.) -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 18 02:54: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 F27B416A40F for ; Wed, 18 Oct 2006 02:54:03 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8D9643D55 for ; Wed, 18 Oct 2006 02:53:59 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id o67so157604pye for ; Tue, 17 Oct 2006 19:53:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=WyV1to7EA8Z/hoD6Zudl2sAkkwPi4544BmwF94Uc342RhWbgQ5latYIBZQOApiK9FNKz4PaqqwlqX7zNCZeuMlZGnx5qUk0SODGAGZ6rEsJ/EaKT+UIZRq9knPtUBHwtbDm/bFDQZNmcwgCHJenRmzMXkDjXMVE9r6Nfiz7M6Zk= Received: by 10.35.48.15 with SMTP id a15mr16658494pyk; Tue, 17 Oct 2006 19:53:58 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 10sm545172nzo.2006.10.17.19.53.54; Tue, 17 Oct 2006 19:53:57 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k9I2r7K2002481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Oct 2006 11:53:07 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k9I2r6LE002480; Wed, 18 Oct 2006 11:53:06 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 18 Oct 2006 11:53:06 +0900 From: Pyun YongHyeon To: "Brian A. Seklecki" Message-ID: <20061018025306.GE1756@cdnetworks.co.kr> References: <44E040CF.9080205@alphaque.com> <44E05598.20004@alphaque.com> <20060816123731.GE45370@cdnetworks.co.kr> <44E4073C.9010008@alphaque.com> <86sljvli0m.fsf@xps.des.no> <20061017205906.U63561@arbitor.digitalfreaks.org> <20061018015511.GC1756@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061018015511.GC1756@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, yamt@netbsd.org, wpaul@freebsd.org, freebsd-hardware@freebsd.org, Dinesh Nair , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Subject: Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Oct 2006 02:54:04 -0000 On Wed, Oct 18, 2006 at 10:55:11AM +0900, To Brian A. Seklecki wrote: > On Tue, Oct 17, 2006 at 09:25:52PM -0400, Brian A. Seklecki wrote: > > > > Dinesh et al: > > > > Did this problem ever get resolved? I'm tracking down a very similar bug > > with an SBC - An Axiomtek SBC83672 Ver.C13.10.0. > > > > Dinish: What platform are you using? You said you had a 4x re(4) SBC, but > > never posted full dmesg(8). Mine is a Via C3/Samuel inside an OEM network > > appliance. URL below. My platform is netbsd-3, but I just tried -current > > to see if recent rtl8169.c changes fix it. No dice. > > > > No dice with NetBSD -current either. > > > > FreeBSD 6.1 panics at probe of re0 as you've posted. With NetBSD, re0 > > probes then fails the diagnostic function, then detatches. re1, re2, > > re3 all then sucsessfully probe on my system, but then they show no > > media status and tcpdump(8)/arp(8) show no activity. They're dead in > > the water. > > > > There has also been some mention of the errors below on NetBSD and OpenBSD > > probably because of the bitrot/driver drift: > > > > http://marc.theaimsgroup.com/?t=111658040100001&r=1&w=2 > > http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=26025 > > > > I'm gonna grab a FreeBSD 7-current snapshot boot only ISO and give it a > > go. I see a 8139C+ fix was commited 5 weeks ago by yongar@. Based on > > some other threads I've been reading on "8139C+ Watchdog Timeouts" and > > "Diag failed, failing to attach" related messages, I imagine FreeBSD has > > this covered. > > > > re0 at pci0 dev 16 function 0: RealTek 8139C+ 10/100BaseTX > > re0: interrupting at irq 5 > > re0: Ethernet address 00:60:e0:e1:3e:31 > > re0: using 64 tx descriptors > > ukphy0 at re0 phy 0: Generic IEEE 802.3u media interface > > ukphy0: OUI 0x000000, model 0x0000, rev. 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Oops, I've missed OID/model number showed on your message. Sorry. Since ukphy(4) showed bogus model number I have no idea what PHY hardware the NIC has. Would you show me "pciconf -lv" output? > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > re: diagnostic failed, failed to receive packet in loopback mode > > re0: attach aborted due to hardware diag failure > > ukphy0 detached > > > > Long ago re_diag() code was disabled by default(rev 1.68). So I think > you should never see the "diagnostic failed" message on FreeBSD. > The other odd thing I see from your demsg output is ukphy(4) > attachment. If you boot system with bootverbose mode ukphy(4) would > have printed PHY OID and model number. Please let me know the > OID/model number. I guess it should use rlphy(4). > (If you should use NetBSD you may need to define MIIVERBOSE to active > verbose message.) -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 18 12:06:13 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 2033616A519 for ; Wed, 18 Oct 2006 12:06:13 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.FreeBSD.org (Postfix) with SMTP id 334BA43D78 for ; Wed, 18 Oct 2006 12:06:11 +0000 (GMT) (envelope-from quetzal@zone3000.net) Received: from unknown (HELO localhost) (217.144.69.37) by 209.67.61.254 with SMTP; 18 Oct 2006 12:06:11 -0000 Date: Wed, 18 Oct 2006 15:05:44 +0300 From: Nikolay Pavlov To: Andriy Gapon Message-ID: <20061018120544.GA5966@zone3000.net> Mail-Followup-To: Nikolay Pavlov , Andriy Gapon , freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org References: <4533BE2E.4080005@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4533BE2E.4080005@icyb.net.ua> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-RELEASE-p10 Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey 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, 18 Oct 2006 12:06:13 -0000 On Monday, 16 October 2006 at 20:15:26 +0300, Andriy Gapon wrote: > > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. > However, the driver doesn't currently work on all hardware that it is to > support. The problem is with choosing proper BAR registers, which, as it > seems, might be different for different chipsets/SMB controllers. > > If you have a system based on NForce2/3/4, could you please share the > following information: > > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de. > E.g.: > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00 > > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 > using your pci handle instead of pci0:1:1, e.g.: > $ pciconf -r pci0:1:1 0x20 > 00000000 > $ pciconf -r pci0:1:1 0x24 > 00000000 > $ pciconf -r pci0:1:1 0x50 > 00001001 > $ pciconf -r pci0:1:1 0x54 > 00001041 > > 3. send chip id and register values here. > > Thank you very much in advance. > > -- > Andriy Gapon > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" root@viking:~# pciconf -l | fgrep 0x0c0500 none0@pci0:1:1: class=0x0c0500 card=0x813f1043 chip=0x00e410de rev=0xa1 hdr=0x00 root@viking:~# pciconf -r pci0:1:1 0x20 00005001 root@viking:~# pciconf -r pci0:1:1 0x24 00005041 root@viking:~# pciconf -r pci0:1:1 0x50 00005001 root@viking:~# pciconf -r pci0:1:1 0x54 00005041 -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 18 21:50: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 0EABC16A415 for ; Wed, 18 Oct 2006 21:50:03 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from slimak.dkm.cz (slimak.dkm.cz [62.24.64.34]) by mx1.FreeBSD.org (Postfix) with SMTP id B2A5943D5D for ; Wed, 18 Oct 2006 21:50:01 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: (qmail 96642 invoked by uid 0); 18 Oct 2006 21:49:54 -0000 Received: from grimm.quip.cz (HELO ?192.168.1.2?) (213.220.192.218) by slimak.dkm.cz with SMTP; 18 Oct 2006 21:49:54 -0000 Message-ID: <4536A181.5080305@quip.cz> Date: Wed, 18 Oct 2006 23:49:53 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cz, en, cs, en-us MIME-Version: 1.0 To: Andriy Gapon References: <4533BE2E.4080005@icyb.net.ua> In-Reply-To: <4533BE2E.4080005@icyb.net.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: nfsmb survey 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, 18 Oct 2006 21:50:03 -0000 > 1. find out pci handle of your SMB controller: # pciconf -lv | fgrep 0x0c0500 -A 4 none1@pci0:1:1: class=0x0c0500 card=0x5348108e chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class = serial bus subclass = SMBus > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: # pciconf -r pci0:1:1 0x20 00001c01 # pciconf -r pci0:1:1 0x24 00001c41 # pciconf -r pci0:1:1 0x50 00001c01 # pciconf -r pci0:1:1 0x54 00001c41 FreeBSD 6.2-BETA2 FreeBSD 6.2-BETA2 #0: Mon Oct 2 03:22:01 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 19 11:00: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 28E3416A52D for ; Thu, 19 Oct 2006 11:00:41 +0000 (UTC) (envelope-from cs@schug.net) Received: from schug.net (s0.schug.net [194.97.148.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id F13B143D7F for ; Thu, 19 Oct 2006 11:00:17 +0000 (GMT) (envelope-from cs@schug.net) Received: by schug.net (Postfix, from userid 10000) id 50FB9C581D; Thu, 19 Oct 2006 13:00:16 +0200 (CEST) Date: Thu, 19 Oct 2006 13:00:16 +0200 From: Christoph Schug To: Andriy Gapon Message-ID: <20061019110016.GA20019@voodoo.schug.net> References: <4533BE2E.4080005@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4533BE2E.4080005@icyb.net.ua> Organization: SpaceNet AG User-Agent: Mutt/1.5.11 OpenPKG/2.5 Cc: freebsd-hardware@freebsd.org Subject: Re: nfsmb survey 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, 19 Oct 2006 11:00:41 -0000 On Mon, Oct 16, 2006, Andriy Gapon wrote: > If you have a system based on NForce2/3/4, could you please share the > following information: Machine is a HP Proliant DL145 G2 > 1. find out pci handle of your SMB controller: # pciconf -l | fgrep 0x0c0500 none1@pci0:1:1: class=0x0c0500 card=0x3207103c chip=0x005210de rev=0xa2 hdr=0x00 > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows:A # pciconf -r pci0:1:1 0x20 00005001· # pciconf -r pci0:1:1 0x24 00005041· # pciconf -r pci0:1:1 0x50 00005001· # pciconf -r pci0:1:1 0x54 00005041· -cs From owner-freebsd-hardware@FreeBSD.ORG Thu Oct 19 14:53: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 2BDA016A40F for ; Thu, 19 Oct 2006 14:53:56 +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 37C2743D46 for ; Thu, 19 Oct 2006 14:53:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k9JErWN7066690; Thu, 19 Oct 2006 10:53:38 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 19 Oct 2006 10:14:32 -0400 User-Agent: KMail/1.9.1 References: <20061017222503.GA9416@zoupla.cottages> In-Reply-To: <20061017222503.GA9416@zoupla.cottages> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610191014.33042.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 19 Oct 2006 10:53:39 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/2050/Thu Oct 19 03:58:33 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Jean-Baptiste Quenot 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: Thu, 19 Oct 2006 14:53:56 -0000 On Tuesday 17 October 2006 18:25, Jean-Baptiste Quenot wrote: > Hi, > > Your suggestion to try the 'Safe Mode' was very good indeed, as it > allowed to pass the disk mounting stage. I found a more long-term > solution by setting hint.apic.0.disabled=1 in /boot/loader.conf. > > But this is not sufficient to make FreeBSD boot, I also have to: > > * disable the front USB panel, and one of the two rear USB panels > in the BIOS otherwise the keyboard and mouse do not work > > * unplug the mouse during the boot, otherwise keyboard and mouse > do not work. I plug it in again once entering user-land Weird, I've no idea what would cause that, though it might be a problem in the USB drivers. You could certainly ask on the freebsd-usb@ mailing list about the USB stuff. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 21 03:01:43 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 C99ED16A407 for ; Sat, 21 Oct 2006 03:01:43 +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 57C7B43D4C for ; Sat, 21 Oct 2006 03:01:43 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr4so.prod.shaw.ca (pd2mr4so-qfe3.prod.shaw.ca [10.0.141.107]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7G0046BTQV4670@l-daemon> for freebsd-hardware@freebsd.org; Fri, 20 Oct 2006 21:01:43 -0600 (MDT) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd2mr4so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7G009FMTQS64R0@pd2mr4so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Fri, 20 Oct 2006 21:01:43 -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 <0J7G003DITQSJWF0@l-daemon> for freebsd-hardware@freebsd.org; Fri, 20 Oct 2006 21:01:40 -0600 (MDT) Date: Fri, 20 Oct 2006 20:01:38 -0700 From: soralx@cydem.org In-reply-to: <200610161201.k9GC17ol003191@lurza.secnetix.de> To: freebsd-hardware@freebsd.org Message-id: <200610202001.38727.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=koi8-r Content-transfer-encoding: 7bit Content-disposition: inline References: <200610161201.k9GC17ol003191@lurza.secnetix.de> 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, 21 Oct 2006 03:01:43 -0000 > I also think that 25 Gbit/s is overly optimistic. ha, no bullstalk here :) > > did you get to the point that you're sure it's being used? > > Now that's easy. Just type "sysctl kern.random". If you > get a bunch of lines talking about "yarrow" and "harvest", > then the kernel's software PRNG is used. If you get an > error message "unknown oid 'kern.random'", then a hardware > generator is being used. I was thinking more about the crypto device rather than the RNG: is /dev/crypto really being used? > Best regards > Oliver ("VIA C3 Nehemiah+RNG+AES ") the OP has a dual-core board -- I was interested in `ubench` of that, as that's the board I want to buy somiteme (maybe)... BTW how are things on the front of fight against noise going? who's winning, and what is the score? [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 21 05:08: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 9F0DC16A407 for ; Sat, 21 Oct 2006 05:08:48 +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 527B143D5A for ; Sat, 21 Oct 2006 05:08:48 +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 k9L58lNn024390 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 20 Oct 2006 22:08:47 -0700 (PDT) (envelope-from dking@ketralnis.com) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <200610202001.38727.soralx@cydem.org> References: <200610161201.k9GC17ol003191@lurza.secnetix.de> <200610202001.38727.soralx@cydem.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6375852F-8B76-4197-A875-A547B2B21E8B@ketralnis.com> Content-Transfer-Encoding: 7bit From: David King Date: Fri, 20 Oct 2006 22:08:43 -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: Sat, 21 Oct 2006 05:08:48 -0000 > I was thinking more about the crypto device rather than the RNG: > is /dev/crypto really being used? It seems so, since it accepts the engine that I pass it in ('-engine padlock'), whereas it complains if I pass it a different engine with hardware that it can't find > the OP has a dual-core board -- I was interested in `ubench` of that, > as that's the board I want to buy somiteme (maybe)... I posted two (), but note that the machine was mostly idle but not perfectly at the times. > BTW how are things on the front of fight against noise going? who's > winning, and what is the score? My own lack of knowledge is keeping me from knowing where to start researching :) I don't know what an AC/DC converter looks like or what search terms to use, so I've been slowly asking some hardware-type guys. Next step is to call Logic Supply that sold me the computer, they seem to sell alternative power supplies and silent systems and can probably tell me where to start (and would probably be happy to exchange currency for goods and services). From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 21 09:23:26 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 5DC7616A403 for ; Sat, 21 Oct 2006 09:23:26 +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 F188E43D49 for ; Sat, 21 Oct 2006 09:23:25 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd2mr2so.prod.shaw.ca (pd2mr2so-qfe3.prod.shaw.ca [10.0.141.109]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7H00AUXBF2IFB0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 21 Oct 2006 03:23:26 -0600 (MDT) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd2mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7H00KA5BF1Q2V0@pd2mr2so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sat, 21 Oct 2006 03:23:26 -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 <0J7H00JOFBF1ZEA0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 21 Oct 2006 03:23:25 -0600 (MDT) Date: Sat, 21 Oct 2006 02:23:24 -0700 From: soralx@cydem.org In-reply-to: <44u0241hf4.fsf@be-well.ilk.org> To: freebsd-hardware@freebsd.org Message-id: <200610210223.24178.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <44wt738057.fsf@be-well.ilk.org> <200610150041.59870.soralx@cydem.org> <44u0241hf4.fsf@be-well.ilk.org> 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, 21 Oct 2006 09:23:26 -0000 > Fair enough. Its speed on your own system may matter less to you than > you think, as well. ;-) yeah, but it's that feeling of disappointment: you expect a marvel of hardware crypto engineering, and get something that's totally unexciting :) Still, hardware encryption speed is importand in many cases, and especially for a server. > > just curious whether the speed VIA claims, 25Gbps(!) peak is achievable > Peak rate is a useless number. If it were sustainable, it wouldn't be > quoted as a "peak" rate; and if it's not sustainable, it doesn't > affect the perceived performance. quoting a peak rate is indeed useless, I hoped VIA were nice enough not to employ this type of marketing trick. Supposedly, it it said to be peak because it's only achievable on their fastest 2GHz C7? But the magnitude of numbers from benchmarks suggest otherwise. > No, not at all; I didn't mean to imply I was. I have the slowest (and > lowest powered) Via chips I could get. The ubench numbers are > slightly lower than the Pentium II system it replaced, at a similar > clock rate. Note that I didn't mean the numbers were bad, either... okay, by now we have enough performance data to be able to determine how fast (or slow) these VIA systems are. Merci to all who did the testing. The conclusion is that these VIA chips are by no means champions performance-wise; this fact makes them run cool as well. If performance matters at all, it'd be better to wait until AMD or Intel release low-power versions of their chips (they do have some now, and had them awile ago, but these don't come close to the low power dissipation of VIA's slower CPUs), or pay for performance (electricity and noise). (all this is obvious, of course, but now we have numbers to help determine where that line between fast-and-power-hungry and slow-and-cool is). [SorAlx] ridin' VN1500-B2 From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 21 10:04: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 C3A2516A416 for ; Sat, 21 Oct 2006 10:04:29 +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 EA1AB43D91 for ; Sat, 21 Oct 2006 10:04:19 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd4mr1so.prod.shaw.ca (pd4mr1so-qfe3.prod.shaw.ca [10.0.141.212]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7H00APEDB8IDC0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 21 Oct 2006 04:04:20 -0600 (MDT) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd4mr1so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J7H005OMDB8NHG0@pd4mr1so.prod.shaw.ca> for freebsd-hardware@freebsd.org; Sat, 21 Oct 2006 04:04: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 <0J7H00JGLDB7ZEB0@l-daemon> for freebsd-hardware@freebsd.org; Sat, 21 Oct 2006 04:04:20 -0600 (MDT) Date: Sat, 21 Oct 2006 03:04:17 -0700 From: soralx@cydem.org In-reply-to: <6375852F-8B76-4197-A875-A547B2B21E8B@ketralnis.com> To: freebsd-hardware@freebsd.org Message-id: <200610210304.18013.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <200610161201.k9GC17ol003191@lurza.secnetix.de> <200610202001.38727.soralx@cydem.org> <6375852F-8B76-4197-A875-A547B2B21E8B@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, 21 Oct 2006 10:04:29 -0000 > > the OP has a dual-core board -- I was interested in `ubench` of that, > > as that's the board I want to buy somiteme (maybe)... > I posted two ( 2006-October/003929.html>), but note that the machine was mostly idle > but not perfectly at the times. yes, I saw them; these ain't that bad, actually :) > > BTW how are things on the front of fight against noise going? who's > > winning, and what is the score? > > My own lack of knowledge is keeping me from knowing where to start > researching :) > > I don't know what an AC/DC converter looks like or what search terms > to use, so I've been slowly asking some hardware-type guys. Next step > is to call Logic Supply that sold me the computer, they seem to sell > alternative power supplies and silent systems and can probably tell > me where to start (and would probably be happy to exchange currency > for goods and services). OK, disregard my previous mumbling about AC/DC, and them converters... That's not the simplest solution, and I only suggested it because I was thinking of trying that myself as well. What should work better for you (so that you wouldn't need to mess around with hardware) is a quality fan-less, radiator-more ATX power supply. Now, these are not the easiest things to find nowadays (at least not the lower-power type that you need), but the following might help: http://www.auphanonline.com/articles/view.php?article_id=1457 http://www.overclockercafe.com/Reviews/other_misc/Tt_Fanless_PSU/index.html http://www.theinquirer.net/default.aspx?article=28410 http://www.tomshardware.com/2005/04/01/really_cool_and_quiet_power_supplies/ (notice the old date) and so on; you can google for more keep in mind that your system doesn't consume much power, so ~250W ATX PSU should be enough. [SorAlx] ridin' VN1500-B2