From owner-freebsd-hardware@FreeBSD.ORG Sun Sep 23 03:21:50 2007 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F4B216A417 for ; Sun, 23 Sep 2007 03:21:50 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from mojo.ru (mojo.ru [84.252.152.63]) by mx1.freebsd.org (Postfix) with ESMTP id C426213C457 for ; Sun, 23 Sep 2007 03:21:49 +0000 (UTC) (envelope-from cnst@FreeBSD.org) Received: from [192.168.0.16] (nc-76-4-28-21.dhcp.embarqhsd.net [76.4.28.21]) (authenticated bits=0) by mojo.ru (8.12.11.20060308/8.12.10) with ESMTP id l8N2nY0v016657 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Sep 2007 06:49:41 +0400 Message-ID: <46F5D427.9020504@FreeBSD.org> Date: Sat, 22 Sep 2007 22:49:11 -0400 From: "Constantine A. Murenin" Organization: Google Summer of Code 2007 Student @ The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-gb, en-gb-oed, en, en-us, ru, ru-ru, ru-su MIME-Version: 1.0 To: "Constantine A. Murenin" References: <200709132302.l8DN2Tv5076033@repoman.freebsd.org> <46E9FC0C.70607@FreeBSD.org> In-Reply-To: <46E9FC0C.70607@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@FreeBSD.org, Alexander Leidinger , Shteryana Shopova , freebsd-current@FreeBSD.org, "Constantine A. Murenin" Subject: Re: GSoC2007: cnst-sensors.2007-09-13.patch 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, 23 Sep 2007 03:21:50 -0000 Dear freebsd-{current,hardware}@, Let me a give a few guiding comments for potential testers and integrators of this patch. First of all, let's start with a common pitfall: * You have to update your /boot/device.hints, and then reboot. In no other circumstance will the isa-based lm(4) or it(4) be probed. Manually updating the hints with kenv(1) after the system has already been booted has no effect on the isa modules. * Second, since this patch is not only about the framework, but about some Super I/O Hardware Monitoring drivers too, let me once again reiterate on the popularity of the chips that are supported by the lm(4) and it(4) drivers. I have four boxes here, all run FreeBSD and OpenBSD. Let's see what Super I/O chips they have: * AOpen AX4G-N (845G + Intel Pentium 4 Northwood): Winbond W83627HF-AM * ASUS Terminator C3 (VIA CLE266 + VIA C3 Samuel 2): Winbond W83627THF-A * ASUS V3-P5G965 (G965 + Intel Core 2 Duo Allendale): Winbond W83627DHG-A * PCCHIPS V21G (VIA CN700 + VIA C7 Esther): ITE IT8716F-S Out of the above, Winbond W83627* are supported by lm(4), and ITE IT8716F-S by it(4). (Obviously, the drivers support other chips, too. ;) In general, most boards from Taiwanese manufacturers have either a Winbond or ITE Tech Super I/O chips, supported by lm(4) and it(4) respectively; e.g. if you have a Gigabyte or ASUS mainboard, then the probability of you having one of these chips is quite substantial -- consider testing the patch if you are interested. Supermicro boards also feature Winbond chips quite often -- feel free to test. Intel-branded boards, on the other hand, often use an SMBus-interfaced Hardware Monitoring solution. I have none of those boards, so none of the SMBus drivers were ported to FreeBSD yet. Anyhow, I hope this information helps some potential testers and integrators. ;) Cheers, Constantine. On 13/09/2007 23:12, Constantine A. Murenin wrote: > Dear freebsd-{arch,current,hackers}@, > > On this 256th day of 2007, it is my great pleasure to announce the > completion of my GSoC2007 project on porting the sysctl hardware sensors > framework from OpenBSD to FreeBSD. > > All of the things that were planned to be ported from OpenBSD base > system to FreeBSD have now been ported. > > The userland part of the framework is entirely source-code compatible > with OpenBSD. For example, you can take OpenBSD's stock sensorsd(8), > and it'll compile and work on FreeBSD with no modifications. > > The framework is quite self-contained, so I think it is a safe bet to at > least try to get it into the tree even at this point, when the code > freeze is taking place in preparation for RELENG_7 branching. > > Therefore, I hereby request that this patch be considered for immediate > inclusion into FreeBSD's main CVS repository. > > The complete CVS patch is available from: > http://mojo.ru/us/GSoC2007.cnst-sensors.2007-09-13.patch.gz > > For backup purposes, a copy of this CVS patch is also available in my > perforce branch, although it has tainted $P4$ tags in individual files, > so use perforce as a last resort: > http://p4web.freebsd.org//depot/projects/soc2007/cnst-sensors/cnst-sensors.2007-09-13.patch > > > Exact details on how to apply and test the patch are available in my > LiveJournal, along with certain other comments: > > http://cnst.livejournal.com/38421.html#directions > > If you have an Intel Core 2 processor, or a Winbond or ITE Tech Super > I/O chip on your board, then please test and report back on how your > tests went. > > Best regards, > Constantine Aleksandrovich Murenin, > Google Summer of Code 2007 Student @ The FreeBSD Project. ;) > > > On 13/09/2007 19:02, Constantine A. Murenin wrote: > >> http://perforce.freebsd.org/chv.cgi?CH=126384 >> >> Change 126384 by cnst@dale on 2007/09/13 23:01:55 >> >> On this 256th day of 2007, it is my great pleasure to >> present a feature-complete port of the hardware sensors >> framework from OpenBSD to FreeBSD. >> >> Below is a complete `cvs diff` of cnst-sensors GSoC2007 >> project as of 2007-256. >> >> It includes the following components, listed below in >> the very same order as they are appearing in this diff: >> >> * sample configuration file for sensorsd >> * rc(8) script and glue code for sensorsd(8) >> * sysctl(3) doc fixes for CTL_HW tree >> * sysctl(3) documentation for hardware sensors >> * sysctl(8) documentation for hardware sensors >> * assorted KNF and bug-fixes for sysctl(8) >> * support for the sensor structure for sysctl(8) >> * coretemp(4) documentation >> * it(4) documentation >> * lm(4) documentation >> * rc.conf(5) documentation for starting sensorsd(8) >> * sensor_attach(9) et al documentation >> * coretemp(4) conversion to the hw.sensors framework >> * it(4) isa driver ported from OpenBSD >> * lm(4) isa driver ported from OpenBSD >> * /sys/kern/kern_sensors.c >> o sensor_attach(9) API for drivers to register ksensors >> o sensor_task_register(9) API for the update task >> o sysctl(3) glue code >> o hw.sensors shadow tree for sysctl(8) internal magic >> * assorted KNF and bug-fixes for /sys/kern/kern_sysctl.c >> * it(4) module for testing sensor_attach/detach et al >> * lm(4) module for testing sensor_attach/detach et al >> * >> * assorted bug-fixes and HW_SENSORS definition for >> * sensors display for systat(1), including all documentation >> * sensorsd(8) and all applicable documentation >> >> The userland part of the framework is entirely source-code >> compatible with OpenBSD 4.1, 4.2 and -current as of today. >> >> All sensor readings can be viewed with `sysctl hw.sensors`, >> monitored in semi-realtime with `systat -sensors` and also >> logged with `sensorsd`. Third-party tools, for example a >> plug-in for nagios, are also available. A separate patch >> for ports/sysutils/symon will be provided upon request. >> >> Submitted by: cnst@FreeBSD.org (Constantine A. Murenin) >> Obtained from: generated by sensors.cvsdiff.sh from >> //depot/projects/soc2007/cnst-sensors/ >> Sponsored by: Google Summer of Code 2007 >> >> >> Obtained from: >> http://mojo.ru/us/GSoC2007.cnst-sensors.2007-09-13.patch.gz >> >> Details at: http://cnst.livejournal.com/38421.html >> >> Affected files ... >> >> .. >> //depot/projects/soc2007/cnst-sensors/cnst-sensors.2007-09-13.patch#1 add >> >> Differences ... >> > From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 00:26:34 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5678A16A417 for ; Mon, 24 Sep 2007 00:26:34 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id BE19513C457 for ; Mon, 24 Sep 2007 00:26:33 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so863833ugf for ; Sun, 23 Sep 2007 17:26:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=rXhL5cg+jWBXYvrK9Jqa0bU2LTC0CgyCPVHUzKjYMgs=; b=dum5zeP1rOug3SNbL9Y7UauoQ1QCW04mlScbq/pD9LQp+iGaRwoXvQmd9dPl7eehQPo8ue4pnYoGaSOXPGbbOJQvM00tENqM3onDBpUQSmP9j95gr+3G5FiXMpxN4SgntY3SGJt2so1U5u+Fq4yfVN4jcIANgP+HghOmFBWrcGU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=HXyAAIUXyRsztOgBM3XgwNQgSlmLfVmSyUvA/1QoeSOYu8hyY5C0liqmAcX/gmTuTZdsio2y63IcaaUJ4fenlIQeKyMIk1amj100tTMBiAacEnSX8OipE1BitUAVGN5CiluPl86xhGErE8uObPbuemIEAdcEbS0c4lokWJc4Lcc= Received: by 10.67.119.15 with SMTP id w15mr7121808ugm.1190591843754; Sun, 23 Sep 2007 16:57:23 -0700 (PDT) Received: by 10.66.237.15 with HTTP; Sun, 23 Sep 2007 16:57:23 -0700 (PDT) Message-ID: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> Date: Mon, 24 Sep 2007 00:57:23 +0100 From: Chris To: freebsd-hardware@freebsd.org, "FreeBSD Stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: nfe driver 6.2 stable 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, 24 Sep 2007 00:26:34 -0000 Hi I installed the following driver. http://www.f.csce.kyushu-u.ac.jp/~shigeaki//software/freebsd-nfe.html Before I had the nve driver which was unstable on this server and on a prior server in both cases causing either spontaneous reboot or just a crash when under load. So far touchwood the nfe driver has stayed up and running at almost 3 days uptime and has had some stress. I know the driver supports device polling which I have chosen not to use yet as I wanted to see initially if it was more stable in its default mode. But what I want to know is the following if possible please. My ifconfig output below. nfe0: flags=8843 mtu 1500 options=8 inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x ether x media: Ethernet autoselect (1000baseTX ) status: active 1 - is there a man page for nfe anywhere? 2 - does it support hardware checksum I remember reading it does but from ifconfig output it appears to not be in use so if it does support it how do I enable it? 3 - same with TOS? 4 - how do I enable jumbo frames if it supports it? 5 - is it safe to use with zero copy sockets? 6 - I currently have both net.isr.direct and mpsafenet disabled is this driver safe to use on them? Thanks Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 02:17:44 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BDEB16A417 for ; Mon, 24 Sep 2007 02:17:44 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4B1B113C465 for ; Mon, 24 Sep 2007 02:17:44 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id DD24D1CC02B; Sun, 23 Sep 2007 19:01:16 -0700 (PDT) Date: Sun, 23 Sep 2007 19:01:16 -0700 From: Jeremy Chadwick To: Chris Message-ID: <20070924020116.GA36909@eos.sc1.parodius.com> Mail-Followup-To: Chris , freebsd-hardware@freebsd.org, FreeBSD Stable References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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, 24 Sep 2007 02:17:44 -0000 On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > nfe0: flags=8843 mtu 1500 > options=8 > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > ether x > media: Ethernet autoselect (1000baseTX ) > status: active > > 1 - is there a man page for nfe anywhere? Closest thing I can find would be the manpage from -CURRENT's nfe(4), which is supposedly the same code. http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > 2 - does it support hardware checksum I remember reading it does but > from ifconfig output it appears to not be in use so if it does support > it how do I enable it? It does support it, but I don't know the circumstances surrounding when it gets enabled. That is to say, it's known that some versions of the chip (and/or associated PHY) have bugs, so possibly hardware checksum offloading is known to be broken on the system you're on. Taken from my 7-CURRENT box at home (Asus A8N-E, nForce 4-based): nfe0: flags=8843 metric 0 mtu 1500 options=10b ether 00:15:f2:17:30:e9 inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet 1000baseTX status: active I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig line. > 3 - same with TOS? TOS (type-of-service) or TSO? If TSO, see above ifconfig. > 4 - how do I enable jumbo frames if it supports it? You should take a bit more itme to read the webpage you obtained the driver from. I see these on the page: 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle Tx/Rx checksum offload settings with ifconfig. 2006/08/11 Added support for jumbo frame capability. yongari@ (Pyun YongHyeon) should be able to provide additional help with both. > 5 - is it safe to use with zero copy sockets? No idea. > 6 - I currently have both net.isr.direct and mpsafenet disabled is > this driver safe to use on them? No idea. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 09:35:30 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DB4116A421; Mon, 24 Sep 2007 09:35:30 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 3B1E313C458; Mon, 24 Sep 2007 09:35:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F784E1.1080000@FreeBSD.org> Date: Mon, 24 Sep 2007 11:35:29 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Benjie Chen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load 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, 24 Sep 2007 09:35:30 -0000 Benjie Chen wrote: > Hi FreeBSD hackers and engineers, > > I am experiencing a kernel panic that comes on when my new PowerEdge 1950 > FreeBSD 6.2 setup is under a certain stress load. I've emailed a few people > on the list who have given me useful comments, some of which I am still > following up. But I wanted to send a general cry for help to see if there > are more knowledge out there about this problem. > > FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver (PERC5i). 4GB > RAM. I am currently running i386, and not amd64, due to various reasons. > > I've ran exhaustively memory tests, disk tests, and network tests and cannot > produce the kernel panic. I worked with Dell support to run memory test 1 > DIMM at a time and cannot find any problem. With 1 DIMM at a time, I could > still get the kernel panic under my work load. > > My work load is heavily hitting a web site running on the machine and > requiring the web service to do MySQL requests. On the side, I am running a > bunch of scripts that mostly read from the MySQL database but also write to > it occasionally. Not memory intensive -- still have usually about 1GB free > memory, but fairly disk intensive. I don't get disk errors. Anywhere from > between 10 minutes to 4 or 5 hours into the test, I get the kernel panic. > Again, still no disk errors. I turned off soft-update, still happens. > > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin > c066c7b4 T _mtx_lock_spin > c066c85c T _mtx_unlock_sleep > > So this could mean that independent stress tests will not result in panic if > there aren't enough concurrency to cause the problem. > > There are a few other complaints about kernel panics at the same IP on the > web (google 0xc066c731)... I was wondering if anyone had dealt with this > before and if there are any work arounds? The IP is meaningless, it changes each time you compile your kernel. Unfortunately even knowing that it is in that symbol is nearly meaningless, because it doesn't provide enough information (only that your panic involved a spin mutex somehow). Please read the chapter on kernel debugging in the developers handbook and file a PR containing enough information for a developer to investigate the problem. Kris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 11:06:53 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6197716A419 for ; Mon, 24 Sep 2007 11:06:51 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5A5F313C45B for ; Mon, 24 Sep 2007 11:06:51 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1IZlkM-0001KR-V4 for freebsd-hardware@freebsd.org; Mon, 24 Sep 2007 11:05:02 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 11:05:02 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 11:05:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Mon, 24 Sep 2007 12:50:54 +0200 Lines: 38 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigD1A7E375A316CC6D39AE1BFB" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.12 (X11/20060911) In-Reply-To: X-Enigmail-Version: 0.94.4.0 Sender: news Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load 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, 24 Sep 2007 11:06:53 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD1A7E375A316CC6D39AE1BFB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Benjie Chen wrote: > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spi= n > c066c7b4 T _mtx_lock_spin > c066c85c T _mtx_unlock_sleep >=20 > So this could mean that independent stress tests will not result in pan= ic if > there aren't enough concurrency to cause the problem. When you get a kernelbacktrace, see if it's the same as the one=20 mentioned here: http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.= html --------------enigD1A7E375A316CC6D39AE1BFB 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 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG95aPldnAQVacBcgRAwHVAJ9wHslgdVRAY0/2fNb4CKq3o9S+ywCgy2qi 0b6j5dYUJplPbWuBHunb7vY= =er0K -----END PGP SIGNATURE----- --------------enigD1A7E375A316CC6D39AE1BFB-- From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 15:42:41 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0C1916A419 for ; Mon, 24 Sep 2007 15:42:41 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 4A6CB13C45A for ; Mon, 24 Sep 2007 15:42:41 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by wa-out-1112.google.com with SMTP id k17so2088930waf for ; Mon, 24 Sep 2007 08:42:40 -0700 (PDT) Received: by 10.115.17.1 with SMTP id u1mr728887wai.1190648560551; Mon, 24 Sep 2007 08:42:40 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Mon, 24 Sep 2007 08:42:40 -0700 (PDT) Message-ID: Date: Mon, 24 Sep 2007 11:42:40 -0400 From: "Benjie Chen" To: "Ivan Voras" In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load 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, 24 Sep 2007 15:42:41 -0000 Ivan and Kris, I will try to get a kernel trace -- it may not happen for awhile since I am not in the office and working remotely for awhile so it may not be easy to get a trace... but I will check. It looks like the problem reported by that link, and some of the links from there though... Benjie On 9/24/07, Ivan Voras wrote: > > Benjie Chen wrote: > > > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin > > c066c7b4 T _mtx_lock_spin > > c066c85c T _mtx_unlock_sleep > > > > So this could mean that independent stress tests will not result in > panic if > > there aren't enough concurrency to cause the problem. > > When you get a kernelbacktrace, see if it's the same as the one > mentioned here: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html > > > > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 15:44:11 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB5E516A421 for ; Mon, 24 Sep 2007 15:44:10 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 785CB13C461 for ; Mon, 24 Sep 2007 15:44:10 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so956319ugf for ; Mon, 24 Sep 2007 08:44:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=VJbGrpp2mUj7vbHgqlxn1kQDUyGd8HRERkdu04RpQ5E=; b=fcIFS0NooTCZ/a3h33gjBcLmVgavv2RkA+lplMfmOClOo2XYo66ZuSuW1m27cNwb8pPk7QKYTo7JhXF6WTtz24aUroL8VFu0q0kOsrj3hUH2W9RxGMJ/ttaiDiWot7hYINQrsJFqaWNS+pC5nj1GTwLcXCNqO0bD/RFeeW9KZ/c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hQDijy4iwKu11NDQPIiuVyPKLxuJ5YrQWBDwsXqeAKm2xXgdpWytyDs8NwrxqAORhUNHeHqbYeVmqCLWMcHSp3Z9CrwhAdzfEgcFRmDsTFMJiQxU95GK51/dIy9q3PBivsEe3geiKTiHDpEAN/ThF3/IhGBySkcJ2ASB9MLs3CM= Received: by 10.67.21.11 with SMTP id y11mr7973025ugi.1190648649094; Mon, 24 Sep 2007 08:44:09 -0700 (PDT) Received: by 10.66.237.15 with HTTP; Mon, 24 Sep 2007 08:44:09 -0700 (PDT) Message-ID: <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> Date: Mon, 24 Sep 2007 16:44:09 +0100 From: Chris To: Chris , freebsd-hardware@freebsd.org, "FreeBSD Stable" In-Reply-To: <20070924020116.GA36909@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> Cc: Subject: Re: nfe driver 6.2 stable 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, 24 Sep 2007 15:44:11 -0000 On 24/09/2007, Jeremy Chadwick wrote: > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > nfe0: flags=8843 mtu 1500 > > options=8 > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > ether x > > media: Ethernet autoselect (1000baseTX ) > > status: active > > > > 1 - is there a man page for nfe anywhere? > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > which is supposedly the same code. > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > 2 - does it support hardware checksum I remember reading it does but > > from ifconfig output it appears to not be in use so if it does support > > it how do I enable it? > > It does support it, but I don't know the circumstances surrounding when > it gets enabled. That is to say, it's known that some versions of the > chip (and/or associated PHY) have bugs, so possibly hardware checksum > offloading is known to be broken on the system you're on. Taken from my > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > nfe0: flags=8843 metric 0 mtu 1500 > options=10b > ether 00:15:f2:17:30:e9 > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet 1000baseTX > status: active > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > line. > > > 3 - same with TOS? > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > 4 - how do I enable jumbo frames if it supports it? > > You should take a bit more itme to read the webpage you obtained the > driver from. I see these on the page: > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > Tx/Rx checksum offload settings with ifconfig. > 2006/08/11 Added support for jumbo frame capability. > > yongari@ (Pyun YongHyeon) should be able to provide additional help > with both. > > > 5 - is it safe to use with zero copy sockets? > > No idea. > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > this driver safe to use on them? > > No idea. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > Thanks yes I meant TSO sorry, I would guess with the checksum either the 6.x driver is older and not fully implemented yet, the 6.x driver does need more patches for certian chipsets so would indicate its older then the CURRENT driver. Or as you said my chipset is known to be unstable with the hardware checksums. The card is more stable when using nve driver no crashes still but the performance is around the same maxing out at around 200mbit. I was expecting nearer 400-500mbit. e1000phy0: on miibus0 Is the line from dmesg, I believe in CURRENT mpsafe is always on regardless so if you have no problems then its a good sign and I will reenable mpsafe networking (default). Thanks really appreciated. Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 15:45:38 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3736616A41A for ; Mon, 24 Sep 2007 15:45:38 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id C888C13C458 for ; Mon, 24 Sep 2007 15:45:37 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so956627ugf for ; Mon, 24 Sep 2007 08:45:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=N7Ht4prgjE+3rzs0ZuoZfQqd5sofkD2Ph5nSB1b/vWo=; b=MXvMH5RQcBbLvrqeoE3SUnvBliRci1hNaEhBJAiYaB6YFSD1KcOdlvLIHlc/rx32JocDF1qGtCjlvC5bIaPlGUOWoNgQ+38NdeUFkBKhs8TsuysWjYoCz+4CasOEeC2BUbCPdA9dztVxEHLUx0bFQ0NFNCMfuVlRpY81MRtyXKU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aArA2sacL4un8x9QQfgpkeDEpYboaAyuXeP+X6ip/kfMi+XM+AXYk9lsTKmSBQcDU0F9W5jcUXPx4g1A+BnNqqabIsTfylO4ThIHrHB49klSSLaAut2e4I6wgKEoHRUVyXHB98vhvigLE30CHj1+D+wMCr9tbOzA8KPZUG510xk= Received: by 10.66.221.5 with SMTP id t5mr4267778ugg.1190648736392; Mon, 24 Sep 2007 08:45:36 -0700 (PDT) Received: by 10.66.237.15 with HTTP; Mon, 24 Sep 2007 08:45:36 -0700 (PDT) Message-ID: <3aaaa3a0709240845q37e3b7c8g84239529b4136ce2@mail.gmail.com> Date: Mon, 24 Sep 2007 16:45:36 +0100 From: Chris To: Chris , freebsd-hardware@freebsd.org, "FreeBSD Stable" In-Reply-To: <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> Cc: Subject: Re: nfe driver 6.2 stable 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, 24 Sep 2007 15:45:38 -0000 On 24/09/2007, Chris wrote: > On 24/09/2007, Jeremy Chadwick wrote: > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > nfe0: flags=8843 mtu 1500 > > > options=8 > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > ether x > > > media: Ethernet autoselect (1000baseTX ) > > > status: active > > > > > > 1 - is there a man page for nfe anywhere? > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > which is supposedly the same code. > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > 2 - does it support hardware checksum I remember reading it does but > > > from ifconfig output it appears to not be in use so if it does support > > > it how do I enable it? > > > > It does support it, but I don't know the circumstances surrounding when > > it gets enabled. That is to say, it's known that some versions of the > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > offloading is known to be broken on the system you're on. Taken from my > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=10b > > ether 00:15:f2:17:30:e9 > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet 1000baseTX > > status: active > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > line. > > > > > 3 - same with TOS? > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > You should take a bit more itme to read the webpage you obtained the > > driver from. I see these on the page: > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > Tx/Rx checksum offload settings with ifconfig. > > 2006/08/11 Added support for jumbo frame capability. > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > with both. > > > > > 5 - is it safe to use with zero copy sockets? > > > > No idea. > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > this driver safe to use on them? > > > > No idea. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > Thanks yes I meant TSO sorry, I would guess with the checksum either > the 6.x driver is older and not fully implemented yet, the 6.x driver > does need more patches for certian chipsets so would indicate its > older then the CURRENT driver. Or as you said my chipset is known to > be unstable with the hardware checksums. > > The card is more stable when using nve driver no crashes still but the > performance is around the same maxing out at around 200mbit. I was > expecting nearer 400-500mbit. > > e1000phy0: on miibus0 > > Is the line from dmesg, I believe in CURRENT mpsafe is always on > regardless so if you have no problems then its a good sign and I will > reenable mpsafe networking (default). > > Thanks really appreciated. > > Chris > Sorry I meant the card is more stable with this nfe then the nve driver. Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 15:49:27 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 849FF16A418 for ; Mon, 24 Sep 2007 15:49:27 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 25B2F13C455 for ; Mon, 24 Sep 2007 15:49:26 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so957403ugf for ; Mon, 24 Sep 2007 08:49:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=3a11fUxx9mLmjO3NWxeqdYHDLwNZwn2ijtLhQCKHqMM=; b=g37m/daTuUulZsVtomXjWiEu8UiZVmxLn3jJwuLkyRvZ06EqEnXPRroYJETmK+KCXcY3IObRgD+cRzDtCahB2yIscMGdrH1Hx64dVPaY3+y2WJXsJ//eHfF7fvbFnq8yJoom1FZjCa4g6ciCl8d3Lalu0O8Aq98u3UFtdoKHEB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pVySX4yk4VgrV4Ede+R545VkELft007QD5NwihWxcPR8dhVOhB5d+yBpXeGUGlpUf2iHgKFf7yqQ6lxZtNyL+jzAhNGgam6aFPoqSWQhuFotmUd4xuSaXwV1j7RmhAB4EbzmLuKZ64JQvzbDf8r/cVVYGVlQ8q2CR1ZOK92hsb4= Received: by 10.66.249.14 with SMTP id w14mr4274741ugh.1190648965396; Mon, 24 Sep 2007 08:49:25 -0700 (PDT) Received: by 10.66.237.15 with HTTP; Mon, 24 Sep 2007 08:49:25 -0700 (PDT) Message-ID: <3aaaa3a0709240849p4ce49c75h4316c1abc56aa68e@mail.gmail.com> Date: Mon, 24 Sep 2007 16:49:25 +0100 From: Chris To: Chris , freebsd-hardware@freebsd.org, "FreeBSD Stable" In-Reply-To: <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> Cc: Subject: Re: nfe driver 6.2 stable 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, 24 Sep 2007 15:49:27 -0000 On 24/09/2007, Chris wrote: > On 24/09/2007, Jeremy Chadwick wrote: > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > nfe0: flags=8843 mtu 1500 > > > options=8 > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > ether x > > > media: Ethernet autoselect (1000baseTX ) > > > status: active > > > > > > 1 - is there a man page for nfe anywhere? > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > which is supposedly the same code. > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > 2 - does it support hardware checksum I remember reading it does but > > > from ifconfig output it appears to not be in use so if it does support > > > it how do I enable it? > > > > It does support it, but I don't know the circumstances surrounding when > > it gets enabled. That is to say, it's known that some versions of the > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > offloading is known to be broken on the system you're on. Taken from my > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=10b > > ether 00:15:f2:17:30:e9 > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet 1000baseTX > > status: active > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > line. > > > > > 3 - same with TOS? > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > You should take a bit more itme to read the webpage you obtained the > > driver from. I see these on the page: > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > Tx/Rx checksum offload settings with ifconfig. > > 2006/08/11 Added support for jumbo frame capability. > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > with both. > > > > > 5 - is it safe to use with zero copy sockets? > > > > No idea. > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > this driver safe to use on them? > > > > No idea. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > Thanks yes I meant TSO sorry, I would guess with the checksum either > the 6.x driver is older and not fully implemented yet, the 6.x driver > does need more patches for certian chipsets so would indicate its > older then the CURRENT driver. Or as you said my chipset is known to > be unstable with the hardware checksums. > > The card is more stable when using nve driver no crashes still but the > performance is around the same maxing out at around 200mbit. I was > expecting nearer 400-500mbit. > > e1000phy0: on miibus0 > > Is the line from dmesg, I believe in CURRENT mpsafe is always on > regardless so if you have no problems then its a good sign and I will > reenable mpsafe networking (default). > > Thanks really appreciated. > > Chris > More info its a NVIDIA nForce 430 MCP13 adaptor from dmesg. 2006/08/17 Provided a patch to support Marvell 88E1116 PHY In the changelog after they added hardware checksum the changelog says MCP65 had it removed from driver due to no support so I may contact the driver author on this to see what he says. Chris Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 16:17:42 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B82916A418 for ; Mon, 24 Sep 2007 16:17:42 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 3265613C447 for ; Mon, 24 Sep 2007 16:17:42 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so963160ugf for ; Mon, 24 Sep 2007 09:17:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=z6J9NhGY45dFiGz3SstSprnAcwguaZ7DAWICjXF+fBA=; b=sjbNfOtgYpOBBjejJOBk1dDo+Ywv/oz7e0qQxwo0/zK1foLXOP8DNuq+BYkq8BMxTThAraXOZFx4/bPCcO/dUDX0k3Pyi+tY84hfP3UBLoUVpcvAPW0bqTHSdd2klcLIo3986KKRaH6ZiY79VOPWv0zcDs7az20IZEal6dQePV0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=t38QmAhgLQraDm3At7pNoX+6l6pM2T4u/aIL61hKxBki+gsVC40iNNI9zkgWgq/jWl0vc51Vf0vADe4M7wZ8ObP4ZybBGY6tmwNFPM9UD4YdauDn5upr1wggi1yD27ChxOXXLvOpk8vVho7xGnG3NO/iy8cWKzNaAudQkJS+pUs= Received: by 10.66.219.11 with SMTP id r11mr7984058ugg.1190650660492; Mon, 24 Sep 2007 09:17:40 -0700 (PDT) Received: by 10.66.237.15 with HTTP; Mon, 24 Sep 2007 09:17:40 -0700 (PDT) Message-ID: <3aaaa3a0709240917p2776136fn50eb2d5bbbaeebf2@mail.gmail.com> Date: Mon, 24 Sep 2007 17:17:40 +0100 From: Chris To: Chris , freebsd-hardware@freebsd.org, "FreeBSD Stable" In-Reply-To: <20070924020116.GA36909@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> Cc: Subject: Re: nfe driver 6.2 stable 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, 24 Sep 2007 16:17:42 -0000 On 24/09/2007, Jeremy Chadwick wrote: > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > nfe0: flags=8843 mtu 1500 > > options=8 > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > ether x > > media: Ethernet autoselect (1000baseTX ) > > status: active > > > > 1 - is there a man page for nfe anywhere? > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > which is supposedly the same code. > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > 2 - does it support hardware checksum I remember reading it does but > > from ifconfig output it appears to not be in use so if it does support > > it how do I enable it? > > It does support it, but I don't know the circumstances surrounding when > it gets enabled. That is to say, it's known that some versions of the > chip (and/or associated PHY) have bugs, so possibly hardware checksum > offloading is known to be broken on the system you're on. Taken from my > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > nfe0: flags=8843 metric 0 mtu 1500 > options=10b > ether 00:15:f2:17:30:e9 > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet 1000baseTX > status: active > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > line. > > > 3 - same with TOS? > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > 4 - how do I enable jumbo frames if it supports it? > > You should take a bit more itme to read the webpage you obtained the > driver from. I see these on the page: > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > Tx/Rx checksum offload settings with ifconfig. > 2006/08/11 Added support for jumbo frame capability. > > yongari@ (Pyun YongHyeon) should be able to provide additional help > with both. > > > 5 - is it safe to use with zero copy sockets? > > No idea. > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > this driver safe to use on them? > > No idea. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > Ok to recap I have nforce 430 MCP13 I checked the src and current and 6.2-stable driver I am using are the same version number but my driver src has this added above tunables. /* definitions for backporting RELENG-6 */ #ifndef IFCAP_TSO4 #define IFCAP_TSO4 0 #define CSUM_TSO 0 #endif #ifndef VLAN_CAPABILITIES #define VLAN_CAPABILITIES(x) #endif #ifndef IFCAP_VLAN_HWCSUM #define IFCAP_VLAN_HWCSUM 0 #endif I am guessing If I set the values to 1 I get the features but would like someone to confirm this for me before I try it thanks. I only have remote access so if it stops the card working I lose access to the box. Chris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 19:15:46 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 437BB16A418; Mon, 24 Sep 2007 19:15:46 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFC713C45B; Mon, 24 Sep 2007 19:15:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80CE0.6010609@FreeBSD.org> Date: Mon, 24 Sep 2007 21:15:44 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load 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, 24 Sep 2007 19:15:46 -0000 Ivan Voras wrote: > Benjie Chen wrote: > >> Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin >> c066c7b4 T _mtx_lock_spin >> c066c85c T _mtx_unlock_sleep >> >> So this could mean that independent stress tests will not result in >> panic if >> there aren't enough concurrency to cause the problem. > > When you get a kernelbacktrace, see if it's the same as the one > mentioned here: > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html Surely it cannot be since it involves a different function ;-) Kris From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 19:24:30 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1329D16A41B for ; Mon, 24 Sep 2007 19:24:30 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id E36DB13C48E for ; Mon, 24 Sep 2007 19:24:29 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1341364rvb for ; Mon, 24 Sep 2007 12:24:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Qt6y2GCW1z1uSO+jacwVctVad8qdG+Lrx6YGBM0PS7M=; b=RwTOfuFp10nzjgcHTJhtzV0bFTNFONMInvl78/BvFyT+ppzkGJIozz9K3uieeuCoIIYVpLd41H+dZmnuGQedOjkyqqqiiHcjPQjyH/Eq7u7S8EVeXHElR9SMbJVSZ+0o8PYxdvoJwd5M+y90xt3pb7GG/5W/wAXng8U4GHihOnw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=N5zLUQ/wMR0NBFPerw7c2jkpVWdtYoRvIiG2x9KWOgEaRJ1hz+PmkD7gm852NK9fLhwu5mGp+xwOShiT6KwQPcs/QuPt2TVcocR6X5tfI8wgG7ubbUxMF02LxUvg3/gL8zttuyvXV3OZDCAtDU+yh2Z3umVq42gtQAZ0EacCCrM= Received: by 10.140.250.14 with SMTP id x14mr1739123rvh.1190661481178; Mon, 24 Sep 2007 12:18:01 -0700 (PDT) Received: by 10.141.159.3 with HTTP; Mon, 24 Sep 2007 12:18:01 -0700 (PDT) Message-ID: <9bbcef730709241218u20d1824cn20c72d0863f6366e@mail.gmail.com> Date: Mon, 24 Sep 2007 21:18:01 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Kris Kennaway" In-Reply-To: <46F80CE0.6010609@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F80CE0.6010609@FreeBSD.org> X-Google-Sender-Auth: adfe825d10757db5 Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load 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, 24 Sep 2007 19:24:30 -0000 On 24/09/2007, Kris Kennaway wrote: > Ivan Voras wrote: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html > > Surely it cannot be since it involves a different function ;-) :) When all you have is a hammer... From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 19:36:57 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6131B16A418 for ; Mon, 24 Sep 2007 19:36:57 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by mx1.freebsd.org (Postfix) with ESMTP id 3AB0D13C461 for ; Mon, 24 Sep 2007 19:36:57 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1344060rvb for ; Mon, 24 Sep 2007 12:36:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=gEa2/4tUSTaYto9mmtyQ0XFkxMpmYPQ+DYlvscpFQmA=; b=sYyWC7cQtROUU7Tef/HcYgho1fl4eY5puxBHb3DKWpJst0tJtcQOD+nLYGfCNf70BfayvrgcjEHWw3XlZeRBmzH/RkF+eIbDj8HD2UFIxPCRAay9sQd17l67uptnPghsbLFOGdvQIkke5XxQWvYPr9DvsIZUe1mD6lqUUBcytP0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=kBGJsqheo2CwnLfkP9oMHPUTdtztHtKiOxgNU6hisD1P8wiRvmbIiHg9hdususfFsaonZdQpLWH0QSANU9FhAx4+4UlkcCKJrP6LCyCkOZlIt2osWJsihJguOXAC233PljMs23eN78UyE32JKDnyx+ZRZqIY9nn6f0q64PJ0YIo= Received: by 10.140.177.15 with SMTP id z15mr1738425rve.1190661075563; Mon, 24 Sep 2007 12:11:15 -0700 (PDT) Received: by 10.141.159.3 with HTTP; Mon, 24 Sep 2007 12:11:15 -0700 (PDT) Message-ID: <9bbcef730709241211o479e3e5dwf64382596c837dfb@mail.gmail.com> Date: Mon, 24 Sep 2007 21:11:15 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Benjie Chen" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: d92aa624b22c440d Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load 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, 24 Sep 2007 19:36:57 -0000 On 24/09/2007, Benjie Chen wrote: > Ivan and Kris, > > I will try to get a kernel trace -- it may not happen for awhile since I am > not in the office and working remotely for awhile so it may not be easy to > get a trace... but I will check. It's fairly easy: 1) add lines like the following in rc.conf: dumpdev="/dev/amrd0s1b" dumpdir="/storage1/crashdumps" (dumpdev is your swap partition, which must be larger than your RAM, dumpdir is where the crash dumps will be saved, also needs to be larger than RAM) 2) add these lines to sysctl.conf: debug.debugger_on_panic=0 debug.trace_on_panic=1 (These will cause the panic message and backtrace to be automatically recorded in the message buffer saved to the kernel crash dump. If not told otherwise, the machine will then reboot and at the next boot generate a crash dump in your dumpdir. When you get the kernel crash dump, run "kgdb vmcore.0 /boot/kernel/kernel" as root and then you can inspect the trace, core dump, etc. You don't need any special knowledge of (k)gdb for this. The one useful command to you may be "bt" - generate a backtrace). > It looks like the problem reported by that link, and some of the links from > there though... I'm trying to solve that one with Craig Rodrigues. So far it's been without success but we know where the problem is. From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 26 04:50:24 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D70416A418 for ; Wed, 26 Sep 2007 04:50:24 +0000 (UTC) (envelope-from bigone@qon.lao.net) Received: from omta08.mta.everyone.net (sitemail3.everyone.net [216.200.145.37]) by mx1.freebsd.org (Postfix) with ESMTP id 77FBF13C468 for ; Wed, 26 Sep 2007 04:50:24 +0000 (UTC) (envelope-from bigone@qon.lao.net) Received: from dm25.mta.everyone.net (bigiplb-dsnat [172.16.0.19]) by omta08.mta.everyone.net (Postfix) with ESMTP id 2F363402AD for ; Tue, 25 Sep 2007 21:50:24 -0700 (PDT) X-Eon-Dm: dm25 Received: by resin11.mta.everyone.net (EON-PICKUP) id resin11.46f93be9.770f; Tue, 25 Sep 2007 21:50:23 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Message-Id: <20070925215023.3D913D4E@resin11.mta.everyone.net> Date: Tue, 25 Sep 2007 21:50:23 -0700 From: "big one" To: X-Eon-Sig: AQKX+3NG+eUPApPhRAEAAAAB,555202586c439675db38caebb2b7612a X-Originating-Ip: [202.73.117.35] Subject: Porting FreeBSD to OLPC XO Laptops X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bigone@qon.lao.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 04:50:24 -0000 OLPC (One Laptop Per Child) project had announced "Buy 2 Get 1" (G1G1) for public. One XO laptop will be sent to the buyer and one laptop will be sent to a child in a poor, developing country. The XO laptops use AMD Geode CPU, but without standard PC BIOS and without VGA/EGA/CGA. The XO laptops do not support off-the-shelf/unmodified Linux. Linux run on top of XO with modified/patched kernel. Is it possible to port FreeBSD for ia32 to OLPC XO laptops? Who can do this project? Thank you. _____________________________________________________________ = You want FREE web-based email ? = You want your own @qon.lao.net address?? = Then you want LaoNet's WebMail ! = Get it at http://webmail.lao.net !! From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 26 04:51:29 2007 Return-Path: Delivered-To: Freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC5E416A41A for ; Wed, 26 Sep 2007 04:51:29 +0000 (UTC) (envelope-from bigone@qon.lao.net) Received: from omta06.mta.everyone.net (sitemail3.everyone.net [216.200.145.37]) by mx1.freebsd.org (Postfix) with ESMTP id D8B1B13C448 for ; Wed, 26 Sep 2007 04:51:29 +0000 (UTC) (envelope-from bigone@qon.lao.net) Received: from dm23.mta.everyone.net (bigiplb-dsnat [172.16.0.19]) by omta06.mta.everyone.net (Postfix) with ESMTP id F36481A203 for ; Tue, 25 Sep 2007 21:07:59 -0700 (PDT) X-Eon-Dm: dm23 Received: by resin17.mta.everyone.net (EON-PICKUP) id resin17.46f563c7.12db4; Tue, 25 Sep 2007 21:07:59 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Message-Id: <20070925210759.2E8C491E@resin17.mta.everyone.net> Date: Tue, 25 Sep 2007 21:07:59 -0700 From: "big one" To: X-Eon-Sig: AQKX+3NG+dsftdMKWQEAAAAB,e1867f3af99f25c8712d38b3ea8635d5 X-Originating-Ip: [202.73.117.35] Cc: Subject: Porting FreeBSD to OLPC XO AMD Geode laptops X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bigone@qon.lao.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 04:51:30 -0000 OLPC (One Laptop Per Child) project had announced "Buy 2 Get 1" (G1G1) for public. One XO laptop will be sent to the buyer and one laptop will be sent to a child in a poor, developing country. The XO laptops use AMD Geode CPU, but without standard PC BIOS and without VGA/EGA/CGA. The XO laptops do not support off-the-shelf/unmodified Linux. Linux run on top of XO with modified/patched kernel. Is it possible to port FreeBSD for ia32 to OLPC XO laptops? Who can do this project? Thank you. _____________________________________________________________ = You want FREE web-based email ? = You want your own @qon.lao.net address?? = Then you want LaoNet's WebMail ! = Get it at http://webmail.lao.net !! From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 26 16:06:25 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A687516A41B for ; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id AA19313C461 for ; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 1AF3A1A4D93; Wed, 26 Sep 2007 08:48:14 -0700 (PDT) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 26 Sep 2007 10:10:25 -0400 User-Agent: KMail/1.9.7 References: <20070829174236.6c33ccfc@n2.lands.raad> <20070904215058.GA85717@cons.org> In-Reply-To: <20070904215058.GA85717@cons.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709261010.26433.jhb@freebsd.org> Cc: err , Martin Cracauer Subject: Re: 8GB RAM: PAE or not PAE? 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, 26 Sep 2007 16:06:25 -0000 On Tuesday 04 September 2007 05:50:58 pm Martin Cracauer wrote: > err wrote on Wed, Aug 29, 2007 at 05:42:36PM +0200: > > Hi > > > > I have an HP DL380 quad core with 8GB of RAM and SAS disks in RAID, with freebsd 6 STABLE on it. > > > > Everything works fine, except for the RAM addressing problem: freebsd sees only 4GB. > > I know it have been discussed, but it could be a problem to me for running a 64bit compiled system; what is the stability of a kernel compiled with the PAE option? > > > > I've a kernel with no modules, and before trying PAE I would know for other people experiences... > > In particular I'm interested in the behavior of ciss, bce, em and usb stuff, and application like Perl, Ruby, PHP 5, MySQL server, heavy MAWK and bzip2 load. > > Usb? Ugh. > > But last time I ran i386+PAE was 6.2-beta and it ran fine with 8 GB > and 8 processors, well enough to complete a complex benchmark suite. > I wouldn't know about USB and other non-primary drivers. > > You should also be able to run a 100% 32 bit userland with a 64 bit > kernel. I'll have to do that next weekend or whenever I find time, > for other reasons. You can't quite do this because some system binaries like ps(1), netstat(1), etc. (just about anything using libkvm) are very intimately involved with the running kernel, so you need 64-bit versions of those binaries. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 26 16:06:25 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C731416A46E for ; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D0AB913C494 for ; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id D82991A4D7C; Wed, 26 Sep 2007 08:48:14 -0700 (PDT) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 26 Sep 2007 10:13:56 -0400 User-Agent: KMail/1.9.7 References: <20070913163122.GB75019@jobbicycle.corp.yahoo.com> In-Reply-To: <20070913163122.GB75019@jobbicycle.corp.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709261013.56774.jhb@freebsd.org> Cc: brad clawsie Subject: Re: problems mounting ipod nano 3g, how can i help? 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, 26 Sep 2007 16:06:25 -0000 On Thursday 13 September 2007 12:31:22 pm brad clawsie wrote: > i hope this is the right list > > i am on 6.2, last makeworld april 8 > > in the past i have never had problems mounting my first gen ipod > shuffle (usb flash) on freebsd using mount_msdosfs > > last night i brought home a new ipod nano 3g (4gb flash usb) and found > that mount_msdosfs could not mount the drive (yes, it is a 'windows' > ipod). > > camcontrol recognizes the device as an ipod, and can perform functions > like eject on it correctly > > mount gives me 'incorrect superblock' errors. ubuntu users are also > reporting badness with this device, but i believe they are capable of > mounting it. i can't even do that. > > how can i help freebsd people address this issue? are there further > diagnostics i can run that would be beneficial? i am willing to do > anything non-destructive. Put GEOM_APPLE in your kernel (or kldload the equivalent module) and mount the first partition. I had to do that with my iPod when it was setup as a "Windows" iPod. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 26 16:06:25 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7C6916A417 for ; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E0CDC13C4A3 for ; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 4981F1A3C1A; Wed, 26 Sep 2007 08:48:13 -0700 (PDT) From: John Baldwin To: freebsd-hardware@freebsd.org, jgrosch@juniper.net Date: Wed, 26 Sep 2007 10:09:01 -0400 User-Agent: KMail/1.9.7 References: <20070829174236.6c33ccfc@n2.lands.raad> <20070829205110.GA68658@juniper.net> In-Reply-To: <20070829205110.GA68658@juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709261009.01555.jhb@freebsd.org> Cc: err Subject: Re: 8GB RAM: PAE or not PAE? 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, 26 Sep 2007 16:06:26 -0000 On Wednesday 29 August 2007 04:51:10 pm Josef Grosch wrote: > On Wed, Aug 29, 2007 at 05:42:36PM +0200, err wrote: > > Hi > > > > I have an HP DL380 quad core with 8GB of RAM and SAS disks in RAID, with freebsd 6 STABLE on it. > > > > Everything works fine, except for the RAM addressing problem: freebsd sees only 4GB. > > I know it have been discussed, but it could be a problem to me for running a 64bit compiled system; what is the stability of a kernel compiled with the PAE option? > > > > I've a kernel with no modules, and before trying PAE I would know for other people experiences... > > In particular I'm interested in the behavior of ciss, bce, em and usb stuff, and application like Perl, Ruby, PHP 5, MySQL server, heavy MAWK and bzip2 load. > > > > Also, if I boot a PAE kernel, in order to have all my RAM available, I have to set the hw.physmem variable to 8G ? > > > > Thanks > > -- > > Emmanuel Richiardone > > > Based on my experience with PAE I would say, don't. I found PAE to be very > brittle. Not all the drivers work well with PAE. Most recent Intel > processors understand 64bit. I have several machines in our datacenter > which are Intel 5160 running amd64. 4.x + PAE is rather questionable, but 6.x + PAE is quite stable. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Wed Sep 26 23:18:21 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1FE016A419 for ; Wed, 26 Sep 2007 23:18:21 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id 1D15F13C45D for ; Wed, 26 Sep 2007 23:18:19 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id l8QNIfR04000; Thu, 27 Sep 2007 09:18:41 +1000 (EST) Message-ID: <20070927091841.30821@caamora.com.au> Date: Thu, 27 Sep 2007 09:18:41 +1000 From: jonathan michaels To: freebsd hardware Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Subject: FreeBSD v6.2-RELEASE with Compaq ProLiant 6400R 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, 26 Sep 2007 23:18:21 -0000 greetings all, i recently acquired a few Compaq ProLiant 6400r (4 gb dram, 4x fxp0 10/100 mhz nic, four PIII 500/100 mhz cpu with l2 cache of 1 Mb and Compaq smart array 221 scsi raid array controller), this machine shares the load with a similarly configured Compaq ProLiant 5500R. the raid is built from 4x36 gb Fujitsu 10K rpm scsi III hard disks, as a single 'drive' (striped i think) backed up to DLT-7000 tape streamer. both these machines are running freebsd v6.2-release both run flawlessly once up and running .. the problems is with the ProLiant 6400R and freebsd (-release, versions 6.2, 6.1, 6.0, 5.2, 4.6, 4.4 and 4.2) once the machine is booted from the proprietary HP "SmartStart" cdrom to configure the host, freebsd works a real treat and has really good uptime, even on my poorish power but once i power down the machine for any reason it will not restart on the installed freebsd filesystems .. these machines (5500r/6400r) were ms win 2003 servers and i reconfigured them both to use unix (Solaris/unixware in teh configuration part of teh initial startup process). i've Google'd, but, nothing like this is even mentioned, hinted at, i meant to say. MS Windows runs flawlessly as does FreeBSD once its booted, getting to to teh boot stage is the problem .. all that happens is teh light on teh cdrom turns yellow and the machine just sits there, waiting .. if it matters there is no MS Windows/Compaq ProLiant diagnostic tools filesystem on the raid/hard disk array setup. i have several ProLiant (as well as several 6400r's) and all work very well with freebsd. can anyone help, suggest, i have also down-load some of teh relevant doc's on teh HP/Compaq web-site and read, read and more read ... most kind regards/appreciations jonathan -- ================================================================ powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system ==== === appropriate solution in an inappropriate world === ==== From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 07:19:27 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A050F16A417 for ; Thu, 27 Sep 2007 07:19:27 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 6810813C4C5 for ; Thu, 27 Sep 2007 07:19:27 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3149463waf for ; Thu, 27 Sep 2007 00:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=aJ0O/W7I1COQTRg/3INvl9D0+HUHlpaDs+JIXRPsumE=; b=iI9PjEKuwnyCm4iuEOcOajIfO9OQc8rPB2L64/86Eb3zoMA7WXhIZDavYLS3XNY7M5LDUz29iRSiiwiogEub+X3i5agsMqq44LI2qyAsP23uAIbNPvTmLRWPA5IH+Cbagq9O0n7N9o+RuupMQlQVWQyKEIJzpXjChFnVt/mkxCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=mTdSGXREJMacKyj8hRjeMrr0ZTe4yiOUg4V9Kka6ff/eVi9NwDX2Peh7A3pyqC7Uvb8tW13JcR/ZCRJCGh9juVNKb/ifKWoOCKeJ3gKyIUaMgczUn0iMoghTTTDudOdgMxR4VTPCZQmu/Jb5MLZ0Dg1joZUzdV9IZB+L31pjVSs= Received: by 10.114.73.1 with SMTP id v1mr754497waa.1190876030559; Wed, 26 Sep 2007 23:53:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m40sm2876528waf.2007.09.26.23.53.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 26 Sep 2007 23:53:49 -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 l8R6o9J0003991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 15:50:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8R6o9sI003990; Thu, 27 Sep 2007 15:50:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 27 Sep 2007 15:50:08 +0900 From: Pyun YongHyeon To: Chris Message-ID: <20070927065008.GD3692@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240917p2776136fn50eb2d5bbbaeebf2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709240917p2776136fn50eb2d5bbbaeebf2@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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: Thu, 27 Sep 2007 07:19:27 -0000 On Mon, Sep 24, 2007 at 05:17:40PM +0100, Chris wrote: > On 24/09/2007, Jeremy Chadwick wrote: > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > nfe0: flags=8843 mtu 1500 > > > options=8 > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > ether x > > > media: Ethernet autoselect (1000baseTX ) > > > status: active > > > > > > 1 - is there a man page for nfe anywhere? > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > which is supposedly the same code. > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > 2 - does it support hardware checksum I remember reading it does but > > > from ifconfig output it appears to not be in use so if it does support > > > it how do I enable it? > > > > It does support it, but I don't know the circumstances surrounding when > > it gets enabled. That is to say, it's known that some versions of the > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > offloading is known to be broken on the system you're on. Taken from my > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=10b > > ether 00:15:f2:17:30:e9 > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet 1000baseTX > > status: active > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > line. > > > > > 3 - same with TOS? > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > You should take a bit more itme to read the webpage you obtained the > > driver from. I see these on the page: > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > Tx/Rx checksum offload settings with ifconfig. > > 2006/08/11 Added support for jumbo frame capability. > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > with both. > > > > > 5 - is it safe to use with zero copy sockets? > > > > No idea. > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > this driver safe to use on them? > > > > No idea. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > Ok to recap I have nforce 430 MCP13 > > I checked the src and current and 6.2-stable driver I am using are the > same version number but my driver src has this added above tunables. > > /* definitions for backporting RELENG-6 */ > #ifndef IFCAP_TSO4 > #define IFCAP_TSO4 0 > #define CSUM_TSO 0 > #endif > #ifndef VLAN_CAPABILITIES > #define VLAN_CAPABILITIES(x) > #endif > #ifndef IFCAP_VLAN_HWCSUM > #define IFCAP_VLAN_HWCSUM 0 > #endif > > I am guessing If I set the values to 1 I get the features but would > like someone to confirm this for me before I try it thanks. I only > have remote access so if it stops the card working I lose access to > the box. > Do you have strong evidence that nForce 430(MCP13, aka MCP51) supports hardware checksum offload? AFAIK MCP13 does NOT have support checksum offload/jumbo frame as well as TSO. If you want to experiment checksum offload capability of MCP13 hardware replace the following line in nfe_attach(). From: case PCI_PRODUCT_NVIDIA_MCP51_LAN1: case PCI_PRODUCT_NVIDIA_MCP51_LAN2: sc->nfe_flags |= NFE_40BIT_ADDR | NFE_PWR_MGMT; break; To: case PCI_PRODUCT_NVIDIA_MCP51_LAN1: case PCI_PRODUCT_NVIDIA_MCP51_LAN2: sc->nfe_flags |= NFE_40BIT_ADDR | NFE_PWR_MGMT | NFE_HW_CSUM; ^^^^^^^^^^^^^^ break; -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 07:22:14 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 288C116A419 for ; Thu, 27 Sep 2007 07:22:14 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id E619C13C4CB for ; Thu, 27 Sep 2007 07:22:13 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3150126waf for ; Thu, 27 Sep 2007 00:22:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=h7Qj1ff2AfoH2gVtPoG0/Qca90TKQoOMmhuSUPcKDnI=; b=pDliKcRaSA75TaWfe/rzmpOroSxccWF6JiIZTlxmf1+Q0Ho/5xxNSxya1vksyjIBOWnMaAHuh62fjk1opt/eadAexeS65poulYmoaGmpoUgXEk8waonVN2lJB+s8nLdI6mw9oUyhsrfUXiKbDU530/2H/kElpTbt04inL6y31VU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=crZlpX9rFx/N3tnpbUF55GMpznIJUkq6MlWiJTg8Rcw99KdFlGaWosnOUZsoB3xE+Z+frltXId3/fxjyjwl803ly84ep9F7Tsc1KPa9oT0vF7PucK0dHHHN9uGysxLIrB5uzDTYcLMHu1Qc4uG+pvibFawJbgICLpd55WtKVR6I= Received: by 10.115.23.12 with SMTP id a12mr781293waj.1190876138710; Wed, 26 Sep 2007 23:55:38 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id f20sm1993801waf.2007.09.26.23.55.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 26 Sep 2007 23:55:36 -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 l8R6pudi004002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 15:51:56 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8R6ptvM004001; Thu, 27 Sep 2007 15:51:55 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 27 Sep 2007 15:51:55 +0900 From: Pyun YongHyeon To: Chris Message-ID: <20070927065155.GE3692@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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: Thu, 27 Sep 2007 07:22:14 -0000 On Mon, Sep 24, 2007 at 04:44:09PM +0100, Chris wrote: > On 24/09/2007, Jeremy Chadwick wrote: > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > nfe0: flags=8843 mtu 1500 > > > options=8 > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > ether x > > > media: Ethernet autoselect (1000baseTX ) > > > status: active > > > > > > 1 - is there a man page for nfe anywhere? > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > which is supposedly the same code. > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > 2 - does it support hardware checksum I remember reading it does but > > > from ifconfig output it appears to not be in use so if it does support > > > it how do I enable it? > > > > It does support it, but I don't know the circumstances surrounding when > > it gets enabled. That is to say, it's known that some versions of the > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > offloading is known to be broken on the system you're on. Taken from my > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=10b > > ether 00:15:f2:17:30:e9 > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet 1000baseTX > > status: active > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > line. > > > > > 3 - same with TOS? > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > You should take a bit more itme to read the webpage you obtained the > > driver from. I see these on the page: > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > Tx/Rx checksum offload settings with ifconfig. > > 2006/08/11 Added support for jumbo frame capability. > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > with both. > > > > > 5 - is it safe to use with zero copy sockets? > > > > No idea. > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > this driver safe to use on them? > > > > No idea. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > Thanks yes I meant TSO sorry, I would guess with the checksum either > the 6.x driver is older and not fully implemented yet, the 6.x driver > does need more patches for certian chipsets so would indicate its > older then the CURRENT driver. Or as you said my chipset is known to > be unstable with the hardware checksums. > See the other mail I've posted. > The card is more stable when using nve driver no crashes still but the > performance is around the same maxing out at around 200mbit. I was > expecting nearer 400-500mbit. > > e1000phy0: on miibus0 > There had been issues nfe(4) with 88E1116/88E1149 PHYs but your issue seems to be different one. How about manually set media configuration? For example, "ifconfig nfe0 media 1000baseTX mediaopt full-duplex" > Is the line from dmesg, I believe in CURRENT mpsafe is always on > regardless so if you have no problems then its a good sign and I will > reenable mpsafe networking (default). > > Thanks really appreciated. > > Chris -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 10:54:07 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0EC916A41B for ; Thu, 27 Sep 2007 10:54:07 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: from smtp4.poczta.interia.pl (smtp35.poczta.interia.pl [80.48.65.35]) by mx1.freebsd.org (Postfix) with ESMTP id B521913C49D for ; Thu, 27 Sep 2007 10:54:06 +0000 (UTC) (envelope-from vermaden@interia.pl) Received: by smtp4.poczta.interia.pl (INTERIA.PL, from userid 502) id A3B5D2EA880; Thu, 27 Sep 2007 12:34:58 +0200 (CEST) Received: from f13.poczta.interia.pl (f13.poczta.interia.pl [10.217.2.13]) by smtp4.poczta.interia.pl (INTERIA.PL) with ESMTP id 42D0B2EA868 for ; Thu, 27 Sep 2007 12:34:57 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by f13.poczta.interia.pl (Postfix) with ESMTP id D137F80DB99 for ; Thu, 27 Sep 2007 12:34:57 +0200 (CEST) Date: 27 Sep 2007 12:34:57 +0200 From: vermaden To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE X-ORIGINATE-IP: 217.76.112.72 X-Mailer: PSE Message-Id: <20070927103457.D137F80DB99@f13.poczta.interia.pl> X-EMID: 85a40acc Subject: ASUS P5B-MX [946GZ/GMA 3000] does not work with Intel driver X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 10:54:07 -0000 I cannot make Intel 3000GMA in ASUS P5B-MX to work with intel driver. I added all info below. How can I help you more to resolve this problem? hardware: ASUS P5B-MX [946GZ chipset + GMA 3000] (82946GZ + ICH7 exacly) kernel config: generic SMP config from /usr/src/sys/i386/conf/SMP ---------------------------------------------------------------------------= ----- % uname -a FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed Sep 26 09:31:01 CEST 20= 07 root@siewa:/usr/obj/usr/src/sys/CUSTOM i386 ---------------------------------------------------------------------------= ----- % kldstat=20 Id Refs Address Size Name 1 12 0xc0400000 7e7820 kernel 2 1 0xc0be8000 633ec acpi.ko 3 1 0xc53bc000 1b000 linux.ko 4 1 0xc5696000 6000 i915.ko 5 1 0xc569c000 f000 drm.ko ---------------------------------------------------------------------------= ----- # kldload agp kldload: can't load agp: File exists ---------------------------------------------------------------------------= ----- % pkg_info xf86-video-intel-2.1.1 Information for xf86-video-intel-2.1.1: Comment: Driver for Intel integrated graphics chipsets Description: Driver for Intel integrated graphics chipsets. It supports the i810, i810-DC100, i810e, i815, i830M, 845G, 852GM, 855GM, 865G, 915G, 915GM, 945G, 945GM, 965G, 965Q, 946GZ and 965GM chipsets. ---------------------------------------------------------------------------= ----- % pciconf -lv hostb0@pci0:0:0:=09class=3D0x060000 card=3D0x823b1043 chip=3D0x29708086 rev= =3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D bridge subclass =3D HOST-PCI none0@pci0:2:0:=09class=3D0x030000 card=3D0x823b1043 chip=3D0x29728086 rev= =3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D display subclass =3D VGA none1@pci0:27:0:=09class=3D0x040300 card=3D0x82901043 chip=3D0x27d88086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) High Definition Audio' class =3D multimedia uhci0@pci0:29:0:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27c88086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB uhci1@pci0:29:1:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27c98086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB uhci2@pci0:29:2:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27ca8086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB uhci3@pci0:29:3:=09class=3D0x0c0300 card=3D0x81791043 chip=3D0x27cb8086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB Universal Host Controller' class =3D serial bus subclass =3D USB ehci0@pci0:29:7:=09class=3D0x0c0320 card=3D0x81791043 chip=3D0x27cc8086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) USB 2.0 Enhanced Host Controller' class =3D serial bus subclass =3D USB pcib1@pci0:30:0:=09class=3D0x060401 card=3D0x81791043 chip=3D0x244e8086 rev= =3D0xe1 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB = Hub Interface to PCI Bridge' class =3D bridge subclass =3D PCI-PCI isab0@pci0:31:0:=09class=3D0x060100 card=3D0x81791043 chip=3D0x27b88086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801GB/GR (ICH7 Family) LPC Interface Controller' class =3D bridge subclass =3D PCI-ISA atapci0@pci0:31:1:=09class=3D0x01018f card=3D0x81791043 chip=3D0x27df8086 r= ev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) Ultra ATA Storage Controller' class =3D mass storage subclass =3D ATA atapci1@pci0:31:2:=09class=3D0x01018f card=3D0x81791043 chip=3D0x27c08086 r= ev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controll= er' class =3D mass storage subclass =3D ATA none2@pci0:31:3:=09class=3D0x0c0500 card=3D0x81791043 chip=3D0x27da8086 rev= =3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801G (ICH7 Family) SMBus Controller' class =3D serial bus subclass =3D SMBus rl0@pci1:0:0:=09class=3D0x020000 card=3D0x10015354 chip=3D0x813910ec rev=3D= 0x10 hdr=3D0x00 vendor =3D 'Realtek Semiconductor' device =3D 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class =3D network subclass =3D ethernet ---------------------------------------------------------------------------= ----- % cat /etc/X11/xorg.conf=20 Section "ServerLayout" =09Identifier "X.org Configured" =09Screen 0 "Screen0" 0 0 =09InputDevice "Mouse0" "CorePointer" =09InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" =09RgbPath "/usr/local/share/X11/rgb" =09ModulePath "/usr/local/lib/xorg/modules" EndSection Section "Module" Load "dri" Load "glx" =09 Load "dbe" =09 Load "extmod" EndSection Section "Device" Identifier "Card0" Driver "intel" EndSection Section "InputDevice" =09Identifier "Keyboard0" =09Driver "kbd" EndSection Section "InputDevice" =09Identifier "Mouse0" =09Driver "mouse" =09Option=09 "Protocol" "auto" =09Option=09 "Device" "/dev/sysmouse" EndSection Section "Monitor" =09Identifier "Monitor0" =09HorizSync 30.0 - 83.0 =09VertRefresh 55.0 - 75.0 =09Option=09 "DPMS" EndSection Section "Screen" =09Identifier "Screen0" =09Device "Card0" =09Monitor "Monitor0" DefaultDepth 24 =09SubSection "Display" =09=09Modes "1280x1024" =09EndSubSection EndSection ---------------------------------------------------------------------------= ----- % cat ~/.xinitrc=20 exec twm ---------------------------------------------------------------------------= ----- % startx x3d09e417d83b660d60edaa2f90afe8b4: not found xauth: creating new authority file /home/vermaden/.serverauth.851 X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386=20 Current Operating System: FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: W= ed Sep 26 09:31:01 CEST 2007 root@siewa:/usr/obj/usr/src/sys/CUSTOM i38= 6 Build Date: 31 July 2007 =09Before reporting problems, check http://wiki.x.org =09to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (=3D=3D) default setting, =09(++) from command line, (!!) notice, (II) informational, =09(WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 27 12:21:10 2007 (=3D=3D) Using config file: "/etc/X11/xorg.conf" (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 X connection to :0.0 broken (explicit kill or server shutdown). ---------------------------------------------------------------------------= ----- % cat /var/log/Xorg.0.log X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386=20 Current Operating System: FreeBSD siewa 6.2-STABLE FreeBSD 6.2-STABLE #0: W= ed Sep 26 09:31:01 CEST 2007 root@siewa:/usr/obj/usr/src/sys/CUSTOM i38= 6 Build Date: 31 July 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (=3D=3D) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (=3D=3D) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 27 12:21:10 2007 (=3D=3D) Using config file: "/etc/X11/xorg.conf" (=3D=3D) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (=3D=3D) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (**) RgbPath set to "/usr/local/share/X11/rgb" (**) ModulePath set to "/usr/local/lib/xorg/modules" (II) Loader magic: 0x819e340 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.1 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (II) Loading /usr/local/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Video Driver, version 1.1 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages =3D 0x03, oldVal1 =3D 0x00000000, mode1Res1 =3D 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2970 card 1043,823b rev 02 class 06,00,00 hdr = 00 (II) PCI: 00:02:0: chip 8086,2972 card 1043,823b rev 02 class 03,00,00 hdr = 00 (II) PCI: 00:1b:0: chip 8086,27d8 card 1043,8290 rev 01 class 04,03,00 hdr = 00 (II) PCI: 00:1d:0: chip 8086,27c8 card 1043,8179 rev 01 class 0c,03,00 hdr = 80 (II) PCI: 00:1d:1: chip 8086,27c9 card 1043,8179 rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1d:2: chip 8086,27ca card 1043,8179 rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1d:3: chip 8086,27cb card 1043,8179 rev 01 class 0c,03,00 hdr = 00 (II) PCI: 00:1d:7: chip 8086,27cc card 1043,8179 rev 01 class 0c,03,20 hdr = 00 (II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev e1 class 06,04,01 hdr = 01 (II) PCI: 00:1f:0: chip 8086,27b8 card 1043,8179 rev 01 class 06,01,00 hdr = 80 (II) PCI: 00:1f:1: chip 8086,27df card 1043,8179 rev 01 class 01,01,8f hdr = 00 (II) PCI: 00:1f:2: chip 8086,27c0 card 1043,8179 rev 01 class 01,01,8f hdr = 00 (II) PCI: 00:1f:3: chip 8086,27da card 1043,8179 rev 01 class 0c,05,00 hdr = 00 (II) PCI: 01:00:0: chip 10ec,8139 card 5354,1001 rev 10 class 02,00,00 hdr = 00 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleare= d) (II) Bus 1 I/O range: [0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xfeb00000 - 0xfebfffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set= ) (--) PCI:*(0:2:0) Intel Corporation 82946GZ/GL Integrated Graphics Controll= er rev 2, Mem @ 0xfea00000/20, 0xe0000000/28, I/O @ 0xdc00/3 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [1] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [2] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [3] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [4] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [5] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [6] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [7] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[B]E [8] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [9] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [10] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B]E [11] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [12] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [13] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [14] -1 0 0x000008f0 - 0x000008ff (0x10) IX[B]E [15] -1 0 0x0000c400 - 0x0000c4ff (0x100) IX[B]E [16] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [17] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [18] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B]E [19] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [20] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]E [21] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) PCI I/O resource overlap reduced 0x0000c800 from 0x0000c8ff to 0x0000c= 87f (II) PCI I/O resource overlap reduced 0x0000d000 from 0x0000d0ff to 0x0000d= 07f (II) PCI I/O resource overlap reduced 0x000008f0 from 0x000008ff to 0x00000= 8f7 (II) PCI I/O resource overlap reduced 0x0000c400 from 0x0000c4ff to 0x0000c= 47f (II) PCI I/O resource overlap reduced 0x0000d800 from 0x0000d8ff to 0x0000d= 87f (II) PCI I/O resource overlap reduced 0x0000d400 from 0x0000d4ff to 0x0000d= 47f (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [1] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [2] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [3] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [4] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [5] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [6] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [7] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [8] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [9] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [10] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [11] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [12] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [13] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [14] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [15] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [16] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [17] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [18] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [19] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [20] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [21] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [5] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [6] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [7] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [8] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [9] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [10] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [11] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [12] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [13] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [14] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [15] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [16] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [17] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [18] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [19] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [20] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [21] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [22] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [23] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [24] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [25] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [26] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [27] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) LoadModule: "dri" (II) Loading /usr/local/lib/xorg/modules/extensions//libdri.so (II) Module dri: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) Loading extension XFree86-DRI (II) LoadModule: "glx" (II) Loading /usr/local/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Server Extension, version 0.3 (=3D=3D) AIGLX disabled (II) Loading extension GLX (II) LoadModule: "dbe" (II) Loading /usr/local/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "extmod" (II) Loading /usr/local/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "intel" (II) Loading /usr/local/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 2.1.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.1 (II) LoadModule: "mouse" (II) Loading /usr/local/lib/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.1.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) LoadModule: "kbd" (II) Loading /usr/local/lib/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.1.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.7 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (--) Chipset 946GZ found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [5] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [6] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [7] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [8] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [9] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [10] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [11] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [12] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [13] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [14] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [15] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [16] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [17] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [18] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [19] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [20] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [21] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [22] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [23] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [24] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [25] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [26] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [27] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [5] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [6] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [7] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [8] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [9] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [10] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [11] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [12] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [13] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [14] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [15] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [16] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [17] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [18] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [19] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [20] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [21] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [22] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [23] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [24] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [25] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [26] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [27] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [28] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [29] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [30] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) [31] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [32] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/local/lib/xorg/modules//libvbe.so (II) Module vbe: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.1.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/local/lib/xorg/modules//libvgahw.so (II) Module vgahw: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 0.1.0 ABI class: X.Org Video Driver, version 1.1 (**) intel(0): Depth 24, (--) framebuffer bpp 32 (=3D=3D) intel(0): RGB weight 888 (=3D=3D) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 946GZ (--) intel(0): Chipset: "946GZ" (--) intel(0): Linear framebuffer at 0xE0000000 (--) intel(0): IO registers at addr 0xFEA00000 (=3D=3D) intel(0): Write-combining range (0xfea00000,0x80000) was already c= lear (=3D=3D) intel(0): Write-combining range (0xfea80000,0x80000) was already c= lear (II) intel(0): 2 display pipes available. (=3D=3D) intel(0): Using XAA for acceleration (--) intel(0): Will try to allocate texture pool for old Mesa 3D driver. (II) intel(0): Will try to reserve 32768 kiB of AGP aperture space for the DRM memory manager. (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/local/lib/xorg/modules//libddc.so (II) Module ddc: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/local/lib/xorg/modules//libi2c.so (II) Module i2c: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.2.0 ABI class: X.Org Video Driver, version 1.1 (II) intel(0): Output VGA using monitor section Monitor0 (II) intel(0): I2C bus "CRTDDC_A" initialized. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" register= ed at address 0x70. (II) intel(0): No SDVO device found on SDVOB (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" register= ed at address 0x72. (II) intel(0): No SDVO device found on SDVOC (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. (=3D=3D) intel(0): Write-combining range (0xa0000,0x10000) was already clea= r (II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0. (II) intel(0): I2C device "CRTDDC_A:ddc2" removed. (II) intel(0): Using hsync ranges from config file (II) intel(0): Using vrefresh ranges from config file (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 62= 8 +hsync +vsync (II) intel(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500= -hsync -vsync (II) intel(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525= -hsync -vsync (II) intel(0): Modeline "720x400" 28.32 720 738 846 900 400 412 414 449= -hsync +vsync (II) intel(0): Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025= 1028 1066 +hsync +vsync (II) intel(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 77= 2 800 +hsync +vsync (II) intel(0): Modeline "1024x768" 75.00 1024 1048 1184 1328 768 771 77= 7 806 -hsync -vsync (II) intel(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 77= 7 806 -hsync -vsync (II) intel(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 62= 5 +hsync +vsync (II) intel(0): Modeline "1280x1024" 138.75 1280 1368 1504 1728 1024 1027= 1034 1072 -hsync +vsync (II) intel(0): Modeline "1280x1024" 109.00 1280 1368 1496 1712 1024 1027= 1034 1063 -hsync +vsync (II) intel(0): Modeline "1024x768" 82.00 1024 1088 1192 1360 768 771 77= 5 805 -hsync +vsync (II) intel(0): Modeline "1024x768" 63.50 1024 1072 1176 1328 768 771 77= 5 798 -hsync +vsync (II) intel(0): Modeline "800x600" 49.00 800 840 920 1040 600 603 607 62= 9 -hsync +vsync (II) intel(0): Modeline "800x600" 38.25 800 832 912 1024 600 603 607 62= 4 -hsync +vsync (II) intel(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025= 1028 1066 +hsync +vsync (II) intel(0): EDID vendor "ACR", prod id 44369 (II) intel(0): Output VGA connected (II) intel(0): Output VGA using initial mode 1280x1024 (=3D=3D) intel(0): Write-combining range (0xa0000,0x10000) was already clea= r (II) intel(0): detected 512 kB GTT. (II) intel(0): detected 7676 kB stolen memory. (=3D=3D) intel(0): video overlay key set to 0x101fe (=3D=3D) intel(0): Will not try to enable page flipping (=3D=3D) intel(0): Triple buffering disabled (=3D=3D) intel(0): Using gamma correction (1.0, 1.0, 1.0) (**) intel(0): Display dimensions: (340, 270) mm (**) intel(0): DPI set to (95, 120) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/local/lib/xorg/modules//libxaa.so (II) Module xaa: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 1.2.0 ABI class: X.Org Video Driver, version 1.1 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/local/lib/xorg/modules//libramdac.so (II) Module ramdac: vendor=3D"X.Org Foundation" compiled for 7.2.0, module version =3D 0.1.0 ABI class: X.Org Video Driver, version 1.1 (II) intel(0): Comparing regs from server start up to After PreInit (=3D=3D) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xe0000000 - 0xefffffff (0x10000000) MS[B] [1] 0 0 0xfea00000 - 0xfeafffff (0x100000) MS[B] [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xfebffc00 - 0xfebfffff (0x400) MX[B]E [7] -1 0 0xfe9f7c00 - 0xfe9f7fff (0x400) MX[B]E [8] -1 0 0xfe9f8000 - 0xfe9fffff (0x8000) MX[B]E [9] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [10] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[B](B) [11] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [12] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [13] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [14] 0 0 0x0000dc00 - 0x0000dc07 (0x8) IS[B] [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [17] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B]E [18] -1 0 0x00000400 - 0x000004ff (0x100) IX[B]E [19] -1 0 0x0000c800 - 0x0000c87f (0x80) IX[B]E [20] -1 0 0x0000c880 - 0x0000c8ff (0x80) IX[B]E [21] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[B]E [22] -1 0 0x0000d000 - 0x0000d07f (0x80) IX[B]E [23] -1 0 0x0000d080 - 0x0000d0ff (0x80) IX[B]E [24] -1 0 0x0000bc00 - 0x0000bcff (0x100) IX[B]E [25] -1 0 0x000008f8 - 0x000008ff (0x8) IX[B]E [26] -1 0 0x000008f0 - 0x000008f7 (0x8) IX[B]E [27] -1 0 0x0000c400 - 0x0000c47f (0x80) IX[B]E [28] -1 0 0x0000c480 - 0x0000c4ff (0x80) IX[B]E [29] -1 0 0x0000d880 - 0x0000d8ff (0x80) IX[B]E [30] -1 0 0x0000d800 - 0x0000d87f (0x80) IX[B]E [31] -1 0 0x0000d480 - 0x0000d4ff (0x80) IX[B]E [32] -1 0 0x0000d400 - 0x0000d47f (0x80) IX[B]E [33] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B](B) [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (WW) intel(0): /dev/agpgart is either not available, or no memory is availa= ble for allocation. Using pre-allocated memory only. (=3D=3D) intel(0): VideoRam: 7676 KB (=3D=3D) intel(0): Write-combining range (0xfea00000,0x80000) was already c= lear (=3D=3D) intel(0): Write-combining range (0xfea80000,0x80000) was already c= lear (II) intel(0): Attempting memory allocation with tiled buffers and=20 large DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (II) intel(0): Attempting memory allocation with tiled buffers and=20 small DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (II) intel(0): Attempting memory allocation with untiled buffers and=20 large DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (II) intel(0): Attempting memory allocation with untiled buffers and=20 small DRI memory manager reservation: (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (WW) intel(0): Not enough video memory. Disabling DRI. (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low= ? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 ---------------------------------------------------------------------- Tutaj sa Twoi nowi znajomi! Sprawdz >>> http://link.interia.pl/f1bb7 From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 13:38:03 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B36C16A41B for ; Thu, 27 Sep 2007 13:38:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3E98413C474 for ; Thu, 27 Sep 2007 13:38:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id C24131A4D93; Thu, 27 Sep 2007 06:38:02 -0700 (PDT) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 27 Sep 2007 09:22:54 -0400 User-Agent: KMail/1.9.7 References: <20070927091841.30821@caamora.com.au> In-Reply-To: <20070927091841.30821@caamora.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709270922.54572.jhb@freebsd.org> Cc: Subject: Re: FreeBSD v6.2-RELEASE with Compaq ProLiant 6400R 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, 27 Sep 2007 13:38:03 -0000 On Wednesday 26 September 2007 07:18:41 pm jonathan michaels wrote: > greetings all, > > i recently acquired a few Compaq ProLiant 6400r (4 gb dram, 4x fxp0 > 10/100 mhz nic, four PIII 500/100 mhz cpu with l2 cache of 1 Mb and > Compaq smart array 221 scsi raid array controller), this machine shares > the load with a similarly configured Compaq ProLiant 5500R. the raid is > built from 4x36 gb Fujitsu 10K rpm scsi III hard disks, as a single > 'drive' (striped i think) backed up to DLT-7000 tape streamer. > > both these machines are running freebsd v6.2-release both run > flawlessly once up and running .. the problems is with the ProLiant > 6400R and freebsd (-release, versions 6.2, 6.1, 6.0, 5.2, 4.6, 4.4 and > 4.2) once the machine is booted from the proprietary HP "SmartStart" > cdrom to configure the host, freebsd works a real treat and has really > good uptime, even on my poorish power but once i power down the > machine for any reason it will not restart on the installed freebsd > filesystems .. these machines (5500r/6400r) were ms win 2003 servers > and i reconfigured them both to use unix (Solaris/unixware in teh > configuration part of teh initial startup process). > > i've Google'd, but, nothing like this is even mentioned, hinted at, i > meant to say. MS Windows runs flawlessly as does FreeBSD once its booted, > getting to to teh boot stage is the problem .. all that happens is teh > light on teh cdrom turns yellow and the machine just sits there, > waiting .. if it matters there is no MS Windows/Compaq ProLiant > diagnostic tools filesystem on the raid/hard disk array setup. > > i have several ProLiant (as well as several 6400r's) and all work very > well with freebsd. > > can anyone help, suggest, i have also down-load some of teh relevant > doc's on teh HP/Compaq web-site and read, read and more read ... > > most kind regards/appreciations What did you set the OS type to in Smart Start? If you used "other" then try using a different setting such as "Novell Netware" or "UnixWare". -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 17:11:19 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6089516A41A for ; Thu, 27 Sep 2007 17:11:19 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id CBA2613C448 for ; Thu, 27 Sep 2007 17:11:17 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id l8RHBfO06898; Fri, 28 Sep 2007 03:11:41 +1000 (EST) Message-ID: <20070928031140.48970@caamora.com.au> Date: Fri, 28 Sep 2007 03:11:40 +1000 From: jonathan michaels Cc: freebsd-hardware@freebsd.org References: <20070927091841.30821@caamora.com.au> <200709270922.54572.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <200709270922.54572.jhb@freebsd.org>; from John Baldwin on Thu, Sep 27, 2007 at 09:22:54AM -0400 Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Subject: Re: FreeBSD v6.2-RELEASE with Compaq ProLiant 6400R 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, 27 Sep 2007 17:11:19 -0000 john, thanks for teh timely responce On Thu, Sep 27, 2007 at 09:22:54AM -0400, John Baldwin wrote: > On Wednesday 26 September 2007 07:18:41 pm jonathan michaels wrote: > > i have several ProLiant (as well as several 6400r's) and all work very > > well with freebsd. except for tis stop on reboot and wait for some indeterninate time to reboot, it is as if teh machine is stoping for some reason and waiting ??? just waiting as if it is asleep, none of teh leds are lit, except for teh powersupply, it also has a redundant ps even if i plug that in it dosent 'help' and none of teh fgiagnostic leds 'issue' error warnings and there is no post messages or other warnings in teh hardware error loging .. just a continuation of teh reboot process where it left off (before it gets to post ??) and teh eventual boot. i have 4 of these (6400R's) i'm wondering if this is a'generic' issue or just specific to this one ?? > > can anyone help, suggest, i have also down-load some of teh relevant > > doc's on teh HP/Compaq web-site and read, read and more read ... > > > > most kind regards/appreciations > > What did you set the OS type to in Smart Start? If you used "other" then try > using a different setting such as "Novell Netware" or "UnixWare". i used solaris, for some reason that seemed the most sensible to use, for as far as i could recall solaris was the most "bsd" like ?? dies the difference in teh memory seen/available have anything t do with this ?? the machine has a little over 4 gb real dram, smart start claims ththat ther is ony 3G8 but freebsd says that it starts with 3G6. is there some way to be able t use the whole dram ?? most kind regards jonathan ps, old saying about looking gift horse in mouth ?? life, grin. -- ================================================================ powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system ==== === appropriate solution in an inappropriate world === ==== From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 17:28:14 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9275616A468 for ; Thu, 27 Sep 2007 17:28:14 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id D415A13C46A for ; Thu, 27 Sep 2007 17:28:12 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1581097ugf for ; Thu, 27 Sep 2007 10:28:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pGmPiNQhU9+Dk5Bma+y3H3HoECEMrwRjWVwwwRdjN8c=; b=YC1UByimQv2JowFokF2HcGxnca5D08OBh5VJXwVcom+WlUh9lCx+Zpo/W2pKPBEuYu5r6Berjzzp4AaqlIkCTnt9Y4mBRw9RLS8ZL/ARZ/PU7/h3g2/cUpfbRvG/DUxuMyM5ZkuyaVMLj+UUQIOpLlMVeNj7vV47veIzNrP1IRc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PVtjycdqVQS5W+z525Kv5fuG+bzdv5d6Jx4pydiElI8MfzCj6RYvook4RuLuuYXe2q+ooCCDY5LeHF88BLkKtHOHgzOkhyloE5Rcuaaf3Rp2rj6zjbwf/nYTMsTq2eM/xVXXx5j4+ofULXpbv310ZqwAQez7FtdtvIZ6HaEOP8s= Received: by 10.66.248.5 with SMTP id v5mr3883548ugh.1190914089588; Thu, 27 Sep 2007 10:28:09 -0700 (PDT) Received: by 10.67.20.1 with HTTP; Thu, 27 Sep 2007 10:28:08 -0700 (PDT) Message-ID: <3aaaa3a0709271028x59476d8i658cd2ca454f154f@mail.gmail.com> Date: Thu, 27 Sep 2007 18:28:08 +0100 From: Chris To: pyunyh@gmail.com In-Reply-To: <20070927065008.GD3692@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240917p2776136fn50eb2d5bbbaeebf2@mail.gmail.com> <20070927065008.GD3692@cdnetworks.co.kr> Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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, 27 Sep 2007 17:28:14 -0000 On 27/09/2007, Pyun YongHyeon wrote: > On Mon, Sep 24, 2007 at 05:17:40PM +0100, Chris wrote: > > On 24/09/2007, Jeremy Chadwick wrote: > > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > > nfe0: flags=8843 mtu 1500 > > > > options=8 > > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > > ether x > > > > media: Ethernet autoselect (1000baseTX ) > > > > status: active > > > > > > > > 1 - is there a man page for nfe anywhere? > > > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > > which is supposedly the same code. > > > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > > > 2 - does it support hardware checksum I remember reading it does but > > > > from ifconfig output it appears to not be in use so if it does support > > > > it how do I enable it? > > > > > > It does support it, but I don't know the circumstances surrounding when > > > it gets enabled. That is to say, it's known that some versions of the > > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > > offloading is known to be broken on the system you're on. Taken from my > > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > > > nfe0: flags=8843 metric 0 mtu 1500 > > > options=10b > > > ether 00:15:f2:17:30:e9 > > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > > media: Ethernet 1000baseTX > > > status: active > > > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > > line. > > > > > > > 3 - same with TOS? > > > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > > > You should take a bit more itme to read the webpage you obtained the > > > driver from. I see these on the page: > > > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > > Tx/Rx checksum offload settings with ifconfig. > > > 2006/08/11 Added support for jumbo frame capability. > > > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > > with both. > > > > > > > 5 - is it safe to use with zero copy sockets? > > > > > > No idea. > > > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > > this driver safe to use on them? > > > > > > No idea. > > > > > > -- > > > | Jeremy Chadwick jdc at parodius.com | > > > | Parodius Networking http://www.parodius.com/ | > > > | UNIX Systems Administrator Mountain View, CA, USA | > > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > > > > > Ok to recap I have nforce 430 MCP13 > > > > I checked the src and current and 6.2-stable driver I am using are the > > same version number but my driver src has this added above tunables. > > > > /* definitions for backporting RELENG-6 */ > > #ifndef IFCAP_TSO4 > > #define IFCAP_TSO4 0 > > #define CSUM_TSO 0 > > #endif > > #ifndef VLAN_CAPABILITIES > > #define VLAN_CAPABILITIES(x) > > #endif > > #ifndef IFCAP_VLAN_HWCSUM > > #define IFCAP_VLAN_HWCSUM 0 > > #endif > > > > I am guessing If I set the values to 1 I get the features but would > > like someone to confirm this for me before I try it thanks. I only > > have remote access so if it stops the card working I lose access to > > the box. > > > > Do you have strong evidence that nForce 430(MCP13, aka MCP51) supports > hardware checksum offload? AFAIK MCP13 does NOT have support checksum > offload/jumbo frame as well as TSO. > > If you want to experiment checksum offload capability of MCP13 > hardware replace the following line in nfe_attach(). > > From: > case PCI_PRODUCT_NVIDIA_MCP51_LAN1: > case PCI_PRODUCT_NVIDIA_MCP51_LAN2: > sc->nfe_flags |= NFE_40BIT_ADDR | NFE_PWR_MGMT; > break; > > To: > case PCI_PRODUCT_NVIDIA_MCP51_LAN1: > case PCI_PRODUCT_NVIDIA_MCP51_LAN2: > sc->nfe_flags |= NFE_40BIT_ADDR | NFE_PWR_MGMT | NFE_HW_CSUM; > ^^^^^^^^^^^^^^ > break; > > -- > Regards, > Pyun YongHyeon > No I didnt know sorry I didnt know MCP13 was aka MCP51 so that explains why thanks. Chris From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 17:30:22 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC01B16A421 for ; Thu, 27 Sep 2007 17:30:22 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id F341E13C459 for ; Thu, 27 Sep 2007 17:30:21 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1581536ugf for ; Thu, 27 Sep 2007 10:30:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=hH83SBFWYVZTrzDOdxjImBAWbO6Z4KLZnxHmkMbWx50=; b=NORctw/giCrHEdK9E+dFl6muocoi7P8h3tTwiV2Ki0GBVwt4VZymLFjo76vkpNPRJWUSNAie7He68yy0QS8WPviWG1WG28OXYMWeqY1wELZ863ppLRGCsPv9TrKHWW7tDqmPLEOg5sUcgGidgc6rWcmcptOy6BQSzXUedw6B8x4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d6rujZTRo25ConaNjRnb8x7ZHrIoAGtPTLK1hGoXZbVd1BjPtjnxBn6NZY3tuud0blm/xnP3bUu3OwJuP+ta3fDNidA4qWTLrg7hUSlfLHMHJQDxfBd8FfCw2v5luw6zfoCNuGset3XuxyZjoHMj+4DWmkDO8Pq9JoPs0mm7gyc= Received: by 10.67.28.4 with SMTP id f4mr3854231ugj.1190914220759; Thu, 27 Sep 2007 10:30:20 -0700 (PDT) Received: by 10.67.20.1 with HTTP; Thu, 27 Sep 2007 10:30:20 -0700 (PDT) Message-ID: <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> Date: Thu, 27 Sep 2007 18:30:20 +0100 From: Chris To: pyunyh@gmail.com In-Reply-To: <20070927065155.GE3692@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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, 27 Sep 2007 17:30:22 -0000 On 27/09/2007, Pyun YongHyeon wrote: > On Mon, Sep 24, 2007 at 04:44:09PM +0100, Chris wrote: > > On 24/09/2007, Jeremy Chadwick wrote: > > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > > nfe0: flags=8843 mtu 1500 > > > > options=8 > > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > > ether x > > > > media: Ethernet autoselect (1000baseTX ) > > > > status: active > > > > > > > > 1 - is there a man page for nfe anywhere? > > > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > > which is supposedly the same code. > > > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > > > 2 - does it support hardware checksum I remember reading it does but > > > > from ifconfig output it appears to not be in use so if it does support > > > > it how do I enable it? > > > > > > It does support it, but I don't know the circumstances surrounding when > > > it gets enabled. That is to say, it's known that some versions of the > > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > > offloading is known to be broken on the system you're on. Taken from my > > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > > > nfe0: flags=8843 metric 0 mtu 1500 > > > options=10b > > > ether 00:15:f2:17:30:e9 > > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > > media: Ethernet 1000baseTX > > > status: active > > > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > > line. > > > > > > > 3 - same with TOS? > > > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > > > You should take a bit more itme to read the webpage you obtained the > > > driver from. I see these on the page: > > > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > > Tx/Rx checksum offload settings with ifconfig. > > > 2006/08/11 Added support for jumbo frame capability. > > > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > > with both. > > > > > > > 5 - is it safe to use with zero copy sockets? > > > > > > No idea. > > > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > > this driver safe to use on them? > > > > > > No idea. > > > > > > -- > > > | Jeremy Chadwick jdc at parodius.com | > > > | Parodius Networking http://www.parodius.com/ | > > > | UNIX Systems Administrator Mountain View, CA, USA | > > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > > > > > Thanks yes I meant TSO sorry, I would guess with the checksum either > > the 6.x driver is older and not fully implemented yet, the 6.x driver > > does need more patches for certian chipsets so would indicate its > > older then the CURRENT driver. Or as you said my chipset is known to > > be unstable with the hardware checksums. > > > > See the other mail I've posted. > > > The card is more stable when using nve driver no crashes still but the > > performance is around the same maxing out at around 200mbit. I was > > expecting nearer 400-500mbit. > > > > e1000phy0: on miibus0 > > > > There had been issues nfe(4) with 88E1116/88E1149 PHYs but your issue > seems to be different one. How about manually set media configuration? > For example, "ifconfig nfe0 media 1000baseTX mediaopt full-duplex" > > > Is the line from dmesg, I believe in CURRENT mpsafe is always on > > regardless so if you have no problems then its a good sign and I will > > reenable mpsafe networking (default). > > > > Thanks really appreciated. > > > > Chris > -- > Regards, > Pyun YongHyeon > I typod I meant to say nve was unstable and nfe has been rock solid so great work with the driver. I enabled mpsafe now and still no problems and its gave me a little more performance as well, a shame my nic has no hardware features (unusual for a gigabit nic) but overall glad its at least stable. Chris From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 22:19:06 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 953AC16A469 for ; Thu, 27 Sep 2007 22:19:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 28DF413C4A5 for ; Thu, 27 Sep 2007 22:19:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 211768015-1834499 for multiple; Thu, 27 Sep 2007 18:17:49 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l8RMIwgd040584; Thu, 27 Sep 2007 18:18:58 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Thu, 27 Sep 2007 17:30:54 -0400 User-Agent: KMail/1.9.6 References: <20070927091841.30821@caamora.com.au> <200709270922.54572.jhb@freebsd.org> <20070928031140.48970@caamora.com.au> In-Reply-To: <20070928031140.48970@caamora.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709271730.54683.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, 27 Sep 2007 18:18:59 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4415/Thu Sep 27 16:02:21 2007 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: jonathan michaels Subject: Re: FreeBSD v6.2-RELEASE with Compaq ProLiant 6400R 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, 27 Sep 2007 22:19:06 -0000 On Thursday 27 September 2007 01:11:40 pm jonathan michaels wrote: > > > can anyone help, suggest, i have also down-load some of teh relevant > > > doc's on teh HP/Compaq web-site and read, read and more read ... > > > > > > most kind regards/appreciations > > > > What did you set the OS type to in Smart Start? If you used "other" then try > > using a different setting such as "Novell Netware" or "UnixWare". > > i used solaris, for some reason that seemed the most sensible to use, > for as far as i could recall solaris was the most "bsd" like ?? For Compaq's purposes, FreeBSD is not anything like Solaris. Other users (if you do a simple web search like I did when I replied to your e-mail) have had success with the options I mentioned above. > dies the difference in teh memory seen/available have anything t do > with this ?? the machine has a little over 4 gb real dram, smart start > claims ththat ther is ony 3G8 but freebsd says that it starts with 3G6. Assuming you are using FreeBSD/i386 and that you get it installed ok, you can try using a PAE kernel to get access to the full 4 GB of RAM. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Thu Sep 27 23:03:57 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FE8D16A418 for ; Thu, 27 Sep 2007 23:03:57 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id DDBBA13C4A6 for ; Thu, 27 Sep 2007 23:03:55 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id l8RN4Kt08068; Fri, 28 Sep 2007 09:04:20 +1000 (EST) Message-ID: <20070928090419.34167@caamora.com.au> Date: Fri, 28 Sep 2007 09:04:19 +1000 From: jonathan michaels References: <20070927091841.30821@caamora.com.au> <200709270922.54572.jhb@freebsd.org> <20070928031140.48970@caamora.com.au> <200709271730.54683.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <200709271730.54683.jhb@freebsd.org>; from John Baldwin on Thu, Sep 27, 2007 at 05:30:54PM -0400 Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Cc: jonathan michaels , freebsd-hardware@freebsd.org Subject: Re: FreeBSD v6.2-RELEASE with Compaq ProLiant 6400R 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, 27 Sep 2007 23:03:57 -0000 On Thu, Sep 27, 2007 at 05:30:54PM -0400, John Baldwin wrote: > On Thursday 27 September 2007 01:11:40 pm jonathan michaels wrote: > > > > can anyone help, suggest, i have also down-load some of teh relevant > > > > doc's on teh HP/Compaq web-site and read, read and more read ... > > > > > > > > most kind regards/appreciations > > > > > > What did you set the OS type to in Smart Start? If you used "other" then > try > > > using a different setting such as "Novell Netware" or "UnixWare". > > > > i used solaris, for some reason that seemed the most sensible to use, > > for as far as i could recall solaris was the most "bsd" like ?? > > For Compaq's purposes, FreeBSD is not anything like Solaris. Other users (if > you do a simple web search like I did when I replied to your e-mail) have had > success with the options I mentioned above. yes i did try for many hours, that is why i finally asked here. i was not getting anywhere in my attempts, it is hard for me to "use" and then to understand teh results > > dies the difference in teh memory seen/available have anything t do > > with this ?? the machine has a little over 4 gb real dram, smart start > > claims ththat ther is ony 3G8 but freebsd says that it starts with 3G6. > > Assuming you are using FreeBSD/i386 and that you get it installed ok, you can > try using a PAE kernel to get access to the full 4 GB of RAM. muchly appreciated, thank your for your time and effort kind regards jonathan -- ================================================================ powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system ==== === appropriate solution in an inappropriate world === ==== From owner-freebsd-hardware@FreeBSD.ORG Fri Sep 28 00:11:02 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F33116A420 for ; Fri, 28 Sep 2007 00:11:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by mx1.freebsd.org (Postfix) with ESMTP id 509EE13C45B for ; Fri, 28 Sep 2007 00:11:02 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so2218529rvb for ; Thu, 27 Sep 2007 17:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=ftZoH4rlDWP9zO9IFc3T0ojH8sTnJgE+A3mqd9+YXEk=; b=q5Gf7OgfQWR2VkzqPg46YzZzhl/iLMs/W6iGx6Oki/ELAJXGax6riY+q3AysO6XDZFAolPBZ2ZqhqVx98B/ajzJFPmPxUShCp5sc2VSoyFFGLJg1gnt6jzQj7al0Ngx1TntIOy2OhyyfJVNO54uKOhV1DPUZurt6jXoOviXXlT4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=ez3LZnagpkQbEqli6UjjPd6WQTccpOGiKXo7BAHCn7D6eco+2EMIRfBRuwwjsGxllEA5fg+SXnhsru55kNokk7r5IlHh7qokObiOvo58taD9qQSa0ML3rTvi61keYS0h1lNu+wlQ//xvs3WhGvHQXoyYnBed7moUsN2rEewdVL4= Received: by 10.114.157.1 with SMTP id f1mr3223566wae.1190938237545; Thu, 27 Sep 2007 17:10:37 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m24sm4431239waf.2007.09.27.17.10.34 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Sep 2007 17:10:36 -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 l8S06vDL007261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Sep 2007 09:06:57 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8S06utB007260; Fri, 28 Sep 2007 09:06:56 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 28 Sep 2007 09:06:56 +0900 From: Pyun YongHyeon To: Chris Message-ID: <20070928000656.GA7119@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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: Fri, 28 Sep 2007 00:11:02 -0000 On Thu, Sep 27, 2007 at 06:30:20PM +0100, Chris wrote: > On 27/09/2007, Pyun YongHyeon wrote: > > On Mon, Sep 24, 2007 at 04:44:09PM +0100, Chris wrote: [...] > > > > > The card is more stable when using nve driver no crashes still but the > > > performance is around the same maxing out at around 200mbit. I was > > > expecting nearer 400-500mbit. > > > > > > e1000phy0: on miibus0 > > > > > > > There had been issues nfe(4) with 88E1116/88E1149 PHYs but your issue > > seems to be different one. How about manually set media configuration? > > For example, "ifconfig nfe0 media 1000baseTX mediaopt full-duplex" > > [...] > > I typod I meant to say nve was unstable and nfe has been rock solid so > great work with the driver. I enabled mpsafe now and still no > problems and its gave me a little more performance as well, a shame my > nic has no hardware features (unusual for a gigabit nic) but overall > glad its at least stable. > How did you check network performance? Maxing out at around 200Mbps seems weird. Personally, I had never seen GigE hardwares that saturate at 200Mbps. One of causes I can think of is speed/duplex mismatches with link partner. Manually setting speed/duplex might fix your performance issue, I guess. -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Fri Sep 28 06:28:52 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 647E816A419 for ; Fri, 28 Sep 2007 06:28:52 +0000 (UTC) (envelope-from Varan_Orapiriyakul@acer.co.th) Received: from smtp.acer.co.th (smtp2.acer.co.th [203.150.235.219]) by mx1.freebsd.org (Postfix) with ESMTP id EC5E013C45A for ; Fri, 28 Sep 2007 06:28:51 +0000 (UTC) (envelope-from Varan_Orapiriyakul@acer.co.th) To: freebsd-hardware@freebsd.org X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006 Message-ID: From: Varan_Orapiriyakul@acer.co.th Date: Fri, 28 Sep 2007 13:25:45 +0700 X-MIMETrack: Serialize by Router on THBKKNS1/SPOKE/ACI(Release 7.0.2|September 26, 2006) at 09/28/2007 01:33:30 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: *********** How to setup FC-HBA to FreeBSD & connect to SAN. *********** X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 06:28:52 -0000 Hi all, Does anyone know " How to config QLogic or Emulex FC HBA to FreeBSD 5.4/5.5/6.2 ? " I try to implement SAN in my organization but I got some of FreeBSD Servers. Please help thank you. Best Regards, Varan Orapiriyakul Technical Support Specialist System Solution Center Acer Computer Co.,Ltd. 191/62-63 ,16th Fl. CTI Tower, Rachadapisek rd. Klongtoey, Bangkok 10110 ,Thailand. Office : (+66) 02-661-9700 Ext 1313 Mobile : (+66) 086-304-4200 Email : varan_orapiriyakul@acer.co.th From owner-freebsd-hardware@FreeBSD.ORG Fri Sep 28 18:05:38 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03CBF16A418 for ; Fri, 28 Sep 2007 18:05:38 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 74DBC13C459 for ; Fri, 28 Sep 2007 18:05:37 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1786438ugf for ; Fri, 28 Sep 2007 11:05:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=6PBJBCVbAzT3e/jDK9zaeE5TyIOZ5MS4/j0Dau5ahRI=; b=XVoUJp1KW3TGL4dIfO3Yj2zam9DLyPZ9NMchJJR5AlPRLsZv5gAkXIZS5EzUtE8WZANfbfGCMZALzQPcbH3ph5dyP7ZGrAkJMB1qP8Hc66sGkXkzAL0K/alpO0B/cdHJWsnEy5pZomLn3wmRaHCfNC9u6TecsqHPqY+3gXSffJE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RWiOv1KBnqLEQlC4QzUEr34itu7bEkSd66vYC0wCjzS2Dxawe/22ucMrOLvHRiDAmHgRSl1iQTUmMsiSdCtQBNhx6h0CdkCMeqYzP7O7Dak6WJ39avfxR+mK231sujho+kuojuGifL6HA9/mGIwHo5Koc05+3sWwwgoOkrUQoNo= Received: by 10.67.28.3 with SMTP id f3mr138272ugj.1191002736168; Fri, 28 Sep 2007 11:05:36 -0700 (PDT) Received: by 10.67.20.1 with HTTP; Fri, 28 Sep 2007 11:05:35 -0700 (PDT) Message-ID: <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> Date: Fri, 28 Sep 2007 19:05:35 +0100 From: Chris To: pyunyh@gmail.com In-Reply-To: <20070928000656.GA7119@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 18:05:38 -0000 On 28/09/2007, Pyun YongHyeon wrote: > On Thu, Sep 27, 2007 at 06:30:20PM +0100, Chris wrote: > > On 27/09/2007, Pyun YongHyeon wrote: > > > On Mon, Sep 24, 2007 at 04:44:09PM +0100, Chris wrote: > > [...] > > > > > > > The card is more stable when using nve driver no crashes still but the > > > > performance is around the same maxing out at around 200mbit. I was > > > > expecting nearer 400-500mbit. > > > > > > > > e1000phy0: on miibus0 > > > > > > > > > > There had been issues nfe(4) with 88E1116/88E1149 PHYs but your issue > > > seems to be different one. How about manually set media configuration? > > > For example, "ifconfig nfe0 media 1000baseTX mediaopt full-duplex" > > > > > [...] > > > > > I typod I meant to say nve was unstable and nfe has been rock solid so > > great work with the driver. I enabled mpsafe now and still no > > problems and its gave me a little more performance as well, a shame my > > nic has no hardware features (unusual for a gigabit nic) but overall > > glad its at least stable. > > > > How did you check network performance? > Maxing out at around 200Mbps seems weird. Personally, I had never seen > GigE hardwares that saturate at 200Mbps. One of causes I can think of > is speed/duplex mismatches with link partner. Manually setting > speed/duplex might fix your performance issue, I guess. > > -- > Regards, > Pyun YongHyeon > These are ftp transfers it is running on a amd62 x2 dual core processor and gig of ram, when at max speed cpu usage is very high in excess of 80% but not completely maxed out. It now seems to be able to sustain around 30meg/sec the highest I have seen I havent done any other testing so if you have a better way it would be good to know thanks. Please bare in mind I have no local access to the server so crashing it eg. is expensive for as will have to pay for a kvm switch netstat -i indicates no collisions for a duplex mismatch so not keen on trying a manual negotiotian again for reasons above. So even for a card with no hardware features you would expect it to exceed 200mbit easily? I havent enabled net isr setting I wonder if that will help. Chris From owner-freebsd-hardware@FreeBSD.ORG Fri Sep 28 21:23:24 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2752716A418 for ; Fri, 28 Sep 2007 21:23:24 +0000 (UTC) (envelope-from smcafee@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id C13B313C465 for ; Fri, 28 Sep 2007 21:23:23 +0000 (UTC) (envelope-from smcafee@collaborativefusion.com) Received: from [192.168.2.72] (icepick.pitbpa0.priv.collaborativefusion.com [192.168.2.72]) (AUTH: LOGIN smcafee, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Fri, 28 Sep 2007 17:13:21 -0400 id 00056421.46FD6E71.000104EB Message-ID: <46FD6E94.2080608@collaborativefusion.com> Date: Fri, 28 Sep 2007 17:13:56 -0400 From: Sean McAfee User-Agent: Thunderbird 2.0.0.6 (X11/20070810) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 21:23:24 -0000 We first became aware of this problem about a month ago. A database server was up but was completely unresponsive to anything other than pings. I power cycled it via the DRAC and after we couldn't find anything suspicious in the logs, we figured it was a fluke. Until the next day, when its twin did the same exact thing. This time, I was able to get a screen shot through the DRAC console. Using old daily outputs and that screenshot, we correlated the crashes to patrol reads. Since then, we've only seen it "in the wild" on one other machine, a 1950, but I've been trying to chase the problem down without much luck. I'm fortunate to have three machines at my disposal for this testing, so I was able to try a variety of combinations: Server 1: Chassis: 2950 v1 System BIOS: 1.1.0 PERC firmware: 1.00.01-0088 PERC F/W (from the 5.0.1-0030 A00 package) OS: 6.2-R_p7, 6-STABLE Server 2: Chassis: 2950 v1 System BIOS: 1.1.0 PERC firmware: 1.03.10-0216 PERC F/W (from the 5.1.1-0040 package) OS: 6.2-R_p7, 6-STABLE Server 3: Chassis: 2950 v2 System BIOS: 1.5.1 PERC firmware: 1.03.10-0216 PERC F/W (from the 5.1.1-0040 package) OS: 6.2-R_p7 They're all running amd64 and each combination was tried with and without the linux_mfi.ko patches found in PR-113232. For disks, they all have 2x36gb RAID1, 4x73gb RAID10 (all SAS.) We use linux_mfi.ko+linux-megacli for management. The original problem occurred during automatic patrol reads coupled with heavy disk load. I've changed the delay interval for the automatic patrol reads and tried to reproduce it but haven't had enough success to make it useful for troubleshooting. Since the automatic reads are meant to be as least aggressive as possible, I've been running a manual patrol read (megacli -AdpPR -Start -a0), which triggers a crash regardless of what I/O is like. The behavior has little to no variation; shortly after the read is started, disk writes immediately cease (shown via an scp from another machine). After a minute, the console will begin to fill up with lines such as: mif0: COMMAND 0xffffffff892bc998 TIMEOUT AFTER 45 SECONDS The first 8 values of the hex never change - I bring that up because I suspect the problem has something to do with the enclosure, which is attached at 8, 255, or fffffff, depending on where you're looking. I've let it go up to 6000 seconds, but it eventually ends in a kernel panic. That just seems to be a side effect of the original problem (processes with nowhere to write data), so I'm not too hung up on that. There's never anything pertaining to it in the controller's event log. Besides the platform version differences I mentioned above, I've tried: - Reducing the patrol read rate - Pulling down and modifying the patches from PR-115133 (which seems to set an upper boundary at 0xffffffff) - Invoking a0/aALL interchangeably - Changing the cache flush interval - Disabling disk coercion - A bunch of other long-shot settings from megacli that aren't worth listing Nothing has shown any appreciable difference in the behavior. Does anyone have an idea about what could be going on or anything else we can try? For now, I'll probably just disable them and set them to auto/1 hour delay during outage windows only, but I'm hoping that someone is able to help with this. At the very least, maybe I can save someone a whole bunch of time. Thanks in advance for any help. -- Sean McAfee Collaborative Fusion, Inc. smcafee@collaborativefusion.com 412-422-3463 x 4025 1710 Murray Avenue, Suite 320 Pittsburgh, PA 15217 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. **************************************************************** From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 01:31:48 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5248B16A41B for ; Sat, 29 Sep 2007 01:31:48 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by mx1.freebsd.org (Postfix) with ESMTP id DF49613C461 for ; Sat, 29 Sep 2007 01:31:47 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so1419808wra for ; Fri, 28 Sep 2007 18:31:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=Mmsz4rkj5s7D+eMkXKp0n4hLiZn9ey7hNpeiRFlwEds=; b=U/DW4BYSYxepmMupmpnHvFmpzjHtc2hqJhtE/AmGUZCNF5IeqB9Ibh0hwryTgTjY97kSHCrtXPQSZkZVFD3hWKNx5R8b1x06xDpA7siCfcILRVMOU4UxQ9/5zby7Ym4FAnOakHcZXStD4Go2BJlXJm6rN9CL2X1xAwbab9S7Olg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=nRHgf7kGAtd8B7LAv43X44mxuBHlTzlFjzQlyfS99l4veLlp3MvIZ6+M4snzwYZkk27ShtNu9+DMn5vc8+ll+vNi7hL2RgDjFkn6E53oT2Th03glosGUGcXOE8CoJznKCBGqU2WFz4gdQaX/5i7imsvodtIjlPX4mKDSAoaQg/k= Received: by 10.114.146.1 with SMTP id t1mr1118169wad.1191029506353; Fri, 28 Sep 2007 18:31:46 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id n38sm6659523wag.2007.09.28.18.31.42 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Sep 2007 18:31:45 -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 l8T1S2DY011564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Sep 2007 10:28:02 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8T1S2Fu011563; Sat, 29 Sep 2007 10:28:02 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 29 Sep 2007 10:28:01 +0900 From: Pyun YongHyeon To: Chris Message-ID: <20070929012801.GA11457@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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: Sat, 29 Sep 2007 01:31:48 -0000 On Fri, Sep 28, 2007 at 07:05:35PM +0100, Chris wrote: > On 28/09/2007, Pyun YongHyeon wrote: > > On Thu, Sep 27, 2007 at 06:30:20PM +0100, Chris wrote: > > > On 27/09/2007, Pyun YongHyeon wrote: > > > > On Mon, Sep 24, 2007 at 04:44:09PM +0100, Chris wrote: > > > > [...] > > > > > > > > > The card is more stable when using nve driver no crashes still but the > > > > > performance is around the same maxing out at around 200mbit. I was > > > > > expecting nearer 400-500mbit. > > > > > > > > > > e1000phy0: on miibus0 > > > > > > > > > > > > > There had been issues nfe(4) with 88E1116/88E1149 PHYs but your issue > > > > seems to be different one. How about manually set media configuration? > > > > For example, "ifconfig nfe0 media 1000baseTX mediaopt full-duplex" > > > > > > > > [...] > > > > > > > > I typod I meant to say nve was unstable and nfe has been rock solid so > > > great work with the driver. I enabled mpsafe now and still no > > > problems and its gave me a little more performance as well, a shame my > > > nic has no hardware features (unusual for a gigabit nic) but overall > > > glad its at least stable. > > > > > > > How did you check network performance? > > Maxing out at around 200Mbps seems weird. Personally, I had never seen > > GigE hardwares that saturate at 200Mbps. One of causes I can think of > > is speed/duplex mismatches with link partner. Manually setting > > speed/duplex might fix your performance issue, I guess. > > > > -- > > Regards, > > Pyun YongHyeon > > > > These are ftp transfers it is running on a amd62 x2 dual core > processor and gig of ram, when at max speed cpu usage is very high in > excess of 80% but not completely maxed out. It now seems to be able > to sustain around 30meg/sec the highest I have seen I havent done any > other testing so if you have a better way it would be good to know ftp transfers involve disk activities so you're not measuring NIC performance. Try one of benchmark programs in ports/benchmarks (e.g. netperf, iperf, ttcp etc). ATM nfe(4)'s interrupt moderation mechanism doesn't seem to work at all so nfe(4) generates too many interrupts. However I don't think it wouldn't be major bottleneck of the performance. > thanks. Please bare in mind I have no local access to the server so > crashing it eg. is expensive for as will have to pay for a kvm switch > netstat -i indicates no collisions for a duplex mismatch so not keen > on trying a manual negotiotian again for reasons above. So even for a > card with no hardware features you would expect it to exceed 200mbit > easily? > Yes. You have a gigabit ethernet controller and fast CPU. Run one of benchmark programs and get a number. > I havent enabled net isr setting I wonder if that will help. > That wouldn't help a lot, I guess. > Chris -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 02:22:09 2007 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D75716A418 for ; Sat, 29 Sep 2007 02:22:09 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: from smtp117.sbc.mail.sp1.yahoo.com (smtp117.sbc.mail.sp1.yahoo.com [69.147.64.90]) by mx1.freebsd.org (Postfix) with SMTP id 51AD813C45D for ; Sat, 29 Sep 2007 02:22:09 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: (qmail 45528 invoked from network); 29 Sep 2007 01:55:29 -0000 Received: from unknown (HELO ?192.168.1.238?) (jinmtb@sbcglobal.net@67.111.218.125 with plain) by smtp117.sbc.mail.sp1.yahoo.com with SMTP; 29 Sep 2007 01:55:28 -0000 X-YMail-OSG: 5.zRXicVM1k2YLV9oIiU195_GB_p2HFIgLXzJi8w4Z4btbV4vCVymfWNwRE_sJ9CntuoIX83iA-- Message-ID: <46FDB090.9040708@george.lbl.gov> Date: Fri, 28 Sep 2007 18:55:28 -0700 From: Jin Guojun User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20061027 X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: TrendNet TEG-PCBUSR 10/100/1000 CardBus PC adapter X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 02:22:09 -0000 This PC Gigabit Ethernet adapter seems to have RealTek chip, but its spec does not say which one. When I plug it in a DELL Latitude 1001 Laptop with FreeBSD 6.2-Release, I got following error: re0: port 0xd000-0xd0ff mem 0xf8001000-0xf80011ff irq 11 at device 0.0 on cardbus0 miibus1: on re0 rgephy0: on miibus1 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX -FDX, auto re0: Ethernet address: 00:18:e7:04:cc:13 re0: couldn't set up irq rgephy0: detached miibus1: detached device_attach: re0 attach returned 22 Is anything I can tweak to make it work under FreeBSD 6.2-Release? Thanks, -Jin From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 02:48:07 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1066016A419 for ; Sat, 29 Sep 2007 02:48:07 +0000 (UTC) (envelope-from jos@catnook.com) Received: from lizzy.dyndns.org (209-204-188-132.dsl.static.sonic.net [209.204.188.132]) by mx1.freebsd.org (Postfix) with SMTP id A1BA513C457 for ; Sat, 29 Sep 2007 02:48:06 +0000 (UTC) (envelope-from jos@catnook.com) Received: (qmail 86958 invoked by uid 1000); 29 Sep 2007 02:21:47 -0000 Date: Fri, 28 Sep 2007 19:21:47 -0700 From: Jos Backus To: freebsd-hardware@freebsd.org, FreeBSD Stable Message-ID: <20070929022147.GA27590@lizzy.catnook.local> Mail-Followup-To: freebsd-hardware@freebsd.org, FreeBSD Stable References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> <20070929012801.GA11457@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070929012801.GA11457@cdnetworks.co.kr> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: Re: nfe driver 6.2 stable X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jos@catnook.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 02:48:07 -0000 On Sat, Sep 29, 2007 at 10:28:01AM +0900, Pyun YongHyeon wrote: [snip] > ATM nfe(4)'s interrupt moderation mechanism doesn't seem to work > at all so nfe(4) generates too many interrupts. However I don't > think it wouldn't be major bottleneck of the performance. Could this be why (on -current) I had to enable polling on nfe0 to get rid of the choppy audio playback I was experiencing? -- Jos Backus jos at catnook.com From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 03:07:36 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CFEB16A418 for ; Sat, 29 Sep 2007 03:07:36 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 7CC5013C448 for ; Sat, 29 Sep 2007 03:07:35 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1848882ugf for ; Fri, 28 Sep 2007 20:07:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=oQPBRb1HMxNwKKmoMEUsLvkAUN6mYYP1am7eNZEH+PE=; b=oWXmArAuoh5hBWMbvGoRnvZrT1Bd8qAyTJAILLR6N44CdOL2pf9My+DS3mDnr0qgctoeG2GiTqQsxPFGwbj3U1R/r1P9pSo0Ac7n88mxSEuW2i20ZlNq9uLbQyk/3JPz48rVWRtxVJLyR1VC47LQxvRfnTsqP5p23aN86hH0XRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=R0VID9qkAAVksZvGucF0nlFoT7m6OXyZXtdN9IFtONlsDSwsPHy0HEfRUcFrtpe5FQoe+8d0vmorfan/zYfpg//wsWrxiW2BBJucioVUBdOxDsYBbuUYgefbuIT/QrWP/kuK1p8WR1IR/0qczOGqwlxHJmJOtP1b0xNf9hTNAA4= Received: by 10.67.24.18 with SMTP id b18mr5873608ugj.1191035253456; Fri, 28 Sep 2007 20:07:33 -0700 (PDT) Received: by 10.67.20.1 with HTTP; Fri, 28 Sep 2007 20:07:33 -0700 (PDT) Message-ID: <3aaaa3a0709282007s1675b714g71d025f87dd1c350@mail.gmail.com> Date: Sat, 29 Sep 2007 04:07:33 +0100 From: Chris To: pyunyh@gmail.com In-Reply-To: <20070929012801.GA11457@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> <20070929012801.GA11457@cdnetworks.co.kr> Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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, 29 Sep 2007 03:07:36 -0000 On 29/09/2007, Pyun YongHyeon wrote: > On Fri, Sep 28, 2007 at 07:05:35PM +0100, Chris wrote: > > On 28/09/2007, Pyun YongHyeon wrote: > > > On Thu, Sep 27, 2007 at 06:30:20PM +0100, Chris wrote: > > > > On 27/09/2007, Pyun YongHyeon wrote: > > > > > On Mon, Sep 24, 2007 at 04:44:09PM +0100, Chris wrote: > > > > > > [...] > > > > > > > > > > > The card is more stable when using nve driver no crashes still but the > > > > > > performance is around the same maxing out at around 200mbit. I was > > > > > > expecting nearer 400-500mbit. > > > > > > > > > > > > e1000phy0: on miibus0 > > > > > > > > > > > > > > > > There had been issues nfe(4) with 88E1116/88E1149 PHYs but your issue > > > > > seems to be different one. How about manually set media configuration? > > > > > For example, "ifconfig nfe0 media 1000baseTX mediaopt full-duplex" > > > > > > > > > > > [...] > > > > > > > > > > > I typod I meant to say nve was unstable and nfe has been rock solid so > > > > great work with the driver. I enabled mpsafe now and still no > > > > problems and its gave me a little more performance as well, a shame my > > > > nic has no hardware features (unusual for a gigabit nic) but overall > > > > glad its at least stable. > > > > > > > > > > How did you check network performance? > > > Maxing out at around 200Mbps seems weird. Personally, I had never seen > > > GigE hardwares that saturate at 200Mbps. One of causes I can think of > > > is speed/duplex mismatches with link partner. Manually setting > > > speed/duplex might fix your performance issue, I guess. > > > > > > -- > > > Regards, > > > Pyun YongHyeon > > > > > > > These are ftp transfers it is running on a amd62 x2 dual core > > processor and gig of ram, when at max speed cpu usage is very high in > > excess of 80% but not completely maxed out. It now seems to be able > > to sustain around 30meg/sec the highest I have seen I havent done any > > other testing so if you have a better way it would be good to know > > ftp transfers involve disk activities so you're not measuring NIC > performance. Try one of benchmark programs in ports/benchmarks > (e.g. netperf, iperf, ttcp etc). > ATM nfe(4)'s interrupt moderation mechanism doesn't seem to work > at all so nfe(4) generates too many interrupts. However I don't > think it wouldn't be major bottleneck of the performance. > > > thanks. Please bare in mind I have no local access to the server so > > crashing it eg. is expensive for as will have to pay for a kvm switch > > netstat -i indicates no collisions for a duplex mismatch so not keen > > on trying a manual negotiotian again for reasons above. So even for a > > card with no hardware features you would expect it to exceed 200mbit > > easily? > > > > Yes. You have a gigabit ethernet controller and fast CPU. > Run one of benchmark programs and get a number. > > > I havent enabled net isr setting I wonder if that will help. > > > > That wouldn't help a lot, I guess. > > > Chris > > -- > Regards, > Pyun YongHyeon > Will let you know results thanks, also will polling work on my card? Chris From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 05:03:43 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA83716A46B for ; Sat, 29 Sep 2007 05:03:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 888DA13C481 for ; Sat, 29 Sep 2007 05:03:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3861411waf for ; Fri, 28 Sep 2007 22:03:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=6Z711KO/9fWUm5ODnoucaxGoX847InyYQ28yzm0riDQ=; b=Wgl6XzqSRDgTqKzX/50v5UulzWjQGVytxwlchfkCpsdCu4kfmeZE5ZwZ/jEI5LF7dkZxXNljKeJf5R3qOUqVNTDUYa2Pb2JCUxESUjrN8FCiB+tE8GxIzJ6um7eB+Sy5KXbkYuCosvnF1ZFU2xjAsnG3lAA6mn+bSuZwIfj9DVo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=TG0PNMXGwLMFcNJRTURmyFKNeQdtqPb8T+lDmmeC029fmLgCUMrHM9/WpA0Zlir+juEO47KumKz5sjS2JHqeSIa5xohXeMSc30Y9oFdXvwQbOfvkuVOl6chRVTXX26uugfAac0dfZjOUWjwwHMywg7rp85+vZTKz5/45vt4xOGQ= Received: by 10.114.176.1 with SMTP id y1mr1224995wae.1191042222925; Fri, 28 Sep 2007 22:03:42 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id n37sm6891491wag.2007.09.28.22.03.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Sep 2007 22:03:41 -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 l8T500Ts012140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Sep 2007 14:00:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8T500Wg012139; Sat, 29 Sep 2007 14:00:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 29 Sep 2007 14:00:00 +0900 From: Pyun YongHyeon To: Chris Message-ID: <20070929050000.GB11457@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> <20070929012801.GA11457@cdnetworks.co.kr> <3aaaa3a0709282007s1675b714g71d025f87dd1c350@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709282007s1675b714g71d025f87dd1c350@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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: Sat, 29 Sep 2007 05:03:43 -0000 On Sat, Sep 29, 2007 at 04:07:33AM +0100, Chris wrote: > > Will let you know results thanks, also will polling work on my card? > Yes. -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 05:06:26 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7621316A49C for ; Sat, 29 Sep 2007 05:06:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.227]) by mx1.freebsd.org (Postfix) with ESMTP id B028913C46E for ; Sat, 29 Sep 2007 05:06:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1952552nzf for ; Fri, 28 Sep 2007 22:06:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=XOhubfstaU2HIfkJcSX3xr9KTjIcK1uVpUGSXepRbk0=; b=gtJNoQC8vXB+gK5xH1SGPXfhffdsy+WfFJubgs9pkcLWCVsyEgug0cGd1wilg9ht/B/ltNm6u8hIofi8QbAw9HXC5aif2JQHhc//N6dJLrz2GSoakj8ftTucdcGYpqNZXpBmUw+n7vbwskB6LdsBLRsEsB9k2RQL/EpCL6fIRvQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=qp9WkA9YQpGA2Ii72o0EBVZukBjoLH9oGcZPy0NUdQPunGX05HvPYaX9ohYi2IWPt6M/A2S/cffo7mEXqU5Ha3imFRwkiaVysk/k3emZwCGr/CtOh483OW2thu2fSmy7s6Jx7sqG4JAfA/uVW1zHCND80JoYXZ/UUMSdBCAwW4w= Received: by 10.114.192.1 with SMTP id p1mr537392waf.1191042381151; Fri, 28 Sep 2007 22:06:21 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id d20sm4860804waa.2007.09.28.22.06.18 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Sep 2007 22:06:20 -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 l8T52fx6012175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Sep 2007 14:02:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8T52e7G012174; Sat, 29 Sep 2007 14:02:40 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 29 Sep 2007 14:02:40 +0900 From: Pyun YongHyeon To: freebsd-hardware@freebsd.org, FreeBSD Stable Message-ID: <20070929050240.GC11457@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> <20070929012801.GA11457@cdnetworks.co.kr> <20070929022147.GA27590@lizzy.catnook.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070929022147.GA27590@lizzy.catnook.local> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: nfe driver 6.2 stable 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: Sat, 29 Sep 2007 05:06:26 -0000 On Fri, Sep 28, 2007 at 07:21:47PM -0700, Jos Backus wrote: > On Sat, Sep 29, 2007 at 10:28:01AM +0900, Pyun YongHyeon wrote: > [snip] > > ATM nfe(4)'s interrupt moderation mechanism doesn't seem to work > > at all so nfe(4) generates too many interrupts. However I don't > > think it wouldn't be major bottleneck of the performance. > > Could this be why (on -current) I had to enable polling on nfe0 to get rid of > the choppy audio playback I was experiencing? > Probably not. Maybe nfe(4) use shared interrupt. Check the output of "vmstat -i". -- Regards, Pyun YongHyeon From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 16:10:41 2007 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59DC416A494 for ; Sat, 29 Sep 2007 16:10:41 +0000 (UTC) (envelope-from whizzter@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224]) by mx1.freebsd.org (Postfix) with ESMTP id ECC7E13C47E for ; Sat, 29 Sep 2007 16:10:40 +0000 (UTC) (envelope-from whizzter@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so1491277wra for ; Sat, 29 Sep 2007 09:10:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=eJse0B6WRLwJ0qgqGxPS7zhqMG38cDfF9nHH+98Espc=; b=CuQj1m3QYjDmSn/0JpXAJLl+Nf+vSj49Sk/xYkKT+8Ols5SqpbvBcq76xiBwV3V5gvb06hw5IwfqmD7e6W4Xx1tXq7+SlCeSXJnHQBcN6fPJMHE4bvkzPuw6gYb05rM12AQ5BWNDm/zdIkqs4BnROzesTWjAEZOJZc6FpDmaVrw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=t0HF8ba11WoYIYFoyEpkFehrlz+woSnj4dcMFzd9/jiP/mfftYALPLqzzySm0T9A1RjD7NrbmxQ9REekOZ2UsYXBgveAUEHIicuGw3YdcrSp3q9ryLJs8FeqrXwnaeyPTJRyb4xRIewcs5AvQDafJdXQUof9prs0YrGsoaha7pY= Received: by 10.90.79.6 with SMTP id c6mr7981335agb.1191080583974; Sat, 29 Sep 2007 08:43:03 -0700 (PDT) Received: by 10.142.98.15 with HTTP; Sat, 29 Sep 2007 08:43:03 -0700 (PDT) Message-ID: <436c7eda0709290843g15833d91k8d9912b4576ef8a4@mail.gmail.com> Date: Sat, 29 Sep 2007 17:43:03 +0200 From: "Jonas Lund" To: "Jin Guojun" In-Reply-To: <46FDB090.9040708@george.lbl.gov> MIME-Version: 1.0 References: <46FDB090.9040708@george.lbl.gov> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hardware@freebsd.org Subject: Re: TrendNet TEG-PCBUSR 10/100/1000 CardBus PC adapter X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 16:10:41 -0000 check the manual page for the driver, it states that there are defunct cards using the chipset. maybe it's one of those? manual page: http://www.freebsd.org/cgi/man.cgi?query=re&sektion=4&manpath=FreeBSD+6.2-RELEASE / Jonas Lund 2007/9/29, Jin Guojun : > > This PC Gigabit Ethernet adapter seems to have RealTek chip, but its > spec does not say which one. > When I plug it in a DELL Latitude 1001 Laptop with FreeBSD 6.2-Release, > I got following error: > > re0: port > 0xd000-0xd0ff mem > 0xf8001000-0xf80011ff irq 11 at device 0.0 on cardbus0 > miibus1: on re0 > rgephy0: on miibus1 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX > -FDX, auto > re0: Ethernet address: 00:18:e7:04:cc:13 > re0: couldn't set up irq > rgephy0: detached > miibus1: detached > device_attach: re0 attach returned 22 > > Is anything I can tweak to make it work under FreeBSD 6.2-Release? > > Thanks, > > -Jin > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org > " > From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 29 18:15:58 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A39B16A418 for ; Sat, 29 Sep 2007 18:15:58 +0000 (UTC) (envelope-from jos@catnook.com) Received: from lizzy.dyndns.org (209-204-188-132.dsl.static.sonic.net [209.204.188.132]) by mx1.freebsd.org (Postfix) with SMTP id ECCF213C458 for ; Sat, 29 Sep 2007 18:15:57 +0000 (UTC) (envelope-from jos@catnook.com) Received: (qmail 30385 invoked by uid 1000); 29 Sep 2007 18:16:18 -0000 Date: Sat, 29 Sep 2007 11:16:18 -0700 From: Jos Backus To: Pyun YongHyeon Message-ID: <20070929181618.GA30333@lizzy.catnook.local> Mail-Followup-To: Pyun YongHyeon , freebsd-hardware@freebsd.org, FreeBSD Stable References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> <20070927065155.GE3692@cdnetworks.co.kr> <3aaaa3a0709271030k24892099ra3409ce6f5f7020f@mail.gmail.com> <20070928000656.GA7119@cdnetworks.co.kr> <3aaaa3a0709281105g1503fdbcu70910de6eae060a0@mail.gmail.com> <20070929012801.GA11457@cdnetworks.co.kr> <20070929022147.GA27590@lizzy.catnook.local> <20070929050240.GC11457@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070929050240.GC11457@cdnetworks.co.kr> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jos@catnook.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 18:15:58 -0000 On Sat, Sep 29, 2007 at 02:02:40PM +0900, Pyun YongHyeon wrote: > On Fri, Sep 28, 2007 at 07:21:47PM -0700, Jos Backus wrote: > > On Sat, Sep 29, 2007 at 10:28:01AM +0900, Pyun YongHyeon wrote: > > [snip] > > > ATM nfe(4)'s interrupt moderation mechanism doesn't seem to work > > > at all so nfe(4) generates too many interrupts. However I don't > > > think it wouldn't be major bottleneck of the performance. > > > > Could this be why (on -current) I had to enable polling on nfe0 to get rid of > > the choppy audio playback I was experiencing? > > > > Probably not. Maybe nfe(4) use shared interrupt. > Check the output of "vmstat -i". pcm0 and nfe0 share irq23: lizzy:~% vmstat -i interrupt total rate irq1: atkbd0 107296 0 irq6: fdc0 1 0 irq12: psm0 563936 1 irq22: atapci2 5293281 11 irq23: pcm0 nfe0 1225731 2 cpu0: timer 947413237 2000 Total 954603482 2015 lizzy:~% Both pcm0 and nfe0 are mobo devices. Is there any way to change the assigned interrupts? -- Jos Backus jos at catnook.com