From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 02:58:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 358431065670; Sun, 27 Jun 2010 02:58:10 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (unknown [IPv6:2001:380:e06:127::53]) by mx1.freebsd.org (Postfix) with ESMTP id ED4A78FC1B; Sun, 27 Jun 2010 02:58:08 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 8A81978C3B; Sun, 27 Jun 2010 11:58:05 +0900 (JST) Received: from artemis (unknown [192.168.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTP id 7BC0878C34; Sun, 27 Jun 2010 11:58:05 +0900 (JST) Message-ID: <6BC2B2FBAFFA4C26A46977F121B707E1@ad.peach.ne.jp> From: "Daisuke Aoyama" To: References: <1931AE1113EC4A8983B8A52A2A1966C2@ad.peach.ne.jp> In-Reply-To: <1931AE1113EC4A8983B8A52A2A1966C2@ad.peach.ne.jp> Date: Sun, 27 Jun 2010 11:57:03 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: isboot (iSCSI boot driver) version 0.1.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 02:58:10 -0000 Updated isboot to 0.1.3. Try this. How to build/upgrade: # cd /usr/src # tar xvf /path/to/iscsi-2.2.4.tar.gz # tar xvf /path/to/isboot-0.1.3.tar.gz # make buildkernel # make installkernel or # cd /usr/src/sys/modules/iscsi/isboot # make obj # make depend # make all # make install After installation, please reboot the server to take effect. Confirm the log shows "iSCSI boot driver version 0.1.3". What's new?: * improve session recovery mode. * fix panic when socket is lost. Download links: http://www.peach.ne.jp/archives/isboot/isboot-0.1.3.tar.gz Download links(for testing purpose only): http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-amd64-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-i386-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh I hope this helps you. Enjoy it. Daisuke Aoyama From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 03:07:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 244F4106564A; Sun, 27 Jun 2010 03:07:49 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (unknown [IPv6:2001:380:e06:127::53]) by mx1.freebsd.org (Postfix) with ESMTP id BAB368FC14; Sun, 27 Jun 2010 03:07:48 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 3624A78C3B; Sun, 27 Jun 2010 12:07:48 +0900 (JST) Received: from artemis (unknown [192.168.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTP id 26E1B78C34; Sun, 27 Jun 2010 12:07:48 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: "Vincent Hoffman" References: <1931AE1113EC4A8983B8A52A2A1966C2@ad.peach.ne.jp> <4C2531FD.8050605@unsane.co.uk> In-Reply-To: <4C2531FD.8050605@unsane.co.uk> Date: Sun, 27 Jun 2010 12:06:47 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: iSCSI boot driver version 0.1.1 for iBFT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 03:07:49 -0000 Vincent Hoffman, wrote: > Since I dont have a supported nic, would the iscsi support in gpxe > (http://etherboot.org/wiki/iscsiboot) > be enough? (might give it a try if i get time after the weekend.) Yes. gPXE + istgt can be used. I have confirmed with Windows before. Now I tested with FreeBSD 8.1+isboot0.1.3 (integrated). If you use integrated version, you can install FreeBSD to iSCSI target, mentioned in http://www.etherboot.org/wiki/sanboot/iscsi_install. There is the log of my old machine which have Intel Fast Ether onboard. (use gPXE1.0.0 FD + FreeBSD-8.1-RC1-i386-isboot-0.1.3.iso) gPXE 1.0.0 "Customize image configuration options" (static IP): --------------------------------------------------------------- #!gpxe ifopen net0 set net0/initiator-iqn iqn.2000-09.org.etherboot:gpxe-fbs8 set net0/ip 192.168.2.224 set net0/netmask 255.255.255.0 set net0/gateway 192.168.2.1 set net0/dns 192.168.2.1 set keep-san 1 sanboot iscsi:192.168.2.36::::iqn.2007-09.jp.ne.peach:isboot-gpxe --------------------------------------------------------------- istgt.conf: --------------------------------------------------------------- [InitiatorGroup97] Comment "Initiator Group97" InitiatorName "iqn.2000-09.org.etherboot:gpxe-fbs8" Netmask 192.168.2.0/24 [LogicalUnit97] Comment "iSCSI Boot Disk3" TargetName "iqn.2007-09.jp.ne.peach:isboot-gpxe" Mapping PortalGroup4 InitiatorGroup97 AuthMethod Auto UseDigest Auto UnitType Disk #QueueDepth 64 # FreeBSD 8.1 gPXE 1.0.0 LUN0 Storage /tank/iscsiz/istgt-boot-gpxe 16GB --------------------------------------------------------------- dmesg: --------------------------------------------------------------- iSCSI boot driver version 0.1.3 IS: Initiator name: iqn.2000-09.org.etherboot:gpxe-fbs8 NIC0: IP address: 192.168.2.224 NIC0: Prefix: 24 NIC0: Gateway: 192.168.2.1 NIC0: MAC address: 00:10:dc:55:5d:a1 TGT0: Target IP address: 192.168.2.36 TGT0: Target Port: 3260 TGT0: Target LUN: 0 TGT0: Target name: iqn.2007-09.jp.ne.peach:isboot-gpxe Boot NIC: fxp0 Configure IPv4 by NIC0 Attempting to login to iSCSI target and scan all LUNs. ... cut ... da0 at isboot0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 16384MB (33554432 512 byte sectors: 255H 63S/T 2088C) ... cut ... Boot device: da0 --------------------------------------------------------------- some results: --------------------------------------------------------------- # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 507630 173014 294006 37% / devfs 1 1 0 100% /dev /dev/da0s1e 507630 12 467008 0% /tmp /dev/da0s1f 12744762 705772 11019410 6% /usr /dev/da0s1d 1500046 294 1379750 0% /var # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) # diskinfo -v da0 da0 512 # sectorsize 17179869184 # mediasize in bytes (16G) 33554432 # mediasize in sectors 0 # stripesize 0 # stripeoffset 2088 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. 10000097 # Disk ident. # ifconfig -a fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:10:dc:00:45:4e ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.10.dc.56.0.0.45.4e.a.2.ff.fe.0.0.0.0 fxp0: flags=8843 metric 0 mtu 1500 options=2009 ether 00:10:dc:55:5d:a1 inet 192.168.2.224 netmask 0xffffff00 broadcast 192.168.2.255 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 nd6 options=3 # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 192.168.2.1 UGS 0 1 fxp0 127.0.0.1 link#4 UH 0 2 lo0 192.168.2.0/24 link#3 U 2 11391 fxp0 192.168.2.224 link#3 UHS 0 16 lo0 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%lo0/64 link#4 U lo0 fe80::1%lo0 link#4 UHS lo0 ff01:4::/32 fe80::1%lo0 U lo0 ff02::%lo0/32 fe80::1%lo0 U lo0 --------------------------------------------------------------- Notes: You have to configure DNS (/etc/resolv.conf) and hostname manually. Or must set exactly matched IP/mask/route in iBFT by sysinstall. This is current limitation. (sysintall breaks booted NIC parameter.) -- Daisuke Aoyama From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 08:36:53 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B6631065670 for ; Sun, 27 Jun 2010 08:36:53 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (gate6.infracaninophile.co.uk [IPv6:2001:8b0:151:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 9AFE68FC13 for ; Sun, 27 Jun 2010 08:36:52 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o5R8ajPD022710 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 27 Jun 2010 09:36:45 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4C270D9C.3000801@infracaninophile.co.uk> Date: Sun, 27 Jun 2010 09:36:44 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Matthew Lear References: <1276889330.2210.44.camel@almscliff.bubblegen.co.uk> <1277155992.1860.3.camel@almscliff.bubblegen.co.uk> <20100622074541.GA71157@icarus.home.lan> <82A96ECD-676C-4A4D-A328-0CFAABD64D50@gid.co.uk> <1277401934.1874.12.camel@almscliff.bubblegen.co.uk> <20100624181535.GA58443@icarus.home.lan> <1277417182.1874.30.camel@almscliff.bubblegen.co.uk> <20100625071644.GA75910@icarus.home.lan> <1277567868.1870.21.camel@almscliff.bubblegen.co.uk> <20100626171251.GA26022@icarus.home.lan> <1277593488.1884.107.camel@almscliff.bubblegen.co.uk> In-Reply-To: <1277593488.1884.107.camel@almscliff.bubblegen.co.uk> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.96.1 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_40,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: Adam Vande More , freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: 7.2-RELEASE-p4, IO errors & RAID1 failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 08:36:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/06/2010 24:04:48, Matthew Lear wrote: > Incidentally, is there a way to easily migrate from a atacontrol created > array to a gmirror created array? I'm running FreeBSD 8.0 on another > machine with a gmirror created RAID1 array with no problem whatsoever (I > chose gmirror as the choice for this machine over atacontrol after > reading various postings about software RAID under recent releases of > FreeBSD). I was planning on upgrading the 7.2 machine to 8.0-RC1 anyway > so if I could easily move to using gmirror then I would. That said, > atacontrol should (I assume) function correctly with 8.x, shouldn't it, > or is support of it dwindling somewhat? So long as your ataraid setup is a simple mirror, this is actually quite easy. Lets assume you have two identical disks, ad0 and ad2 from which you create a RAID ar0. To switch over to gmirror based RAID: * Edit /etc/fstab changing all references to ar0 to read ad0, so eg. change: /dev/ar0s1a / ufs rw 1 1 to read: /dev/ad0s1a / ufs rw 1 1 and similarly for any other partitions on ar0 (don't forget the swap area) * Edit /boot/loader.conf to load the necessary gmirror kernel modules add: geom_mirror_load="YES" * Reboot If necessary, drop into the system BIOS and make sure that which ever drive corresponding to your ad0 is set as the primary drive to boot from. This should bring your system up on just your ad0 drive -- so no resilience for a few minutes. (Effectively, you're back at the default system on a single disk layout now) * Delete the old ar0 RAID: # atacontrol delete ar0 This should have no effect on the running system as all it does is remove some meta-data stored on the disk. * Configure a new geom mirror device. You need to know the sysctl magic to let you futz with a mounted drive: # sysctl kern.geom.debugflags=16 # gmirror label -v -b load gm0 /dev/ad0 (If you're a fan of the classic article on OnLamp http://onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html) which recommends using round-robin as the balancing algorithm: that's fine as well, but 'load' as a mechanism wasn't available when that article was written, and it is generally recognised as superior nowadays.) * Re-edit /etc/fstab to change all references from ad0 to mirror/gm0 so eg. change: /dev/ad0s1a / ufs rw 1 1 to: /dev/mirror/gm0s1a / ufs rw 1 1 and similarly for any other partitions on ad0 * Reboot. You should see messages towards the end of the kernel initialisation sequence saying gmirror raid created successfully. * Now add your second drive to the mirror: # gmirror insert gm0 /dev/ad2 * The system will spend some time synchronizing the data from ad0 to ad0 -- the system can be put back into use immediately if needed, but it's better to let the resynch finish first, as you won't be resilient until it has. Also, active disk use will slow down the synchronisation process. Monitor synchronisation progress by 'gmirror status gm0' or by running gstat(8). * Once everything is synch'd it's all ready for immediate use. > How easy is it to upgrade an array to use larger disks - atacontrol or > gmirror? Feel free to respond with RTFM :-) I suppose one possible > solution would be to use something like GpartEd (example Linux land > tool) to grow a certain partition on an array (eg the partition mounted > on /usr/local). That way both partitions on each of the separate array > subdisks would be grown transparently since the operation would be > performed on partition ar0s1 (ie, taken care of by atacontrol / > gmirror). gmirror doesn't really help you with resizing disks or filesystems. Note the the recipe above assumes you want to mirror the entire contents of one disk onto another -- which is the usual idea for the system drive used by a server -- so ideally you want two identical drives. If one of your drives fails and you need to replace it, but can't get the exact same model, you will have to use a *bigger* drive -- ie. a larger number of sectors. Be wary when buying, as disks of different models but with nominally the same capacity can easily vary by a few thousand sectors. Anyhow, it is certainly possible to replace one of the drives in a gmirror setup with another of much larger capacity, synchronise the drives, then replace the second drive with a similar larger one and synchronise back again. If you have hot-swap capability, you can do all that without downtime. However, you will end up with a system layout exactly the same size as the original disks. In order to grow the filesystems to fill the drives, you will have to do all sorts of high-risk invasive procedures to rewrite partition tables and run growfs(8) to expand your UFS filesystems to fill the available space. Note: you can't shrink UFS partitions easily -- generally you have to backup the data, and then delete and recreate the partition as a smaller size and restore the data. If you want to do this sort of migration from ar0 to a much bigger gmirror setup, probably the lowest risk, least effort route is to mount the two new drives on the system, configure a gmirror across the two, partition and create filesystems on the gmirror, use dump(8) and restore(8) to copy the filesystems from your live disks, then shutdown, take out the old ar0 disks and boot from the new gmirror. Remember you're going to have to fix /etc/fstab on the gmirror before rebooting. If you can't fit 4 drives in your system at once, then take out one drive (which will break the ar0 mirror), replace it with one of your new disks, build the gmirror on it as above, then shutdown, remove the 2nd ar0 drive, reboot, add the 2nd gmirror drive and resynch. If you really want to be able to resize partitions easily or swap out the hardware and have the system utilize the increased space without a great deal of faffing around, then ZFS is your friend. See: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror You should be able to adapt those instructions to install a ZFS system on some fresh drives attached to an existing system which uses atacontrol or gmirror raid + UFS rather than booting from installation media, or you can split your original mirror and build half a ZFS mirror in the space that creates, then resynch disks afterwards. It's more work to set up ZFS initially, but once it is done, it just ticks along happily and it makes any subsequent disk manipulations much easier and safer. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwnDZwACgkQ8Mjk52CukIzBmwCcC1bA1h0Ux80LuW+Ip4W6YKbn tcEAn14MxpNRBgUSIYfK6CRb5eF3WiT9 =oFID -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 09:16:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07783106566C for ; Sun, 27 Jun 2010 09:16:31 +0000 (UTC) (envelope-from matt@bubblegen.co.uk) Received: from relay.pcl-ipout01.plus.net (relay.pcl-ipout01.plus.net [212.159.7.99]) by mx1.freebsd.org (Postfix) with ESMTP id 686148FC1A for ; Sun, 27 Jun 2010 09:16:29 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAHKzJkxUXeb0/2dsb2JhbACDHZwQca1lj3iBKYFfBIEmcgQ Received: from outmx03.plus.net ([84.93.230.244]) by relay.pcl-ipout01.plus.net with ESMTP; 27 Jun 2010 10:16:28 +0100 Received: from bubblegen.plus.com ([80.229.236.194] helo=[192.136.1.18]) by outmx03.plus.net with esmtp (Exim) id 1OSnyW-0007Rn-61; Sun, 27 Jun 2010 10:16:28 +0100 From: Matthew Lear To: Matthew Seaman In-Reply-To: <4C270D9C.3000801@infracaninophile.co.uk> References: <1276889330.2210.44.camel@almscliff.bubblegen.co.uk> <1277155992.1860.3.camel@almscliff.bubblegen.co.uk> <20100622074541.GA71157@icarus.home.lan> <82A96ECD-676C-4A4D-A328-0CFAABD64D50@gid.co.uk> <1277401934.1874.12.camel@almscliff.bubblegen.co.uk> <20100624181535.GA58443@icarus.home.lan> <1277417182.1874.30.camel@almscliff.bubblegen.co.uk> <20100625071644.GA75910@icarus.home.lan> <1277567868.1870.21.camel@almscliff.bubblegen.co.uk> <20100626171251.GA26022@icarus.home.lan> <1277593488.1884.107.camel@almscliff.bubblegen.co.uk> <4C270D9C.3000801@infracaninophile.co.uk> Content-Type: text/plain; charset="UTF-8" Date: Sun, 27 Jun 2010 10:16:27 +0100 Message-ID: <1277630187.1832.2.camel@almscliff.bubblegen.co.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Cc: Adam Vande More , freebsd-stable@freebsd.org, Jeremy Chadwick Subject: Re: 7.2-RELEASE-p4, IO errors & RAID1 failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 09:16:31 -0000 On Sun, 2010-06-27 at 09:36 +0100, Matthew Seaman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 27/06/2010 24:04:48, Matthew Lear wrote: > > Incidentally, is there a way to easily migrate from a atacontrol created > > array to a gmirror created array? I'm running FreeBSD 8.0 on another > > machine with a gmirror created RAID1 array with no problem whatsoever (I > > chose gmirror as the choice for this machine over atacontrol after > > reading various postings about software RAID under recent releases of > > FreeBSD). I was planning on upgrading the 7.2 machine to 8.0-RC1 anyway > > so if I could easily move to using gmirror then I would. That said, > > atacontrol should (I assume) function correctly with 8.x, shouldn't it, > > or is support of it dwindling somewhat? > > So long as your ataraid setup is a simple mirror, this is actually quite > easy. > > Lets assume you have two identical disks, ad0 and ad2 from which you > create a RAID ar0. To switch over to gmirror based RAID: > > * Edit /etc/fstab changing all references to ar0 to read ad0, so > eg. change: > /dev/ar0s1a / ufs rw 1 1 > to read: > /dev/ad0s1a / ufs rw 1 1 > > and similarly for any other partitions on ar0 (don't forget the > swap area) > > * Edit /boot/loader.conf to load the necessary gmirror kernel modules > add: > geom_mirror_load="YES" > > * Reboot > If necessary, drop into the system BIOS and make sure that which > ever drive corresponding to your ad0 is set as the primary drive > to boot from. > > This should bring your system up on just your ad0 drive -- so no > resilience for a few minutes. > > (Effectively, you're back at the default system on a single > disk layout now) > > * Delete the old ar0 RAID: > # atacontrol delete ar0 > > This should have no effect on the running system as all it does > is remove some meta-data stored on the disk. > > * Configure a new geom mirror device. You need to know the sysctl > magic to let you futz with a mounted drive: > # sysctl kern.geom.debugflags=16 > # gmirror label -v -b load gm0 /dev/ad0 > > (If you're a fan of the classic article on OnLamp > http://onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html) which > recommends using round-robin as the balancing algorithm: that's > fine as well, but 'load' as a mechanism wasn't available when > that article was written, and it is generally recognised as > superior nowadays.) > > * Re-edit /etc/fstab to change all references from ad0 to mirror/gm0 > so eg. change: > /dev/ad0s1a / ufs rw 1 1 > to: > /dev/mirror/gm0s1a / ufs rw 1 1 > > and similarly for any other partitions on ad0 > > * Reboot. You should see messages towards the end of the kernel > initialisation sequence saying gmirror raid created successfully. > > * Now add your second drive to the mirror: > # gmirror insert gm0 /dev/ad2 > > * The system will spend some time synchronizing the data from ad0 to > ad0 -- the system can be put back into use immediately if needed, > but it's better to let the resynch finish first, as you won't be > resilient until it has. Also, active disk use will slow down the > synchronisation process. Monitor synchronisation progress by > 'gmirror status gm0' or by running gstat(8). > > * Once everything is synch'd it's all ready for immediate use. > > > How easy is it to upgrade an array to use larger disks - atacontrol or > > gmirror? Feel free to respond with RTFM :-) I suppose one possible > > solution would be to use something like GpartEd (example Linux land > > tool) to grow a certain partition on an array (eg the partition mounted > > on /usr/local). That way both partitions on each of the separate array > > subdisks would be grown transparently since the operation would be > > performed on partition ar0s1 (ie, taken care of by atacontrol / > > gmirror). > > gmirror doesn't really help you with resizing disks or filesystems. > Note the the recipe above assumes you want to mirror the entire contents > of one disk onto another -- which is the usual idea for the system drive > used by a server -- so ideally you want two identical drives. If one of > your drives fails and you need to replace it, but can't get the exact > same model, you will have to use a *bigger* drive -- ie. a larger number > of sectors. Be wary when buying, as disks of different models but with > nominally the same capacity can easily vary by a few thousand sectors. > > Anyhow, it is certainly possible to replace one of the drives in a > gmirror setup with another of much larger capacity, synchronise the > drives, then replace the second drive with a similar larger one and > synchronise back again. If you have hot-swap capability, you can do all > that without downtime. However, you will end up with a system layout > exactly the same size as the original disks. In order to grow the > filesystems to fill the drives, you will have to do all sorts of > high-risk invasive procedures to rewrite partition tables and run > growfs(8) to expand your UFS filesystems to fill the available space. > Note: you can't shrink UFS partitions easily -- generally you have to > backup the data, and then delete and recreate the partition as a smaller > size and restore the data. > > If you want to do this sort of migration from ar0 to a much bigger > gmirror setup, probably the lowest risk, least effort route is to mount > the two new drives on the system, configure a gmirror across the two, > partition and create filesystems on the gmirror, use dump(8) and > restore(8) to copy the filesystems from your live disks, then shutdown, > take out the old ar0 disks and boot from the new gmirror. Remember > you're going to have to fix /etc/fstab on the gmirror before rebooting. > > If you can't fit 4 drives in your system at once, then take out one > drive (which will break the ar0 mirror), replace it with one of your new > disks, build the gmirror on it as above, then shutdown, remove the 2nd > ar0 drive, reboot, add the 2nd gmirror drive and resynch. > > If you really want to be able to resize partitions easily or swap out > the hardware and have the system utilize the increased space without a > great deal of faffing around, then ZFS is your friend. See: > > http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror > > You should be able to adapt those instructions to install a ZFS system > on some fresh drives attached to an existing system which uses > atacontrol or gmirror raid + UFS rather than booting from installation > media, or you can split your original mirror and build half a ZFS mirror > in the space that creates, then resynch disks afterwards. > > It's more work to set up ZFS initially, but once it is done, it just > ticks along happily and it makes any subsequent disk manipulations much > easier and safer. > Excellent info, Matthew. Thank you very much indeed. From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 21:23:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B16C4106564A for ; Sun, 27 Jun 2010 21:23:19 +0000 (UTC) (envelope-from bsd@nezmer.info) Received: from mail.nezmer.info (nezmer.info [97.107.142.36]) by mx1.freebsd.org (Postfix) with ESMTP id 9607F8FC1C for ; Sun, 27 Jun 2010 21:23:19 +0000 (UTC) Date: Mon, 28 Jun 2010 00:23:15 +0300 From: Nezmer To: freebsd-stable@freebsd.org Message-ID: <20100627212315.GA3002@mail> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: zfsboot: geom_mbr.ko does not populate logical partitions correctly X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 21:23:19 -0000 Hi, I moved my installation to a ZFS boot partition today (ad6s1a). I had an ext2 logical partition living inside slice 4 (ad6s4). "geom_mbr.ko" used to take care of that and populate (ad6s[5-9]) and the correct entry under "/dev/ext2fs/". Now with zfsboot, weird entries (ad6s4s{1,2,5}) are populated and no correct entry under "/dev/ext2fs/" is present. Non of those weird entries represent the ext2 partition. I still have an identical UFS installation in (ad6s3a) that is still working correctly. Any ideas how to fix this? From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 22:42:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A2FF106564A for ; Sun, 27 Jun 2010 22:42:50 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 9A6FB8FC13 for ; Sun, 27 Jun 2010 22:42:49 +0000 (UTC) Received: (qmail 37613 invoked by uid 2000); 27 Jun 2010 22:16:07 -0000 Date: Sun, 27 Jun 2010 17:16:07 -0500 From: "Rick C. Petty" To: freebsd-stable@freebsd.org Message-ID: <20100627221607.GA31646@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 22:42:50 -0000 First off, many thanks to Rick Macklem for making NFSv4 possible in FreeBSD! I recently updated my NFS server and clients to v4, but have since noticed significant performance penalties. For instance, when I try "ls a b c" (if a, b, and c are empty directories) on the client, it takes up to 1.87 seconds (wall time) whereas before it always finished in under 0.1 seconds. If I repeat the test, it takes the same amount of time in v4 (in v3, wall time was always under 0.01 seconds for subsequent requests, as if the directory listing was cached). If I try to play an h264 video file on the filesystem using mplayer, it often jitters and skipping around in time introduces up to a second or so pause. With NFSv3 it behaved more like the file was on local disk (no noticable pauses or jitters). Has anyone seen this behavior upon switching to v4 or does anyone have any suggestions for tuning? Both client and server are running the same GENERIC kernel, 8.1-PRERELEASE as of 2010-May-29. They are connected via gigabit. Both v3 and v4 tests were performed on the exact same hardware and I/O, CPU, network loads. All I did was toggle nfsv4_server_enable (and nfsuserd/nfscbd of course). It seems like a server-side issue, because if I try an nfs3 client mount to the nfs4 server and run the same tests, I see only a slight improvement in performance. In both cases, my mount options were "rdirplus,bg,intr,soft" (and "nfsv4" added in the one case, obviously). On the server, I have these tunables explicitly set: kern.ipc.maxsockbuf=524288 vfs.newnfs.issue_delegations=1 On the client, I just have the maxsockbuf setting (this is twice the default value). I'm open to trying other tunables or patches. TIA, -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Sun Jun 27 23:47:39 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 881351065670 for ; Sun, 27 Jun 2010 23:47:39 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3DE478FC18 for ; Sun, 27 Jun 2010 23:47:38 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAFp/J0yDaFvK/2dsb2JhbACfK3G+A4J4AQSCJwQ X-IronPort-AV: E=Sophos;i="4.53,493,1272859200"; d="scan'208";a="82070765" Received: from fraser.cs.uoguelph.ca ([131.104.91.202]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 27 Jun 2010 19:47:36 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id 4A823109C2E9; Sun, 27 Jun 2010 19:47:38 -0400 (EDT) X-Virus-Scanned: amavisd-new at fraser.cs.uoguelph.ca Received: from fraser.cs.uoguelph.ca ([127.0.0.1]) by localhost (fraser.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1aWkmJ2Yi2L; Sun, 27 Jun 2010 19:47:37 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by fraser.cs.uoguelph.ca (Postfix) with ESMTP id AE1B6109C2B2; Sun, 27 Jun 2010 19:47:37 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5S04Sn04933; Sun, 27 Jun 2010 20:04:29 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Sun, 27 Jun 2010 20:04:28 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100627221607.GA31646@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2010 23:47:39 -0000 On Sun, 27 Jun 2010, Rick C. Petty wrote: > First off, many thanks to Rick Macklem for making NFSv4 possible in > FreeBSD! > > I recently updated my NFS server and clients to v4, but have since noticed > significant performance penalties. For instance, when I try "ls a b c" (if > a, b, and c are empty directories) on the client, it takes up to 1.87 > seconds (wall time) whereas before it always finished in under 0.1 seconds. > If I repeat the test, it takes the same amount of time in v4 (in v3, wall > time was always under 0.01 seconds for subsequent requests, as if the > directory listing was cached). > Weird, I don't see that here. The only thing I can think of is that the experimental client/server will try to do I/O at the size of MAXBSIZE by default, which might be causing a burst of traffic your net interface can't keep up with. (This can be turned down to 32K via the rsize=32768,wsize=32768 mount options. I found this necessary to avoid abissmal performance on some Macs for the Mac OS X port.) The other thing that can really slow it down is if the uid<->login-name (and/or gid<->group-name) is messed up, but this would normally only show up for things like "ls -l". (Beware having multiple password database entries for the same uid, such as "root" and "toor".) > If I try to play an h264 video file on the filesystem using mplayer, it > often jitters and skipping around in time introduces up to a second or so > pause. With NFSv3 it behaved more like the file was on local disk (no > noticable pauses or jitters). > > Has anyone seen this behavior upon switching to v4 or does anyone have any > suggestions for tuning? > > Both client and server are running the same GENERIC kernel, 8.1-PRERELEASE > as of 2010-May-29. They are connected via gigabit. Both v3 and v4 tests > were performed on the exact same hardware and I/O, CPU, network loads. > All I did was toggle nfsv4_server_enable (and nfsuserd/nfscbd of course). > > It seems like a server-side issue, because if I try an nfs3 client mount > to the nfs4 server and run the same tests, I see only a slight improvement > in performance. In both cases, my mount options were > "rdirplus,bg,intr,soft" (and "nfsv4" added in the one case, obviously). > I don't recommend the use of "intr or soft" for NFSv4 mounts, but they wouldn't affect performance for trivial tests. You might want to try: "nfsv4,rsize=32768,wsize=32768" and see how that works. When you did the nfs3 mount did you specify "newnfs" or "nfs" for the file system type? (I'm wondering if you still saw the problem with the regular "nfs" client against the server? Others have had good luck using the server for NFSv3 mounts.) > On the server, I have these tunables explicitly set: > > kern.ipc.maxsockbuf=524288 > vfs.newnfs.issue_delegations=1 > > On the client, I just have the maxsockbuf setting (this is twice the > default value). I'm open to trying other tunables or patches. TIA, > When I see abissmal NFS perf. it is usually an issue with the underlying transport. Looking at things like "netstat -i" or "netstat -s" might give you a hint? Having said that, the only difference I can think of between the two NFS subsystems that might affect the transport layer is the default I/O size, as noted above. rick From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 01:19:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15DFF106566B for ; Mon, 28 Jun 2010 01:19:15 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id C20BB8FC16 for ; Mon, 28 Jun 2010 01:19:14 +0000 (UTC) Received: by vws13 with SMTP id 13so6792954vws.13 for ; Sun, 27 Jun 2010 18:19:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=Qo2BYzc2/bSBWb5LSL3WaPAHcNf5m0nVOzzdSVwhPRE=; b=hEtcHn56S3sTnbAbyA6mw9tF43heJjatlv051JDWCT5hGy51+2vAf0OQ+lN+ExMGXN fEA35Ju6tDMVIjShdDQ+FGb2i0X1jGAJhSn8o1yosLczhBAsfY/bpQ7doAmygJxh+VlD Bi1bm9b8iMuQOn5bmdkA6P8Ym4ruK9BCnfdNk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=d/TrCIfLWJQiyrPvc8gtI6BUYVfnJaY83NQgbCpbFCXAj1LEOaX6n20nSjvakTwIYX QT973LbHgBnQhU0jt26NtN54RGJSvjEckBDoTOXdEynpWYd6pCMg24utpgGMgydICxbb HR7O2qIpupOnfNpSao5GPswzt62poCISerlwE= MIME-Version: 1.0 Received: by 10.220.46.134 with SMTP id j6mr2479828vcf.24.1277686312000; Sun, 27 Jun 2010 17:51:52 -0700 (PDT) Received: by 10.220.18.84 with HTTP; Sun, 27 Jun 2010 17:51:51 -0700 (PDT) Date: Mon, 28 Jun 2010 08:51:51 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 01:19:15 -0000 Hello all, I just joined this mailing list because I don't know where to look for help. I hope someone can help me on my problem. I first installed FreeBSD 8.0 a few weeks after it was officially released. It was working fine and was able to upgrade it until 8.0-p3. The system was last rebooted maybe sometime on March 2010. Then I manually rebooted it and now, it is unable to boot. The machine is made up of an Intel D945GCLF2 with 1GB RAM and 1TB SATA HDD. This is my home server. Kindly check the screenshot at http://imagebin.org/102605 for the screen output during bootup. I don't know how to recover this system and hopefully someone could help me on how to do it. Thank you in advance. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 02:25:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EB46106564A for ; Mon, 28 Jun 2010 02:25:08 +0000 (UTC) (envelope-from A.J.Caines@halplant.com) Received: from triton.bsd-unix.net (triton.bsd-unix.net [209.8.43.226]) by mx1.freebsd.org (Postfix) with ESMTP id D737D8FC0A for ; Mon, 28 Jun 2010 02:25:07 +0000 (UTC) Received: from triton.bsd-unix.net (localhost [127.0.0.1]) by triton.bsd-unix.net (Postfix) with ESMTP id 47FAA9B42E for ; Sun, 27 Jun 2010 22:08:54 -0400 (EDT) X-Virus-Scanned: amavisd-new at bsd-unix.net Received: from triton.bsd-unix.net ([127.0.0.1]) by triton.bsd-unix.net (triton.bsd-unix.net.bsd-unix.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IjyH6X0gQlos for ; Sun, 27 Jun 2010 22:08:54 -0400 (EDT) Received: from hal10000.halplant.com (ip68-105-188-179.dc.dc.cox.net [68.105.188.179]) (Authenticated sender: ajc) by triton.bsd-unix.net (Postfix) with ESMTPSA id 1AA189B425 for ; Sun, 27 Jun 2010 22:08:54 -0400 (EDT) Message-ID: <4C280435.4060603@halplant.com> Date: Sun, 27 Jun 2010 22:08:53 -0400 From: "Andrew J. Caines" Organization: H.A.L. Plant User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100410 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 02:25:08 -0000 GNUbie, > Kindly check the screenshot at http://imagebin.org/102605 for the > screen output during bootup. I don't know how to recover this system > and hopefully someone could help me on how to do it. Can you boot the old kernel[1]? [1] See http://www.freebsd.org/doc/en/books/handbook/kernelconfig-trouble.html -- -Andrew J. Caines- Unix Systems Engineer A.J.Caines@halplant.com FreeBSD/Linux/Solaris, Web/Mail/Proxy/... http://halplant.com:2001/ "Machines take me by surprise with great frequency" - Alan Turing From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 03:14:02 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE71A106566B for ; Mon, 28 Jun 2010 03:14:02 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 4E0048FC17 for ; Mon, 28 Jun 2010 03:14:01 +0000 (UTC) Received: (qmail 45576 invoked by uid 2000); 28 Jun 2010 03:14:01 -0000 Date: Sun, 27 Jun 2010 22:14:01 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100628031401.GA45282@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 03:14:02 -0000 On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote: > > Weird, I don't see that here. The only thing I can think of is that the > experimental client/server will try to do I/O at the size of MAXBSIZE > by default, which might be causing a burst of traffic your net interface > can't keep up with. (This can be turned down to 32K via the > rsize=32768,wsize=32768 mount options. I found this necessary to avoid > abissmal performance on some Macs for the Mac OS X port.) Hmm. When I mounted the same filesystem with nfs3 from a different client, everything started working at almost normal speed (still a little slower though). Now on that same host I saw a file get corrupted. On the server, I see the following: % hd testfile | tail -4 00677fd0 2a 24 cc 43 03 90 ad e2 9a 4a 01 d9 c4 6a f7 14 |*$.C.....J...j..| 00677fe0 3f ba 01 77 28 4f 0f 58 1a 21 67 c5 73 1e 4f 54 |?..w(O.X.!g.s.OT| 00677ff0 bf 75 59 05 52 54 07 6f db 62 d6 4a 78 e8 3e 2b |.uY.RT.o.b.Jx.>+| 00678000 But on the client I see this: % hd testfile | tail -4 00011ff0 1e af dc 8e d6 73 67 a2 cd 93 fe cb 7e a4 dd 83 |.....sg.....~...| 00012000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00678000 The only thing I could do to fix it was to copy the file on the server, delete the original file on the client, and move the copied file back. Not only is it affecting random file reads, but started breaking src and ports builds in random places. In one situation, portmaster failed because of a port checksum. It then tried to refetch and failed with the same checksum problem. I manually deleted the file, tried again and it built just fine. The ports tree and distfiles are nfs4 mounted. > The other thing that can really slow it down is if the uid<->login-name > (and/or gid<->group-name) is messed up, but this would normally only > show up for things like "ls -l". (Beware having multiple password database > entries for the same uid, such as "root" and "toor".) I use the same UIDs/GIDs on all my boxes, so that can't be it. But thanks for the idea. > I don't recommend the use of "intr or soft" for NFSv4 mounts, but they > wouldn't affect performance for trivial tests. You might want to try: > "nfsv4,rsize=32768,wsize=32768" and see how that works. I'm trying that right now (with rdirplus also) on one host. If I start to the delays again, I'll compare between hosts. > When you did the nfs3 mount did you specify "newnfs" or "nfs" for the > file system type? (I'm wondering if you still saw the problem with the > regular "nfs" client against the server? Others have had good luck using > the server for NFSv3 mounts.) I used "nfs" for FStype. So I should be using "newnfs"? This wasn't very clear in the man pages. In fact "newnfs" wasn't mentioned in "man mount_newnfs". > When I see abissmal NFS perf. it is usually an issue with the underlying > transport. Looking at things like "netstat -i" or "netstat -s" might > give you a hint? I suspected it might be transport-related. I didn't see anything out of the ordinary from netstat, but then again I don't know what's "ordinary" with NFS. =) ~~ One other thing I noticed but I'm not sure if it's a bug or expected behavior (unrelated to the delays or corruption), is I have the following filesystems on the server: /vol/a /vol/a/b /vol/a/c I export all three volumes and set my NFS V4 root to "/". On the client, I'll "mount ... server:vol /vol" and the "b" and "c" directories show up but when I try "ls /vol/a/b /vol/a/c", they show up empty. In dmesg I see: kernel: nfsv4 client/server protocol prob err=10020 After unmounting /vol, I discovered that my client already had /vol/a/b and /vol/a/c directories (because pre-NFSv4, I had to mount each filesystem separately). Once I removed those empty dirs and remounted, the problem went away. But it did drive me crazy for a few hours. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 03:47:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D977A106566B for ; Mon, 28 Jun 2010 03:47:42 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 632328FC14 for ; Mon, 28 Jun 2010 03:47:42 +0000 (UTC) Received: (qmail 45805 invoked by uid 2000); 28 Jun 2010 03:47:41 -0000 Date: Sun, 27 Jun 2010 22:47:41 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100628034741.GA45748@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628031401.GA45282@kay.kiwi-computer.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 03:47:42 -0000 On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote: > > Weird, I don't see that here. The only thing I can think of is that the > experimental client/server will try to do I/O at the size of MAXBSIZE > by default, which might be causing a burst of traffic your net interface > can't keep up with. (This can be turned down to 32K via the > rsize=32768,wsize=32768 mount options. I found this necessary to avoid > abissmal performance on some Macs for the Mac OS X port.) I just ran into the speed problem again after remounting. This time I tried to do a "make buildworld" and make got stuck on [newnfsreq] for ten minutes, with no other filesystem activity on either client or server. The file system corruption is still pretty bad. I can no longer build any ports on one machine, because after the port is extracted, the config.sub files are being filled with all zeros. It took me awhile to track this down while trying to build devel/libtool22: + ac_build_alias=amd64-portbld-freebsd8.1 + test xamd64-portbld-freebsd8.1 = x + test xamd64-portbld-freebsd8.1 = x + /bin/sh libltdl/config/config.sub amd64-portbld-freebsd8.1 + ac_cv_build='' + printf '%s\n' 'configure:4596: result: ' + printf '%s\n' '' + as_fn_error 'invalid value of canonical build' 4600 5 + as_status=0 + test 0 -eq 0 + as_status=1 + test 5 And although my work dir is on local disk, % hd work/libtool-2.2.6b/libltdl/config/config.sub: 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00007660 Again, my ports tree is mounted as FSType nfs with option nfsv4. FreeBSD/amd64 8.1-PRERELEASE r208408M GENERIC kernel. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 04:13:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A8F5106564A for ; Mon, 28 Jun 2010 04:13:41 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id E28E78FC12 for ; Mon, 28 Jun 2010 04:13:40 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAKO+J0yDaFvI/2dsb2JhbACfKnG+HYJ4AQSCJwQ X-IronPort-AV: E=Sophos;i="4.53,494,1272859200"; d="scan'208";a="82085618" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 00:13:37 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id DA0E6940099; Mon, 28 Jun 2010 00:13:39 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vmaLMeAi6aJK; Mon, 28 Jun 2010 00:13:38 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 81839940076; Mon, 28 Jun 2010 00:13:38 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5S4UUk04846; Mon, 28 Jun 2010 00:30:30 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 00:30:30 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100628031401.GA45282@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 04:13:41 -0000 On Sun, 27 Jun 2010, Rick C. Petty wrote: > > Hmm. When I mounted the same filesystem with nfs3 from a different client, > everything started working at almost normal speed (still a little slower > though). > > Now on that same host I saw a file get corrupted. On the server, I see > the following: > > % hd testfile | tail -4 > 00677fd0 2a 24 cc 43 03 90 ad e2 9a 4a 01 d9 c4 6a f7 14 |*$.C.....J...j..| > 00677fe0 3f ba 01 77 28 4f 0f 58 1a 21 67 c5 73 1e 4f 54 |?..w(O.X.!g.s.OT| > 00677ff0 bf 75 59 05 52 54 07 6f db 62 d6 4a 78 e8 3e 2b |.uY.RT.o.b.Jx.>+| > 00678000 > > But on the client I see this: > > % hd testfile | tail -4 > 00011ff0 1e af dc 8e d6 73 67 a2 cd 93 fe cb 7e a4 dd 83 |.....sg.....~...| > 00012000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 00678000 > > The only thing I could do to fix it was to copy the file on the server, > delete the original file on the client, and move the copied file back. > > Not only is it affecting random file reads, but started breaking src > and ports builds in random places. In one situation, portmaster failed > because of a port checksum. It then tried to refetch and failed with the > same checksum problem. I manually deleted the file, tried again and it > built just fine. The ports tree and distfiles are nfs4 mounted. > I can't explain the corruption, beyond the fact that "soft,intr" can cause all sorts of grief. If mounts without "soft,intr" still show corruption problems, try disabling delegations (either kill off the nfscbd daemons on the client or set vfs.newnfs.issue_delegations=0 on the server). It is disabled by default because it is the "greenest" part of the subsystem. >> The other thing that can really slow it down is if the uid<->login-name >> (and/or gid<->group-name) is messed up, but this would normally only >> show up for things like "ls -l". (Beware having multiple password database >> entries for the same uid, such as "root" and "toor".) > > I use the same UIDs/GIDs on all my boxes, so that can't be it. But thanks > for the idea. > Make sure you don't have multiple entries for the same uid, such as "root" and "toor" both for uid 0 in your /etc/passwd. (ie. get rid of one of them, if you have both) > >> When you did the nfs3 mount did you specify "newnfs" or "nfs" for the >> file system type? (I'm wondering if you still saw the problem with the >> regular "nfs" client against the server? Others have had good luck using >> the server for NFSv3 mounts.) > > I used "nfs" for FStype. So I should be using "newnfs"? This wasn't very > clear in the man pages. In fact "newnfs" wasn't mentioned in > "man mount_newnfs". > When you specify "nfs" for an NFSv3 mount, you get the regular client. When you specify "newnfs" for an NFSv3 mount, you get the experimental client. When you specify "nfsv4" you always get the experimental NFS client, and it doesn't matter which FStype you've specified. > > One other thing I noticed but I'm not sure if it's a bug or expected > behavior (unrelated to the delays or corruption), is I have the following > filesystems on the server: > > /vol/a > /vol/a/b > /vol/a/c > > I export all three volumes and set my NFS V4 root to "/". On the client, > I'll "mount ... server:vol /vol" and the "b" and "c" directories show up > but when I try "ls /vol/a/b /vol/a/c", they show up empty. In dmesg I see: > If you are using UFS/FFS on the server, this should work and I don't know why the empty directories under /vol on the client confused it. If your server is using ZFS, everything from / including /vol need to be exported. > kernel: nfsv4 client/server protocol prob err=10020 > This error indicates that there wasn't a valid FH for the server. I suspect that the mount failed. (It does a loop of Lookups from "/" in the kernel during the mount and it somehow got confused part way through.) > After unmounting /vol, I discovered that my client already had /vol/a/b and > /vol/a/c directories (because pre-NFSv4, I had to mount each filesystem > separately). Once I removed those empty dirs and remounted, the problem > went away. But it did drive me crazy for a few hours. > I don't know why these empty dirs would confuse it. I'll try a test here, but I suspect the real problem was that the mount failed and then happened to succeed after you deleted the empty dirs. It still smells like some sort of transport/net interface/... issue is at the bottom of this. (see response to your next post) rick From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 04:18:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DE39106564A for ; Mon, 28 Jun 2010 04:18:24 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id D6AAB8FC1F for ; Mon, 28 Jun 2010 04:18:23 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAM+/J0yDaFvG/2dsb2JhbACfKnG+IoJSglIE X-IronPort-AV: E=Sophos;i="4.53,494,1272859200"; d="scan'208";a="82085820" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 00:18:20 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id E7A662101B3; Mon, 28 Jun 2010 00:18:22 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxzDAsnVeYHf; Mon, 28 Jun 2010 00:18:22 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 11385210136; Mon, 28 Jun 2010 00:18:22 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5S4ZE705399; Mon, 28 Jun 2010 00:35:14 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 00:35:14 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100628034741.GA45748@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 04:18:24 -0000 On Sun, 27 Jun 2010, Rick C. Petty wrote: > On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote: >> >> Weird, I don't see that here. The only thing I can think of is that the >> experimental client/server will try to do I/O at the size of MAXBSIZE >> by default, which might be causing a burst of traffic your net interface >> can't keep up with. (This can be turned down to 32K via the >> rsize=32768,wsize=32768 mount options. I found this necessary to avoid >> abissmal performance on some Macs for the Mac OS X port.) > > I just ran into the speed problem again after remounting. This time > I tried to do a "make buildworld" and make got stuck on [newnfsreq] for > ten minutes, with no other filesystem activity on either client or server. > Being stuck in "newnfsreq" means that it is trying to establish a TCP connection with the server (again smells like some networking issue). > The file system corruption is still pretty bad. I can no longer build any > ports on one machine, because after the port is extracted, the config.sub > files are being filled with all zeros. It took me awhile to track this > down while trying to build devel/libtool22: > Assuming your mounts are not using "soft,intr", I can't explain the corruption. Disabling delegations is the next step. (They aren't required for correct behaviour and are disabled by default because they are the "greenest" part of the implementation.) rick From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 04:58:55 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 099D6106564A for ; Mon, 28 Jun 2010 04:58:55 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [76.96.27.212]) by mx1.freebsd.org (Postfix) with ESMTP id E34838FC0C for ; Mon, 28 Jun 2010 04:58:54 +0000 (UTC) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta14.emeryville.ca.mail.comcast.net with comcast id bGeC1e0060b6N64AEGyuTU; Mon, 28 Jun 2010 04:58:54 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta03.emeryville.ca.mail.comcast.net with comcast id bGyt1e0033S48mS8PGytDe; Mon, 28 Jun 2010 04:58:54 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 0DE659B425; Sun, 27 Jun 2010 21:58:53 -0700 (PDT) Date: Sun, 27 Jun 2010 21:58:53 -0700 From: Jeremy Chadwick To: "Rick C. Petty" Message-ID: <20100628045852.GA75380@icarus.home.lan> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628034741.GA45748@kay.kiwi-computer.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 04:58:55 -0000 On Sun, Jun 27, 2010 at 10:47:41PM -0500, Rick C. Petty wrote: > On Sun, Jun 27, 2010 at 08:04:28PM -0400, Rick Macklem wrote: > > > > Weird, I don't see that here. The only thing I can think of is that the > > experimental client/server will try to do I/O at the size of MAXBSIZE > > by default, which might be causing a burst of traffic your net interface > > can't keep up with. (This can be turned down to 32K via the > > rsize=32768,wsize=32768 mount options. I found this necessary to avoid > > abissmal performance on some Macs for the Mac OS X port.) > > I just ran into the speed problem again after remounting. This time > I tried to do a "make buildworld" and make got stuck on [newnfsreq] for > ten minutes, with no other filesystem activity on either client or server. > > The file system corruption is still pretty bad. I can no longer build any > ports on one machine, because after the port is extracted, the config.sub > files are being filled with all zeros. It took me awhile to track this > down while trying to build devel/libtool22: > > + ac_build_alias=amd64-portbld-freebsd8.1 > + test xamd64-portbld-freebsd8.1 = x > + test xamd64-portbld-freebsd8.1 = x > + /bin/sh libltdl/config/config.sub amd64-portbld-freebsd8.1 > + ac_cv_build='' > + printf '%s\n' 'configure:4596: result: ' > + printf '%s\n' '' > > + as_fn_error 'invalid value of canonical build' 4600 5 > + as_status=0 > + test 0 -eq 0 > + as_status=1 > + test 5 > > And although my work dir is on local disk, > > % hd work/libtool-2.2.6b/libltdl/config/config.sub: > > 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > |................| > * > 00007660 > > Again, my ports tree is mounted as FSType nfs with option nfsv4. > FreeBSD/amd64 8.1-PRERELEASE r208408M GENERIC kernel. This sounds like NFSv4 is "tickling" some kind of bug in your NIC driver but I'm not entirely sure. Can you provide output from: 1) ifconfig -a (you can X out the IPs + MACs if you want) 2) netstat -m 3) vmstat -i 4) prtconf -lvc (only need the Ethernet-related entries) 5) sysctl dev.XXX.N (ex. for em0, XXX=em, N=0) And also check "dmesg" to see if there's any messages the kernel has been spitting out which look relevant? Thanks. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Mon Jun 28 06:16:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F8C11065672 for ; Mon, 28 Jun 2010 06:16:05 +0000 (UTC) (envelope-from alexs@ulgsm.ru) Received: from mail.ulgsm.ru (skuns.ulgsm.ru [93.93.136.26]) by mx1.freebsd.org (Postfix) with ESMTP id 158358FC12 for ; Mon, 28 Jun 2010 06:16:04 +0000 (UTC) Received: from mail.ulgsm.ru (localhost [127.0.0.1]) by mail.ulgsm.ru (Postfix) with ESMTP id 109183A548 for ; Mon, 28 Jun 2010 10:16:02 +0400 (MSD) X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on skuns.gsm900.net Received: from mail.ulgsm.ru (localhost [127.0.0.1]) by mail.ulgsm.ru (Postfix) with ESMTP id E86D23A541 for ; Mon, 28 Jun 2010 10:16:01 +0400 (MSD) Received: from mail.ulgsm.ru (bazar.gsm900.net [192.168.0.160]) by mail.ulgsm.ru (Postfix) with ESMTP id B5C103A536 for ; Mon, 28 Jun 2010 10:16:01 +0400 (MSD) Date: Mon, 28 Jun 2010 10:16:01 +0400 From: =?utf-8?B?0JrQu9GO0YfQvdC40LrQvtCyINCQLtChLg==?= To: freebsd-stable@freebsd.org Message-ID: <20100628061601.GA51359@mail.ulgsm.ru> References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 06:16:05 -0000 * Rick Macklem [2010-06-26 10:24:44 -0400]: > > > On Sat, 26 Jun 2010, alexs@ulgsm.ru wrote: > > [stuff snipped] > > > > > > dhcp seems ok. > > [alexs:ul-it13:~]>kenv > > LINES="24" > > acpi_load="YES" > > boot.netif.gateway="10.144.140.1" > > boot.netif.hwaddr="00:1c:c0:5a:f4:72" > > boot.netif.ip="10.144.142.78" > > boot.netif.netmask="255.255.252.0" > > boot.nfsroot.nfshandle="Xbb55e849c6f9fd520c000000011c0600c20af931000000000000000000000000X" > > boot.nfsroot.path="/exp/fbsd71" > > boot.nfsroot.server="10.144.140.160" > > .... > > > > It is from diskless host in same subnet where tftp and nfs server. > > > > Ok, this is when the server is on the same subnet and works ok. Am I > correct? Yes. > > > If i use server from over subnet, pxe cant load pxeboot, and kernel can`t > > mount boot.nfsroot.path="/exp/fbsd71". > > > > I thought you had said that you had gotten pxeboot to work across to > the other subnet and that it was the mount of "/" that then failed? > (It is that case where "boot.netif.gateway" needs to be checked to see > that it has the gateway for the client's subnet.) > > > About pxe google found http://www.appdeploy.com/faq/detail.asp?id=10 > > As i understand router must make ip helper. > > I seen it in cisco routers, not freebsd. > > > If you haven't been able to get pxeboot to work when the server is on > a different subnet, I'm afraid I can't help with that. Sorry. its my english.. There are two problem, first with pxeboot file downloading, and it not freebsd maillist subject. And second with mount root from nfs server in different subnet. I`ll try write again from anothe way. I have two subnets: 10.144.142.0/22 - here is tftp server and diskless. 10.144.130.0/24 - here is nfs server. in isc-dhcpd.conf: next-server 10.144.140.160; option root-path "10.144.130.160:/exp/fbsdstable"; In this case, pxeboot loading is ok, kernel loading from 10.144.130.160:/exp/fbsdstable ok too. booting freeze on: ... uhub3: 2 ports with 2 removable, self powered uhub4: 8 ports with 8 removable, self powered Received DHCP Offer packet on re0 from 10.144.140.160 (accepted) (no root path) Sending DHCP Request packet from interface re0 (00:1c:c0:5a:f4:72) Received DHCP Ack packet on re0 from 10.144.140.160 (accepted) (got root path) re0 at 10.144.142.78 server 10.144.130.160 server name DHCPserver boot file pxeboot subnet mask 255.255.252.0 router 10.144.140.1 rootfs 10.144.140.160:/exp/fbsdstable Adjusted interface re0 SMP: AP CPU #1 Launched! Trying to mount root from nfs: NFS ROOT: 10.144.130.160:/exp/fbsdstable Now diskless 8.1 PRERELEASE -- alexs From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 10:27:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B65C0106564A for ; Mon, 28 Jun 2010 10:27:07 +0000 (UTC) (envelope-from alexs@ulgsm.ru) Received: from mail.ulgsm.ru (skuns.ulgsm.ru [93.93.136.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5C5B58FC1B for ; Mon, 28 Jun 2010 10:27:06 +0000 (UTC) Received: from mail.ulgsm.ru (localhost [127.0.0.1]) by mail.ulgsm.ru (Postfix) with ESMTP id E77BA3B908 for ; Mon, 28 Jun 2010 14:27:03 +0400 (MSD) X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on skuns.gsm900.net Received: from mail.ulgsm.ru (localhost [127.0.0.1]) by mail.ulgsm.ru (Postfix) with ESMTP id CB3853B907 for ; Mon, 28 Jun 2010 14:27:03 +0400 (MSD) Received: from mail.ulgsm.ru (bazar.gsm900.net [192.168.0.160]) by mail.ulgsm.ru (Postfix) with ESMTP id 98B053B906 for ; Mon, 28 Jun 2010 14:27:03 +0400 (MSD) Date: Mon, 28 Jun 2010 14:27:03 +0400 From: alexs@ulgsm.ru To: freebsd-stable@freebsd.org Message-ID: <20100628102703.GA78354@mail.ulgsm.ru> References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628061601.GA51359@mail.ulgsm.ru> User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 10:27:07 -0000 * alexs@ulgsm.ru [2010-06-28 10:16:01 +0400]: > I have two subnets: > 10.144.142.0/22 - here is tftp server and diskless. > 10.144.130.0/24 - here is nfs server. > > in isc-dhcpd.conf: > next-server 10.144.140.160; > option root-path "10.144.130.160:/exp/fbsdstable"; > > > In this case, pxeboot loading is ok, kernel loading from > 10.144.130.160:/exp/fbsdstable ok too. > > booting freeze on: > ... > uhub3: 2 ports with 2 removable, self powered > uhub4: 8 ports with 8 removable, self powered > Received DHCP Offer packet on re0 from 10.144.140.160 (accepted) (no root path) > Sending DHCP Request packet from interface re0 (00:1c:c0:5a:f4:72) > Received DHCP Ack packet on re0 from 10.144.140.160 (accepted) (got root path) > re0 at 10.144.142.78 server 10.144.130.160 server name DHCPserver boot file pxeboot > subnet mask 255.255.252.0 router 10.144.140.1 rootfs 10.144.140.160:/exp/fbsdstable > Adjusted interface re0 > SMP: AP CPU #1 Launched! > Trying to mount root from nfs: > NFS ROOT: 10.144.130.160:/exp/fbsdstable > > > Now diskless 8.1 PRERELEASE > kernel built with: options BOOTP # Use BOOTP to obtain IP address/hostname options BOOTP_NFSROOT # NFS mount root file system using BOOTP info options BOOTP_NFSV3 -- alexs From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 13:56:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9923F106566B for ; Mon, 28 Jun 2010 13:56:23 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC948FC08 for ; Mon, 28 Jun 2010 13:56:22 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmQFAEhHKEyDaFvG/2dsb2JhbACSfYwyccA3hSQE X-IronPort-AV: E=Sophos;i="4.53,497,1272859200"; d="scan'208";a="81890813" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 09:56:09 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 7EC79210156; Mon, 28 Jun 2010 09:56:11 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KntGVKBXJWVh; Mon, 28 Jun 2010 09:56:10 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 30DC3210109; Mon, 28 Jun 2010 09:56:10 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5SED2s09358; Mon, 28 Jun 2010 10:13:02 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 10:13:02 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: alexs@ulgsm.ru In-Reply-To: <20100628102703.GA78354@mail.ulgsm.ru> Message-ID: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 13:56:23 -0000 On Mon, 28 Jun 2010, alexs@ulgsm.ru wrote: > > > kernel built with: > options BOOTP # Use BOOTP to obtain IP address/hostname > options BOOTP_NFSROOT # NFS mount root file system using BOOTP info > options BOOTP_NFSV3 > Try building a kernel without the above options, but with options NFS_ROOT specified. I think that's what most pxeboot users do and it was what I had assumed when I looked at the code. If that doesn't fix the problem...I haven't got a solution for you, rick From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 14:00:56 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79543106564A for ; Mon, 28 Jun 2010 14:00:56 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 088768FC08 for ; Mon, 28 Jun 2010 14:00:55 +0000 (UTC) Received: (qmail 52506 invoked by uid 2000); 28 Jun 2010 14:00:54 -0000 Date: Mon, 28 Jun 2010 09:00:54 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100628140054.GA52174@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 14:00:56 -0000 On Mon, Jun 28, 2010 at 12:30:30AM -0400, Rick Macklem wrote: > > I can't explain the corruption, beyond the fact that "soft,intr" can > cause all sorts of grief. If mounts without "soft,intr" still show > corruption problems, try disabling delegations (either kill off the > nfscbd daemons on the client or set vfs.newnfs.issue_delegations=0 > on the server). It is disabled by default because it is the "greenest" > part of the subsystem. I tried without soft,intr and "make buildworld" failed with what looks like file corruption again. I'm trying without delegations now. > Make sure you don't have multiple entries for the same uid, such as "root" > and "toor" both for uid 0 in your /etc/passwd. (ie. get rid of one of > them, if you have both) Hmm, that's a strange requirement, since FreeBSD by default comes with both. That should probably be documented in the nfsv4 man page. > When you specify "nfs" for an NFSv3 mount, you get the regular client. > When you specify "newnfs" for an NFSv3 mount, you get the experimental > client. When you specify "nfsv4" you always get the experimental NFS > client, and it doesn't matter which FStype you've specified. Ok. So my comparison was with the regular and experimental clients. > If you are using UFS/FFS on the server, this should work and I don't know > why the empty directories under /vol on the client confused it. If your > server is using ZFS, everything from / including /vol need to be exported. Nope, UFS2 only (on both clients and server). > > kernel: nfsv4 client/server protocol prob err=10020 > > This error indicates that there wasn't a valid FH for the server. I > suspect that the mount failed. (It does a loop of Lookups from "/" in > the kernel during the mount and it somehow got confused part way through.) If the mount failed, why would it allow me to "ls /vol/a" and see both "b" and "c" directories as well as other files/directories on /vol/ ? > I don't know why these empty dirs would confuse it. I'll try a test > here, but I suspect the real problem was that the mount failed and > then happened to succeed after you deleted the empty dirs. It doesn't seem likely. I spent an hour mounting and unmounting and each mount looked successful in that there were files and directories besides the two I was trying to decend into. > It still smells like some sort of transport/net interface/... issue > is at the bottom of this. (see response to your next post) It's possible. I just had another NFSv4 client (with the same server) lock up: load: 0.00 cmd: ls 17410 [nfsv4lck] 641.87r 0.00u 0.00s 0% 1512k and: load: 0.00 cmd: make 87546 [wait] 37095.09r 0.01u 0.01s 0% 844k That make has been hung for hours, and the ls(1) was executed during that lockup. I wish there was a way I could unhang these processes and unmount the NFS mount without panicking the kernel, but alas even this fails: # umount -f /sw load: 0.00 cmd: umount 17479 [nfsclumnt] 1.27r 0.00u 0.04s 0% 788k A "shutdown -p now" resulted in a panic with the speaker beeping constantly and no console output. It's possible the NICs are all suspect, but all of this worked fine a couple of days ago when I was only using NFSv3. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 14:20:26 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9897D1065672 for ; Mon, 28 Jun 2010 14:20:26 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 2F5488FC0A for ; Mon, 28 Jun 2010 14:20:25 +0000 (UTC) Received: (qmail 52718 invoked by uid 2000); 28 Jun 2010 14:20:25 -0000 Date: Mon, 28 Jun 2010 09:20:25 -0500 From: "Rick C. Petty" To: Jeremy Chadwick Message-ID: <20100628142025.GB52174@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628045852.GA75380@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628045852.GA75380@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 14:20:26 -0000 On Sun, Jun 27, 2010 at 09:58:53PM -0700, Jeremy Chadwick wrote: > > > > Again, my ports tree is mounted as FSType nfs with option nfsv4. > > FreeBSD/amd64 8.1-PRERELEASE r208408M GENERIC kernel. > > This sounds like NFSv4 is "tickling" some kind of bug in your NIC driver > but I'm not entirely sure. Can you provide output from: > > 1) ifconfig -a (you can X out the IPs + MACs if you want) On the NFSv4 server: nfe0: flags=8843 metric 0 mtu 1500 options=8010b ether 00:22:15:b4:2d:XX inet 172.XX.XX.4 netmask 0xffffff00 broadcast 172.XX.XX.255 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 nd6 options=3 On one of the clients: re0: flags=8843 metric 0 mtu 1500 options=389b ether e0:cb:4e:cd:d3:XX inet 172.XX.XX.9 netmask 0xffffff00 broadcast 172.XX.XX.255 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 nd6 options=3 > 2) netstat -m server: 1739/1666/3405 mbufs in use (current/cache/total) 257/1257/1514/25600 mbuf clusters in use (current/cache/total/max) 256/547 mbuf+clusters out of packet secondary zone in use (current/cache) 0/405/405/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 948K/4550K/5499K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines client: 264/2046/2310 mbufs in use (current/cache/total) 256/1034/1290/25600 mbuf clusters in use (current/cache/total/max) 256/640 mbuf+clusters out of packet secondary zone in use (current/cache) 3/372/375/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 590K/4067K/4657K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines > 3) vmstat -i Server: interrupt total rate irq1: atkbd0 24 0 irq18: atapci1 1883933 0 irq20: nfe0 ohci1 1712603504 793 cpu0: timer 4315963536 1999 irq256: hdac0 12 0 irq257: ahci0 139934363 64 cpu2: timer 4315960172 1999 cpu1: timer 4315960172 1999 cpu3: timer 4315960172 1999 Total 19118265888 8858 Client: interrupt total rate irq1: atkbd0 1063022 0 irq16: hdac0 16013959 6 irq17: atapci0+++ 6 0 irq18: ohci0 ohci1* 5324486 2 irq19: atapci1 7500968 2 irq20: ahc0 19 0 irq21: ahc1 112390 0 cpu0: timer 5125670841 1999 irq256: hdac1 2 0 irq257: re0 742537149 289 cpu1: timer 5125664297 1999 Total 11023887139 4301 > 4) prtconf -lvc (only need the Ethernet-related entries) I'll assume you meant to type "pciconf", on the server: nfe0@pci0:0:10:0: class=0x020000 card=0x82f21043 chip=0x076010de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'NForce Network Controller (MCP78 NIC)' class = network subclass = ethernet cap 01[44] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 16 messages, 64 bit, vector masks cap 08[6c] = HT MSI fixed address window disabled at 0xfee00000 client: re0@pci0:1:0:0: class=0x020000 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(256) link x1(x1) cap 11[b0] = MSI-X supports 4 messages in map 0x20 cap 03[d0] = VPD > 5) sysctl dev.XXX.N (ex. for em0, XXX=em, N=0) server: dev.nfe.0.%desc: NVIDIA nForce MCP77 Networking Adapter dev.nfe.0.%driver: nfe dev.nfe.0.%location: slot=10 function=0 handle=\_SB_.PCI0.NMAC dev.nfe.0.%pnpinfo: vendor=0x10de device=0x0760 subvendor=0x1043 subdevice=0x82f2 class=0x020000 dev.nfe.0.%parent: pci0 dev.nfe.0.process_limit: 192 dev.nfe.0.stats.rx.frame_errors: 0 dev.nfe.0.stats.rx.extra_bytes: 0 dev.nfe.0.stats.rx.late_cols: 0 dev.nfe.0.stats.rx.runts: 0 dev.nfe.0.stats.rx.jumbos: 0 dev.nfe.0.stats.rx.fifo_overuns: 0 dev.nfe.0.stats.rx.crc_errors: 0 dev.nfe.0.stats.rx.fae: 0 dev.nfe.0.stats.rx.len_errors: 0 dev.nfe.0.stats.rx.unicast: 1762645090 dev.nfe.0.stats.rx.multicast: 1 dev.nfe.0.stats.rx.broadcast: 7608 dev.nfe.0.stats.tx.octets: 2036479975330 dev.nfe.0.stats.tx.zero_rexmits: 2090186021 dev.nfe.0.stats.tx.one_rexmits: 0 dev.nfe.0.stats.tx.multi_rexmits: 0 dev.nfe.0.stats.tx.late_cols: 0 dev.nfe.0.stats.tx.fifo_underuns: 0 dev.nfe.0.stats.tx.carrier_losts: 0 dev.nfe.0.stats.tx.excess_deferrals: 0 dev.nfe.0.stats.tx.retry_errors: 0 dev.nfe.0.stats.tx.unicast: 0 dev.nfe.0.stats.tx.multicast: 0 dev.nfe.0.stats.tx.broadcast: 0 dev.nfe.0.wake: 0 client: c: RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet dev.re.0.%driver: re dev.re.0.%location: slot=0 function=0 dev.re.0.%pnpinfo: vendor=0x10ec device=0x8168 subvendor=0x1043 subdevice=0x8432 class=0x020000 dev.re.0.%parent: pci1 > check "dmesg" to see if there's any messages the kernel has > been spitting out which look relevant? Thanks. server, immediately after restarting all of nfs scripts (rpcbind nfsclient nfsuserd nfsserver mountd nfsd statd lockd nfscbd): Jun 27 18:04:44 rpcbind: cannot get information for udp6 Jun 27 18:04:44 rpcbind: cannot get information for tcp6 NLM: failed to contact remote rpcbind, stat = 5, port = 28416 Jun 27 18:05:12 amanda kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 client, when noticing the mounting-over-directories problem: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 nfsv4 client/server protocol prob err=10020 nfsv4 client/server protocol prob err=10020 ... No other related messages were found in /var/log/messages either. -- -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 14:22:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C37E11065673 for ; Mon, 28 Jun 2010 14:22:00 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 77CCD8FC25 for ; Mon, 28 Jun 2010 14:22:00 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1OTFDh-000OrT-LR; Mon, 28 Jun 2010 17:21:57 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Rick Macklem In-reply-to: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> Comments: In-reply-to Rick Macklem message dated "Mon, 28 Jun 2010 10:13:02 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jun 2010 17:21:57 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org, alexs@ulgsm.ru Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 14:22:00 -0000 > > > On Mon, 28 Jun 2010, alexs@ulgsm.ru wrote: > > > > > > > kernel built with: > > options BOOTP # Use BOOTP to obtain IP address/hostname > > options BOOTP_NFSROOT # NFS mount root file system using BOOTP info > > options BOOTP_NFSV3 > > > Try building a kernel without the above options, but with > options NFS_ROOT > specified. I think that's what most pxeboot users do and it was what > I had assumed when I looked at the code. > > If that doesn't fix the problem...I haven't got a solution for you, rick I use: options BOOTP_NFSV3 # Use NFS v3 to NFS mount root but the best advice I can give, on the server run tcpdump/wireshark it is very enlighting. danny From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 14:56:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C54D106564A for ; Mon, 28 Jun 2010 14:56:03 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 605778FC14 for ; Mon, 28 Jun 2010 14:56:02 +0000 (UTC) Received: from omta07.emeryville.ca.mail.comcast.net ([76.96.30.59]) by qmta07.emeryville.ca.mail.comcast.net with comcast id bQo71e0021GXsucA7Sw1lT; Mon, 28 Jun 2010 14:56:01 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta07.emeryville.ca.mail.comcast.net with comcast id bSw01e00Q3S48mS8USw1u2; Mon, 28 Jun 2010 14:56:01 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8AAEE9B425; Mon, 28 Jun 2010 07:56:00 -0700 (PDT) Date: Mon, 28 Jun 2010 07:56:00 -0700 From: Jeremy Chadwick To: "Rick C. Petty" Message-ID: <20100628145600.GA92144@icarus.home.lan> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628045852.GA75380@icarus.home.lan> <20100628142025.GB52174@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628142025.GB52174@kay.kiwi-computer.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 14:56:03 -0000 On Mon, Jun 28, 2010 at 09:20:25AM -0500, Rick C. Petty wrote: > > > > > > Again, my ports tree is mounted as FSType nfs with option nfsv4. > > > FreeBSD/amd64 8.1-PRERELEASE r208408M GENERIC kernel. > > > > This sounds like NFSv4 is "tickling" some kind of bug in your NIC driver > > but I'm not entirely sure. Can you provide output from: > > > > 1) ifconfig -a (you can X out the IPs + MACs if you want) > > > On one of the clients: > > re0: flags=8843 metric 0 mtu 1500 > options=389b > ether e0:cb:4e:cd:d3:XX > inet 172.XX.XX.9 netmask 0xffffff00 broadcast 172.XX.XX.255 > media: Ethernet autoselect (1000baseT ) > status: active > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=3 > > > 2) netstat -m > > server: > > 1739/1666/3405 mbufs in use (current/cache/total) > 257/1257/1514/25600 mbuf clusters in use (current/cache/total/max) > 256/547 mbuf+clusters out of packet secondary zone in use (current/cache) > 0/405/405/12800 4k (page size) jumbo clusters in use (current/cache/total/max) > 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) > 948K/4550K/5499K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/0/0 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > client: > > 264/2046/2310 mbufs in use (current/cache/total) > 256/1034/1290/25600 mbuf clusters in use (current/cache/total/max) > 256/640 mbuf+clusters out of packet secondary zone in use (current/cache) > 3/372/375/12800 4k (page size) jumbo clusters in use (current/cache/total/max) > 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) > 590K/4067K/4657K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/0/0 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > > 3) vmstat -i > > Server: > > interrupt total rate > irq1: atkbd0 24 0 > irq18: atapci1 1883933 0 > irq20: nfe0 ohci1 1712603504 793 > cpu0: timer 4315963536 1999 > irq256: hdac0 12 0 > irq257: ahci0 139934363 64 > cpu2: timer 4315960172 1999 > cpu1: timer 4315960172 1999 > cpu3: timer 4315960172 1999 > Total 19118265888 8858 > > Client: > > interrupt total rate > irq1: atkbd0 1063022 0 > irq16: hdac0 16013959 6 > irq17: atapci0+++ 6 0 > irq18: ohci0 ohci1* 5324486 2 > irq19: atapci1 7500968 2 > irq20: ahc0 19 0 > irq21: ahc1 112390 0 > cpu0: timer 5125670841 1999 > irq256: hdac1 2 0 > irq257: re0 742537149 289 > cpu1: timer 5125664297 1999 > Total 11023887139 4301 > > > 4) prtconf -lvc (only need the Ethernet-related entries) > > I'll assume you meant to type "pciconf", on the server: Yes sorry -- I spend my days at work dealing with Solaris (which is where where prtconf comes from :-) ). Three other things to provide output from if you could (you can X out IPs and MACs too), from both client and server: 6) netstat -idn 7) sysctl hw.pci | grep msi 8) Contents of /etc/sysctl.conf Thanks. > server, immediately after restarting all of nfs scripts (rpcbind > nfsclient nfsuserd nfsserver mountd nfsd statd lockd nfscbd): > > Jun 27 18:04:44 rpcbind: cannot get information for udp6 > Jun 27 18:04:44 rpcbind: cannot get information for tcp6 These two usually indicate you removed IPv6 support from the kernel, except your ifconfig output (I've remove it) on the server shows you do have IPv6 support. I've been trying to get these warnings removed for quite some time (PR kern/96242). They're harmless, but the inconsistency here is a little weird -- are you explicitly disabling IPv6 on nfe0? The remaining messages in your kernel log Rick can probably explain. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Mon Jun 28 15:18:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26A6B1065670 for ; Mon, 28 Jun 2010 15:18:37 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id BA1AB8FC18 for ; Mon, 28 Jun 2010 15:18:36 +0000 (UTC) Received: (qmail 53424 invoked by uid 2000); 28 Jun 2010 15:18:35 -0000 Date: Mon, 28 Jun 2010 10:18:35 -0500 From: "Rick C. Petty" To: Jeremy Chadwick Message-ID: <20100628151835.GA53315@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628045852.GA75380@icarus.home.lan> <20100628142025.GB52174@kay.kiwi-computer.com> <20100628145600.GA92144@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628145600.GA92144@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 15:18:37 -0000 On Mon, Jun 28, 2010 at 07:56:00AM -0700, Jeremy Chadwick wrote: > > Three other things to provide output from if you could (you can X out IPs > and MACs too), from both client and server: > > 6) netstat -idn server: Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop nfe0 1500 00:22:15:b4:2d:XX 1767890778 0 0 872169302 0 0 0 nfe0 1500 172.XX.XX.0/2 172.XX.XX.4 1767882158 - - 1964274616 - - - lo0 16384 3728 0 0 3728 0 0 0 lo0 16384 (28)00:00:00:00:00:00:fe:80:00:02:00:00:00:00:00:00:00:00:00:00:00:01 3728 0 0 3728 0 0 0 lo0 16384 (28)00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01 3728 0 0 3728 0 0 0 lo0 16384 127.0.0.0/8 127.0.0.1 3648 - - 3664 - - - client: Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll Drop re0 1500 e0:cb:4e:cd:d3:XX 955288523 0 0 696819089 0 0 0 re0 1500 172.XX.XX.0/2 172.XX.XX.2 955279721 - - 696814499 - - - lo0 16384 3148 0 0 3148 0 0 0 lo0 16384 (28)00:00:00:00:00:00:fe:80:00:02:00:00:00:00:00:00:00:00:00:00:00:01 3148 0 0 3148 0 0 0 lo0 16384 (28)00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01 3148 0 0 3148 0 0 0 lo0 16384 127.0.0.0/8 127.0.0.1 3112 - - 3112 - - - > 7) sysctl hw.pci | grep msi both server and client: hw.pci.honor_msi_blacklist: 1 hw.pci.enable_msix: 1 hw.pci.enable_msi: 1 > 8) Contents of /etc/sysctl.conf server and client: # 4 virtual channels dev.pcm.0.play.vchans=4 # Read modules from /usr/local/modules kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules # Remove those annoying ARP moved messages: net.link.ether.inet.log_arp_movements=0 # 32MB write cache on disk controllers system-wide vfs.hirunningspace=33554432 # Allow users to mount file systems vfs.usermount=1 # misc net.link.tap.user_open=1 net.inet.ip.forwarding=1 compat.linux.osrelease=2.6.16 debug.ddb.textdump.pending=1 # for NFSv4 kern.ipc.maxsockbuf=524288 > > server, immediately after restarting all of nfs scripts (rpcbind > > nfsclient nfsuserd nfsserver mountd nfsd statd lockd nfscbd): > > > > Jun 27 18:04:44 rpcbind: cannot get information for udp6 > > Jun 27 18:04:44 rpcbind: cannot get information for tcp6 > > These two usually indicate you removed IPv6 support from the kernel, > except your ifconfig output (I've remove it) on the server shows you do > have IPv6 support. I've been trying to get these warnings removed for > quite some time (PR kern/96242). They're harmless, but the > inconsistency here is a little weird -- are you explicitly disabling > IPv6 on nfe0? I have WITHOUT_IPV6= in my make.conf on all my machines (or I have problems with jdk1.6) and WITHOUT_INET6= in my src.conf. I'm not sure why the rpcbind/ifconfig binaries have a different concept than the kernel since I always "make buildworld kernel" and keep things in sync with mergemaster when I reboot. I'm building new worlds/kernels now to see if that makes any difference. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 15:35:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCE39106564A for ; Mon, 28 Jun 2010 15:35:28 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 530388FC1F for ; Mon, 28 Jun 2010 15:35:27 +0000 (UTC) Received: (qmail 53634 invoked by uid 2000); 28 Jun 2010 15:35:27 -0000 Date: Mon, 28 Jun 2010 10:35:27 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100628153527.GB53315@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 15:35:28 -0000 On Mon, Jun 28, 2010 at 12:35:14AM -0400, Rick Macklem wrote: > > Being stuck in "newnfsreq" means that it is trying to establish a TCP > connection with the server (again smells like some networking issue). > > Disabling delegations is the next step. (They aren't > required for correct behaviour and are disabled by default because > they are the "greenest" part of the implementation.) After disabling delegations, I was able to build world and kernel on two different clients, and my port build problems went away as well. I'm still left with a performance problem, although not quite as bad as I originally reported. Directory listings are snappy once again, but playing h264 video is choppy, particularly when seeking around: there's almost a full second delay before it kicks in, no matter where I seek. With NFSv3 the delay on seeks was less than 0.1 seconds and the playback was never jittery. I can try it again with v3 client and v4 server, if you think that's worthy of pursuit. If it makes any difference, the server's four CPUs are pegged at 100% (running "nice +4" cpu-bound jobs). But that was the case before I enabled v4 server too. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 16:29:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A375106564A for ; Mon, 28 Jun 2010 16:29:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id D71F18FC24 for ; Mon, 28 Jun 2010 16:29:14 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta09.westchester.pa.mail.comcast.net with comcast id bPQq1e0011wpRvQ59UVEWW; Mon, 28 Jun 2010 16:29:14 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta18.westchester.pa.mail.comcast.net with comcast id bUVD1e0023S48mS3eUVDNV; Mon, 28 Jun 2010 16:29:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D79CF9B425; Mon, 28 Jun 2010 09:29:11 -0700 (PDT) Date: Mon, 28 Jun 2010 09:29:11 -0700 From: Jeremy Chadwick To: "Rick C. Petty" Message-ID: <20100628162911.GA94456@icarus.home.lan> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628045852.GA75380@icarus.home.lan> <20100628142025.GB52174@kay.kiwi-computer.com> <20100628145600.GA92144@icarus.home.lan> <20100628151835.GA53315@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628151835.GA53315@kay.kiwi-computer.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 16:29:15 -0000 On Mon, Jun 28, 2010 at 10:18:35AM -0500, Rick C. Petty wrote: > > 8) Contents of /etc/sysctl.conf > > server and client: > > # for NFSv4 > kern.ipc.maxsockbuf=524288 You might want to discuss this one with Rick a bit (I'm not sure of the implications). Regarding heavy network I/O (I don't use NFS but Samba), I've found that the following tunables do in fact make a performance difference -- you might try and see if these have some impact (or, try forcing a specific protocol type for NFS, e.g. TCP-only; I'm not familiar with NFSv4 though). These are adjustable in sysctl.conf, thus adjustable in real-time. # Increase send/receive buffer maximums from 256KB to 16MB. # FreeBSD 7.x and later will auto-tune the size, but only up to the max. net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.recvbuf_max=16777216 # Double send/receive TCP datagram memory allocation. This defines the # amount of memory taken up by default *per socket*. net.inet.tcp.sendspace=65536 net.inet.tcp.recvspace=131072 That's about all I can comment on -- if NFSv3 works OK for you (performance-wise), then I'm not sure where the bottleneck could be. > > > Jun 27 18:04:44 rpcbind: cannot get information for udp6 > > > Jun 27 18:04:44 rpcbind: cannot get information for tcp6 > > > > These two usually indicate you removed IPv6 support from the kernel, > > except your ifconfig output (I've remove it) on the server shows you do > > have IPv6 support. I've been trying to get these warnings removed for > > quite some time (PR kern/96242). They're harmless, but the > > inconsistency here is a little weird -- are you explicitly disabling > > IPv6 on nfe0? > > I have WITHOUT_IPV6= in my make.conf on all my machines (or I have > problems with jdk1.6) and WITHOUT_INET6= in my src.conf. I'm not sure > why the rpcbind/ifconfig binaries have a different concept than the > kernel since I always "make buildworld kernel" and keep things in sync > with mergemaster when I reboot. I'm building new worlds/kernels now > to see if that makes any difference. make.conf WITHOUT_IPV6 would affect ports, src.conf WITHOUT_INET6 would affect the base system (thus rpcbind). The src.conf entry is what's causing rpcbind to spit out the above "cannot get information" messages, even though IPv6 is available in your kernel (see below). However: your kernel configuration file must contain "options INET6" or else you wouldn't have IPv6 addresses on lo0. So even though your kernel and world are synchronised, IPv6 capability-wise they probably aren't. This may be your intended desire though, and if so, no biggie. If you wanted to work around the problem, you can supposedly comment out the udp6 and tcp6 lines in /etc/netconfig. I choose not to do this (put up with the warning messages) since I'm not sure of the repercussions of adjusting this file (e.g. will something else down the road break). -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Mon Jun 28 18:01:32 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 8D7E7106566B; Mon, 28 Jun 2010 18:01:32 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Mon, 28 Jun 2010 14:01:16 -0400 User-Agent: KMail/1.6.2 References: <20100623025855.82916.qmail@exxodus.fedaykin.here> <201006251758.56393.jkim@FreeBSD.org> <4C25C3D3.3030109@FreeBSD.org> In-Reply-To: <4C25C3D3.3030109@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_uNOKM6vkj5rWLGa" Message-Id: <201006281401.19017.jkim@FreeBSD.org> Cc: d@delphij.net, python@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 18:01:32 -0000 --Boundary-00=_uNOKM6vkj5rWLGa Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Saturday 26 June 2010 05:09 am, Mario Sergio Fujikawa Ferreira wrote: > On 25/06/2010 18:58, Jung-uk Kim wrote: > > On Friday 25 June 2010 04:54 am, Mario Sergio Fujikawa Ferreira wrote: > >> On Wed, Jun 23, 2010 at 05:08:38PM -0400, Jung-uk Kim wrote: > >>> Date: Wed, 23 Jun 2010 17:08:38 -0400 > >>> From: Jung-uk Kim > >>> To: freebsd-stable@FreeBSD.org > >>> Cc: d@delphij.net, Mario Sergio Fujikawa Ferreira > >>> Subject: Re: FreeBSD 8.1-PRERELEASE: > >>> WARNING ioctl sign-extension ioctl ffffffff8004667e > >>> User-Agent: KMail/1.6.2 > >>> > >>> On Wednesday 23 June 2010 03:38 pm, Jung-uk Kim wrote: > >>>> On Wednesday 23 June 2010 03:10 pm, Jung-uk Kim wrote: > >>>>> On Wednesday 23 June 2010 03:01 pm, Jung-uk Kim wrote: > >>>>>> On Wednesday 23 June 2010 02:41 pm, Xin LI wrote: > >>>>>>> On 2010/06/23 11:37, Jung-uk Kim wrote: > >>>>>>>> On Wednesday 23 June 2010 02:12 pm, Xin LI wrote: > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> On 2010/06/22 19:58, Mario Sergio Fujikawa Ferreira > > > > wrote: > >>>>>>>>>> Hi, > >>>>>>>>>> > >>>>>>>>>> I am getting more than 4 thousand of the following > >>>>>>>>>> messages a day: > >>>>>>>>>> > >>>>>>>>>> WARNING pid 24509 (python2.6): ioctl sign-extension > >>>>>>>>>> ioctl ffffffff8004667e > >>>>>>>>> > >>>>>>>>> [...] > >>>>>>>>> > >>>>>>>>> I think we may need to check the code and patch it. > >>>>>>>>> Basically this means that python (or some .so modules) > >>>>>>>>> passed an int or unsigned int as parameter 'cmd', we > >>>>>>>>> need to change it to unsigned long. > >>>>>>>>> > >>>>>>>>> The warning itself should be harmless to my best of > >>>>>>>>> knowledge, one can probably remove the printf in > >>>>>>>>> kernel source code as a workaround. > >>>>>>>>> > >>>>>>>>> By the way it seems to be a POSIX violation and we > >>>>>>>>> didn't seem to really use so wide cmd, but I have not > >>>>>>>>> yet verified everything myself. > >>>>>>>> > >>>>>>>> Long time ago, I had a similar problem with termios > >>>>>>>> TIOCGWINSZ and we patched the port like this: > >>>>>>>> > >>>>>>>> http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/python > >>>>>>>> /fil es /A tt > >>>>>>>> ic/patch-Modules%3A%3Afcntlmodule.c?rev=1.1;content-typ > >>>>>>>> e=te xt %2 Fpl ain > >>>>>>>> > >>>>>>>> I believe it was upstream patched at the time but I > >>>>>>>> won't be surprised if something similar was > >>>>>>>> reintroduced. It happens when a Python internal > >>>>>>>> integer type is converted to a native unsigned long. > >>>>>>> > >>>>>>> Well, only *BSD have cmd a long value so it's likely that > >>>>>>> it would be reintroduced. > >>>>>> > >>>>>> Yes, that's what I mean. > >>>>>> > >>>>>>> I have checked the 4.4BSD archive and understood that our > >>>>>>> ioctl's cmd parameter was made long around 1991 or 1992s > >>>>>>> but didn't see what it actually buy us... > >>>>>> > >>>>>> Like it or not, it is too late to revert. :-( > >>>>> > >>>>> From Python 2.6.5: > >>>>> > >>>>> static PyObject * > >>>>> fcntl_ioctl(PyObject *self, PyObject *args) > >>>>> { > >>>>> #define IOCTL_BUFSZ 1024 > >>>>> int fd; > >>>>> /* In PyArg_ParseTuple below, we use the unsigned > >>>>> non-checked 'I' format for the 'code' parameter because > >>>>> Python turns 0x8000000 into either a large positive number > >>>>> (PyLong or PyInt on 64-bit platforms) or a negative number on > >>>>> others (32-bit PyInt) whereas the system expects it to be a > >>>>> 32bit bit field value regardless of it being passed as an int > >>>>> or unsigned long on various platforms. See the > >>>>> termios.TIOCSWINSZ constant across platforms for an example > >>>>> of thise. > >>>>> > >>>>> If any of the 64bit platforms ever decide to use more > >>>>> than 32bits in their unsigned long ioctl codes this will > >>>>> break and need special casing based on the platform being > >>>>> built on. */ > >>>>> unsigned int code; > >>>>> ... > >>>>> > >>>>> It is still a kludge and it won't be fixed. :-( > >>>> > >>>> Please drop the attached patch in ports/lang/python26/files > >>>> and test. Note I am not a Python guy, so please don't shoot > >>>> me. ;-) > >>> > >>> I found that Python guys added 'k' format since 2.3, which > >>> converts a Python integer to unsigned long. Please ignore the > >>> previous patch and try the attached patch instead. > >> > >> Unfortunately it didn't work. > >> > >> 1) Added patch to lang/python26 > >> 2) Recompiled lang/python26 > >> 3) cd /var/db/ports&& portupgrade -f python* py26* deluge* > >> > >> Restarted deluge afterwards. The message is still there: > >> > >> Jun 25 05:49:38 exxodus kernel: WARNING pid 38635 (python2.6): > >> ioctl sign-extension ioctl ffffffff8004667e > > > > It may be a deeper problen, then. :-( > > > > First of all, I cannot reproduce the problem because deluged > > dumps core on my box and I gave it up. Just staring at the code, > > it seems they rely on a bundled libtorrent for Python binding and > > the libtorrent relies on Boost, in turn. Then, the actual > > non-blocking socket implementation is done with Boost ASIO[1]. > > It is possible that there are more complicated problems between > > these and the Python binding. In fact, I can see a lot of these: > > > > int name() const > > { > > return FIONBIO; > > } > > ... > > if (!ec&& command.name() == static_cast(FIONBIO)) > > ... > > socket_ops::ioctl(impl.socket_, command.name(), ...) > > ... > > > > They are just assuming it is an int type, I guess. > > > > Sigh, what a mess... > > Given that your python patch is a step on the right direction, I > would propose that it be further tested and then committed if > possible. > > > [1] Boost and its Python binding from ports seems to be a newer > > ASIO version than the bundled ASIO headers. Probably it is a > > reason for the crash but I didn't bother too much. > > If you have the time, everything you need to run the latest deluge > 1.3.0 RC1 can be found at > > http://www.freebsd.org/cgi/query-pr.cgi?pr=144337 > > Check the PR, all the necessary ports can be found there. Let me > know what you think. Please drop the attached patch in ports/devel/boost-libs/files, rebuild all dependencies, and try your deluge ports again[1]. Jung-uk Kim [1] Your libtorrent Python slave port and deluge ports don't build/package cleanly. I guess you need to update the PR's. --Boundary-00=_uNOKM6vkj5rWLGa Content-Type: text/plain; charset="iso-8859-1"; name="patch-boost_asio-ioctl" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch-boost_asio-ioctl" --- boost/asio/detail/io_control.hpp.orig 2010-01-04 04:36:00.000000000 -0500 +++ boost/asio/detail/io_control.hpp 2010-06-25 18:38:28.000000000 -0400 @@ -46,7 +46,7 @@ public: } // Get the name of the IO control command. - int name() const + ioctl_cmd_type name() const { return FIONBIO; } @@ -96,7 +96,7 @@ public: } // Get the name of the IO control command. - int name() const + ioctl_cmd_type name() const { return FIONREAD; } --- boost/asio/detail/reactive_descriptor_service.hpp.orig 2010-06-25 18:24:52.000000000 -0400 +++ boost/asio/detail/reactive_descriptor_service.hpp 2010-06-25 18:56:32.000000000 -0400 @@ -223,7 +223,7 @@ public: // descriptor is put into the state that has been requested by the user. If // the ioctl syscall was successful then we need to update the flags to // match. - if (!ec && command.name() == static_cast(FIONBIO)) + if (!ec && command.name() == static_cast(FIONBIO)) { if (*static_cast(command.data())) { --- boost/asio/detail/reactive_socket_service.hpp.orig 2010-04-07 04:44:41.000000000 -0400 +++ boost/asio/detail/reactive_socket_service.hpp 2010-06-25 18:55:06.000000000 -0400 @@ -453,7 +453,7 @@ public: // already in the correct state. This ensures that the underlying socket // is put into the state that has been requested by the user. If the ioctl // syscall was successful then we need to update the flags to match. - if (!ec && command.name() == static_cast(FIONBIO)) + if (!ec && command.name() == static_cast(FIONBIO)) { if (*static_cast(command.data())) { --- boost/asio/detail/win_iocp_socket_service.hpp.orig 2010-03-29 21:20:37.000000000 -0400 +++ boost/asio/detail/win_iocp_socket_service.hpp 2010-06-25 18:55:49.000000000 -0400 @@ -564,7 +564,7 @@ public: socket_ops::ioctl(impl.socket_, command.name(), static_cast(command.data()), ec); - if (!ec && command.name() == static_cast(FIONBIO)) + if (!ec && command.name() == static_cast(FIONBIO)) { if (*static_cast(command.data())) impl.flags_ |= implementation_type::user_set_non_blocking; --- boost/asio/detail/descriptor_ops.hpp.orig 2010-01-04 04:36:00.000000000 -0500 +++ boost/asio/detail/descriptor_ops.hpp 2010-06-25 18:37:37.000000000 -0400 @@ -110,7 +110,7 @@ inline int gather_write(int d, const buf return result; } -inline int ioctl(int d, long cmd, ioctl_arg_type* arg, +inline int ioctl(int d, ioctl_cmd_type cmd, ioctl_arg_type* arg, boost::system::error_code& ec) { clear_error(ec); --- boost/asio/detail/socket_ops.hpp.orig 2010-01-04 06:55:09.000000000 -0500 +++ boost/asio/detail/socket_ops.hpp 2010-06-25 18:39:55.000000000 -0400 @@ -596,7 +596,7 @@ inline int getsockname(socket_type s, so return result; } -inline int ioctl(socket_type s, long cmd, ioctl_arg_type* arg, +inline int ioctl(socket_type s, ioctl_cmd_type cmd, ioctl_arg_type* arg, boost::system::error_code& ec) { clear_error(ec); --- boost/asio/detail/socket_types.hpp.orig 2010-03-21 05:39:26.000000000 -0400 +++ boost/asio/detail/socket_types.hpp 2010-06-25 18:48:43.000000000 -0400 @@ -189,6 +189,12 @@ typedef sockaddr_in6 sockaddr_in6_type; typedef sockaddr_storage sockaddr_storage_type; typedef sockaddr_un sockaddr_un_type; typedef addrinfo addrinfo_type; +#if (defined(__MACH__) && defined(__APPLE__)) || defined(__DragonFly__) || \ + define(__FreeBSD__) || defined(__NetBSD__) || defined(__OpenBSD__) +typedef unsigned long ioctl_cmd_type; +#else +typedef int ioctl_cmd_type; +#endif typedef int ioctl_arg_type; typedef uint32_t u_long_type; typedef uint16_t u_short_type; --Boundary-00=_uNOKM6vkj5rWLGa-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 18:13:30 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id A949A106566C; Mon, 28 Jun 2010 18:13:30 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Mon, 28 Jun 2010 14:13:16 -0400 User-Agent: KMail/1.6.2 References: <20100623025855.82916.qmail@exxodus.fedaykin.here> <4C25C3D3.3030109@FreeBSD.org> <201006281401.19017.jkim@FreeBSD.org> In-Reply-To: <201006281401.19017.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_+YOKMgDy+zZ+WMz" Message-Id: <201006281413.18567.jkim@FreeBSD.org> Cc: d@delphij.net, python@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 18:13:30 -0000 --Boundary-00=_+YOKMgDy+zZ+WMz Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Monday 28 June 2010 02:01 pm, Jung-uk Kim wrote: > Please drop the attached patch in ports/devel/boost-libs/files, > rebuild all dependencies, and try your deluge ports again[1]. Please ignore the previous patch and try this one. Sorry, there was a typo. :-( Jung-uk Kim --Boundary-00=_+YOKMgDy+zZ+WMz Content-Type: text/plain; charset="iso-8859-1"; name="patch-boost_asio-ioctl" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch-boost_asio-ioctl" --- boost/asio/detail/io_control.hpp.orig 2010-01-04 04:36:00.000000000 -0500 +++ boost/asio/detail/io_control.hpp 2010-06-25 18:38:28.000000000 -0400 @@ -46,7 +46,7 @@ public: } // Get the name of the IO control command. - int name() const + ioctl_cmd_type name() const { return FIONBIO; } @@ -96,7 +96,7 @@ public: } // Get the name of the IO control command. - int name() const + ioctl_cmd_type name() const { return FIONREAD; } --- boost/asio/detail/reactive_descriptor_service.hpp.orig 2010-06-25 18:24:52.000000000 -0400 +++ boost/asio/detail/reactive_descriptor_service.hpp 2010-06-25 18:56:32.000000000 -0400 @@ -223,7 +223,7 @@ public: // descriptor is put into the state that has been requested by the user. If // the ioctl syscall was successful then we need to update the flags to // match. - if (!ec && command.name() == static_cast(FIONBIO)) + if (!ec && command.name() == static_cast(FIONBIO)) { if (*static_cast(command.data())) { --- boost/asio/detail/reactive_socket_service.hpp.orig 2010-04-07 04:44:41.000000000 -0400 +++ boost/asio/detail/reactive_socket_service.hpp 2010-06-25 18:55:06.000000000 -0400 @@ -453,7 +453,7 @@ public: // already in the correct state. This ensures that the underlying socket // is put into the state that has been requested by the user. If the ioctl // syscall was successful then we need to update the flags to match. - if (!ec && command.name() == static_cast(FIONBIO)) + if (!ec && command.name() == static_cast(FIONBIO)) { if (*static_cast(command.data())) { --- boost/asio/detail/win_iocp_socket_service.hpp.orig 2010-03-29 21:20:37.000000000 -0400 +++ boost/asio/detail/win_iocp_socket_service.hpp 2010-06-25 18:55:49.000000000 -0400 @@ -564,7 +564,7 @@ public: socket_ops::ioctl(impl.socket_, command.name(), static_cast(command.data()), ec); - if (!ec && command.name() == static_cast(FIONBIO)) + if (!ec && command.name() == static_cast(FIONBIO)) { if (*static_cast(command.data())) impl.flags_ |= implementation_type::user_set_non_blocking; --- boost/asio/detail/descriptor_ops.hpp.orig 2010-01-04 04:36:00.000000000 -0500 +++ boost/asio/detail/descriptor_ops.hpp 2010-06-25 18:37:37.000000000 -0400 @@ -110,7 +110,7 @@ inline int gather_write(int d, const buf return result; } -inline int ioctl(int d, long cmd, ioctl_arg_type* arg, +inline int ioctl(int d, ioctl_cmd_type cmd, ioctl_arg_type* arg, boost::system::error_code& ec) { clear_error(ec); --- boost/asio/detail/socket_ops.hpp.orig 2010-01-04 06:55:09.000000000 -0500 +++ boost/asio/detail/socket_ops.hpp 2010-06-25 18:39:55.000000000 -0400 @@ -596,7 +596,7 @@ inline int getsockname(socket_type s, so return result; } -inline int ioctl(socket_type s, long cmd, ioctl_arg_type* arg, +inline int ioctl(socket_type s, ioctl_cmd_type cmd, ioctl_arg_type* arg, boost::system::error_code& ec) { clear_error(ec); --- boost/asio/detail/socket_types.hpp.orig 2010-03-21 05:39:26.000000000 -0400 +++ boost/asio/detail/socket_types.hpp 2010-06-25 18:48:43.000000000 -0400 @@ -189,6 +189,12 @@ typedef sockaddr_in6 sockaddr_in6_type; typedef sockaddr_storage sockaddr_storage_type; typedef sockaddr_un sockaddr_un_type; typedef addrinfo addrinfo_type; +#if (defined(__MACH__) && defined(__APPLE__)) || defined(__DragonFly__) || \ + defined(__FreeBSD__) || defined(__NetBSD__) || defined(__OpenBSD__) +typedef unsigned long ioctl_cmd_type; +#else +typedef int ioctl_cmd_type; +#endif typedef int ioctl_arg_type; typedef uint32_t u_long_type; typedef uint16_t u_short_type; --Boundary-00=_+YOKMgDy+zZ+WMz-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 19:09:08 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBD15106566C for ; Mon, 28 Jun 2010 19:09:08 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 813698FC18 for ; Mon, 28 Jun 2010 19:09:08 +0000 (UTC) Received: (qmail 9478 invoked by uid 399); 28 Jun 2010 19:09:07 -0000 Received: from localhost (HELO ?192.168.0.145?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 28 Jun 2010 19:09:07 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Date: Mon, 28 Jun 2010 12:08:28 -0700 (PDT) From: Doug Barton To: Jung-uk Kim In-Reply-To: <201006281401.19017.jkim@FreeBSD.org> Message-ID: References: <20100623025855.82916.qmail@exxodus.fedaykin.here> <201006251758.56393.jkim@FreeBSD.org> <4C25C3D3.3030109@FreeBSD.org> <201006281401.19017.jkim@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: Outlook -- Not just for spreading viruses anymore! OpenPGP: id=1A1ABC84 Organization: http://SupersetSolutions.com/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: d@delphij.net, freebsd-stable@FreeBSD.org, python@freebsd.org, Mario Sergio Fujikawa Ferreira Subject: Re: FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 19:09:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 28 Jun 2010, Jung-uk Kim wrote: > Please drop the attached patch in ports/devel/boost-libs/files, > rebuild all dependencies, and try your deluge ports again[1]. > > Jung-uk Kim > > [1] Your libtorrent Python slave port and deluge ports don't > build/package cleanly. I guess you need to update the PR's. I'm actually working now on the update for libtorrent-rasterbar-15 and deluge based on the work that lioux did, so I will gladly try your patch (from the 2nd e-mail) and let you know how it goes. I'm currently working with the author of libtorrent to iron out some bugs that we've found while working on the python bindings, and in preparation for his new release of 0.15.1, so hopefully it will all be done later this week. :) Doug - -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iQEcBAEBCAAGBQJMKPNPAAoJEFzGhvEaGryEHPkIAK4DCd6dGtPJHlmTDUkZhBxc CR4GgDi5xTuw5weHzEFLV8l//tXxGBkcMYLMpxH+icakeVkxgBH4J5XIF05fRiYY Nf3pB8/2SZJv+Ni78t105FI98BrtDBuY+sO1cyfdLoy61AVvWPiEdfJYHXSlBLy9 ykmuZWpB6iP93PTtWrdzcTtTC+qA/YEDBa7NevLr9XvsEC7/ocdJgvufUQ8XS/SB baCiU/MwleeuNeHuXxAuXjsVUo0Et7QkoU9yZsdIk5efQRnbsEDyKXfT+h2ti5RO GuEnlW1kx1ldYJIMbqYVDwNfv/fllDWEyKS+36AhF0ZUexUz2Kryew4BsZS5y98= =sBTZ -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 23:32:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABB701065732 for ; Mon, 28 Jun 2010 23:32:06 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5168FC13 for ; Mon, 28 Jun 2010 23:32:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAFfNKEyDaFvJ/2dsb2JhbACfNnHBCoUkBA X-IronPort-AV: E=Sophos;i="4.53,499,1272859200"; d="scan'208";a="82195603" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 19:32:03 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 52302FB80DA; Mon, 28 Jun 2010 19:32:05 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bvYK8RNrnqcz; Mon, 28 Jun 2010 19:32:04 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 58A4AFB80BD; Mon, 28 Jun 2010 19:32:04 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5SNmxP14973; Mon, 28 Jun 2010 19:48:59 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 19:48:59 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100628153527.GB53315@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 23:32:06 -0000 On Mon, 28 Jun 2010, Rick C. Petty wrote: > On Mon, Jun 28, 2010 at 12:35:14AM -0400, Rick Macklem wrote: >> >> Being stuck in "newnfsreq" means that it is trying to establish a TCP >> connection with the server (again smells like some networking issue). >> >> Disabling delegations is the next step. (They aren't >> required for correct behaviour and are disabled by default because >> they are the "greenest" part of the implementation.) > > After disabling delegations, I was able to build world and kernel on two > different clients, and my port build problems went away as well. > Ok, it sounds like you found some kind of race condition in the delegation handling. (I'll see if I can reproduce it here. It could be fun to find:-) > I'm still left with a performance problem, although not quite as bad as I > originally reported. Directory listings are snappy once again, but playing > h264 video is choppy, particularly when seeking around: there's almost a > full second delay before it kicks in, no matter where I seek. With NFSv3 > the delay on seeks was less than 0.1 seconds and the playback was never > jittery. > Hmm, see below w.r.t. 100% cpu. > I can try it again with v3 client and v4 server, if you think that's > worthy of pursuit. If it makes any difference, the server's four CPUs are > pegged at 100% (running "nice +4" cpu-bound jobs). But that was the case > before I enabled v4 server too. > It would be interesting to see if the performance problem exists for NFSv3 mounts against the experimental (nfsv4) server. Since the CPUs are 100% busy, it might be a scheduling issue w.r.t. the nfsd threads (ie. the ones in the experimental server don't have as high a priority as for the regular server?). I've always tested on a machine where the CPU (I only have single core) are nowhere near 100% busy. If this theory is correct, the performance issue should still be noticible for an NFSv3 mount to the experimental server. I'll try running something compute bound on the server here and see what happens. rick From owner-freebsd-stable@FreeBSD.ORG Mon Jun 28 23:49:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E8B7106564A for ; Mon, 28 Jun 2010 23:49:09 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id D47BC8FC0C for ; Mon, 28 Jun 2010 23:49:08 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAAbSKEyDaFvG/2dsb2JhbACfNnHBEYUkBA X-IronPort-AV: E=Sophos;i="4.53,500,1272859200"; d="scan'208";a="82196940" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 19:49:05 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id F2B232101CD; Mon, 28 Jun 2010 19:49:07 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2jql+BWICdW; Mon, 28 Jun 2010 19:49:06 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id DD6392101C4; Mon, 28 Jun 2010 19:49:06 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5T061016688; Mon, 28 Jun 2010 20:06:01 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 20:06:01 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100628140054.GA52174@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 23:49:09 -0000 On Mon, 28 Jun 2010, Rick C. Petty wrote: > >> Make sure you don't have multiple entries for the same uid, such as "root" >> and "toor" both for uid 0 in your /etc/passwd. (ie. get rid of one of >> them, if you have both) > > Hmm, that's a strange requirement, since FreeBSD by default comes with > both. That should probably be documented in the nfsv4 man page. > Well, if the mapping from uid->name is not unique, getpwuid() will just return one of them and it probably won't be the expected one. Having both "root" and "toor" only cause weird behaviour when "root" tries to use a mount point. I had thought it was in the man pages, but I now see it isn't mentioned. I'll try and remember to add it. >> >> This error indicates that there wasn't a valid FH for the server. I >> suspect that the mount failed. (It does a loop of Lookups from "/" in >> the kernel during the mount and it somehow got confused part way through.) > > If the mount failed, why would it allow me to "ls /vol/a" and see both "b" > and "c" directories as well as other files/directories on /vol/ ? > >> I don't know why these empty dirs would confuse it. I'll try a test >> here, but I suspect the real problem was that the mount failed and >> then happened to succeed after you deleted the empty dirs. > > It doesn't seem likely. I spent an hour mounting and unmounting and each > mount looked successful in that there were files and directories besides > the two I was trying to decend into. > My theory was that, since you used "soft", one of the Lookups during the mounting process in the kernel failed with ETIMEDOUT. It isn't coded to handle that. There are lots of things that will break in the NFSv4 client if "soft" or "intr" are used. (That is in the mount_nfs man page, but right at the end, so it could get missed.) Maybe "broken mount" would have been a better term than "failed mount". If more recent mount attempts are without "soft", then I would expect them to work reliably. (If you feel daring, add the empty subdirs back and see if it fails?) I will try a case with empty subdirs on the client, to see if there is a problem when I do it. (It should just cover them up until umount, but it could certainly be broken:-) >> It still smells like some sort of transport/net interface/... issue >> is at the bottom of this. (see response to your next post) > > It's possible. I just had another NFSv4 client (with the same server) lock > up: > > load: 0.00 cmd: ls 17410 [nfsv4lck] 641.87r 0.00u 0.00s 0% 1512k > > and: > > load: 0.00 cmd: make 87546 [wait] 37095.09r 0.01u 0.01s 0% 844k > > That make has been hung for hours, and the ls(1) was executed during that > lockup. I wish there was a way I could unhang these processes and unmount > the NFS mount without panicking the kernel, but alas even this fails: > > # umount -f /sw > load: 0.00 cmd: umount 17479 [nfsclumnt] 1.27r 0.00u 0.04s 0% 788k > The plan is to implement a "hard forced" umount (something like -ff) which will throw away data, but get the umount done, but it hasn't been coded yet. (For 8.2 maybe?) > A "shutdown -p now" resulted in a panic with the speaker beeping > constantly and no console output. > > It's possible the NICs are all suspect, but all of this worked fine a > couple of days ago when I was only using NFSv3. > Yea, if NFSv3 worked fine with the same kernel, it seems more likely an experimental NFS server issue, possibly related to scheduling the busy CPUs. (If it was a NIC related problem, it is most likely related to the driver, but if the NFSv3 case was using the same driver, that doesn't seem likely.) You are now using "rsize=32768,wsize=32768" aren't you? (If you aren't yet using that, try it, since larger bursts of traffic can definitely "tickle" nics driver problems, to borrow Jeremy's term.) rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 00:24:29 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01398106564A for ; Tue, 29 Jun 2010 00:24:29 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id A46A28FC24 for ; Tue, 29 Jun 2010 00:24:27 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAP/ZKEyDaFvG/2dsb2JhbACfNnHAdYUkBJEP X-IronPort-AV: E=Sophos;i="4.53,500,1272859200"; d="scan'208";a="81998554" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 20:24:22 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 27FF52101D5; Mon, 28 Jun 2010 20:24:24 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekvLdV2xnIte; Mon, 28 Jun 2010 20:24:23 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 21AD02101D3; Mon, 28 Jun 2010 20:24:23 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5T0fHv20684; Mon, 28 Jun 2010 20:41:18 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 20:41:17 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Daniel Braniss In-Reply-To: Message-ID: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, alexs@ulgsm.ru Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 00:24:29 -0000 On Mon, 28 Jun 2010, Daniel Braniss wrote: >> >> >> On Mon, 28 Jun 2010, alexs@ulgsm.ru wrote: >> >>> >>> >>> kernel built with: >>> options BOOTP # Use BOOTP to obtain IP address/hostname >>> options BOOTP_NFSROOT # NFS mount root file system using BOOTP info >>> options BOOTP_NFSV3 >>> >> Try building a kernel without the above options, but with >> options NFS_ROOT >> specified. I think that's what most pxeboot users do and it was what >> I had assumed when I looked at the code. >> >> If that doesn't fix the problem...I haven't got a solution for you, rick > > I use: > options BOOTP_NFSV3 # Use NFS v3 to NFS mount root > Looking at the code, it appears that BOOTP_NFSROOT doesn't set mygateway in the nfs_diskless structure, which would explain why the mount of root in the kernel doesn't work. I think using NFS_ROOT but not the BOOTPxxx options will work around this or you could test the following patch and see if it helps. (Testing the patch would be appreciated, since I don't have any way to test across multiple subnets and it would be nice to have a fix for the BOOTPxxx cases.) rick --- untested patch for bootp_subr.c --- --- nfsclient/bootp_subr.c.sav 2010-06-28 19:16:02.000000000 -0400 +++ nfsclient/bootp_subr.c 2010-06-28 19:21:52.000000000 -0400 @@ -1524,6 +1524,7 @@ printf(" "); ifctx->gotgw = 1; gctx->gotgw = 1; + nd->mygateway = ifctx->gw; } } From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 01:52:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DCA8106566C for ; Tue, 29 Jun 2010 01:52:28 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 50C7A8FC08 for ; Tue, 29 Jun 2010 01:52:27 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEABbvKEyDaFvH/2dsb2JhbACfNXHARIUkBA X-IronPort-AV: E=Sophos;i="4.53,501,1272859200"; d="scan'208";a="82009326" Received: from danube.cs.uoguelph.ca ([131.104.91.199]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 28 Jun 2010 21:52:25 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by danube.cs.uoguelph.ca (Postfix) with ESMTP id C9AE81084789; Mon, 28 Jun 2010 21:52:26 -0400 (EDT) X-Virus-Scanned: amavisd-new at danube.cs.uoguelph.ca Received: from danube.cs.uoguelph.ca ([127.0.0.1]) by localhost (danube.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8+iYSKd-OFAj; Mon, 28 Jun 2010 21:52:25 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by danube.cs.uoguelph.ca (Postfix) with ESMTP id B9BB3108478F; Mon, 28 Jun 2010 21:52:25 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5T29L800838; Mon, 28 Jun 2010 22:09:21 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Mon, 28 Jun 2010 22:09:21 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100628153527.GB53315@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 01:52:28 -0000 On Mon, 28 Jun 2010, Rick C. Petty wrote: > > I can try it again with v3 client and v4 server, if you think that's > worthy of pursuit. If it makes any difference, the server's four CPUs are > pegged at 100% (running "nice +4" cpu-bound jobs). But that was the case > before I enabled v4 server too. > If it is practical, it would be interesting to see what effect killing off the cpu bound jobs has w.r.t. performance. rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 02:28:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67FBB106564A for ; Tue, 29 Jun 2010 02:28:59 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id E409D8FC08 for ; Tue, 29 Jun 2010 02:28:58 +0000 (UTC) Received: (qmail 63510 invoked by uid 2000); 29 Jun 2010 02:28:57 -0000 Date: Mon, 28 Jun 2010 21:28:57 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100629022857.GA63450@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 02:28:59 -0000 On Mon, Jun 28, 2010 at 10:09:21PM -0400, Rick Macklem wrote: > > > On Mon, 28 Jun 2010, Rick C. Petty wrote: > > > If it makes any difference, the server's four CPUs are > >pegged at 100% (running "nice +4" cpu-bound jobs). But that was the case > >before I enabled v4 server too. > > If it is practical, it would be interesting to see what effect killing > off the cpu bound jobs has w.r.t. performance. I sent SIGTSTP to all those processes and brought the CPUs to idle. The jittering/stuttering is still present when watching h264 video. So that rules out scheduling issues. I'll be investigating Jeremy's TCP tuning suggestions next. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 02:36:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FE8F106567A for ; Tue, 29 Jun 2010 02:36:34 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 69A1B8FC08 for ; Tue, 29 Jun 2010 02:36:33 +0000 (UTC) Received: (qmail 63649 invoked by uid 2000); 29 Jun 2010 02:36:32 -0000 Date: Mon, 28 Jun 2010 21:36:32 -0500 From: "Rick C. Petty" To: Jeremy Chadwick Message-ID: <20100629023632.GB63450@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628045852.GA75380@icarus.home.lan> <20100628142025.GB52174@kay.kiwi-computer.com> <20100628145600.GA92144@icarus.home.lan> <20100628151835.GA53315@kay.kiwi-computer.com> <20100628162911.GA94456@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100628162911.GA94456@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: Rick Macklem , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 02:36:34 -0000 On Mon, Jun 28, 2010 at 09:29:11AM -0700, Jeremy Chadwick wrote: > > # Increase send/receive buffer maximums from 256KB to 16MB. > # FreeBSD 7.x and later will auto-tune the size, but only up to the max. > net.inet.tcp.sendbuf_max=16777216 > net.inet.tcp.recvbuf_max=16777216 > > # Double send/receive TCP datagram memory allocation. This defines the > # amount of memory taken up by default *per socket*. > net.inet.tcp.sendspace=65536 > net.inet.tcp.recvspace=131072 I tried adjusting to these settings, on both the client and the server. I still see the same jittery/stuttery video behavior. Thanks for your suggestions though, these are probably good settings to have around anyway since I have 12 GB of RAM on the client and 8 GB of RAM on the server. > make.conf WITHOUT_IPV6 would affect ports, src.conf WITHOUT_INET6 would > affect the base system (thus rpcbind). The src.conf entry is what's > causing rpcbind to spit out the above "cannot get information" messages, > even though IPv6 is available in your kernel (see below). > > However: your kernel configuration file must contain "options INET6" or > else you wouldn't have IPv6 addresses on lo0. So even though your > kernel and world are synchronised, IPv6 capability-wise they probably > aren't. This may be your intended desire though, and if so, no biggie. Oh forgot about that. I'll have to add the "nooptions" since I like to build as close to GENERIC as possible. Mostly the WITHOUT_* stuff in /etc/src.conf is to reduce my overall build times, since I don't need some of those tools. I'm okay with the messages though; I'll probably comment out WITHOUT_INET6. Thanks again for your suggestions, -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 03:06:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89C4F106564A for ; Tue, 29 Jun 2010 03:06:35 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 16D088FC0C for ; Tue, 29 Jun 2010 03:06:34 +0000 (UTC) Received: (qmail 63892 invoked by uid 2000); 29 Jun 2010 03:06:33 -0000 Date: Mon, 28 Jun 2010 22:06:33 -0500 From: "Rick C. Petty" To: Rick Macklem Message-ID: <20100629030633.GC63450@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 03:06:35 -0000 On Mon, Jun 28, 2010 at 07:48:59PM -0400, Rick Macklem wrote: > > Ok, it sounds like you found some kind of race condition in the delegation > handling. (I'll see if I can reproduce it here. It could be fun to find:-) Good luck with that! =) > >I can try it again with v3 client and v4 server, if you think that's > >worthy of pursuit. If it makes any difference, the server's four CPUs are > >pegged at 100% (running "nice +4" cpu-bound jobs). But that was the case > >before I enabled v4 server too. > > > It would be interesting to see if the performance problem exists for > NFSv3 mounts against the experimental (nfsv4) server. Hmm, I couldn't reproduce the problem. Once I unmounted the nfsv4 client and tried v3, the jittering stopped. Then I unmounted v3 and tried v4 again, no jitters. I played with a couple of combinations back and forth (toggling the presence of "nfsv4" in the options) and sometimes I saw jittering but only with v4, but nothing like what I was seeing before. Perhaps this is a result of Jeremy's TCP tuning tweaks. This is also a difficult thing to test, because the server and client have so much memory, they cache the date blocks. So if I try my stutter test on the same video a second time, I only notice stutters if I skip to parts I haven't skipped to before. I can comment that it seemed like more of a latency issue than a throughput issue to me. But the disks aren't ever under a high load. But it's hard to determine accurate load when the disks are seeking. Oh, I'm using the AHCI controller mode/driver on those disks instead of ATA, if that matters. One time when I mounted the v4 again, it broke subdirectories like I was talking about before. Essentially it would give me a readout of all the top-level directories but wouldn't descend into subdirectories which reflect different mountpoints on the server. An unmount and a remount (without changes to /etc/fstab) fixed the problem. I'm wondering if there isn't some race condition that seems to affect crossing mountpoints on the server. When the situation happens, it affects all mountpoints equally and persists for the duration of that mount. And of course, I can't reproduce the problem when I try. I saw the broken mountpoint crossing on another client (without any TCP tuning) but each time it happened I saw this in the logs: nfscl: consider increasing kern.ipc.maxsockbuf Once I doubled that value, the problem went away.. at least with this particular v4 server mountpoint. At the moment, things are behaving as expected. The v4 file system seems just as fast as v3 did, and I don't need a dozen mountpoints specified on each client thanks to v4. Once again, I thank you, Rick, for all your hard work! -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 04:00:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17AF1106566B for ; Tue, 29 Jun 2010 04:00:08 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 7CA3A8FC0C for ; Tue, 29 Jun 2010 04:00:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o5T3xxMu002524; Tue, 29 Jun 2010 14:00:00 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 29 Jun 2010 13:59:59 +1000 (EST) From: Ian Smith To: Rick Macklem In-Reply-To: Message-ID: <20100629134033.O9227@sola.nimnet.asn.au> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "Rick C. Petty" , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 04:00:08 -0000 On Mon, 28 Jun 2010, Rick Macklem wrote: > On Mon, 28 Jun 2010, Rick C. Petty wrote: > > > > > > Make sure you don't have multiple entries for the same uid, such as > > > "root" > > > and "toor" both for uid 0 in your /etc/passwd. (ie. get rid of one of > > > them, if you have both) > > > > Hmm, that's a strange requirement, since FreeBSD by default comes with > > both. That should probably be documented in the nfsv4 man page. > > > > Well, if the mapping from uid->name is not unique, getpwuid() will just > return one of them and it probably won't be the expected one. Having > both "root" and "toor" only cause weird behaviour when "root" tries to > use a mount point. I had thought it was in the man pages, but I now > see it isn't mentioned. I'll try and remember to add it. Not wanting to hijack this (interesting) thread, but .. I have to concur with Rick P - that's rather a odd requirement when each FreeBSD install since at least 2.2 has come with root and toor (in that order) in /etc/passwd. I don't use toor, but often enough read about folks who do, and don't recall it ever being an issue with NFSv3. Are you sure this is a problem that cannot be coded around in NFSv4? cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 06:49:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 918DE106566C for ; Tue, 29 Jun 2010 06:49:06 +0000 (UTC) (envelope-from alexs@ulgsm.ru) Received: from mail.ulgsm.ru (skuns.ulgsm.ru [93.93.136.26]) by mx1.freebsd.org (Postfix) with ESMTP id 32ED48FC1A for ; Tue, 29 Jun 2010 06:49:05 +0000 (UTC) Received: from mail.ulgsm.ru (localhost [127.0.0.1]) by mail.ulgsm.ru (Postfix) with ESMTP id 1F5B43BC32 for ; Tue, 29 Jun 2010 10:49:03 +0400 (MSD) X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on skuns.gsm900.net Received: from mail.ulgsm.ru (localhost [127.0.0.1]) by mail.ulgsm.ru (Postfix) with ESMTP id 0121F3BC30 for ; Tue, 29 Jun 2010 10:49:03 +0400 (MSD) Received: from mail.ulgsm.ru (bazar.gsm900.net [192.168.0.160]) by mail.ulgsm.ru (Postfix) with ESMTP id BDE053BC28 for ; Tue, 29 Jun 2010 10:49:02 +0400 (MSD) Date: Tue, 29 Jun 2010 10:49:02 +0400 From: alexs@ulgsm.ru To: freebsd-stable@freebsd.org Message-ID: <20100629064902.GA39446@mail.ulgsm.ru> References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 06:49:06 -0000 * Rick Macklem [2010-06-28 20:41:17 -0400]: > > > On Mon, 28 Jun 2010, Daniel Braniss wrote: > > >> > >> > >> On Mon, 28 Jun 2010, alexs@ulgsm.ru wrote: > >> > >>> > >>> > >>> kernel built with: > >>> options BOOTP # Use BOOTP to obtain IP address/hostname > >>> options BOOTP_NFSROOT # NFS mount root file system using BOOTP info > >>> options BOOTP_NFSV3 > >>> > >> Try building a kernel without the above options, but with > >> options NFS_ROOT > >> specified. I think that's what most pxeboot users do and it was what > >> I had assumed when I looked at the code. > >> > >> If that doesn't fix the problem...I haven't got a solution for you, rick > > > > I use: > > options BOOTP_NFSV3 # Use NFS v3 to NFS mount root > > > Looking at the code, it appears that BOOTP_NFSROOT doesn't set mygateway > in the nfs_diskless structure, which would explain why the mount of root > in the kernel doesn't work. > > I think using NFS_ROOT but not the BOOTPxxx options will work around this > or you could test the following patch and see if it helps. (Testing the > patch would be appreciated, since I don't have any way to test across > multiple subnets and it would be nice to have a fix for the BOOTPxxx > cases.) > > rick > --- untested patch for bootp_subr.c --- > --- nfsclient/bootp_subr.c.sav 2010-06-28 19:16:02.000000000 -0400 > +++ nfsclient/bootp_subr.c 2010-06-28 19:21:52.000000000 -0400 > @@ -1524,6 +1524,7 @@ > printf(" "); > ifctx->gotgw = 1; > gctx->gotgw = 1; > + nd->mygateway = ifctx->gw; > } > } Yes. without BOOTPxxx options boot is fine. I tryed your path with BOOTPxxx options, result panic. Trying to mount root from nfs: Panic: nfs_mountroot: RTM_ADD: 17 cpuid=1 Uptime 10s > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- alexs From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 09:25:26 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C157106566B for ; Tue, 29 Jun 2010 09:25:26 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id A02848FC17 for ; Tue, 29 Jun 2010 09:25:25 +0000 (UTC) Received: by wyb34 with SMTP id 34so1906802wyb.13 for ; Tue, 29 Jun 2010 02:25:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=Rw8+10IjOH+UEqHQAbt0+8Ei6JUNveDDe9EaRpB3lnU=; b=mZ0l8t54Pc5Y9vyDqkMjfM6YjYBrl01XDS9m5IDOezJluoIiewbzmA2I+US7iTiX2I T/ch2MYQvUVuxqPYlYOFvtWLgJCjEaM2u/JXsNK3UBKlGYy/h3a50BByhFMK9OrFDtsZ 7HfLo1KDPDtUQyYZ6cOyfJCLvtvnCNc+y6UNE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CT/rz8VU0ePWHMnddA217JxJ/43CgMhY7ATloSVoPtZZZwTbMvLEfij86P6cQV/DMo l5hc9CHtR2VGzm7oarrwxU8NQDuVOVMcRT+pKFh4gcz+hi/YOAtaFu4+CrQL7U/gRoSv 1hf81Jh4NQC/smrZShZIp0sAOpyGUSD6VKofQ= MIME-Version: 1.0 Received: by 10.227.127.83 with SMTP id f19mr4940522wbs.83.1277803519218; Tue, 29 Jun 2010 02:25:19 -0700 (PDT) Received: by 10.216.37.68 with HTTP; Tue, 29 Jun 2010 02:25:19 -0700 (PDT) Date: Tue, 29 Jun 2010 13:25:19 +0400 Message-ID: From: pluknet To: freebsd-stable Content-Type: text/plain; charset=ISO-8859-1 Subject: ps doesn't respect -o cpu keyword X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 09:25:26 -0000 Hi. I noticed that ps on all supported releases (w/ ULE) shows the value of cpu keyword always as 0 (zero). COMMAND CPU kernel/swapper 0 kernel/firmware taskq 0 kernel/thread taskq 0 kernel/kqueue taskq 0 kernel/acpi_task_0 0 kernel/acpi_task_1 0 kernel/acpi_task_2 0 kernel/igb0 taskq 0 kernel/igb1 taskq 0 init 0 g_event 0 g_up 0 g_down 0 xpt_thrd 0 sctp_iterator 0 pagedaemon 0 vmdaemon 0 pagezero 0 audit 0 idle/idle: cpu2 0 idle/idle: cpu1 0 P.S. That's only for ps; top is not affected. PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 171 ki31 0K 24K RUN 0 117.2H 43.46% {idle: cpu0} 11 root 171 ki31 0K 24K RUN 2 115.3H 40.28% {idle: cpu2} 11 root 171 ki31 0K 24K CPU1 1 103.1H 36.67% {idle: cpu1} 12 root -68 - 0K 184K CPU0 0 981:19 22.75% {irq260: igb1} 0 root -68 0 0K 64K - 1 200:18 1.07% {igb1 taskq} 12 root -32 - 0K 184K WAIT 1 55:24 0.59% {swi4: clock} 12 root -68 - 0K 184K WAIT 2 310:31 0.29% {irq259: igb1} 12 root -40 - 0K 184K WAIT 0 5:48 0.20% {swi2: cambio} 4 root -8 - 0K 8K - 2 26:21 0.00% g_down 64298 root 44 0 10748K 6776K select 2 23:06 0.00% snmpd 16 root 44 - 0K 8K syncer 2 22:22 0.00% syncer 12 root -64 - 0K 184K WAIT 1 16:22 0.00% {irq32: sym0} 13 root 44 - 0K 8K - 0 13:55 0.00% yarrow 12 root -44 - 0K 184K WAIT 2 11:39 0.00% {swi1: netisr 0} -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 09:54:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36172106564A for ; Tue, 29 Jun 2010 09:54:48 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C40FA8FC14 for ; Tue, 29 Jun 2010 09:54:47 +0000 (UTC) Received: by wyb34 with SMTP id 34so1928255wyb.13 for ; Tue, 29 Jun 2010 02:54:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=SCo5rx2ccI9+DZ5T/xRAixSNcrrPi60nHAeLDZe1WK0=; b=LLLe9kbGEbrnrGcqHOfX4h83O3tK51Z7yDw3ZyMMgmjJVBCJNvhCfZnXxRB240zYK6 PygYlY1v7tlHV3av93C57buDObQ7mdjFIp6GLOMXdmyYuAgJMjZLYljW2OT30/YsNb90 VnM8th85Kcz/mmyS0OShb1La4gZJspSEfAbXA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=rapZ4t+xjO0TsF5t6SAKk9r1QvFUhNHjpiNeyTHs+HRbOmj2Ub6xOMh7PgOwIIVQ8E Z7EsTWqw7u0wK2yk11+Zm1jHrp9EmF4Ts9lBkSZBYrU39Oj9QLT80sIaBrUgST9w84KZ AYBmTQYuTUyK5J/YKX5OUXC527xyylpFYXsFI= MIME-Version: 1.0 Received: by 10.216.89.132 with SMTP id c4mr9251831wef.106.1277805283636; Tue, 29 Jun 2010 02:54:43 -0700 (PDT) Received: by 10.216.37.68 with HTTP; Tue, 29 Jun 2010 02:54:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 29 Jun 2010 13:54:43 +0400 Message-ID: From: pluknet To: freebsd-stable Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: ps doesn't respect -o cpu keyword X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 09:54:48 -0000 On 29 June 2010 13:25, pluknet wrote: > Hi. > > I noticed that ps on all supported releases (w/ ULE) > shows the value of cpu keyword always as 0 (zero). Please, ignore my stupidity. Thought that's a CPU number. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 14:41:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84EB8106566B for ; Tue, 29 Jun 2010 14:41:59 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 344B38FC0C for ; Tue, 29 Jun 2010 14:41:58 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAI6jKUyDaFvJ/2dsb2JhbACfO3G/WYJ9gicE X-IronPort-AV: E=Sophos;i="4.53,505,1272859200"; d="scan'208";a="82108960" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 29 Jun 2010 10:41:55 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 4D4CCFB8058; Tue, 29 Jun 2010 10:41:57 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqsCFXQb-yeH; Tue, 29 Jun 2010 10:41:56 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 85465FB8012; Tue, 29 Jun 2010 10:41:56 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5TEwqw25933; Tue, 29 Jun 2010 10:58:52 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 29 Jun 2010 10:58:52 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Ian Smith In-Reply-To: <20100629134033.O9227@sola.nimnet.asn.au> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Rick C. Petty" , freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 14:41:59 -0000 On Tue, 29 Jun 2010, Ian Smith wrote: > > Not wanting to hijack this (interesting) thread, but .. > > I have to concur with Rick P - that's rather a odd requirement when each > FreeBSD install since at least 2.2 has come with root and toor (in that > order) in /etc/passwd. I don't use toor, but often enough read about > folks who do, and don't recall it ever being an issue with NFSv3. Are > you sure this is a problem that cannot be coded around in NFSv4? > Currently when the nfsuserd needs to translate a uid (such as 0) into a name (NFSv4 uses names instead of the numbers used by NFSv3), it calls getpwuid() and uses whatever name is returned. If there are more than one name for the uid (such as the above case for 0), then you get one of them and that causes confusion. I suppose if the FreeBSD world feels that "root" and "toor" must both exist in the password database, then "nfsuserd" could be hacked to handle the case of translating uid 0 to "root" without calling getpwuid(). It seems ugly, but if deleting "toor" from the password database upsets people, I can do that. rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 15:12:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 995A61065670 for ; Tue, 29 Jun 2010 15:12:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 45D178FC19 for ; Tue, 29 Jun 2010 15:12:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmUGAJeqKUyDaFvJ/2dsb2JhbACTDIw3ccAHhSQE X-IronPort-AV: E=Sophos;i="4.53,505,1272859200"; d="scan'208";a="82115123" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 29 Jun 2010 11:12:07 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id EA559FB8012; Tue, 29 Jun 2010 11:12:09 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-XUAc4uPIyj; Tue, 29 Jun 2010 11:12:08 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id AF5A0FB80FB; Tue, 29 Jun 2010 11:12:04 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5TFT1t29396; Tue, 29 Jun 2010 11:29:01 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 29 Jun 2010 11:29:00 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: alexs@ulgsm.ru In-Reply-To: <20100629064902.GA39446@mail.ulgsm.ru> Message-ID: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> <20100629064902.GA39446@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 15:12:11 -0000 On Tue, 29 Jun 2010, alexs@ulgsm.ru wrote: >> >> I think using NFS_ROOT but not the BOOTPxxx options will work around this >> or you could test the following patch and see if it helps. (Testing the >> patch would be appreciated, since I don't have any way to test across >> multiple subnets and it would be nice to have a fix for the BOOTPxxx >> cases.) >> >> rick >> --- untested patch for bootp_subr.c --- >> --- nfsclient/bootp_subr.c.sav 2010-06-28 19:16:02.000000000 -0400 >> +++ nfsclient/bootp_subr.c 2010-06-28 19:21:52.000000000 -0400 >> @@ -1524,6 +1524,7 @@ >> printf(" "); >> ifctx->gotgw = 1; >> gctx->gotgw = 1; >> + nd->mygateway = ifctx->gw; >> } >> } > > > Yes. without BOOTPxxx options boot is fine. > Ok, so at least you got it working. > > I tryed your path with BOOTPxxx options, result panic. > > Trying to mount root from nfs: > Panic: nfs_mountroot: RTM_ADD: 17 > cpuid=1 > Uptime 10s > Oh well, the patch was just a stab in the dark. The panic indicates that it already has the route set up (17 == EEXIST), so trying to set it again failed and panic'd. So, I don't know why the case with BOOTPxxx options fails to get through the gateway. If you feel like doing so, you could capture a packet trace (via tcpdump, wireshark, ...) after reverting the patch. The easiest way to do this would be to plug the client and another machine that can do the packet capture into an old 10baseT (non-switched) hub. If you don't have one of those, most network switches will allow a port to be "mirrored" (at least I think that's the term used), so that the packets come out on a second port for the machine doing the capturing. You could do a capture at the server end, but it probably wouldn't tell you anything useful (the packets wouldn't show up, is my guess?). Anyhow, thanks for the help tracking this down and we now know NFS_ROOT works for this case and BOOTPxxx doesn't, rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 15:20:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 600171065673 for ; Tue, 29 Jun 2010 15:20:35 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 0E7A58FC0A for ; Tue, 29 Jun 2010 15:20:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAMKrKUyDaFvI/2dsb2JhbACfQ3HAGYUkBJEb X-IronPort-AV: E=Sophos;i="4.53,505,1272859200"; d="scan'208";a="82116780" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 29 Jun 2010 11:20:32 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 2054594014A; Tue, 29 Jun 2010 11:20:34 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2cUw6ejQbDVN; Tue, 29 Jun 2010 11:20:33 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 4001B9400CF; Tue, 29 Jun 2010 11:20:33 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5TFbTl00616; Tue, 29 Jun 2010 11:37:29 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 29 Jun 2010 11:37:29 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Daniel Braniss In-Reply-To: Message-ID: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, alexs@ulgsm.ru Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 15:20:35 -0000 On Mon, 28 Jun 2010, Daniel Braniss wrote: >> >> >> On Mon, 28 Jun 2010, alexs@ulgsm.ru wrote: >> >>> >>> >>> kernel built with: >>> options BOOTP # Use BOOTP to obtain IP address/hostname >>> options BOOTP_NFSROOT # NFS mount root file system using BOOTP info >>> options BOOTP_NFSV3 >>> >> Try building a kernel without the above options, but with >> options NFS_ROOT >> specified. I think that's what most pxeboot users do and it was what >> I had assumed when I looked at the code. >> >> If that doesn't fix the problem...I haven't got a solution for you, rick > > I use: > options BOOTP_NFSV3 # Use NFS v3 to NFS mount root > Here's the critical snippet of code: #if defined(BOOTP_NFSROOT) && defined(BOOTP) bootpc_init(); /* use bootp to get nfs_diskless filled in */ #elif defined(NFS_ROOT) nfs_setup_diskless(); #endif Just fyi, as you can see, unless you have BOOTP_NFSROOT and BOOTP options, it does things the NFS_ROOT way and basically ignores BOOTP_NFSV3. (At least thats the way it looks to me. I've been tricked by convoluted code before:-) > but the best advice I can give, on the server run tcpdump/wireshark > it is very enlighting. > Yes, that might tell us why the case with BOOTPxxx options doesn't work through the gateway, although I'm afraid that the packets that tell us why it doesn't get past the gateway might not be getting to the server. I suggested ways to capture them in the other reply. Btw, thanks for your help testing the NFSv3 pxeboot stuff among other things you've tested, rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 15:21:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48FDA1065676 for ; Tue, 29 Jun 2010 15:21:08 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E44408FC15 for ; Tue, 29 Jun 2010 15:21:07 +0000 (UTC) Received: by vws13 with SMTP id 13so9567479vws.13 for ; Tue, 29 Jun 2010 08:20:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ap5HZNSUNASU7MnD+Pr9PvO9cTe8BjDhPFpgrKxnMX4=; b=AAHxXW889A3PJK1rq5Z5ybvZkiWv7l659uz+6Dmt5d5AIQxYaPqzVaI7HzyAEyHb8d vnjiCt2l5/kcyit0pmliTf3smZxW2cfIy1RBl2R6sD4ZJaepFVvsbymYc2htOZWayr37 QW2XJj4B2/hiOq++p6HMB7brb1u1+2q3iifWw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JWO1uyS3nFcfwLWotfDlctVOQp0Ek4AR+2FaFPPIiyqcrUFbNojcmUVcqSio3TTNZR oddzIWX5MkS9yRDdZHuF903bK/yJd38DI2j9Wo/RiPZulGfC4X1TOobXhcuhb1CBXz2k hCLJlwLEOD5eNctI2lUSlq14P/c1vsPwm9/hY= MIME-Version: 1.0 Received: by 10.224.106.18 with SMTP id v18mr4855566qao.172.1277824857680; Tue, 29 Jun 2010 08:20:57 -0700 (PDT) Received: by 10.229.109.195 with HTTP; Tue, 29 Jun 2010 08:20:57 -0700 (PDT) In-Reply-To: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> Date: Tue, 29 Jun 2010 10:20:57 -0500 Message-ID: From: Adam Vande More To: Rick Macklem Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Rick C. Petty" , freebsd-stable@freebsd.org, Ian Smith Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 15:21:08 -0000 On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote: > I suppose if the FreeBSD world feels that "root" and "toor" must both > exist in the password database, then "nfsuserd" could be hacked to handle > the case of translating uid 0 to "root" without calling getpwuid(). It > seems ugly, but if deleting "toor" from the password database upsets > people, I can do that. > I agree with Ian on this. I don't use toor either, but have seen people use it, and sometimes it will get recommended here for various reasons e.g. running a root account with a different default shell. It wouldn't bother me having to do this provided it was documented, but having to do so would be a POLA violation to many users I think. -- Adam Vande More From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 15:31:21 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19B001065670 for ; Tue, 29 Jun 2010 15:31:21 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id BE5C48FC08 for ; Tue, 29 Jun 2010 15:31:20 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmUGABquKUyDaFvI/2dsb2JhbACTDIw3ccAihSQE X-IronPort-AV: E=Sophos;i="4.53,505,1272859200"; d="scan'208";a="82273478" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 29 Jun 2010 11:31:17 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id CC58994014A; Tue, 29 Jun 2010 11:31:19 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHJpNFTMobfw; Tue, 29 Jun 2010 11:31:19 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id EF3139400CF; Tue, 29 Jun 2010 11:31:18 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5TFmFF01797; Tue, 29 Jun 2010 11:48:15 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 29 Jun 2010 11:48:15 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: alexs@ulgsm.ru In-Reply-To: <20100629064902.GA39446@mail.ulgsm.ru> Message-ID: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> <20100629064902.GA39446@mail.ulgsm.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 15:31:21 -0000 On Tue, 29 Jun 2010, alexs@ulgsm.ru wrote: > > Yes. without BOOTPxxx options boot is fine. > Btw, if you feel like helping out with testing it, I have patches for this case that modify pxeboot to use NFSv3 instead of NFSv2. The more testing they get the better. They're at: http://people.freebsd.org/~rmacklem/nfsdiskless-patches/ Have a good day, rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 15:32:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2101C1065673 for ; Tue, 29 Jun 2010 15:32:54 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-59-6.mpls.qwest.net [174.20.59.6]) by mx1.freebsd.org (Postfix) with SMTP id 961A88FC0C for ; Tue, 29 Jun 2010 15:32:53 +0000 (UTC) Received: (qmail 72176 invoked by uid 2000); 29 Jun 2010 15:32:52 -0000 Date: Tue, 29 Jun 2010 10:32:52 -0500 From: "Rick C. Petty" To: Adam Vande More Message-ID: <20100629153252.GA71786@kay.kiwi-computer.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Rick Macklem , freebsd-stable@freebsd.org, Ian Smith Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 15:32:54 -0000 On Tue, Jun 29, 2010 at 10:20:57AM -0500, Adam Vande More wrote: > On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote: > > > I suppose if the FreeBSD world feels that "root" and "toor" must both > > exist in the password database, then "nfsuserd" could be hacked to handle > > the case of translating uid 0 to "root" without calling getpwuid(). It > > seems ugly, but if deleting "toor" from the password database upsets > > people, I can do that. > > I agree with Ian on this. I don't use toor either, but have seen people use > it, and sometimes it will get recommended here for various reasons e.g. > running a root account with a different default shell. It wouldn't bother > me having to do this provided it was documented, but having to do so would > be a POLA violation to many users I think. To be fair, I'm not sure this is even a problem. Rick M. only suggested it as a possibility. I would think that getpwuid() would return the first match which has always been root. At least that's what it does when scanning the passwd file; I'm not sure about NIS. If someone can prove that this will cause a problem with NFSv4, we could consider hackingit. Otherwise I don't think we should change this behavior yet. -- Rick C. Petty From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 15:59:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49138106566C for ; Tue, 29 Jun 2010 15:59:45 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id E894D8FC1D for ; Tue, 29 Jun 2010 15:59:44 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAF+1KUyDaFvJ/2dsb2JhbACfQnHAZ4UkBA X-IronPort-AV: E=Sophos;i="4.53,505,1272859200"; d="scan'208";a="82277692" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 29 Jun 2010 11:59:41 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id DC3AAFB8058; Tue, 29 Jun 2010 11:59:43 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Hy8JsoAd8C8; Tue, 29 Jun 2010 11:59:43 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 35664FB8012; Tue, 29 Jun 2010 11:59:43 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5TGGds04724; Tue, 29 Jun 2010 12:16:39 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 29 Jun 2010 12:16:39 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100629153252.GA71786@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> <20100629153252.GA71786@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Adam Vande More , freebsd-stable@freebsd.org, Ian Smith Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 15:59:45 -0000 On Tue, 29 Jun 2010, Rick C. Petty wrote: > > To be fair, I'm not sure this is even a problem. Rick M. only suggested it > as a possibility. I would think that getpwuid() would return the first > match which has always been root. At least that's what it does when > scanning the passwd file; I'm not sure about NIS. If someone can prove > that this will cause a problem with NFSv4, we could consider hackingit. > Otherwise I don't think we should change this behavior yet. > I do know that it causes problems from my testing. I think getpwuid() gets "toor" because of the way /etc/passwd gets stored in the database created from it via "vipw". I have no problem coding it as a special case for nfsuserd and documenting it. I just won't guarantee how soon it will happen:-) rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 16:14:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEF49106566C for ; Tue, 29 Jun 2010 16:14:11 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 6BD558FC1C for ; Tue, 29 Jun 2010 16:14:11 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAOS4KUyDaFvG/2dsb2JhbACfQnHAZIUkBA X-IronPort-AV: E=Sophos;i="4.53,505,1272859200"; d="scan'208";a="82279667" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 29 Jun 2010 12:14:08 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 2D086210178; Tue, 29 Jun 2010 12:14:10 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L24qobB1m5gF; Tue, 29 Jun 2010 12:14:09 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 16138210153; Tue, 29 Jun 2010 12:14:09 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o5TGV5h06440; Tue, 29 Jun 2010 12:31:05 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 29 Jun 2010 12:31:05 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100629030633.GC63450@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> <20100629030633.GC63450@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 16:14:11 -0000 On Mon, 28 Jun 2010, Rick C. Petty wrote: >>> >> It would be interesting to see if the performance problem exists for >> NFSv3 mounts against the experimental (nfsv4) server. > > Hmm, I couldn't reproduce the problem. Once I unmounted the nfsv4 client > and tried v3, the jittering stopped. Then I unmounted v3 and tried v4 > again, no jitters. I played with a couple of combinations back and forth > (toggling the presence of "nfsv4" in the options) and sometimes I saw > jittering but only with v4, but nothing like what I was seeing before. > Perhaps this is a result of Jeremy's TCP tuning tweaks. > > This is also a difficult thing to test, because the server and client have > so much memory, they cache the date blocks. So if I try my stutter test > on the same video a second time, I only notice stutters if I skip to parts > I haven't skipped to before. I can comment that it seemed like more of a > latency issue than a throughput issue to me. But the disks aren't ever > under a high load. But it's hard to determine accurate load when the > disks are seeking. Oh, I'm using the AHCI controller mode/driver on those > disks instead of ATA, if that matters. > I basically don't have a clue what might be the source of the problem. I do agree that it sounds like an intermittent latency issue. The only thing I can think of that you might try is simply increasing the number of nfsd threads on the server. They don't add much overhead and the default of '4'is pretty small. (It's just the "-n N" option on nfsd, just in case you weren't aware of it.) > One time when I mounted the v4 again, it broke subdirectories like I was > talking about before. Essentially it would give me a readout of all the > top-level directories but wouldn't descend into subdirectories which > reflect different mountpoints on the server. An unmount and a remount > (without changes to /etc/fstab) fixed the problem. I'm wondering if there > isn't some race condition that seems to affect crossing mountpoints on the > server. When the situation happens, it affects all mountpoints equally > and persists for the duration of that mount. And of course, I can't > reproduce the problem when I try. > If it happened for a "hard mount" (no "soft,intr" mount options) then it is a real bug. The server mount point crossings are detected via a change in the value of the fsid attribute. I suspect that under some circumstances, the wrong value of fsid is getting cached in the client. (I just remembered that you use "rdirplus" and it "might" not be caching the server's notion of fsid in the right place.) If you were really keen (if you ever look up "keen" in Webster's, it's not what we tend to use it for at all. It was actually a "wail for the dead" and a keener was a professional wailer for the dead, hired for funerals of important but maybe not that well liked individuals. But I digress...), you could try a bunch of mounts./dismounts without "rdirplus" and see if you can even get it to fail without the option. > I saw the broken mountpoint crossing on another client (without any TCP > tuning) but each time it happened I saw this in the logs: > > nfscl: consider increasing kern.ipc.maxsockbuf > > Once I doubled that value, the problem went away.. at least with this > particular v4 server mountpoint. > If this had any effect, it was probably timing/latency related to a bug w.r.t. caching of the server's notion of fsid. I'll poke around and see if I can spot where this might be broken. > At the moment, things are behaving as expected. The v4 file system seems > just as fast as v3 did, and I don't need a dozen mountpoints specified > on each client thanks to v4. Once again, I thank you, Rick, for all your > hard work! > Btw, if the mountpoint crossing bug gets too irritating, you can do the multiple mounts for NFSv4 just like NFSv3. (That's what you have to do do for the Solaris10 NFSv4 client, because its completely broken w.r.t. mountpoint crossings.) rick From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 16:16:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73D80106566C for ; Tue, 29 Jun 2010 16:16:22 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email1.allantgroup.com (email1.emsphone.com [199.67.51.115]) by mx1.freebsd.org (Postfix) with ESMTP id 3A5E58FC16 for ; Tue, 29 Jun 2010 16:16:21 +0000 (UTC) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email1.allantgroup.com (8.14.0/8.14.0) with ESMTP id o5TGGKIt056858 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Jun 2010 11:16:20 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.4/8.14.4) with ESMTP id o5TGGJUh002888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Jun 2010 11:16:19 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.4/8.14.3/Submit) id o5TG6lwB078497; Tue, 29 Jun 2010 11:06:48 -0500 (CDT) (envelope-from dan) Date: Tue, 29 Jun 2010 11:06:47 -0500 From: Dan Nelson To: "Rick C. Petty" Message-ID: <20100629160647.GD50409@dan.emsphone.com> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> <20100629153252.GA71786@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100629153252.GA71786@kay.kiwi-computer.com> X-OS: FreeBSD 8.1-PRERELEASE User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: clamav-milter 0.96 at email1.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (email1.allantgroup.com [199.67.51.78]); Tue, 29 Jun 2010 11:16:20 -0500 (CDT) X-Scanned-By: MIMEDefang 2.45 Cc: Adam Vande More , Rick Macklem , freebsd-stable@freebsd.org, Ian Smith Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 16:16:22 -0000 In the last episode (Jun 29), Rick C. Petty said: > On Tue, Jun 29, 2010 at 10:20:57AM -0500, Adam Vande More wrote: > > On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote: > > > > > I suppose if the FreeBSD world feels that "root" and "toor" must both > > > exist in the password database, then "nfsuserd" could be hacked to > > > handle the case of translating uid 0 to "root" without calling > > > getpwuid(). It seems ugly, but if deleting "toor" from the password > > > database upsets people, I can do that. > > > > I agree with Ian on this. I don't use toor either, but have seen people > > use it, and sometimes it will get recommended here for various reasons > > e.g. running a root account with a different default shell. It > > wouldn't bother me having to do this provided it was documented, but > > having to do so would be a POLA violation to many users I think. > > To be fair, I'm not sure this is even a problem. Rick M. only suggested > it as a possibility. I would think that getpwuid() would return the first > match which has always been root. At least that's what it does when > scanning the passwd file; I'm not sure about NIS. If someone can prove > that this will cause a problem with NFSv4, we could consider hackingit. > Otherwise I don't think we should change this behavior yet. If there are multiple users that map to the same userid, nscd on Linux will select one name at random and return it for getpwuid() calls. I haven't seen this behaviour on FreeBSD or Solaris, though. They always seem to return the first entry in the passwd file. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 16:22:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C58B1065675 for ; Tue, 29 Jun 2010 16:22:15 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id A8C5D8FC16 for ; Tue, 29 Jun 2010 16:22:14 +0000 (UTC) Received: by wwb28 with SMTP id 28so1548215wwb.13 for ; Tue, 29 Jun 2010 09:22:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=hEH/t26Jm7Q1laCsYKvHL9Bg6syDtjWIWQWIcA9Q2Dw=; b=iXrT8e/KRF9FVUROqADm8xDXlluUF7BWwxvUauKcweDOMK6RuXyTD3oL2mc9nREt4l Tc1TMPC5rtwmcxbIhGjHOpAmTT/Mz9gMPfqRs0pGkeSgxlUo4CKVTFkpz210So+tm9uS LiANwd8DfhosUrhp1u0PsLnasbji7QqRrEKqg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=SjUNNFxoHb3FPGhq2cr565MRGyAqKQNx44tbQtGpgIS8m+PiHURAIGBp/gp5xunKHR z/XvGVW6x4VLLZaWIBGATYh0X0yU3BCA/xQ0eC4JSv/JsXUsGwv8RB45V+PPu/flgua4 3KJvjkAot5/VeWWrzfr5LPSOZ4w3p4r/Am+Tg= MIME-Version: 1.0 Received: by 10.216.184.67 with SMTP id r45mr9708798wem.15.1277827116298; Tue, 29 Jun 2010 08:58:36 -0700 (PDT) Received: by 10.216.28.200 with HTTP; Tue, 29 Jun 2010 08:58:36 -0700 (PDT) Date: Tue, 29 Jun 2010 17:58:36 +0200 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: FreeBSD Stable Mailing List Content-Type: text/plain; charset=ISO-8859-1 Subject: Panic on 8-STABLE at boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 16:22:15 -0000 i've got a panic with zfs only machine so i decided to build a witness kernel and just after the first reboot: http://img190.imageshack.us/img190/3314/panicflowtable2.jpg the second boot: no prob uname -a FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #8: Tue Jun 29 14:30:12 CEST 2010 root@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL amd64 dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log conf:http://freelooser.fr/freebsd/SECUMAIL.txt From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 16:49:41 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD491106566C for ; Tue, 29 Jun 2010 16:49:41 +0000 (UTC) (envelope-from lioux@FreeBSD.org) Received: from goat.gigo.com (ipv6.gigo.com [IPv6:2001:470:1:18::2]) by mx1.freebsd.org (Postfix) with ESMTP id 872AE8FC16 for ; Tue, 29 Jun 2010 16:49:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by goat.gigo.com (Postfix) with ESMTP id 7EFDD5C7F for ; Tue, 29 Jun 2010 09:49:41 -0700 (PDT) Received: from goat.gigo.com ([127.0.0.1]) by localhost (vette.gigo.com [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id pUlkZekJ0g+b for ; Tue, 29 Jun 2010 09:49:41 -0700 (PDT) Received: from 189.72.155.250 (189-72-155-250.bsace702.dsl.brasiltelecom.net.br [189.72.155.250]) by goat.gigo.com (Postfix) with ESMTPSA id 030815C7A for ; Tue, 29 Jun 2010 09:49:40 -0700 (PDT) Received: (qmail 67919 invoked by uid 80); 29 Jun 2010 13:46:30 -0300 Received: from 200.201.164.11 ([200.201.164.11]) by exxodus.dyndns.org (Horde Framework) with HTTP; Tue, 29 Jun 2010 13:46:54 -0300 Message-ID: <20100629134654.95522440ypjxkbcu@exxodus.dyndns.org> Date: Tue, 29 Jun 2010 13:46:54 -0300 From: Mario Sergio Fujikawa Ferreira To: Jung-uk Kim References: <20100623025855.82916.qmail@exxodus.fedaykin.here> <4C25C3D3.3030109@FreeBSD.org> <201006281401.19017.jkim@FreeBSD.org> <201006281413.18567.jkim@FreeBSD.org> (sfid-20100628_15271_589DE428) (sfid-20100628_15271_589DE428) In-Reply-To: <201006281413.18567.jkim@FreeBSD.org> (sfid-20100628_15271_589DE428) (sfid-20100628_15271_589DE428) MIME-Version: 1.0 User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (1.1.4) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Description: Plaintext Version of Message X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: d@delphij.net, freebsd-stable@FreeBSD.org, python@freebsd.org Subject: Re: FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 16:49:41 -0000 Quoting Jung-uk Kim : > On Monday 28 June 2010 02:01 pm, Jung-uk Kim wrote: >> Please drop the attached patch in ports/devel/boost-libs/files, >> rebuild all dependencies, and try your deluge ports again[1]. > > Please ignore the previous patch and try this one. Sorry, there was a > typo. :-( I updated boost-libs with your patch which fixed the issue. I no longer have the ioctl warning. :) 1) I rebuilt the libtorrent-rasterbar-14 then libtorrent-rasterbar-14-python. 2) Tried deluge, there were warnings still. 3) Then, rebuilt deluge. 4) Tried deluge, warnings were gone. I still have the lang/python26 patches you sent earlier. So I have both the python and boost-libs patches on my system. Do you want to me to do any further testing? Regards, -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." feature, n: a documented bug | bug, n: an undocumented feature From owner-freebsd-stable@FreeBSD.ORG Tue Jun 29 19:21:33 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 3AB011065678; Tue, 29 Jun 2010 19:21:33 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Mario Sergio Fujikawa Ferreira Date: Tue, 29 Jun 2010 15:21:18 -0400 User-Agent: KMail/1.6.2 References: <20100623025855.82916.qmail@exxodus.fedaykin.here> <201006281413.18567.jkim@FreeBSD.org> <20100629134654.95522440ypjxkbcu@exxodus.dyndns.org> In-Reply-To: <20100629134654.95522440ypjxkbcu@exxodus.dyndns.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201006291521.20911.jkim@FreeBSD.org> Cc: d@delphij.net, freebsd-stable@FreeBSD.org, python@FreeBSD.org Subject: Re: FreeBSD 8.1-PRERELEASE: WARNING ioctl sign-extension ioctl ffffffff8004667e X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2010 19:21:34 -0000 On Tuesday 29 June 2010 12:46 pm, Mario Sergio Fujikawa Ferreira wrote: > Quoting Jung-uk Kim : > > On Monday 28 June 2010 02:01 pm, Jung-uk Kim wrote: > >> Please drop the attached patch in ports/devel/boost-libs/files, > >> rebuild all dependencies, and try your deluge ports again[1]. > > > > Please ignore the previous patch and try this one. Sorry, there > > was a typo. :-( > > I updated boost-libs with your patch which fixed the issue. I no > longer have the ioctl warning. :) > > 1) I rebuilt the libtorrent-rasterbar-14 then > libtorrent-rasterbar-14-python. > > 2) Tried deluge, there were warnings still. > > 3) Then, rebuilt deluge. > > 4) Tried deluge, warnings were gone. > > I still have the lang/python26 patches you sent earlier. So I > have both the python and boost-libs patches on my system. > > Do you want to me to do any further testing? No, that should be good enough. Thanks for testing my patches! Jung-uk Kim From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 04:15:12 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99FEB106566B for ; Wed, 30 Jun 2010 04:15:12 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id DC6758FC0C for ; Wed, 30 Jun 2010 04:15:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o5U4EtRn096060; Wed, 30 Jun 2010 14:14:55 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 30 Jun 2010 14:14:54 +1000 (EST) From: Ian Smith To: Dan Nelson In-Reply-To: <20100629160647.GD50409@dan.emsphone.com> Message-ID: <20100630132444.G9227@sola.nimnet.asn.au> References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> <20100629153252.GA71786@kay.kiwi-computer.com> <20100629160647.GD50409@dan.emsphone.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "Rick C. Petty" , Rick Macklem , freebsd-stable@freebsd.org, Adam Vande More Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 04:15:12 -0000 On Tue, 29 Jun 2010, Dan Nelson wrote: > In the last episode (Jun 29), Rick C. Petty said: > > On Tue, Jun 29, 2010 at 10:20:57AM -0500, Adam Vande More wrote: > > > On Tue, Jun 29, 2010 at 9:58 AM, Rick Macklem wrote: > > > > > > > I suppose if the FreeBSD world feels that "root" and "toor" must both > > > > exist in the password database, then "nfsuserd" could be hacked to > > > > handle the case of translating uid 0 to "root" without calling > > > > getpwuid(). It seems ugly, but if deleting "toor" from the password > > > > database upsets people, I can do that. > > > > > > I agree with Ian on this. I don't use toor either, but have seen people > > > use it, and sometimes it will get recommended here for various reasons > > > e.g. running a root account with a different default shell. It > > > wouldn't bother me having to do this provided it was documented, but > > > having to do so would be a POLA violation to many users I think. > > > > To be fair, I'm not sure this is even a problem. Rick M. only suggested > > it as a possibility. I would think that getpwuid() would return the first > > match which has always been root. At least that's what it does when > > scanning the passwd file; I'm not sure about NIS. If someone can prove > > that this will cause a problem with NFSv4, we could consider hackingit. > > Otherwise I don't think we should change this behavior yet. > > If there are multiple users that map to the same userid, nscd on Linux will > select one name at random and return it for getpwuid() calls. I haven't > seen this behaviour on FreeBSD or Solaris, though. They always seem to > return the first entry in the passwd file. I wondered whether this might be a Linux thing. On my 7.2 system, % find /usr/src -name "*.[ch]" -exec grep -Hw getpwuid {} \; > file returns 195 lines, many in the form getpwuid(getuid()), in many base and contrib components - including id(1), bind, sendmail etc - that could be nondeterministic if getpwuid(0) ever returned other than root. Just one mention of 'toor' in /usr/src/usr.sbin/makefs/compat/pwcache.c Not claiming to know how the lookups in /usr/src/lib/libc/gen/getpwent.c work under the hood, but this does seem likely a non-issue on FreeBSD. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 06:14:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3CB8106564A for ; Wed, 30 Jun 2010 06:14:41 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id 562AD8FC0A for ; Wed, 30 Jun 2010 06:14:40 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1OTqZC-000Km1-07; Wed, 30 Jun 2010 09:14:38 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Rick Macklem In-reply-to: References: <20100625152027.GA78442@mail.ulgsm.ru> <20100626113418.GA80299@mail.ulgsm.ru> <20100628061601.GA51359@mail.ulgsm.ru> <20100628102703.GA78354@mail.ulgsm.ru> Comments: In-reply-to Rick Macklem message dated "Tue, 29 Jun 2010 11:37:29 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jun 2010 09:14:37 +0300 From: Daniel Braniss Message-ID: Cc: freebsd-stable@freebsd.org, alexs@ulgsm.ru Subject: Re: diskless boot, nfs server behind router X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 06:14:41 -0000 > > > On Mon, 28 Jun 2010, Daniel Braniss wrote: > > >> > >> > >> On Mon, 28 Jun 2010, alexs@ulgsm.ru wrote: > >> > >>> > >>> > >>> kernel built with: > >>> options BOOTP # Use BOOTP to obtain IP address/hostname > >>> options BOOTP_NFSROOT # NFS mount root file system using BOOTP info > >>> options BOOTP_NFSV3 > >>> > >> Try building a kernel without the above options, but with > >> options NFS_ROOT > >> specified. I think that's what most pxeboot users do and it was what > >> I had assumed when I looked at the code. > >> > >> If that doesn't fix the problem...I haven't got a solution for you, rick > > > > I use: > > options BOOTP_NFSV3 # Use NFS v3 to NFS mount root > > > > Here's the critical snippet of code: > #if defined(BOOTP_NFSROOT) && defined(BOOTP) > bootpc_init(); /* use bootp to get nfs_diskless filled in */ > #elif defined(NFS_ROOT) > nfs_setup_diskless(); > #endif > > Just fyi, as you can see, unless you have BOOTP_NFSROOT and BOOTP options, > it does things the NFS_ROOT way and basically ignores BOOTP_NFSV3. > (At least thats the way it looks to me. I've been tricked by convoluted > code before:-) you are correct, I missed the NFS_ROOT which is defined in GENERIC, and yes, convoluted is an understatement :-) danny From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 09:30:27 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4016A1065674 for ; Wed, 30 Jun 2010 09:30:27 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id C29008FC24 for ; Wed, 30 Jun 2010 09:30:26 +0000 (UTC) Received: by fxm13 with SMTP id 13so274401fxm.13 for ; Wed, 30 Jun 2010 02:30:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=5XMMPDMi1g0YGyz0W4Awg80poLD9rkrLEmtys4W1JR0=; b=istgdXMGAR0NmmwgMMX6oriOuVuD6lCQJqXM5S5GeobULbB1U/aj5eCHycw0IaNATa TiBNkjqRlwIB2BOkojJ/Y4R50Yq83icHvWhFpCTbhlFvfznxavGQa47zRCqlv8brs+Hb FS2RhRxBEb2SDZlS8aYu59PzSUe6tQdn0eMRs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=r0HCQINx+TG6hIAnKeEykyLG4DcugSc92947bugvULqvvxlMnVppsw7a7r0xEhr3Ij vE8cj66kIS7tJV7Q3p8AddiaQNavJ0c1yiJsCFmmKSsEu8brEyBxEfxToTVs9e+ZQMQW 7u9NlhadvdGPBxjGEPDK3rVx5hzuCahz+2c0I= MIME-Version: 1.0 Received: by 10.216.164.70 with SMTP id b48mr11026729wel.21.1277890216871; Wed, 30 Jun 2010 02:30:16 -0700 (PDT) Received: by 10.216.28.200 with HTTP; Wed, 30 Jun 2010 02:30:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Jun 2010 11:30:16 +0200 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: FreeBSD Stable Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Panic on 8-STABLE at boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 09:30:27 -0000 and after 9 hours, another panic: http://freelooser.fr/freebsd/deadlock.jpg any help is appreciated 2010/6/29 Micka=EBl Maillot : > i've got a panic with zfs only machine so i decided to build a witness ke= rnel > and just after the first reboot: > http://img190.imageshack.us/img190/3314/panicflowtable2.jpg > > the second boot: no prob > > uname -a > FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE > #8: Tue Jun 29 14:30:12 CEST 2010 > root@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL =A0amd64 > > dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log > conf:http://freelooser.fr/freebsd/SECUMAIL.txt > From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 11:00:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 054B71065673 for ; Wed, 30 Jun 2010 11:00:59 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8CE998FC0A for ; Wed, 30 Jun 2010 11:00:58 +0000 (UTC) Received: by ewy26 with SMTP id 26so212660ewy.13 for ; Wed, 30 Jun 2010 04:00:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OgCzu42AhzMCFnv2Ykvla24QyBzaHoaKfUcBZY+XIek=; b=KgAX2nY5WAzCIpmKK7CGXc2F2SSLe0Ea+xd7e0RqrYxMtKDUZ+/dIDOLxtzRvZ+9ja AlhyPpq+yhvTZaUEHQgC6lmbgWNo1y8l0UCmLb2Lx8eoofuIhYqTUi/PM8n6MH42hiR4 aHSlgqfgwMcnCzNqoDeLXHkv26YhhTrsFVEeI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=W/v2ZUzs8y1wpDJkmR9hSaoemOrlEsdrHMvHXHAZ3MK6NMwPGOzp3fwsZ4SDRlqJTC nVxYQnh34jasRCzuEmvu9bKLVb5KxERo2W3ItC5JPa0uI1E0LZnzmoSoAFJO3uKmPnb/ bzFiQFZh46Hb2MN1vz4IWYzD0c2/jJs1nZYf8= MIME-Version: 1.0 Received: by 10.216.161.11 with SMTP id v11mr11124569wek.31.1277895650356; Wed, 30 Jun 2010 04:00:50 -0700 (PDT) Received: by 10.216.37.68 with HTTP; Wed, 30 Jun 2010 04:00:50 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Jun 2010 15:00:50 +0400 Message-ID: From: pluknet To: =?ISO-8859-1?Q?Micka=EBl_Maillot?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Stable Mailing List , Kip Macy Subject: Re: Panic on 8-STABLE at boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 11:00:59 -0000 On 29 June 2010 19:58, Micka=EBl Maillot wrote: > i've got a panic with zfs only machine so i decided to build a witness ke= rnel > and just after the first reboot: > http://img190.imageshack.us/img190/3314/panicflowtable2.jpg > > the second boot: no prob > > uname -a > FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE > #8: Tue Jun 29 14:30:12 CEST 2010 > root@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL =A0amd64 > > dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log > conf:http://freelooser.fr/freebsd/SECUMAIL.txt This afaik was fixed a while ago in CURRENT: http://svn.freebsd.org/viewvc/base?view=3Drevision&revision=3D207303 I wonder it's not MFC'ed yet. --=20 wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 11:28:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31A8A1065678 for ; Wed, 30 Jun 2010 11:28:52 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id BEC798FC15 for ; Wed, 30 Jun 2010 11:28:51 +0000 (UTC) Received: by wyb34 with SMTP id 34so859789wyb.13 for ; Wed, 30 Jun 2010 04:28:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=amNipMq1cnMI8/TfBjjg3L7HyTVnuVfhulTdD9TAjSg=; b=viELy42Vzov05qrEv0w5Jn9LQQ4WcJ0B/l2d9EQk8djOBIbcGQAbGOBGQ/DS2QhMHM a59Z2SVhhnMFWUfF8dFZNMAhbuevzQ+YnTB5sv3LicBAtHX5Q6kegD76yUI0K1xVkzvc FsIxCilE8FyraTMXRi6J/VGpVq4ITySoSuuuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=WF58C+bLYU/79PfoLGwYdMlblINN20vrW425MpCYxEC73wnUUmIU0GtVaZT4wuyM0o pv+0moEk2QjHauWC07itAfb6jS0k8XuzZwRFDf8xsv58E0Cn8UgFJnpsHBfDTohik4Ql LSnOZcGmPrCWy2xOMF7GSM9rYGr8bp4Dr+MC0= MIME-Version: 1.0 Received: by 10.216.158.85 with SMTP id p63mr6947837wek.67.1277897330874; Wed, 30 Jun 2010 04:28:50 -0700 (PDT) Received: by 10.216.37.68 with HTTP; Wed, 30 Jun 2010 04:28:50 -0700 (PDT) Date: Wed, 30 Jun 2010 15:28:50 +0400 Message-ID: From: pluknet To: freebsd-stable Content-Type: text/plain; charset=ISO-8859-1 Subject: pde.demotions counts even if pg_ps disabled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 11:28:52 -0000 HI. This is 7.3-RELEASE-p1 right after boot. Looks like pmap_demote_pde is not properly protected w/ pg_ps_enabled. # sysctl vm.pmap vm.pmap.pmap_collect_active: 0 vm.pmap.pmap_collect_inactive: 0 vm.pmap.pv_entry_spare: 1421 vm.pmap.pv_entry_allocs: 686316 vm.pmap.pv_entry_frees: 675473 vm.pmap.pc_chunk_tryfail: 0 vm.pmap.pc_chunk_frees: 5392 vm.pmap.pc_chunk_allocs: 5465 vm.pmap.pc_chunk_count: 73 vm.pmap.pv_entry_count: 10843 vm.pmap.pde.promotions: 0 vm.pmap.pde.p_failures: 0 vm.pmap.pde.mappings: 0 vm.pmap.pde.demotions: 5 vm.pmap.shpgperproc: 200 vm.pmap.pv_entry_max: 4264612 vm.pmap.pg_ps_enabled: 0 # uptime 3:25PM up 19 mins, 2 users, load averages: 0.00, 0.00, 0.01 -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 12:57:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F990106566B for ; Wed, 30 Jun 2010 12:57:37 +0000 (UTC) (envelope-from nickolasbug@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D77148FC20 for ; Wed, 30 Jun 2010 12:57:36 +0000 (UTC) Received: by mail-fx0-f54.google.com with SMTP id 13so437327fxm.13 for ; Wed, 30 Jun 2010 05:57:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=5ByfJvbyBh+jUxMuz/msJKJU8iCcMJdIxpZgJOtC39g=; b=d2v0FKA5p6gRm4WcqxcHrnXE3mmPf2YUKMb4TUqM0tICskmEeZE0PsGIjgAT42LhQC nAvQyx3ID5I1PMH2aVWEGdrBqVCBwkV9cEh1ooFYBQfS+uImxgk2NDxykIomoyIdXFWG JPWvZ3YESRM3N25k2Djeenip+qUmo4jl77/rs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=R1dHkKQncoxJUUp9EeuzjXg2UFKqn/eo9DGZ7fUJhO15McIqYKEJdVulxSTBI9ZEcS fqK5PBA8fGYPDac9p3h4h7uOpDpin2e+fz49U9P3iTFwRX2G993rD2v2MTPwNijsOPop mj7tCcY41+SEWvP8RvpOnrZhVZksicWe+yir8= MIME-Version: 1.0 Received: by 10.216.176.7 with SMTP id a7mr11289258wem.59.1277902655987; Wed, 30 Jun 2010 05:57:35 -0700 (PDT) Received: by 10.216.51.141 with HTTP; Wed, 30 Jun 2010 05:57:35 -0700 (PDT) Date: Wed, 30 Jun 2010 15:57:35 +0300 Message-ID: From: nickolasbug@gmail.com To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Kernel panic in pppoe_findsession (ng_pppoe.c) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 12:57:37 -0000 Hello! Yestarday I've got 4 kernel panics with the same problem - page fault while in kernel mode, in netgraph pppoe module. I've defined, that fault produce pppoe_findsession() function - see below. Here is the contents of /var/crash/info.5 file: Dump header from device /dev/gpt/swap Architecture: amd64 Architecture Version: 2 Dump Length: 1490821120B (1421 MB) Blocksize: 512 Dumptime: Tue Jun 29 14:35:53 2010 Hostname: cloud Magic: FreeBSD Kernel Dump Version String: FreeBSD 8.1-PRERELEASE #18: Sun Jun 6 00:32:09 EEST 2010 root@cloud:/usr/obj/usr/src/sys/CLOUD Panic String: page fault Dump Parity: 4273635620 Bounds: 5 Dump Status: good I can give more information, if you need (core.txt.5 file, kernel config file, etc). And here is kgdb log: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x8064ed050 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff803c2869 stack pointer = 0x28:0xffffff803bee7880 frame pointer = 0x28:0xffffff803bee78c0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (nfe0 taskq) trap number = 12 panic: page fault cpuid = 1 Uptime: 19d12h24m25s Physical memory: 2024 MB Dumping 1421 MB: 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262 1246 1230 1214 1198 1182 1166 1150 1134 1118 1102 1086 1070 1054 1038 1022 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14 Reading symbols from /boot/kernel/vesa.ko...Reading symbols from /boot/kernel/vesa.ko.symbols...done. done. Loaded symbols for /boot/kernel/vesa.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from /boot/kernel/snd_hda.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_hda.ko Reading symbols from /boot/kernel/acpi_asus.ko...Reading symbols from /boot/kernel/acpi_asus.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_asus.ko Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols from /boot/kernel/acpi_aiboost.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi_aiboost.ko Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko Reading symbols from /boot/kernel/procfs.ko...Reading symbols from /boot/kernel/procfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/procfs.ko Reading symbols from /boot/kernel/pseudofs.ko...Reading symbols from /boot/kernel/pseudofs.ko.symbols...done. done. Loaded symbols for /boot/kernel/pseudofs.ko Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from /boot/kernel/linprocfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linprocfs.ko Reading symbols from /boot/kernel/linsysfs.ko...Reading symbols from /boot/kernel/linsysfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/linsysfs.ko Reading symbols from /boot/kernel/blank_saver.ko...Reading symbols from /boot/kernel/blank_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/blank_saver.ko Reading symbols from /usr/local/modules/rtc.ko...done. Loaded symbols for /usr/local/modules/rtc.ko Reading symbols from /boot/kernel/if_gif.ko...Reading symbols from /boot/kernel/if_gif.ko.symbols...done. done. Loaded symbols for /boot/kernel/if_gif.ko #0 doadump () at pcpu.h:223 223 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) list *0xffffffff803c2869 0xffffffff803c2869 is in pppoe_findsession (/usr/src/sys/netgraph/ng_pppoe.c:567). 562 uint16_t hash = SESSHASH(session); 563 sessp sp = NULL; 564 565 mtx_lock(&privp->sesshash[hash].mtx); 566 LIST_FOREACH(sp, &privp->sesshash[hash].head, sessions) { 567 if (sp->Session_ID == session && 568 bcmp(sp->pkt_hdr.eh.ether_dhost, 569 wh->eh.ether_shost, ETHER_ADDR_LEN) == 0) { 570 break; 571 } (kgdb) backtrace #0 doadump () at pcpu.h:223 #1 0xffffffff802e7cd9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xffffffff802e810c in panic (fmt=0xffffffff80581c64 "%s") at /usr/src/sys/kern/kern_shutdown.c:590 #3 0xffffffff8051dfd8 in trap_fatal (frame=0xffffff0002415ba0, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:777 #4 0xffffffff8051e3a4 in trap_pfault (frame=0xffffff803bee77d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:693 #5 0xffffffff8051ebf2 in trap (frame=0xffffff803bee77d0) at /usr/src/sys/amd64/amd64/trap.c:451 #6 0xffffffff805047f3 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:223 #7 0xffffffff803c2869 in pppoe_findsession (privp=0xffffff8000838000, wh=Variable "wh" is not available. ) at /usr/src/sys/netgraph/ng_pppoe.c:566 #8 0xffffffff803c3094 in ng_pppoe_rcvdata_ether (hook=Variable "hook" is not available. ) at /usr/src/sys/netgraph/ng_pppoe.c:1613 #9 0xffffffff803bd5b3 in ng_apply_item (node=0xffffff0002c5e600, item=0xffffff0002c67a80, rw=0) at /usr/src/sys/netgraph/ng_base.c:2336 #10 0xffffffff803bc62d in ng_snd_item (item=Variable "item" is not available. ) at /usr/src/sys/netgraph/ng_base.c:2253 #11 0xffffffff803a0917 in ether_demux (ifp=0xffffff0002941000, m=0xffffff0029860a00) at /usr/src/sys/net/if_ethersubr.c:918 #12 0xffffffff803a0d73 in ether_input (ifp=0xffffff0002941000, m=0xffffff0029860a00) at /usr/src/sys/net/if_ethersubr.c:760 #13 0xffffffff803a085f in ether_demux (ifp=0xffffff0002940800, m=0xffffff0029860a00) at /usr/src/sys/net/if_ethersubr.c:810 #14 0xffffffff803a0d73 in ether_input (ifp=0xffffff0002940800, m=0xffffff0029860a00) at /usr/src/sys/net/if_ethersubr.c:760 #15 0xffffffff80538377 in nfe_int_task (arg=Variable "arg" is not available. ) at /usr/src/sys/dev/nfe/if_nfe.c:2119 #16 0xffffffff80323852 in taskqueue_run (queue=0xffffff00026f3d00) at /usr/src/sys/kern/subr_taskqueue.c:239 #17 0xffffffff80323ac6 in taskqueue_thread_loop (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/subr_taskqueue.c:360 #18 0xffffffff802bf397 in fork_exit (callout=0xffffffff80323a80 , arg=0xffffff80003c61b8, frame=0xffffff803bee7c80) at /usr/src/sys/kern/kern_fork.c:844 #19 0xffffffff80504cce in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:562 #20 0x0000000000000000 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x0000000000000000 in ?? () #24 0x0000000000000000 in ?? () #25 0x0000000000000000 in ?? () #26 0x0000000000000000 in ?? () #27 0x0000000000000000 in ?? () #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000000000000000 in ?? () #31 0x0000000000000000 in ?? () #32 0x0000000000000000 in ?? () #33 0x0000000000000000 in ?? () #34 0x0000000000000000 in ?? () #35 0x0000000000000000 in ?? () #36 0x0000000000000000 in ?? () #37 0x0000000000000000 in ?? () #38 0x0000000000000000 in ?? () #39 0x0000000000000000 in ?? () #40 0x0000000000000000 in ?? () #41 0x0000000000000000 in ?? () #42 0x0000000000000000 in ?? () #43 0x0000000000000000 in ?? () #44 0x000000000173d000 in ?? () #45 0x0000000000000000 in ?? () #46 0xffffff0002415ba0 in ?? () #47 0xffffffff80764900 in affinity () #48 0xffffff00022fe7c0 in ?? () #49 0xffffff803bee7440 in ?? () #50 0xffffff803bee73f8 in ?? () #51 0xffffff0002415ba0 in ?? () #52 0xffffffff8030b7e3 in sched_switch (td=0xffffff80003c61b8, newtd=0xffffffff80323a80, flags=Variable "flags" is not available. ) at /usr/src/sys/kern/sched_ule.c:1844 Previous frame inner to this frame (corrupt stack?) From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 13:43:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD2D0106564A for ; Wed, 30 Jun 2010 13:43:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id AE84B8FC18 for ; Wed, 30 Jun 2010 13:43:45 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 5C73146B35; Wed, 30 Jun 2010 09:43:45 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 663DF8A04F; Wed, 30 Jun 2010 09:43:44 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 30 Jun 2010 09:36:23 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201006300936.23839.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 30 Jun 2010 09:43:44 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: pluknet Subject: Re: pde.demotions counts even if pg_ps disabled X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 13:43:45 -0000 On Wednesday 30 June 2010 7:28:50 am pluknet wrote: > HI. > > This is 7.3-RELEASE-p1 right after boot. > Looks like pmap_demote_pde is not properly protected w/ pg_ps_enabled. The direct map always uses superpages, but we may demote a superpage in the direct map due to conflict caching attributes (all PCI BARs are mapped UC for example). -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 13:53:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3D131065675 for ; Wed, 30 Jun 2010 13:53:17 +0000 (UTC) (envelope-from freebsd@vfemail.net) Received: from vfemail.net (dotsevenfive.vfemail.net [69.11.239.75]) by mx1.freebsd.org (Postfix) with ESMTP id 5EC998FC13 for ; Wed, 30 Jun 2010 13:53:16 +0000 (UTC) Received: (qmail 76678 invoked by uid 89); 30 Jun 2010 13:21:31 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with SMTP; 30 Jun 2010 13:21:31 -0000 Received: (qmail 63487 invoked by uid 89); 30 Jun 2010 12:16:08 -0000 Received: from unknown (HELO www-51-2.vfemail.net) (vfemail@172.16.100.51) by FreeQueue with SMTP; 30 Jun 2010 12:16:08 -0000 Received: (qmail 39228 invoked by uid 89); 30 Jun 2010 12:16:53 -0000 Received: by simscan 1.4.0 ppid: 39151, pid: 39223, t: 0.2599s scanners:none Received: from unknown (HELO bofh-x.m0osk.net) (ZnJlZWJzZEB2ZmVtYWlsLm5ldA==@82.3.149.69) by mail.vfemail.net with ESMTPA; 30 Jun 2010 12:16:53 -0000 Message-ID: <4C2B35A2.7010709@vfemail.net> Date: Wed, 30 Jun 2010 13:16:34 +0100 From: Free BSD User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.9.1.9) Gecko/20100412 Thunderbird/3.0.4 MIME-Version: 1.0 To: FreeBSD Stable Mailing List Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: kernel issues with 8 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 13:53:18 -0000 Dear List Members I have recently installed 8 STABLE and built my custom kernel, but still getting these in my pciconf list none0@pci0:0:3:0: class=0x078000 card=0x02761028 chip=0x2e148086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Active Client Manager HECI Device (PCIVEN_8086&DEV_2E14&SUBSYS_3035103C&REV_03B1B68)' class = simple comms none1@pci0:0:3:3: class=0x070002 card=0x02761028 chip=0x2e178086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel PCI Serial Port (CC_0700)' class = simple comms subclass = UART I have device uart # Generic UART driver in my custom kernel, so I would expect uart devices to be detected and usable -- however, they are not. Also, even though I have custom keyboard in my kernel configuration, whenever I boot into single user mode I get US layout (it works fine when in multi-user mode). I am using a Dell Optiplex 960 series machine. I have googled as much as I can, and also visited the intel website for further information -- no luck so far. Any pointer to possible solution is highly appreciated Thanks From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 14:15:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA846106564A for ; Wed, 30 Jun 2010 14:15:54 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id B25AE8FC15 for ; Wed, 30 Jun 2010 14:15:54 +0000 (UTC) Received: from omta02.emeryville.ca.mail.comcast.net ([76.96.30.19]) by qmta12.emeryville.ca.mail.comcast.net with comcast id cD8Q1e0050QkzPwACEFtcL; Wed, 30 Jun 2010 14:15:53 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta02.emeryville.ca.mail.comcast.net with comcast id cEFs1e00J3S48mS8NEFsdV; Wed, 30 Jun 2010 14:15:53 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 012BD9B425; Wed, 30 Jun 2010 07:15:51 -0700 (PDT) Date: Wed, 30 Jun 2010 07:15:51 -0700 From: Jeremy Chadwick To: Free BSD Message-ID: <20100630141551.GA61130@icarus.home.lan> References: <4C2B35A2.7010709@vfemail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C2B35A2.7010709@vfemail.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Stable Mailing List Subject: Re: kernel issues with 8 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 14:15:54 -0000 On Wed, Jun 30, 2010 at 01:16:34PM +0100, Free BSD wrote: > Dear List Members > > I have recently installed 8 STABLE and built my custom kernel, but > still getting these in my pciconf list > > none0@pci0:0:3:0: class=0x078000 card=0x02761028 > chip=0x2e148086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel Active Client Manager HECI Device > (PCIVEN_8086&DEV_2E14&SUBSYS_3035103C&REV_03B1B68)' > class = simple comms > > > none1@pci0:0:3:3: class=0x070002 card=0x02761028 > chip=0x2e178086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel PCI Serial Port (CC_0700)' > class = simple comms > subclass = UART > > > I have > device uart # Generic UART driver > in my custom kernel, so I would expect uart devices to be detected > and usable -- however, they are not. Are you including "device puc" in your device list? puc connects PCI-based serial/parallel devices to uart/sio and ppc. Please see the uart(4) man page. > Also, even though I have custom keyboard in my kernel configuration, > whenever I boot into single user mode I get US layout (it works fine > when in multi-user mode). This is probably normal. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Wed Jun 30 16:27:20 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76F08106566B for ; Wed, 30 Jun 2010 16:27:20 +0000 (UTC) (envelope-from pmather@vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.freebsd.org (Postfix) with ESMTP id 1ED238FC08 for ; Wed, 30 Jun 2010 16:27:19 +0000 (UTC) Received: from zidane.cc.vt.edu (zidane.cc.vt.edu [198.82.163.227]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id o5UG7np3027671 for ; Wed, 30 Jun 2010 12:07:55 -0400 Received: from auth3.smtp.vt.edu (EHLO auth3.smtp.vt.edu) ([198.82.161.152]) by zidane.cc.vt.edu (MOS 4.1.8-GA FastPath queued) with ESMTP id JAT90770; Wed, 30 Jun 2010 12:07:54 -0400 (EDT) Received: from gromit.tower.lib.vt.edu (gromit.tower.lib.vt.edu [128.173.51.22]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id o5UG7scX028035 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 30 Jun 2010 12:07:54 -0400 From: Paul Mather Content-Type: multipart/signed; boundary=Apple-Mail-7--1040836416; protocol="application/pkcs7-signature"; micalg=sha1 Date: Wed, 30 Jun 2010 12:07:54 -0400 Message-Id: To: FreeBSD Stable Mime-Version: 1.0 (Apple Message framework v1081) X-Mailer: Apple Mail (2.1081) X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu pmather@vt.edu 2 pass X-Mirapoint-IP-Reputation: reputation=neutral-1, source=Fixed, refid=n/a, actions=MAILHURDLE SPF TAG X-Junkmail-Status: score=10/50, host=zidane.cc.vt.edu X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A020203.4C2B6BDA.032E,ss=1,fgs=0, ip=0.0.0.0, so=2009-09-22 00:05:22, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 16:27:20 -0000 --Apple-Mail-7--1040836416 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I am running FreeBSD/amd64 RELENG_8 on a Dell Optiplex 745. The hard = drive in the system is SATA and I have "Normal", not "Legacy" SATA = support enabled in the BIOS. (BIOS is V2.6.4.) I am assuming this will = enable native AHCI mode for the drive. I built a kernel with ATA_CAM support, but for some reason the SATA = drive is probing at slow, UDMA2, speeds: ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 SATA 2.x device ada0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) ada0: 152587MB (312500000 512 byte sectors: 16H 63S/T 16383C) When I run "camcontrol identify" on the drive, it states the drive is = capable of UDMA6 speeds: backup# camcontrol identify ada0 pass0: ATA-7 SATA 2.x device pass0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) protocol ATA/ATAPI-7 SATA 2.x device model ST3160812AS firmware revision 3.ADJ serial number 5LS8PPDD cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 312500000 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6=20 Feature Support Enable Value Vendor read ahead yes yes write cache yes yes flush cache yes yes overlap no Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management yes yes 254/0xFE 208/0xD0 media status notification no no power-up in Standby no no write-read-verify no no 0/0x0 unload no no free-fall no no data set management (TRIM) no So, why the slower speed? Also, "camcontrol identify" states the drive = supports NCQ with up to 32 tags supported, yet "camcontrol tags ada0" = reports only 1 device opening, not 32 as I would expect: backup# camcontrol tags ada0 (pass0:ata2:0:0:0): device openings: 1 To enable ATA_CAM AHCI support, I included this in my kernel config = file: # ATA and ATAPI devices options ATA_CAM device ahci device atacore device atapci options ATA_STATIC_ID # Static device numbering Is this the correct way to enable ATA_CAM AHCI support? I tried = initially including just "options ATA_CAM" and "device ahci" but the = resultant kernel would not probe my disk drive as ada0. Does my problem lie with my kernel config or is the Dell Optiplex 745 = BIOS brain dead when it comes to AHCI native support? The only option = it appears to have in the BIOS is "Normal" and "Legacy" when it comes to = the SATA controller mode. I've attached my full kernel config and dmesg at the end of this e-mail. Cheers, Paul. Kernel config: # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual = page, # and/or the handbook section on Kernel Configuration Files: # # = http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-con= fig.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check = first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.531.2.13 2010/05/02 06:24:17 = imp Exp $ cpu HAMMER ident VPN # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for = devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=3Dvalue', see kenv(1) # # env "GENERIC.env" #makeoptions DEBUG=3D-g # Build kernel with gdb(1) debug = symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread = preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission = Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates = support options UFS_ACL # Support for access control = lists options UFS_DIRHASH # Improve performance on big = directories options UFS_GJOURNAL # Enable gjournal-based UFS = journaling options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFSLOCKD # Network Lock Manager #options NFS_ROOT # NFS usable as /, requires = NFSCLIENT #options MSDOSFS # MSDOS Filesystem #options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires = PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat (sgtty) options COMPAT_FREEBSD32 # Compatible with i386 binaries #options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options COMPAT_FREEBSD5 # Compatible with FreeBSD5 #options COMPAT_FREEBSD6 # Compatible with FreeBSD6 #options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SCSI_DELAY=3D5000 # Delay (in ms) before = probing SCSI options KTRACE # ktrace(1) support options STACK # stack(9) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options P1003_1B_SEMAPHORES # POSIX-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time = extensions options PRINTF_BUFR_SIZE=3D128 # Prevent printf output being = interspersed. options KBD_INSTALL_CDEV # install a CDEV entry in /dev options HWPMC_HOOKS # Necessary kernel hooks for = hwpmc(4) options AUDIT # Security event auditing options MAC # TrustedBSD MAC Framework options FLOWTABLE # per-cpu routing cache #options KDTRACE_FRAME # Ensure frames are compiled in #options KDTRACE_HOOKS # Kernel DTrace hooks options INCLUDE_CONFIG_FILE # Include this file in kernel # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor = Kernel # CPU frequency control device cpufreq # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices options ATA_CAM device ahci device atacore device atapci options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI = access) device ses # SCSI Environmental Services (and = SAF-TE) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Serial (COM) ports device uart # Generic UART driver # Parallel port device ppc device ppbus # Parallel port bus (required) # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these = NICs! device miibus # MII bus support device bge # Broadcom BCM570xx Gigabit Ethernet # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device vlan # 802.1Q VLAN support device tun # Packet tunnel. device pty # BSD-style compatibility pseudo ttys device md # Memory "disks" device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support options USB_DEBUG # enable debug msgs device uhci # UHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ukbd # Keyboard device umass # Disks/Mass storage - Requires scbus = and da device ums # Mouse # pf firewall with ALTQ support device pf device pflog device pfsync options ALTQ options ALTQ_CBQ # Class Bases Queuing (CBQ) options ALTQ_RED # Random Early Detection (RED) options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) options ALTQ_PRIQ # Priority Queuing (PRIQ) options ALTQ_NOPCC # Required for SMP build # In order to enable IPSEC you MUST also add device crypto to=20 # your kernel configuration options IPSEC # IP security (requires device crypto) options IPSEC_NAT_T # NAT-T support, UDP encap of ESP device crypto # core crypto support Dmesg: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-PRERELEASE #7: Mon Jun 28 13:02:30 EDT 2010 paul@backup.tower.lib.vt.edu:/usr/obj/usr/src/sys/VPN amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz (1862.01-MHz = K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x6f6 Family =3D 6 Model =3D f = Stepping =3D 6 = Features=3D0xbfebfbff = Features2=3D0xe3bd AMD Features=3D0x20000800 AMD Features2=3D0x1 TSC: P-state invariant real memory =3D 536870912 (512 MB) avail memory =3D 504094720 (480 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 cryptosoft0: on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, f00000 (3) failed acpi0: reservation of 1000000, 1edffc00 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on = acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 acpi_button0: enable wake failed pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: mem = 0xfc000000-0xfcffffff,0xd0000000-0xdfffffff,0xfd000000-0xfdffffff irq 16 = at device 0.0 on pci1 uhci0: port 0xff20-0xff3f irq = 16 at device 26.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0xff00-0xff1f irq = 17 at device 26.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 ehci0: mem = 0xfebfbc00-0xfebfbfff irq 22 at device 26.7 on pci0 ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: on ehci0 hdac0: mem = 0xfebfc000-0xfebfffff irq 16 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20100226_0142 hdac0: [ITHREAD] pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 bge0: mem 0xfbef0000-0xfbefffff irq 16 at device 0.0 on pci3 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-FDX, auto bge0: Ethernet address: 00:19:b9:17:ba:4f bge0: [FILTER] uhci2: port 0xff80-0xff9f irq = 23 at device 29.0 on pci0 uhci2: [ITHREAD] usbus3: on uhci2 uhci3: port 0xff60-0xff7f irq = 17 at device 29.1 on pci0 uhci3: [ITHREAD] usbus4: on uhci3 uhci4: port 0xff40-0xff5f irq = 18 at device 29.2 on pci0 uhci4: [ITHREAD] usbus5: on uhci4 ehci1: mem = 0xff980800-0xff980bff irq 23 at device 29.7 on pci0 ehci1: [ITHREAD] usbus6: EHCI version 1.0 usbus6: on ehci1 pcib4: at device 30.0 on pci0 pci4: on pcib4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port = 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xec= c0-0xeccf irq 20 at device 31.2 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ichsmb0: port 0xece0-0xecff mem = 0xfebfbb00-0xfebfbbff irq 20 at device 31.3 on pci0 ichsmb0: [ITHREAD] smbus0: on ichsmb0 atapci1: port = 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xec= d0-0xecdf irq 20 at device 31.5 on pci0 atapci1: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] atrtc0: port 0x70-0x7f irq 8 on acpi0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppc0: [ITHREAD] ppbus0: on ppc0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] orm0: at iomem = 0xc0000-0xce7ff,0xce800-0xd07ff,0xd0800-0xd3fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. hdac0: HDA Codec #0: Analog Devices AD1983 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 480Mbps High Speed USB v2.0 pcm0: at cad 0 nid 1 on hdac0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 ata4: timeout waiting for read DRQ ata4: timeout waiting for read DRQ ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 SATA 2.x device ada0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) ada0: 152587MB (312500000 512 byte sectors: 16H 63S/T 16383C) lapic1: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! cd0 at ata4 bus 0 scbus2 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device=20 cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present = - tray closed uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered Root mount waiting for: usbus6 usbus2 Root mount waiting for: usbus6 usbus2 uhub2: 4 ports with 4 removable, self powered uhub6: 6 ports with 6 removable, self powered Root mount waiting for: usbus6 ugen6.2: at usbus6 umass0: = on usbus6 umass0: SCSI over Bulk-Only; quirks =3D 0x0000 ugen1.2: at usbus1 ukbd0: on usbus1 kbd2 at ukbd0 Root mount waiting for: usbus6 Trying to mount root from ufs:/dev/ada0s1a ugen1.3: at usbus1 ums0: = on usbus1 ums0: 3 buttons and [XYZ] coordinates ID=3D0 bge0: link state changed to UP --Apple-Mail-7--1040836416-- From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 17:12:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 497841065670 for ; Wed, 30 Jun 2010 17:12:41 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 317F88FC23 for ; Wed, 30 Jun 2010 17:12:40 +0000 (UTC) Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta03.emeryville.ca.mail.comcast.net with comcast id cGim1e0031eYJf8A3HCgHW; Wed, 30 Jun 2010 17:12:40 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta19.emeryville.ca.mail.comcast.net with comcast id cHCf1e00M3S48mS01HCgux; Wed, 30 Jun 2010 17:12:40 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 676FD9B425; Wed, 30 Jun 2010 10:12:39 -0700 (PDT) Date: Wed, 30 Jun 2010 10:12:39 -0700 From: Jeremy Chadwick To: Paul Mather Message-ID: <20100630171239.GA65888@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Stable Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 17:12:41 -0000 On Wed, Jun 30, 2010 at 12:07:54PM -0400, Paul Mather wrote: > I am running FreeBSD/amd64 RELENG_8 on a Dell Optiplex 745. The hard drive in the system is SATA and I have "Normal", not "Legacy" SATA support enabled in the BIOS. (BIOS is V2.6.4.) I am assuming this will enable native AHCI mode for the drive. That isn't correct. Some Dell OptiPlex systems explicitly have an AHCI option in their BIOS for enabling/disabling AHCI. I do not believe the 745 offers this capability, which means no AHCI is available. (We use these OptiPlex models at my workplace so I'm familiar with them) > I built a kernel with ATA_CAM support, but for some reason the SATA drive is probing at slow, UDMA2, speeds: I don't know anything about this option, but the "common" way to get ATA to utilise SCSI CAM is to enable AHCI in one's system BIOS and load the ahci.ko (not ataahci.ko) driver using /boot/loader.conf (ahci_load="yes") or "load ahci" from the loader "OK" prompt. That's literally all you need. In your case since you don't have AHCI available, you're probably going to have to stick to using standard ata(4) (read: remove ATA_CAM and ahci from your kernel configuration). Be aware ahci.ko IS NOT the same thing as ataahci.ko. The latter adds AHCI support but via the classic ata(4) layer (meaning: AHCI without SCSI CAM. This also lacks NCQ support, but does gain you hot-swap capability). > Does my problem lie with my kernel config or is the Dell Optiplex 745 > BIOS brain dead when it comes to AHCI native support? The only option > it appears to have in the BIOS is "Normal" and "Legacy" when it comes > to the SATA controller mode. It's not "brain dead". "Normal" is not the same thing as AHCI. "Normal" tells the controller to run in standard SATA mode, "Legacy" causes the controller to emulate classic PATA (literally you'll see PATA controllers show up on IRQs 14 and 15, etc.). Validation that your system doesn't have AHCI enabled/doesn't have AHCI available is here: > atapci0: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xecc0-0xeccf irq 20 at device 31.2 on pci0 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > atapci1: port 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xecd0-0xecdf irq 20 at device 31.5 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] An AHCI-enabled controller, with a system using ahci.ko, will look like this: ahci0: port 0x1c50-0x1c57,0x1c44-0x1c47,0x1c48-0x1c4f,0x1c40-0x1c43,0x18e0-0x18ff mem 0xdc000800-0xdc000fff irq 17 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: at channel 1 on ahci0 ahcich1: [ITHREAD] ahcich2: at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: at channel 3 on ahci0 ahcich3: [ITHREAD] ahcich4: at channel 4 on ahci0 ahcich4: [ITHREAD] ahcich5: at channel 5 on ahci0 ahcich5: [ITHREAD] -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Wed Jun 30 17:39:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69D51106566B for ; Wed, 30 Jun 2010 17:39:06 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id E988C8FC15 for ; Wed, 30 Jun 2010 17:39:05 +0000 (UTC) Received: by fxm13 with SMTP id 13so754582fxm.13 for ; Wed, 30 Jun 2010 10:38:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=EdxiXjEZ9VFIoOvU0stso47aBR+DYo3wHJfyIHRKQBE=; b=A6N5aau+V5spLEzs/J4wSyU0LE4x1F3KgQ45JnT/B3rfeCZ3zN552EtNb0kEr7y0Wu jGOMpAVU9B4xtJ8n/5MLjfNLNdX6mjahbgn4vBt3Xnyzp2VMZsgt6umhxkBxlfgAOols mYsRuWJbDSb3bUiwaa2g6kYEnvcZp5XvBhiqo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=nirteEKcoZvU0jaNi9Yo17PdE7cOmdPXq5twOytCw9U6o6ynrEiE7Ha56v2qQCZfsr 2SoAfln5P+qJGkTrhUfNgUT9v2rO9A4S0/52SWbjaHB3GKmCfVi3CBtZtUbb/sPmHJ5C qKxkIshySfEBdSOW1X9Mhq3G7TsfF3bueLbAM= Received: by 10.223.47.145 with SMTP id n17mr8060123faf.26.1277919534972; Wed, 30 Jun 2010 10:38:54 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id z12sm50955819fah.33.2010.06.30.10.38.53 (version=SSLv3 cipher=RC4-MD5); Wed, 30 Jun 2010 10:38:54 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C2B8103.6010409@FreeBSD.org> Date: Wed, 30 Jun 2010 20:38:11 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: FreeBSD Stable References: In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , Paul Mather Subject: Re: Fwd: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 17:39:06 -0000 Garrett Cooper wrote: > I am running FreeBSD/amd64 RELENG_8 on a Dell Optiplex 745. The hard > drive in the system is SATA and I have "Normal", not "Legacy" SATA > support enabled in the BIOS. (BIOS is V2.6.4.) I am assuming this > will enable native AHCI mode for the drive. > > I built a kernel with ATA_CAM support, but for some reason the SATA > drive is probing at slow, UDMA2, speeds: > > ada0 at ata2 bus 0 scbus0 target 0 lun 0 > ada0: ATA-7 SATA 2.x device > ada0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) > ada0: 152587MB (312500000 512 byte sectors: 16H 63S/T 16383C) > When I run "camcontrol identify" on the drive, it states the drive is > capable of UDMA6 speeds: > > backup# camcontrol identify ada0 > PIO supported PIO4 > DMA supported WDMA2 UDMA6 > Native Command Queuing (NCQ) yes 32 tags > > So, why the slower speed? Also, "camcontrol identify" states the > drive supports NCQ with up to 32 tags supported, yet "camcontrol tags > ada0" reports only 1 device opening, not 32 as I would expect: > > backup# camcontrol tags ada0 > (pass0:ata2:0:0:0): device openings: 1 Speed, number of tags and other options limited by lowest of device and controller capabilities. > To enable ATA_CAM AHCI support, I included this in my kernel config file: > > # ATA and ATAPI devices > options ATA_CAM > device ahci > device atacore > device atapci > options ATA_STATIC_ID # Static device numbering > > Is this the correct way to enable ATA_CAM AHCI support? I tried > initially including just "options ATA_CAM" and "device ahci" but the > resultant kernel would not probe my disk drive as ada0. Your controller seems to not report AHCI support. In such case legacy mode driver attaches to it. But as soon as you have no `device ataintel` line, only generic driver was there, limited by UDMA2 mode. PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. > Does my problem lie with my kernel config or is the Dell Optiplex 745 > BIOS brain dead when it comes to AHCI native support? The only option > it appears to have in the BIOS is "Normal" and "Legacy" when it comes > to the SATA controller mode. Your controller is not identified as AHCI: > atapci0: port > 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xecc0-0xeccf > irq 20 at device 31.2 on pci0 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > atapci1: port > 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xecd0-0xecdf > irq 20 at device 31.5 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] You may check `pciconf -lvcb` output. For ICH8 with AHCI you should see there something like: ahci0@pci0:0:31:2: class=0x010601 card=0xa00c14ff chip=0x28298086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile SATA AHCI Controller' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0xe880, size 8, enabled bar [14] = type I/O Port, range 32, base 0xe800, size 4, enabled bar [18] = type I/O Port, range 32, base 0xe480, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xe400, size 4, enabled bar [20] = type I/O Port, range 32, base 0xe080, size 32, enabled bar [24] = type Memory, range 32, base 0xfeaff800, size 2048, enabled cap 05[80] = MSI supports 4 messages enabled with 4 messages cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair Pay attention to "subclass = SATA". -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 20:52:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B40061065674; Wed, 30 Jun 2010 20:52:54 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.freebsd.org (Postfix) with ESMTP id 2350F8FC1C; Wed, 30 Jun 2010 20:52:54 +0000 (UTC) Received: from dagger.cc.vt.edu (dagger.cc.vt.edu [198.82.163.114]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id o5UKqNUt024852; Wed, 30 Jun 2010 16:52:23 -0400 Received: from auth3.smtp.vt.edu (EHLO auth3.smtp.vt.edu) ([198.82.161.152]) by dagger.cc.vt.edu (MOS 4.1.8-GA FastPath queued) with ESMTP id JYN40265; Wed, 30 Jun 2010 16:52:23 -0400 (EDT) Received: from gromit.tower.lib.vt.edu (gromit.tower.lib.vt.edu [128.173.51.22]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id o5UKqN1h022895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 30 Jun 2010 16:52:23 -0400 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Paul Mather In-Reply-To: <4C2B8103.6010409@FreeBSD.org> Date: Wed, 30 Jun 2010 16:52:22 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> References: <4C2B8103.6010409@FreeBSD.org> To: FreeBSD Stable X-Mailer: Apple Mail (2.1081) X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu paul@gromit.dlib.vt.edu 5 none X-Mirapoint-IP-Reputation: reputation=neutral-1, source=Fixed, refid=n/a, actions=MAILHURDLE SPF TAG X-Junkmail-Status: score=10/50, host=dagger.cc.vt.edu X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A020206.4C2BAE87.017E,ss=1,fgs=0, ip=0.0.0.0, so=2009-09-22 00:05:22, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Cc: Alexander Motin Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 20:52:54 -0000 On Jun 30, 2010, at 1:38 PM, Alexander Motin wrote: >> To enable ATA_CAM AHCI support, I included this in my kernel config = file: >>=20 >> # ATA and ATAPI devices >> options ATA_CAM >> device ahci >> device atacore >> device atapci >> options ATA_STATIC_ID # Static device numbering >>=20 >> Is this the correct way to enable ATA_CAM AHCI support? I tried >> initially including just "options ATA_CAM" and "device ahci" but the >> resultant kernel would not probe my disk drive as ada0. >=20 > Your controller seems to not report AHCI support. In such case legacy > mode driver attaches to it. But as soon as you have no `device = ataintel` > line, only generic driver was there, limited by UDMA2 mode. >=20 > PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. Thank you (and Jeremy Chadwick) for the help and information. The = kernel configuration options I used above were taken from a VirtualBox = FreeBSD/amd64 install I have that I converted over to ATA_CAM when the = code first went into RELENG_8 and it wasn't exactly clear at the time = what options were absolutely required. (I'm not even sure that "options = ATA_CAM" is needed any more, given "device ahci" implies it.) >> Does my problem lie with my kernel config or is the Dell Optiplex 745 >> BIOS brain dead when it comes to AHCI native support? The only = option >> it appears to have in the BIOS is "Normal" and "Legacy" when it comes >> to the SATA controller mode. >=20 > Your controller is not identified as AHCI: >=20 >> atapci0: port >> = 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xec= c0-0xeccf >> irq 20 at device 31.2 on pci0 >> atapci0: [ITHREAD] >> ata2: on atapci0 >> ata2: [ITHREAD] >> ata3: on atapci0 >> ata3: [ITHREAD] >> atapci1: port >> = 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xec= d0-0xecdf >> irq 20 at device 31.5 on pci0 >> atapci1: [ITHREAD] >> ata4: on atapci1 >> ata4: [ITHREAD] >> ata5: on atapci1 >> ata5: [ITHREAD] >=20 > You may check `pciconf -lvcb` output. For ICH8 with AHCI you should = see > there something like: > ahci0@pci0:0:31:2: class=3D0x010601 card=3D0xa00c14ff = chip=3D0x28298086 > rev=3D0x03 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Mobile SATA AHCI Controller' > class =3D mass storage > subclass =3D SATA > bar [10] =3D type I/O Port, range 32, base 0xe880, size 8, = enabled > bar [14] =3D type I/O Port, range 32, base 0xe800, size 4, = enabled > bar [18] =3D type I/O Port, range 32, base 0xe480, size 8, = enabled > bar [1c] =3D type I/O Port, range 32, base 0xe400, size 4, = enabled > bar [20] =3D type I/O Port, range 32, base 0xe080, size 32, = enabled > bar [24] =3D type Memory, range 32, base 0xfeaff800, size 2048, = enabled > cap 05[80] =3D MSI supports 4 messages enabled with 4 messages > cap 01[70] =3D powerspec 3 supports D0 D3 current D0 > cap 12[a8] =3D SATA Index-Data Pair >=20 > Pay attention to "subclass =3D SATA". Then that's where my problem lies: atapci0@pci0:0:31:2: class=3D0x01018f card=3D0x01da1028 = chip=3D0x28208086 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'SATA IDE Controller:4 port (82801HB/HR/HH/HO)' class =3D mass storage subclass =3D ATA bar [10] =3D type I/O Port, range 32, base 0xfe00, size 8, = enabled bar [14] =3D type I/O Port, range 32, base 0xfe10, size 4, = enabled bar [18] =3D type I/O Port, range 32, base 0xfe20, size 8, = enabled bar [1c] =3D type I/O Port, range 32, base 0xfe30, size 4, = enabled bar [20] =3D type I/O Port, range 32, base 0xfec0, size 16, = enabled bar [24] =3D type I/O Port, range 32, base 0xecc0, size 16, = enabled cap 01[70] =3D powerspec 3 supports D0 D3 current D0 atapci1@pci0:0:31:5: class=3D0x010185 card=3D0x01da1028 = chip=3D0x28258086 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801H (ICH8 Family) 2 port SATA Controller' class =3D mass storage subclass =3D ATA bar [10] =3D type I/O Port, range 32, base 0xfe40, size 8, = enabled bar [14] =3D type I/O Port, range 32, base 0xfe50, size 4, = enabled bar [18] =3D type I/O Port, range 32, base 0xfe60, size 8, = enabled bar [1c] =3D type I/O Port, range 32, base 0xfe70, size 4, = enabled bar [20] =3D type I/O Port, range 32, base 0xfed0, size 16, = enabled bar [24] =3D type I/O Port, range 32, base 0xecd0, size 16, = enabled cap 01[70] =3D powerspec 3 supports D0 D3 current D0 I thought ICH8 supported AHCI, but maybe it's only ICH8R that does? I'm = assuming that "subclass =3D ATA" means the controller can't operate in = AHCI mode. The BIOS setting is also confusing. It has two options, = "Normal" and "Legacy." "Normal" mode says, "The hard drive controller = is configured for native mode. This mode provides the highest drive = performance and most flexibility." I guess I misinterpreted "native = mode" to be AHCI mode. Thanks again for the help and for clearing things up. Cheers, Paul.= From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 21:19:20 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D82C1065672 for ; Wed, 30 Jun 2010 21:19:20 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id A53C38FC17 for ; Wed, 30 Jun 2010 21:19:19 +0000 (UTC) Received: by fxm13 with SMTP id 13so872321fxm.13 for ; Wed, 30 Jun 2010 14:19:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=xhvHOghjSa4BBAcIBRX5lclBHSSLrkMF5aQzu6QI+NA=; b=aFyWXLBsFplC866MutEkyrtv57OdkG3YmnFW0C1UGbttgmKJxuUu3/6N6ThTN4SEIX zrM933X4oVgPHyyNO0Zk7iFTSo3O4yyAWtyYmKuqXtTA+4GGyy0NlYamarFgfGkx7IWt EzfTg6a5WTHM/WswlcIpH+uNdogYiUY3DdJq4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=eBawfwTT6r4EPd1R9ecFoq+GGJhaqYz7+x+apyWr+mMVmdGqqwQf2zbyDxatVSq3Cd HRNJhNFHB02kskBy+fgxM8/ngYP1RiVEgD1v+qLUq04pzFETStN3IsaFOeoh2Mn+tFoS pht93lZehfnI01tCOHq2vvohz1aYcZquLOuXA= Received: by 10.223.109.146 with SMTP id j18mr8326182fap.87.1277932754895; Wed, 30 Jun 2010 14:19:14 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id e10sm51378189fak.14.2010.06.30.14.19.13 (version=SSLv3 cipher=RC4-MD5); Wed, 30 Jun 2010 14:19:14 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C2BB4A6.7040800@FreeBSD.org> Date: Thu, 01 Jul 2010 00:18:30 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Paul Mather References: <4C2B8103.6010409@FreeBSD.org> <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> In-Reply-To: <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 21:19:20 -0000 Paul Mather wrote: >> PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. > > Thank you (and Jeremy Chadwick) for the help and information. The kernel configuration options I used above were taken from a VirtualBox FreeBSD/amd64 install I have that I converted over to ATA_CAM when the code first went into RELENG_8 and it wasn't exactly clear at the time what options were absolutely required. (I'm not even sure that "options ATA_CAM" is needed any more, given "device ahci" implies it.) `options ATA_CAM` enables CAM wrapper for legacy drivers, which gave you adaX devices instead of adX. It doesn't give major benefits, just unifies behavior. > I thought ICH8 supported AHCI, but maybe it's only ICH8R that does? All ICH8 support AHCI, though not all BIOSes initialize them respectively. The only benefit of ICH8R is a port multipliers support, though it also seems to be artificial limitation - I've seen BIOS allowing it on regular ICH8. > I'm assuming that "subclass = ATA" means the controller can't operate in AHCI mode. Yes. At least it is not configured to do so. > The BIOS setting is also confusing. It has two options, "Normal" and "Legacy." "Normal" mode says, "The hard drive controller is configured for native mode. This mode provides the highest drive performance and most flexibility." I guess I misinterpreted "native mode" to be AHCI mode. "Native" mode means that ATA controllers works as normal PCI device. In "Legacy" mode controller uses legacy ISA I/O ports and IRQs. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 21:21:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACD29106564A for ; Wed, 30 Jun 2010 21:21:40 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 9125B8FC1D for ; Wed, 30 Jun 2010 21:21:40 +0000 (UTC) Received: from omta03.emeryville.ca.mail.comcast.net ([76.96.30.27]) by qmta12.emeryville.ca.mail.comcast.net with comcast id cE7t1e00D0b6N64ACMMfHL; Wed, 30 Jun 2010 21:21:39 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta03.emeryville.ca.mail.comcast.net with comcast id cMMe1e00B3S48mS8PMMfyC; Wed, 30 Jun 2010 21:21:39 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 695699B425; Wed, 30 Jun 2010 14:21:38 -0700 (PDT) Date: Wed, 30 Jun 2010 14:21:38 -0700 From: Jeremy Chadwick To: Paul Mather Message-ID: <20100630212138.GA71370@icarus.home.lan> References: <4C2B8103.6010409@FreeBSD.org> <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Alexander Motin , FreeBSD Stable Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 21:21:40 -0000 On Wed, Jun 30, 2010 at 04:52:22PM -0400, Paul Mather wrote: > I thought ICH8 supported AHCI, but maybe it's only ICH8R that does? No, not necessarily. There are ICHxx (non-ICHxxR) models which definitely provide AHCI (ex. ICHxxM for their Mobile chipsets; yes, many laptops do have AHCI capability). Thus there are many different sub-models of ICH8, in addition to different perf/chip revisions of ICH8. Specification details: http://www.intel.com/assets/pdf/datasheet/313056.pdf http://www.intel.com/design/chipsets/specupdt/313057.htm Dell very likely chose not to engineer this particular motherboard to not provide AHCI capability (Option ROM space (usually included with the system BIOS), PCI and ICH8 register setups (done by the BIOS), etc.)). I know Gigabyte has done this with some of their boards as well. If you have concerns that your motherboard provides features that you can't use, you need to contact Dell. > I'm assuming that "subclass = ATA" means the controller can't operate > in AHCI mode. The BIOS setting is also confusing. It has two > options, "Normal" and "Legacy." "Normal" mode says, "The hard drive > controller is configured for native mode. This mode provides the > highest drive performance and most flexibility." I guess I > misinterpreted "native mode" to be AHCI mode. "Native", "Normal", and "Enhanced" are all terms used to describe the controller operating in standard SATA (non-AHCI) fashion. Dell's in-BIOS description is nothing but schmooze; it's not the same as AHCI. "Legacy" just means the controller appears and operates purely in PATA-esque mode, so that you can use SATA drives on systems which don't have SATA chipset drivers (ex. MS-DOS). To get an idea of what an AHCI-capable board offers via the BIOS, you should review the following manual for a Supermicro ICH7-based system. This chipset is older than yours, chosen for sake of example. See Chapter 7-3, section "Main Setup Features": http://www.supermicro.com/manuals/superserver/1U/MNL-0813.pdf Furthermore, I can assure you that the Dell OptiPlex 745 Mini-Tower offers AHCI capability, and toggling its use via the system BIOS. You won't find it mentioned in Dell's "Tech Specs" PDF about this though. I realise this is not the system you have, but I'm simply pointing out that it's a board manufacturer decision whether or not to provide the capability, and that their decision obviously changed over the years. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Wed Jun 30 21:57:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D736106566C; Wed, 30 Jun 2010 21:57:57 +0000 (UTC) (envelope-from akihiko@e-tokyo.prug.or.jp) Received: from lepus.e-tokyo.prug.or.jp (lepus.e-tokyo.prug.or.jp [IPv6:2001:218:4a2:10:21c:c4ff:fedb:f712]) by mx1.freebsd.org (Postfix) with ESMTP id 01E5D8FC1B; Wed, 30 Jun 2010 21:57:56 +0000 (UTC) Received: from lyra.e-tokyo.prug.or.jp (lyra.e-tokyo.prug.or.jp [IPv6:2001:218:4a2:10:21c:c4ff:fe5f:160f]) by lepus.e-tokyo.prug.or.jp (8.14.4/8.14.3) with ESMTP id o5ULvsIC006500; Thu, 1 Jul 2010 06:57:54 +0900 (JST) Date: Thu, 01 Jul 2010 06:57:49 +0900 (JST) Message-Id: <20100701.065749.1568838937885851562.akihiko@e-tokyo.prug.or.jp> To: freebsd@jdc.parodius.com From: Akihiko Taniguchi In-Reply-To: <20100630212138.GA71370@icarus.home.lan> References: <4C2B8103.6010409@FreeBSD.org> <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> <20100630212138.GA71370@icarus.home.lan> X-Mailer: Mew version 7.0.50 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, mav@freebsd.org Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 21:57:57 -0000 xc From owner-freebsd-stable@FreeBSD.ORG Wed Jun 30 23:54:47 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3F77106566C for ; Wed, 30 Jun 2010 23:54:47 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 5E9CB8FC08 for ; Wed, 30 Jun 2010 23:54:47 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAG92K0yDaFvG/2dsb2JhbACfVXHALoUlBA X-IronPort-AV: E=Sophos;i="4.53,516,1272859200"; d="scan'208";a="82488289" Received: from amazon.cs.uoguelph.ca ([131.104.91.198]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 30 Jun 2010 19:54:44 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 4AE59210190; Wed, 30 Jun 2010 19:54:46 -0400 (EDT) X-Virus-Scanned: amavisd-new at amazon.cs.uoguelph.ca Received: from amazon.cs.uoguelph.ca ([127.0.0.1]) by localhost (amazon.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oylgWZOEUh4Z; Wed, 30 Jun 2010 19:54:45 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by amazon.cs.uoguelph.ca (Postfix) with ESMTP id 1774E210175; Wed, 30 Jun 2010 19:54:45 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o610Bhb10601; Wed, 30 Jun 2010 20:11:44 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 30 Jun 2010 20:11:42 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Ian Smith In-Reply-To: <20100630132444.G9227@sola.nimnet.asn.au> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628140054.GA52174@kay.kiwi-computer.com> <20100629134033.O9227@sola.nimnet.asn.au> <20100629153252.GA71786@kay.kiwi-computer.com> <20100629160647.GD50409@dan.emsphone.com> <20100630132444.G9227@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "Rick C. Petty" , Dan Nelson , freebsd-stable@freebsd.org, Adam Vande More Subject: Re: Why is NFSv4 so slow? (root/toor) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2010 23:54:47 -0000 On Wed, 30 Jun 2010, Ian Smith wrote: > > I wondered whether this might be a Linux thing. On my 7.2 system, > > % find /usr/src -name "*.[ch]" -exec grep -Hw getpwuid {} \; > file > > returns 195 lines, many in the form getpwuid(getuid()), in many base and > contrib components - including id(1), bind, sendmail etc - that could be > nondeterministic if getpwuid(0) ever returned other than root. > > Just one mention of 'toor' in /usr/src/usr.sbin/makefs/compat/pwcache.c > > Not claiming to know how the lookups in /usr/src/lib/libc/gen/getpwent.c > work under the hood, but this does seem likely a non-issue on FreeBSD. > I remember it causing some confusion while testing, but I can't remember when or where. It might have been Linux or I might have been logged in as "toor" or ???? I think I will hardcode the "root" case in nfsuserd, just to be safe. (I also migt have editted /etc/passwd and reordered entries without paying attention to it.) rick From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 06:23:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E72106566C for ; Thu, 1 Jul 2010 06:23:40 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 00FAD8FC20 for ; Thu, 1 Jul 2010 06:23:38 +0000 (UTC) Received: by ewy26 with SMTP id 26so718671ewy.13 for ; Wed, 30 Jun 2010 23:23:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fFXPn7gWNAnraCB+zj/iIorxf8EhfAaNtr0Ok9EWK44=; b=VXumX/mnsjZPY3Jo1xzAUN0uwmKmTWxaE1zWN+I5FZo/thgEoM+kI0Bhz96YkFfjWx oIoQE4kev283uV+E7diDzbIIsy8zMkkbiUD6Bdi3mDunY7bEi07pIazNcfSHhh7uxKjI KfVo+vu+wyfgwk80/98fnBI787YC1YNxA3pNM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QpdxCMu56nmkryjg+TpRVsxohX0puxhHF/LhqiW0OQS7UXE5SCjt7kOj5E10ddUDsH tjlIHoYyPna3dhKxPL241rL+11F2mb49/4fzanpOwyrfx7ANLCndHsDaHlkcSKjOEpUh Bd/Xq2w6cdKetznWibtI2JPXVqmGQfJrx6NZQ= MIME-Version: 1.0 Received: by 10.213.19.211 with SMTP id c19mr1668379ebb.93.1277965407571; Wed, 30 Jun 2010 23:23:27 -0700 (PDT) Received: by 10.216.28.200 with HTTP; Wed, 30 Jun 2010 23:23:27 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Jul 2010 08:23:27 +0200 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: pluknet Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Stable Mailing List , Kip Macy Subject: Re: Panic on 8-STABLE at boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 06:23:40 -0000 thx pluknet. my second panic appear today on 3 recent 8-stable amd64 machine after doing 8 ~ 10h of zfs receive. 2010/6/30 pluknet : > On 29 June 2010 19:58, Micka=EBl Maillot wrot= e: >> i've got a panic with zfs only machine so i decided to build a witness k= ernel >> and just after the first reboot: >> http://img190.imageshack.us/img190/3314/panicflowtable2.jpg >> >> the second boot: no prob >> >> uname -a >> FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE >> #8: Tue Jun 29 14:30:12 CEST 2010 >> root@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL =A0amd64 >> >> dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log >> conf:http://freelooser.fr/freebsd/SECUMAIL.txt > > This afaik was fixed a while ago in CURRENT: > http://svn.freebsd.org/viewvc/base?view=3Drevision&revision=3D207303 > > I wonder it's not MFC'ed yet. > > -- > wbr, > pluknet > From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 09:27:11 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27A2E106566B; Thu, 1 Jul 2010 09:27:11 +0000 (UTC) (envelope-from mickael.maillot@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 87E8A8FC12; Thu, 1 Jul 2010 09:27:10 +0000 (UTC) Received: by ewy26 with SMTP id 26so802911ewy.13 for ; Thu, 01 Jul 2010 02:26:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EBLads1zQ4Eq+WtdSosmyZF+p7pCZ74hAi/tif+Jt5c=; b=QwDsRLE2mPaKmLzPwbt0lNa3Ni5O9DUH07FcbhWAlervcIrdXSl6N1LO8U5Q4DpOI8 f9ICtDDD7G9SdcSziIm3tOB+AIR04sYSrytlWHDQ3fGFuLAASzcLkOk9YJBzeuk71jWk /PANnfdgMX36sSMBx24APputWS/EEKHjnCVao= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wXO0ReB9HYRe6np+Ov6K2bMCXkWAb7ITIivUwx0U71/38hPfw+1i+6Sqw+y7zaFLbJ a76Jf3RyGrkuto6cSqWt4Qqq/rrg3ujuqwt0yamAeDoGVMDw/91mjqzaiS0KsDSRtXAK YH3++D7yh1jEP+tfG2AS+8mFjmFfXEQLyUiow= MIME-Version: 1.0 Received: by 10.213.9.204 with SMTP id m12mr1972704ebm.61.1277976416832; Thu, 01 Jul 2010 02:26:56 -0700 (PDT) Received: by 10.216.28.200 with HTTP; Thu, 1 Jul 2010 02:26:56 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Jul 2010 11:26:56 +0200 Message-ID: From: =?ISO-8859-1?Q?Micka=EBl_Maillot?= To: pluknet Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Stable Mailing List , Kip Macy Subject: Re: Panic on 8-STABLE at boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 09:27:11 -0000 a little more info about thread 100090 http://freelooser.fr/freebsd/deadlock3.jpg 2010/7/1 Micka=EBl Maillot : > thx pluknet. > > my second panic appear today on 3 recent 8-stable amd64 machine after > doing 8 ~ 10h of zfs receive. > > 2010/6/30 pluknet : >> On 29 June 2010 19:58, Micka=EBl Maillot wro= te: >>> i've got a panic with zfs only machine so i decided to build a witness = kernel >>> and just after the first reboot: >>> http://img190.imageshack.us/img190/3314/panicflowtable2.jpg >>> >>> the second boot: no prob >>> >>> uname -a >>> FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE >>> #8: Tue Jun 29 14:30:12 CEST 2010 >>> root@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL =A0amd64 >>> >>> dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log >>> conf:http://freelooser.fr/freebsd/SECUMAIL.txt >> >> This afaik was fixed a while ago in CURRENT: >> http://svn.freebsd.org/viewvc/base?view=3Drevision&revision=3D207303 >> >> I wonder it's not MFC'ed yet. >> >> -- >> wbr, >> pluknet >> > From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 12:40:05 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B11A4106567D; Thu, 1 Jul 2010 12:40:05 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.freebsd.org (Postfix) with ESMTP id 611258FC19; Thu, 1 Jul 2010 12:40:05 +0000 (UTC) Received: from steiner.cc.vt.edu (steiner.cc.vt.edu [198.82.163.51]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id o61CdBCu018487; Thu, 1 Jul 2010 08:39:34 -0400 Received: from auth3.smtp.vt.edu (EHLO auth3.smtp.vt.edu) ([198.82.161.152]) by steiner.cc.vt.edu (MOS 4.1.8-GA FastPath queued) with ESMTP id IUL46682; Thu, 01 Jul 2010 08:39:34 -0400 (EDT) Received: from gromit.tower.lib.vt.edu (gromit.tower.lib.vt.edu [128.173.51.22]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id o61CdY43030716 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Jul 2010 08:39:34 -0400 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Paul Mather In-Reply-To: <4C2BB4A6.7040800@FreeBSD.org> Date: Thu, 1 Jul 2010 08:39:34 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <91399FEA-024C-4CA1-BCBD-208B41AA9C59@gromit.dlib.vt.edu> References: <4C2B8103.6010409@FreeBSD.org> <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> <4C2BB4A6.7040800@FreeBSD.org> To: Alexander Motin X-Mailer: Apple Mail (2.1081) X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu paul@gromit.dlib.vt.edu 5 none X-Mirapoint-IP-Reputation: reputation=neutral-1, source=Fixed, refid=n/a, actions=MAILHURDLE SPF TAG X-Junkmail-Status: score=10/50, host=steiner.cc.vt.edu X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A020202.4C2C8C86.0247,ss=1,fgs=0, ip=0.0.0.0, so=2009-09-22 00:05:22, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false Cc: FreeBSD Stable Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 12:40:05 -0000 On Jun 30, 2010, at 5:18 PM, Alexander Motin wrote: > Paul Mather wrote: >>> PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. >>=20 >> Thank you (and Jeremy Chadwick) for the help and information. The = kernel configuration options I used above were taken from a VirtualBox = FreeBSD/amd64 install I have that I converted over to ATA_CAM when the = code first went into RELENG_8 and it wasn't exactly clear at the time = what options were absolutely required. (I'm not even sure that "options = ATA_CAM" is needed any more, given "device ahci" implies it.) >=20 > `options ATA_CAM` enables CAM wrapper for legacy drivers, which gave = you > adaX devices instead of adX. It doesn't give major benefits, just > unifies behavior. So, does that mean if you omit "options ATA_CAM" and have "device ahci" = you will get adX devices, not adaX devices? In other words, if you have = "device ahci" (or "device siis" or "device mvs") will you will always = get adaX devices, whether or not you have "options ATA_CAM" in your = kernel config file? Does "options ATA_CAM" work with "device ata" or the modular ATA = subsystem? Is that the intended use of "options ATA_CAM": to provide = adaX devices and a CAM interface for accessing ATA devices? Cheers, Paul.= From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 12:46:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEEFB1065672 for ; Thu, 1 Jul 2010 12:46:07 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 99A888FC14 for ; Thu, 1 Jul 2010 12:46:07 +0000 (UTC) Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta13.westchester.pa.mail.comcast.net with comcast id cahb1e0020xGWP85Dcm7UU; Thu, 01 Jul 2010 12:46:07 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta12.westchester.pa.mail.comcast.net with comcast id ccm51e00G3S48mS3Ycm6vh; Thu, 01 Jul 2010 12:46:07 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5E9719B425; Thu, 1 Jul 2010 05:46:04 -0700 (PDT) Date: Thu, 1 Jul 2010 05:46:04 -0700 From: Jeremy Chadwick To: Paul Mather Message-ID: <20100701124604.GA93927@icarus.home.lan> References: <4C2B8103.6010409@FreeBSD.org> <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> <20100630212138.GA71370@icarus.home.lan> <5F157782-DAA6-4AB6-91CB-BC1863F17B83@gromit.dlib.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5F157782-DAA6-4AB6-91CB-BC1863F17B83@gromit.dlib.vt.edu> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@FreeBSD.org Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 12:46:08 -0000 On Thu, Jul 01, 2010 at 08:26:31AM -0400, Paul Mather wrote: > On Jun 30, 2010, at 5:21 PM, Jeremy Chadwick wrote: > >> I'm assuming that "subclass = ATA" means the controller can't operate > >> in AHCI mode. The BIOS setting is also confusing. It has two > >> options, "Normal" and "Legacy." "Normal" mode says, "The hard drive > >> controller is configured for native mode. This mode provides the > >> highest drive performance and most flexibility." I guess I > >> misinterpreted "native mode" to be AHCI mode. > > > > "Native", "Normal", and "Enhanced" are all terms used to describe the > > controller operating in standard SATA (non-AHCI) fashion. Dell's > > in-BIOS description is nothing but schmooze; it's not the same as AHCI. > > "Legacy" just means the controller appears and operates purely in > > PATA-esque mode, so that you can use SATA drives on systems which don't > > have SATA chipset drivers (ex. MS-DOS). > > Thank you for helping clear that up. I have a Supermicro > X8ST3-F-based server here, and it offers three choices for drive mode: > IDE, RAID, and AHCI. I think it's much clearer, there, what you're > getting. Dell could learn a thing or two from them. :-) It's a matter of demographic -- Dell often caters to home/residential users, while Supermicro caters to engineers, SAs, and other highly technical folk. The latter excludes "gamers" or "tech forum freaks"; these two rarely, if ever, actually program or interface with the devices or chips they're talking about. Speculation on my part, but I'm sure if you Google for "ICH8 ACHI" you'll find hundreds of posts on random forums, and most of these posts will do nothing but confuse. :-) Dell started adding more technically-savvy options to their later models, probably because of pressure from the above two groups, or competitive pressure. Hard to say. > > Furthermore, I can assure you that the Dell OptiPlex 745 Mini-Tower > > offers AHCI capability, and toggling its use via the system BIOS. You > > won't find it mentioned in Dell's "Tech Specs" PDF about this though. I > > realise this is not the system you have, but I'm simply pointing out > > that it's a board manufacturer decision whether or not to provide the > > capability, and that their decision obviously changed over the years. > > Oddly enough, it *is* a Dell OptiPlex 745 in Mini-Tower configuration. > This is the manual I'm led to via the service tag: > http://support.dell.com/support/edocs/systems/op745/en/UG_en/mtindex.htm > > Are you saying there is an option in the BIOS to enable AHCI on these > systems? Sorry for inducing confusion -- I meant the Dell OptiPlex 760. At my workplace we literally have 4 different Dell OptiPlex models in use as workstations. I often mix up the model numbers, case in point. I'm re-CC'ing the mailing list here, because I want to make sure my mistake gets noted in case someone ends up searching the lists ("Hey! I have a 745, what is this guy talking about?!?") -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 14:05:02 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E771106566B for ; Thu, 1 Jul 2010 14:05:02 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id B75888FC21 for ; Thu, 1 Jul 2010 14:05:01 +0000 (UTC) Received: by wwb28 with SMTP id 28so845586wwb.31 for ; Thu, 01 Jul 2010 07:04:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=2JsPZ7AA2Oeivilwbbe/9YJ2i65+NCO4QPbTRd2I+ts=; b=rY2OhgKszaBLctf7EWbCJ0IjqrYqV+Ns3ioPa1QIigHbHuztyaMwvB+CvSvOnwKJ9u LF4R5BO+S9CJ4LRykzeDf9h9zwGz4Hyo6LIwgKNKzSigy4MRQN1elEcTswHdZmPJQNXt /ZjS/NIJW5Cfmn/P/6urysTidUoHKHpYpNb6w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZEGvUfQxc+QXJ1p5ISDU0kmhYCpLamNaQFRl+6YtVYT8yx4j8YtzEm1mAXQim69m35 FzmQHyXdn8OoegkWk199/NOI0fpRY7d+Hg4KHhCN6JnxDrZBLLVG0gV03dHmFLo/KPwc GXXK6MpFnlf9gp2RaJ/+30NSdGeUmACJVuyQY= MIME-Version: 1.0 Received: by 10.213.9.200 with SMTP id m8mr2322157ebm.11.1277993096245; Thu, 01 Jul 2010 07:04:56 -0700 (PDT) Received: by 10.213.15.208 with HTTP; Thu, 1 Jul 2010 07:04:56 -0700 (PDT) In-Reply-To: <4C2B35A2.7010709@vfemail.net> References: <4C2B35A2.7010709@vfemail.net> Date: Thu, 1 Jul 2010 15:04:56 +0100 Message-ID: From: Tom Evans To: Free BSD Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Stable Mailing List Subject: Re: kernel issues with 8 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 14:05:02 -0000 On Wed, Jun 30, 2010 at 1:16 PM, Free BSD wrote: > Dear List Members > Also, even though I have custom keyboard in my kernel configuration, > whenever I boot into single user mode I get US layout (it works fine when in > multi-user mode). Does it work correctly if you run kbdmap and choose the correct layout? If so, set keymap in /etc/rc.conf so it is always configured correctly. Cheers Tom From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 14:47:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 591F51065672 for ; Thu, 1 Jul 2010 14:47:49 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 07EB38FC12 for ; Thu, 1 Jul 2010 14:47:48 +0000 (UTC) Received: by vws6 with SMTP id 6so1629981vws.13 for ; Thu, 01 Jul 2010 07:47:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=+DnMJ5rAfmdCVfCKTPr085TEsbUM5X8Fb7iQ/uQU/O0=; b=fBbs0ahUlCNCkd2f/Q0P1lCf+ffo3+51b62rztmntyRUUrUi/kUYhiLyQyUTF8GPg+ s8zS9jmpqQqLOinYvJpU+LJ9FH7/6JWAYviZPrNXonV19pfMGOedt9cZUWCm+OJraD56 70K2CrHQ97gw/ZdRpnGyYSCydmLfDWVy2QVdg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=l3nfbXe1oCpaDxigaG6MkopNQ29wHxSmXjmCzMjRieJ0vCnp0Eup8vh36rHjWj4WJ5 0eJKVXpYLyRMg7/W8YgFXR3IrCnfKq4y6M2NKLML3Ok3C4QQZucfc+mU40m6H/GbavK/ xER8pRtabfKGPNlKZy/UVPhTge1KjD7HIuUaw= MIME-Version: 1.0 Received: by 10.220.127.15 with SMTP id e15mr5689230vcs.147.1277995664181; Thu, 01 Jul 2010 07:47:44 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 07:47:44 -0700 (PDT) In-Reply-To: <4C280435.4060603@halplant.com> References: <4C280435.4060603@halplant.com> Date: Thu, 1 Jul 2010 22:47:44 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 14:47:49 -0000 Hello Andrew, On Mon, Jun 28, 2010 at 10:08 AM, Andrew J. Caines wrote: > GNUbie, > >> Kindly check the screenshot at http://imagebin.org/102605 for the >> screen output during bootup. I don't know how to recover this system >> and hopefully someone could help me on how to do it. > > Can you boot the old kernel[1]? > > [1] See > http://www.freebsd.org/doc/en/books/handbook/kernelconfig-trouble.html I'm sorry for the late reply as I've been busy for the past 5 days. No, I can't boot from my old kernel. Also, I didn't customized the kernel. How can I proceed from here? Thank you in advance. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 14:49:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DE471065673 for ; Thu, 1 Jul 2010 14:49:51 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1EB108FC1A for ; Thu, 1 Jul 2010 14:49:50 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAMRHLEyDaFvJ/2dsb2JhbACfaXG/CIUlBA X-IronPort-AV: E=Sophos;i="4.53,520,1272859200"; d="scan'208";a="82512080" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 01 Jul 2010 10:49:47 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 29C19FB80CA; Thu, 1 Jul 2010 10:49:49 -0400 (EDT) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PB0bacg6R0WI; Thu, 1 Jul 2010 10:49:48 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 569DEFB80C1; Thu, 1 Jul 2010 10:49:48 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o61F6no20906; Thu, 1 Jul 2010 11:06:49 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Thu, 1 Jul 2010 11:06:49 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: "Rick C. Petty" In-Reply-To: <20100628153527.GB53315@kay.kiwi-computer.com> Message-ID: References: <20100627221607.GA31646@kay.kiwi-computer.com> <20100628031401.GA45282@kay.kiwi-computer.com> <20100628034741.GA45748@kay.kiwi-computer.com> <20100628153527.GB53315@kay.kiwi-computer.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Why is NFSv4 so slow? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 14:49:51 -0000 On Mon, 28 Jun 2010, Rick C. Petty wrote: > On Mon, Jun 28, 2010 at 12:35:14AM -0400, Rick Macklem wrote: >> >> Being stuck in "newnfsreq" means that it is trying to establish a TCP >> connection with the server (again smells like some networking issue). >> >> Disabling delegations is the next step. (They aren't >> required for correct behaviour and are disabled by default because >> they are the "greenest" part of the implementation.) > > After disabling delegations, I was able to build world and kernel on two > different clients, and my port build problems went away as well. > I was able to reproduce a problem when delegations are enabled and the "rdirplus" option was used on a mount. Since I haven't done non-trivial testing with "rdirplus" set, but have done quite a bit with delegations enabled for mounts without "rdirplus", I suspect the problem is related to using "rdirplus" on NFSv4 mounts. So, I'd recommend against using "rdirplus" on NFSv4 mounts until the problem gets resolved. You could try re-enabling delegations and the try mounts without "rdirplus" and see if the problems during builds still show up? Thanks for your help with testing, rick From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 14:53:00 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19D67106564A for ; Thu, 1 Jul 2010 14:53:00 +0000 (UTC) (envelope-from maurovale@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9ADE78FC14 for ; Thu, 1 Jul 2010 14:52:59 +0000 (UTC) Received: by bwz12 with SMTP id 12so1184555bwz.13 for ; Thu, 01 Jul 2010 07:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=DTutfOH27Fa0uN7/azn+9UtXGzGeLZzusYprurLltN0=; b=GlnRV0lCPiMKay+Rp9TkreCUch2nCBS+sTF/4LNHIpOS5YS81T8mOcS+eN6xryh7Pb QtVzzMcrPnsKD4bY7LOW91Lb1EOIDvODBmpA1vlBQF70GrSzdJzlV600+SxT/tRHGxI1 AwjlBEg+B+XN+WhzvbcPdkwPOys+M0nMgJEoI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qL9ifxZXFNaUIbSpjqrxzWFYmRDjbAzcU20vbPlduXtAe7nc8pKr5502pJGV9ZZRD7 wkfvsBNK60CtI0Bg9n3D82r2n2rfgNTX+RgW2uZFkFRNZvd+4Offlgn2mIXog62bp/Ju eUG5G1Qzci1LB8fkIaW2WpJI6kOChnP1W4JtY= MIME-Version: 1.0 Received: by 10.204.136.71 with SMTP id q7mr6767314bkt.111.1277995966362; Thu, 01 Jul 2010 07:52:46 -0700 (PDT) Received: by 10.204.59.15 with HTTP; Thu, 1 Jul 2010 07:52:45 -0700 (PDT) In-Reply-To: References: <4C280435.4060603@halplant.com> Date: Thu, 1 Jul 2010 15:52:45 +0100 Message-ID: From: "M. Vale" To: GNUbie Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 14:53:00 -0000 2010/7/1 GNUbie > Hello Andrew, > > On Mon, Jun 28, 2010 at 10:08 AM, Andrew J. Caines > wrote: > > GNUbie, > > > >> Kindly check the screenshot at http://imagebin.org/102605 for the > >> screen output during bootup. I don't know how to recover this system > >> and hopefully someone could help me on how to do it. > > > > Can you boot the old kernel[1]? > > > > [1] See > > http://www.freebsd.org/doc/en/books/handbook/kernelconfig-trouble.html > > I'm sorry for the late reply as I've been busy for the past 5 days. > > No, I can't boot from my old kernel. Also, I didn't customized the kernel. > > How can I proceed from here? > > Thank you in advance. > > Regards, > > GNUbie > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Hi, do you have VirtualBOX installed ? Also do you add any module to /boot/loader.conf ? like vboxdrv ? Regards MV From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 14:58:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7F40106566B for ; Thu, 1 Jul 2010 14:58:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id BE11A8FC13 for ; Thu, 1 Jul 2010 14:58:49 +0000 (UTC) Received: from omta17.emeryville.ca.mail.comcast.net ([76.96.30.73]) by qmta12.emeryville.ca.mail.comcast.net with comcast id ccsM1e0091afHeLACeyprD; Thu, 01 Jul 2010 14:58:49 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta17.emeryville.ca.mail.comcast.net with comcast id ceyo1e0093S48mS8deyoVT; Thu, 01 Jul 2010 14:58:49 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 1CE2D9B425; Thu, 1 Jul 2010 07:58:48 -0700 (PDT) Date: Thu, 1 Jul 2010 07:58:48 -0700 From: Jeremy Chadwick To: Tom Evans Message-ID: <20100701145848.GA97312@icarus.home.lan> References: <4C2B35A2.7010709@vfemail.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: FreeBSD Stable Mailing List , Free BSD Subject: Re: kernel issues with 8 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 14:58:49 -0000 On Thu, Jul 01, 2010 at 03:04:56PM +0100, Tom Evans wrote: > On Wed, Jun 30, 2010 at 1:16 PM, Free BSD wrote: > > Dear List Members > > Also, even though I have custom keyboard in my kernel configuration, > > whenever I boot into single user mode I get US layout (it works fine when in > > multi-user mode). > > Does it work correctly if you run kbdmap and choose the correct > layout? If so, set keymap in /etc/rc.conf so it is always configured > correctly. AFAIK this only applies to multi-user mode. rc scripts (thus use of rc.conf), to my knowledge, aren't run in single-user. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 15:38:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DFCC106566B for ; Thu, 1 Jul 2010 15:38:19 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 531E58FC0A for ; Thu, 1 Jul 2010 15:38:19 +0000 (UTC) Received: by vws6 with SMTP id 6so1696416vws.13 for ; Thu, 01 Jul 2010 08:38:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=5MNqjeo37J5jHRq+zmX2LNYF/3T+T8SuZAxE47ieeos=; b=v2/1f1lKao3U7PZ0B81CYG4vdUzCzN+7CdJgdDGHyTCs3FUy2B2iUkNqM69/lWoJXB ipbqGA1FlCqKVsM0LznRj5Xn5VhgOZXNSD8cyNcNlnLe/KUJWDUGdNBk6KimethEROgf S9+Svczf5s9XGnZ1oLV1zqQg7R2Do1aMHa2tk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ok3hpbRHssfmsUxODjYDEz7cPODLJcHF8o9nvZOL1vxreSRJCm6ATvVWz/E/WvnNcq CvfKtcibr7/YLeH/Qk4fJbiIiwREZ6o2qSq0wGXmsJBaUuuoPGvEYIIA2nfZpd613pVE cuA+dlMCLrf8FvEAqicSc+0h1CQyxdQv/fLKQ= MIME-Version: 1.0 Received: by 10.220.127.65 with SMTP id f1mr930658vcs.90.1277998693270; Thu, 01 Jul 2010 08:38:13 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 08:38:13 -0700 (PDT) In-Reply-To: References: <4C280435.4060603@halplant.com> Date: Thu, 1 Jul 2010 23:38:13 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: maurovale@gmail.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 15:38:19 -0000 Hello MV, On Thu, Jul 1, 2010 at 10:52 PM, M. Vale wrote: > > Hi, do you have VirtualBOX installed ? > > Also do you add any module to /boot/loader.conf ? like vboxdrv ? No, I don't have. It's a plain/single FreeBSD 8.0-p3 system as my home server. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 15:42:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D98E3106566B for ; Thu, 1 Jul 2010 15:42:37 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6121E8FC1B for ; Thu, 1 Jul 2010 15:42:36 +0000 (UTC) Received: by fxm13 with SMTP id 13so1517945fxm.13 for ; Thu, 01 Jul 2010 08:42:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=/1so5CFIGN80+7w6bucPRUlJxSFgSSGQulpruMHS3kc=; b=CdqGUo2Uy18puZZDFRJJBJTgWEgNaSZeBvBAhFgx1cnGAl45NC13c23ivscxLo86KH JGgRt9L0XxBToBAjm9x5ddPfLfKUTqiXQ7BmGhA3YbF3XpNghzbZKrSsajGsyHxsaoAT FS59jslx6YpTmEmS1Je5LOcVgADS3li4Z0KiA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=RHAG1+uBw6nBiVHw+8MrHtkWldIwmh3m563l+D7IsXRA+iIfw3gaVj/4SJg2pppYue 6F4gaW4YwuTtFLJFY2+Z3jmhset6O4uUMMe3gTs/WSr9oeL/7KJ7AIRnFhdIQ2L8MG5m vI+kzIOcTQ+bFNpS+2uOfLHn4wwFup6a7vc4U= Received: by 10.86.87.12 with SMTP id k12mr4824fgb.31.1277989320412; Thu, 01 Jul 2010 06:02:00 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 7sm53064160far.30.2010.07.01.06.01.58 (version=SSLv3 cipher=RC4-MD5); Thu, 01 Jul 2010 06:01:58 -0700 (PDT) Sender: Alexander Motin Message-ID: <4C2C9199.8050102@FreeBSD.org> Date: Thu, 01 Jul 2010 16:01:13 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Paul Mather References: <4C2B8103.6010409@FreeBSD.org> <1CD8E4CC-53C6-4594-9FF4-CDD57A6B51AC@gromit.dlib.vt.edu> <4C2BB4A6.7040800@FreeBSD.org> <91399FEA-024C-4CA1-BCBD-208B41AA9C59@gromit.dlib.vt.edu> In-Reply-To: <91399FEA-024C-4CA1-BCBD-208B41AA9C59@gromit.dlib.vt.edu> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Problems with ATA_CAM support in RELENG_8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 15:42:38 -0000 Paul Mather wrote: > On Jun 30, 2010, at 5:18 PM, Alexander Motin wrote: >> Paul Mather wrote: >>>> PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. >>> Thank you (and Jeremy Chadwick) for the help and information. The kernel configuration options I used above were taken from a VirtualBox FreeBSD/amd64 install I have that I converted over to ATA_CAM when the code first went into RELENG_8 and it wasn't exactly clear at the time what options were absolutely required. (I'm not even sure that "options ATA_CAM" is needed any more, given "device ahci" implies it.) >> `options ATA_CAM` enables CAM wrapper for legacy drivers, which gave you >> adaX devices instead of adX. It doesn't give major benefits, just >> unifies behavior. > > So, does that mean if you omit "options ATA_CAM" and have "device ahci" you will get adX devices, not adaX devices? In other words, if you have "device ahci" (or "device siis" or "device mvs") will you will always get adaX devices, whether or not you have "options ATA_CAM" in your kernel config file? If you have ahci, siis and mvs drivers in kernel, but no "options ATA_CAM", you will get adaX devices for native SATA controllers, supported by these three drivers and adX for other (legacy) ones. > Does "options ATA_CAM" work with "device ata" or the modular ATA subsystem? Both. It is an option of "device atacore", which is part of "device ata" > Is that the intended use of "options ATA_CAM": to provide adaX devices and a CAM interface for accessing ATA devices? Yes. It disables ATA peripheral drivers and bus management code, allowing CAM ones to be used on top of the ATA controller drivers. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 15:59:50 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24BD3106566C for ; Thu, 1 Jul 2010 15:59:50 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id CCF8E8FC1A for ; Thu, 1 Jul 2010 15:59:49 +0000 (UTC) Received: by vws6 with SMTP id 6so1724965vws.13 for ; Thu, 01 Jul 2010 08:59:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Uyf9tlOlRsj7K9JDqTi7IjSvqlr9OripdNwFDjovhJo=; b=ONwpRtVtTF0cmXvvgIKXVxrUNfdfwcuSJ1B4ZWIGIIo1wsnUstGsIYtABr3nAsw8HJ hSAynGFF7FdmHiztsVr2AtPdEpVsxZ6O9FfdlJ4gpBZZVhzHmigyrDyV7dTVJSjqmf2O Sq2YFi/D9z9/XepCisRRDbscCFQ3Hdj7dYCqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jYivpfEQHu3jcAbOpwqtL0FlKNgN8/CXhrfsfjEKRdKZRyx7es9SiUoU1JHZEgvvIX GjFHP8nEB4xFi8HZYjHxz59E8O2eFHsZndTbwJL1RRFt/cphoOiL3fXOhF6HYrbR9PlN upf56ALHUPXy+JuKzJ37iuG5VGk80vEQ7lEHQ= MIME-Version: 1.0 Received: by 10.220.127.79 with SMTP id f15mr5780900vcs.131.1277999983203; Thu, 01 Jul 2010 08:59:43 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 08:59:43 -0700 (PDT) In-Reply-To: References: <4C280435.4060603@halplant.com> Date: Thu, 1 Jul 2010 23:59:43 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: maurovale@gmail.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 15:59:50 -0000 Hello MV, On Thu, Jul 1, 2010 at 11:47 PM, M. Vale wrote: > > Hum strange I've seen this occur on 2 types of situations: > > 1 - virtualbox or other module loaded at boot time > 2 - Hardware problem > > To fix it you have a list of small options. > > The first one is by booting with the FreeBSD CD and choosing rescue/upgrade > system > > Other option is by removing Memory DIMM's to ensure that the problem is not > caused by a fault RAM module. I am currently running memtest86 here on my livecd. If there is no error, then this could be something else. Still strange for me on the stdout before my system reboots that says: "Cannot dump. Device not defined or unavailable." Does it mean that when loading the kernel, it cannot dump it to the / or some other designated place? Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:03:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C0671065672 for ; Thu, 1 Jul 2010 16:03:03 +0000 (UTC) (envelope-from michal@ionic.co.uk) Received: from mail1.sharescope.co.uk (mail1.ionic.co.uk [85.159.80.19]) by mx1.freebsd.org (Postfix) with ESMTP id D9E068FC12 for ; Thu, 1 Jul 2010 16:03:02 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail1.sharescope.co.uk (Postfix) with ESMTP id 3837FFC0B7 for ; Thu, 1 Jul 2010 16:03:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at sharescope.co.uk Received: from mail1.sharescope.co.uk ([127.0.0.1]) by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnxUek6BszBN for ; Thu, 1 Jul 2010 17:02:58 +0100 (BST) Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2]) by mail1.sharescope.co.uk (Postfix) with ESMTPS id 3D7FBFC0AA for ; Thu, 1 Jul 2010 17:02:58 +0100 (BST) Message-ID: <4C2CBC30.4060504@ionic.co.uk> Date: Thu, 01 Jul 2010 17:02:56 +0100 From: Michal User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4C280435.4060603@halplant.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:03:03 -0000 > I am currently running memtest86 here on my livecd. If there is no > error, then this could be something else. > I've seen memtest pass but it still be a RAM problem. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:06:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD99B106566C for ; Thu, 1 Jul 2010 16:06:07 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6C25F8FC21 for ; Thu, 1 Jul 2010 16:06:07 +0000 (UTC) Received: by vws6 with SMTP id 6so1733727vws.13 for ; Thu, 01 Jul 2010 09:06:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=KeVe7/UyFmKCVwqf65j5bnITRo+iGevUSnO6krmLq3Y=; b=F+ifE+Jd67A2I82jFOR3Ri6kXn4ngkr/cRk4VSJ1f3LgqHa14/Uok5uSkLf273OTUi i28mY+DOgGww1Vyl4hwtkEVuoy5jFqU7/k3eQw7uD9kkcL4MwOsLwBstM7d4jTlbZwbh mY2o+gjpos+gXe1SNgsiRyAnh3uEAe6fjwWAU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=MAIey5H6DOlYjT5COHm47owdFgnty4LZkIlEiSP4BXT1WmBvJ/UNn/DQutGiZRWEhV IGewlV94q8LcoiTZsanJ5Ww0K9yA8RpIMDG7sh4pya6T38j7RRwrd7SEZkIVWYxKG+cF rR6xEcVnG4h45ahJ6wolBacPoCxa0XSKv8cxo= MIME-Version: 1.0 Received: by 10.220.75.200 with SMTP id z8mr4952251vcj.57.1278000366523; Thu, 01 Jul 2010 09:06:06 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:06:06 -0700 (PDT) In-Reply-To: <4C2CBC30.4060504@ionic.co.uk> References: <4C280435.4060603@halplant.com> <4C2CBC30.4060504@ionic.co.uk> Date: Fri, 2 Jul 2010 00:06:06 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: michal@ionic.co.uk Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:06:07 -0000 Hello Michal, On Fri, Jul 2, 2010 at 12:02 AM, Michal wrote: > >> I am currently running memtest86 here on my livecd. If there is no >> error, then this could be something else. > > I've seen memtest pass but it still be a RAM problem. So, what can you recommend in order to confirm if the RAM is faulty or not? Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:06:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 632FC1065675 for ; Thu, 1 Jul 2010 16:06:24 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by mx1.freebsd.org (Postfix) with ESMTP id 456748FC34 for ; Thu, 1 Jul 2010 16:06:23 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta02.emeryville.ca.mail.comcast.net with comcast id cduK1e0031HpZEsA2g6Pfz; Thu, 01 Jul 2010 16:06:23 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta14.emeryville.ca.mail.comcast.net with comcast id cg6N1e00T3S48mS8ag6Pyd; Thu, 01 Jul 2010 16:06:23 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id D91B29B425; Thu, 1 Jul 2010 09:06:22 -0700 (PDT) Date: Thu, 1 Jul 2010 09:06:22 -0700 From: Jeremy Chadwick To: GNUbie Message-ID: <20100701160622.GA98823@icarus.home.lan> References: <4C280435.4060603@halplant.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: maurovale@gmail.com, freebsd-stable@freebsd.org Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:06:24 -0000 On Thu, Jul 01, 2010 at 11:59:43PM +0800, GNUbie wrote: > Hello MV, > > On Thu, Jul 1, 2010 at 11:47 PM, M. Vale wrote: > > > > Hum strange I've seen this occur on 2 types of situations: > > > > 1 - virtualbox or other module loaded at boot time > > 2 - Hardware problem > > > > To fix it you have a list of small options. > > > > The first one is by booting with the FreeBSD CD and choosing rescue/upgrade > > system > > > > Other option is by removing Memory DIMM's to ensure that the problem is not > > caused by a fault RAM module. > > I am currently running memtest86 here on my livecd. If there is no > error, then this could be something else. > > Still strange for me on the stdout before my system reboots that says: > "Cannot dump. Device not defined or unavailable." Does it mean that > when loading the kernel, it cannot dump it to the / or some other > designated place? Kernel crash dumps are not enabled by default. You need to define the following in /etc/rc.conf before that will happen: dumpdev="auto" Be aware that kernel crash dumps don't always work reliably -- or rather, the savecore(8) portion (once the system is back up, writing the crash details to files in /var/crash on the filesystem). Of course, I'm going off of history (circa 2007), but there wasn't ever any indication that the problem was fixed: http://www.freebsd.org/cgi/query-pr.cgi?pr=118255 If you can't get the OS installed (e.g. this is happening when booting the FreeBSD installation CD), you're kinda out of luck, unless others know of a way around it. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 16:14:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8422D1065675 for ; Thu, 1 Jul 2010 16:14:31 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 34E528FC1F for ; Thu, 1 Jul 2010 16:14:30 +0000 (UTC) Received: by vws6 with SMTP id 6so1745262vws.13 for ; Thu, 01 Jul 2010 09:14:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=pbAS8G80lkmOA+e69jEjDqeXR34iFAmpRQ5i6i8vhG8=; b=LjSQ2eNi56zsZsR/xijHZpRifvHeark9W8Ksqd//3gBEEFP5G+Qjne/f4xV0I3SG41 Ik2zJ6Z2O2C63vO4x52WPkX0m/TMlQcTtUFmx8HYRBgFwUuwp8Csw986VR+6DRLtZHUM AKrfPh8SgU9A3mYIfoOvpmQK1Nwb94fY7ymTE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SX675/b18VEVKNoO7DgfzrxMkUbKdBWgrh6DTLtTNFekdgzOtB9h1zLROBRS2d4tIp Bka3922wmel5Gl9IOdGGqKIj9NUc5VFguqNQXRc/n8L8P6Sekd3QwXvhvjp5r0KBAVmW BJL8/ssQouIZYDhHmYmaUniLYxIhZ+6LtGrLg= MIME-Version: 1.0 Received: by 10.220.121.226 with SMTP id i34mr5875982vcr.10.1278000868161; Thu, 01 Jul 2010 09:14:28 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:14:28 -0700 (PDT) In-Reply-To: <20100701160622.GA98823@icarus.home.lan> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> Date: Fri, 2 Jul 2010 00:14:28 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: maurovale@gmail.com, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:14:31 -0000 Hello Jeremy, On Fri, Jul 2, 2010 at 12:06 AM, Jeremy Chadwick wrote: > > Kernel crash dumps are not enabled by default. =A0You need to define the > following in /etc/rc.conf before that will happen: > > dumpdev=3D"auto" Ok. So, the line "Cannot dump. Device not defined or unavailable." is already going to be an output of the kernel crash. Meaning, during bootup, somehow the kernel crash and since crash dumps was not defined, that is why I was getting that message I just mentioned. Moving forward, what are your recommendations in order for me to be able to boot from my system? Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:15:54 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AF641065673 for ; Thu, 1 Jul 2010 16:15:54 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id E2DEA8FC3C for ; Thu, 1 Jul 2010 16:15:53 +0000 (UTC) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta04.westchester.pa.mail.comcast.net with comcast id ccSM1e00617dt5G54gFuGy; Thu, 01 Jul 2010 16:15:54 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta13.westchester.pa.mail.comcast.net with comcast id cgFs1e00U3S48mS3ZgFtoj; Thu, 01 Jul 2010 16:15:54 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 96D939B425; Thu, 1 Jul 2010 09:15:51 -0700 (PDT) Date: Thu, 1 Jul 2010 09:15:51 -0700 From: Jeremy Chadwick To: GNUbie Message-ID: <20100701161551.GA99011@icarus.home.lan> References: <4C280435.4060603@halplant.com> <4C2CBC30.4060504@ionic.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: michal@ionic.co.uk, freebsd-stable@freebsd.org Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:15:54 -0000 On Fri, Jul 02, 2010 at 12:06:06AM +0800, GNUbie wrote: > Hello Michal, > > On Fri, Jul 2, 2010 at 12:02 AM, Michal wrote: > > > >> I am currently running memtest86 here on my livecd. If there is no > >> error, then this could be something else. > > > > I've seen memtest pass but it still be a RAM problem. > > So, what can you recommend in order to confirm if the RAM is faulty or not? Simple: replace the RAM, file for an RMA, etc.. If there's no warranty or the warranty has expired and you need brand recommendations for a new purchase: Crucial is excellent, avoid Corsair at all costs. There is no software-based RAM tester available for PC architecture that can stress-test RAM 100% reliably. Proper memory analysers are almost always hardware and do a multitude of tests (hard and soft failures, ECC analysis, voltage regulator stress tests, and thermal stress tests). An old job of mine required me to use one of these on a daily basis, testing for bad RAM from Sun IPC/IPX and UltraSparc boxes. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 16:16:38 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7ADB106566B for ; Thu, 1 Jul 2010 16:16:38 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 546008FC0C for ; Thu, 1 Jul 2010 16:16:38 +0000 (UTC) Received: by vws6 with SMTP id 6so1748019vws.13 for ; Thu, 01 Jul 2010 09:16:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=BAvRp2KFsunOWacq3a+mTeIvpyTMiguIO//dfxfKvnE=; b=cNSS3Czyktb7ufEUW3thHDNlOfwF70j1php6JW0rHbq9irPX3wgf/kv2k1XJcFBIxn 1KifMOFdA4NZf1o6Rp/jR3+yuRu7GKmiDZULbqCNgbQKlO9lbv6BsCrC/tiR+zmPrs4x v06dos7zGKAc8NXAIPPRPyFlA6aV0DV9aRAg0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tMA06UmAwgmbAkQcflX5sb9OqBTqXEOTMExPEG5Uoo2euJupOEcLQTL5rlRF5Hrz5j wNdhEumJlLnugKZg0jTz2Ls2oxo+0SFdOA7HKCk5kNWjm6oLWTtofgtgd1t1hY6LoWM3 U0kw031nZ6gD7luuMjk2gtBKiposcNun6LwHc= MIME-Version: 1.0 Received: by 10.220.124.211 with SMTP id v19mr3734737vcr.153.1278000990323; Thu, 01 Jul 2010 09:16:30 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:16:30 -0700 (PDT) In-Reply-To: <4C2CBE96.20500@ionic.co.uk> References: <4C280435.4060603@halplant.com> <4C2CBC30.4060504@ionic.co.uk> <4C2CBE96.20500@ionic.co.uk> Date: Fri, 2 Jul 2010 00:16:30 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: michal@ionic.co.uk Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:16:38 -0000 Hello Michal, On Fri, Jul 2, 2010 at 12:13 AM, Michal wrote: > >> So, what can you recommend in order to confirm if the RAM is faulty or >> not? > > Some different sticks That I need to buy another 1GB stick tomorrow. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:20:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4034106567C for ; Thu, 1 Jul 2010 16:20:52 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 73E5C8FC0A for ; Thu, 1 Jul 2010 16:20:52 +0000 (UTC) Received: by vws6 with SMTP id 6so1754065vws.13 for ; Thu, 01 Jul 2010 09:20:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=B1u0pwhhZ1HMPvJ/MYCMsRjaRgHDQ9v0pugcw7qbDUY=; b=J1frr489gbejRrLMpDdocUxzmJAKonO3mf+WWAw4P6+CSuYXDptIHBfQBbsWqMze1W 7jqC6K3Nuqp1OJOZSr01ARhLk4Z34YVALEdigGbBkn968WT952E+/cfMC6jyz/pBfGdl uOwn6hN2K5B+mSeilCQnORYExdh7xymJFH1mk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QclflM20sCNHwKp36NRY2mHTOI2Hw14uyz+BR/mDhB5rgHeIkJ99sjtTGRcB+iAGvj qxRPzr9aR1g/1L8zalUHd2YNnZNB3LI655Ocf5dGZnGml9kYic+XHpD0qPcTZoBiO+nl ul/gHcUxjf4U8xfcS5MMBkC4D1lzbGlz28SJI= MIME-Version: 1.0 Received: by 10.220.98.140 with SMTP id q12mr5414784vcn.268.1278001248427; Thu, 01 Jul 2010 09:20:48 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:20:48 -0700 (PDT) In-Reply-To: <20100701161551.GA99011@icarus.home.lan> References: <4C280435.4060603@halplant.com> <4C2CBC30.4060504@ionic.co.uk> <20100701161551.GA99011@icarus.home.lan> Date: Fri, 2 Jul 2010 00:20:48 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: michal@ionic.co.uk, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:20:52 -0000 Hello Jeremy, On Fri, Jul 2, 2010 at 12:15 AM, Jeremy Chadwick wrote: > > Simple: replace the RAM, file for an RMA, etc.. =A0If there's no warranty > or the warranty has expired and you need brand recommendations for a new > purchase: Crucial is excellent, avoid Corsair at all costs. I'm using Kingston and it's still less than a year since I bought this RAM. I have to ask the shop where I bought this RAM and hopefully they will replace it. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:22:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F119C106564A for ; Thu, 1 Jul 2010 16:22:48 +0000 (UTC) (envelope-from michal@ionic.co.uk) Received: from mail1.sharescope.co.uk (mail1.ionic.co.uk [85.159.80.19]) by mx1.freebsd.org (Postfix) with ESMTP id 61E718FC1A for ; Thu, 1 Jul 2010 16:22:48 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail1.sharescope.co.uk (Postfix) with ESMTP id E3E69FC0B7 for ; Thu, 1 Jul 2010 16:22:48 +0000 (UTC) X-Virus-Scanned: amavisd-new at sharescope.co.uk Received: from mail1.sharescope.co.uk ([127.0.0.1]) by localhost (mail1.sharescope.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yo4OtJdx3pcK for ; Thu, 1 Jul 2010 17:22:45 +0100 (BST) Received: from [192.168.2.37] (office.ionic.co.uk [85.159.85.2]) by mail1.sharescope.co.uk (Postfix) with ESMTPS id 037D9FC0AA for ; Thu, 1 Jul 2010 17:22:45 +0100 (BST) Message-ID: <4C2CC0D3.8060908@ionic.co.uk> Date: Thu, 01 Jul 2010 17:22:43 +0100 From: Michal User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4C280435.4060603@halplant.com> <4C2CBC30.4060504@ionic.co.uk> <20100701161551.GA99011@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:22:49 -0000 On 01/07/2010 17:20, GNUbie wrote: > Hello Jeremy, > > On Fri, Jul 2, 2010 at 12:15 AM, Jeremy Chadwick > wrote: >> >> Simple: replace the RAM, file for an RMA, etc.. If there's no warranty >> or the warranty has expired and you need brand recommendations for a new >> purchase: Crucial is excellent, avoid Corsair at all costs. > > I'm using Kingston and it's still less than a year since I bought this > RAM. I have to ask the shop where I bought this RAM and hopefully they > will replace it. > > Regards, > > GNUbie You can file an RMA with kingston if you have the serial number (I think) it should be on the sticks From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:27:45 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BB4F1065670 for ; Thu, 1 Jul 2010 16:27:45 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id EF5858FC1A for ; Thu, 1 Jul 2010 16:27:44 +0000 (UTC) Received: by vws6 with SMTP id 6so1763510vws.13 for ; Thu, 01 Jul 2010 09:27:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=caxhPN4h+ZqxP5QiZALYQEmprZP3Idglfg1/z5uZfYU=; b=VhpGk7SSnAovHbyr28ShuDtZlK4pd2pr8YjrJev8/X82kTWWLvOM04igMNGN37abx0 Pxf8gtEqO8vynqqFBRUj8Dh/rpnQyyazm55+I0BBT1wdCUXWaoNrUsuxHP+Kh/sqrUk+ qfgI5g/QPEzNGL6RHCMq8+7kE4Qr+/fqQDJos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=obJt708ZKwgWvvInZP6tt4CJ0vjMP1I7U0PIcG/1mBAWGtsSFOoyymlVAAsqlL4S8w JOoOrKu1Y6fCjNvQFG1bRkgif4nHjeUXGkZLzCjG9O9n7D3SVGLAEeACkOu3auxiwiFn FWUPMnxDom5AYOmUIqEOeuUcEHCtzjTwGX3aY= MIME-Version: 1.0 Received: by 10.220.89.212 with SMTP id f20mr2360271vcm.243.1278001658544; Thu, 01 Jul 2010 09:27:38 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:27:38 -0700 (PDT) In-Reply-To: <4C2CC0B2.4030100@exonetric.com> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <4C2CC0B2.4030100@exonetric.com> Date: Fri, 2 Jul 2010 00:27:38 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: maurovale@gmail.com, freebsd@jdc.parodius.com, mark@exonetric.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:27:45 -0000 Hello Mark, On Fri, Jul 2, 2010 at 12:22 AM, Mark Blackman wrote: > GNUbie wrote: > >> Moving forward, what are your recommendations in order for me to be >> able to boot from my system? > > Boot from a "live" CD of some recent/reasonable vintage, mount the > filesystems and try to reinstall the old kernel installation? probably > as simple as a > > 1. "move installed kernel directory to another name" > 2. "move kernel.old directory to kernel" > > Bear in mind, I've not done this kind of fiddling for a while, so > I might have the precise details wrong. I have here the FreeBSD 8.0 installer. Choosing "upgrade" is different in what are you trying to recommend, right? If that is the case, I will chroot to the HDD's / once I'm able to mount it? Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:29:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F16591065670 for ; Thu, 1 Jul 2010 16:29:22 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9EA728FC16 for ; Thu, 1 Jul 2010 16:29:22 +0000 (UTC) Received: by vws6 with SMTP id 6so1765697vws.13 for ; Thu, 01 Jul 2010 09:29:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=74k7be/TTFeHecYtLSLlUlN7/CL0he/Bs4dHRpwDTPI=; b=sofDx/e0YGImEOcIZ1Y9h5hXd/0HKMsT0qPI00HyUSazRDU1HK8ReCUnjPclAvng7l 8Q1Pg9fpuRkZ49jdZ7emkEgtPtTRQ9pVL0jlYCoHP7fVsB6vZ8G1uRh+5lg1lL6dpjlS u0mXEEJbanmt720zK23rJNuS86AxU4CRjXS3w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=h5kpDLb3OB52I0fsvxz1qgpSLv87YF/ZeS+Oy3H6vp7sFIDYnwTPYLnzlHoLTsLzsY 41D6alwLRBV9jHlOo9jPaDAdfTwKCut/Yxcch/g78LQzn4sqXUhyzoXheZmWPDnYVIJp cKJEVYaepPWrj0/Xar0toYSol+tLx1LG6TY+Q= MIME-Version: 1.0 Received: by 10.220.159.14 with SMTP id h14mr5279049vcx.255.1278001757300; Thu, 01 Jul 2010 09:29:17 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:29:17 -0700 (PDT) In-Reply-To: <4C2CC0D3.8060908@ionic.co.uk> References: <4C280435.4060603@halplant.com> <4C2CBC30.4060504@ionic.co.uk> <20100701161551.GA99011@icarus.home.lan> <4C2CC0D3.8060908@ionic.co.uk> Date: Fri, 2 Jul 2010 00:29:17 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: michal@ionic.co.uk Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:29:23 -0000 Hello Michal, On Fri, Jul 2, 2010 at 12:22 AM, Michal wrote: > > You can file an RMA with kingston if you have the serial number (I think) it > should be on the sticks Ok then. I will try to contact a local Kingston office in my place. Thank you. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:36:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6BB4106564A for ; Thu, 1 Jul 2010 16:36:22 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay0.exonetric.net (relay0.exonetric.net [82.138.248.161]) by mx1.freebsd.org (Postfix) with ESMTP id 969A88FC1D for ; Thu, 1 Jul 2010 16:36:22 +0000 (UTC) Received: from markimac.fairfx.local (unknown [62.244.179.66]) by relay0.exonetric.net (Postfix) with ESMTP id B3BC057269; Thu, 1 Jul 2010 17:36:21 +0100 (BST) Message-ID: <4C2CC405.5000300@exonetric.com> Date: Thu, 01 Jul 2010 17:36:21 +0100 From: Mark Blackman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100504 SeaMonkey/2.0.5 MIME-Version: 1.0 To: GNUbie References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <4C2CC0B2.4030100@exonetric.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: maurovale@gmail.com, freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:36:22 -0000 GNUbie wrote: > Hello Mark, > > On Fri, Jul 2, 2010 at 12:22 AM, Mark Blackman wrote: >> GNUbie wrote: >> >>> Moving forward, what are your recommendations in order for me to be >>> able to boot from my system? >> >> Boot from a "live" CD of some recent/reasonable vintage, mount the >> filesystems and try to reinstall the old kernel installation? probably >> as simple as a >> >> 1. "move installed kernel directory to another name" >> 2. "move kernel.old directory to kernel" >> >> Bear in mind, I've not done this kind of fiddling for a while, so >> I might have the precise details wrong. > > I have here the FreeBSD 8.0 installer. Choosing "upgrade" is different > in what are you trying to recommend, right? If that is the case, I > will chroot to the HDD's / once I'm able to mount it? sorry, i'd have to dig out the 8.0 installer to give you precise instructions. The general idea is to boot from the kernel on the CD, then at the main menu there is a "fixit" option which should get you to repair mode. From there you should get a shell which uses binaries on the CD to permit you mount the existing filesystems and use the old kernel installation at least. I didn't pay close attention to the beginning of the thread, but I believe you have had some kernel working on this machine at some point. - Mark From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:47:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12244106566C for ; Thu, 1 Jul 2010 16:47:24 +0000 (UTC) (envelope-from mark@exonetric.com) Received: from relay0.exonetric.net (relay0.exonetric.net [82.138.248.161]) by mx1.freebsd.org (Postfix) with ESMTP id C7D528FC1C for ; Thu, 1 Jul 2010 16:47:23 +0000 (UTC) Received: from markimac.fairfx.local (unknown [62.244.179.66]) by relay0.exonetric.net (Postfix) with ESMTP id 7164D57008; Thu, 1 Jul 2010 17:22:11 +0100 (BST) Message-ID: <4C2CC0B2.4030100@exonetric.com> Date: Thu, 01 Jul 2010 17:22:10 +0100 From: Mark Blackman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100504 SeaMonkey/2.0.5 MIME-Version: 1.0 To: GNUbie References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: maurovale@gmail.com, freebsd-stable@freebsd.org, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:47:24 -0000 GNUbie wrote: > Moving forward, what are your recommendations in order for me to be > able to boot from my system? Boot from a "live" CD of some recent/reasonable vintage, mount the filesystems and try to reinstall the old kernel installation? probably as simple as a 1. "move installed kernel directory to another name" 2. "move kernel.old directory to kernel" Bear in mind, I've not done this kind of fiddling for a while, so I might have the precise details wrong. - Mark From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:51:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2830106566B for ; Thu, 1 Jul 2010 16:51:36 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 806A98FC1A for ; Thu, 1 Jul 2010 16:51:36 +0000 (UTC) Received: by vws6 with SMTP id 6so1795662vws.13 for ; Thu, 01 Jul 2010 09:51:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fciUtlCsJHxTuFv6tVU8xfhOlJ8ki0WuZNXj78M8ssA=; b=EXeXSP0kz3PmmKTjoWgyM/2j7WyXIcweCl7jfJKGYegwYegZxFHUTWDoI+4xI7+16z Qsg/AsrDQFcaeBhw2u2vHZhklq+a4wSaHz7/buQEUn40o5kejqAlbx95vMk4sJTgsGg5 HMSupk/PM6+ohyVmY6L68Y4ZrV0GmadQENhDU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=uOjAlETJUpibqrNyGJPCZg9GiPAtjboRjqJV+ezpoRVcn7TJL1uf/aZgbtz5AnpKoz sFtwDiY4MBqLtF2xR5nwEmNcJ20/AQmpDvXdVOWohve18YzRHOwAiaRk+tH5ZkEn9Fdz swBl80siD8ZJvO6otJHa32OOVAvpzvTvsGRAU= MIME-Version: 1.0 Received: by 10.220.127.79 with SMTP id f15mr5820034vcs.131.1278003093597; Thu, 01 Jul 2010 09:51:33 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:51:33 -0700 (PDT) In-Reply-To: <4C2CC405.5000300@exonetric.com> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <4C2CC0B2.4030100@exonetric.com> <4C2CC405.5000300@exonetric.com> Date: Fri, 2 Jul 2010 00:51:33 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: maurovale@gmail.com, freebsd@jdc.parodius.com, mark@exonetric.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:51:36 -0000 Hello Mark, On Fri, Jul 2, 2010 at 12:36 AM, Mark Blackman wrote: > > sorry, i'd have to dig out the 8.0 installer to give you precise > instructions. > > The general idea is to boot from the kernel on the CD, then at > the main menu there is a "fixit" option which should get you to > repair mode. From there you should get a shell which uses binaries > on the CD to permit you mount the existing filesystems and use > the old kernel installation at least. > > I didn't pay close attention to the beginning of the thread, but > I believe you have had =A0some kernel working on this machine at > some point. Ok then. I will try it here. I will update you for whatever will be the res= ult. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 16:59:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA020106564A for ; Thu, 1 Jul 2010 16:59:51 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0D28FC13 for ; Thu, 1 Jul 2010 16:59:50 +0000 (UTC) Received: by vws6 with SMTP id 6so1806965vws.13 for ; Thu, 01 Jul 2010 09:59:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=PuIar/X4ysp4ZwGkbNq8xOBYBI6BonwiWUz+P9b1ZVo=; b=Np0ITZ8NAQHWqo6hMdK9LBZ5Ue7f0fM+/r29xt0mhpV7Ek0zdfdsqd4hz9ninQrbYk nEvE4qYNUUMkvIZiNtc33yAIgAk0aQck2Kf1khoBHB55YoNzmNXNufAUgsYmVBrvy3ml e6G6DyI0h561KT+D4k56zy839PzuAuI99Ts1o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Sl7GmjUs5utsjuZqjvhi0s/S2sGsEoTh51KQ7WIGxZzJxuhCW6wltfLy5Cx0L6xf1T T7BrzhN+n/6p94mofhT440V2P+68O3ZkCah5gu4GB0DndA32fRLfaVA6G8iUZxJYwVFT tHCnDgH2tZaPR4EcyiMUV1oha+xumqwZ8ML2o= MIME-Version: 1.0 Received: by 10.220.98.140 with SMTP id q12mr5444042vcn.268.1278003587348; Thu, 01 Jul 2010 09:59:47 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 09:59:47 -0700 (PDT) In-Reply-To: <2E1EC727E18E4B4EB7EE084A9BC99A57@sunrise> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <2E1EC727E18E4B4EB7EE084A9BC99A57@sunrise> Date: Fri, 2 Jul 2010 00:59:47 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: ssanbeg@gmail.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 16:59:51 -0000 Hello Scott, On Fri, Jul 2, 2010 at 12:52 AM, Scott Sanbeg wrote: > I had the same thing happening while running in VirtualBox. Tested on a > bare-metal machine afterward the results were the same - following the > how-to's on running a ZFS root, or a ZFS swap device, or a gmirror root that > included swap (w/o ZFS at all) produced what your screenshot shows. My > platform is amd64. I also have a ZFS on which I mount it on my /data slice. The rest are the default UFS. My machine is based on an Intel D945GCLF2 with 1GB RAM and 1TB SATA HDD. Is your problem solved already? Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 17:05:06 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A96571065672 for ; Thu, 1 Jul 2010 17:05:06 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0998FC19 for ; Thu, 1 Jul 2010 17:05:05 +0000 (UTC) Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta05.westchester.pa.mail.comcast.net with comcast id carw1e0031HzFnQ55h565T; Thu, 01 Jul 2010 17:05:06 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta14.westchester.pa.mail.comcast.net with comcast id ch551e0053S48mS3ah55tg; Thu, 01 Jul 2010 17:05:06 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E618D9B425; Thu, 1 Jul 2010 10:05:03 -0700 (PDT) Date: Thu, 1 Jul 2010 10:05:03 -0700 From: Jeremy Chadwick To: GNUbie Message-ID: <20100701170503.GA99226@icarus.home.lan> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: maurovale@gmail.com, freebsd-stable@freebsd.org Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 17:05:06 -0000 On Fri, Jul 02, 2010 at 12:14:28AM +0800, GNUbie wrote: > Hello Jeremy, > > On Fri, Jul 2, 2010 at 12:06 AM, Jeremy Chadwick > wrote: > > > > Kernel crash dumps are not enabled by default.  You need to define the > > following in /etc/rc.conf before that will happen: > > > > dumpdev="auto" > > Ok. So, the line "Cannot dump. Device not defined or unavailable." is > already going to be an output of the kernel crash. Meaning, during > bootup, somehow the kernel crash and since crash dumps was not > defined, that is why I was getting that message I just mentioned. > > Moving forward, what are your recommendations in order for me to be > able to boot from my system? 1) Your screen shot doesn't indicate the root filesystem is being mounted, which more or less inhibits your ability to get a crash dump. I don't think it's worth putting forth effort to try and get one. Interesting though *is* the fact that the kernel crashes at the point where the root fileystem normally gets mounted. Example system: SMP: AP CPU #1 Launched! Root mount waiting for: usbus7 usbus3 Root mount waiting for: usbus7 usbus3 uhub3: 6 ports with 6 removable, self powered uhub7: 6 ports with 6 removable, self powered Trying to mount root from ufs:/dev/ada0s1a I'm wondering if the "Swap zone entries" message is giving us some hints as to where the problem lies (filesystem corruption? Not sure!). 2) I'm not entirely sure your system has bad RAM. It's possible, but honestly it wouldn't be my first guess. Bad hardware is always a possibility though, so it's worth considering. 3) Have you tried downloading a 8.1-RC1 LiveFS CD and seeing if it boots, works, etc? You might be able to start to recovery your system from there. For those who haven't looked at the screen shot, the kernel outputs the following immediately before/during the crash (i386 system): uhub4: on usbus4 SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! Swap zone entries reduced from 121574 to 4742. Fatal double fault: eip = 0xc0ace110 esp = 0xffe8b000 ebp = 0xffe8b840 cpuid = 3; apic id = 03 panic: double fault cpuid = 3 Uptime: 2s Cannot dump, blah blah, automatic reboot in 15 seconds... Not sure about EBP (the screen shot is washed out and I haven't tried using Photoshop to clean it up). -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 17:10:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3107E106564A for ; Thu, 1 Jul 2010 17:10:28 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id CB45B8FC20 for ; Thu, 1 Jul 2010 17:10:26 +0000 (UTC) Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta13.westchester.pa.mail.comcast.net with comcast id cceC1e0040mv7h05DhATNL; Thu, 01 Jul 2010 17:10:27 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta11.westchester.pa.mail.comcast.net with comcast id chAR1e0073S48mS3XhASZN; Thu, 01 Jul 2010 17:10:27 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 26C4D9B425; Thu, 1 Jul 2010 10:10:24 -0700 (PDT) Date: Thu, 1 Jul 2010 10:10:24 -0700 From: Jeremy Chadwick To: GNUbie Message-ID: <20100701171024.GA562@icarus.home.lan> References: <20100701160622.GA98823@icarus.home.lan> <4C2CC0B2.4030100@exonetric.com> <4C2CC405.5000300@exonetric.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: maurovale@gmail.com, freebsd-stable@freebsd.org, mark@exonetric.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 17:10:28 -0000 On Fri, Jul 02, 2010 at 12:51:33AM +0800, GNUbie wrote: > Hello Mark, > > On Fri, Jul 2, 2010 at 12:36 AM, Mark Blackman wrote: > > > > sorry, i'd have to dig out the 8.0 installer to give you precise > > instructions. > > > > The general idea is to boot from the kernel on the CD, then at > > the main menu there is a "fixit" option which should get you to > > repair mode. From there you should get a shell which uses binaries > > on the CD to permit you mount the existing filesystems and use > > the old kernel installation at least. > > > > I didn't pay close attention to the beginning of the thread, but > > I believe you have had  some kernel working on this machine at > > some point. > > Ok then. I will try it here. I will update you for whatever will be the result. Mark's referring to the following choice in the FreeBSD installer (otherwise known as sysinstall(8)): Fixit Repair mode with CDROM/DVD/floppy or start shell Be aware that you'll need the "livefs" CD/DVD to use this. The "Shell" choice won't give you all the necessary utilities you might need. Otherwise, you'll need to use the FreeBSD "memstick" image (written to a USB pen/flash drive (not hard disk). Said image is bootable. You can use the memstick image for both a FreeBSD install *and* fixit; quite nice! -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 17:20:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBC551065679 for ; Thu, 1 Jul 2010 17:20:51 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 67A968FC17 for ; Thu, 1 Jul 2010 17:20:51 +0000 (UTC) Received: by vws6 with SMTP id 6so1834420vws.13 for ; Thu, 01 Jul 2010 10:20:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DCDf0IDcSg3ajZ2vO8b3cRn+28HTHJBeGsnTjFXtYUk=; b=FLciwtXKemkymkP0ZS9B9EyMEEcYg5D2H+SasaBMYtog+TlKbpqTcCYOzirV5OnU1F q6R7c388sYPpDAw7yxapaLtHDaBV9Qn5JScCZDZqDH+QUsCJ6TNFMy2aysjBwl40RGQK 90Zb57+XIiSAAt+alCeE1X1Xkjys7lGHsV6zk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RhUWe1M/YFib/ndD0slrxMWTznvXwm7Bo+hDs0FVkxaeU7gvFRmn4NAv97DXxpil/B boSK9sGjclqyN3kowNnDzzwrPEtOZK2R9b0OqHJ4irPQ57kbzRqwVi+ayF/UyxLyeXU0 9VcKMw3vUqAg83nA34W1QO9RXIdpVob+SLF90= MIME-Version: 1.0 Received: by 10.220.127.65 with SMTP id f1mr1007911vcs.90.1278004845209; Thu, 01 Jul 2010 10:20:45 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 10:20:45 -0700 (PDT) In-Reply-To: <20100701170503.GA99226@icarus.home.lan> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <20100701170503.GA99226@icarus.home.lan> Date: Fri, 2 Jul 2010 01:20:45 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: maurovale@gmail.com, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 17:20:51 -0000 Hello Jeremy, On Fri, Jul 2, 2010 at 1:05 AM, Jeremy Chadwick wrote: > > 3) Have you tried downloading a 8.1-RC1 LiveFS CD and seeing if it > boots, works, etc? =A0You might be able to start to recovery your system > from there. I just booted the FreeBSD 8.0 DVD but whenever I choose the fixit, it is asking me for a live filesystem CD/DVD. So now, I am downloading the FreeBSD 8.0 and 8.1-RC1 livefs.iso then I will burn them. Thank you. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 17:23:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23B75106566C for ; Thu, 1 Jul 2010 17:23:41 +0000 (UTC) (envelope-from ssanbeg@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id DF52B8FC1F for ; Thu, 1 Jul 2010 17:23:40 +0000 (UTC) Received: by pwj9 with SMTP id 9so271401pwj.13 for ; Thu, 01 Jul 2010 10:23:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:x-mimeole; bh=WsA6ETvg5IYDhbIWAMhGRqhx7X7Lb7KU3zJBy7tQFKo=; b=po+MfLRvsA65IDksC+LLdaVjATRP96m4MirCbJGAwbrIlACBDXTVYIxYCDjVUWVmV5 l1F7WnSqvczQDHmbBG6f012Da0AGjS+vvpigIgS38HD9tmwqukAF0w19s8qvpIJWqY59 XE4vPC1Py3kKLcycS2Bw+YF6fOuQmMAHk9FhU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole; b=YVE5UXgq1mJh5b0D2MvxzfNQv96MNxPY4KeHImzau0K+88Ja6hWWNg1k3pgfqvJ0A8 bimC1OOtHJmtrRxJ+Uznj/h0oDcoICcbX1+PESJqDGQ1oplrORlqZ+GwrVcFKM0kX1wd jmALG00ZIfh3kqeK1iryZFQF+1efGtcFH6QqI= Received: by 10.143.87.7 with SMTP id p7mr12824010wfl.146.1278003188477; Thu, 01 Jul 2010 09:53:08 -0700 (PDT) Received: from sunrise (pool-98-117-108-60.sttlwa.fios.verizon.net [98.117.108.60]) by mx.google.com with ESMTPS id f2sm7279124wfp.11.2010.07.01.09.53.06 (version=SSLv3 cipher=RC4-MD5); Thu, 01 Jul 2010 09:53:06 -0700 (PDT) From: "Scott Sanbeg" To: "'GNUbie'" , References: <4C280435.4060603@halplant.com><20100701160622.GA98823@icarus.home.lan> In-Reply-To: Date: Thu, 1 Jul 2010 09:52:53 -0700 Message-ID: <2E1EC727E18E4B4EB7EE084A9BC99A57@sunrise> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 thread-index: AcsZOLZyNPBcJGm4Sje+Lm0U5B3vnQABJzTQ X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18197 Cc: Subject: RE: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 17:23:41 -0000 I had the same thing happening while running in VirtualBox. Tested on a bare-metal machine afterward the results were the same - following the how-to's on running a ZFS root, or a ZFS swap device, or a gmirror root = that included swap (w/o ZFS at all) produced what your screenshot shows. My platform is amd64.=20 Scott -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of GNUbie Sent: Thursday, July 01, 2010 9:14 AM To: freebsd-stable@freebsd.org Cc: maurovale@gmail.com; freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 Hello Jeremy, On Fri, Jul 2, 2010 at 12:06 AM, Jeremy Chadwick wrote: > > Kernel crash dumps are not enabled by default. =A0You need to define = the > following in /etc/rc.conf before that will happen: > > dumpdev=3D"auto" Ok. So, the line "Cannot dump. Device not defined or unavailable." is already going to be an output of the kernel crash. Meaning, during bootup, somehow the kernel crash and since crash dumps was not defined, that is why I was getting that message I just mentioned. Moving forward, what are your recommendations in order for me to be able to boot from my system? Regards, GNUbie _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 17:25:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF0401065678 for ; Thu, 1 Jul 2010 17:25:03 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 501C48FC23 for ; Thu, 1 Jul 2010 17:25:02 +0000 (UTC) Received: by vws6 with SMTP id 6so1840163vws.13 for ; Thu, 01 Jul 2010 10:24:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=peEBTmqn9VsVMzate6gs6vFsc8Yn25gvHzft0Z4pNac=; b=NX++R1oIJDoTQbrbi8hdraZN+kspKyfB+d0gEBaOhjnd0Jasj8lpmzhRYEjkIpzPX4 eWVhLrZRpdKmLh5R4WJZj/vrjckHaPfVZp0YrPf4bH/hJomeqSOYW6PGzax353orRcmf KZ/SEwOROTfaR0YFpuAzCVHgZX/HNdtNHc1cM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=VlIUI808SL/ddpgNjTvH2gKwLI2XTucY8yuo3z4tHQf374CLBJI0ID5n2ZiSkgEOX5 mTOSE0fSwMDEucfm0qnf3TbJE//MqV1C5Z87j1n/s3CKq7UVQqnUN7uxRDL5rWVHz5WQ 4cshJ/B8pRkWEKurZ9Fo5Dn4cMiAKxyM0Lz70= MIME-Version: 1.0 Received: by 10.220.159.14 with SMTP id h14mr5322142vcx.255.1278005097803; Thu, 01 Jul 2010 10:24:57 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 10:24:57 -0700 (PDT) In-Reply-To: <23E8A4AA1EF343A1AF66BC96FF41FB50@sunrise> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <2E1EC727E18E4B4EB7EE084A9BC99A57@sunrise> <23E8A4AA1EF343A1AF66BC96FF41FB50@sunrise> Date: Fri, 2 Jul 2010 01:24:57 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: ssanbeg@gmail.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 17:25:04 -0000 Hello Scott, On Fri, Jul 2, 2010 at 1:17 AM, Scott Sanbeg wrote: > For me, GNUbie, it was a matter of laying out UFS filesystems. The system > comes up just fine with this and has run rock-solid for 3 weeks or so now. I > am currently scripting a configuration for creating a RAID-1 boot/swap > device and RAID-1+0 everything else, and expect to complete it some time > next week. > > I will return to the pursuit of getting ZFS to work for root at a later > time. ZFS is cool, but 8.0-RELEASEp3 doesn't appear to like it very well. Or > it's me being a newbie once again to the FreeBSD/ZFS platform. :) Count me in. I'm a total newbie. ;-) Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 17:25:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DB8A1065670 for ; Thu, 1 Jul 2010 17:25:40 +0000 (UTC) (envelope-from ssanbeg@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 13ECE8FC19 for ; Thu, 1 Jul 2010 17:25:39 +0000 (UTC) Received: by pvb32 with SMTP id 32so983846pvb.13 for ; Thu, 01 Jul 2010 10:25:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:x-mimeole; bh=9bRf0LSaO9J2EEuzsC/qHbOz3PYWaJse3XyXJvpa5kA=; b=On3KNvnDxBphm/1MPhO7IPv8EZRdeNSSLHGDS6P5uhipSUMVkAdIhe2zTS4oP+ZeFX j3GFdHmfUwvbv1jP3qh9C9m8puRsUFA5ZcF3G8QQfYEcDOHx9LLRUXCkmgJ1tYbso6ef k9aM7BMwZ8lRlyc8f1InGYpwatY6xcHYdM7yE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole; b=tsovTpfKiTg7mjEglbqpHdXgjhJGDHy2vGBV0SIMRK25yD1exip4v+X3fQCVR6QMCh tVb7w7c9idBEAAoyWU1AG4Vp5O+/8SmL+i9j27ddpmmvDCXUexnGdPmpNz05YrTMXm6b jIZhAJjn3ZUHI/o4IrY2xM305s446o5SJuDNs= Received: by 10.142.213.13 with SMTP id l13mr9487840wfg.36.1278004673177; Thu, 01 Jul 2010 10:17:53 -0700 (PDT) Received: from sunrise (pool-98-117-108-60.sttlwa.fios.verizon.net [98.117.108.60]) by mx.google.com with ESMTPS id c15sm7312556rvi.11.2010.07.01.10.17.52 (version=SSLv3 cipher=RC4-MD5); Thu, 01 Jul 2010 10:17:52 -0700 (PDT) From: "Scott Sanbeg" To: "'GNUbie'" , References: <4C280435.4060603@halplant.com><20100701160622.GA98823@icarus.home.lan><2E1EC727E18E4B4EB7EE084A9BC99A57@sunrise> In-Reply-To: Date: Thu, 1 Jul 2010 10:17:38 -0700 Message-ID: <23E8A4AA1EF343A1AF66BC96FF41FB50@sunrise> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 thread-index: AcsZPs9+UB+jzjx8SeCDnNzEP1ygkgAAbS9Q X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18197 Cc: Subject: RE: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 17:25:40 -0000 For me, GNUbie, it was a matter of laying out UFS filesystems. The system comes up just fine with this and has run rock-solid for 3 weeks or so now. I am currently scripting a configuration for creating a RAID-1 boot/swap device and RAID-1+0 everything else, and expect to complete it some time next week. I will return to the pursuit of getting ZFS to work for root at a later time. ZFS is cool, but 8.0-RELEASEp3 doesn't appear to like it very well. Or it's me being a newbie once again to the FreeBSD/ZFS platform. :) Scott -----Original Message----- From: GNUbie [mailto:gnubie@gmail.com] Sent: Thursday, July 01, 2010 10:00 AM To: freebsd-stable@freebsd.org Cc: ssanbeg@gmail.com Subject: Re: Unable to boot FreeBSD 8.0-p3 Hello Scott, On Fri, Jul 2, 2010 at 12:52 AM, Scott Sanbeg wrote: > I had the same thing happening while running in VirtualBox. Tested on a > bare-metal machine afterward the results were the same - following the > how-to's on running a ZFS root, or a ZFS swap device, or a gmirror root that > included swap (w/o ZFS at all) produced what your screenshot shows. My > platform is amd64. I also have a ZFS on which I mount it on my /data slice. The rest are the default UFS. My machine is based on an Intel D945GCLF2 with 1GB RAM and 1TB SATA HDD. Is your problem solved already? Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:01:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42F46106564A for ; Thu, 1 Jul 2010 18:01:10 +0000 (UTC) (envelope-from alan.bryan@yahoo.com) Received: from web50501.mail.re2.yahoo.com (web50501.mail.re2.yahoo.com [206.190.38.77]) by mx1.freebsd.org (Postfix) with SMTP id 02BAF8FC20 for ; Thu, 1 Jul 2010 18:01:09 +0000 (UTC) Received: (qmail 43263 invoked by uid 60001); 1 Jul 2010 18:01:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278007264; bh=jyctgp9elowTKq64lN4Abx34MLD/q9KPog1d+DECw7o=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vhilqvponJmlzEfcAV0fpHJoijg266FdjMdlgkWVlGtHhmtPrj2K4yN6piH/UZm4aX1TnXGAZNU/S2NuraxIIClWDPF3uKumoPi0ypi1maDlY7+hOmSfEQ4zifUO59Q4CeYmPVgthaVFT6zw5GpObMevXFqECnLbgbcOKk3dWVk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bvL7XaV2JPH3kZrqKgMEm++Ea0OwWxOg6bcNzvmfkM3WCKydW0tLZovpUqE10ygRmLL5aUhhqrpdSuYPOClXIc9D2LGk40/XNwkpSsFus5lxKNJnvBMJ7jqFMxC1GrEWXy8j0gqScwVk6b67KRiwN0O+jyqFJXBx6+JgByaWPHw=; Message-ID: <425902.41392.qm@web50501.mail.re2.yahoo.com> X-YMail-OSG: LDbmq7EVM1lkzPsNTgQDAjzOtk1ywG8zS2abJWp8qzJLaNf yBZYrnGM.U_I5HcuVBHTewRPrDbhl3a9fSxRIggfHFaO6.mKZCCjklhy4629 s5xJg8kwT4hYaylVNAMqvwIA3J7v2WGrk5bFI9z_sr.Exg6Y9yiLS1pJaZ30 CuoBZ7LHNWQtSMJJcWJ9CNHbPNhLTxPDd7R7i.D6ik4H2t7XvbbGtPlp8dBD D11BHd6zmMwXa_d0dR_y7ImT6rxnw3fU4lEDU5ntoy9JkisQXBDiMyPPk_qR V5dEieoUK7jmoFZFAh6bd2ackHAZTXBhwWgLPiv6X2YNFSNH5a6WoPFevu5L eldksoadGR4rXFZ1e4BqUwnikpizLRZ4pADH0Wt52L5WIwCiooUXyJ.YuQBg YFQ-- Received: from [99.24.6.121] by web50501.mail.re2.yahoo.com via HTTP; Thu, 01 Jul 2010 11:01:04 PDT X-Mailer: YahooMailClassic/11.1.4 YahooMailWebService/0.8.104.274457 Date: Thu, 1 Jul 2010 11:01:04 -0700 (PDT) From: alan bryan To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:01:10 -0000 Setup:=0A=0Aserver - FreeBSD 8-stable from today.=A0 2 UFS dirs exported vi= a NFS.=0Aclient - FreeBSD 8.0-Release. Running a test php script that copi= es around various files to/from 2 separate NFS mounts.=0A=0ASituation: =0A= =0Ascript is started (forked to do 20 simultaneous runs) and 20 1GB files a= re copied to the NFS dir which works fine.=A0 When it then switches to read= ing those files back and simultaneously writing to the other NFS mount I se= e a hang of 75 seconds.=A0 If I do an "ls -l" on the NFS mount it hangs too= .=A0 After 75 seconds the client has reported:=0A=0Anfs server 192.168.10.1= 33:/usr/local/export1: not responding=0Anfs server 192.168.10.133:/usr/loca= l/export1: is alive again=0Anfs server 192.168.10.133:/usr/local/export1: n= ot responding=0Anfs server 192.168.10.133:/usr/local/export1: is alive agai= n =0A=0Aand then things start working again.=A0 The server was originally F= reeBSD 8.0-Release also but was upgraded to the latest stable to see if thi= s issue could be avoided.=0A=0A# nfsstat -s -W -w 1=0A GtAttr Lookup Rdlink= =A0=A0=A0Read=A0 Write Rename Access=A0 Rddir=0A=A0 =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 222=A0 =A0 257=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 178=A0 =A0 135=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 = =A0=A0=A085=A0 =A0 127=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0= =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 = =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =0A=0A... for 75 rows of all zeros=0A=0A=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 272=A0 =A0 266=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A=A0 = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167=A0 =A0 165=A0 =A0 =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=0A=0AI also tried runs with 15 simultaneous processe= s and 25. 15 processes gave only about a 5 second stall but 25 gave again = the same 75 second stall. =0A=0AFurther, I tested with 2 mounts to the sa= me server but from ZFS filesytems with the exact same stall/timeout periods= . So, it doesn't appear to matter what the underlying filesystem is - it's= something in NFS or networking code.=0A=0AAny ideas on what's going on her= e? What's causing the complete stall period of zero NFS activity? Any fl= aws with my testing methods?=0A=0AThanks for any and all help/ideas.=0A=0A-= -Alan=0A=0A=0A=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:03:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02FC71065675 for ; Thu, 1 Jul 2010 18:03:28 +0000 (UTC) (envelope-from gnubie@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A4F638FC19 for ; Thu, 1 Jul 2010 18:03:27 +0000 (UTC) Received: by vws6 with SMTP id 6so1892348vws.13 for ; Thu, 01 Jul 2010 11:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ZgYOpR6W25YvNga87rqkRY0u//5dtHIZbxkl0/r5O/c=; b=vQgpvwWK2odRPhP2bNiTqQekATagQOoGJ4NrFIoD4w2HL/K95Xw7Ztlmw7Srjb1wpk 9la9a3MileZsE8gmcv/a4eZqog+5dDF6yowqDp1ZOe0HqXQgOPXYDeuw5kjo7cfwT8t3 shZL3JYfnJ5dd3qCJw7aE+TlBRcZ386wbuL7Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=d55wJcYFJkEGiOCW7DyOWut5iWnsMn/4zEwW0eu/Vj2SOD5aBF1UDXamv9Hq5nOAUv FpShD3vXAUB/Kf3A6LMRV5oXqCvfMEq5HdvZpn6dipVQo1rmEf9i2K7h6yhuMSdCckdT bZ3YwxDKCE6nAyXOTwX8+zb3LcAstBWGO1Vh0= MIME-Version: 1.0 Received: by 10.220.124.73 with SMTP id t9mr5854307vcr.177.1278007403297; Thu, 01 Jul 2010 11:03:23 -0700 (PDT) Received: by 10.220.90.212 with HTTP; Thu, 1 Jul 2010 11:03:22 -0700 (PDT) In-Reply-To: References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <20100701170503.GA99226@icarus.home.lan> Date: Fri, 2 Jul 2010 02:03:22 +0800 Message-ID: From: GNUbie To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: michal@ionic.co.uk, maurovale@gmail.com, ssanbeg@gmail.com, freebsd@jdc.parodius.com, mark@exonetric.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:03:28 -0000 Hello all, On Fri, Jul 2, 2010 at 1:20 AM, GNUbie wrote: > > I just booted the FreeBSD 8.0 DVD but whenever I choose the fixit, it > is asking me for a live filesystem CD/DVD. So now, I am downloading > the FreeBSD 8.0 and 8.1-RC1 livefs.iso then I will burn them. I realized that choosing fixit, it doesn't know that the LiveFS cd is inside an external USB DVD drive which I cannot mount the filesystem on my HDD. Regards, GNUbie From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:06:35 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 763E9106566B for ; Thu, 1 Jul 2010 18:06:35 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2EF1F8FC18 for ; Thu, 1 Jul 2010 18:06:34 +0000 (UTC) Received: by gyf3 with SMTP id 3so1546760gyf.13 for ; Thu, 01 Jul 2010 11:06:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=96BtFixCvakOQV0XJKRgywudtecQc5FLEHZfVi4xCso=; b=W5ZWzC4n+3tpzBNXNEpXXr51FU7qymMAyX+b6h/IzR74ZRGDuR5kxPq8WOd3lhWhah C6Wxx5R234TM8JodJiU4Snd1xb34StrYhJprzqDV+0cp+GucsG3KY2KR27FB3h3MAzEe Y3zAOsyNsZbTifg2G9IfY+nhfxOQRISyEoHpQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oIIQE1U2CThiBIgZ89adGTy7oGOgTa/IhxPApwjBfO8MoHHIdLEr0RD8KPWjfOIN4P Qbfr36zg/bfddzd/jhu9Oa94l/xRGJpsX7SnopvNZmfjP7HiQpCeIEV5SoNOniveWxhq fgGRcqkKAA+CPOAMFNF8ceyfA2q3cRvagJ+VU= MIME-Version: 1.0 Received: by 10.229.183.198 with SMTP id ch6mr6414356qcb.243.1278007587377; Thu, 01 Jul 2010 11:06:27 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 11:06:27 -0700 (PDT) In-Reply-To: <20100701145848.GA97312@icarus.home.lan> References: <4C2B35A2.7010709@vfemail.net> <20100701145848.GA97312@icarus.home.lan> Date: Thu, 1 Jul 2010 11:06:27 -0700 Message-ID: From: Garrett Cooper To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Tom Evans , FreeBSD Stable Mailing List , Free BSD Subject: Re: kernel issues with 8 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:06:35 -0000 On Thu, Jul 1, 2010 at 7:58 AM, Jeremy Chadwick wrote: > On Thu, Jul 01, 2010 at 03:04:56PM +0100, Tom Evans wrote: >> On Wed, Jun 30, 2010 at 1:16 PM, Free BSD wrote: >> > Dear List Members >> > Also, even though I have custom keyboard in my kernel configuration, >> > whenever I boot into single user mode I get US layout (it works fine w= hen in >> > multi-user mode). >> >> Does it work correctly if you run kbdmap and choose the correct >> layout? If so, set keymap in /etc/rc.conf so it is always configured >> correctly. > > AFAIK this only applies to multi-user mode. =A0rc scripts (thus use of > rc.conf), to my knowledge, aren't run in single-user. Depending on what's going on, I've run rc scripts in single user mode to diagnose issues and/or get my machine(s) up to limping state, but by and large that's not a supported model (and thus I have booted my machine into quasi-multiuser mode). Just wanted to say that there are other folks out there using rc scripts for `non-standard' multiuser scenarios :). Thanks, -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:10:40 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C22A9106566B for ; Thu, 1 Jul 2010 18:10:40 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 376FF8FC14 for ; Thu, 1 Jul 2010 18:10:39 +0000 (UTC) Received: by gxk7 with SMTP id 7so1539193gxk.13 for ; Thu, 01 Jul 2010 11:10:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=/4TT1BVu7zazFb9/FbZcoPs7itVW/yY2TlDIyKRu0Qk=; b=F6fj4tqHwrLe+ekSPpDn6uce4bMQAnq7jGGn+UH5AnDKGfbpeoBMnzw4xovJvl3F87 2W9JfsqeL523s8xyu1PzgDd770JCTYX80ZaTkJwvsrIi+PLbaErWKqk4uM12K5YgdHFx ck2me4qWuW/Vt4DJtdcXIJwK+xmdElZoSFDV4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KhBXlDwBA+eYdpzvo/YOYQoaYqZeDCz5wVnBqfUtbAy4xZmBZBOMPRVmSPpdz9va/E ObIht9QxBNMul0rzHD1ZSEpjqOHO7nS08iJ6W05l7R6OeGjGo9w2W4ffg20x0897D+/x VeFshsofeAA61bgcX7mdoROhuTZUXVKP9ycGI= MIME-Version: 1.0 Received: by 10.229.232.6 with SMTP id js6mr6499703qcb.14.1278007836411; Thu, 01 Jul 2010 11:10:36 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 11:10:36 -0700 (PDT) In-Reply-To: <4C2CC0B2.4030100@exonetric.com> References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <4C2CC0B2.4030100@exonetric.com> Date: Thu, 1 Jul 2010 11:10:36 -0700 Message-ID: From: Garrett Cooper To: Mark Blackman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, GNUbie , maurovale@gmail.com, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:10:40 -0000 On Thu, Jul 1, 2010 at 9:22 AM, Mark Blackman wrote: > GNUbie wrote: > >> Moving forward, what are your recommendations in order for me to be >> able to boot from my system? > > Boot from a "live" CD of some recent/reasonable vintage, mount the > filesystems and try to reinstall the old kernel installation? probably > as simple as a > > 1. "move installed kernel directory to another name" > 2. "move kernel.old directory to kernel" > > Bear in mind, I've not done this kind of fiddling for a while, so > I might have the precise details wrong. 1. Go into rescue shell. 2. Enter in: cd /mnt/boot; mv kernel kernel.old 3. Install kernel distribution from sysinstall :). -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:12:09 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2F3B106566C for ; Thu, 1 Jul 2010 18:12:09 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 995FE8FC0A for ; Thu, 1 Jul 2010 18:12:09 +0000 (UTC) Received: by gyf3 with SMTP id 3so1551598gyf.13 for ; Thu, 01 Jul 2010 11:12:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=68PHpgAmAZxo/kXubrAJZBdyIau0tPKzynWhlm7HYIY=; b=fo6SQ7lU6J7SLgfq6CNfF72tEpH1IPsN/zszHMRpK0/juZGxQmuy2DTgLNuUemrRxt DbPNT22WBSOO9eOcMXuR9h3lleW7UFpl+TT2De9DMs7OgQIXl6H5rMupKLQJ31RzCs23 xpMPV62NnCWMO8Da0Bw4fqJaxno4Q3TckdPvU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ws+SjtALvjT467ztesCwsZrYAAqDxA520bJeC17rUxAryNsjhGvS2bWQ1pio8XSLsw u+U8rWAi+HNo358H10OAP5XN+dOki4Cf6vFEamIeNTsso/S/NiJeiPKJ+KWsckqm97sk LMLoT8zT1R9fWC/F5+Yag929RrR07TPJ+2Pq0= MIME-Version: 1.0 Received: by 10.229.223.201 with SMTP id il9mr6472314qcb.89.1278007925688; Thu, 01 Jul 2010 11:12:05 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 11:12:05 -0700 (PDT) In-Reply-To: References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <4C2CC0B2.4030100@exonetric.com> Date: Thu, 1 Jul 2010 11:12:05 -0700 Message-ID: From: Garrett Cooper To: Mark Blackman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, GNUbie , maurovale@gmail.com, freebsd@jdc.parodius.com Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:12:10 -0000 On Thu, Jul 1, 2010 at 11:10 AM, Garrett Cooper wrote: > On Thu, Jul 1, 2010 at 9:22 AM, Mark Blackman wrote: >> GNUbie wrote: >> >>> Moving forward, what are your recommendations in order for me to be >>> able to boot from my system? >> >> Boot from a "live" CD of some recent/reasonable vintage, mount the >> filesystems and try to reinstall the old kernel installation? probably >> as simple as a >> >> 1. "move installed kernel directory to another name" >> 2. "move kernel.old directory to kernel" >> >> Bear in mind, I've not done this kind of fiddling for a while, so >> I might have the precise details wrong. > > 1. Go into rescue shell. 1.a. mount filesystem ;P. > 2. Enter in: cd /mnt/boot; mv kernel kernel.old > 3. Install kernel distribution from sysinstall -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:13:31 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8763106566B for ; Thu, 1 Jul 2010 18:13:31 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 92A608FC0A for ; Thu, 1 Jul 2010 18:13:31 +0000 (UTC) Received: by qwg5 with SMTP id 5so982903qwg.13 for ; Thu, 01 Jul 2010 11:13:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Ki2JLRGZnHMHVifVW3aGM05w4gTD2GHRhLeHZTccuks=; b=Tgbr19d9Mls/DE7nDh/Qwvev12tQH3FJWSGC+xs9YaAVBKwfaLm7lHZcyr8K0x4Qp8 7N4nlWIuFniCq3/bfd5bHZsWSoyEuytdfR0t2LT1YMj29b6x5qk61wHV/6bWjH2RZTGs P1f+oRJQns2Xl6QwLyYR2ixgUNVT6BQsWQskg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oUFHC/zBDk8F47Dn5nlYJfFT0ndW4gXfZ4ISQtguY/CuLAPHDIBarQs8fHbiMr4APr uUHOkkNwBR++WeAkAW1PQPYPm5o1vVE05apZHu2u8tiKZubwrtGvMz2v0Cqtx8vgnWMl oJyK/5p69RP/p1W04y8G5z2TaowsNY6ZxV+Ho= MIME-Version: 1.0 Received: by 10.224.11.69 with SMTP id s5mr6162764qas.158.1278007999940; Thu, 01 Jul 2010 11:13:19 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 11:13:19 -0700 (PDT) In-Reply-To: <425902.41392.qm@web50501.mail.re2.yahoo.com> References: <425902.41392.qm@web50501.mail.re2.yahoo.com> Date: Thu, 1 Jul 2010 11:13:19 -0700 Message-ID: From: Garrett Cooper To: alan bryan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:13:32 -0000 On Thu, Jul 1, 2010 at 11:01 AM, alan bryan wrote: > Setup: > > server - FreeBSD 8-stable from today.=A0 2 UFS dirs exported via NFS. > client - FreeBSD 8.0-Release. =A0Running a test php script that copies ar= ound various files to/from 2 separate NFS mounts. > > Situation: > > script is started (forked to do 20 simultaneous runs) and 20 1GB files ar= e copied to the NFS dir which works fine.=A0 When it then switches to readi= ng those files back and simultaneously writing to the other NFS mount I see= a hang of 75 seconds.=A0 If I do an "ls -l" on the NFS mount it hangs too.= =A0 After 75 seconds the client has reported: > > nfs server 192.168.10.133:/usr/local/export1: not responding > nfs server 192.168.10.133:/usr/local/export1: is alive again > nfs server 192.168.10.133:/usr/local/export1: not responding > nfs server 192.168.10.133:/usr/local/export1: is alive again > > and then things start working again.=A0 The server was originally FreeBSD= 8.0-Release also but was upgraded to the latest stable to see if this issu= e could be avoided. > > # nfsstat -s -W -w 1 > =A0GtAttr Lookup Rdlink=A0=A0=A0Read=A0 Write Rename Access=A0 Rddir > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 222=A0 =A0 257=A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 178=A0 =A0 135=A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=A0=A085=A0 =A0 127=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > > ... for 75 rows of all zeros > > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 272=A0 =A0 266=A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167=A0 =A0 165=A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0 =A0 0 > > I also tried runs with 15 simultaneous processes and 25. =A015 processes = gave only about a 5 second stall but 25 gave again the same 75 second stall= . > > Further, I tested with 2 mounts to the same server but from ZFS filesytem= s with the exact same stall/timeout periods. =A0So, it doesn't appear to ma= tter what the underlying filesystem is - it's something in NFS or networkin= g code. > > Any ideas on what's going on here? =A0What's causing the complete stall p= eriod of zero NFS activity? =A0 Any flaws with my testing methods? > > Thanks for any and all help/ideas. What network driver are you using? Have you tried tcpdumping the packets? -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:30:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20BB41065674 for ; Thu, 1 Jul 2010 18:30:23 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.50]) by mx1.freebsd.org (Postfix) with ESMTP id E213F8FC08 for ; Thu, 1 Jul 2010 18:30:22 +0000 (UTC) Received: (qmail 9981 invoked from network); 1 Jul 2010 18:30:22 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 1 Jul 2010 18:30:22 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 26B4B5084D; Thu, 1 Jul 2010 14:30:20 -0400 (EDT) From: Lowell Gilbert To: GNUbie References: <4C280435.4060603@halplant.com> <20100701160622.GA98823@icarus.home.lan> <20100701170503.GA99226@icarus.home.lan> Date: Thu, 01 Jul 2010 14:30:19 -0400 In-Reply-To: (gnubie@gmail.com's message of "Fri, 2 Jul 2010 02:03:22 +0800") Message-ID: <4439w3837o.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot FreeBSD 8.0-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:30:23 -0000 GNUbie writes: > I realized that choosing fixit, it doesn't know that the LiveFS cd is > inside an external USB DVD drive which I cannot mount the filesystem > on my HDD. I can't parse that sentence well enough to figure out what you mean. Taking a wild guess: I think what you want to do is mount the hard disk on the fixit filesystem (which is actually in memory, if I recall correctly). That's no problem: you can fsck the hard disk's partitions easily from the fixit environment, and having done that, you can just mount them. They won't be mounted in their "normal" place, but you can mount, for example, the root filesystem from the hard disk on /mnt, then /usr on /mnt/usr, etc. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 18:51:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63F8E1065677 for ; Thu, 1 Jul 2010 18:51:34 +0000 (UTC) (envelope-from alan.bryan@yahoo.com) Received: from web50508.mail.re2.yahoo.com (web50508.mail.re2.yahoo.com [206.190.38.84]) by mx1.freebsd.org (Postfix) with SMTP id 0D5DF8FC19 for ; Thu, 1 Jul 2010 18:51:33 +0000 (UTC) Received: (qmail 39739 invoked by uid 60001); 1 Jul 2010 18:51:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278010288; bh=fDGwQjDDjK+2jb49OrsyAcNwZH734YhkskEk+gy31Hw=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vIv+QkopnkWaUiEgIWeYr41wJeI/b+00IuKrKkpOdrgBM8N80lWN/s4D9aGUJZfs5hwTsWv+4We7NrnzxHPKOQGjZ4Di3dU0cgDa4dZVxB0w03cZlXw8yadr8gEkyS/35agajVmUN3NOlohxt+I539rZMkhsj+M+M+PiauxwzUI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=mIDERZWNl5rurs0q3YobSvrRASD9sW+jY+dvj9tMgcTPFh+ZhkaGbSkoPSrTME+EwGI0ayP29l01bgNpv5x2UUmUi2x1VqOwz6NS49PavgAuWSWMBzNdCljQQDQRjDovKXy6A8CAaHtWJKBU2+5MyI+SOlNvG/6CkedgiEL6uxA=; Message-ID: <538823.39365.qm@web50508.mail.re2.yahoo.com> X-YMail-OSG: Sp13VBwVM1m8adgJ1HQiiPDsLdYmRHWgLEFhjpKzfSrVmji NEiXbWyBJaPX0o4El7XNxokqekhluLg5q37Geyyj36sBSChcPmciFs7q_4kB Qw8pDZ1vU9wzuHo62vMJAx_63qBTnjEJinvrPobROh6DDCTUBo_qrqQ3UgQf b8ZPp2TB0VGDPS9joTVH4_lejuY.0V9pKrykQ5aVA0cMOa6IIDT2gMS3Vin5 O5gBnuc9_iVEm8KRcVJId0J7A8Q9Ta2D7DjmZSsIS223HPrwx5DfNhjJxOSz aysv0DRhoItxSjTfI4JxLXJtCQVSx..KKPL4xDyFjH4OSXevi8cfxPff_Yj8 KmA-- Received: from [99.24.6.121] by web50508.mail.re2.yahoo.com via HTTP; Thu, 01 Jul 2010 11:51:28 PDT X-Mailer: YahooMailClassic/11.1.4 YahooMailWebService/0.8.104.274457 Date: Thu, 1 Jul 2010 11:51:28 -0700 (PDT) From: alan bryan To: Garrett Cooper In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 18:51:34 -0000 =0A=0A--- On Thu, 7/1/10, Garrett Cooper wrote:=0A=0A>= From: Garrett Cooper =0A> Subject: Re: NFS 75 second s= tall=0A> To: "alan bryan" =0A> Cc: freebsd-stable@fre= ebsd.org=0A> Date: Thursday, July 1, 2010, 11:13 AM=0A> On Thu, Jul 1, 2010= at 11:01 AM, alan=0A> bryan =0A> wrote:=0A> > Setup:= =0A> >=0A> > server - FreeBSD 8-stable from today.=A0 2 UFS dirs=0A> export= ed via NFS.=0A> > client - FreeBSD 8.0-Release. =A0Running a test php=0A> s= cript that copies around various files to/from 2 separate=0A> NFS mounts.= =0A> >=0A> > Situation:=0A> >=0A> > script is started (forked to do 20 simu= ltaneous runs)=0A> and 20 1GB files are copied to the NFS dir which works= =0A> fine.=A0 When it then switches to reading those files back=0A> and sim= ultaneously writing to the other NFS mount I see a=0A> hang of 75 seconds.= =A0 If I do an "ls -l" on the NFS mount it=0A> hangs too.=A0 After 75 secon= ds the client has reported:=0A> >=0A> > nfs server 192.168.10.133:/usr/loca= l/export1: not=0A> responding=0A> > nfs server 192.168.10.133:/usr/local/ex= port1: is alive=0A> again=0A> > nfs server 192.168.10.133:/usr/local/export= 1: not=0A> responding=0A> > nfs server 192.168.10.133:/usr/local/export1: i= s alive=0A> again=0A> >=0A> > and then things start working again.=A0 The s= erver was=0A> originally FreeBSD 8.0-Release also but was upgraded to the= =0A> latest stable to see if this issue could be avoided.=0A> >=0A> > # nfs= stat -s -W -w 1=0A> > =A0GtAttr Lookup Rdlink=A0=A0=A0Read=A0 Write Rename= =0A> Access=A0 Rddir=0A> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 2= 22=A0 =A0 257=A0 =A0=0A> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> > =A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 178=A0 =A0 135=A0 =A0=0A> =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=0A> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=A0= =A085=A0 =A0 127=A0=0A> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> > =A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0=0A> =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 =A0 0=0A> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0= =A0 =A0 0=A0 =A0 =A0 0=A0=0A> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> > = =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0=0A> = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0= =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0=0A> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =0A> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0= =0A> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >=0A> > ... for 75 rows of all= zeros=0A> >=0A> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 272=A0 = =A0 266=A0 =A0=0A> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> > =A0 =A0 =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167=A0 =A0 165=A0 =A0=0A> =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=0A> >=0A> > I also tried runs with 15 simultaneous processes = and=0A> 25. =A015 processes gave only about a 5 second stall but 25=0A> gav= e again the same 75 second stall.=0A> >=0A> > Further, I tested with 2 moun= ts to the same server but=0A> from ZFS filesytems with the exact same stall= /timeout=0A> periods. =A0So, it doesn't appear to matter what the=0A> under= lying filesystem is - it's something in NFS or=0A> networking code.=0A> >= =0A> > Any ideas on what's going on here? =A0What's causing=0A> the complet= e stall period of zero NFS activity? =A0 Any flaws=0A> with my testing meth= ods?=0A> >=0A> > Thanks for any and all help/ideas.=0A> =0A> What network d= river are you using? Have you tried=0A> tcpdumping the packets?=0A> -Garret= t=0A> =0A=0AI'm using igb currently but have also used em. I have not trie= d tcpdumping the packets yet on this test. Any suggestions on things to lo= ok out for (I'm not that familiar with that whole process).=0A=0AWhich brin= gs up another point - I'm using TCP connections for NFS, not UDP. =0A=0A--= Alan=0A=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 19:23:59 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87A86106566B for ; Thu, 1 Jul 2010 19:23:59 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 37A328FC15 for ; Thu, 1 Jul 2010 19:23:58 +0000 (UTC) Received: by gwb1 with SMTP id 1so652137gwb.13 for ; Thu, 01 Jul 2010 12:23:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Vza7lFsk4MwTgwwrMrZEs1G7rfl5T5Q0fTgzK+cx5xI=; b=fQir3/tB9iLFYhbBMDn3ud40rDj3H6LLI/qX3Y+ti3E9fxuL1KqJ40Gs0RGPA3APPo b0LzMUQm3KYBe0Hhza+KWk7bI6sYkX+Ndh/SF8fDdnrKW+KpjpHKltzNuEbsDjBpcHBX g/uzf/uaKQcwRIe8h9qhbalWTbmyR2mHJ75Nc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dFvLN8r8vyl0fS2yQg9nUf2GAq7dRMn+wpNcDzXv8MlEGevC69z2fcxKVLAoxmwM+U osMmH/WIeMSJzdGUwvzEZ+6mzD0bXlrxHYAiqhojZ6dfdJCrEm5j16VBMZskWl71brxV GfDV3TWJlrhVSKTBCWZTw19vNOjjZ00RMfzGw= MIME-Version: 1.0 Received: by 10.229.235.197 with SMTP id kh5mr6645721qcb.237.1278012229927; Thu, 01 Jul 2010 12:23:49 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 12:23:49 -0700 (PDT) In-Reply-To: <538823.39365.qm@web50508.mail.re2.yahoo.com> References: <538823.39365.qm@web50508.mail.re2.yahoo.com> Date: Thu, 1 Jul 2010 12:23:49 -0700 Message-ID: From: Garrett Cooper To: alan bryan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 19:23:59 -0000 On Thu, Jul 1, 2010 at 11:51 AM, alan bryan wrote: > > > --- On Thu, 7/1/10, Garrett Cooper wrote: > >> From: Garrett Cooper >> Subject: Re: NFS 75 second stall >> To: "alan bryan" >> Cc: freebsd-stable@freebsd.org >> Date: Thursday, July 1, 2010, 11:13 AM >> On Thu, Jul 1, 2010 at 11:01 AM, alan >> bryan >> wrote: >> > Setup: >> > >> > server - FreeBSD 8-stable from today.=A0 2 UFS dirs >> exported via NFS. >> > client - FreeBSD 8.0-Release. =A0Running a test php >> script that copies around various files to/from 2 separate >> NFS mounts. >> > >> > Situation: >> > >> > script is started (forked to do 20 simultaneous runs) >> and 20 1GB files are copied to the NFS dir which works >> fine.=A0 When it then switches to reading those files back >> and simultaneously writing to the other NFS mount I see a >> hang of 75 seconds.=A0 If I do an "ls -l" on the NFS mount it >> hangs too.=A0 After 75 seconds the client has reported: >> > >> > nfs server 192.168.10.133:/usr/local/export1: not >> responding >> > nfs server 192.168.10.133:/usr/local/export1: is alive >> again >> > nfs server 192.168.10.133:/usr/local/export1: not >> responding >> > nfs server 192.168.10.133:/usr/local/export1: is alive >> again >> > >> > and then things start working again.=A0 The server was >> originally FreeBSD 8.0-Release also but was upgraded to the >> latest stable to see if this issue could be avoided. >> > >> > # nfsstat -s -W -w 1 >> > =A0GtAttr Lookup Rdlink=A0=A0=A0Read=A0 Write Rename >> Access=A0 Rddir >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 222=A0 =A0 257 >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 178=A0 =A0 135 >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=A0=A085=A0 =A0 127 >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > >> > ... for 75 rows of all zeros >> > >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 272=A0 =A0 266 >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167=A0 =A0 165 >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> > >> > I also tried runs with 15 simultaneous processes and >> 25. =A015 processes gave only about a 5 second stall but 25 >> gave again the same 75 second stall. >> > >> > Further, I tested with 2 mounts to the same server but >> from ZFS filesytems with the exact same stall/timeout >> periods. =A0So, it doesn't appear to matter what the >> underlying filesystem is - it's something in NFS or >> networking code. >> > >> > Any ideas on what's going on here? =A0What's causing >> the complete stall period of zero NFS activity? =A0 Any flaws >> with my testing methods? >> > >> > Thanks for any and all help/ideas. >> >> What network driver are you using? Have you tried >> tcpdumping the packets? >> -Garrett >> > > I'm using igb currently but have also used em. =A0I have not tried tcpdum= ping the packets yet on this test. =A0Any suggestions on things to look out= for (I'm not that familiar with that whole process). > > Which brings up another point - I'm using TCP connections for NFS, not UD= P. Is the net.inet.tcp.tso sysctl enabled or not? What about rxcsum and tx= csum? Thanks, -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 20:18:19 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06226106564A for ; Thu, 1 Jul 2010 20:18:19 +0000 (UTC) (envelope-from alan.bryan@yahoo.com) Received: from web50504.mail.re2.yahoo.com (web50504.mail.re2.yahoo.com [206.190.38.80]) by mx1.freebsd.org (Postfix) with SMTP id B57608FC12 for ; Thu, 1 Jul 2010 20:18:18 +0000 (UTC) Received: (qmail 47580 invoked by uid 60001); 1 Jul 2010 20:18:15 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278015495; bh=ZRu9EMSENp1GC3vEJqtscNMnjmEQgPUbGo0LMrAyzEY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=QJ8jsSm8i4ZacyjxjDF/ywPj/VkVdLYVV8sZ0CYXYyWQre9v5EPnuxgg8UiP70HCctsv+WWFZFjli3ohMMSTvWrAS68FFDKFbzL6kNvYoJHxl8mju7h/l9t5PzTSuz/Bg26bfH31CqbnLczkBpJIUgPHolY4C9FZsfSj5z2oOLc= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=QxdZrHH1G7nPX0r2kFV808NKqs1MwftNvBFptoE7cbPUYhJKtwuTe9gRIObe72i25CjKJ3oydefivcbTt3Ysq/Lpm/TnEHgnrvKV8WvZ+Gz2ZV0QrTtoQnFvwvdb55raO+keymtunBlMgCsvkywpIxNHKhZOPZX57HjkrMd0EBI=; Message-ID: <604345.41122.qm@web50504.mail.re2.yahoo.com> X-YMail-OSG: 6l6XbaoVM1m3pgi4p3dO4AqSCfUUc6dHkeHSJ9gPuClSs23 ML.Pf.LkBO83irtmdrR1hoC.WhkOIddb8hXasQ0FfsFiKzjctabtH.JOM.Rb XAvi1SLI1VLa_KEE499PTEtPNQsD_hBPkL6EE5up5e.VI.iyeiaANWVJ3YVZ v7.VkPOGSQbAtTu3baf4NNSjhNG1bVjvMft6uJpMnmzD.5YTPcEntSsyzxt4 up0GQVp6t_eXXjRgTe1zsMocNAl1oHBY93hd1DjnJpFTf6c6_CQ9jfbic3.6 xc2QeDVglcGVpbf.JccgcWAle_s6KzveKtB0Am5UYrTPH7.p3ZYsfKtclyVV gbg-- Received: from [99.24.6.121] by web50504.mail.re2.yahoo.com via HTTP; Thu, 01 Jul 2010 13:18:15 PDT X-Mailer: YahooMailClassic/11.1.4 YahooMailWebService/0.8.104.274457 Date: Thu, 1 Jul 2010 13:18:15 -0700 (PDT) From: alan bryan To: Garrett Cooper In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 20:18:19 -0000 =0A=0A--- On Thu, 7/1/10, Garrett Cooper wrote:=0A=0A>= From: Garrett Cooper =0A> Subject: Re: NFS 75 second s= tall=0A> To: "alan bryan" =0A> Cc: freebsd-stable@fre= ebsd.org=0A> Date: Thursday, July 1, 2010, 12:23 PM=0A> On Thu, Jul 1, 2010= at 11:51 AM, alan=0A> bryan =0A> wrote:=0A> >=0A> >= =0A> > --- On Thu, 7/1/10, Garrett Cooper =0A> wrote:= =0A> >=0A> >> From: Garrett Cooper =0A> >> Subject: Re:= NFS 75 second stall=0A> >> To: "alan bryan" =0A> >> = Cc: freebsd-stable@freebsd.org=0A> >> Date: Thursday, July 1, 2010, 11:13 A= M=0A> >> On Thu, Jul 1, 2010 at 11:01 AM, alan=0A> >> bryan =0A> >> wrote:=0A> >> > Setup:=0A> >> >=0A> >> > server - FreeBSD 8-= stable from today.=A0 2 UFS=0A> dirs=0A> >> exported via NFS.=0A> >> > clie= nt - FreeBSD 8.0-Release. =A0Running a=0A> test php=0A> >> script that copi= es around various files to/from 2=0A> separate=0A> >> NFS mounts.=0A> >> >= =0A> >> > Situation:=0A> >> >=0A> >> > script is started (forked to do 20= =0A> simultaneous runs)=0A> >> and 20 1GB files are copied to the NFS dir w= hich=0A> works=0A> >> fine.=A0 When it then switches to reading those=0A> f= iles back=0A> >> and simultaneously writing to the other NFS mount=0A> I se= e a=0A> >> hang of 75 seconds.=A0 If I do an "ls -l" on the=0A> NFS mount i= t=0A> >> hangs too.=A0 After 75 seconds the client has=0A> reported:=0A> >>= >=0A> >> > nfs server 192.168.10.133:/usr/local/export1:=0A> not=0A> >> re= sponding=0A> >> > nfs server 192.168.10.133:/usr/local/export1:=0A> is aliv= e=0A> >> again=0A> >> > nfs server 192.168.10.133:/usr/local/export1:=0A> n= ot=0A> >> responding=0A> >> > nfs server 192.168.10.133:/usr/local/export1:= =0A> is alive=0A> >> again=0A> >> >=0A> >> > and then things start working = again.=A0 The=0A> server was=0A> >> originally FreeBSD 8.0-Release also but= was=0A> upgraded to the=0A> >> latest stable to see if this issue could be= =0A> avoided.=0A> >> >=0A> >> > # nfsstat -s -W -w 1=0A> >> > =A0GtAttr Loo= kup Rdlink=A0=A0=A0Read=A0 Write=0A> Rename=0A> >> Access=A0 Rddir=0A> >> >= =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 222=A0 =A0=0A> 257=0A> >> = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 178=A0 =A0=0A> 135=0A> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> = >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=A0=A085=A0=0A> =A0 127= =0A> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> > =A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0 =A0 0=0A> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> > = =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0=0A> >= > =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0 =A0 0=0A> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0= =A0 =A0=0A> =A0 0=0A> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >=0A> >= > > ... for 75 rows of all zeros=0A> >> >=0A> >> > =A0 =A0 =A0 0=A0 =A0 =A0= 0=A0 =A0 =A0 0=A0 =A0 272=A0 =A0=0A> 266=0A> >> =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=0A> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167=A0 =A0=0A= > 165=0A> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >=0A> >> > I also tried= runs with 15 simultaneous=0A> processes and=0A> >> 25. =A015 processes gav= e only about a 5 second=0A> stall but 25=0A> >> gave again the same 75 seco= nd stall.=0A> >> >=0A> >> > Further, I tested with 2 mounts to the same=0A>= server but=0A> >> from ZFS filesytems with the exact same=0A> stall/timeou= t=0A> >> periods. =A0So, it doesn't appear to matter what=0A> the=0A> >> un= derlying filesystem is - it's something in NFS=0A> or=0A> >> networking cod= e.=0A> >> >=0A> >> > Any ideas on what's going on here? =A0What's=0A> causi= ng=0A> >> the complete stall period of zero NFS activity? =A0=0A> Any flaws= =0A> >> with my testing methods?=0A> >> >=0A> >> > Thanks for any and all h= elp/ideas.=0A> >>=0A> >> What network driver are you using? Have you tried= =0A> >> tcpdumping the packets?=0A> >> -Garrett=0A> >>=0A> >=0A> > I'm usin= g igb currently but have also used em. =A0I=0A> have not tried tcpdumping t= he packets yet on this test.=0A> =A0Any suggestions on things to look out f= or (I'm not that=0A> familiar with that whole process).=0A> >=0A> > Which b= rings up another point - I'm using TCP=0A> connections for NFS, not UDP.=0A= > =0A> =A0 =A0 Is the net.inet.tcp.tso sysctl enabled or=0A> not? What abou= t rxcsum and txcsum?=0A> Thanks,=0A> -Garrett=0A> =0A=0AI haven't intention= ally/explicitly set any of this so it's "default":=0A=0A# sysctl net.inet.t= cp.tso=0Anet.inet.tcp.tso: 1=0A=0A=0Aigb0: flags=3D8843 metric 0 mtu 1500=0A=09options=3D13b=0A=09ether 00:30:48:c3:26:94=0A=09inet= 192.168.10.133 netmask 0xffffff00 broadcast 192.168.10.255=0A=09media: Eth= ernet autoselect (1000baseT )=0A=09status: active=0A=0AThanks,= =0AAlan=0A=0A=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 20:28:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B3CA106566C for ; Thu, 1 Jul 2010 20:28:57 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0FEA08FC18 for ; Thu, 1 Jul 2010 20:28:56 +0000 (UTC) Received: by vws6 with SMTP id 6so2088865vws.13 for ; Thu, 01 Jul 2010 13:28:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=H+f+sC5m/gWPX7sbFrDUCndypgXfvklTUtiEv7v0qbQ=; b=L64HVx1eVW/nPDIRR1Kw/zecAiB5cLGvJWjIU2wSaq6+kNbxylm2V2kmmG31ua4O8V 6kgV3h1xGXX2bkWwC1rOUybO8HGp0OwzW8DhR+XKha8fkeumMY/v+F9YvAM+Qezl0crx uG0/ptVbDqWnxvShO0Gk3yhwl7YBh5mUCLvc4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=A0XwI+Ah2l6j3ZAJhRtXG4DoZW3PSvwA6VHHsGY0mmAQHKr2WLRcnYqy9KRUuo+PGM FQD9B5bF+CU18aYrCG3hNTZph+xCh/IIwpfhvJpeoIrYzpBtAkZcdxu9mvlLo5Zlad9p jUxDUDZHFFYb5hOtJgqldd6NgPMUnhr9HUiAM= MIME-Version: 1.0 Received: by 10.229.96.19 with SMTP id f19mr36867qcn.43.1278016133374; Thu, 01 Jul 2010 13:28:53 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 13:28:53 -0700 (PDT) In-Reply-To: <604345.41122.qm@web50504.mail.re2.yahoo.com> References: <604345.41122.qm@web50504.mail.re2.yahoo.com> Date: Thu, 1 Jul 2010 13:28:53 -0700 Message-ID: From: Garrett Cooper To: alan bryan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 20:28:57 -0000 On Thu, Jul 1, 2010 at 1:18 PM, alan bryan wrote: > > > --- On Thu, 7/1/10, Garrett Cooper wrote: > >> From: Garrett Cooper >> Subject: Re: NFS 75 second stall >> To: "alan bryan" >> Cc: freebsd-stable@freebsd.org >> Date: Thursday, July 1, 2010, 12:23 PM >> On Thu, Jul 1, 2010 at 11:51 AM, alan >> bryan >> wrote: >> > >> > >> > --- On Thu, 7/1/10, Garrett Cooper >> wrote: >> > >> >> From: Garrett Cooper >> >> Subject: Re: NFS 75 second stall >> >> To: "alan bryan" >> >> Cc: freebsd-stable@freebsd.org >> >> Date: Thursday, July 1, 2010, 11:13 AM >> >> On Thu, Jul 1, 2010 at 11:01 AM, alan >> >> bryan >> >> wrote: >> >> > Setup: >> >> > >> >> > server - FreeBSD 8-stable from today.=A0 2 UFS >> dirs >> >> exported via NFS. >> >> > client - FreeBSD 8.0-Release. =A0Running a >> test php >> >> script that copies around various files to/from 2 >> separate >> >> NFS mounts. >> >> > >> >> > Situation: >> >> > >> >> > script is started (forked to do 20 >> simultaneous runs) >> >> and 20 1GB files are copied to the NFS dir which >> works >> >> fine.=A0 When it then switches to reading those >> files back >> >> and simultaneously writing to the other NFS mount >> I see a >> >> hang of 75 seconds.=A0 If I do an "ls -l" on the >> NFS mount it >> >> hangs too.=A0 After 75 seconds the client has >> reported: >> >> > >> >> > nfs server 192.168.10.133:/usr/local/export1: >> not >> >> responding >> >> > nfs server 192.168.10.133:/usr/local/export1: >> is alive >> >> again >> >> > nfs server 192.168.10.133:/usr/local/export1: >> not >> >> responding >> >> > nfs server 192.168.10.133:/usr/local/export1: >> is alive >> >> again >> >> > >> >> > and then things start working again.=A0 The >> server was >> >> originally FreeBSD 8.0-Release also but was >> upgraded to the >> >> latest stable to see if this issue could be >> avoided. >> >> > >> >> > # nfsstat -s -W -w 1 >> >> > =A0GtAttr Lookup Rdlink=A0=A0=A0Read=A0 Write >> Rename >> >> Access=A0 Rddir >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 222 >> 257 >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 178 >> 135 >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=A0=A085 >> =A0 127 >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > >> >> > ... for 75 rows of all zeros >> >> > >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 272 >> 266 >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 167 >> 165 >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> > >> >> > I also tried runs with 15 simultaneous >> processes and >> >> 25. =A015 processes gave only about a 5 second >> stall but 25 >> >> gave again the same 75 second stall. >> >> > >> >> > Further, I tested with 2 mounts to the same >> server but >> >> from ZFS filesytems with the exact same >> stall/timeout >> >> periods. =A0So, it doesn't appear to matter what >> the >> >> underlying filesystem is - it's something in NFS >> or >> >> networking code. >> >> > >> >> > Any ideas on what's going on here? =A0What's >> causing >> >> the complete stall period of zero NFS activity? >> Any flaws >> >> with my testing methods? >> >> > >> >> > Thanks for any and all help/ideas. >> >> >> >> What network driver are you using? Have you tried >> >> tcpdumping the packets? >> >> -Garrett >> >> >> > >> > I'm using igb currently but have also used em. =A0I >> have not tried tcpdumping the packets yet on this test. >> =A0Any suggestions on things to look out for (I'm not that >> familiar with that whole process). >> > >> > Which brings up another point - I'm using TCP >> connections for NFS, not UDP. >> >> =A0 =A0 Is the net.inet.tcp.tso sysctl enabled or >> not? What about rxcsum and txcsum? >> Thanks, >> -Garrett >> > > I haven't intentionally/explicitly set any of this so it's "default": > > # sysctl net.inet.tcp.tso > net.inet.tcp.tso: 1 > > > igb0: flags=3D8843 metric 0 mtu 1= 500 > =A0 =A0 =A0 =A0options=3D13b > =A0 =A0 =A0 =A0ether 00:30:48:c3:26:94 > =A0 =A0 =A0 =A0inet 192.168.10.133 netmask 0xffffff00 broadcast 192.168.1= 0.255 > =A0 =A0 =A0 =A0media: Ethernet autoselect (1000baseT ) > =A0 =A0 =A0 =A0status: active Devise all of the available permutations that you need to use to test this out; there are a total of 3 variables, so 9 permutations, but you've already `tested one', so that makes the permutation count 8. Example: TXCSUM=3Doff, RXCSUM=3Don, TSO=3Don TXCSUM=3Don, RXCSUM=3Doff, TSO=3Don TXCSUM=3Don, RXCSUM=3Doff, TSO=3Doff ... Try executing the permutations on the client first, keeping the server constant, then make the client constant and make the server variable, and finally do both to the server and client. Be sure to take measurements for each permutation to ensure that things make functional sense. The reason why I'm suggesting this is that there were issues with em(4) [and igb(4) too I think since it uses common code], with various hardware offload bits on 8.0-RELEASE (IIRC disabling txcsum did the trick, but you may have to do more than that in order to get things to work). Here's a similar thread with a different driver: http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008264.html (just to illustrate the thought process used to determine the source of failure). Thanks, -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 20:36:17 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD31B106566B for ; Thu, 1 Jul 2010 20:36:17 +0000 (UTC) (envelope-from alan.bryan@yahoo.com) Received: from web50504.mail.re2.yahoo.com (web50504.mail.re2.yahoo.com [206.190.38.80]) by mx1.freebsd.org (Postfix) with SMTP id 65D108FC18 for ; Thu, 1 Jul 2010 20:36:17 +0000 (UTC) Received: (qmail 59876 invoked by uid 60001); 1 Jul 2010 20:36:13 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278016573; bh=gCZm7JPThb+MPmT117MUVVwiwwhlcMJJZx91HQfeWJg=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=T2g9BvIqExb/XTDwDALxTirgjEdIX6sG17hdN/5rl6zldQzXGR6SbnPof4uJatLfRM1UJYReZ5Petw/pfH1dM89rpxBLExZNGaum25q2n/AZcBOnp7tppLJMLFk66sLLI2AUJVTP0sUUz7J6BLyaGZ6j70T3ar46VxvuiWHsy2M= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=flRYZTe9zwCB92Ack8/MEDrNFMzfe36YZCtbsouBj8I4MGhiWrylPh7GOBooyGJ74V174yhXhpnomTDv/CchPh/4GdS5qFpUoYfSERWny/u8Sx7mO65XQhGq9k7byGa3BMHqSZjWAHmes3EnAF0pMTkqyI82r0UUXTMebvEMh0Y=; Message-ID: <119072.59868.qm@web50504.mail.re2.yahoo.com> X-YMail-OSG: 2VGIE7oVM1mmK_CVxnIidyNwvwljWwecYM5ZjH2FGuOQMnX IIkdCJEABWljFnxnN5x3zS5dwf2YZG6DdUK34AXcMHdN1FgpSdSAQnVSamQR yW9uIoJApEVVmjhKP42mzggW5sjB6rvc9Xd17hSSyZYHDvY80oRZjqJsAMeW 6psKIUCBMPzY3YcK83pzk6PQxTOWGDcD.CyLgdMU7gG2IuEsrvJueVEHiI2G .mEtugz9tNnOJNJFR87hviVnJHJgFcag73rVX6mEiYXj.LAk.TvOMpBLELmM O3rzhtyKwslhiUqKhA4R3AgTBspqbHYYH47ZoS2m_YVQO6LlxRyGd5km4YD7 V6Q-- Received: from [99.24.6.121] by web50504.mail.re2.yahoo.com via HTTP; Thu, 01 Jul 2010 13:36:12 PDT X-Mailer: YahooMailClassic/11.1.4 YahooMailWebService/0.8.104.274457 Date: Thu, 1 Jul 2010 13:36:12 -0700 (PDT) From: alan bryan To: Garrett Cooper In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 20:36:17 -0000 =0A=0A--- On Thu, 7/1/10, Garrett Cooper wrote:=0A=0A>= From: Garrett Cooper =0A> Subject: Re: NFS 75 second s= tall=0A> To: "alan bryan" =0A> Cc: freebsd-stable@fre= ebsd.org=0A> Date: Thursday, July 1, 2010, 1:28 PM=0A> On Thu, Jul 1, 2010 = at 1:18 PM, alan=0A> bryan =0A> wrote:=0A> >=0A> >=0A= > > --- On Thu, 7/1/10, Garrett Cooper =0A> wrote:=0A> = >=0A> >> From: Garrett Cooper =0A> >> Subject: Re: NFS = 75 second stall=0A> >> To: "alan bryan" =0A> >> Cc: f= reebsd-stable@freebsd.org=0A> >> Date: Thursday, July 1, 2010, 12:23 PM=0A>= >> On Thu, Jul 1, 2010 at 11:51 AM, alan=0A> >> bryan =0A> >> wrote:=0A> >> >=0A> >> >=0A> >> > --- On Thu, 7/1/10, Garrett Coo= per =0A> >> wrote:=0A> >> >=0A> >> >> From: Garrett Coo= per =0A> >> >> Subject: Re: NFS 75 second stall=0A> >> = >> To: "alan bryan" =0A> >> >> Cc: freebsd-stable@fre= ebsd.org=0A> >> >> Date: Thursday, July 1, 2010, 11:13 AM=0A> >> >> On Thu,= Jul 1, 2010 at 11:01 AM, alan=0A> >> >> bryan =0A> >= > >> wrote:=0A> >> >> > Setup:=0A> >> >> >=0A> >> >> > server - FreeBSD 8-s= table from=0A> today.=A0 2 UFS=0A> >> dirs=0A> >> >> exported via NFS.=0A> = >> >> > client - FreeBSD 8.0-Release.=0A> =A0Running a=0A> >> test php=0A> = >> >> script that copies around various files=0A> to/from 2=0A> >> separate= =0A> >> >> NFS mounts.=0A> >> >> >=0A> >> >> > Situation:=0A> >> >> >=0A> >= > >> > script is started (forked to do 20=0A> >> simultaneous runs)=0A> >> = >> and 20 1GB files are copied to the NFS=0A> dir which=0A> >> works=0A> >>= >> fine.=A0 When it then switches to reading=0A> those=0A> >> files back= =0A> >> >> and simultaneously writing to the other=0A> NFS mount=0A> >> I s= ee a=0A> >> >> hang of 75 seconds.=A0 If I do an "ls -l"=0A> on the=0A> >> = NFS mount it=0A> >> >> hangs too.=A0 After 75 seconds the client=0A> has=0A= > >> reported:=0A> >> >> >=0A> >> >> > nfs server=0A> 192.168.10.133:/usr/l= ocal/export1:=0A> >> not=0A> >> >> responding=0A> >> >> > nfs server=0A> 19= 2.168.10.133:/usr/local/export1:=0A> >> is alive=0A> >> >> again=0A> >> >> = > nfs server=0A> 192.168.10.133:/usr/local/export1:=0A> >> not=0A> >> >> re= sponding=0A> >> >> > nfs server=0A> 192.168.10.133:/usr/local/export1:=0A> = >> is alive=0A> >> >> again=0A> >> >> >=0A> >> >> > and then things start w= orking=0A> again.=A0 The=0A> >> server was=0A> >> >> originally FreeBSD 8.0= -Release also but=0A> was=0A> >> upgraded to the=0A> >> >> latest stable to= see if this issue could=0A> be=0A> >> avoided.=0A> >> >> >=0A> >> >> > # n= fsstat -s -W -w 1=0A> >> >> > =A0GtAttr Lookup Rdlink=A0=A0=A0Read=A0=0A> W= rite=0A> >> Rename=0A> >> >> Access=A0 Rddir=0A> >> >> > =A0 =A0 =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> 222=0A> >> 257=0A> >> >> =A0 0=A0 =A0 =A0= 0=A0 =A0 =A0 0=0A> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0= =0A> 178=0A> >> 135=0A> >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> > = =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0=0A> =A0=A0=A085=0A> >> =A0 127= =0A> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> > =A0 =A0 =A0 0=A0= =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 0=0A> >> >> =A0 =A0 0= =A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 = =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 0=0A> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0= =A0 0=0A> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0= =0A> >> =A0 0=0A> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> > =A0= =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 0=0A> >> >= > =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0=0A> =A0 0=0A> >> =A0 0=0A> >> >> =A0 =A0 0=A0 =A0 =A0= 0=A0 =A0 =A0 0=0A> >> >> >=0A> >> >> > ... for 75 rows of all zeros=0A> >>= >> >=0A> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> 272=0A= > >> 266=0A> >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> > =A0 =A0 =A0 = 0=A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0=0A> 167=0A> >> 165=0A> >> >> =A0 0=A0 = =A0 =A0 0=A0 =A0 =A0 0=0A> >> >> >=0A> >> >> > I also tried runs with 15=0A= > simultaneous=0A> >> processes and=0A> >> >> 25. =A015 processes gave only= about a 5=0A> second=0A> >> stall but 25=0A> >> >> gave again the same 75 = second stall.=0A> >> >> >=0A> >> >> > Further, I tested with 2 mounts to=0A= > the same=0A> >> server but=0A> >> >> from ZFS filesytems with the exact s= ame=0A> >> stall/timeout=0A> >> >> periods. =A0So, it doesn't appear to=0A>= matter what=0A> >> the=0A> >> >> underlying filesystem is - it's something= =0A> in NFS=0A> >> or=0A> >> >> networking code.=0A> >> >> >=0A> >> >> > An= y ideas on what's going on here?=0A> =A0What's=0A> >> causing=0A> >> >> the= complete stall period of zero NFS=0A> activity?=0A> >> Any flaws=0A> >> >>= with my testing methods?=0A> >> >> >=0A> >> >> > Thanks for any and all he= lp/ideas.=0A> >> >>=0A> >> >> What network driver are you using? Have=0A> y= ou tried=0A> >> >> tcpdumping the packets?=0A> >> >> -Garrett=0A> >> >>=0A>= >> >=0A> >> > I'm using igb currently but have also used=0A> em. =A0I=0A> = >> have not tried tcpdumping the packets yet on this=0A> test.=0A> >> =A0An= y suggestions on things to look out for (I'm=0A> not that=0A> >> familiar w= ith that whole process).=0A> >> >=0A> >> > Which brings up another point - = I'm using=0A> TCP=0A> >> connections for NFS, not UDP.=0A> >>=0A> >> =A0 = =A0 Is the net.inet.tcp.tso sysctl enabled or=0A> >> not? What about rxcsum= and txcsum?=0A> >> Thanks,=0A> >> -Garrett=0A> >>=0A> >=0A> > I haven't in= tentionally/explicitly set any of this so=0A> it's "default":=0A> >=0A> > #= sysctl net.inet.tcp.tso=0A> > net.inet.tcp.tso: 1=0A> >=0A> >=0A> > igb0:= =0A> flags=3D8843=0A> metric 0 mtu = 1500=0A> > =A0 =A0 =A0=0A> =A0options=3D13b=0A> > =A0 =A0 =A0 =A0ether 00:30:48:c3:26:94=0A> > = =A0 =A0 =A0 =A0inet 192.168.10.133 netmask 0xffffff00=0A> broadcast 192.168= .10.255=0A> > =A0 =A0 =A0 =A0media: Ethernet autoselect (1000baseT=0A> )=0A> > =A0 =A0 =A0 =A0status: active=0A> =0A> Devise all of the a= vailable permutations that you need to=0A> use to test=0A> this out; there = are a total of 3 variables, so 9=0A> permutations, but=0A> you've already `= tested one', so that makes the permutation=0A> count 8.=0A> Example:=0A> = =0A> TXCSUM=3Doff, RXCSUM=3Don, TSO=3Don=0A> TXCSUM=3Don, RXCSUM=3Doff, TSO= =3Don=0A> TXCSUM=3Don, RXCSUM=3Doff, TSO=3Doff=0A> =0A> ...=0A> =0A> Try ex= ecuting the permutations on the client first, keeping=0A> the server=0A> co= nstant, then make the client constant and make the server=0A> variable,=0A>= and finally do both to the server and client.=0A> =0A> Be sure to take mea= surements for each permutation to ensure=0A> that=0A> things make functiona= l sense.=0A> =0A> The reason why I'm suggesting this is that there were=0A>= issues with=0A> em(4) [and igb(4) too I think since it uses common code],= =0A> with various=0A> hardware offload bits on 8.0-RELEASE (IIRC disabling = txcsum=0A> did the=0A> trick, but you may have to do more than that in orde= r to=0A> get things to=0A> work).=0A> =0A> Here's a similar thread with a d= ifferent driver:=0A> http://lists.freebsd.org/pipermail/freebsd-current/200= 9-June/008264.html=0A> (just to illustrate the thought process used to dete= rmine=0A> the source=0A> of failure).=0A> =0A> Thanks,=0A> -Garrett=0A> =0A= =0AThanks for the detailed test plan!=0A=0AIs it also fair to then assume t= hat if I update the NFS client machine to the latest 8-Stable that should a= lso fix this issue? (Both will then be running the latest 8-stable code). = These are not in production so I can test or upgrade with no issues.=0A=0A= Thanks again.=0A--Alan=0A=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 20:53:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91D00106566C for ; Thu, 1 Jul 2010 20:53:52 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 79F678FC0A for ; Thu, 1 Jul 2010 20:53:52 +0000 (UTC) Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta10.emeryville.ca.mail.comcast.net with comcast id cdFm1e0021smiN4AAktsjp; Thu, 01 Jul 2010 20:53:52 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta20.emeryville.ca.mail.comcast.net with comcast id cktr1e0043S48mS8gktraR; Thu, 01 Jul 2010 20:53:51 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 093609B425; Thu, 1 Jul 2010 13:53:51 -0700 (PDT) Date: Thu, 1 Jul 2010 13:53:50 -0700 From: Jeremy Chadwick To: alan bryan Message-ID: <20100701205350.GA6690@icarus.home.lan> References: <425902.41392.qm@web50501.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <425902.41392.qm@web50501.mail.re2.yahoo.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 20:53:52 -0000 On Thu, Jul 01, 2010 at 11:01:04AM -0700, alan bryan wrote: > Setup: > > server - FreeBSD 8-stable from today.  2 UFS dirs exported via NFS. > client - FreeBSD 8.0-Release. Running a test php script that copies around various files to/from 2 separate NFS mounts. > > Situation: > > script is started (forked to do 20 simultaneous runs) and 20 1GB files are copied to the NFS dir which works fine.  When it then switches to reading those files back and simultaneously writing to the other NFS mount I see a hang of 75 seconds.  If I do an "ls -l" on the NFS mount it hangs too.  After 75 seconds the client has reported: > > nfs server 192.168.10.133:/usr/local/export1: not responding > nfs server 192.168.10.133:/usr/local/export1: is alive again > nfs server 192.168.10.133:/usr/local/export1: not responding > nfs server 192.168.10.133:/usr/local/export1: is alive again > > and then things start working again.  The server was originally FreeBSD 8.0-Release also but was upgraded to the latest stable to see if this issue could be avoided. > > ... > > Any ideas on what's going on here? What's causing the complete stall period of zero NFS activity? Any flaws with my testing methods? One thing worth asking: are there any firewall stacks (ipfw, ipfilter, or pf) in use on either the client or server? -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Thu Jul 1 20:59:58 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 379B31065672 for ; Thu, 1 Jul 2010 20:59:58 +0000 (UTC) (envelope-from alan.bryan@yahoo.com) Received: from web50506.mail.re2.yahoo.com (web50506.mail.re2.yahoo.com [206.190.38.82]) by mx1.freebsd.org (Postfix) with SMTP id E70DD8FC0A for ; Thu, 1 Jul 2010 20:59:57 +0000 (UTC) Received: (qmail 90146 invoked by uid 60001); 1 Jul 2010 20:59:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1278017997; bh=EoXu7sWwwjt4tPh323qpVYPF2BJviGxtMPN9D11+n/8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LfpbgLTu7AJf3K1Ag8Vx7eBProC9xKg55JSax4PHebr6c1e1qZN6a/K+W91NyAFvphZDk9nH7F7GSMKD26H3LAO2IP9qSP7U6ed0PeqL7B7ssV1ld8hpsz3Ll5lDXi7nPrZMoZE7lCEXzGm9NvLpFLswzmyB/mW5GfZIkIG810Y= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=TlL4CuDuCn9iC7xBBsMz84CFQEVtWkbnpsp19fNjow/vQVZ0M/tEUbhSP0k7qyRrsrevs2eiAChZLPVoyjwBz3dNnfsu0ZDlXVUQmIRlQm0t7YL4A5Spv4wu1rW7k2siUDgm3fY59C0sOb96L9gXI4q5wN9jbdZNVNHBjEx+sHk=; Message-ID: <173056.89627.qm@web50506.mail.re2.yahoo.com> X-YMail-OSG: M6FVTvAVM1md85BhBL8Wiyy5WG0DAMc1B6mi9HvnittqLcu i7tyW6y1ZCOxR0n3.JSaiIK93VOQqNicUL2tB7qfSgGczq2OWAoXpoICOPbe KzIWY3l0a.k3vQs55WReN.zyiykaLI2LESiKa8TVwcI12kDjP1EOA40xUz86 axJpXZdcJyP5e3AeuuO0ziY_jhOebys1Aed9NAMWqP10h5LFst2Z67LjDOUz 12l95Z4BUvQaB949Hp9_aPNO.flyqtG98zrWxElw0Vq3kU5WKgYPNJzDoCDT 7ES0D18tD5idxWhEkxyeNEOAPh1425eExle.snPQdIDhPAOIsQzTDtmRrQkg MfQ-- Received: from [99.24.6.121] by web50506.mail.re2.yahoo.com via HTTP; Thu, 01 Jul 2010 13:59:57 PDT X-Mailer: YahooMailClassic/11.1.4 YahooMailWebService/0.8.104.274457 Date: Thu, 1 Jul 2010 13:59:57 -0700 (PDT) From: alan bryan To: Jeremy Chadwick In-Reply-To: <20100701205350.GA6690@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 20:59:58 -0000 =0A=0A--- On Thu, 7/1/10, Jeremy Chadwick wrote:= =0A=0A> From: Jeremy Chadwick =0A> Subject: Re: N= FS 75 second stall=0A> To: "alan bryan" =0A> Cc: free= bsd-stable@freebsd.org=0A> Date: Thursday, July 1, 2010, 1:53 PM=0A> On Thu= , Jul 01, 2010 at 11:01:04AM=0A> -0700, alan bryan wrote:=0A> > Setup:=0A> = > =0A> > server - FreeBSD 8-stable from today.=A0 2 UFS dirs=0A> exported v= ia NFS.=0A> > client - FreeBSD 8.0-Release.=A0 Running a test php=0A> scrip= t that copies around various files to/from 2 separate=0A> NFS mounts.=0A> >= =0A> > Situation: =0A> > =0A> > script is started (forked to do 20 simulta= neous runs)=0A> and 20 1GB files are copied to the NFS dir which works=0A> = fine.=A0 When it then switches to reading those files back=0A> and simultan= eously writing to the other NFS mount I see a=0A> hang of 75 seconds.=A0 If= I do an "ls -l" on the NFS mount it=0A> hangs too.=A0 After 75 seconds the= client has reported:=0A> > =0A> > nfs server 192.168.10.133:/usr/local/exp= ort1: not=0A> responding=0A> > nfs server 192.168.10.133:/usr/local/export1= : is alive=0A> again=0A> > nfs server 192.168.10.133:/usr/local/export1: no= t=0A> responding=0A> > nfs server 192.168.10.133:/usr/local/export1: is ali= ve=0A> again =0A> > =0A> > and then things start working again.=A0 The serv= er was=0A> originally FreeBSD 8.0-Release also but was upgraded to the=0A> = latest stable to see if this issue could be avoided.=0A> >=0A> > ...=0A> > = =0A> > Any ideas on what's going on here?=A0 What's=0A> causing the complet= e stall period of zero NFS=0A> activity?=A0=A0=A0Any flaws with my testing= =0A> methods?=0A> =0A> One thing worth asking: are there any firewall stack= s=0A> (ipfw, ipfilter,=0A> or pf) in use on either the client or server?=0A= > =0A> -- =0A> | Jeremy Chadwick=A0 =A0 =A0 =A0 =A0 =A0=0A> =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0=0A> =A0 =A0 =A0=A0=A0jdc@parodius.com=0A> |=0A> | Parodius= Networking=A0 =A0 =A0 =A0 =A0=0A> =A0 =A0 =A0 =A0 =A0 =A0=A0=A0http://www.= parodius.com/ |=0A> | UNIX Systems Administrator=A0 =A0 =A0 =A0=0A> =A0 =A0= =A0 =A0 =A0 Mountain View, CA, USA |=0A> | Making life hard for others sin= ce 1977.=A0 =A0=0A> =A0 =A0 =A0 =A0 =A0 PGP: 4BD6C0CB |=0A> =0A> =0A=0A=0AN= ope, no firewalls - just 2 machines connected directly to a Dell 2716 Gbit = switch.=0A=0AThanks,=0AAlan=0A=0A=0A=0A From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 21:12:57 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3CEE106566C for ; Thu, 1 Jul 2010 21:12:57 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 94F518FC13 for ; Thu, 1 Jul 2010 21:12:57 +0000 (UTC) Received: by gwb1 with SMTP id 1so738000gwb.13 for ; Thu, 01 Jul 2010 14:12:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xGI/owDW1VsVZSD5P3ND09gRhXQsqYjObGVeoyLDb8U=; b=Zj3XlNMYGSH19zojv0VovJi7xSaY3Z5W8E2eqLHThmcSguLS3lsBiLdE4v5geUGBr1 cA7OqcFblsv5NFm+a7z66C40aZ6mXd9HINbG7zhV68EcKCHR8LJGez56ZpsxOY3Ib6fz tkeIUAf5xsiaMn5LbHZaQVQl9sec0XHwlUJJk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VAXA71bEUSj9+zYns1N46MX4ndZFx2aDqsZoAEI6Kp2jxtvf1W9vAfhOUZm1jZnkTx ty8ELddknVUne93LP059kGMcMaTYFk7Bd2UiNwkUX6kHE6CGdUbHg4l74Ap/quZ+NEx8 fzFlo7gjAoXhF3FRgyYxBzUIQnxFeoGZDNqO0= MIME-Version: 1.0 Received: by 10.229.185.2 with SMTP id cm2mr82880qcb.47.1278018773031; Thu, 01 Jul 2010 14:12:53 -0700 (PDT) Received: by 10.229.221.83 with HTTP; Thu, 1 Jul 2010 14:12:52 -0700 (PDT) In-Reply-To: <119072.59868.qm@web50504.mail.re2.yahoo.com> References: <119072.59868.qm@web50504.mail.re2.yahoo.com> Date: Thu, 1 Jul 2010 14:12:52 -0700 Message-ID: From: Garrett Cooper To: alan bryan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: NFS 75 second stall X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 21:12:58 -0000 On Thu, Jul 1, 2010 at 1:36 PM, alan bryan wrote: > > > --- On Thu, 7/1/10, Garrett Cooper wrote: > >> From: Garrett Cooper >> Subject: Re: NFS 75 second stall >> To: "alan bryan" >> Cc: freebsd-stable@freebsd.org >> Date: Thursday, July 1, 2010, 1:28 PM >> On Thu, Jul 1, 2010 at 1:18 PM, alan >> bryan >> wrote: >> > >> > >> > --- On Thu, 7/1/10, Garrett Cooper >> wrote: >> > >> >> From: Garrett Cooper >> >> Subject: Re: NFS 75 second stall >> >> To: "alan bryan" >> >> Cc: freebsd-stable@freebsd.org >> >> Date: Thursday, July 1, 2010, 12:23 PM >> >> On Thu, Jul 1, 2010 at 11:51 AM, alan >> >> bryan >> >> wrote: >> >> > >> >> > >> >> > --- On Thu, 7/1/10, Garrett Cooper >> >> wrote: >> >> > >> >> >> From: Garrett Cooper >> >> >> Subject: Re: NFS 75 second stall >> >> >> To: "alan bryan" >> >> >> Cc: freebsd-stable@freebsd.org >> >> >> Date: Thursday, July 1, 2010, 11:13 AM >> >> >> On Thu, Jul 1, 2010 at 11:01 AM, alan >> >> >> bryan >> >> >> wrote: >> >> >> > Setup: >> >> >> > >> >> >> > server - FreeBSD 8-stable from >> today.=A0 2 UFS >> >> dirs >> >> >> exported via NFS. >> >> >> > client - FreeBSD 8.0-Release. >> =A0Running a >> >> test php >> >> >> script that copies around various files >> to/from 2 >> >> separate >> >> >> NFS mounts. >> >> >> > >> >> >> > Situation: >> >> >> > >> >> >> > script is started (forked to do 20 >> >> simultaneous runs) >> >> >> and 20 1GB files are copied to the NFS >> dir which >> >> works >> >> >> fine.=A0 When it then switches to reading >> those >> >> files back >> >> >> and simultaneously writing to the other >> NFS mount >> >> I see a >> >> >> hang of 75 seconds.=A0 If I do an "ls -l" >> on the >> >> NFS mount it >> >> >> hangs too.=A0 After 75 seconds the client >> has >> >> reported: >> >> >> > >> >> >> > nfs server >> 192.168.10.133:/usr/local/export1: >> >> not >> >> >> responding >> >> >> > nfs server >> 192.168.10.133:/usr/local/export1: >> >> is alive >> >> >> again >> >> >> > nfs server >> 192.168.10.133:/usr/local/export1: >> >> not >> >> >> responding >> >> >> > nfs server >> 192.168.10.133:/usr/local/export1: >> >> is alive >> >> >> again >> >> >> > >> >> >> > and then things start working >> again.=A0 The >> >> server was >> >> >> originally FreeBSD 8.0-Release also but >> was >> >> upgraded to the >> >> >> latest stable to see if this issue could >> be >> >> avoided. >> >> >> > >> >> >> > # nfsstat -s -W -w 1 >> >> >> > =A0GtAttr Lookup Rdlink=A0=A0=A0Read >> Write >> >> Rename >> >> >> Access=A0 Rddir >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> 222 >> >> 257 >> >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> 178 >> >> 135 >> >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0=A0=A085 >> >> =A0 127 >> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 0 >> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 0 >> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 0 >> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 0 >> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> =A0 0 >> >> =A0 0 >> >> >> =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > >> >> >> > ... for 75 rows of all zeros >> >> >> > >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> 272 >> >> 266 >> >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > =A0 =A0 =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> 167 >> >> 165 >> >> >> =A0 0=A0 =A0 =A0 0=A0 =A0 =A0 0 >> >> >> > >> >> >> > I also tried runs with 15 >> simultaneous >> >> processes and >> >> >> 25. =A015 processes gave only about a 5 >> second >> >> stall but 25 >> >> >> gave again the same 75 second stall. >> >> >> > >> >> >> > Further, I tested with 2 mounts to >> the same >> >> server but >> >> >> from ZFS filesytems with the exact same >> >> stall/timeout >> >> >> periods. =A0So, it doesn't appear to >> matter what >> >> the >> >> >> underlying filesystem is - it's something >> in NFS >> >> or >> >> >> networking code. >> >> >> > >> >> >> > Any ideas on what's going on here? >> =A0What's >> >> causing >> >> >> the complete stall period of zero NFS >> activity? >> >> Any flaws >> >> >> with my testing methods? >> >> >> > >> >> >> > Thanks for any and all help/ideas. >> >> >> >> >> >> What network driver are you using? Have >> you tried >> >> >> tcpdumping the packets? >> >> >> -Garrett >> >> >> >> >> > >> >> > I'm using igb currently but have also used >> em. =A0I >> >> have not tried tcpdumping the packets yet on this >> test. >> >> =A0Any suggestions on things to look out for (I'm >> not that >> >> familiar with that whole process). >> >> > >> >> > Which brings up another point - I'm using >> TCP >> >> connections for NFS, not UDP. >> >> >> >> =A0 =A0 Is the net.inet.tcp.tso sysctl enabled or >> >> not? What about rxcsum and txcsum? >> >> Thanks, >> >> -Garrett >> >> >> > >> > I haven't intentionally/explicitly set any of this so >> it's "default": >> > >> > # sysctl net.inet.tcp.tso >> > net.inet.tcp.tso: 1 >> > >> > >> > igb0: >> flags=3D8843 >> metric 0 mtu 1500 >> > >> =A0options=3D13b >> > =A0 =A0 =A0 =A0ether 00:30:48:c3:26:94 >> > =A0 =A0 =A0 =A0inet 192.168.10.133 netmask 0xffffff00 >> broadcast 192.168.10.255 >> > =A0 =A0 =A0 =A0media: Ethernet autoselect (1000baseT >> ) >> > =A0 =A0 =A0 =A0status: active >> >> Devise all of the available permutations that you need to >> use to test >> this out; there are a total of 3 variables, so 9 >> permutations, but >> you've already `tested one', so that makes the permutation >> count 8. >> Example: >> >> TXCSUM=3Doff, RXCSUM=3Don, TSO=3Don >> TXCSUM=3Don, RXCSUM=3Doff, TSO=3Don >> TXCSUM=3Don, RXCSUM=3Doff, TSO=3Doff >> >> ... >> >> Try executing the permutations on the client first, keeping >> the server >> constant, then make the client constant and make the server >> variable, >> and finally do both to the server and client. >> >> Be sure to take measurements for each permutation to ensure >> that >> things make functional sense. >> >> The reason why I'm suggesting this is that there were >> issues with >> em(4) [and igb(4) too I think since it uses common code], >> with various >> hardware offload bits on 8.0-RELEASE (IIRC disabling txcsum >> did the >> trick, but you may have to do more than that in order to >> get things to >> work). >> >> Here's a similar thread with a different driver: >> http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008264.html >> (just to illustrate the thought process used to determine >> the source >> of failure). > > Thanks for the detailed test plan! Np ;).. > Is it also fair to then assume that if I update the NFS client machine to= the latest 8-Stable that should also fix this issue? =A0(Both will then be= running the latest 8-stable code). =A0These are not in production so I can= test or upgrade with no issues. You can try that, but it would be better to determine (with minimal effort) that disabling one of the features is the root cause; after that you can upgrade to a later version if you want and see whether or not there's an issue with the stack (there's been some churn with em(4) cards though so I'd avoid doing that unless you're willing to live with soaking things in a bit more on the 8.0-RELEASE machine side). FWIW I've seen whacky ass problems with TSO on and ipfw on my Dell 2950 (uses bce(4)) so I've disabled it for the time being... Cheers, -Garrett From owner-freebsd-stable@FreeBSD.ORG Thu Jul 1 22:16:34 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 1364E1065675 for ; Thu, 1 Jul 2010 22:16:34 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from xps.daemonology.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx2.freebsd.org (Postfix) with SMTP id 3F02F14DFF6 for ; Thu, 1 Jul 2010 22:16:33 +0000 (UTC) Received: (qmail 17397 invoked from network); 1 Jul 2010 22:16:32 -0000 Received: from unknown (HELO xps.daemonology.net) (127.0.0.1) by localhost with SMTP; 1 Jul 2010 22:16:32 -0000 Message-ID: <4C2D13C0.2010300@freebsd.org> Date: Thu, 01 Jul 2010 15:16:32 -0700 From: FreeBSD Security Officer Organization: FreeBSD Project User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.10) Gecko/20100627 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd security , FreeBSD Stable X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: FreeBSD supported branches update X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: security-officer@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jul 2010 22:16:34 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect the EoL (end-of-life) of FreeBSD 7.2. The new list is below and at . Users of FreeBSD 7.2 are advised to upgrade promptly to a newer release, either by downloading an updated source tree and building updates manually, or (for i386 and amd64 systems) using the FreeBSD Update utility as described in the relevant release announcement. [Excerpt from http://security.freebsd.org/ follows] Supported FreeBSD Releases The FreeBSD Security Officer provides security advisories for several branches of FreeBSD development. These are the -STABLE Branches and the Security Branches. (Advisories are not issued for the -CURRENT Branch.) * The -STABLE branch tags have names like RELENG_7. The corresponding builds have names like FreeBSD 7.0-STABLE. * Each FreeBSD Release has an associated Security Branch. The Security Branch tags have names like RELENG_7_0. The corresponding builds have names like FreeBSD 7.0-RELEASE-p1. Isses affecting the FreeBSD Ports Collection are covered in the FreeBSD VuXML document. Each branch is supported by the Security Officer for a limited time only, and is designated as one of `Early adopter', `Normal', or `Extended'. The designation is used as a guideline for determining the lifetime of the branch as follows. Early adopter Releases which are published from the -CURRENT branch will be supported by the Security Officer for a minimum of 6 months after the release. Normal Releases which are published from a -STABLE branch will be supported by the Security Officer for a minimum of 12 months after the release, and for sufficient additional time (if needed) to ensure that there is a newer release for at least 3 months before the older Normal release expires. Extended Selected releases (normally every second release plus the last release from each -STABLE branch) will be supported by the Security Officer for a minimum of 24 months after the release, and for sufficient additional time (if needed) to ensure that there is a newer Extended release for at least 3 months before the older Extended release expires. The current designation and estimated lifetimes of the currently supported branches are given below. The Estimated EoL (end-of-life) column gives the earliest date on which that branch is likely to be dropped. Please note that these dates may be extended into the future, but only extenuating circumstances would lead to a branch's support being dropped earlier than the date listed. +--------------------------------------------------------------------+ | Branch | Release | Type | Release date | Estimated EoL | |-----------+-----------+--------+-----------------+-----------------| |RELENG_6 |n/a |n/a |n/a |November 30, 2010| |-----------+-----------+--------+-----------------+-----------------| |RELENG_6_4 |6.4-RELEASE|Extended|November 28, 2008|November 30, 2010| |-----------+-----------+--------+-----------------+-----------------| |RELENG_7 |n/a |n/a |n/a |last release + 2y| |-----------+-----------+--------+-----------------+-----------------| |RELENG_7_1 |7.1-RELEASE|Extended|January 4, 2009 |January 31, 2011 | |-----------+-----------+--------+-----------------+-----------------| |RELENG_7_3 |7.3-RELEASE|Extended|March 23, 2010 |March 31, 2012 | |-----------+-----------+--------+-----------------+-----------------| |RELENG_8 |n/a |n/a |n/a |last release + 2y| |-----------+-----------+--------+-----------------+-----------------| |RELENG_8_0 |8.0-RELEASE|Normal |November 25, 2009|November 30, 2010| |-----------+-----------+--------+-----------------+-----------------| |RELENG_8_1 |8.1-RELEASE|Extended|not yet |release + 2 years| +--------------------------------------------------------------------+ [End excerpt] - -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkwtE8AACgkQFdaIBMps37JJMQCfbEbvHes9mBz/h56y7TuzpeJf uOEAn0Gyh7HN0x/rcOsuCCq05tAyPkHT =qksg -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 14:00:52 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54A2A106564A for ; Fri, 2 Jul 2010 14:00:52 +0000 (UTC) (envelope-from bounce2@edt02.net) Received: from mailflip51.edt02.net (mailflip51.edt02.net [83.136.208.79]) by mx1.freebsd.org (Postfix) with ESMTP id AAD408FC17 for ; Fri, 2 Jul 2010 14:00:51 +0000 (UTC) Received: from mailflip51.edt02.net (unknown [192.168.20.72]) by mailflip51.edt02.net (Postfix) with SMTP id 3C92541D49E for ; Fri, 2 Jul 2010 15:01:17 +0200 (CEST) From: "SERVICE COMMERCIAL" To: stable@freebsd.org X-EDATIS-ID: 17289/134639/789777/613736/0/3-0--0-0-0-0-2284 Content-Transfer-Encoding: quoted-printable Message-Id: <20100702130118.3C92541D49E@mailflip51.edt02.net> Date: Fri, 2 Jul 2010 15:01:17 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: ACTIVITE ETRADUP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: SERVICE COMMERCIAL List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 14:00:52 -0000 3D"" FOR SA= LES IN STOCK - AVAILABLE TODAY 2 SUNFIRE 15K COMPLETE 150 x SUN USB MOUSE USED 150 x SUN QWERTY USB KEYBOARD 2x LICENCES N199-919-99A9 SUN SANTRICITY 9.19= 1 x SUN RACK 900-38 with complete Rohs PSU perfect= condition. 2 x COMPLETE SG-XSWBR0200E-8P-Z BROCADE SW200E wit= h rackmount 2x SUN FIRE V890 A53-JNG4C216GTF&nbs= p; 4x 1.35 Ghz CPU ULTRASPARC V 16 x 501-7385-01&nb= sp; 512MB 232p PC133 18c 16x16 Registered ECC SDRAM DIMM Sun Systems A53= -JNG4C216GTF Sun Fire V890 Server 4 * 1.35GHz UltraSPARC IV = pro Sun Fire V890 Server 4 * 1.35GHz UltraSPARC IV processors with 16MB 6x SUN 54= 0-5459-01 146.0GB Hard Drive FC (540-5459-01) SUN 146GB 3.5T= H 10K RPM FC HDD W/SLED= 2x 375-3354-01 SUN 4GB Single P= ort Fibre PCI-X SUN 2x 501-6635-06<= /span> · DUAL GIGABITETHERNET / DUAL SCSI = PCI A 1x 501-6767-03<= /span>, SUN, SUN ALOM + (Plus) Card V490/890 (PK= 1D/1-B22-1C)DAPTER 2x SUNFIRE X4100 AMD OSY285FAA6CB DUAL-CORE OPTE= RON 285 SE 2.6GHZ 2MB L2 CACHE SOCKET-940PIN PROCESSOR Redudant PSU, 4 Ethernet gigabit.<= span style=3D"color: black;"> 1x 2GB FC Dual Chan= nel HBA PCI-X 66-133MHZ FC5010409-04 2x SUN 390-0213= -04-BGP 73.0GB Hard Drive SAS (0556) SUN 73GB 2.5 SAS 10K HDD<= span lang=3D"EN-US" style=3D"color: black;"> 1x SUNFIRE X4100 AMD OPTERON 248E 2.2GHZR Redudant PSU, 4 Ethernet gigabit.<= span style=3D"color: black;"> 2x SUN 390-0213= -04-BGP 73.0GB Hard Drive SAS (0556) SUN 73GB 2.5 SAS 10K HDD<= span lang=3D"EN-US" style=3D"color: black;"> 1 SUN FIRE 25 K - 4 rack = 1 RACK 900-38 = 8 STOREDGE S1 2x72 gb UW 1= 60 10k/rpm 3 STOREDGE 3120 JBOD 4 x 146 gb = uw320 15k/rpm 594-1908-01 8 STOREDGE S1 2x72 gb UW 1= 60 10k/rpm 4 STOREDGE 3120 JBOD 4 x 146 gb = uw320 10k/rpm 1 UltraSPARC IV CPU/Memo= ry board 4 x 1.05GHz 540-5664-07= 5 CPU/Memory Uniboard w/ 4×= ; US IV 1.05GHz, 16GB 540-5602-03 2 CPU/Memory board w/ 4 × = US IV 1.05GHz,0GB 540-5664-04 1 SYSTEM CONTROL BOARD CP2140-65= 0 501-6772 8 X4422A Dual Gigabit Ethe= rnet / Dual SCSI PCI Adapter 501-6635 13 X1034A Quad Fast Ethernet PCI (QFE/= P) 501-5406 1 DVD drive 390-0161= 1 DDS4 tape 390-0027= 1 UltraSPARC IV CPU/Memo= ry board 4 x 1.05GHz 540-5664-07= 7 CPU/Memory Uniboard w/ 4×= ; US IV 1.05GHz, 16GB 540-5662-05 1 CPU/Memory board w/ 4 × = US IV 1.05GHz,0GB 540-5664-04 1 SYSTEM CONTROL BOARD CP2140-65= 0 501-6772 8 SUN STOREDGE CONTROLER A= V950-00475 1 DVD drive 390-0161= 1 DAT72 Tape 380-1324= Pour ne plus recevoir des messages de ETRADUP, [1]suive= z ce lien. = References 1. 3D"http://ho=/ From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 14:38:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF80D1065743 for ; Fri, 2 Jul 2010 14:38:33 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailC.acsu.buffalo.edu (localmailC.acsu.buffalo.edu [128.205.5.204]) by mx1.freebsd.org (Postfix) with ESMTP id 828F18FC1B for ; Fri, 2 Jul 2010 14:38:33 +0000 (UTC) Received: from localmailC.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 482B254D05 for ; Fri, 2 Jul 2010 10:38:27 -0400 (EDT) Received: from localmailC.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailC.acsu.buffalo.edu (Postfix) with ESMTP id D71EC54D26 for ; Fri, 2 Jul 2010 10:38:25 -0400 (EDT) Received: from mweb2.acsu.buffalo.edu (mweb2.acsu.buffalo.edu [128.205.5.239]) by localmailC.acsu.buffalo.edu (Prefixe) with ESMTP id D21DC54C73 for ; Fri, 2 Jul 2010 10:38:25 -0400 (EDT) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) by mweb2.acsu.buffalo.edu (Postfix) with ESMTP id 9B76C207BD for ; Fri, 2 Jul 2010 10:38:25 -0400 (EDT) From: Ken Smith To: freebsd-stable Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-/PRJEpA8KcWjT2hXf0ML" Date: Fri, 02 Jul 2010 10:38:24 -0400 Message-ID: <1278081504.83414.26.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port X-PM-EL-Spam-Prob: : 8% Subject: FreeBSD 8.1-RC2 Available... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 14:38:33 -0000 --=-/PRJEpA8KcWjT2hXf0ML Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The second and most likely final Release Candidate for the FreeBSD 8.1 release cycle is now available for amd64, i386, ia64, powerpc, and sparc64 architectures. Files suitable for creating installation media or doing FTP based installs through the network should be available on most of the FreeBSD mirror sites. Checksums for the images are at the bottom of this message. There was a recent regression fix related to Atheros AR9280 cards being detected incorrectly, making them unusable. If you were having problems with a wireless card that had worked before not working with the earlier test builds hopefully this will fix the problem. Testing of this fix would be appreciated. At this time DVD images are not available. There was a fairly serious security issue with the png graphics package. We will generate DVD images when the rebuilt packages become available, that will be announced then the images are ready. The target schedule for the release is available here: http://www.freebsd.org/releases/8.1R/schedule.html and the wiki page tracking the current status is here: http://wiki.freebsd.org/Releng/8.1TODO If you find problems you can report them through the normal Gnats based PR system or here on this mailing list. If you are updating an already running machine the CVS branch tag is RELENG_8_1, or if you prefer SVN use "releng/8.1". The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 8.0-RELEASE, 8.1-BETA1, or 8.1-RC1 can upgrade as follows: =20 # freebsd-update upgrade -r 8.1-RC2 During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. =20 # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now =20 After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again: # freebsd-update install # shutdown -r now Users of earlier FreeBSD releases (FreeBSD 7.x) can also use freebsd-update to upgrade to FreeBSD 8.1-RC2, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of "freebsd-update install", in order to handle differences in the system libraries between FreeBSD 7.x and FreeBSD 8.x. Checksums: MD5 (FreeBSD-8.1-RC2-amd64-bootonly.iso) =3D 473a9f6e280e6cac8cfcf62c4ebb3c= 99 MD5 (FreeBSD-8.1-RC2-amd64-disc1.iso) =3D 7eba227c8b8175a21446879fbc802a39 MD5 (FreeBSD-8.1-RC2-amd64-livefs.iso) =3D caa8df85fceb5e7eb9e9394aa378540d MD5 (FreeBSD-8.1-RC2-amd64-memstick.img) =3D 71f7c41900d41ad7e7cec63b7b75da= d8 MD5 (FreeBSD-8.1-RC2-i386-bootonly.iso) =3D f8ebd88798da2f161b33a2f714c0e12= 5 MD5 (FreeBSD-8.1-RC2-i386-disc1.iso) =3D fd77efeecd224298c6f3a08f239f294a MD5 (FreeBSD-8.1-RC2-i386-livefs.iso) =3D 9ec3b7901f377c643b8060b71c75ef25 MD5 (FreeBSD-8.1-RC2-i386-memstick.img) =3D 916e2a13027b01b912f92a94a06e7c8= 4 MD5 (FreeBSD-8.1-RC2-ia64-bootonly.iso) =3D 3daed89818fd2c7a3561d78c4b9f492= 7 MD5 (FreeBSD-8.1-RC2-ia64-disc1.iso) =3D 89d064dd30375a4c9ee6e7dc7336ac2e MD5 (FreeBSD-8.1-RC2-ia64-disc2.iso) =3D e6b7caa02ecc8d1c62cbcecdb87ca9ea MD5 (FreeBSD-8.1-RC2-ia64-disc3.iso) =3D d3c1c4a194687b20c35fbbbaa83dacc2 MD5 (FreeBSD-8.1-RC2-ia64-dvd1.iso) =3D 9a3ee466a926c213a911d8c08b8ff450 MD5 (FreeBSD-8.1-RC2-ia64-livefs.iso) =3D c979d4bee75481e0ba39ead8f431e3ed MD5 (FreeBSD-8.1-RC2-pc98-bootonly.iso) =3D b487ef910c2950239d307a9684e636c= 1 MD5 (FreeBSD-8.1-RC2-pc98-disc1.iso) =3D 11d1fe67a521c29b8909ca5e41266eaa MD5 (FreeBSD-8.1-RC2-pc98-livefs.iso) =3D d5c03f71857d1951987e4aeb9259ec7a MD5 (FreeBSD-8.1-RC2-powerpc-bootonly.iso) =3D 86a088efbbd9fa2eb2f226ed637f= 063d MD5 (FreeBSD-8.1-RC2-powerpc-disc1.iso) =3D e2808baeab27cad13d494b8b7397de8= c MD5 (FreeBSD-8.1-RC2-powerpc-disc2.iso) =3D 6836e68d4004cf5d904460ef55ae85d= f MD5 (FreeBSD-8.1-RC2-powerpc-disc3.iso) =3D ff131875a7b7665084793cce6087364= 2 MD5 (FreeBSD-8.1-RC2-sparc64-bootonly.iso) =3D 28d00dbbbd590e60b33a079337a8= 98a7 MD5 (FreeBSD-8.1-RC2-sparc64-disc1.iso) =3D 53a8b1bc84869c80e024688b45de2f9= a MD5 (FreeBSD-8.1-RC2-sparc64-livefs.iso) =3D f76fe1312d097d159d3c3ab9e58025= 74 SHA256 (FreeBSD-8.1-RC2-amd64-bootonly.iso) =3D f8a9a009f7528ba48b09a928884= 346652048c70b5f6c9c21bd13874bcdcbe8f0 SHA256 (FreeBSD-8.1-RC2-amd64-disc1.iso) =3D 5aa8ef16b34fe7dae852f1ef16a486= 3bedd194677a9b3070777a646db122fa0f SHA256 (FreeBSD-8.1-RC2-amd64-livefs.iso) =3D b72f294d5208eca1e179b41340ea3= ae809e1397b3f2ef4d3260a319d6d56ab6b SHA256 (FreeBSD-8.1-RC2-amd64-memstick.img) =3D 5de904a3fc33c510f97dc87f8b4= fa288661f956fac3ba74ff41e9f720228978f SHA256 (FreeBSD-8.1-RC2-i386-bootonly.iso) =3D dfe2916339a6160584977ed588af= 5bc4a045cac1df438f2eed8550a7ae9cd9ae SHA256 (FreeBSD-8.1-RC2-i386-disc1.iso) =3D 335ad68ce598e5f1557ca4179fde306= 3793c484cd5f3022926fbff2a25fc5540 SHA256 (FreeBSD-8.1-RC2-i386-livefs.iso) =3D f6474a515a85a51a7e5dc8e033edf5= d04caf186f5727dcd143d4060d7fbf61ef SHA256 (FreeBSD-8.1-RC2-i386-memstick.img) =3D 6795004759b253dcb0443ca81187= 14cd1e2ac12173ab7be6b35d45af61495f3b SHA256 (FreeBSD-8.1-RC2-ia64-bootonly.iso) =3D 501489d8eb78adb8518d0b060e83= 17a7e4ef3973119521f36a1ec7a95f8788fe SHA256 (FreeBSD-8.1-RC2-ia64-disc1.iso) =3D 2f70b137e90d9cc4352f3d537e02dcd= bd5adf425e68185186e0a0355720416cd SHA256 (FreeBSD-8.1-RC2-ia64-disc2.iso) =3D b9d18d85b6bf36a38feb8af056724c5= 6739be7738c1e67b8b22f9d25f2f4a29f SHA256 (FreeBSD-8.1-RC2-ia64-disc3.iso) =3D d155c16d0416f73fcc84449d28ee7dd= 9ad4a50f766a297bd522c73204f3fe45f SHA256 (FreeBSD-8.1-RC2-ia64-dvd1.iso) =3D 820778f864c0af8b4c564bbe1eac9690= 320e3f69073015f5c8bc36cb570cce20 SHA256 (FreeBSD-8.1-RC2-ia64-livefs.iso) =3D 24d4dfee814958cfb7072da341c03f= 0e349ef4b135e65277a61140632fa32cf3 SHA256 (FreeBSD-8.1-RC2-pc98-bootonly.iso) =3D b81d0277ab17ad3a2f5f89ab451f= e784c8cfcdef2df3b9628cb068d7b911b7a4 SHA256 (FreeBSD-8.1-RC2-pc98-disc1.iso) =3D 1653e1fe1b3f8dbb13a5ad642ef6d10= 7dd5269ef97af9c24f000e8033590cf93 SHA256 (FreeBSD-8.1-RC2-pc98-livefs.iso) =3D 66fd758e507e8c06c0f2c87345257b= 64e4201d8b7e9d4bed511b8a53105ca91d SHA256 (FreeBSD-8.1-RC2-powerpc-bootonly.iso) =3D e1506bd5a8408d9f50149436c= ed6964b638714ea8b6af1b62f01cd2e68d26010 SHA256 (FreeBSD-8.1-RC2-powerpc-disc1.iso) =3D 1df04962269e14654d9f23c45404= c6e67d3ecdae7cece449b6b41c92b5ed38fe SHA256 (FreeBSD-8.1-RC2-powerpc-disc2.iso) =3D 5af170e5a16c72bbf5d52aa13536= c5b30da0cfa5ae2161c4954b26f809a7291b SHA256 (FreeBSD-8.1-RC2-powerpc-disc3.iso) =3D d5b639b41c907be46a467885dc86= 269b42e0c33ee41e5b252d7519cf46dfc2d0 SHA256 (FreeBSD-8.1-RC2-sparc64-bootonly.iso) =3D 956105978f3759e2e510f1e31= 95b7f93da3f6ec2a8be749a8d53986bf79fe899 SHA256 (FreeBSD-8.1-RC2-sparc64-disc1.iso) =3D 79a66f53662e7a1d34c04f7470b4= 4052eb44debede03a8a3ad900e9348d06836 SHA256 (FreeBSD-8.1-RC2-sparc64-livefs.iso) =3D aaebc4a306d14bffa0c1066301b= 2f7dc0af796586d23de2ccb5a0bc6239a5f6a --=20 Ken Smith - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-/PRJEpA8KcWjT2hXf0ML Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkwt+dMACgkQ/G14VSmup/bo/ACfTjSpavNpqLyg2YsWszs+IIZA QKcAn2RbxkmnHrJsm7LkY2GlbMdKDfBR =hMHc -----END PGP SIGNATURE----- --=-/PRJEpA8KcWjT2hXf0ML-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 16:55:03 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 222E51065672; Fri, 2 Jul 2010 16:55:03 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id AE1068FC18; Fri, 2 Jul 2010 16:55:02 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o62GsoqA057527; Fri, 2 Jul 2010 09:54:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=subject:from:to:cc:content-type:date:message-id: mime-version:x-mailer:content-transfer-encoding; b=x/6B6IMDzkD5+i5RxfJl67wvkia/oUZ4hOIOR6JkcT339i/4UF/hYY5yCF2iHErd From: Sean Bruno To: freebsd-stable Content-Type: text/plain; charset="UTF-8" Date: Fri, 02 Jul 2010 09:54:50 -0700 Message-ID: <1278089690.2469.22.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Cc: yongari@freebsd.org Subject: [stable 7] bge() related panic on an HP dl380g3 (32 bit) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 16:55:03 -0000 Started seeing this panic today from our BSD7 variant here at Yahoo. Our BGE driver is identical to 7stable at this time. Looks like all of these boxes are HP DL380G3 models. I have included the panic and pciconf -lv information. I assume that these machines have a variant of BGE that needs some kind of exception/quirk that I'm unaware of. ---------------------------- panic ------------------------------------- Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 06 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x20:0xa053f8e6 stack pointer = 0x28:0xa9599978 frame pointer = 0x28:0xa95999a4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 33 (irq29: bge0) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper(a07a1271,a9599814,a04e7fe9,a07c029d,0,...) at db_trace_self_wrapper+0x26 kdb_backtrace(a07c029d,0,a076d19d,a9599820,0,...) at kdb_backtrace+0x29 panic(a076d19d,a07c15d2,a97b17a4,1,1,...) at panic+0x119 trap_fatal(a08a63e0,0,1,0,0,...) at trap_fatal+0x333 trap_pfault(a97e2800,a95998bc,dbdd,0,a9796250,...) at trap_pfault+0x260 trap(a9599938) at trap+0x462 calltrap() at calltrap+0x6 --- trap 0xc, eip = 0xa053f8e6, esp = 0xa9599978, ebp = 0xa95999a4 --- m_copym(a9df8800,5dc,5c8,1,0,...) at m_copym+0x36 ip_fragment(a9f66810,a9599a70,5dc,7,0,...) at ip_fragment+0x235 ip_output(a9df8800,0,a9599a44,0,0,a9ef6974,a085b740,0,0,a9ef6974,a05b54c1,a085b744,a085b74c,3e8) at ip_output+0xba6 tcp_respond(ab433448,a9f66810,a9f66824,a9df8800,0,...) at tcp_respond +0x395 tcp_dropwithreset(5a8,4,a9f66824,a9599b90,a9df8800,...) at tcp_dropwithreset+0xe9 tcp_input(a9df8800,14,a97966f0,a9599bf0,1,...) at tcp_input+0xcde ip_input(a9df8800,0,800,a97e2800,800,...) at ip_input+0x6f8 netisr_dispatch(2,a9df8800,10,3,0,...) at netisr_dispatch+0x55 ether_demux(a97e2800,a9df8800,3,0,3,...) at ether_demux+0x1c1 ether_input(a97e2800,a9df8800,a08b2480,a9cf4900,0,...) at ether_input +0x323 bge_rxeof(0,1,9157deaa,5647,1000000,...) at bge_rxeof+0x2c2 bge_intr(a97f7000,0,a079c70e,4fc,0,...) at bge_intr+0x132 ithread_loop(a97d9ad0,a9599d38,0,0,0,...) at ithread_loop+0x1ab fork_exit(a04c28c0,a97d9ad0,a9599d38) at fork_exit+0x99 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xa9599d70, ebp = 0 --- Uptime: 8h36m2s Physical memory: 3894 MB Dumping 296 MB:Aborting dump due to I/O error. status == 0xb, scsi status == 0x0 ** DUMP FAILED (ERROR 5) ** Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs 4096 MB Detected ProLiant System BIOS - P29 (09/15/2004) Copyright 1982, 2004 Hewlett-Packard Development Group, L.P. Processor 1 initialized at 3.06 GHz/533 MHz(512 Kbyte L2) Advanced Memory Protection Mode: Advanced ECC Support Redundant ROM Detected - This system contains a valid backup system ROM. ------------- pciconf -lv --------------------------------------------- hostb0@pci0:0:0:0: class=0x060000 card=0x00000000 chip=0x00141166 rev=0x33 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'Host Bridge (CNB20-HE)' class = bridge subclass = HOST-PCI hostb1@pci0:0:0:1: class=0x060000 card=0x00000000 chip=0x00141166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'Host Bridge (CNB20-HE)' class = bridge subclass = HOST-PCI hostb2@pci0:0:0:2: class=0x060000 card=0x00000000 chip=0x00141166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'Host Bridge (CNB20-HE)' class = bridge subclass = HOST-PCI vgapci0@pci0:0:3:0: class=0x030000 card=0x001e0e11 chip=0x47521002 rev=0x27 hdr=0x00 vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' device = 'ATI On-Board VGA for HP Proliant 350 G3 (Rage XL PCI)' class = display subclass = VGA none0@pci0:0:4:0: class=0x088000 card=0xb2060e11 chip=0xb2030e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'Integrated Lights Out Processor (iLo)' class = base peripheral none1@pci0:0:4:2: class=0x088000 card=0xb2060e11 chip=0xb2040e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'Integrated Lights Out Processor (iLo)' class = base peripheral isab0@pci0:0:15:0: class=0x060100 card=0x02011166 chip=0x02011166 rev=0x93 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CSB5 PCI to ISA Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:0:15:1: class=0x01018a card=0x02121166 chip=0x02121166 rev=0x93 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CSB5 PCI EIDE Controller' class = mass storage subclass = ATA ohci0@pci0:0:15:2: class=0x0c0310 card=0x02201166 chip=0x02201166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'OpenHCI Compliant USB Controller (OSB4)' class = serial bus subclass = USB hostb3@pci0:0:15:3: class=0x060000 card=0x02301166 chip=0x02251166 rev=0x00 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'PCI Bridge (CSB5)' class = bridge subclass = HOST-PCI hostb4@pci0:0:16:0: class=0x060000 card=0x00000000 chip=0x01011166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CIOB-X2' class = bridge subclass = HOST-PCI hostb5@pci0:0:16:2: class=0x060000 card=0x00000000 chip=0x01011166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CIOB-X2' class = bridge subclass = HOST-PCI hostb6@pci0:0:17:0: class=0x060000 card=0x00000000 chip=0x01011166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CIOB-X2' class = bridge subclass = HOST-PCI hostb7@pci0:0:17:2: class=0x060000 card=0x00000000 chip=0x01011166 rev=0x05 hdr=0x00 vendor = 'ServerWorks (Was: Reliance Computer Corp)' device = 'CIOB-X2' class = bridge subclass = HOST-PCI ciss0@pci0:1:3:0: class=0x010400 card=0x40800e11 chip=0xb1780e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'SMART2 Array Controller (CISSB)' class = mass storage subclass = RAID bge0@pci0:2:1:0: class=0x020000 card=0x00cb0e11 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class = network subclass = ethernet bge1@pci0:2:2:0: class=0x020000 card=0x00cb0e11 chip=0x16a714e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5703X NetXtreme Gigabit Ethernet' class = network subclass = ethernet none2@pci0:6:30:0: class=0x080400 card=0xa2fe0e11 chip=0xa0f70e11 rev=0x14 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'PCI Hot Plug Controller' class = base peripheral subclass = PCI hot-plug controller --------------------------------- boot messages ------------------------ Jul 1 15:14:47 pud628 kernel: bge0: mem 0xf7ef0000-0xf7efffff irq 29 at device 1.0 on pci2 Jul 1 15:14:47 pud628 kernel: bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf7ef0000 Jul 1 15:14:47 pud628 kernel: bge0: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI-X Jul 1 15:14:47 pud628 kernel: miibus0: on bge0 Jul 1 15:14:47 pud628 kernel: brgphy0: PHY 1 on miibus0 Jul 1 15:14:47 pud628 kernel: brgphy0: OUI 0x000818, model 0x0016, rev. 2 Jul 1 15:14:47 pud628 kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto Jul 1 15:14:47 pud628 kernel: bge0: bpf attached Jul 1 15:14:47 pud628 kernel: bge0: Ethernet address: 00:11:85:bb:d9:7b Jul 1 15:14:47 pud628 kernel: ioapic1: routing intpin 13 (PCI IRQ 29) to vector 53 Jul 1 15:14:47 pud628 kernel: bge0: [MPSAFE] Jul 1 15:14:47 pud628 kernel: bge0: [ITHREAD] Jul 1 15:14:47 pud628 kernel: pci0:2:2:0: bad VPD cksum, remain 223 Jul 1 15:14:47 pud628 kernel: bge1: mem 0xf7ee0000-0xf7eeffff irq 31 at device 2.0 on pci2 Jul 1 15:14:47 pud628 kernel: bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf7ee0000 Jul 1 15:14:47 pud628 kernel: bge1: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI-X Jul 1 15:14:47 pud628 kernel: miibus1: on bge1 Jul 1 15:14:47 pud628 kernel: brgphy1: PHY 1 on miibus1 Jul 1 15:14:47 pud628 kernel: brgphy1: OUI 0x000818, model 0x0016, rev. 2 Jul 1 15:14:47 pud628 kernel: brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto Jul 1 15:14:47 pud628 kernel: bge1: bpf attached Jul 1 15:14:47 pud628 kernel: bge1: Ethernet address: 00:11:85:bb:d9:7a Jul 1 15:14:47 pud628 kernel: ioapic1: routing intpin 15 (PCI IRQ 31) to vector 54 Jul 1 15:14:47 pud628 kernel: bge1: [MPSAFE] Jul 1 15:14:47 pud628 kernel: bge1: [ITHREAD] From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 17:39:24 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2A37106566C for ; Fri, 2 Jul 2010 17:39:24 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9B16F8FC15 for ; Fri, 2 Jul 2010 17:39:24 +0000 (UTC) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.4/8.14.3) with ESMTP id o62HdMOU092319; Fri, 2 Jul 2010 13:39:22 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201007021739.o62HdMOU092319@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 02 Jul 2010 13:39:22 -0400 To: freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <201006102031.o5AKVCH2016467@lava.sentex.ca> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: jfvogel@gmail.com Subject: Re: RELENG_7 em problems (and RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 17:39:24 -0000 Hi Jack, Just a followup to the email below. I now saw what appears to be the same problem on RELENG_8, but on a different nic and with VLANs. So not sure if this is a general em problem, a problem specific to some em NICs, or a TSO problem in general. The issue seemed to be triggered when I added a new vlan based on em3@pci0:14:0:0: class=0x020000 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel PRO/1000 PL Network Adaptor (82573L)' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) pci14: on pcib5 em3: port 0x6000-0x601f mem 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 em3: Using MSI interrupt em3: [FILTER] em3: Ethernet address: 00:30:48:9f:eb:81 em3: flags=8943 metric 0 mtu 1500 options=2098 ether 00:30:48:9f:eb:81 inet 10.255.255.254 netmask 0xfffffffc broadcast 10.255.255.255 media: Ethernet autoselect (1000baseT ) status: active I had to disable tso, rxcsum and txsum in order to see the devices on the other side of the two vlans trunked off em3. Unfortunately, the other sides were switches 100km and 500km away so I didnt have any tcpdump capabilities to diagnose the issue. I had already created one vlan off this NIC and all was fine. A few weeks later, I added a new one and I could no longer telnet into the remote switches from the local machine.... But, I could telnet into the switches from machines not on the problem box. Hence, it would appear to be a general TSO issue no ? I disabled tso on the nic (I didnt disable net.inet.tcp.tso as I forgot about that).. Still nothing. I could always ping the remote devices, but no tcp services. I then remembered this issue from before, so I tried disabling tso on the NIC. Still nothing. Then I disabled rxcsum and txcsum and I could then telnet into the remote devices. This newly observed issue was from a buildworld on Mon Jun 14 11:29:12 EDT 2010. I will try and recreate the issue locally again to see if I can trigger the problem on demand. Any thoughts on what it might be ? Perhaps an issue specific to certain em nics ? ---Mike At 04:31 PM 6/10/2010, Mike Tancsa wrote: >Hi Jack, > I am seeing some issues on RELENG_7 with a specific em nic > >em2@pci0:13:0:0: class=0x020000 card=0x108c15d9 >chip=0x108c8086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel Corporation 82573E Gigabit Ethernet > Controller (Copper) (82573E)' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > >If I disable tso, I am not able to make a tcp connection into the host > >eg >0[psbgate1]# ifconfig em2 >em2: flags=8843 metric 0 mtu 1500 > >options=219b > ether 00:30:48:9f:eb:80 > inet 192.168.128.200 netmask 0xfffffff0 broadcast 192.168.128.207 > media: Ethernet autoselect (100baseTX ) > status: active >0[psbgate1]# ifconfig em2 -tso >0[psbgate1]# > > >Looking at the pcap, the checksum is bad on the syn-ack. If I >re-enable tso, it seems to be ok > >16:18:01.113297 IP (tos 0x10, ttl 64, id 6339, offset 0, flags [DF], >proto TCP (6), length 60) 192.168.128.196.54172 > >192.168.128.200.22: S, cksum 0x4e79 (correct), >3313156149:3313156149(0) win 65535 3,sackOK,timestamp 3376174416 0> >16:18:01.123676 IP (tos 0x0, ttl 64, id 3311, offset 0, flags [DF], >proto TCP (6), length 60) 192.168.128.200.22 > >192.168.128.196.54172: S, cksum 0x81c9 (incorrect (-> 0x51f2), >1373042663:1373042663(0) ack 3313156150 win 65535 1460,nop,wscale 3,sackOK,timestamp 1251567646 3376174416> > > >em2: port 0x5000-0x501f >mem 0xe8200000-0xe821ffff irq 16 at device 0.0 on pci13 >em2: Using MSI interrupt >em2: [FILTER] >em2: Ethernet address: 00:30:48:9f:eb:80 >pcib5: irq 16 at device 28.5 on pci0 >pci14: on pcib5 >em3: port 0x6000-0x601f >mem 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 >em3: Using MSI interrupt >em3: [FILTER] >em3: Ethernet address: 00:30:48:9f:eb:81 > > >Also there is still the issue with > >http://lists.freebsd.org/pipermail/freebsd-stable/2009-November/052842.html > >in RELENG_7 ? > > ---Mike > > >-------------------------------------------------------------------- >Mike Tancsa, tel +1 519 651 3400 >Sentex Communications, mike@sentex.net >Providing Internet since 1994 www.sentex.net >Cambridge, Ontario Canada www.sentex.net/mike > >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 17:44:33 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF4CA106566C for ; Fri, 2 Jul 2010 17:44:33 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id A6F808FC15 for ; Fri, 2 Jul 2010 17:44:33 +0000 (UTC) Received: by gwb1 with SMTP id 1so1263940gwb.13 for ; Fri, 02 Jul 2010 10:44:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=PXxDb4N4kce7X0tfH0fatXzLY2GU/Lg5LpVv11RqE2c=; b=vi+4nuPSBNgBIQdOehb7lTN8e24o9JARFKqReQhGXkrS1iehNF0yVHjqyYPKZNFanF MEanO23vvRpzRNZYGVoqjr7D9/TJJVm5O1YsXSK5UJt83YEkE3cKRKY7e2M6H9lYA7C+ +XytQKUp/WyL3m8f9D9dEyxsPGGvrC3XxyDk4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qfoQjG7MEtIA/od4nI9W1tExBdbTJMFtqnYcZnWGhh4WUyWbMTcH1kG2VNy/0GOGSL A358SNlWR202ot7Xcu6Q+pVm464SXmrpiWUKer18Bwtd8zAvIehUa3mD0Kw+3UKflTb2 O+QkyQB77X8Yf04EJ/ER+AtaEb1jdyxi6D3MY= MIME-Version: 1.0 Received: by 10.229.245.68 with SMTP id lt4mr768966qcb.71.1278092666557; Fri, 02 Jul 2010 10:44:26 -0700 (PDT) Received: by 10.229.250.197 with HTTP; Fri, 2 Jul 2010 10:44:26 -0700 (PDT) In-Reply-To: <201007021739.o62HdMOU092319@lava.sentex.ca> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> <201007021739.o62HdMOU092319@lava.sentex.ca> Date: Fri, 2 Jul 2010 10:44:26 -0700 Message-ID: From: Jack Vogel To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_7 em problems (and RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 17:44:34 -0000 I got the email, there are server outages around here today and people leaving for a long weekend, so not much getting done. I'll take some time and look into this after the weekend, ok? Jack On Fri, Jul 2, 2010 at 10:39 AM, Mike Tancsa wrote: > Hi Jack, > Just a followup to the email below. I now saw what appears to be the > same problem on RELENG_8, but on a different nic and with VLANs. So not > sure if this is a general em problem, a problem specific to some em NICs, or > a TSO problem in general. The issue seemed to be triggered when I added a > new vlan based on > > em3@pci0:14:0:0: class=0x020000 card=0x109a15d9 chip=0x109a8086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel PRO/1000 PL Network Adaptor (82573L)' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > > pci14: on pcib5 > em3: port 0x6000-0x601f mem > 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 > em3: Using MSI interrupt > em3: [FILTER] > em3: Ethernet address: 00:30:48:9f:eb:81 > > em3: flags=8943 metric 0 > mtu 1500 > options=2098 > ether 00:30:48:9f:eb:81 > inet 10.255.255.254 netmask 0xfffffffc broadcast 10.255.255.255 > media: Ethernet autoselect (1000baseT ) > status: active > > I had to disable tso, rxcsum and txsum in order to see the devices on the > other side of the two vlans trunked off em3. Unfortunately, the other sides > were switches 100km and 500km away so I didnt have any tcpdump capabilities > to diagnose the issue. I had already created one vlan off this NIC and all > was fine. A few weeks later, I added a new one and I could no longer telnet > into the remote switches from the local machine.... But, I could telnet into > the switches from machines not on the problem box. Hence, it would appear to > be a general TSO issue no ? I disabled tso on the nic (I didnt disable > net.inet.tcp.tso as I forgot about that).. Still nothing. I could always > ping the remote devices, but no tcp services. I then remembered this issue > from before, so I tried disabling tso on the NIC. Still nothing. Then I > disabled rxcsum and txcsum and I could then telnet into the remote devices. > > This newly observed issue was from a buildworld on Mon Jun 14 11:29:12 EDT > 2010. > > I will try and recreate the issue locally again to see if I can trigger the > problem on demand. Any thoughts on what it might be ? Perhaps an issue > specific to certain em nics ? > > ---Mike > > > At 04:31 PM 6/10/2010, Mike Tancsa wrote: > >> Hi Jack, >> I am seeing some issues on RELENG_7 with a specific em nic >> >> em2@pci0:13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 >> rev=0x03 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Intel Corporation 82573E Gigabit Ethernet Controller >> (Copper) (82573E)' >> class = network >> subclass = ethernet >> cap 01[c8] = powerspec 2 supports D0 D3 current D0 >> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message >> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) >> >> If I disable tso, I am not able to make a tcp connection into the host >> >> eg >> 0[psbgate1]# ifconfig em2 >> em2: flags=8843 metric 0 mtu 1500 >> >> >> options=219b >> ether 00:30:48:9f:eb:80 >> inet 192.168.128.200 netmask 0xfffffff0 broadcast 192.168.128.207 >> media: Ethernet autoselect (100baseTX ) >> status: active >> 0[psbgate1]# ifconfig em2 -tso >> 0[psbgate1]# >> >> >> Looking at the pcap, the checksum is bad on the syn-ack. If I re-enable >> tso, it seems to be ok >> >> 16:18:01.113297 IP (tos 0x10, ttl 64, id 6339, offset 0, flags [DF], proto >> TCP (6), length 60) 192.168.128.196.54172 > 192.168.128.200.22: S, cksum >> 0x4e79 (correct), 3313156149:3313156149(0) win 65535 > 3,sackOK,timestamp 3376174416 0> >> 16:18:01.123676 IP (tos 0x0, ttl 64, id 3311, offset 0, flags [DF], proto >> TCP (6), length 60) 192.168.128.200.22 > 192.168.128.196.54172: S, cksum >> 0x81c9 (incorrect (-> 0x51f2), 1373042663:1373042663(0) ack 3313156150 win >> 65535 >> >> >> em2: port 0x5000-0x501f mem >> 0xe8200000-0xe821ffff irq 16 at device 0.0 on pci13 >> em2: Using MSI interrupt >> em2: [FILTER] >> em2: Ethernet address: 00:30:48:9f:eb:80 >> pcib5: irq 16 at device 28.5 on pci0 >> pci14: on pcib5 >> em3: port 0x6000-0x601f mem >> 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 >> em3: Using MSI interrupt >> em3: [FILTER] >> em3: Ethernet address: 00:30:48:9f:eb:81 >> >> >> Also there is still the issue with >> >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2009-November/052842.html >> >> in RELENG_7 ? >> >> ---Mike >> >> >> -------------------------------------------------------------------- >> Mike Tancsa, tel +1 519 651 3400 >> Sentex Communications, mike@sentex.net >> Providing Internet since 1994 www.sentex.net >> Cambridge, Ontario Canada www.sentex.net/mike >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > -------------------------------------------------------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet since 1994 www.sentex.net > Cambridge, Ontario Canada www.sentex.net/mike > > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:11:42 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2381106564A; Fri, 2 Jul 2010 19:11:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id B67AC8FC12; Fri, 2 Jul 2010 19:11:42 +0000 (UTC) Received: by pvb32 with SMTP id 32so1546993pvb.13 for ; Fri, 02 Jul 2010 12:11:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=IIbW4kmTN0+wnvzQdNrfSvN4XnBszXWDq9I+kJa98BU=; b=OQPRxM+HLifeK5Gxuzu4DOedrOyIBQze/a3qN0evGA+pDH4er6beX10Q82cQee6gOT veZ2pmE4Ry1TrWE/z6JzhZhYGK4jlXB74ayu4L54AmgUYlOIfgOiurgr3089N/4l7vIa CKjlVra+cnhd4dz4nrQwTGE4duD3G33w/JjTw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=SS5UcaIE9B1NjtvMBQLLcNSG+/LEUnv4ZFr7bBujHE4fREIEOn9zIN1FmZ7CwjMy/F dJz0kJbByavk/gUjI1XKzidZMNiu1XZeFFkKKYTrXLV2cCAoPMt+muYLjYuwMu+whH+A 5cRZqGMmqOx2PmzdpQDbnboeLx3Uyn4TEUA/Q= Received: by 10.142.127.9 with SMTP id z9mr1618895wfc.185.1278097896776; Fri, 02 Jul 2010 12:11:36 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id b2sm1074993rvn.22.2010.07.02.12.11.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jul 2010 12:11:35 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 2 Jul 2010 12:11:10 -0700 From: Pyun YongHyeon Date: Fri, 2 Jul 2010 12:11:10 -0700 To: Sean Bruno Message-ID: <20100702191110.GA10862@michelle.cdnetworks.com> References: <1278089690.2469.22.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1278089690.2469.22.camel@localhost.localdomain> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable , yongari@freebsd.org Subject: Re: [stable 7] bge() related panic on an HP dl380g3 (32 bit) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 19:11:43 -0000 On Fri, Jul 02, 2010 at 09:54:50AM -0700, Sean Bruno wrote: > Started seeing this panic today from our BSD7 variant here at Yahoo. > Our BGE driver is identical to 7stable at this time. Looks like all of > these boxes are HP DL380G3 models. I have included the panic and > pciconf -lv information. > > > I assume that these machines have a variant of BGE that needs some kind > of exception/quirk that I'm unaware of. > Does your bge(4) driver include r208995? > ---------------------------- panic ------------------------------------- > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 06 > fault virtual address = 0xc > fault code = supervisor read, page not present > instruction pointer = 0x20:0xa053f8e6 > stack pointer = 0x28:0xa9599978 > frame pointer = 0x28:0xa95999a4 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 33 (irq29: bge0) > trap number = 12 > panic: page fault > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper(a07a1271,a9599814,a04e7fe9,a07c029d,0,...) at > db_trace_self_wrapper+0x26 > kdb_backtrace(a07c029d,0,a076d19d,a9599820,0,...) at kdb_backtrace+0x29 > panic(a076d19d,a07c15d2,a97b17a4,1,1,...) at panic+0x119 > trap_fatal(a08a63e0,0,1,0,0,...) at trap_fatal+0x333 > trap_pfault(a97e2800,a95998bc,dbdd,0,a9796250,...) at trap_pfault+0x260 > trap(a9599938) at trap+0x462 > calltrap() at calltrap+0x6 > --- trap 0xc, eip = 0xa053f8e6, esp = 0xa9599978, ebp = 0xa95999a4 --- > m_copym(a9df8800,5dc,5c8,1,0,...) at m_copym+0x36 > ip_fragment(a9f66810,a9599a70,5dc,7,0,...) at ip_fragment+0x235 > ip_output(a9df8800,0,a9599a44,0,0,a9ef6974,a085b740,0,0,a9ef6974,a05b54c1,a085b744,a085b74c,3e8) at ip_output+0xba6 > tcp_respond(ab433448,a9f66810,a9f66824,a9df8800,0,...) at tcp_respond > +0x395 > tcp_dropwithreset(5a8,4,a9f66824,a9599b90,a9df8800,...) at > tcp_dropwithreset+0xe9 > tcp_input(a9df8800,14,a97966f0,a9599bf0,1,...) at tcp_input+0xcde > ip_input(a9df8800,0,800,a97e2800,800,...) at ip_input+0x6f8 > netisr_dispatch(2,a9df8800,10,3,0,...) at netisr_dispatch+0x55 > ether_demux(a97e2800,a9df8800,3,0,3,...) at ether_demux+0x1c1 > ether_input(a97e2800,a9df8800,a08b2480,a9cf4900,0,...) at ether_input > +0x323 > bge_rxeof(0,1,9157deaa,5647,1000000,...) at bge_rxeof+0x2c2 > bge_intr(a97f7000,0,a079c70e,4fc,0,...) at bge_intr+0x132 > ithread_loop(a97d9ad0,a9599d38,0,0,0,...) at ithread_loop+0x1ab > fork_exit(a04c28c0,a97d9ad0,a9599d38) at fork_exit+0x99 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xa9599d70, ebp = 0 --- > Uptime: 8h36m2s > Physical memory: 3894 MB > Dumping 296 MB:Aborting dump due to I/O error. > status == 0xb, scsi status == 0x0 > > ** DUMP FAILED (ERROR 5) ** > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > cpu_reset: Stopping other CPUs > 4096 MB Detected > > ProLiant System BIOS - P29 (09/15/2004) > Copyright 1982, 2004 Hewlett-Packard Development Group, L.P. > > > Processor 1 initialized at 3.06 GHz/533 MHz(512 Kbyte L2) > > Advanced Memory Protection Mode: Advanced ECC Support > Redundant ROM Detected - This system contains a valid backup system ROM. > > ------------- pciconf -lv --------------------------------------------- > hostb0@pci0:0:0:0: class=0x060000 card=0x00000000 chip=0x00141166 > rev=0x33 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'Host Bridge (CNB20-HE)' > class = bridge > subclass = HOST-PCI > hostb1@pci0:0:0:1: class=0x060000 card=0x00000000 chip=0x00141166 > rev=0x00 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'Host Bridge (CNB20-HE)' > class = bridge > subclass = HOST-PCI > hostb2@pci0:0:0:2: class=0x060000 card=0x00000000 chip=0x00141166 > rev=0x00 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'Host Bridge (CNB20-HE)' > class = bridge > subclass = HOST-PCI > vgapci0@pci0:0:3:0: class=0x030000 card=0x001e0e11 chip=0x47521002 > rev=0x27 hdr=0x00 > vendor = 'ATI Technologies Inc. / Advanced Micro Devices, Inc.' > device = 'ATI On-Board VGA for HP Proliant 350 G3 (Rage XL PCI)' > class = display > subclass = VGA > none0@pci0:0:4:0: class=0x088000 card=0xb2060e11 chip=0xb2030e11 > rev=0x01 hdr=0x00 > vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' > device = 'Integrated Lights Out Processor (iLo)' > class = base peripheral > none1@pci0:0:4:2: class=0x088000 card=0xb2060e11 chip=0xb2040e11 > rev=0x01 hdr=0x00 > vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' > device = 'Integrated Lights Out Processor (iLo)' > class = base peripheral > isab0@pci0:0:15:0: class=0x060100 card=0x02011166 chip=0x02011166 > rev=0x93 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'CSB5 PCI to ISA Bridge' > class = bridge > subclass = PCI-ISA > atapci0@pci0:0:15:1: class=0x01018a card=0x02121166 chip=0x02121166 > rev=0x93 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'CSB5 PCI EIDE Controller' > class = mass storage > subclass = ATA > ohci0@pci0:0:15:2: class=0x0c0310 card=0x02201166 chip=0x02201166 > rev=0x05 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'OpenHCI Compliant USB Controller (OSB4)' > class = serial bus > subclass = USB > hostb3@pci0:0:15:3: class=0x060000 card=0x02301166 chip=0x02251166 > rev=0x00 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'PCI Bridge (CSB5)' > class = bridge > subclass = HOST-PCI > hostb4@pci0:0:16:0: class=0x060000 card=0x00000000 chip=0x01011166 > rev=0x05 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'CIOB-X2' > class = bridge > subclass = HOST-PCI > hostb5@pci0:0:16:2: class=0x060000 card=0x00000000 chip=0x01011166 > rev=0x05 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'CIOB-X2' > class = bridge > subclass = HOST-PCI > hostb6@pci0:0:17:0: class=0x060000 card=0x00000000 chip=0x01011166 > rev=0x05 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'CIOB-X2' > class = bridge > subclass = HOST-PCI > hostb7@pci0:0:17:2: class=0x060000 card=0x00000000 chip=0x01011166 > rev=0x05 hdr=0x00 > vendor = 'ServerWorks (Was: Reliance Computer Corp)' > device = 'CIOB-X2' > class = bridge > subclass = HOST-PCI > ciss0@pci0:1:3:0: class=0x010400 card=0x40800e11 chip=0xb1780e11 > rev=0x01 hdr=0x00 > vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' > device = 'SMART2 Array Controller (CISSB)' > class = mass storage > subclass = RAID > bge0@pci0:2:1:0: class=0x020000 card=0x00cb0e11 chip=0x16a714e4 > rev=0x02 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5703X NetXtreme Gigabit Ethernet' > class = network > subclass = ethernet > bge1@pci0:2:2:0: class=0x020000 card=0x00cb0e11 chip=0x16a714e4 > rev=0x02 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5703X NetXtreme Gigabit Ethernet' > class = network > subclass = ethernet > none2@pci0:6:30:0: class=0x080400 card=0xa2fe0e11 chip=0xa0f70e11 > rev=0x14 hdr=0x00 > vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' > device = 'PCI Hot Plug Controller' > class = base peripheral > subclass = PCI hot-plug controller > > --------------------------------- boot messages ------------------------ > Jul 1 15:14:47 pud628 kernel: bge0: mem 0xf7ef0000-0xf7efffff irq 29 at device 1.0 on pci2 > Jul 1 15:14:47 pud628 kernel: bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf7ef0000 > Jul 1 15:14:47 pud628 kernel: bge0: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI-X > Jul 1 15:14:47 pud628 kernel: miibus0: on bge0 > Jul 1 15:14:47 pud628 kernel: brgphy0: PHY 1 on miibus0 > Jul 1 15:14:47 pud628 kernel: brgphy0: OUI 0x000818, model 0x0016, rev. 2 > Jul 1 15:14:47 pud628 kernel: brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > Jul 1 15:14:47 pud628 kernel: bge0: bpf attached > Jul 1 15:14:47 pud628 kernel: bge0: Ethernet address: 00:11:85:bb:d9:7b > Jul 1 15:14:47 pud628 kernel: ioapic1: routing intpin 13 (PCI IRQ 29) to vector 53 > Jul 1 15:14:47 pud628 kernel: bge0: [MPSAFE] > Jul 1 15:14:47 pud628 kernel: bge0: [ITHREAD] > Jul 1 15:14:47 pud628 kernel: pci0:2:2:0: bad VPD cksum, remain 223 > Jul 1 15:14:47 pud628 kernel: bge1: mem 0xf7ee0000-0xf7eeffff irq 31 at device 2.0 on pci2 > Jul 1 15:14:47 pud628 kernel: bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf7ee0000 > Jul 1 15:14:47 pud628 kernel: bge1: CHIP ID 0x00001002; ASIC REV 0x01; CHIP REV 0x10; PCI-X > Jul 1 15:14:47 pud628 kernel: miibus1: on bge1 > Jul 1 15:14:47 pud628 kernel: brgphy1: PHY 1 on miibus1 > Jul 1 15:14:47 pud628 kernel: brgphy1: OUI 0x000818, model 0x0016, rev. 2 > Jul 1 15:14:47 pud628 kernel: brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > Jul 1 15:14:47 pud628 kernel: bge1: bpf attached > Jul 1 15:14:47 pud628 kernel: bge1: Ethernet address: 00:11:85:bb:d9:7a > Jul 1 15:14:47 pud628 kernel: ioapic1: routing intpin 15 (PCI IRQ 31) to vector 54 > Jul 1 15:14:47 pud628 kernel: bge1: [MPSAFE] > Jul 1 15:14:47 pud628 kernel: bge1: [ITHREAD] > > > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:19:05 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82E80106566B for ; Fri, 2 Jul 2010 19:19:05 +0000 (UTC) (envelope-from schlake@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3D6618FC15 for ; Fri, 2 Jul 2010 19:19:04 +0000 (UTC) Received: by vws6 with SMTP id 6so3677290vws.13 for ; Fri, 02 Jul 2010 12:18:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=SLazFFgQeb2TnQnOIMPzjjHZ1cgd+JywCYEWMM9mwrM=; b=UEyVeEw2T29nzs3GrlFhlJlsjrgy58aZDg1AaPJHysQhEORw6ongnlFCdkygEKH5Cn 3YQA4zIFawgr/tCuIsf6wTnX0TZyw36a524ZGR+H+0do5oTDXDA42E2UpjGBfoRdFs0V 0oOemtvD42JVJiK5GKmD7kPhTx07Efw5/Ded4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=NxN3HmaDpPl/b8ETg6ayVKOMzUrKWC8wmL5IFC4zyrYlzqBNu7cjfMZ4qDwBzu9mDs NceAsr00nt/VHn2BLiE2SuQLly5EzRvXZt4TExXwC0dCgZrcb/dJbWSa0xjjzLDVF1NC Kjz7pL371ZmbsQ+mpg5ybbB9kx1RGNuxiS1pA= MIME-Version: 1.0 Received: by 10.220.88.199 with SMTP id b7mr650265vcm.83.1278098336792; Fri, 02 Jul 2010 12:18:56 -0700 (PDT) Received: by 10.220.183.6 with HTTP; Fri, 2 Jul 2010 12:18:56 -0700 (PDT) Date: Fri, 2 Jul 2010 13:18:56 -0600 Message-ID: From: "William D. Colburn (Schlake)" To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: My kernel panics suck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 19:19:05 -0000 I got my new 8-stable system up, and now I just have recurrent disk controller failures. The machine can't stay more than about ten minutes before it panics into a hung kernel, or simple reboots. Unfortunately, I know the root cause of the panics. If my computer is sitting on the table, then the kernel doesn't panic. If the computer is sitting on the desk, then it panics like mad. The table is wooden, the desk is metal. Of course, I'm also changing power too. On the table, I use a wall outlet, while on the desk I use my Smart UPS. Unfortunately, you can't really help me with this. I'm just writing in out of the hope that I'll get some sympathy for this problem. -- Schlake From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:24:28 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ED67106564A for ; Fri, 2 Jul 2010 19:24:28 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.re1.yahoo.com (mrout1-b.corp.re1.yahoo.com [69.147.107.20]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF0B8FC1B for ; Fri, 2 Jul 2010 19:24:28 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o62JON5t066215; Fri, 2 Jul 2010 12:24:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=subject:from:to:cc:in-reply-to:references:content-type:date: message-id:mime-version:x-mailer:content-transfer-encoding; b=CQ/AwkwH+8PUqRNWxobSkZOgDTcJJXzBePibEfmyo0OVdMt2uLhXO4uPjhH9OHEP From: Sean Bruno To: "pyunyh@gmail.com" In-Reply-To: <20100702191110.GA10862@michelle.cdnetworks.com> References: <1278089690.2469.22.camel@localhost.localdomain> <20100702191110.GA10862@michelle.cdnetworks.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 02 Jul 2010 12:24:23 -0700 Message-ID: <1278098663.2469.31.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) Content-Transfer-Encoding: 7bit Cc: freebsd-stable , "yongari@freebsd.org" Subject: Re: [stable 7] bge() related panic on an HP dl380g3 (32 bit) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 19:24:28 -0000 On Fri, 2010-07-02 at 12:11 -0700, Pyun YongHyeon wrote: > On Fri, Jul 02, 2010 at 09:54:50AM -0700, Sean Bruno wrote: > > Started seeing this panic today from our BSD7 variant here at Yahoo. > > Our BGE driver is identical to 7stable at this time. Looks like all of > > these boxes are HP DL380G3 models. I have included the panic and > > pciconf -lv information. > > > > > > I assume that these machines have a variant of BGE that needs some kind > > of exception/quirk that I'm unaware of. > > > > Does your bge(4) driver include r208995? It did not. I screwed up the report. The bge(4) driver under test was from r205616 (we built it in April). Did this panic look like the one fixed by r208995? Sean From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:34:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F1B1106566B; Fri, 2 Jul 2010 19:34:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 564998FC15; Fri, 2 Jul 2010 19:34:15 +0000 (UTC) Received: by pxi3 with SMTP id 3so1582883pxi.13 for ; Fri, 02 Jul 2010 12:34:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=/+1XhIu9A/Y7Sh6wwKFrPwwNRFG4rYejbqlyzwkjX1I=; b=vYeR2h5agSM225F/r6KYHHZzk679ptJhpCa3PH0X+X7o471ZMM+CfXr4rl+7uTrzim F7IQKGLX4uu6m8dgMNbTXsHdieEcz07TLyhiznJ7VwLYaSjc0bR5lvFVmLDn0j4Mdwda LusMkW5Lqvb8ex58INtsVTHdiF0S4s9i0hPR4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=YhQ4Gt5hiW3FAU92xtNxPm3qoPTRKoZVA1SP7ktlek9YBDco3Bmq645jHRMrci8UuU PsaiwKuNksxyE9lvjdWtoK5FpFegnp1Z3WffgnkY6CU+te/tiCnU4OtOQoknknzcfGKR z1kzXQVbkGiM2F2iVPRlYel7Quxk6vnE8HJFE= Received: by 10.142.127.9 with SMTP id z9mr1608359wfc.335.1278099248496; Fri, 02 Jul 2010 12:34:08 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id c23sm1100253rvf.0.2010.07.02.12.34.07 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jul 2010 12:34:07 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 2 Jul 2010 12:33:41 -0700 From: Pyun YongHyeon Date: Fri, 2 Jul 2010 12:33:41 -0700 To: Sean Bruno Message-ID: <20100702193341.GC10862@michelle.cdnetworks.com> References: <1278089690.2469.22.camel@localhost.localdomain> <20100702191110.GA10862@michelle.cdnetworks.com> <1278098663.2469.31.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1278098663.2469.31.camel@localhost.localdomain> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable , "yongari@freebsd.org" Subject: Re: [stable 7] bge() related panic on an HP dl380g3 (32 bit) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 19:34:15 -0000 On Fri, Jul 02, 2010 at 12:24:23PM -0700, Sean Bruno wrote: > On Fri, 2010-07-02 at 12:11 -0700, Pyun YongHyeon wrote: > > On Fri, Jul 02, 2010 at 09:54:50AM -0700, Sean Bruno wrote: > > > Started seeing this panic today from our BSD7 variant here at Yahoo. > > > Our BGE driver is identical to 7stable at this time. Looks like all of > > > these boxes are HP DL380G3 models. I have included the panic and > > > pciconf -lv information. > > > > > > > > > I assume that these machines have a variant of BGE that needs some kind > > > of exception/quirk that I'm unaware of. > > > > > > > Does your bge(4) driver include r208995? > > It did not. I screwed up the report. > > The bge(4) driver under test was from r205616 (we built it in April). > > Did this panic look like the one fixed by r208995? > Yes. > Sean > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:37:22 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA175106566B for ; Fri, 2 Jul 2010 19:37:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 982378FC0A for ; Fri, 2 Jul 2010 19:37:22 +0000 (UTC) Received: by pwj9 with SMTP id 9so841051pwj.13 for ; Fri, 02 Jul 2010 12:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=HwRTmrRGirtoS2Vq5Vl0Lhg+s2QGq3V4sVD4cgDQvek=; b=kwhXXEp3mi0WTXJrJL1wVJ9VyOjfB0m3DxqhrmU8MDuQbW9GGGQ/6QcqHgojTahgg2 ctxyIHPqC1SEcA4Ebz2NLnlr990+gQWQ4aNBLiN7fJFI1wRYLvEFqpHsck2QKiMoBVpP Dn6niC+7N3LqLWVib1R0k1rn8VrPWU+k5g8zY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=sKatFeDFv7QJMT4azgGnzanFYCdjGZl7IJxilxmMk4UQ73Fjbzi7ztIa/lNsH0gZhB 9CjzGTsbjkWoPK2H/sVh/iTfcHEy/2b266VDtKzAwEBrY2Zm6/xSrZJbjIORBT1oslwu sdBKiwMSRk99hUWS85Qwil02KMqwkvhl9xA28= Received: by 10.142.211.5 with SMTP id j5mr1747056wfg.156.1278099442044; Fri, 02 Jul 2010 12:37:22 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id c15sm1101317rvi.11.2010.07.02.12.37.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jul 2010 12:37:21 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 2 Jul 2010 12:36:54 -0700 From: Pyun YongHyeon Date: Fri, 2 Jul 2010 12:36:54 -0700 To: Mike Tancsa Message-ID: <20100702193654.GD10862@michelle.cdnetworks.com> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> <201007021739.o62HdMOU092319@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201007021739.o62HdMOU092319@lava.sentex.ca> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, jfvogel@gmail.com Subject: Re: RELENG_7 em problems (and RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 19:37:23 -0000 On Fri, Jul 02, 2010 at 01:39:22PM -0400, Mike Tancsa wrote: > Hi Jack, > Just a followup to the email below. I now saw what appears > to be the same problem on RELENG_8, but on a different nic and with > VLANs. So not sure if this is a general em problem, a problem > specific to some em NICs, or a TSO problem in general. The issue > seemed to be triggered when I added a new vlan based on > > em3@pci0:14:0:0: class=0x020000 card=0x109a15d9 > chip=0x109a8086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel PRO/1000 PL Network Adaptor (82573L)' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > > pci14: on pcib5 > em3: port 0x6000-0x601f > mem 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 > em3: Using MSI interrupt > em3: [FILTER] > em3: Ethernet address: 00:30:48:9f:eb:81 > > em3: flags=8943 > metric 0 mtu 1500 > options=2098 > ether 00:30:48:9f:eb:81 > inet 10.255.255.254 netmask 0xfffffffc broadcast 10.255.255.255 > media: Ethernet autoselect (1000baseT ) > status: active > > I had to disable tso, rxcsum and txsum in order to see the devices on > the other side of the two vlans trunked off em3. Unfortunately, the > other sides were switches 100km and 500km away so I didnt have any > tcpdump capabilities to diagnose the issue. I had already created > one vlan off this NIC and all was fine. A few weeks later, I added a > new one and I could no longer telnet into the remote switches from > the local machine.... But, I could telnet into the switches from > machines not on the problem box. Hence, it would appear to be a > general TSO issue no ? I disabled tso on the nic (I didnt disable > net.inet.tcp.tso as I forgot about that).. Still nothing. I could > always ping the remote devices, but no tcp services. I then > remembered this issue from before, so I tried disabling tso on the > NIC. Still nothing. Then I disabled rxcsum and txcsum and I could > then telnet into the remote devices. > > This newly observed issue was from a buildworld on Mon Jun 14 > 11:29:12 EDT 2010. > > I will try and recreate the issue locally again to see if I can > trigger the problem on demand. Any thoughts on what it might be ? > Perhaps an issue specific to certain em nics ? > http://www.freebsd.org/cgi/query-pr.cgi?pr=141843 I'm not sure whether you're seeing the same issue though. I didn't have chance to try latest em(4) on stable/7. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:46:39 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0BA91065701 for ; Fri, 2 Jul 2010 19:46:39 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.freebsd.org (Postfix) with ESMTP id B3E3D8FC21 for ; Fri, 2 Jul 2010 19:46:39 +0000 (UTC) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.4/8.14.3) with ESMTP id o62JkbZ1092967; Fri, 2 Jul 2010 15:46:37 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201007021946.o62JkbZ1092967@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 02 Jul 2010 15:46:37 -0400 To: pyunyh@gmail.com From: Mike Tancsa In-Reply-To: <20100702193654.GD10862@michelle.cdnetworks.com> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> <201007021739.o62HdMOU092319@lava.sentex.ca> <20100702193654.GD10862@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org, jfvogel@gmail.com Subject: Re: RELENG_7 em problems (and RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 19:46:40 -0000 At 03:36 PM 7/2/2010, Pyun YongHyeon wrote: >http://www.freebsd.org/cgi/query-pr.cgi?pr=141843 >I'm not sure whether you're seeing the same issue though. >I didn't have chance to try latest em(4) on stable/7. Wow, what a detailed PR! That sure sounds like the issue I am seeing as well. I am just setting up another box to try and recreate the issue ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 20:29:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12DA7106566B for ; Fri, 2 Jul 2010 20:29:18 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id A86088FC0A for ; Fri, 2 Jul 2010 20:29:17 +0000 (UTC) Received: by wwd20 with SMTP id 20so761505wwd.1 for ; Fri, 02 Jul 2010 13:29:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.31.133 with SMTP id y5mr4510874ebc.6.1278102551634; Fri, 02 Jul 2010 13:29:11 -0700 (PDT) Received: by 10.213.9.6 with HTTP; Fri, 2 Jul 2010 13:29:11 -0700 (PDT) X-Originating-IP: [93.203.32.164] In-Reply-To: References: Date: Fri, 2 Jul 2010 22:29:11 +0200 Message-ID: From: "C. P. Ghost" To: "William D. Colburn (Schlake)" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: My kernel panics suck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 20:29:18 -0000 On Fri, Jul 2, 2010 at 9:18 PM, William D. Colburn (Schlake) wrote: > I got my new 8-stable system up, and now I just have recurrent disk > controller failures. =A0The machine can't stay more than about ten > minutes before it panics into a hung kernel, or simple reboots. > Unfortunately, I know the root cause of the panics. =A0If my computer is > sitting on the table, then the kernel doesn't panic. =A0If the computer > is sitting on the desk, then it panics like mad. =A0The table is wooden, > the desk is metal. =A0Of course, I'm also changing power too. =A0On the > table, I use a wall outlet, while on the desk I use my Smart UPS. > Unfortunately, you can't really help me with this. =A0I'm just writing > in out of the hope that I'll get some sympathy for this problem. Yuck...! If you have an electrical insulation problem, and your desk is metal, I'd _really_ urge you to replace your hardware completely, or have it properly insulated by a professional electrician. An electric shock could cause real pain() and panic(). ;-) But seriously, if that's the only reason for the panics, it's a pretty strong hint that you have an electrical problem: when ICs are underpowered, they tend to behave erratically. > -- Schlake -cpghost. --=20 Cordula's Web. http://www.cordula.ws/ From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 23:35:18 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA2F1106564A for ; Fri, 2 Jul 2010 23:35:18 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 973198FC0C for ; Fri, 2 Jul 2010 23:35:18 +0000 (UTC) Received: by iwn35 with SMTP id 35so1801287iwn.13 for ; Fri, 02 Jul 2010 16:35:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=IfODIUjx3YvjaqGKUBKbXidQisKvsHqk1TTG6Zj0dig=; b=irMtWc97M/MFaDBetjADj12b12UsNz4I3SCfF6aL3e+s/pHLmR39XhhgKjdzZTG5Lp 5ZBtFfomqrq948tjEYaKKrm3yygcNSwqyo9fo20YFn3OBsWsRh1WHa6Pc9GAQzqDIXVX u1R6MyJnh1N6G5SYrNmQpDOsolnLDtnEc2OBE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=eO89NpyQ487vOSI/qsOxMCwbCp8+jg4e55hyDTM6vPzEfUnJ4LA1Tspv/3pRPoVuFD +KbTDHQMD9dC9kXWrt3IP2J0uYw0BymgWQWbJMglG2Z92Y5VqLTo+s39yr9uH7i5OrNf PQ4wqllil3RZw2i1aiJupj1gh1TCyqbiO6Iek= Received: by 10.231.60.7 with SMTP id n7mr1521025ibh.60.1278113718223; Fri, 02 Jul 2010 16:35:18 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-128-180.dsl.klmzmi.sbcglobal.net [99.181.128.180]) by mx.google.com with ESMTPS id x6sm5257811ibb.5.2010.07.02.16.35.16 (version=SSLv3 cipher=RC4-MD5); Fri, 02 Jul 2010 16:35:16 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C2E77B2.4080907@dataix.net> Date: Fri, 02 Jul 2010 19:35:14 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.10) Gecko/20100626 Thunderbird MIME-Version: 1.0 To: "C. P. Ghost" References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=89D8547E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, "William D. Colburn \(Schlake\)" Subject: Re: My kernel panics suck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 23:35:19 -0000 On 07/02/2010 16:29, C. P. Ghost wrote: > On Fri, Jul 2, 2010 at 9:18 PM, William D. Colburn (Schlake) > wrote: >> I got my new 8-stable system up, and now I just have recurrent disk >> controller failures. The machine can't stay more than about ten >> minutes before it panics into a hung kernel, or simple reboots. >> Unfortunately, I know the root cause of the panics. If my computer is >> sitting on the table, then the kernel doesn't panic. If the computer >> is sitting on the desk, then it panics like mad. The table is wooden, >> the desk is metal. Of course, I'm also changing power too. On the >> table, I use a wall outlet, while on the desk I use my Smart UPS. >> Unfortunately, you can't really help me with this. I'm just writing >> in out of the hope that I'll get some sympathy for this problem. > > Yuck...! If you have an electrical insulation problem, and your desk > is metal, I'd _really_ urge you to replace your hardware completely, > or have it properly insulated by a professional electrician. An electric > shock could cause real pain() and panic(). ;-) > > But seriously, if that's the only reason for the panics, it's a pretty > strong hint that you have an electrical problem: when ICs are > underpowered, they tend to behave erratically. > >> -- Schlake > > -cpghost. > Adding to this, though I find it unlikely but worth mentioning but you could be grounding out to a already charged surface through a screw in the case (laptop/desktop), check the bottom and cover up anything you find with black electrical tape and try again. Another route would be to grab a multimeter and test the metal table for a positive ? source. If that metal table also happens to be screwed down to the floor then take all the screws out as one maybe more could be running across some weird current. Regards, -- +-+-+-+-+-+ |j|h|e|l|l| +-+-+-+-+-+ From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 23:49:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7285D1065670 for ; Fri, 2 Jul 2010 23:49:48 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [76.96.62.32]) by mx1.freebsd.org (Postfix) with ESMTP id 1F0498FC08 for ; Fri, 2 Jul 2010 23:49:47 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta03.westchester.pa.mail.comcast.net with comcast id dBCb1e0070bG4ec53BpoUL; Fri, 02 Jul 2010 23:49:48 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta03.westchester.pa.mail.comcast.net with comcast id dBpm1e00D3S48mS3PBpngc; Fri, 02 Jul 2010 23:49:48 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 6752C9B425; Fri, 2 Jul 2010 16:49:45 -0700 (PDT) Date: Fri, 2 Jul 2010 16:49:45 -0700 From: Jeremy Chadwick To: jhell Message-ID: <20100702234945.GA45713@icarus.home.lan> References: <4C2E77B2.4080907@dataix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C2E77B2.4080907@dataix.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org, "C. P. Ghost" , "William D. Colburn \(Schlake\)" Subject: Re: My kernel panics suck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 23:49:48 -0000 On Fri, Jul 02, 2010 at 07:35:14PM -0400, jhell wrote: > On 07/02/2010 16:29, C. P. Ghost wrote: > > On Fri, Jul 2, 2010 at 9:18 PM, William D. Colburn (Schlake) > > wrote: > >> I got my new 8-stable system up, and now I just have recurrent disk > >> controller failures. The machine can't stay more than about ten > >> minutes before it panics into a hung kernel, or simple reboots. > >> Unfortunately, I know the root cause of the panics. If my computer is > >> sitting on the table, then the kernel doesn't panic. If the computer > >> is sitting on the desk, then it panics like mad. The table is wooden, > >> the desk is metal. Of course, I'm also changing power too. On the > >> table, I use a wall outlet, while on the desk I use my Smart UPS. > >> Unfortunately, you can't really help me with this. I'm just writing > >> in out of the hope that I'll get some sympathy for this problem. > > > > Yuck...! If you have an electrical insulation problem, and your desk > > is metal, I'd _really_ urge you to replace your hardware completely, > > or have it properly insulated by a professional electrician. An electric > > shock could cause real pain() and panic(). ;-) > > > > But seriously, if that's the only reason for the panics, it's a pretty > > strong hint that you have an electrical problem: when ICs are > > underpowered, they tend to behave erratically. > > > >> -- Schlake > > > > -cpghost. > > > > Adding to this, though I find it unlikely but worth mentioning but you > could be grounding out to a already charged surface through a screw in > the case (laptop/desktop), check the bottom and cover up anything you > find with black electrical tape and try again. Another route would be to > grab a multimeter and test the metal table for a positive ? source. If > that metal table also happens to be screwed down to the floor then take > all the screws out as one maybe more could be running across some weird > current. I'm a little surprised everyone's focused on the desk/grounding rather than the UPS. The OP doesn't state whether or not he's using a laptop either (it matters). I'm not denying improper grounding could cause issues, but I'd expect to hear of the OP getting shocked or something along those lines rather than "my storage controller acts silly". Ripple or dirty power coming from a UPS -- because not all of them clean things up -- could cause all sorts of chaos hardware-wise too, and in some cases permanent damage. -- | Jeremy Chadwick jdc@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-stable@FreeBSD.ORG Sat Jul 3 00:40:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0BAF1065672 for ; Sat, 3 Jul 2010 00:40:08 +0000 (UTC) (envelope-from schlake@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 81F3A8FC0A for ; Sat, 3 Jul 2010 00:40:08 +0000 (UTC) Received: by vws6 with SMTP id 6so4036785vws.13 for ; Fri, 02 Jul 2010 17:40:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=jEKgKxHIq+qIW0E9CPl/R+vZWmM53lNtSQWwSR65oUA=; b=REOMnKDCBxeWTAeQDl9uMyhET4cedYjHYr77Wd/LN52lf2rCunSmsmKg4BDG1LoZ2S h/Ou+GlTsVS58KhUqzKg06Hb0uLzH8XJ2JV4QnoQkrkNNTNEQo+VypbdNoxqZvt3NT9e Z2jQIs7gQ9ym9KMFH16zPBLcEuGTnH8n10BZk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KMDTNzki8AJOz+AEKmK2yIcGVHxaNPOYx6zMi6XmsSmDVP6cc4l3h4xRQTMHnml/NV xaK6PtbAlLLYaDyRtVIf9z4YMsmKIObCar1BoFBHtPi2fUnmjiWEjcHCsgvM+MyUt7Yc 5/2M5tCQSgR4vLW6CGdDoXlEp6dcj41xbtARY= MIME-Version: 1.0 Received: by 10.220.59.202 with SMTP id m10mr833135vch.59.1278117603290; Fri, 02 Jul 2010 17:40:03 -0700 (PDT) Received: by 10.220.183.6 with HTTP; Fri, 2 Jul 2010 17:40:03 -0700 (PDT) In-Reply-To: <20100702234945.GA45713@icarus.home.lan> References: <4C2E77B2.4080907@dataix.net> <20100702234945.GA45713@icarus.home.lan> Date: Fri, 2 Jul 2010 18:40:03 -0600 Message-ID: From: "William D. Colburn (Schlake)" To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Cc: "C. P. Ghost" , freebsd-stable@freebsd.org Subject: Re: My kernel panics suck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 00:40:09 -0000 On Fri, Jul 2, 2010 at 5:49 PM, Jeremy Chadwick wrote: > Ripple or dirty power coming from a UPS -- because not all of them clean > things up -- could cause all sorts of chaos hardware-wise too, and in > some cases permanent damage. The UPS is actually my biggest suspect. It was an expensive one, but it is well over five years old now. As I told someone privately, though, I have a broken ankle, and this is my disk server with about 9T of spinning disk in it. It is hard for me to move currently. -- -- Schlake From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 01:51:30 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7516E106566B for ; Sat, 3 Jul 2010 01:51:30 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 280ED8FC16 for ; Sat, 3 Jul 2010 01:51:29 +0000 (UTC) Received: by qyk7 with SMTP id 7so730283qyk.13 for ; Fri, 02 Jul 2010 18:51:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JSvWqGmvxL4xgxhkG/b0afIVKZeR1gl3BCGQCH8mY9A=; b=kh4q+hBV4j3lG9L6q+YmzSgnZLgVDcasSs29HvI5HWZlzTT369i6QIGbzyrp7tLbc1 Abp5LFb9Nt2RniNYAxmaW9nZ2QCNM0Q9CFnp+/pBNX3uSu9CxmXNbA2lTXARzl0win+W j2g+mvTl1XJbFZDxdBx7E5Oouc5VCdFxU9aKo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NsXJkIzyv1thZq9sBStXsGnKP5JxBhyphy9VdoFrEo4ghjQk8zTBys4jOr9H3QnNBv lBb2yuS1KVkqbOkkUI8ssm5RYaEaMFA8Pn80KwcU3T2eG/g9BLx/JZ8wP6ph7EqhSi3G T+66c1Q32ZOUduQLipZDk66BJcmhpnJCJ7y5A= MIME-Version: 1.0 Received: by 10.224.10.204 with SMTP id q12mr935257qaq.134.1278121882337; Fri, 02 Jul 2010 18:51:22 -0700 (PDT) Received: by 10.229.192.201 with HTTP; Fri, 2 Jul 2010 18:51:22 -0700 (PDT) In-Reply-To: References: <4C2E77B2.4080907@dataix.net> <20100702234945.GA45713@icarus.home.lan> Date: Fri, 2 Jul 2010 18:51:22 -0700 Message-ID: From: Garrett Cooper To: "William D. Colburn (Schlake)" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, "C. P. Ghost" , Jeremy Chadwick Subject: Re: My kernel panics suck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 01:51:30 -0000 On Fri, Jul 2, 2010 at 5:40 PM, William D. Colburn (Schlake) wrote: > On Fri, Jul 2, 2010 at 5:49 PM, Jeremy Chadwick > wrote: >> Ripple or dirty power coming from a UPS -- because not all of them clean >> things up -- could cause all sorts of chaos hardware-wise too, and in >> some cases permanent damage. > > The UPS is actually my biggest suspect. =A0It was an expensive one, but > it is well over five years old now. =A0As I told someone privately, > though, I have a broken ankle, and this is my disk server with about > 9T of spinning disk in it. =A0It is hard for me to move currently. If your system // storage controller has an event log (IPMI/RAID?) I would check to see what's reported by the system at the time of failure. Some servers also record events into the BMC (going back to IPMI) and display trouble codes on the LCDs (like Dell). It could be an issue with the power supply as well -- see whether or not you can spin up the disks a little slower (there are knobs in the kernel you can set to slow down detection so things work), or take some of the RAID members/volumes offline before booting up so you can power them down safely? If your system has a redundant power supply, try using the other one to see whether or not the issue persists. As for ruling out the UPS, try plugging the machine straight into the wall -- does it work? HTH, -Garrett From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 08:05:30 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C029A106566B for ; Sat, 3 Jul 2010 08:05:30 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from stith.flb.omnilan.net (stith.flb.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 255908FC1E for ; Sat, 3 Jul 2010 08:05:29 +0000 (UTC) Received: from titan.flintsbach.schmalzbauer.de (titan.flintsbach.schmalzbauer.de [172.21.1.150]) (authenticated bits=0) by stith.flb.omnilan.net (8.13.8/8.13.8) with ESMTP id o6385P1j057256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Jul 2010 10:05:28 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <4C2EEF3E.2010008@omnilan.de> Date: Sat, 03 Jul 2010 10:05:18 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Thunderbird 2.0.0.23 (X11/20090906) MIME-Version: 1.0 To: freebsd-stable X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1DE569796D978C419DB213EC" Subject: selective jail restriction controlling in rc.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 08:05:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1DE569796D978C419DB213EC Content-Type: multipart/mixed; boundary="------------020206070603080009060807" This is a multi-part message in MIME format. --------------020206070603080009060807 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Hello all, I very much liked the possibillity to easily manage jails via rc.conf. Unfortunately I was missing some features. First, there are many security.jail.allow_* sysctl which didn't get=20 attention. Second; I needed to allow different things on different jails. For=20 examply only one distinct jail should habe sysvIPC. Please find attached a patch wich extends rc.d to my needs. Some jail_start() modifications were neccessary and some cleanups could=20 be done in the "Configuring jails:" section (not needed any more) amd in = the _ip_multi processing, since that's not needed any more. One have to seperatly define ip4 and ip6 addresses. The can be with or=20 without mask, single oder comma seperated list, doesn't matter, thanks=20 to the jail_handle_ips_option() coder, it just works :) Thanks, -Harry --------------020206070603080009060807 Content-Type: text/plain; name="jail-allow-selectables.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="jail-allow-selectables.patch" --- src/etc/defaults/rc.conf 2010-06-28 19:22:08.000000000 +0200 +++ src/etc/defaults/rc.conf 2010-07-03 09:54:55.000000000 +0200 @@ -642,8 +642,13 @@ jail_enable=3D"NO" # Set to NO to disable starting of any jails jail_list=3D"" # Space separated list of names of jails jail_set_hostname_allow=3D"YES" # Allow root user in a jail to change it= s hostname -jail_socket_unixiproute_only=3D"YES" # Route only TCP/IP within a jail jail_sysvipc_allow=3D"NO" # Allow SystemV IPC use from within a jail +jail_socket_unixiproute_only=3D"YES" # Route only TCP/IP within a jail +jail_raw_sockets_allow=3D"NO" # Prison root can create raw sockets +jail_chflags_allow=3D"NO" # Processes in jail can alter system file flag= s +jail_mount_allow=3D"NO" # Processes in jail can mount/unmount jail-frien= dly file systems +jail_quotas_allow=3D"NO" # The prison root may administer quotas on the = jail's filesystem(s) +socket_af_allow=3D"NO" # Sockets within a jail are normally restricted t= o IPv4, IPv6, local (UNIX), and route. =20 # # To use rc's built-in jail infrastructure create entries for @@ -672,6 +677,14 @@ #jail_example_procfs_enable=3D"NO" # mount procfs in jail #jail_example_mount_enable=3D"NO" # mount/umount jail's fs #jail_example_fstab=3D"" # fstab(5) for mount/umount +#jail_example_allow_set_hostname=3D"NO" # This jail can set hostname +#jail_example_allow_sysvipc=3D"NO" # This jail can use SystemV IPC +#jail_example_allow_raw_sockets=3D"NO" # This jail can create raw socke= ts (ping) +#jail_example_allow_chflags=3D"NO" # This jail can alter it's filesyste= m flags +#jail_example_allow_mount=3D"NO" # This jail can mount jail friendly f= ilesystems +#jail_example_allow_quotas=3D"NO" # This jail can modify quotas on it'= s filesystems +#jail_example_allow_socket_af=3D"NO" # This jail can use other protocol= stacks than IP4, IP6 and local + #jail_example_flags=3D"-l -U root" # flags for jail(8) =20 ############################################################## --- src/etc/rc.d/jail 2010-06-28 19:22:11.000000000 +0200 +++ src/etc/rc.d/jail 2010-07-03 10:02:34.000000000 +0200 @@ -21,6 +21,8 @@ start_cmd=3D"jail_start" stop_cmd=3D"jail_stop" =20 +jail_restrictions=3D"set_hostname sysvipc raw_sockets chflags mount quot= as socket_af" + # init_variables _j # Initialize the various jail variables for jail _j. # @@ -38,7 +40,8 @@ _fdescdir=3D"${_devdir}/fd" _procdir=3D"${_rootdir}/proc" eval _hostname=3D\"\$jail_${_j}_hostname\" - eval _ip=3D\"\$jail_${_j}_ip\" + eval _ip4=3D\"\$jail_${_j}_ip4\" + eval _ip6=3D\"\$jail_${_j}_ip6\" eval _interface=3D\"\${jail_${_j}_interface:-${jail_interface}}\" eval _exec=3D\"\$jail_${_j}_exec\" =20 @@ -122,8 +125,9 @@ debug "$_j procfs enable: $_procfs" debug "$_j mount enable: $_mount" debug "$_j hostname: $_hostname" - debug "$_j ip: $_ip" - jail_show_addresses ${_j} + debug "$_j ip4: $_ip4" + debug "$_j ip6: $_ip6" +# jail_show_addresses ${_j} debug "$_j interface: $_interface" debug "$_j fib: $_fib" debug "$_j root: $_rootdir" @@ -347,27 +351,27 @@ # Debug print the input for the given _multi aliases # for a jail for init_variables(). # -jail_show_addresses() -{ - local _j _type alias - _j=3D"$1" - alias=3D0 - - if [ -z "${_j}" ]; then - warn "jail_show_addresses: you must specify a jail" - return - fi - - while : ; do - eval _addr=3D\"\$jail_${_j}_ip_multi${alias}\" - if [ -n "${_addr}" ]; then - debug "${_j} ip_multi${alias}: $_addr" - alias=3D$((${alias} + 1)) - else - break - fi - done -} +#jail_show_addresses() +#{ +# local _j _type alias +# _j=3D"$1" +# alias=3D0 +# +# if [ -z "${_j}" ]; then +# warn "jail_show_addresses: you must specify a jail" +# return +# fi +# +# while : ; do +# eval _addr=3D\"\$jail_${_j}_ip_multi${alias}\" +# if [ -n "${_addr}" ]; then +# debug "${_j} ip_multi${alias}: $_addr" +# alias=3D$((${alias} + 1)) +# else +# break +# fi +# done +#} =20 # jail_extract_address argument # The second argument is the string from one of the _ip @@ -481,20 +485,26 @@ *) ;; esac =20 - # Append address to list of addresses for the jail command. - case "${_addrl}" in - "") _addrl=3D"${_addr}" ;; - *) _addrl=3D"${_addrl},${_addr}" ;; - esac - # Configure interface alias if requested by a given interface # and if we could correctly parse everything. case "${_iface}" in "") continue ;; esac case "${_type}" in - inet) ;; - inet6) ;; + inet) {=09 + # Append address to list of addresses for the jail command. + case "${_addrl4}" in + "") _addrl4=3D"${_addr}" ;; + *) _addrl4=3D"${_addrl4},${_addr}" ;; + esac + };; + inet6) { + # Append address to list of addresses for the jail command. + case "${_addrl6}" in + "") _addrl6=3D"${_addr}" ;; + *) _addrl6=3D"${_addrl6},${_addr}" ;; + esac + };; *) warn "Could not determine address family. Not going" \ "to ${_action} address '${_addr}' for ${_jail}." continue @@ -531,18 +541,18 @@ esac =20 # Handle addresses. - jail_handle_ips_option ${_action} "${_ip}" + jail_handle_ips_option ${_action} "${_ip4},${_ip6}" # Handle jail_xxx_ip_multi - alias=3D0 - while : ; do - eval _x=3D\"\$jail_${_jail}_ip_multi${alias}\" - case "${_x}" in - "") break ;; - *) jail_handle_ips_option ${_action} "${_x}" - alias=3D$((${alias} + 1)) - ;; - esac - done +# alias=3D0 +# while : ; do +# eval _x=3D\"\$jail_${_jail}_ip4_multi${alias}\" +# case "${_x}" in +# "") break ;; +# *) jail_handle_ips_option ${_action} "${_x}" +# alias=3D$((${alias} + 1)) +# ;; +# esac +# done } =20 jail_start() @@ -566,7 +576,8 @@ echo -n " [${_hostname} already running (/var/run/jail_${_jail}.id ex= ists)]" continue; fi - _addrl=3D"" + _addrl4=3D"" + _addrl6=3D"" jail_ips "add" if [ -n "${_fib}" ]; then _setfib=3D"setfib -F '${_fib}'" @@ -625,6 +636,15 @@ fi fi fi + _j_allow_parms=3D"" + for relax in ${jail_restrictions}; do + eval _param_allow=3D\"\${jail_${_jail}_allow_${relax}:-\${jail_allow_= $relax}}\" + [ -z "${_param_allow}" ] && _param_allow=3D"NO" + checkyesno _param_allow && \ + _j_allow_parms=3D"${_j_allow_parms}allow.${relax}=3D1 "=20 + debug "$_jail _allow_${relax}: $_param_allow" + done + debug "$_jail selectiv relaxation: $_j_allow_parms" _tmp_jail=3D${_tmp_dir}/jail.$$ =20 i=3D0 @@ -634,9 +654,10 @@ ${out} i=3D$((i + 1)) done - - eval ${_setfib} jail ${_flags} -i ${_rootdir} ${_hostname} \ - \"${_addrl}\" ${_exec_start} > ${_tmp_jail} 2>&1 + =09 + eval ${_setfib} jail ${_flags} -i -c name=3D${_jail}\ + path=3D${_rootdir} host.hostname=3D${_hostname} \ + ip4.addr=3D${_addrl4} ip6.addr=3D${_addrl6} ${_j_allow_parms} command= =3D${_exec_start} > ${_tmp_jail} 2>&1 =20 if [ "$?" -eq 0 ] ; then _jail_id=3D$(head -1 ${_tmp_jail}) --------------020206070603080009060807-- --------------enig1DE569796D978C419DB213EC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkwu70UACgkQLDqVQ9VXb8g/hQCfZB01buby15Zku8XaWwphuL6V dFoAoLAsl8Jv7TQWbvmE8v1LCfqOQ2lz =hEYV -----END PGP SIGNATURE----- --------------enig1DE569796D978C419DB213EC-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 08:10:16 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF982106566C for ; Sat, 3 Jul 2010 08:10:16 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from stith.flb.omnilan.net (stith.flb.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 34B378FC08 for ; Sat, 3 Jul 2010 08:10:15 +0000 (UTC) Received: from titan.flintsbach.schmalzbauer.de (titan.flintsbach.schmalzbauer.de [172.21.1.150]) (authenticated bits=0) by stith.flb.omnilan.net (8.13.8/8.13.8) with ESMTP id o638AEGJ057319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Jul 2010 10:10:15 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <4C2EF065.2020208@omnilan.de> Date: Sat, 03 Jul 2010 10:10:13 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Thunderbird 2.0.0.23 (X11/20090906) MIME-Version: 1.0 To: freebsd-stable References: <4C2EEF3E.2010008@omnilan.de> In-Reply-To: <4C2EEF3E.2010008@omnilan.de> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8E59990CE9C8552FBBC6ACE4" Subject: Re: selective jail restriction controlling in rc.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 08:10:17 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8E59990CE9C8552FBBC6ACE4 Content-Type: multipart/mixed; boundary="------------010100070009070004040306" This is a multi-part message in MIME format. --------------010100070009070004040306 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Harald Schmalzbauer schrieb am 03.07.2010 10:05 (localtime): =2E.. > One have to seperatly define ip4 and ip6 addresses. The can be with or = > without mask, single oder comma seperated list, doesn't matter, thanks = > to the jail_handle_ips_option() coder, it just works :) I forgot to change that in defults/rc.conf. Please find attached the corrected version. -Harry --------------010100070009070004040306 Content-Type: text/plain; name="jail-allow-selectables.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="jail-allow-selectables.patch" --- src/etc/defaults/rc.conf 2010-06-28 19:22:08.000000000 +0200 +++ src/etc/defaults/rc.conf 2010-07-03 10:08:31.000000000 +0200 @@ -642,8 +642,13 @@ jail_enable=3D"NO" # Set to NO to disable starting of any jails jail_list=3D"" # Space separated list of names of jails jail_set_hostname_allow=3D"YES" # Allow root user in a jail to change it= s hostname -jail_socket_unixiproute_only=3D"YES" # Route only TCP/IP within a jail jail_sysvipc_allow=3D"NO" # Allow SystemV IPC use from within a jail +jail_socket_unixiproute_only=3D"YES" # Route only TCP/IP within a jail +jail_raw_sockets_allow=3D"NO" # Prison root can create raw sockets +jail_chflags_allow=3D"NO" # Processes in jail can alter system file flag= s +jail_mount_allow=3D"NO" # Processes in jail can mount/unmount jail-frien= dly file systems +jail_quotas_allow=3D"NO" # The prison root may administer quotas on the = jail's filesystem(s) +socket_af_allow=3D"NO" # Sockets within a jail are normally restricted t= o IPv4, IPv6, local (UNIX), and route. =20 # # To use rc's built-in jail infrastructure create entries for @@ -658,8 +663,8 @@ #jail_example_hostname=3D"default.domain.com" # Jail's hostname #jail_example_interface=3D"" # Jail's interface variable to create IP = aliases on #jail_example_fib=3D"0" # Routing table for setfib(1) -#jail_example_ip=3D"192.0.2.10,2001:db8::17" # Jail's primary IPv4 and I= Pv6 address -#jail_example_ip_multi0=3D"2001:db8::10" # and another IPv6 address +#jail_example_ip4=3D"192.0.2.10/24,10.1.2.3" # Jail's IPv4 address(es) +#jail_example_ip6=3D"2001:db8::10,fec0::0:1:2:3" # Jail's IPv6 address(= es) #jail_example_exec_start=3D"/bin/sh /etc/rc" # command to execute in ja= il for starting #jail_example_exec_afterstart0=3D"/bin/sh command" # command to execute = after the one for # starting the jail. More than one can be @@ -672,6 +677,14 @@ #jail_example_procfs_enable=3D"NO" # mount procfs in jail #jail_example_mount_enable=3D"NO" # mount/umount jail's fs #jail_example_fstab=3D"" # fstab(5) for mount/umount +#jail_example_allow_set_hostname=3D"NO" # This jail can set hostname +#jail_example_allow_sysvipc=3D"NO" # This jail can use SystemV IPC +#jail_example_allow_raw_sockets=3D"NO" # This jail can create raw socke= ts (ping) +#jail_example_allow_chflags=3D"NO" # This jail can alter it's filesyste= m flags +#jail_example_allow_mount=3D"NO" # This jail can mount jail friendly f= ilesystems +#jail_example_allow_quotas=3D"NO" # This jail can modify quotas on it'= s filesystems +#jail_example_allow_socket_af=3D"NO" # This jail can use other protocol= stacks than IP4, IP6 and local + #jail_example_flags=3D"-l -U root" # flags for jail(8) =20 ############################################################## --- src/etc/rc.d/jail 2010-06-28 19:22:11.000000000 +0200 +++ src/etc/rc.d/jail 2010-07-03 10:02:34.000000000 +0200 @@ -21,6 +21,8 @@ start_cmd=3D"jail_start" stop_cmd=3D"jail_stop" =20 +jail_restrictions=3D"set_hostname sysvipc raw_sockets chflags mount quot= as socket_af" + # init_variables _j # Initialize the various jail variables for jail _j. # @@ -38,7 +40,8 @@ _fdescdir=3D"${_devdir}/fd" _procdir=3D"${_rootdir}/proc" eval _hostname=3D\"\$jail_${_j}_hostname\" - eval _ip=3D\"\$jail_${_j}_ip\" + eval _ip4=3D\"\$jail_${_j}_ip4\" + eval _ip6=3D\"\$jail_${_j}_ip6\" eval _interface=3D\"\${jail_${_j}_interface:-${jail_interface}}\" eval _exec=3D\"\$jail_${_j}_exec\" =20 @@ -122,8 +125,9 @@ debug "$_j procfs enable: $_procfs" debug "$_j mount enable: $_mount" debug "$_j hostname: $_hostname" - debug "$_j ip: $_ip" - jail_show_addresses ${_j} + debug "$_j ip4: $_ip4" + debug "$_j ip6: $_ip6" +# jail_show_addresses ${_j} debug "$_j interface: $_interface" debug "$_j fib: $_fib" debug "$_j root: $_rootdir" @@ -347,27 +351,27 @@ # Debug print the input for the given _multi aliases # for a jail for init_variables(). # -jail_show_addresses() -{ - local _j _type alias - _j=3D"$1" - alias=3D0 - - if [ -z "${_j}" ]; then - warn "jail_show_addresses: you must specify a jail" - return - fi - - while : ; do - eval _addr=3D\"\$jail_${_j}_ip_multi${alias}\" - if [ -n "${_addr}" ]; then - debug "${_j} ip_multi${alias}: $_addr" - alias=3D$((${alias} + 1)) - else - break - fi - done -} +#jail_show_addresses() +#{ +# local _j _type alias +# _j=3D"$1" +# alias=3D0 +# +# if [ -z "${_j}" ]; then +# warn "jail_show_addresses: you must specify a jail" +# return +# fi +# +# while : ; do +# eval _addr=3D\"\$jail_${_j}_ip_multi${alias}\" +# if [ -n "${_addr}" ]; then +# debug "${_j} ip_multi${alias}: $_addr" +# alias=3D$((${alias} + 1)) +# else +# break +# fi +# done +#} =20 # jail_extract_address argument # The second argument is the string from one of the _ip @@ -481,20 +485,26 @@ *) ;; esac =20 - # Append address to list of addresses for the jail command. - case "${_addrl}" in - "") _addrl=3D"${_addr}" ;; - *) _addrl=3D"${_addrl},${_addr}" ;; - esac - # Configure interface alias if requested by a given interface # and if we could correctly parse everything. case "${_iface}" in "") continue ;; esac case "${_type}" in - inet) ;; - inet6) ;; + inet) {=09 + # Append address to list of addresses for the jail command. + case "${_addrl4}" in + "") _addrl4=3D"${_addr}" ;; + *) _addrl4=3D"${_addrl4},${_addr}" ;; + esac + };; + inet6) { + # Append address to list of addresses for the jail command. + case "${_addrl6}" in + "") _addrl6=3D"${_addr}" ;; + *) _addrl6=3D"${_addrl6},${_addr}" ;; + esac + };; *) warn "Could not determine address family. Not going" \ "to ${_action} address '${_addr}' for ${_jail}." continue @@ -531,18 +541,18 @@ esac =20 # Handle addresses. - jail_handle_ips_option ${_action} "${_ip}" + jail_handle_ips_option ${_action} "${_ip4},${_ip6}" # Handle jail_xxx_ip_multi - alias=3D0 - while : ; do - eval _x=3D\"\$jail_${_jail}_ip_multi${alias}\" - case "${_x}" in - "") break ;; - *) jail_handle_ips_option ${_action} "${_x}" - alias=3D$((${alias} + 1)) - ;; - esac - done +# alias=3D0 +# while : ; do +# eval _x=3D\"\$jail_${_jail}_ip4_multi${alias}\" +# case "${_x}" in +# "") break ;; +# *) jail_handle_ips_option ${_action} "${_x}" +# alias=3D$((${alias} + 1)) +# ;; +# esac +# done } =20 jail_start() @@ -566,7 +576,8 @@ echo -n " [${_hostname} already running (/var/run/jail_${_jail}.id ex= ists)]" continue; fi - _addrl=3D"" + _addrl4=3D"" + _addrl6=3D"" jail_ips "add" if [ -n "${_fib}" ]; then _setfib=3D"setfib -F '${_fib}'" @@ -625,6 +636,15 @@ fi fi fi + _j_allow_parms=3D"" + for relax in ${jail_restrictions}; do + eval _param_allow=3D\"\${jail_${_jail}_allow_${relax}:-\${jail_allow_= $relax}}\" + [ -z "${_param_allow}" ] && _param_allow=3D"NO" + checkyesno _param_allow && \ + _j_allow_parms=3D"${_j_allow_parms}allow.${relax}=3D1 "=20 + debug "$_jail _allow_${relax}: $_param_allow" + done + debug "$_jail selectiv relaxation: $_j_allow_parms" _tmp_jail=3D${_tmp_dir}/jail.$$ =20 i=3D0 @@ -634,9 +654,10 @@ ${out} i=3D$((i + 1)) done - - eval ${_setfib} jail ${_flags} -i ${_rootdir} ${_hostname} \ - \"${_addrl}\" ${_exec_start} > ${_tmp_jail} 2>&1 + =09 + eval ${_setfib} jail ${_flags} -i -c name=3D${_jail}\ + path=3D${_rootdir} host.hostname=3D${_hostname} \ + ip4.addr=3D${_addrl4} ip6.addr=3D${_addrl6} ${_j_allow_parms} command= =3D${_exec_start} > ${_tmp_jail} 2>&1 =20 if [ "$?" -eq 0 ] ; then _jail_id=3D$(head -1 ${_tmp_jail}) --------------010100070009070004040306-- --------------enig8E59990CE9C8552FBBC6ACE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkwu8GUACgkQLDqVQ9VXb8jVQQCgnncGnjHvT7MnbZ5iis4QrX8G YKQAn0NxIVxGAldo9jwgulIK0WiHXPT2 =dig7 -----END PGP SIGNATURE----- --------------enig8E59990CE9C8552FBBC6ACE4-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 13:02:51 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A535A106566C; Sat, 3 Jul 2010 13:02:51 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (unknown [IPv6:2001:380:e06:127::53]) by mx1.freebsd.org (Postfix) with ESMTP id 6A3288FC08; Sat, 3 Jul 2010 13:02:51 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id CB1E678C3B; Sat, 3 Jul 2010 22:02:37 +0900 (JST) Received: from artemis (unknown [192.168.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTP id B8AC278C34; Sat, 3 Jul 2010 22:02:37 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: References: <1931AE1113EC4A8983B8A52A2A1966C2@ad.peach.ne.jp> <6BC2B2FBAFFA4C26A46977F121B707E1@ad.peach.ne.jp> In-Reply-To: <6BC2B2FBAFFA4C26A46977F121B707E1@ad.peach.ne.jp> Date: Sat, 3 Jul 2010 21:57:58 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: [Need Help]isboot (iSCSI boot driver) version 0.2.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 13:02:51 -0000 Hi all, I uploaded isboot 0.2.1. Now isboot supports R2T command and non-immediate mode. I believe that the compatibility of iSCSI target is improved. Please check it with your iSCSI target and NIC. Also this version supports task queue, which improves performance. My test machine got read 74MB/s, write 60MB/s (at bs=1m). Notes/Known Issues/Limitations: FreeBSD can't use transfer length > 64KB. It seems CAM tag is used only 2 of 64 tags. I don't know a reason, but MAXPHYS limit? How to build/upgrade: # cd /usr/src # tar xvf /path/to/iscsi-2.2.4.tar.gz # tar xvf /path/to/isboot-0.2.1.tar.gz # make buildkernel # make installkernel or # cd /usr/src/sys/modules/iscsi/isboot # make obj # make depend # make clean # make all # make install After installation, please reboot the server to take effect. Confirm the log shows "iSCSI boot driver version 0.2.1". What's new?: * support CHAP/Mutual CHAP * add task queue * R2T command and non-immediate mode Performance(without digest): # dd if=/dev/da4 of=/dev/null bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 14.374117 secs (74699672 bytes/sec) # dd if=/dev/zero of=/dev/da4 bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 17.823493 secs (60243064 bytes/sec) Download links: http://www.peach.ne.jp/archives/isboot/isboot-0.2.1.tar.gz Download links(for testing purpose only): http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC2-amd64-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC2-i386-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh gPXE + isboot + istgt(for reference): http://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004432.html Previous versions: http://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004431.html http://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html I hope this helps you. Enjoy it. Daisuke Aoyama From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 15:05:07 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23013106564A; Sat, 3 Jul 2010 15:05:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id D249E8FC16; Sat, 3 Jul 2010 15:05:06 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 38D8741C74D; Sat, 3 Jul 2010 17:05:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id Fo66ipqjIWuD; Sat, 3 Jul 2010 17:05:05 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 6B4FB41C756; Sat, 3 Jul 2010 17:05:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 169034448EC; Sat, 3 Jul 2010 15:02:19 +0000 (UTC) Date: Sat, 3 Jul 2010 15:02:19 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Harald Schmalzbauer In-Reply-To: <4C2EF065.2020208@omnilan.de> Message-ID: <20100703145827.E14969@maildrop.int.zabbadoz.net> References: <4C2EEF3E.2010008@omnilan.de> <4C2EF065.2020208@omnilan.de> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-jail@FreeBSD.org, freebsd-stable Subject: Re: selective jail restriction controlling in rc.conf X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-jail@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 15:05:07 -0000 On Sat, 3 Jul 2010, Harald Schmalzbauer wrote: Hallo Harald, > Harald Schmalzbauer schrieb am 03.07.2010 10:05 (localtime): > ... >> One have to seperatly define ip4 and ip6 addresses. The can be with or >> without mask, single oder comma seperated list, doesn't matter, thanks to >> the jail_handle_ips_option() coder, it just works :) > > I forgot to change that in defults/rc.conf. > Please find attached the corrected version. there is currently an ongoing discussion about jail configuration on the freebsd-jail@ mailing list: http://lists.freebsd.org/pipermail/freebsd-jail/2010-June/thread.html#1308 I think your comments (and patches) are better sent there, rather than to stable@. Gruesse, Bjern -- Bjoern A. Zeeb From August on I will have a life. It's now up to you to do the maths and count to 64. -- Bondorf, Germany, 14th June 2010 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 20:20:36 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8996106564A for ; Sat, 3 Jul 2010 20:20:36 +0000 (UTC) (envelope-from crwhipp@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8CBD58FC2B for ; Sat, 3 Jul 2010 20:20:36 +0000 (UTC) Received: by pzk12 with SMTP id 12so818706pzk.13 for ; Sat, 03 Jul 2010 13:20:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=wnDyuVLW/zKxMINAxYW/D08UicIMp3p1qubOd10Dnnk=; b=pSVEesVkgY/xdNv6AZsusy0YxlQBPgxecYTw1gkYR/oOToDHOXv8mSsWj0t8ED1Tta Pp6w2IUFFi3oCkWEXLGd7MCdiGNkK7Ic8we3XyfT0QxGbN799UoEpvNkly2ET0cBrKfm PLudXr/aEg0jm4QISQalCdAyil4+KcQd4AeXw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=FMdrM2kMGSaviqAIiVOecqepK5NUokbSI+qT0GRKAfHnmF55yefP7u2PNZBHXlIFJW zJ0EjGDueIYLnI9WvL3GJFgMrcuDKhdyX7MH6haSkdxGceAaD+F+DcqJfFlmuzJXv7WM vksKHYexHlY4jrhxe4Fw7kE0ecD7McJ4WZwlw= Received: by 10.114.92.1 with SMTP id p1mr760034wab.134.1278186564785; Sat, 03 Jul 2010 12:49:24 -0700 (PDT) Received: from [192.168.0.50] (174-26-24-250.phnx.qwest.net [174.26.24.250]) by mx.google.com with ESMTPS id d38sm33169345wam.20.2010.07.03.12.49.23 (version=SSLv3 cipher=RC4-MD5); Sat, 03 Jul 2010 12:49:23 -0700 (PDT) Message-ID: <4C2F946C.8090009@gmail.com> Date: Sat, 03 Jul 2010 12:50:04 -0700 From: Craig Whipp User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Atheros AR9280 on 8.1-RC2 - unusable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 20:20:36 -0000 I recently upgraded a system of mine with an Atheros AR9280 to FreeBSD 8.1-RC2. Upon booting, the system log keeps getting appended with entries that state: ath0: bb hang detected (0x80) and ath0: ath_chan_set: unable to reset channel X (XXXX, flags 0x480), hal status 3 where X and XXXX cycle through the various channels and frequencies. The associated wlan device is unable to associate with the wireless access point. Let me know if there's any other information I can provide. This card was experienced occaisional lockups in 8.0-RELEASE, and will only associate with the ath driver if the driver is compiled into the kernel - loading via a module would not work. I'm posting this here because I saw Ken Smith's comment about recent AR9280 regression and fixes on this branch. Thanks, - Craig From owner-freebsd-stable@FreeBSD.ORG Sat Jul 3 20:51:13 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 606B7106566B for ; Sat, 3 Jul 2010 20:51:13 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 24DF58FC17 for ; Sat, 3 Jul 2010 20:51:13 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id o63KpBTo019333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 3 Jul 2010 13:51:12 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 97CF51CC0D for ; Sat, 3 Jul 2010 13:51:11 -0700 (PDT) To: stable@freebsd.org Date: Sat, 03 Jul 2010 13:51:11 -0700 From: "Kevin Oberman" Message-Id: <20100703205111.97CF51CC0D@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-07-02_03:2010-02-06, 2010-07-02, 2010-07-03 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-1005130000 definitions=main-1007030092 Cc: Subject: Odd behavior of labels on different filesystem types X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2010 20:51:13 -0000 I have run into an odd behavior in 8-stable that I can't see a reason for. If I have a FAT32 formatted removable drive, I get /dev entries for it as both /dev/msdosfs/LABEL and /dev/ufsid/ID. When I mount the filesystem, the /dev/ufsid label is removed, but the other two remain. If I have a UFS filesystem on the disk, I have similar devices except that the LABEL is /dev/ufs/LABEL. But, when the UFS device is mounted, the /dev/ufsid/ID AND the /dev/ufs/LABEL devs are both deleted. I'm not sure which is "right", but I can't see the reason for the different behavior and it has caused a fair bit of trouble when working with gnome-mount as I can't unmount a ufs device. When the /dev/ufs/LABEL device is created again on the umount, gnome-mount sees a new device and immediately re-mounts it. Can this inconsistency be corrected? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751