From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 09:21:23 2009 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 930A61065672; Sun, 6 Sep 2009 09:21:23 +0000 (UTC) (envelope-from thierry.herbelot@free.fr) Received: from smtpfb1-g21.free.fr (smtpfb1-g21.free.fr [212.27.42.9]) by mx1.freebsd.org (Postfix) with ESMTP id 56A7F8FC0A; Sun, 6 Sep 2009 09:21:20 +0000 (UTC) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by smtpfb1-g21.free.fr (Postfix) with ESMTP id 6BB1F2D4F0; Sun, 6 Sep 2009 11:03:02 +0200 (CEST) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id DC3F74C817B; Sun, 6 Sep 2009 11:02:55 +0200 (CEST) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id C8E784C8192; Sun, 6 Sep 2009 11:02:52 +0200 (CEST) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id n8692kdn025859; Sun, 6 Sep 2009 11:02:47 +0200 (CEST) From: Thierry Herbelot To: stable@freebsd.org Date: Sun, 6 Sep 2009 11:02:39 +0200 User-Agent: KMail/1.9.10 X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909061102.40450.thierry.herbelot@free.fr> Cc: jhb@freebsd.org Subject: Panic in recent 7.2-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: Sun, 06 Sep 2009 09:21:23 -0000 Hello, I'm having a panic with the latest kernel build of my -Stable file server (sources cvsupped around yesterday evening, CEST). The panic happens soon after entering multi-user : panic: vm_phys_paddr_to_vm_page: paddr 0xf0000 is not in any segment KDB: enter: panic [thread pid 1005 tid 100154 ] Stopped at kdb_enter_why+0x3a: movl $0,kdb_why db> where Tracing pid 1005 tid 100154 td 0x8ecad480 kdb_enter_why(80ba731f,80ba731f,80bc1ad6,fb301a94,fb301a94,...) at kdb_enter_why+0x3a panic(80bc1ad6,f0000,0,8ecad480,0,...) at panic+0xd1 vm_phys_paddr_to_vm_page(f0000,f0000,fb301ad8,1,80a36a78,...) at vm_phys_paddr_to_vm_page+0x4d dev_pager_getpages(92b8d980,fb301c04,1,0,fb301bcc,...) at dev_pager_getpages+0xe1 vm_fault(89267bfc,33d90000,1,0,89b0b50c,...) at vm_fault+0x1020 trap_pfault(202,7,8583b900,80cd9800,89b0eb00,...) at trap_pfault+0x15b trap(fb301d38) at trap+0x247 An excerpt of the dmesg is : Copyright (c) 1992-2009 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 7.2-STABLE #35: Sun Sep 6 10:04:40 CEST 2009 XXX@YYY:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0x8101a000. Preloaded elf module "/boot/kernel/zfs.ko" at 0x8101a188. Preloaded elf module "/boot/kernel/opensolaris.ko" at 0x8101a230. Preloaded elf module "/boot/kernel/snd_cmi.ko" at 0x8101a2e0. Preloaded elf module "/boot/kernel/sound.ko" at 0x8101a38c. Preloaded /boot/zfs/zpool.cache "/boot/zfs/zpool.cache" at 0x8101a438. Preloaded elf module "/boot/kernel/acpi.ko" at 0x8101a490. The previous kernel is older (around 22 august) and works as expected. Some idents for the panic kernel are : (ie after SVN rev 196838) $FreeBSD: src/sys/i386/i386/pmap.c,v 1.594.2.20 2009/09/04 19:59:32 jhb Exp $ $FreeBSD: src/sys/kern/kern_mbuf.c,v 1.32.2.6 2009/09/04 19:59:32 jhb Exp $ $FreeBSD: src/sys/vm/device_pager.c,v 1.84.2.3 2009/09/04 19:59:32 jhb Exp $ $FreeBSD: src/sys/vm/vm_object.c,v 1.385.2.7 2009/09/04 19:59:32 jhb Exp $ $FreeBSD: src/sys/vm/vm_page.c,v 1.357.2.10 2009/09/04 19:59:32 jhb Exp $ $FreeBSD: src/sys/vm/vm_phys.c,v 1.4.2.2 2009/09/04 19:59:32 jhb Exp $ Cheers TfH From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 10:11:43 2009 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 A32061065670; Sun, 6 Sep 2009 10:11:43 +0000 (UTC) (envelope-from tejblum@yandex-team.ru) Received: from archeopterix.yandex.ru (archeopterix.yandex.ru [93.158.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 5CBE28FC0C; Sun, 6 Sep 2009 10:11:43 +0000 (UTC) Received: from tejblum.pp.ru (dhcp250-245.yandex.ru [87.250.250.245]) by archeopterix.yandex.ru (Postfix) with ESMTPS id B19E459D948; Sun, 6 Sep 2009 13:53:55 +0400 (MSD) Message-ID: <4AA386B1.9020501@yandex-team.ru> Date: Sun, 06 Sep 2009 13:53:53 +0400 From: Dmitrij Tejblum User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.17) Gecko/20081109 SeaMonkey/1.1.12 MIME-Version: 1.0 To: stable@freebsd.org, jhb@freebsd.org References: <200909061102.40450.thierry.herbelot@free.fr> In-Reply-To: <200909061102.40450.thierry.herbelot@free.fr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Thierry Herbelot Subject: Re: Panic in recent 7.2-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: Sun, 06 Sep 2009 10:11:43 -0000 Thierry Herbelot wrote: > Hello, > > I'm having a panic with the latest kernel build of my -Stable file server > (sources cvsupped around yesterday evening, CEST). The panic happens soon > after entering multi-user : > > panic: vm_phys_paddr_to_vm_page: paddr 0xf0000 is not in any segment > KDB: enter: panic > [thread pid 1005 tid 100154 ] > Stopped at kdb_enter_why+0x3a: movl $0,kdb_why > db> where > Tracing pid 1005 tid 100154 td 0x8ecad480 > kdb_enter_why(80ba731f,80ba731f,80bc1ad6,fb301a94,fb301a94,...) at > kdb_enter_why+0x3a > panic(80bc1ad6,f0000,0,8ecad480,0,...) at panic+0xd1 > vm_phys_paddr_to_vm_page(f0000,f0000,fb301ad8,1,80a36a78,...) at > vm_phys_paddr_to_vm_page+0x4d > dev_pager_getpages(92b8d980,fb301c04,1,0,fb301bcc,...) at > dev_pager_getpages+0xe1 > vm_fault(89267bfc,33d90000,1,0,89b0b50c,...) at vm_fault+0x1020 > trap_pfault(202,7,8583b900,80cd9800,89b0eb00,...) at trap_pfault+0x15b > trap(fb301d38) at trap+0x247 > Similar panic here. I believe, the panic introduced in SVN revision 196838. For us, the panic is caused by the `dmidecode' program. The dmidecode program mmap /dev/mem at offset 0xf0000 and reads on... From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 11:35:51 2009 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 6A35C1065670 for ; Sun, 6 Sep 2009 11:35:51 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id DDA908FC12 for ; Sun, 6 Sep 2009 11:35:50 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n86B2c6I070131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Sep 2009 14:02:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n86B2cao006750; Sun, 6 Sep 2009 14:02:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n86B2cb9006749; Sun, 6 Sep 2009 14:02:38 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 6 Sep 2009 14:02:38 +0300 From: Kostik Belousov To: Thierry Herbelot Message-ID: <20090906110238.GH47688@deviant.kiev.zoral.com.ua> References: <200909061102.40450.thierry.herbelot@free.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ewQ5hdP4CtoTt3oD" Content-Disposition: inline In-Reply-To: <200909061102.40450.thierry.herbelot@free.fr> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: stable@freebsd.org, jhb@freebsd.org Subject: Re: Panic in recent 7.2-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: Sun, 06 Sep 2009 11:35:51 -0000 --ewQ5hdP4CtoTt3oD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 06, 2009 at 11:02:39AM +0200, Thierry Herbelot wrote: > Hello, >=20 > I'm having a panic with the latest kernel build of my -Stable file server= =20 > (sources cvsupped around yesterday evening, CEST). The panic happens soon= =20 > after entering multi-user : >=20 > panic: vm_phys_paddr_to_vm_page: paddr 0xf0000 is not in any segment > KDB: enter: panic > [thread pid 1005 tid 100154 ] > Stopped at kdb_enter_why+0x3a: movl $0,kdb_why > db> where > Tracing pid 1005 tid 100154 td 0x8ecad480 > kdb_enter_why(80ba731f,80ba731f,80bc1ad6,fb301a94,fb301a94,...) at=20 > kdb_enter_why+0x3a > panic(80bc1ad6,f0000,0,8ecad480,0,...) at panic+0xd1 > vm_phys_paddr_to_vm_page(f0000,f0000,fb301ad8,1,80a36a78,...) at=20 > vm_phys_paddr_to_vm_page+0x4d > dev_pager_getpages(92b8d980,fb301c04,1,0,fb301bcc,...) at=20 > dev_pager_getpages+0xe1 > vm_fault(89267bfc,33d90000,1,0,89b0b50c,...) at vm_fault+0x1020 > trap_pfault(202,7,8583b900,80cd9800,89b0eb00,...) at trap_pfault+0x15b > trap(fb301d38) at trap+0x247 >=20 > An excerpt of the dmesg is : >=20 > Copyright (c) 1992-2009 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 7.2-STABLE #35: Sun Sep 6 10:04:40 CEST 2009 > XXX@YYY:/usr/obj/usr/src/sys/GENERIC > Preloaded elf kernel "/boot/kernel/kernel" at 0x8101a000. > Preloaded elf module "/boot/kernel/zfs.ko" at 0x8101a188. > Preloaded elf module "/boot/kernel/opensolaris.ko" at 0x8101a230. > Preloaded elf module "/boot/kernel/snd_cmi.ko" at 0x8101a2e0. > Preloaded elf module "/boot/kernel/sound.ko" at 0x8101a38c. > Preloaded /boot/zfs/zpool.cache "/boot/zfs/zpool.cache" at 0x8101a438. > Preloaded elf module "/boot/kernel/acpi.ko" at 0x8101a490. >=20 > The previous kernel is older (around 22 august) and works as expected. >=20 > Some idents for the panic kernel are : (ie after SVN rev 196838) > $FreeBSD: src/sys/i386/i386/pmap.c,v 1.594.2.20 2009/09/04 19:59:32 jhb E= xp $ > $FreeBSD: src/sys/kern/kern_mbuf.c,v 1.32.2.6 2009/09/04 19:59:32 jhb Exp= $ > $FreeBSD: src/sys/vm/device_pager.c,v 1.84.2.3 2009/09/04 19:59:32 jhb Ex= p $ > $FreeBSD: src/sys/vm/vm_object.c,v 1.385.2.7 2009/09/04 19:59:32 jhb Exp $ > $FreeBSD: src/sys/vm/vm_page.c,v 1.357.2.10 2009/09/04 19:59:32 jhb Exp $ > $FreeBSD: src/sys/vm/vm_phys.c,v 1.4.2.2 2009/09/04 19:59:32 jhb Exp $ I expect that the following patch, that is the partial merge of r194459, would fix it. It patches sys/vm/vm_phys.c. Index: vm_phys.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- vm_phys.c (revision 194458) +++ vm_phys.c (revision 194459) @@ -382,8 +382,7 @@ if (pa >=3D seg->start && pa < seg->end) return (&seg->first_page[atop(pa - seg->start)]); } - panic("vm_phys_paddr_to_vm_page: paddr %#jx is not in any segment", - (uintmax_t)pa); + return (NULL); } =20 /* --ewQ5hdP4CtoTt3oD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqjlssACgkQC3+MBN1Mb4hczACg09EEqUwHW42cTveQh1y+RxFH +egAn0UvVDUL5aD0pjooYN1JKPMwG0G/ =hcK2 -----END PGP SIGNATURE----- --ewQ5hdP4CtoTt3oD-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 12:51:48 2009 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 A29391065670 for ; Sun, 6 Sep 2009 12:51:48 +0000 (UTC) (envelope-from mikael@t-online.hu) Received: from thor.iszerviz.hu (thor.iszerviz.hu [62.77.131.9]) by mx1.freebsd.org (Postfix) with ESMTP id 66CDB8FC0C for ; Sun, 6 Sep 2009 12:51:48 +0000 (UTC) Received: from [10.2.2.230] (m0n0.iszerviz.hu [62.77.131.200]) by thor.iszerviz.hu (Postfix) with ESMTP id B7F294FFCC for ; Sun, 6 Sep 2009 14:31:19 +0200 (CEST) Message-ID: <4AA3AB97.1050403@t-online.hu> Date: Sun, 06 Sep 2009 14:31:19 +0200 From: Mikael Bak User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Build kernel 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, 06 Sep 2009 12:51:48 -0000 Hi, I have installed FreeBSD 7.2 on an old laptop. It's only for fun and learning. I wanted to make my console use full 1024x768, so I followed this howto: http://kimklai.blogspot.com/2007/05/howto-freebsd-console-framebuffer.html # make buildkernel KERNCONF=GENERICVESA Gives me after quite long time this error message: make: don't know how to make /usr/src/sys/sys/gdefs.h. Stop *** Error code 2 Changes to GENERIC: +options VESA +options SC_PIXEL_MODE -options SMP -device apic -device eisa I would like to disable things I don't need, because the laptop is quite old and slow and don't have too much RAM. The laptop is an old Dell Latitude CPt C-series, 400MHz PII, 256 MB RAM, 6.5GB HDD. If I succeed I will try to disable other thing in the kernel to optimize even more. But perhaps I managed to disable somethig vital? TIA, Mikael From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 13:12:46 2009 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 4B7981065670 for ; Sun, 6 Sep 2009 13:12:46 +0000 (UTC) (envelope-from mikael@t-online.hu) Received: from thor.iszerviz.hu (thor.iszerviz.hu [62.77.131.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0E8738FC12 for ; Sun, 6 Sep 2009 13:12:45 +0000 (UTC) Received: from [192.168.1.144] (5403732B.catv.pool.telekom.hu [84.3.115.43]) by thor.iszerviz.hu (Postfix) with ESMTP id 2CDA84FFCC for ; Sun, 6 Sep 2009 15:12:45 +0200 (CEST) Message-ID: <4AA3B548.9000500@t-online.hu> Date: Sun, 06 Sep 2009 15:12:40 +0200 From: Mikael Bak User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: stable@freebsd.org References: <4AA3AB97.1050403@t-online.hu> In-Reply-To: <4AA3AB97.1050403@t-online.hu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Build kernel 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, 06 Sep 2009 13:12:46 -0000 Mikael Bak wrote: > -options SMP > -device apic > -device eisa > Responding to myself. I reactivated the above options, and now I get a different error: /usr/src/sys/dev/aic7xxx/aic7xxx.c:7896: internal compiler error: in output_constructor, at varasm.c:4311 [snip] *** Error code 1 I installed kernel source using sysinstall using an FTP mirror as described here: http://www.freebsd.org/doc/en/books/handbook/kernelconfig-building.html Did I perhaps miss installing something? TIA, Mikael From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 14:10:22 2009 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 80AAC106566B; Sun, 6 Sep 2009 14:10:22 +0000 (UTC) (envelope-from thierry.herbelot@free.fr) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by mx1.freebsd.org (Postfix) with ESMTP id 476A08FC18; Sun, 6 Sep 2009 14:10:19 +0000 (UTC) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id CD2AA4C810A; Sun, 6 Sep 2009 16:10:15 +0200 (CEST) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id D016D4C8101; Sun, 6 Sep 2009 16:10:12 +0200 (CEST) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id n86EA9kk012836; Sun, 6 Sep 2009 16:10:10 +0200 (CEST) From: Thierry Herbelot To: Kostik Belousov Date: Sun, 6 Sep 2009 16:10:02 +0200 User-Agent: KMail/1.9.10 References: <200909061102.40450.thierry.herbelot@free.fr> <20090906110238.GH47688@deviant.kiev.zoral.com.ua> In-Reply-To: <20090906110238.GH47688@deviant.kiev.zoral.com.ua> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200909061610.03858.thierry.herbelot@free.fr> Cc: stable@freebsd.org, jhb@freebsd.org Subject: Re: Panic in recent 7.2-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: Sun, 06 Sep 2009 14:10:22 -0000 Le Sunday 06 September 2009, Kostik Belousov a écrit : > > I expect that the following patch, that is the partial merge of r194459, > would fix it. It patches sys/vm/vm_phys.c. > > Index: vm_phys.c > =================================================================== > --- vm_phys.c (revision 194458) > +++ vm_phys.c (revision 194459) > @@ -382,8 +382,7 @@ > if (pa >= seg->start && pa < seg->end) > return (&seg->first_page[atop(pa - seg->start)]); > } > - panic("vm_phys_paddr_to_vm_page: paddr %#jx is not in any segment", > - (uintmax_t)pa); > + return (NULL); This seems indeed the missing part : I should have looked in -current .... Thanks TfH > } > > /* From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 15:46:04 2009 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 0E146106566B for ; Sun, 6 Sep 2009 15:46:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id A90368FC0C for ; Sun, 6 Sep 2009 15:46:03 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id A824B730DA; Sun, 6 Sep 2009 17:51:54 +0200 (CEST) Date: Sun, 6 Sep 2009 17:51:54 +0200 From: Luigi Rizzo To: stable@freebsd.org Message-ID: <20090906155154.GA8283@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: incorrect usleep/select delays with HZ > 2500 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, 06 Sep 2009 15:46:04 -0000 (this problem seems to affect both current and -stable, so let's see if here i have better luck) I just noticed [Note 1,2] that when setting HZ > 2500 (even if it is an exact divisor of the APIC/CPU clock) there is a significant drift between the delays generated by usleep()/select() and those computed by gettimeofday(). In other words, the error grows with the amount of delay requested. To show the problem, try this function int f(int wait_time) { // wait_time in usec struct timeval start, end; gettimeofday(&start); usleep(w); // or try select gettimeofday(&end) timersub(&end, &start, &x); return = x.tv_usec + 1000000*x.tv_sec - wait_time; } for various HZ (kern.hz=NNNN in /boot/loader.conf) and wait times. Ideally, we would expect the timings to be in error by something between 0 and 1 (or 2) ticks, irrespective of the value of wait_time. In fact, this is what you see with HZ=1000, 2000 and 2500. But larger values of HZ (e.g. 4000, 5000, 10k, 40k) create a drift of 0.5% and above (i.e. with HZ=5000, a 1-second delay lasts 1.0064s and a 10s delay lasts 10.062s; with HZ=10k the error becomes 1% and at HZ=40k the error becomes even bigger. Note that with the fixes described below, even HZ=40k works perfectly well. Turns out that the error has three components (described with possible fixes): 1. CAUSE: Errors in the measurement of the TSC (and APIC) frequencies, see [Note 3] for more details. This is responsible for the drift. FIX: It can be removed by rounding the measurement to the closest nominal values (e.g. my APIC runs at 100 MHz; we can use a table of supported values). Otherwise, see [Note 4] PROBLEM: is this general enough ? 2. CAUSE: Use of approximate kernel time functions (getnanotime/getmicrotime) in nanosleep() and select(). This imposes an error of max(1tick, 1ms) in the computation of delays, irrespective of HZ values. BTW For reasons I don't understand this seems to affect nanosleep() more than select(). FIX: It can be reduced to just 1 tick making kern.timecounter.tick writable and letting the user set it to 1 if high precision is required. PROBLEM: none that i see. 3. CAUSE an error in tvtohz(), reported long ago in http://www.dragonflybsd.org/presentations/nanosleep/ which causes a systematic error of an extra tick in the computation of the sleep times. FIX: the above link also contains a proposed fix (which in fact reverts a bug introduced in some old commit on FreeBSD) PROBLEM: none that i see. Applying these three fixes i was able to run a kernel with HZ=40000 and see timing errors within 80-90us even with ten second delays. This would put us on par with Linux [Note 5]. This is a significant improvement over the current situation and the reason why I would like to explore the possibility of applying some of these fixes. I know there are open problems -- e.g. when the timer source used by gettimeofday() gets corrected by ntp or other things, hardclock() still ticks at the same rate so you'll see a drift if you don't apply corrections there as well. Similarly, if HZ is not an exact divisor of the clock source used by gettimeofday(), i suppose errors will accumulate as well. However fixing these other drift seems reasonably orthogonal at least to #2 and #3 above, and a lot more difficult so we could at least start from these simple fixes. Would anyone be interested in reproducing the experiment (test program attached -- run it with 'lat -p -i wait_time_in_microseconds') and try to explain me what changes the system's behaviour above HZ=2500 ? cheers luigi Notes: [Note 1] I have some interest in running machines with high HZ values because this gives better precision to dummynet and various other tasks with soft timing constraints. [Note 2] I have seen the same phenomenon on the following platform: RELENG_8/amd64 with AMD BE-2400 dual core cpu RELENG_7/i386 with AMD BE-2400 dual core cpu RELENG_7/i386 with Intel Centrino single core (Dell X1 Laptop) [Note 3] the TSC frequency is computed reading the tsc around a call to DELAY(1000000) and assuming that the i8254 runs at the nominal rate, 1.193182 MHz. From tests I have made, the measurement in init_TSC() returns a large error when HZ is large, whereas repeating the measurement at a later time returns a much more reliable value. As an example, see the following: Sep 6 14:21:59 lr kernel: TSC clock: at init_TSC 2323045616 Hz Sep 6 14:21:59 lr kernel: Features=0x178bfbff Sep 6 14:21:59 lr kernel: AMD Features=0xea500800 Sep 6 14:21:59 lr kernel: TSC: P-state invariant Sep 6 14:21:59 lr kernel: TSC clock: at cpu_startup_end 2323056910 Hz Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe 2311254060 Hz Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe_2 2311191310 Hz Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300822648 Hz Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300830946 Hz Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300840133 Hz Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300835253 Hz Sep 6 14:21:59 lr kernel: TSC clock: at lapic_setup_clock 2300868376 Hz The latter values are close to what is reported when HZ=1000. [Note 4] DELAY() uses the TSC when available, but perhaps for larger intervals (say above 100ms) it might be better to always use the 8254 which at least does not change frequency over time ? [Note 5] Linux has some high precision timers which one could expect to use for high precision delays. In fact, I ran the test program on a recent Linux 2.6.30 (using HZ=1000), and the usleep() version has an error between 80 and 90us irrespective of the delay. However the select() version is much worse, and loses approx 1ms per second. ------------------------------------------------------ From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 16:02:57 2009 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 76E3E1065670; Sun, 6 Sep 2009 16:02:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id CAF3B8FC15; Sun, 6 Sep 2009 16:02:56 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n86G2mww088478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Sep 2009 19:02:48 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n86G2lwT011004; Sun, 6 Sep 2009 19:02:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n86G2lmo011003; Sun, 6 Sep 2009 19:02:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 6 Sep 2009 19:02:47 +0300 From: Kostik Belousov To: "A.J. Fonz van Werven" Message-ID: <20090906160247.GI47688@deviant.kiev.zoral.com.ua> References: <20090906110238.GH47688@deviant.kiev.zoral.com.ua> <200909061537.n86FbqhP001617@satellite.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JIpyCmsTxyPLrmrM" Content-Disposition: inline In-Reply-To: <200909061537.n86FbqhP001617@satellite.xs4all.nl> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Thierry Herbelot , stable@freebsd.org, jhb@freebsd.org Subject: Re: Panic in recent 7.2-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: Sun, 06 Sep 2009 16:02:57 -0000 --JIpyCmsTxyPLrmrM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 06, 2009 at 05:37:52PM +0200, A.J. Fonz van Werven wrote: > Kostik Belousov wrote: >=20 > > I expect that the following patch, that is the partial merge of r194459, > > would fix it. It patches sys/vm/vm_phys.c. > >=20 > > Index: vm_phys.c > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > --- vm_phys.c (revision 194458) > > +++ vm_phys.c (revision 194459) > > @@ -382,8 +382,7 @@ > > if (pa >=3D seg->start && pa < seg->end) > > return (&seg->first_page[atop(pa - seg->start)]); > > } > > - panic("vm_phys_paddr_to_vm_page: paddr %#jx is not in any segment", > > - (uintmax_t)pa); > > + return (NULL); > > } > > =20 > > /* >=20 > Hi, >=20 > A quick grep on the file in question revealed that there are two > functions that may panic() with "page not in any segment": the > vm_phys_paddr_to_vm_page() being patched and also the next function > vm_phys_paddr_to_segind(). I'm not exactly current with the memory > management code so this may be a very stupid question, but I'll ask it > anyway: don't both functions need to be patched? vm_phys_paddr_to_segind is used during vm bootstrap, the call sequence is vm_page_startup->vm_phys_add_page->vm_phys_paddr_to_segind. vm_page_startup calls vm_phys_add_page only for pages that should not cause the mentioned panic in vm_phys_paddr_to_segind, since it iterates over the pages of the segments created by vm_phys_create_seg() in vm_phys_init(). --JIpyCmsTxyPLrmrM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqj3ScACgkQC3+MBN1Mb4hIGwCgjkEX3RwkuNVhXEND/x0X13AL CSsAnRVAkUd1fePCxcyMFvbs+X+baH2b =WwRo -----END PGP SIGNATURE----- --JIpyCmsTxyPLrmrM-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 16:06:33 2009 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 2ED93106566C for ; Sun, 6 Sep 2009 16:06:33 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id D9C848FC14 for ; Sun, 6 Sep 2009 16:06:32 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.3/8.14.3) with ESMTP id n86Fis53051919 for ; Sun, 6 Sep 2009 08:44:54 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.3/8.14.3/Submit) id n86FisEU051918 for stable@freebsd.org; Sun, 6 Sep 2009 08:44:54 -0700 (PDT) (envelope-from david) Date: Sun, 6 Sep 2009 08:44:54 -0700 From: David Wolfskill To: stable@freebsd.org Message-ID: <20090906154454.GN23018@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , stable@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KCXyoJ//PRyfzsc9" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: panic: vm_phys_paddr_to_vm_page: paddr 0xf8000 is not in any segment X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Wolfskill , 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: Sun, 06 Sep 2009 16:06:33 -0000 --KCXyoJ//PRyfzsc9 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable First got this on my laptop (but not my headless build machine) -- each of which is i386 -- yesterday, at r196858; after reverting to r196827 (from Thursday), then rebuilding stable/7 at r196886, it recurred. It appears to be happening when xdm(1) gets started., which is pretty late in the transition to multi-user mode. One oddity of which to be aware: all ports (save for misc/compat6x) are built and installed while running stable/6. (I track stable/6, stable/7, and head, as well as track ports, daily, on both the build machine and the laptop. As I try to have some time to actually use the laptop, rather than merely building stuff on it, I don't try to update the ports collection daily for each of the 3 versions of the OS I run. And as the laptop is "user-facing," it tends to have a lot (863, at last count) of ports installed.) misc/compat6x was installed and is updated under stable/7; it is presently at compat6x-i386-6.4.604000.200810_3 -- updated Sep 4 06:03:18 2009. For the past couple of weeks (until yesterday), I noticed that during the attempt to start xdm(1), the laptop (when running stable/7) would sometimes lock up (i.e., keyboard apparently non-functional;; mouse non-functional; only thing I could find to make any progress was a power cycle, then booting single-user & issuing "fsck -p && exit"). Since I wasn't able to get any information, I didn't mention it here previously, but now aat least I have an apparently consistennt panic -- but only when running stable/7. I have no problems runnning xdm(1) under stable/6 (not that that's a surprise), but I also have no problems runing xdm(1) under head. I've copied the crashinfo(8) information to a file visible to my Web server; it may be viewed at . I'll paste the uname info & backtrace here, but for more details, please see that page. (Of course, if the details you seek aren't in the crashinfo(8) output, please just let me know what you seek....) FreeBSD localhost 7.2-STABLE FreeBSD 7.2-STABLE #935 r196886: Sun Sep 6 05= :35:04 PDT 2009 root@g1-69.catwhisker.org:/common/S3/obj/usr/src/sys/CA= NARY i386 #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:196 #1 0xc049a979 in db_fncall (dummy1=3D1, dummy2=3D0, dummy3=3D-1060239008,= =20 dummy4=3D0xc3b6986c "\200@=E2=C3") at /usr/src/sys/ddb/db_command.c:516 #2 0xc049aefc in db_command (last_cmdp=3D0xc0c95694, cmd_table=3D0x0, dopa= ger=3D1) at /usr/src/sys/ddb/db_command.c:413 #3 0xc049b00a in db_command_loop () at /usr/src/sys/ddb/db_command.c:466 #4 0xc049cabd in db_trap (type=3D3, code=3D0) at /usr/src/sys/ddb/db_main.= c:228 #5 0xc0812406 in kdb_trap (type=3D3, code=3D0, tf=3D0xc3b69a14) at /usr/src/sys/kern/subr_kdb.c:524 #6 0xc0af205b in trap (frame=3D0xc3b69a14) at /usr/src/sys/i386/i386/trap.= c:692 #7 0xc0ad5d4b in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #8 0xc081258a in kdb_enter_why (why=3D0xc0b93e11 "panic",=20 msg=3D0xc0b93e11 "panic") at cpufunc.h:60 #9 0xc07e55b6 in panic ( fmt=3D0xc0bb024d "vm_phys_paddr_to_vm_page: paddr %#jx is not in any se= gment") at /usr/src/sys/kern/kern_shutdown.c:557 #10 0xc0a504bd in vm_phys_paddr_to_vm_page (pa=3D1015808) at /usr/src/sys/vm/vm_phys.c:385 #11 0xc0a2ec21 in dev_pager_getpages (object=3D0xc4d29000, m=3D0xc3b69c04,= =20 count=3D1, reqpage=3D0) at /usr/src/sys/vm/device_pager.c:240 #12 0xc0a3ae90 in vm_fault (map=3D0xc4d0d000, vaddr=3D676900864,=20 fault_type=3D1 '\001', fault_flags=3DVariable "fault_flags" is not avai= lable. ) at vm_pager.h:130 #13 0xc0af13bb in trap_pfault (frame=3D0xc3b69d38, usermode=3D1, eva=3D6769= 04576) at /usr/src/sys/i386/i386/trap.c:833 #14 0xc0af1d27 in trap (frame=3D0xc3b69d38) at /usr/src/sys/i386/i386/trap.= c:399 #15 0xc0ad5d4b in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #16 0x285599c1 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb)=20 Given that last ("Previous frame inner to this frame (corrupt stack?)"), I'm not at all certain that the backtraace (or the dump) will be all that useful. And because of my odd configuration, this may not be of sufficient interest to merit much expenditure of anyone else's time. I'm quite willing to experiment, try patches, or whatnot. I have local mirrors of the CVVS & SVN repositories handy. I'm not much of a kernel hacker per se, but I am fairly comfortable hacking sources in general. I welcome clues. Thanks. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --KCXyoJ//PRyfzsc9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqj2PUACgkQmprOCmdXAD3SVACeNQr/0ryxOk5IPeMy/rvyrCl6 tCQAniDxz45Hn0PfnJfBC+2Qh+h4Qbsc =/nHQ -----END PGP SIGNATURE----- --KCXyoJ//PRyfzsc9-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 16:07:58 2009 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 6331A10656A8; Sun, 6 Sep 2009 16:07:58 +0000 (UTC) (envelope-from thierry.herbelot@free.fr) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by mx1.freebsd.org (Postfix) with ESMTP id 3D6D28FC08; Sun, 6 Sep 2009 16:07:54 +0000 (UTC) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id 8BB954C80D0; Sun, 6 Sep 2009 18:07:49 +0200 (CEST) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id 5D10F4C8140; Sun, 6 Sep 2009 18:07:47 +0200 (CEST) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id n86G7jVO007673; Sun, 6 Sep 2009 18:07:46 +0200 (CEST) From: Thierry Herbelot To: "A.J. \"Fonz\" van Werven" Date: Sun, 6 Sep 2009 18:07:39 +0200 User-Agent: KMail/1.9.10 References: <200909061537.n86FbqhP001617@satellite.xs4all.nl> In-Reply-To: <200909061537.n86FbqhP001617@satellite.xs4all.nl> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200909061807.40053.thierry.herbelot@free.fr> Cc: stable@freebsd.org, jhb@freebsd.org Subject: Re: Panic in recent 7.2-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: Sun, 06 Sep 2009 16:07:58 -0000 Le Sunday 06 September 2009, A.J. "Fonz" van Werven a écrit : > Kostik Belousov wrote: > > I expect that the following patch, that is the partial merge of r194459, > > would fix it. It patches sys/vm/vm_phys.c. > > > > Index: vm_phys.c > > =================================================================== > > --- vm_phys.c (revision 194458) > > +++ vm_phys.c (revision 194459) > > @@ -382,8 +382,7 @@ > > if (pa >= seg->start && pa < seg->end) > > return (&seg->first_page[atop(pa - seg->start)]); > > } > > - panic("vm_phys_paddr_to_vm_page: paddr %#jx is not in any segment", > > - (uintmax_t)pa); > > + return (NULL); > > } > > > > /* > > Hi, > > A quick grep on the file in question revealed that there are two > functions that may panic() with "page not in any segment": the > vm_phys_paddr_to_vm_page() being patched and also the next function > vm_phys_paddr_to_segind(). I'm not exactly current with the memory > management code so this may be a very stupid question, but I'll ask it > anyway: don't both functions need to be patched? > > My apologies if I'm way off the mark here, but I'm just trying to help. you are right : there seems the vm handling has been recently updated and maybe even "those who know" may not have reviewed/updated all panic conditions (removing the panic in vm_phys_paddr_to_vm_page at least allows correct operation of a -Stable kernel, like under -Current) TfH > > Regards, > > Alphons From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 16:10:05 2009 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 A1F8F106566B for ; Sun, 6 Sep 2009 16:10:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id DBE538FC1E for ; Sun, 6 Sep 2009 16:10:04 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n86G9tCH088991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Sep 2009 19:09:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n86G9t9V011083; Sun, 6 Sep 2009 19:09:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n86G9tSs011082; Sun, 6 Sep 2009 19:09:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 6 Sep 2009 19:09:55 +0300 From: Kostik Belousov To: David Wolfskill , stable@freebsd.org Message-ID: <20090906160955.GJ47688@deviant.kiev.zoral.com.ua> References: <20090906154454.GN23018@albert.catwhisker.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="j+MD90OnwjQyWNYt" Content-Disposition: inline In-Reply-To: <20090906154454.GN23018@albert.catwhisker.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Subject: Re: panic: vm_phys_paddr_to_vm_page: paddr 0xf8000 is not in any segment 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, 06 Sep 2009 16:10:05 -0000 --j+MD90OnwjQyWNYt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Sep 06, 2009 at 08:44:54AM -0700, David Wolfskill wrote: > First got this on my laptop (but not my headless build machine) -- > each of which is i386 -- yesterday, at r196858; after reverting to > r196827 (from Thursday), then rebuilding stable/7 at r196886, it > recurred. Please try r196894. --j+MD90OnwjQyWNYt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqj3tMACgkQC3+MBN1Mb4iHXgCg88ZS7QZRx4oRIidXvfyFf0Fl jR4AoIHD9cZPrMolAgDImoJZecnU3DlQ =41FF -----END PGP SIGNATURE----- --j+MD90OnwjQyWNYt-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 16:12:17 2009 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 EEFB0106566B; Sun, 6 Sep 2009 16:12:17 +0000 (UTC) (envelope-from a.j.werven@student.utwente.nl) Received: from satellite.xs4all.nl (zoefsam.xs4all.nl [82.95.125.145]) by mx1.freebsd.org (Postfix) with ESMTP id 753238FC13; Sun, 6 Sep 2009 16:12:17 +0000 (UTC) Received: from satellite.xs4all.nl (localhost [127.0.0.1]) by satellite.xs4all.nl (8.14.3/8.14.3) with ESMTP id n86Fbq0x001618; Sun, 6 Sep 2009 17:37:52 +0200 (CEST) (envelope-from fonz@satellite.xs4all.nl) Received: (from fonz@localhost) by satellite.xs4all.nl (8.14.3/8.14.3/Submit) id n86FbqhP001617; Sun, 6 Sep 2009 17:37:52 +0200 (CEST) (envelope-from fonz) From: "A.J. \"Fonz\" van Werven" Message-Id: <200909061537.n86FbqhP001617@satellite.xs4all.nl> In-Reply-To: <20090906110238.GH47688@deviant.kiev.zoral.com.ua> To: Kostik Belousov Date: Sun, 6 Sep 2009 17:37:52 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL124c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Cc: Thierry Herbelot , stable@freebsd.org, jhb@freebsd.org Subject: Re: Panic in recent 7.2-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: Sun, 06 Sep 2009 16:12:18 -0000 Kostik Belousov wrote: > I expect that the following patch, that is the partial merge of r194459, > would fix it. It patches sys/vm/vm_phys.c. > > Index: vm_phys.c > =================================================================== > --- vm_phys.c (revision 194458) > +++ vm_phys.c (revision 194459) > @@ -382,8 +382,7 @@ > if (pa >= seg->start && pa < seg->end) > return (&seg->first_page[atop(pa - seg->start)]); > } > - panic("vm_phys_paddr_to_vm_page: paddr %#jx is not in any segment", > - (uintmax_t)pa); > + return (NULL); > } > > /* Hi, A quick grep on the file in question revealed that there are two functions that may panic() with "page not in any segment": the vm_phys_paddr_to_vm_page() being patched and also the next function vm_phys_paddr_to_segind(). I'm not exactly current with the memory management code so this may be a very stupid question, but I'll ask it anyway: don't both functions need to be patched? My apologies if I'm way off the mark here, but I'm just trying to help. Regards, Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- Pope Benedict XVI, Southpark season 11 episode 5 From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 16:19:05 2009 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 C5177106566C for ; Sun, 6 Sep 2009 16:19:05 +0000 (UTC) (envelope-from a.j.werven@student.utwente.nl) Received: from satellite.xs4all.nl (zoefsam.xs4all.nl [82.95.125.145]) by mx1.freebsd.org (Postfix) with ESMTP id 5A5A08FC13 for ; Sun, 6 Sep 2009 16:19:04 +0000 (UTC) Received: from satellite.xs4all.nl (localhost [127.0.0.1]) by satellite.xs4all.nl (8.14.3/8.14.3) with ESMTP id n86GIo6b040439; Sun, 6 Sep 2009 18:18:50 +0200 (CEST) (envelope-from fonz@satellite.xs4all.nl) Received: (from fonz@localhost) by satellite.xs4all.nl (8.14.3/8.14.3/Submit) id n86GIo1D040432; Sun, 6 Sep 2009 18:18:50 +0200 (CEST) (envelope-from fonz) From: "A.J. \"Fonz\" van Werven" Message-Id: <200909061618.n86GIo1D040432@satellite.xs4all.nl> In-Reply-To: <20090906154454.GN23018@albert.catwhisker.org> To: David Wolfskill , stable@freebsd.org Date: Sun, 6 Sep 2009 18:18:50 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL124c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Cc: Subject: Re: panic: vm_phys_paddr_to_vm_page: paddr 0xf8000 is not in any segment 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, 06 Sep 2009 16:19:05 -0000 David Wolfskill wrote: > It appears to be happening when xdm(1) gets started. I'm getting the same when starting X manually (startx). > I welcome clues. A patch has been submitted to this list less than an hour ago and I've already seen the SVN commit as well. I'm currently rebuilding, you might want to try the same. Let's hope this fixes it. Regards, Alphons -- All right, that does it Bill [Donahue]. I'm pretty sure that killing Jesus is not very Christian. -- Pope Benedict XVI, Southpark season 11 episode 5 From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 17:00:27 2009 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 6102B1065670 for ; Sun, 6 Sep 2009 17:00:27 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 32F368FC08 for ; Sun, 6 Sep 2009 17:00:26 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.3/8.14.3) with ESMTP id n86H0QWe052440; Sun, 6 Sep 2009 10:00:26 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.3/8.14.3/Submit) id n86H0QXb052439; Sun, 6 Sep 2009 10:00:26 -0700 (PDT) (envelope-from david) Date: Sun, 6 Sep 2009 10:00:26 -0700 From: David Wolfskill To: Kostik Belousov Message-ID: <20090906170026.GO23018@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Kostik Belousov , stable@freebsd.org References: <20090906154454.GN23018@albert.catwhisker.org> <20090906160955.GJ47688@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yUmmepPgoWmUqRhm" Content-Disposition: inline In-Reply-To: <20090906160955.GJ47688@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org Subject: Re: panic: vm_phys_paddr_to_vm_page: paddr 0xf8000 is not in any segment 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, 06 Sep 2009 17:00:27 -0000 --yUmmepPgoWmUqRhm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 06, 2009 at 07:09:55PM +0300, Kostik Belousov wrote: > On Sun, Sep 06, 2009 at 08:44:54AM -0700, David Wolfskill wrote: > > First got this on my laptop (but not my headless build machine) -- > > each of which is i386 -- yesterday, at r196858; after reverting to > > r196827 (from Thursday), then rebuilding stable/7 at r196886, it > > recurred. > Please try r196894. Hand-applied; rebuilt. On reboot, no panic -- thanks! :-) [The bad news is that I did get the apparent hang at xdm(8) start-up. Three out of three tries.... :-{] Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --yUmmepPgoWmUqRhm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqj6qkACgkQmprOCmdXAD1InACfazjj/WQGnHQ7jE3JuWVvJBT7 oMQAniQLlpW7k1vEcjRIyxEGRaYOgtyx =dikf -----END PGP SIGNATURE----- --yUmmepPgoWmUqRhm-- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 6 17:26:26 2009 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 279D0106566B for ; Sun, 6 Sep 2009 17:26:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 92FED8FC29 for ; Sun, 6 Sep 2009 17:26:25 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n86HQDDb093755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Sep 2009 20:26:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n86HQDvY011493; Sun, 6 Sep 2009 20:26:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n86HQCw1011492; Sun, 6 Sep 2009 20:26:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 6 Sep 2009 20:26:12 +0300 From: Kostik Belousov To: David Wolfskill , stable@freebsd.org Message-ID: <20090906172612.GK47688@deviant.kiev.zoral.com.ua> References: <20090906154454.GN23018@albert.catwhisker.org> <20090906160955.GJ47688@deviant.kiev.zoral.com.ua> <20090906170026.GO23018@albert.catwhisker.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4Djgzn3z2HSNnx0" Content-Disposition: inline In-Reply-To: <20090906170026.GO23018@albert.catwhisker.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Subject: Re: panic: vm_phys_paddr_to_vm_page: paddr 0xf8000 is not in any segment 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, 06 Sep 2009 17:26:26 -0000 --T4Djgzn3z2HSNnx0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 06, 2009 at 10:00:26AM -0700, David Wolfskill wrote: > On Sun, Sep 06, 2009 at 07:09:55PM +0300, Kostik Belousov wrote: > > On Sun, Sep 06, 2009 at 08:44:54AM -0700, David Wolfskill wrote: > > > First got this on my laptop (but not my headless build machine) -- > > > each of which is i386 -- yesterday, at r196858; after reverting to > > > r196827 (from Thursday), then rebuilding stable/7 at r196886, it > > > recurred. > > Please try r196894. >=20 > Hand-applied; rebuilt. On reboot, no panic -- thanks! :-) >=20 > [The bad news is that I did get the apparent hang at xdm(8) start-up. > Three out of three tries.... :-{] Could you, please, get more details ? I assume that hang occured during the X server startup, actually. Does machine respond to the pings ? If yes, can you ssh into it ? Also, you might try to install sysinstall/dmidecode and try running it, to verify that /dev/mem works. --T4Djgzn3z2HSNnx0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqj8LQACgkQC3+MBN1Mb4hUjACeL6O55a4JmPUNdvXs95AKVaTS w5kAnibEcM1TSz8+a0QYQIM/UJU0fX5I =j5ko -----END PGP SIGNATURE----- --T4Djgzn3z2HSNnx0-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 7 01:08:41 2009 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 EB32C1065676 for ; Mon, 7 Sep 2009 01:08:41 +0000 (UTC) (envelope-from peter@wemm.org) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id ACF4D8FC13 for ; Mon, 7 Sep 2009 01:08:41 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 3so547030qwe.7 for ; Sun, 06 Sep 2009 18:08:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.121.132 with SMTP id h4mr8772547qar.255.1252283789392; Sun, 06 Sep 2009 17:36:29 -0700 (PDT) In-Reply-To: <20090906155154.GA8283@onelab2.iet.unipi.it> References: <20090906155154.GA8283@onelab2.iet.unipi.it> Date: Sun, 6 Sep 2009 17:36:29 -0700 Message-ID: From: Peter Wemm To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 07 Sep 2009 01:08:42 -0000 On Sun, Sep 6, 2009 at 8:51 AM, Luigi Rizzo wrote: > (this problem seems to affect both current and -stable, > so let's see if here i have better luck) > > I just noticed [Note 1,2] that when setting HZ > 2500 (even if it is > an exact divisor of the APIC/CPU clock) there is a significant > drift between the delays generated by usleep()/select() and those > computed by gettimeofday(). =A0In other words, the error grows with > the amount of delay requested. > > To show the problem, try this function > > =A0 =A0 =A0 =A0int f(int wait_time) { =A0// wait_time in usec > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0struct timeval start, end; > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0gettimeofday(&start); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0usleep(w); =A0 =A0 =A0// or try select > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0gettimeofday(&end) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0timersub(&end, &start, &x); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return =3D x.tv_usec + 1000000*x.tv_sec - = wait_time; > =A0 =A0 =A0 =A0} > > for various HZ (kern.hz=3DNNNN in /boot/loader.conf) and wait times. > Ideally, we would expect the timings to be in error by something > between 0 and 1 (or 2) ticks, irrespective of the value of wait_time. > In fact, this is what you see with HZ=3D1000, 2000 and 2500. > But larger values of HZ (e.g. 4000, 5000, 10k, 40k) create > a drift of 0.5% and above (i.e. with HZ=3D5000, a 1-second delay > lasts 1.0064s and a 10s delay lasts 10.062s; with HZ=3D10k the > error becomes 1% and at HZ=3D40k the error becomes even bigger. Technically, it isn't even an error because the sleeps are defined as 'at least' the value specified. If you're looking for real-time-OS level performance, you probably need to look at one. > Note that with the fixes described below, even HZ=3D40k works perfectly w= ell. > > Turns out that the error has three components (described with > possible fixes): > > 1. =A0CAUSE: Errors in the measurement of the TSC (and APIC) frequencies, > =A0 =A0 =A0 =A0see [Note 3] for more details. This is responsible for the= drift. > =A0 =A0FIX: It can be removed by rounding the measurement to the closest > =A0 =A0 =A0 =A0nominal values (e.g. my APIC runs at 100 MHz; we can use a > =A0 =A0 =A0 =A0table of supported values). Otherwise, see [Note 4] > =A0 =A0PROBLEM: is this general enough ? > > 2. =A0CAUSE: Use of approximate kernel time functions (getnanotime/getmic= rotime) > =A0 =A0 =A0 =A0in nanosleep() and select(). This imposes an error of max(= 1tick, 1ms) > =A0 =A0 =A0 =A0in the computation of delays, irrespective of HZ values. > =A0 =A0 =A0 =A0BTW For reasons I don't understand this seems to affect > =A0 =A0 =A0 =A0nanosleep() more than select(). > =A0 =A0FIX: It can be reduced to just 1 tick making kern.timecounter.tick= writable > =A0 =A0 =A0 =A0and letting the user set it to 1 if high precision is requ= ired. > =A0 =A0PROBLEM: none that i see. > > 3. =A0CAUSE an error in tvtohz(), reported long ago in > =A0 =A0 =A0 =A0http://www.dragonflybsd.org/presentations/nanosleep/ > =A0 =A0 =A0 =A0which causes a systematic error of an extra tick in the co= mputation > =A0 =A0 =A0 =A0of the sleep times. > =A0 =A0FIX: the above link also contains a proposed fix (which in fact > =A0 =A0 =A0 =A0reverts a bug introduced in some old commit on FreeBSD) > =A0 =A0PROBLEM: none that i see. This change, as-is, is extremely dangerous. tsleep/msleep() use a value of 0 meaning 'forever'. Changing tvtohz() so that it can now return 0 for a non-zero tv is setting land-mines all over the place. There's something like 27 callers of tvtohz() in sys/kern alone, some of which are used to supply tsleep/msleep() timeouts. Note that the dragonflybsd patch above only adds the 'returns 0' check to one single caller. You either need to patch all callers of tvtohz() since you've change the semantics, or add a 'if (ticks =3D=3D 0) ticks =3D 1' check (or checks) in the appropriate places inside tvtohz(). If you don't do it, then you end up with callers of random functions with very small timeouts instead finding themselves sleeping forever. > Applying these three fixes i was able to run a kernel with HZ=3D40000 > and see timing errors within 80-90us even with ten second delays. > This would put us on par with Linux [Note 5]. > This is a significant improvement over the current situation > and the reason why I would like to explore the possibility of applying > some of these fixes. > > I know there are open problems -- e.g. when the timer source used > by gettimeofday() gets corrected by ntp or other things, hardclock() > still ticks at the same rate so you'll see a drift if you don't apply > corrections there as well. Similarly, if HZ is not an exact > divisor of the clock source used by gettimeofday(), i suppose > errors will accumulate as well. However fixing these other > drift seems reasonably orthogonal at least to #2 and #3 above, and > a lot more difficult so we could at least start from these simple > fixes. > > > Would anyone be interested in reproducing the experiment (test program > attached -- run it with 'lat -p -i wait_time_in_microseconds') > and try to explain me what changes the system's behaviour above HZ=3D2500= ? > > =A0 =A0 =A0 =A0cheers > =A0 =A0 =A0 =A0luigi > > Notes: > > [Note 1] I have some interest in running machines with high HZ values > =A0 =A0because this gives better precision to dummynet and various > =A0 =A0other tasks with soft timing constraints. > > [Note 2] I have seen the same phenomenon on the following platform: > =A0 =A0 =A0 =A0RELENG_8/amd64 with AMD BE-2400 dual core cpu > =A0 =A0 =A0 =A0RELENG_7/i386 with AMD BE-2400 dual core cpu > =A0 =A0 =A0 =A0RELENG_7/i386 with Intel Centrino single core (Dell X1 Lap= top) > > > [Note 3] the TSC frequency is computed reading the tsc around a > =A0 =A0 =A0 =A0call to DELAY(1000000) and assuming that the i8254 runs > =A0 =A0 =A0 =A0at the nominal rate, 1.193182 MHz. > =A0 =A0 =A0 =A0From tests I have made, the measurement in init_TSC() retu= rns > =A0 =A0 =A0 =A0a large error when HZ is large, whereas repeating the meas= urement > =A0 =A0 =A0 =A0at a later time returns a much more reliable value. > =A0 =A0 =A0 =A0As an example, see the following: > > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at init_TSC 2323045616 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: Features=3D0x178bfbff > =A0 =A0Sep =A06 14:21:59 lr kernel: AMD Features=3D0xea500800 > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC: P-state invariant > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at cpu_startup_end 2323056= 910 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at acpi_timer_probe 231125= 4060 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at acpi_timer_probe_2 2311= 191310 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at pn_probe_start 23008226= 48 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300830= 946 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at pn_probe_start 23008401= 33 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300835= 253 Hz > =A0 =A0Sep =A06 14:21:59 lr kernel: TSC clock: at lapic_setup_clock 23008= 68376 Hz > > =A0 =A0 =A0 =A0The latter values are close to what is reported when HZ=3D= 1000. > > [Note 4] DELAY() uses the TSC when available, but perhaps for > =A0 =A0 =A0 =A0larger intervals (say above 100ms) it might be better > =A0 =A0 =A0 =A0to always use the 8254 which at least does not change freq= uency > =A0 =A0 =A0 =A0over time ? > > [Note 5] Linux has some high precision timers which one could expect > =A0 =A0to use for high precision delays. In fact, I ran the test > =A0 =A0program on a recent Linux 2.6.30 (using HZ=3D1000), and the > =A0 =A0usleep() version has an error between 80 and 90us irrespective > =A0 =A0of the delay. However the select() version is much worse, > =A0 =A0and loses approx 1ms per second. > > ------------------------------------------------------ > _______________________________________________ > 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" > --=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Mon Sep 7 07:16:06 2009 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 917FF106568B for ; Mon, 7 Sep 2009 07:16:06 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 206338FC26 for ; Mon, 7 Sep 2009 07:16:05 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 22274730DA; Mon, 7 Sep 2009 09:21:59 +0200 (CEST) Date: Mon, 7 Sep 2009 09:21:59 +0200 From: Luigi Rizzo To: Peter Wemm Message-ID: <20090907072159.GA18906@onelab2.iet.unipi.it> References: <20090906155154.GA8283@onelab2.iet.unipi.it> 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: stable@freebsd.org Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 07 Sep 2009 07:16:06 -0000 On Sun, Sep 06, 2009 at 05:36:29PM -0700, Peter Wemm wrote: > On Sun, Sep 6, 2009 at 8:51 AM, Luigi Rizzo wrote: > > (this problem seems to affect both current and -stable, > > so let's see if here i have better luck) > > > > I just noticed [Note 1,2] that when setting HZ > 2500 (even if it is > > an exact divisor of the APIC/CPU clock) there is a significant > > drift between the delays generated by usleep()/select() and those > > computed by gettimeofday(). ?In other words, the error grows with > > the amount of delay requested. > > > > To show the problem, try this function > > > > ? ? ? ?int f(int wait_time) { ?// wait_time in usec > > ? ? ? ? ? ? ? ?struct timeval start, end; > > ? ? ? ? ? ? ? ?gettimeofday(&start); > > ? ? ? ? ? ? ? ?usleep(w); ? ? ?// or try select > > ? ? ? ? ? ? ? ?gettimeofday(&end) > > ? ? ? ? ? ? ? ?timersub(&end, &start, &x); > > ? ? ? ? ? ? ? ?return = x.tv_usec + 1000000*x.tv_sec - wait_time; > > ? ? ? ?} > > > > for various HZ (kern.hz=NNNN in /boot/loader.conf) and wait times. > > Ideally, we would expect the timings to be in error by something > > between 0 and 1 (or 2) ticks, irrespective of the value of wait_time. > > In fact, this is what you see with HZ=1000, 2000 and 2500. > > But larger values of HZ (e.g. 4000, 5000, 10k, 40k) create > > a drift of 0.5% and above (i.e. with HZ=5000, a 1-second delay > > lasts 1.0064s and a 10s delay lasts 10.062s; with HZ=10k the > > error becomes 1% and at HZ=40k the error becomes even bigger. > > Technically, it isn't even an error because the sleeps are defined as > 'at least' the value specified. If you're looking for real-time-OS > level performance, you probably need to look at one. I know a non RTOS has limitations on the guarantees it can give. But with this in mind (e.g. be happy with something that works as expected just 'most of the times'), on this specific issue FreeBSD could behave much better while still remaining technically correct. > > 3. ?CAUSE an error in tvtohz(), reported long ago in > > ? ? ? ?http://www.dragonflybsd.org/presentations/nanosleep/ > > ? ? ? ?which causes a systematic error of an extra tick in the computation > > ? ? ? ?of the sleep times. > > ? ?FIX: the above link also contains a proposed fix (which in fact > > ? ? ? ?reverts a bug introduced in some old commit on FreeBSD) > > ? ?PROBLEM: none that i see. > > This change, as-is, is extremely dangerous. tsleep/msleep() use a > value of 0 meaning 'forever'. Changing tvtohz() so that it can now > return 0 for a non-zero tv is setting land-mines all over the place. > There's something like 27 callers of tvtohz() in sys/kern alone, some > of which are used to supply tsleep/msleep() timeouts. Note that the > dragonflybsd patch above only adds the 'returns 0' check to one single > caller. You either need to patch all callers of tvtohz() since you've > change the semantics, or add a 'if (ticks == 0) ticks = 1' check (or > checks) in the appropriate places inside tvtohz(). > > If you don't do it, then you end up with callers of random functions > with very small timeouts instead finding themselves sleeping forever. You are right, a proper fix for this third issue should be different (if we want a fix at all -- I'd be almost satisfied by just removing the drift). The simplest option is perhaps to compute a custom value for nanosleep, select and poll. This would remove the risk of side effects to other parts of the system, and we could also use the chance to compensate for the errors that arise when hz*tick != 1000000 or when we know that hardclock does not run exactly every 'tick' (an integer) microseconds. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Mon Sep 7 09:37:27 2009 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 2BE6E1065670; Mon, 7 Sep 2009 09:37:27 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 75AD18FC14; Mon, 7 Sep 2009 09:37:26 +0000 (UTC) Received: by bwz2 with SMTP id 2so243308bwz.43 for ; Mon, 07 Sep 2009 02:37:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=B3hir2z9ETfG8nqQUASiCmuZH2wm+79iNdqfr0lZ4WE=; b=pzgxS2JTB5VRHom2bdpzcZE9v1BObTIhjCcF+zyfZOTzhIPz7PtuiTRopoM2onwgyG 3WS85ruKna55k36wpGP9Aex2m/FFum3ldUdS6jOsfjllj7wwT20Lt8YNj9rdmi4vHHat 9rZD6R6QsL2e3qEELFmufLCft+emCBSPwQtCs= 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=omTT4qUy8jJc6G4F7e4e9F+hM+KlyHIsuXxRAFMIMhusKYNjtXM/yY751iKlbcWDYR ZcZU/0lQ2TutRAVWknt8I/E4Y7xdBIh1VtyIAyjzFV/h5qq1CUef7wUsnNfq0TRgLFMq ZpeuHAw/iGHCezdbsDuWimGWRvAbiFMwoa30k= MIME-Version: 1.0 Received: by 10.204.26.150 with SMTP id e22mr11957784bkc.68.1252316245452; Mon, 07 Sep 2009 02:37:25 -0700 (PDT) In-Reply-To: <200908141122.n7EBM9ml032712@svn.freebsd.org> References: <200908141122.n7EBM9ml032712@svn.freebsd.org> Date: Mon, 7 Sep 2009 13:37:25 +0400 Message-ID: From: pluknet To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable Subject: Re: svn commit: r196210 - in stable/8/sys: . amd64/include/xen cddl/contrib/opensolaris contrib/dev/acpica contrib/pf dev/ata dev/cxgb dev/sound/usb dev/usb dev/usb/controller dev/usb/input dev/usb/mis... 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, 07 Sep 2009 09:37:27 -0000 2009/8/14 Konstantin Belousov : > Author: kib > Date: Fri Aug 14 11:22:09 2009 > New Revision: 196210 > URL: http://svn.freebsd.org/changeset/base/196210 > > Log: > =A0MFC r196206: > =A0Take the number of allocated freeblks into consideration for > =A0softdep_slowdown(), to prevent kernel memory exhaustioni on > =A0mass-truncation. > > =A0Approved by: =A0re (rwatson) > [...] Hi. Is it scheduled to be merged to stable/7 (and even to stable/6, which also has this issue)? Thanks. > Modified: stable/8/sys/ufs/ffs/ffs_softdep.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > --- stable/8/sys/ufs/ffs/ffs_softdep.c =A0Fri Aug 14 11:17:34 2009 =A0 = =A0 =A0 =A0(r196209) > +++ stable/8/sys/ufs/ffs/ffs_softdep.c =A0Fri Aug 14 11:22:09 2009 =A0 = =A0 =A0 =A0(r196210) > @@ -663,6 +663,8 @@ static int req_clear_inodedeps; =A0 =A0 /* synce > =A0static int req_clear_remove; =A0 /* syncer process flush some freeblks= */ > =A0#define FLUSH_REMOVE =A0 =A0 =A0 =A0 =A0 2 > =A0#define FLUSH_REMOVE_WAIT =A0 =A0 =A03 > +static long num_freeblkdep; =A0 =A0/* number of freeblks workitems alloc= ated */ > + > =A0/* > =A0* runtime statistics > =A0*/ > @@ -2223,6 +2225,9 @@ softdep_setup_freeblocks(ip, length, fla > =A0 =A0 =A0 =A0freeblks->fb_uid =3D ip->i_uid; > =A0 =A0 =A0 =A0freeblks->fb_previousinum =3D ip->i_number; > =A0 =A0 =A0 =A0freeblks->fb_devvp =3D ip->i_devvp; > + =A0 =A0 =A0 ACQUIRE_LOCK(&lk); > + =A0 =A0 =A0 num_freeblkdep++; > + =A0 =A0 =A0 FREE_LOCK(&lk); > =A0 =A0 =A0 =A0extblocks =3D 0; > =A0 =A0 =A0 =A0if (fs->fs_magic =3D=3D FS_UFS2_MAGIC) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0extblocks =3D btodb(fragroundup(fs, ip->i_= din2->di_extsize)); > @@ -2815,6 +2820,7 @@ handle_workitem_freeblocks(freeblks, fla > > =A0 =A0 =A0 =A0ACQUIRE_LOCK(&lk); > =A0 =A0 =A0 =A0WORKITEM_FREE(freeblks, D_FREEBLKS); > + =A0 =A0 =A0 num_freeblkdep--; > =A0 =A0 =A0 =A0FREE_LOCK(&lk); > =A0} > > @@ -5768,7 +5774,8 @@ softdep_slowdown(vp) > =A0 =A0 =A0 =A0max_softdeps_hard =3D max_softdeps * 11 / 10; > =A0 =A0 =A0 =A0if (num_dirrem < max_softdeps_hard / 2 && > =A0 =A0 =A0 =A0 =A0 =A0num_inodedep < max_softdeps_hard && > - =A0 =A0 =A0 =A0 =A0 VFSTOUFS(vp->v_mount)->um_numindirdeps < maxindirde= ps) { > + =A0 =A0 =A0 =A0 =A0 VFSTOUFS(vp->v_mount)->um_numindirdeps < maxindirde= ps && > + =A0 =A0 =A0 =A0 =A0 num_freeblkdep < max_softdeps_hard) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0FREE_LOCK(&lk); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return (0); > =A0 =A0 =A0 =A0} --=20 wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Mon Sep 7 14:44:30 2009 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 F30D91065679; Mon, 7 Sep 2009 14:44:29 +0000 (UTC) (envelope-from kensmith@buffalo.edu) Received: from localmailD.acsu.buffalo.edu (localmailD.acsu.buffalo.edu [128.205.5.208]) by mx1.freebsd.org (Postfix) with ESMTP id C5D778FC08; Mon, 7 Sep 2009 14:44:29 +0000 (UTC) Received: from localmailD.acsu.buffalo.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6F2CB618C3; Mon, 7 Sep 2009 10:26:43 -0400 (EDT) Received: from localmailD.acsu.buffalo.edu (localhost [127.0.0.1]) by localmailD.acsu.buffalo.edu (Postfix) with ESMTP id C3CBBC1896; Mon, 7 Sep 2009 10:26:41 -0400 (EDT) Received: from mweb2.acsu.buffalo.edu (mweb2.acsu.buffalo.edu [128.205.5.239]) by localmailD.acsu.buffalo.edu (Prefixe) with ESMTP id BC463C1895; Mon, 7 Sep 2009 10:26:41 -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 A566A207B4; Mon, 7 Sep 2009 10:26:41 -0400 (EDT) From: Ken Smith To: freebsd-current , freebsd-stable Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-xmSWkBgDt4b8l14MH12L" Date: Mon, 07 Sep 2009 10:26:38 -0400 Message-Id: <1252333598.56240.23.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 FreeBSD GNOME Team Port X-PM-EL-Spam-Prob: : 8% Cc: Subject: 8.0-BETA4 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: Mon, 07 Sep 2009 14:44:30 -0000 --=-xmSWkBgDt4b8l14MH12L Content-Type: text/plain Content-Transfer-Encoding: quoted-printable The fourth and most likely final BETA build for the FreeBSD 8.0 release cycle is now available. We expect the next test build to be the first if the Release Candidates, RC1. Since BETA3 many bugs that were identified from testing done so far were addressed. Some of the bigger issues were an mbuf leak along with work done in the general IPv6, jail, and usb subsystems. Issues in other areas have been addressed as well. Due to the issues identified in this early phase of testing the schedule for release has been pushed back. The current target for the release itself is September 29th, with two RC builds between now and then. Details about the current target schedule along with much more detail about the current status of the release is available here: http://wiki.freebsd.org/8.0TODO If you notice problems you can report them through the normal Gnats PR system or on the freebsd-current mailing list. I do cross-post announcements to freebsd-stable because this particular release is "about to become a stable branch" but when it comes to watching for issues related to the release most of the developers pay more attention to the freebsd-current list. ISO images for all supported architectures are available on the FTP sites, (sparc64 was uploaded a short time ago and may not be available on some sites yet) and a "memory stick" image is available for amd64/i386 architectures. For amd64/i386 architectures the cdrom and memstick images include the documentation packages this time but no other packages. The DVD image includes a first rough pass at what packages will be available but the list will certainly change between now and release. None of the other images include packages. If you are using csup/cvsup methods to update an older system the branch tag to use is RELENG_8. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, or 8.0-BETA3 can upgrade as follows: =20 # freebsd-update upgrade -r 8.0-BETA4 =20 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. Systems running 8.0-BETA3 may print the warning INDEX-OLD.all: Invalid arguments when downloading updates; this warning is a harmless bug (fixed in 8.0-BETA4) and can be safely ignored. # freebsd-update install =20 The system must be rebooted with the newly installed kernel before continui= ng. =20 # shutdown -r now =20 After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install =20 At this point, users of systems being upgraded from FreeBSD 7.x will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See: http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html for mode details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install =20 Finally, reboot into 8.0-BETA4: =20 # shutdown -r now MD5/SHA256 checksums for the image files: MD5 (8.0-BETA4-amd64-bootonly.iso) =3D 4215023f0492e959be3c643fef44d448 MD5 (8.0-BETA4-amd64-disc1.iso) =3D f767d33bbaa0af665e33992c1f43cc39 MD5 (8.0-BETA4-amd64-dvd1.iso) =3D ac66ea49d75908607c0fe984f88b7a50 MD5 (8.0-BETA4-amd64-livefs.iso) =3D ead1d6a75cce81a24d3d3b8f0cbc8faf MD5 (8.0-BETA4-amd64-memstick.img) =3D 69629e60befe708b4373871af23d61a3 MD5 (8.0-BETA4-i386-bootonly.iso) =3D db2e16a1a807d124a693743ca7a75992 MD5 (8.0-BETA4-i386-disc1.iso) =3D 30508ce737aa29d0fe2baf2f450ddc83 MD5 (8.0-BETA4-i386-dvd1.iso) =3D 307b28a35bcfbb547ce3afbbad051e89 MD5 (8.0-BETA4-i386-livefs.iso) =3D d65f152bfbd62ea5e3c2e1858bbb89ee MD5 (8.0-BETA4-i386-memstick.img) =3D 5d262034175abd24b27ec7110ebd88a7 MD5 (8.0-BETA4-ia64-bootonly.iso) =3D 5147bd2c2dba2a72ec7f36eb8af0ccb6 MD5 (8.0-BETA4-ia64-disc1.iso) =3D 4da8a10c19c6642175a13aacf5fbf996 MD5 (8.0-BETA4-ia64-disc2.iso) =3D 895fca6034ecec7afb99878dbc93ded9 MD5 (8.0-BETA4-ia64-disc3.iso) =3D 49e440ad63251033bc154b35a48b379e MD5 (8.0-BETA4-ia64-dvd1.iso) =3D 52350dd2bd330fa58271819cb82c5e79 MD5 (8.0-BETA4-ia64-livefs.iso) =3D 93018d3777f360780272188a4473dda5 MD5 (8.0-BETA4-pc98-bootonly.iso) =3D 3c1340312e19f5a14c46fbce001fbafa MD5 (8.0-BETA4-pc98-disc1.iso) =3D 495674329c64d6d60b0d41f0922ac20a MD5 (8.0-BETA4-pc98-livefs.iso) =3D ede97f44cbf9c0205ca0b50b0b7900b9 MD5 (8.0-BETA4-powerpc-bootonly.iso) =3D 71deda0e81c1bfa1c232e85aec7b5852 MD5 (8.0-BETA4-powerpc-disc1.iso) =3D cb437fe6c588035492d30a4c9a4ec7f9 MD5 (8.0-BETA4-powerpc-disc2.iso) =3D 2c59a9fcf633c64fe9462967bbd14a93 MD5 (8.0-BETA4-powerpc-disc3.iso) =3D fb2d9d5a59518d30c28c8454bdf66ed4 MD5 (8.0-BETA4-sparc64-bootonly.iso) =3D e2cc9393e0b596acdb36a8b07fbc480e MD5 (8.0-BETA4-sparc64-disc1.iso) =3D 706f2e57ff1502ccaac37dd4571d898a MD5 (8.0-BETA4-sparc64-dvd1.iso) =3D 9ac3509c8731874ae20009f170daf0e7 SHA256 (8.0-BETA4-amd64-bootonly.iso) =3D 3b4a1b964f64e68609f8010e43145c7a7= 57c352e62b2b8128dff3947f08c330b SHA256 (8.0-BETA4-amd64-disc1.iso) =3D e42cb6a4d46fcc924615949fe9da4217f9c8= 24e4c30fb6371787e28d5ec50ff8 SHA256 (8.0-BETA4-amd64-dvd1.iso) =3D 61bb39599c2b2b76de0643d677702683c4274= 901dbaaa3944b3a419402046dcf SHA256 (8.0-BETA4-amd64-livefs.iso) =3D f6b9fc2bfe74bb7bc730fa6786af09e4cca= 8d92a812ee1968283dff3eb6adc48 SHA256 (8.0-BETA4-amd64-memstick.img) =3D a930e419bed019114ddcf5833b3af1950= f4ef32444bb02b1b84e84d91c754bda SHA256 (8.0-BETA4-i386-bootonly.iso) =3D c2adde76995cbc25ac16afb2c4cb46686d= f54435f64e98ae4701908f024a0102 SHA256 (8.0-BETA4-i386-disc1.iso) =3D 0bbee2a9ffd4c00070cae001652037c8b1945= 02dfc1a35c3ac0da1172c26bfdd SHA256 (8.0-BETA4-i386-dvd1.iso) =3D 4dcd81040e977ff2f6c30aae04497416c2aec9= eb8d4a5ac0dab6f2cd965bfaee SHA256 (8.0-BETA4-i386-livefs.iso) =3D fac4c8c08698c30801f4555d5127c8bb5d78= 6d6bebe164fd27e66bea737526bf SHA256 (8.0-BETA4-i386-memstick.img) =3D 4a39d259b18f8d900a7bfc1878ed6ac4fd= a82812e13999da0265976eb1ba15e8 SHA256 (8.0-BETA4-ia64-bootonly.iso) =3D 5688b9c8bf13337835b2dce2fa7d6fb0ea= 17d397e927ef770d097a6728c8db23 SHA256 (8.0-BETA4-ia64-disc1.iso) =3D 33ddac157f6529bb31388d8c4ffdfb4824c98= 9c0c0d843ecec071eb67ea36786 SHA256 (8.0-BETA4-ia64-disc2.iso) =3D ae71fd5d8d29666fa15689ddd8ffd45e3b6d3= 54af9e1cb96b5a62280b452cbe5 SHA256 (8.0-BETA4-ia64-disc3.iso) =3D 330b43e5f81887de948257db46ed407a5c5a9= 4c09e6d41155159e0617c0be53e SHA256 (8.0-BETA4-ia64-dvd1.iso) =3D 4324c3c08d625b92942424a1c6e14085593ee6= 2237ddd4f2eac2f35d7fb0f27b SHA256 (8.0-BETA4-ia64-livefs.iso) =3D 860cad096ef74efa534bae3642dff5ec545e= d47faa21a6cd65b197b12827885d SHA256 (8.0-BETA4-pc98-bootonly.iso) =3D 0ce882dd48863f2f4180cbdf5f17ff595d= 7942bf7ac84029adef27a65b1b5481 SHA256 (8.0-BETA4-pc98-disc1.iso) =3D 4815a84ef0e834d3d57f7420c1f25ff93d0e3= b698cc6eecee8b587f9896edd01 SHA256 (8.0-BETA4-pc98-livefs.iso) =3D cb6ea4a931551c2220c739d66f05c120926a= 7c2650373fc72770a25ea5e10a3d SHA256 (8.0-BETA4-powerpc-bootonly.iso) =3D 6f97a8c061065661996e6efdad45bbb= aaafc2e8f80717fa845b2bc3ae14d7212 SHA256 (8.0-BETA4-powerpc-disc1.iso) =3D 9b1fb4af1a9a53e5723fdfd897d8a57a4e= 815ada22637285b7360d24f512290c SHA256 (8.0-BETA4-powerpc-disc2.iso) =3D 8e82ccaca6673cb3177870748ffdcb891f= b16904eacd98822cca31f9888656ae SHA256 (8.0-BETA4-powerpc-disc3.iso) =3D 651561d9021d5c68f266f21d6df31c87fe= c1368a428492274177810ea1333c3c SHA256 (8.0-BETA4-sparc64-bootonly.iso) =3D 35dd8a303df41cb7ca744c37aee104e= 18f441967a14a3c9eb36bc4bcaf78c01b SHA256 (8.0-BETA4-sparc64-disc1.iso) =3D 1d5ab4e67225a8640c9200424a140fff00= 3203ab5edb855172d7030130974529 SHA256 (8.0-BETA4-sparc64-dvd1.iso) =3D 59ab2cca0fa637e9ef5007117f1005570c1= 02cf4665009c6021992dd1b8bd77b --=20 Ken Smith - From there to here, from here to | kensmith@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-xmSWkBgDt4b8l14MH12L Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkqlGBEACgkQ/G14VSmup/Y1vgCeIFUkql2Jfe7bInSy4pGVWmNu 8rEAn26p3YY/0nTBUMFZmnZlG2Th/VA9 =S6S0 -----END PGP SIGNATURE----- --=-xmSWkBgDt4b8l14MH12L-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 7 19:52:11 2009 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 D560B106566B for ; Mon, 7 Sep 2009 19:52:11 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id 6D52D8FC0C for ; Mon, 7 Sep 2009 19:52:11 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 7CEC4D259B; Mon, 7 Sep 2009 09:52:10 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id CDAEF153882; Mon, 7 Sep 2009 09:52:07 -1000 (HST) Date: Mon, 7 Sep 2009 09:52:07 -1000 From: Clifton Royston To: Luigi Rizzo Message-ID: <20090907195207.GD10384@lava.net> References: <20090906155154.GA8283@onelab2.iet.unipi.it> <20090907072159.GA18906@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090907072159.GA18906@onelab2.iet.unipi.it> User-Agent: Mutt/1.4.2.2i Cc: stable@freebsd.org, Peter Wemm Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 07 Sep 2009 19:52:11 -0000 On Mon, Sep 07, 2009 at 09:21:59AM +0200, Luigi Rizzo wrote: > On Sun, Sep 06, 2009 at 05:36:29PM -0700, Peter Wemm wrote: > > On Sun, Sep 6, 2009 at 8:51 AM, Luigi Rizzo wrote: > > > (this problem seems to affect both current and -stable, > > > so let's see if here i have better luck) > > > > > > I just noticed [Note 1,2] that when setting HZ > 2500 (even if it is > > > an exact divisor of the APIC/CPU clock) there is a significant > > > drift between the delays generated by usleep()/select() and those > > > computed by gettimeofday(). ?In other words, the error grows with > > > the amount of delay requested. > > > > > > To show the problem, try this function > > > > > > ? ? ? ?int f(int wait_time) { ?// wait_time in usec > > > ? ? ? ? ? ? ? ?struct timeval start, end; > > > ? ? ? ? ? ? ? ?gettimeofday(&start); > > > ? ? ? ? ? ? ? ?usleep(w); ? ? ?// or try select > > > ? ? ? ? ? ? ? ?gettimeofday(&end) > > > ? ? ? ? ? ? ? ?timersub(&end, &start, &x); > > > ? ? ? ? ? ? ? ?return = x.tv_usec + 1000000*x.tv_sec - wait_time; > > > ? ? ? ?} > > > > > > for various HZ (kern.hz=NNNN in /boot/loader.conf) and wait times. > > > Ideally, we would expect the timings to be in error by something > > > between 0 and 1 (or 2) ticks, irrespective of the value of wait_time. > > > In fact, this is what you see with HZ=1000, 2000 and 2500. > > > But larger values of HZ (e.g. 4000, 5000, 10k, 40k) create > > > a drift of 0.5% and above (i.e. with HZ=5000, a 1-second delay > > > lasts 1.0064s and a 10s delay lasts 10.062s; with HZ=10k the > > > error becomes 1% and at HZ=40k the error becomes even bigger. > > > > Technically, it isn't even an error because the sleeps are defined as > > 'at least' the value specified. If you're looking for real-time-OS > > level performance, you probably need to look at one. > > I know a non RTOS has limitations on the guarantees it can give. > But with this in mind (e.g. be happy with something that works as > expected just 'most of the times'), on this specific issue FreeBSD > could behave much better while still remaining technically correct. I agree. The best is the enemy of the good; while it will never be an RTOS, there is no reason not to make the behavior as good as possible, especially where a small investment of effort is required. > > > 3. ?CAUSE an error in tvtohz(), reported long ago in > > > ? ? ? ?http://www.dragonflybsd.org/presentations/nanosleep/ > > > ? ? ? ?which causes a systematic error of an extra tick in the computation > > > ? ? ? ?of the sleep times. > > > ? ?FIX: the above link also contains a proposed fix (which in fact > > > ? ? ? ?reverts a bug introduced in some old commit on FreeBSD) > > > ? ?PROBLEM: none that i see. > > > > This change, as-is, is extremely dangerous. tsleep/msleep() use a > > value of 0 meaning 'forever'. Changing tvtohz() so that it can now > > return 0 for a non-zero tv is setting land-mines all over the place. > > There's something like 27 callers of tvtohz() in sys/kern alone, some > > of which are used to supply tsleep/msleep() timeouts. Note that the > > dragonflybsd patch above only adds the 'returns 0' check to one single > > caller. You either need to patch all callers of tvtohz() since you've > > change the semantics, or add a 'if (ticks == 0) ticks = 1' check (or > > checks) in the appropriate places inside tvtohz(). > > > > If you don't do it, then you end up with callers of random functions > > with very small timeouts instead finding themselves sleeping forever. > > You are right, a proper fix for this third issue should be different > (if we want a fix at all -- I'd be almost satisfied by just > removing the drift). Simply returning max(1, ticks) from tvtohz, as suggested above, would eliminate this concern and still improve the performance for a great number of cases. > The simplest option is perhaps to compute a custom value for > nanosleep, select and poll. This would remove the risk of side > effects to other parts of the system, and we could also use the > chance to compensate for the errors that arise when hz*tick != > 1000000 or when we know that hardclock does not run exactly every > 'tick' (an integer) microseconds. This would also be a good solution. It would be perfectly possible to implement it in two stages - first by adapting tvothz() as above, as an immediate and hopefully non-controversial improvement, and second by refactoring the latter proposed change so that the non-sleep users (nanosleep etc.) call a separate routine which is allowed to return 0; tvtohz() could then be replaced with the degenerate function { return (ticks = trueticks(tv) ? ticks : 1; } All IMHO, of course. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Mon Sep 7 22:09:01 2009 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 2FA85106566B for ; Mon, 7 Sep 2009 22:09:01 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout012.mac.com (asmtpout012.mac.com [17.148.16.87]) by mx1.freebsd.org (Postfix) with ESMTP id 1ABE28FC0C for ; Mon, 7 Sep 2009 22:09:00 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from cswiger1.apple.com ([17.227.140.124]) by asmtp012.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KPM007LMDE4GV90@asmtp012.mac.com> for stable@freebsd.org; Mon, 07 Sep 2009 14:08:29 -0700 (PDT) Message-id: <6F002A04-5CF9-466F-AEFB-6B983C0E1980@mac.com> From: Chuck Swiger To: Luigi Rizzo In-reply-to: <20090907072159.GA18906@onelab2.iet.unipi.it> Date: Mon, 07 Sep 2009 14:08:28 -0700 References: <20090906155154.GA8283@onelab2.iet.unipi.it> <20090907072159.GA18906@onelab2.iet.unipi.it> X-Mailer: Apple Mail (2.936) Cc: stable@freebsd.org, Peter Wemm Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 07 Sep 2009 22:09:01 -0000 Hi, all-- On Sep 7, 2009, at 12:21 AM, Luigi Rizzo wrote: >>> 3. ?CAUSE an error in tvtohz(), reported long ago in >>> ? ? ? ?http://www.dragonflybsd.org/presentations/nanosleep/ >>> ? ? ? ?which causes a systematic error of an extra tick in the >>> computation >>> ? ? ? ?of the sleep times. >>> ? ?FIX: the above link also contains a proposed fix (which in fact >>> ? ? ? ?reverts a bug introduced in some old commit on FreeBSD) >>> ? ?PROBLEM: none that i see. >> >> This change, as-is, is extremely dangerous. tsleep/msleep() use a >> value of 0 meaning 'forever'. Changing tvtohz() so that it can now >> return 0 for a non-zero tv is setting land-mines all over the place. >> There's something like 27 callers of tvtohz() in sys/kern alone, some >> of which are used to supply tsleep/msleep() timeouts. Note that the >> dragonflybsd patch above only adds the 'returns 0' check to one >> single >> caller. You either need to patch all callers of tvtohz() since >> you've >> change the semantics, or add a 'if (ticks == 0) ticks = 1' check (or >> checks) in the appropriate places inside tvtohz(). >> >> If you don't do it, then you end up with callers of random functions >> with very small timeouts instead finding themselves sleeping forever. > > You are right, a proper fix for this third issue should be different > (if we want a fix at all -- I'd be almost satisfied by just > removing the drift). A while ago, I took a fairly close look at timing accuracy (ie, trying to sleep until exactly the next second or whatever, and then comparing the actual time you were woken up against the target time), did my own fancy graphs showing sawtooth waves indicating timer aliasing problems, etc. There's no question that the system is allowed to sleep longer than requested, and, if the system is busy doing other tasks, some amount of extra delay is expected and OK, but missing the target time by more than several ticks, especially if the system is idle, is bogus. The Dragonfly patch to tvtohz() definitely improves timer accuracy, but it ends up computing a tick value which is too small by one sometimes (ie, the target time lands *within* that scheduler quantum, rather than at or before the start of that tick), causing negative offsets from the desired time (ie, you woke up just a bit too soon). That's also bogus. :-) From my own testing of various platforms, as well as the results reported elsewhere, MacOS X has the most consistent timer accuracy, which is probably not too surprising given that soft realtime capabilities for audio/visual processing tasks such as iTunes, Quicktime, LogicStudio, etc are pretty important to the Mac userbase. I just compared the tvtohz() implementations in kern/kern_clock.c between FreeBSD and Darwin/XNU (specifically xnu-1228.15.4, the kernel for 10.5.8), and they are effectively identical. However, that's probably moot because Darwin uses tvtoabstime() rather than tvtohz() for the callouts in the setitimer()/getitimer() implementation from kern/kern_time.c: /* FreeBSD */ int kern_setitimer(struct thread *td, u_int which, struct itimerval *aitv, struct itimerval *oitv) { [ ... ] if (which == ITIMER_REAL) { PROC_LOCK(p); if (timevalisset(&p->p_realtimer.it_value)) callout_stop(&p->p_itcallout); getmicrouptime(&ctv); if (timevalisset(&aitv->it_value)) { callout_reset(&p->p_itcallout, tvtohz(&aitv- >it_value), realitexpire, p); timevaladd(&aitv->it_value, &ctv); } *oitv = p->p_realtimer; p->p_realtimer = *aitv; PROC_UNLOCK(p); if (timevalisset(&oitv->it_value)) { if (timevalcmp(&oitv->it_value, &ctv, <)) timevalclear(&oitv->it_value); else timevalsub(&oitv->it_value, &ctv); } [ ... ] /* Darwin */ int setitimer(struct proc *p, struct setitimer_args *uap, register_t *retval) { [ ... ] switch (uap->which) { case ITIMER_REAL: proc_spinlock(p); if (timerisset(&aitv.it_value)) { microuptime(&p->p_rtime); timevaladd(&p->p_rtime, &aitv.it_value); p->p_realtimer = aitv; if (!thread_call_enter_delayed(p->p_rcall, tvtoabstime(&p->p_rtime))) // [1] p->p_ractive++; } else { timerclear(&p->p_rtime); p->p_realtimer = aitv; if (thread_call_cancel(p->p_rcall)) p->p_ractive--; } proc_spinunlock(p); break; [ ... ] > The simplest option is perhaps to compute a custom value for > nanosleep, select and poll. This would remove the risk of side > effects to other parts of the system, and we could also use the > chance to compensate for the errors that arise when hz*tick != > 1000000 or when we know that hardclock does not run exactly every > 'tick' (an integer) microseconds. I think it would be relatively simple to adapt the DragonFly change but ensure that tztohz() returns at least 1, and that would be helpful improvement. However, in the long run, a callout mechanism based upon scheduler ticks rather than actual time values suffers an inherent loss of accuracy (you're performing an integer division of time intervals by HZ and rounding up to use the API, after all) and makes assumptions that the scheduler's clock is always running at a constant frequency such that tick * HZ is exactly a million microseconds. Regards, -- -Chuck [1]: See http://www.opensource.apple.com/source/xnu/xnu-1228.15.4/osfmk/kern/thread_call.c From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 10:39:23 2009 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 A45291065670 for ; Tue, 8 Sep 2009 10:39:23 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (spirit.gamesnet.de [87.230.101.86]) by mx1.freebsd.org (Postfix) with ESMTP id 607538FC20 for ; Tue, 8 Sep 2009 10:39:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id EA124290523 for ; Tue, 8 Sep 2009 12:19:50 +0200 (CEST) X-Virus-Scanned: amavisd-new at gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jah0-u+THDGO for ; Tue, 8 Sep 2009 12:19:46 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id 8D550290516 for ; Tue, 8 Sep 2009 12:19:46 +0200 (CEST) Date: Tue, 8 Sep 2009 12:19:45 +0200 From: Tobias Lott To: freebsd-stable Message-ID: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: System crawls after Upgrade 7.0->7.2 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, 08 Sep 2009 10:39:23 -0000 Hey Everyone, I upgraded a Dual Core Machine to 7.2-Stable (2 Days ago), all OS related Stuff is located on an UFS Slice, Application is on a ZFS Volume. After the Upgrade everything seemed fine, but a User noticed one PHP Script which is basically loading a plain Textfile into Mysql times out. PHP Timeout was set to 60 secs, that was more then enough just one day before the upgrade. System-wise its like Mysql can't get get the data fast enough, process is max at 10% cpu usage most of the time in sbwait state. Haven't changed any sysctl (kern.maxvnodes="200000", vm.kmem_size="512M" vm.kmem_size_max="512M" vfs.zfs.arc_max="100M" but had those before already) or kernel parameter at that time. But according to the Wiki's ZFS Tuning Guide those aren't needed anymore so I tried without but no change there either. I checked the following (and the current used values each): maxproc maxfiles kern.ipc.somaxconn kern.ipc.nmbclusters Getting no error messages dmesg, syslog wise. Tried moving Mysql to the UFS Slice but same thing happens happens there. Some very basic testing like dd-ing: # dd if=/dev/da0 of=/dev/null bs=1024 count=1048576 1048576+0 records in 1048576+0 records out 1073741824 bytes transferred in 157.698602 secs (6808823 bytes/sec) FreeBSD hostname 7.2-STABLE FreeBSD 7.2-STABLE #3 r196954: Tue Sep 8 02:10:22 CEST 2009 root@hostname:/usr/obj/usr/src/sys/SPIRIT amd64 Since I upgraded the Machines zpool to version 13 already I don't really wanna go back to 7.0, but it seems the only way out atm. Hopefully someone can give me a Hint where maybe I forgot to check. Somehow it feels like the last Versions, I'd say starting with 7.x doesn't really feel that Rock-Stable as Versions Prior used to be. Prolly cause I'm using an Experimental Feature like ZFS, so no Offense nor Blame and this is not intended as a Flame or whatsoever! So don't get me wrong, I always liked, used, recommended FreeBSD since 4.0 and will continue to do so! Best Regards -- Tobias Lott From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 12:37:32 2009 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 D12BE1065679 for ; Tue, 8 Sep 2009 12:37:32 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 450D78FC17 for ; Tue, 8 Sep 2009 12:37:31 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-154-162.lns11.adl6.internode.on.net [121.45.154.162]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n88CbTCM063685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 8 Sep 2009 22:07:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Tue, 8 Sep 2009 22:07:03 +0930 User-Agent: KMail/1.9.10 References: <200908201204.24914.doconnor@gsoft.com.au> In-Reply-To: <200908201204.24914.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1265019.9Vy9aMJiMZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909082207.24169.doconnor@gsoft.com.au> X-Spam-Score: -1.582 () AWL,BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Subject: Re: Blocked process 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, 08 Sep 2009 12:37:32 -0000 --nextPart1265019.9Vy9aMJiMZ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 20 Aug 2009, Daniel O'Connor wrote: > Unfortunately the system is in Finland and I'm in Australia so I > can't sit at the console :( Someone visited the site and determined that the floppy drive cable was=20 intermittently fouling the CPU fan. I believe this was causing the CPU=20 to overheat and be throttled by the BIOS. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1265019.9Vy9aMJiMZ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKplAD5ZPcIHs/zowRAp/dAJ47UI4N228JoSx+XHzzpYTzPI1INgCglTuj LyHQg7dYlOl74AyCs4OdS7s= =pB6o -----END PGP SIGNATURE----- --nextPart1265019.9Vy9aMJiMZ-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 12:39:41 2009 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 46995106574C for ; Tue, 8 Sep 2009 12:39:41 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id AF6A38FC1D for ; Tue, 8 Sep 2009 12:39:40 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-154-162.lns11.adl6.internode.on.net [121.45.154.162]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n88CdchZ063737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 8 Sep 2009 22:09:39 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: FreeBSD Stable Date: Tue, 8 Sep 2009 22:09:36 +0930 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2203584.XaaQBOYEgD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909082209.37454.doconnor@gsoft.com.au> X-Spam-Score: -1.585 () AWL,BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Subject: Detecting CPU throttling on over temperature 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, 08 Sep 2009 12:39:41 -0000 --nextPart2203584.XaaQBOYEgD Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I recently discovered a system where the floppy drive cable was=20 intermittently fouling the CPU fan - I believe this caused the CPU to=20 overheat and then get throttled by the BIOS. Does anyone know if it is possible to determine if this is the case? ie=20 is there a way to be informed if throttling has occurred? Thanks. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2203584.XaaQBOYEgD Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKplCJ5ZPcIHs/zowRAgGpAKCda+Ns1+hLPAKVz2lI+xi4MRMljACcDHk9 BfvZtlPKckmM+BhYchhNqk4= =mvR9 -----END PGP SIGNATURE----- --nextPart2203584.XaaQBOYEgD-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 14:25:41 2009 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 8917F1065695 for ; Tue, 8 Sep 2009 14:25:41 +0000 (UTC) (envelope-from hrkfdn@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id 1EA908FC25 for ; Tue, 8 Sep 2009 14:25:40 +0000 (UTC) Received: by ewy4 with SMTP id 4so1705911ewy.36 for ; Tue, 08 Sep 2009 07:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=eNoimdiCNinFB5nocpx2QhAnTEuEzKZzS1ZLa5bH/C0=; b=QpB9W9/UAB3RSBMOkIT72MCVypTxlnbk3HuegxF+d8+1dIboo87bYNwYRbxmX2yFey hO0Ad05qDYoZ25MDWQfsAgAGvlH4Rdl8n2n/Qv04GwAPUJC10fvazuWXIv5Nd00GpKnV FZ+0Z3rgZafS7e2aso1G+d0JqAj2mvferACSo= 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=AnR0owBajn/CEF2tDPNrDB9aSpvfwD7xF23Q7k3PZIiWLE02K/akgSYJ4BgrxpenqF BiZ5F2jjUDRwnavx77leuD1oR+peWC7CYNZoc8lr1A8mF9xbNS2qHT0vX7Uyxmjgk0qf 01Igy0tBf2GnocwdZ5Oz8SqpUNzbwBE10hYxo= MIME-Version: 1.0 Received: by 10.211.128.9 with SMTP id f9mr17597905ebn.93.1252417967940; Tue, 08 Sep 2009 06:52:47 -0700 (PDT) In-Reply-To: <200909082209.37454.doconnor@gsoft.com.au> References: <200909082209.37454.doconnor@gsoft.com.au> Date: Tue, 8 Sep 2009 15:52:47 +0200 Message-ID: From: Henrik Friedrichsen To: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Detecting CPU throttling on over temperature 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, 08 Sep 2009 14:25:41 -0000 I don't know whether there is a more convenient way, but you could definitely check the current CPU frequency to detect whether it changed from the previous one or not. There are several ways to this, depends on the CPU. You can try messing with cpufreq(4). On Tue, Sep 8, 2009 at 2:39 PM, Daniel O'Connor wrot= e: > Hi, > I recently discovered a system where the floppy drive cable was > intermittently fouling the CPU fan - I believe this caused the CPU to > overheat and then get throttled by the BIOS. > > Does anyone know if it is possible to determine if this is the case? ie > is there a way to be informed if throttling has occurred? > > Thanks. > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > =C2=A0-- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 15:23:36 2009 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 EC7D0106566B for ; Tue, 8 Sep 2009 15:23:36 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 618778FC18 for ; Tue, 8 Sep 2009 15:23:36 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id n88FNXFF006455; Tue, 8 Sep 2009 17:23:34 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 0203224; Tue, 8 Sep 2009 17:23:32 +0200 (CEST) Date: Tue, 8 Sep 2009 17:23:32 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-stable@freebsd.org Message-Id: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.9.8.150616 Cc: freebsd-fs@freebsd.org Subject: zfs kernel panic 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, 08 Sep 2009 15:23:37 -0000 Hi folks, I just upgraded a zfs server from 7.0-something to 7.2-stable and hoped to get rid of some minor instabilities I experienced every 6 months or so. Unfortunately, the new system crashed for the first time after only a few hours when copying some files via scp onto it. I got a kernel panic which looked quite similar to the one reported here (kmem_map too small): I have a dual cpu dual core opteron system with 4GB of RAM and a 3-disk raidz1. I took out the memory settings from loader.conf as suggested in UPDATING. I did not yet upgrade zpool nor zfs version (would that help?). Are there any known issues or any further hints what might cause the crash? I copied the files again, but this time everything went fine. cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 15:39:47 2009 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 84284106568B; Tue, 8 Sep 2009 15:39:47 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 3C3208FC13; Tue, 8 Sep 2009 15:39:47 +0000 (UTC) Received: from c83-253-252-234.bredband.comhem.se ([83.253.252.234]:58698 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Ml2nB-0004xF-5A; Tue, 08 Sep 2009 17:39:39 +0200 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 1AB0D1DF75; Tue, 8 Sep 2009 17:38:58 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1075.2) Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes From: Thomas Backman In-Reply-To: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> Date: Tue, 8 Sep 2009 17:38:55 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> To: =?iso-8859-1?Q?Gerrit_K=FChn?= X-Mailer: Apple Mail (2.1075.2) X-Originating-IP: 83.253.252.234 X-Scan-Result: No virus found in message 1Ml2nB-0004xF-5A. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1Ml2nB-0004xF-5A ff9feeb5216626fda05dfcdf4d007935 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zfs kernel panic 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, 08 Sep 2009 15:39:47 -0000 On Sep 8, 2009, at 5:23 PM, Gerrit K=FChn wrote: > Hi folks, > > I just upgraded a zfs server from 7.0-something to 7.2-stable and =20 > hoped to > get rid of some minor instabilities I experienced every 6 months or =20= > so. > Unfortunately, the new system crashed for the first time after only =20= > a few > hours when copying some files via scp onto it. > I got a kernel panic which looked quite similar to the one reported =20= > here > (kmem_map too small): > = > > > I have a dual cpu dual core opteron system with 4GB of RAM and a 3-=20 > disk > raidz1. I took out the memory settings from loader.conf as suggested =20= > in > UPDATING. I did not yet upgrade zpool nor zfs version (would that =20 > help?). > Are there any known issues or any further hints what might cause the > crash? I copied the files again, but this time everything went fine. Hmm. Do you use i386 or amd64? This panic is (was?) pretty common on =20 i386 before tuning, but... 4GB RAM and an Opteron should have you =20 running amd64, no? Regards, Thomas= From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 16:44:18 2009 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 0A5A01065670; Tue, 8 Sep 2009 16:44:18 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4B0538FC13; Tue, 8 Sep 2009 16:44:17 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 90F9E45C98; Tue, 8 Sep 2009 18:44:15 +0200 (CEST) Received: from localhost (chello087206049004.chello.pl [87.206.49.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 813CF45683; Tue, 8 Sep 2009 18:44:10 +0200 (CEST) Date: Tue, 8 Sep 2009 18:44:13 +0200 From: Pawel Jakub Dawidek To: Gerrit =?iso-8859-1?Q?K=FChn?= Message-ID: <20090908164413.GC1539@garage.freebsd.pl> References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JYK4vJDZwFMowpUq" Content-Disposition: inline In-Reply-To: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zfs kernel panic 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, 08 Sep 2009 16:44:18 -0000 --JYK4vJDZwFMowpUq Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 08, 2009 at 05:23:32PM +0200, Gerrit K=FChn wrote: > Hi folks, >=20 > I just upgraded a zfs server from 7.0-something to 7.2-stable and hoped to > get rid of some minor instabilities I experienced every 6 months or so. > Unfortunately, the new system crashed for the first time after only a few > hours when copying some files via scp onto it. > I got a kernel panic which looked quite similar to the one reported here > (kmem_map too small): > >=20 > I have a dual cpu dual core opteron system with 4GB of RAM and a 3-disk > raidz1. I took out the memory settings from loader.conf as suggested in > UPDATING. I did not yet upgrade zpool nor zfs version (would that help?). > Are there any known issues or any further hints what might cause the > crash? I copied the files again, but this time everything went fine. If this is amd64, add vm.kmem_size=3D"4G" to your loader.conf back. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --JYK4vJDZwFMowpUq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKpondForvXbEpPzQRAluUAJ44tvn4pDDin8niwggxLpojwbAsEgCfSi6+ bUW230aApqoP797xQp1WpD8= =zzNS -----END PGP SIGNATURE----- --JYK4vJDZwFMowpUq-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 17:28:10 2009 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 91CF61065670 for ; Tue, 8 Sep 2009 17:28:10 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id AB7048FC1D for ; Tue, 8 Sep 2009 17:28:09 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 253775946; Tue, 08 Sep 2009 19:28:05 +0300 Message-ID: <4AA6860F.1020203@FreeBSD.org> Date: Tue, 08 Sep 2009 19:27:59 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Daniel O'Connor References: <1252426982.00160755.1252414203@10.7.7.3> In-Reply-To: <1252426982.00160755.1252414203@10.7.7.3> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 08 Sep 2009 17:28:10 -0000 Daniel O'Connor wrote: > I recently discovered a system where the floppy drive cable was > intermittently fouling the CPU fan - I believe this caused the CPU to > overheat and then get throttled by the BIOS. > > Does anyone know if it is possible to determine if this is the case? ie > is there a way to be informed if throttling has occurred? Theoretically it is possible. I know off-topic tool reporting this. Also you can just monitor CPU temperature, depending on CPU type. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 18:00:13 2009 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 756DB1065695 for ; Tue, 8 Sep 2009 18:00:13 +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 47D498FC1F for ; Tue, 8 Sep 2009 18:00:13 +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 D55CF46B39; Tue, 8 Sep 2009 14:00:12 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 241288A01B; Tue, 8 Sep 2009 14:00:12 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 8 Sep 2009 13:08:23 -0400 User-Agent: KMail/1.9.7 References: <20090906155154.GA8283@onelab2.iet.unipi.it> In-Reply-To: <20090906155154.GA8283@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909081308.23345.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 08 Sep 2009 14:00:12 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Luigi Rizzo Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 08 Sep 2009 18:00:13 -0000 On Sunday 06 September 2009 11:51:54 am Luigi Rizzo wrote: > [Note 3] the TSC frequency is computed reading the tsc around a > call to DELAY(1000000) and assuming that the i8254 runs > at the nominal rate, 1.193182 MHz. > From tests I have made, the measurement in init_TSC() returns > a large error when HZ is large, whereas repeating the measurement > at a later time returns a much more reliable value. > As an example, see the following: > > Sep 6 14:21:59 lr kernel: TSC clock: at init_TSC 2323045616 Hz > Sep 6 14:21:59 lr kernel: Features=0x178bfbff > Sep 6 14:21:59 lr kernel: AMD Features=0xea500800 > Sep 6 14:21:59 lr kernel: TSC: P-state invariant > Sep 6 14:21:59 lr kernel: TSC clock: at cpu_startup_end 2323056910 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe 2311254060 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe_2 2311191310 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300822648 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300830946 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300840133 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300835253 Hz > Sep 6 14:21:59 lr kernel: TSC clock: at lapic_setup_clock 2300868376 Hz > > The latter values are close to what is reported when HZ=1000. Try disabling legacy USB support in the BIOS to see if an SMI# is firing during the DELAY() causing the TSC freq to be too high. I have seen the USB legacy support cause this in other machines. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 18:09:15 2009 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 CD284106568B for ; Tue, 8 Sep 2009 18:09:15 +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 3A9E18FC16 for ; Tue, 8 Sep 2009 18:09:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id n88HscMl042193; Wed, 9 Sep 2009 03:54:38 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 9 Sep 2009 03:54:38 +1000 (EST) From: Ian Smith To: Henrik Friedrichsen In-Reply-To: Message-ID: <20090909030624.Y89278@sola.nimnet.asn.au> References: <200909082209.37454.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 08 Sep 2009 18:09:15 -0000 On Tue, 8 Sep 2009, Henrik Friedrichsen wrote: > I don't know whether there is a more convenient way, but you could > definitely check the current CPU frequency to detect whether it > changed from the previous one or not. There are several ways to this, > depends on the CPU. You can try messing with cpufreq(4). > > On Tue, Sep 8, 2009 at 2:39 PM, Daniel O'Connor wrote: > > Hi, > > I recently discovered a system where the floppy drive cable was > > intermittently fouling the CPU fan - I believe this caused the CPU to > > overheat and then get throttled by the BIOS. > > > > Does anyone know if it is possible to determine if this is the case? ie > > is there a way to be informed if throttling has occurred? Might be easier to hack powerd.c as an existing pretty lightweight way of monitoring CPU freq (to log or signal on detected freq lowered by throttling, say?) even if you don't need/want it to actually vary freq according to load, eg setting idle/busy shift factors to 'never/always'? cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 18:27:57 2009 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 99DF41065672 for ; Tue, 8 Sep 2009 18:27:57 +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 2E7B98FC1C for ; Tue, 8 Sep 2009 18:27:56 +0000 (UTC) Received: (qmail 3785 invoked by uid 399); 8 Sep 2009 18:27:55 -0000 Received: from localhost (HELO ?10.9.1.128?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 8 Sep 2009 18:27:55 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4AA6A22B.1070402@FreeBSD.org> Date: Tue, 08 Sep 2009 11:27:55 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: John Baldwin References: <20090902160440.GA28417@sd-13813.dedibox.fr> <4A9E98AD.1070202@FreeBSD.org> <200909030808.08440.jhb@freebsd.org> In-Reply-To: <200909030808.08440.jhb@freebsd.org> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Bjoern A. Zeeb" , FLEURIOT Damien , freebsd-jail@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Not getting an IPv6 in a jail 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, 08 Sep 2009 18:27:57 -0000 John Baldwin wrote: > On Wednesday 02 September 2009 12:09:17 pm Doug Barton wrote: >> FLEURIOT Damien wrote: >> >>> BIND's now happily running in its jail and responding to public >>> queries. >> It's up to you if you choose to do it, but there is no reason to run >> BIND in a jail. The chroot feature provided by default by rc.d/named >> is quite adequate security. > > That is debatable. One of the chief benefits of a jail is that if a server is > compromised so that an attacker can gain root access that root access is > limited in what it can do compared to a simple chroot. That is true for any > server you would run under a jail, not just BIND. On a strictly intellectual level I agree that jails are in some ways more limited than chroots. OTOH, named chroots by default into /var/named which has no binaries at all. The most "interesting" things in the chroot environment are /dev/null and /dev/random. Jails by nature have a more or less complete FreeBSD system available to the attacker. Also, in addition to being chroot'ed named runs by default as user 'bind' which is rather limited in what it can modify in the chroot. I realize that it's theoretically possible for an attacker to break out of a chroot environment, escalate their privileges, etc. I suppose my point is that if you're looking for things to tighten down on a FreeBSD system the default named configuration is not the first place I'd look. :) Doug From owner-freebsd-stable@FreeBSD.ORG Tue Sep 8 20:55:04 2009 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 A15AE106566B for ; Tue, 8 Sep 2009 20:55:04 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE4A8FC13 for ; Tue, 8 Sep 2009 20:55:04 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 3BB2D730DA; Tue, 8 Sep 2009 23:01:00 +0200 (CEST) Date: Tue, 8 Sep 2009 23:01:00 +0200 From: Luigi Rizzo To: John Baldwin Message-ID: <20090908210100.GA72735@onelab2.iet.unipi.it> References: <20090906155154.GA8283@onelab2.iet.unipi.it> <200909081308.23345.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909081308.23345.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 08 Sep 2009 20:55:04 -0000 On Tue, Sep 08, 2009 at 01:08:23PM -0400, John Baldwin wrote: > On Sunday 06 September 2009 11:51:54 am Luigi Rizzo wrote: > > [Note 3] the TSC frequency is computed reading the tsc around a > > call to DELAY(1000000) and assuming that the i8254 runs > > at the nominal rate, 1.193182 MHz. > > From tests I have made, the measurement in init_TSC() returns > > a large error when HZ is large, whereas repeating the measurement > > at a later time returns a much more reliable value. > > As an example, see the following: > > > > Sep 6 14:21:59 lr kernel: TSC clock: at init_TSC 2323045616 Hz > > Sep 6 14:21:59 lr kernel: > Features=0x178bfbff > > Sep 6 14:21:59 lr kernel: AMD > Features=0xea500800 > > Sep 6 14:21:59 lr kernel: TSC: P-state invariant > > Sep 6 14:21:59 lr kernel: TSC clock: at cpu_startup_end 2323056910 Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe 2311254060 Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe_2 2311191310 > Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300822648 Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300830946 Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300840133 Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300835253 Hz > > Sep 6 14:21:59 lr kernel: TSC clock: at lapic_setup_clock 2300868376 Hz > > > > The latter values are close to what is reported when HZ=1000. > > Try disabling legacy USB support in the BIOS to see if an SMI# is firing > during the DELAY() causing the TSC freq to be too high. I have seen the USB > legacy support cause this in other machines. Thanks, will try tomorrow. Would this explain the measurement becomes better as we get further into the initialization, and why high HZ values affect the measurement ? cheers luigi From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 00:08:10 2009 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 C0EB1106566C for ; Wed, 9 Sep 2009 00:08:10 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (sysmon.tcworks.net [65.66.76.4]) by mx1.freebsd.org (Postfix) with ESMTP id 73E6B8FC15 for ; Wed, 9 Sep 2009 00:08:10 +0000 (UTC) Received: from sysmon.tcworks.net (localhost [127.0.0.1]) by sysmon.tcworks.net (8.13.1/8.13.1) with ESMTP id n88NlJan034971 for ; Tue, 8 Sep 2009 18:47:19 -0500 (CDT) (envelope-from lambert@lambertfam.org) Received: (from lambert@localhost) by sysmon.tcworks.net (8.13.1/8.13.1/Submit) id n88NlJii034970 for freebsd-stable@freebsd.org; Tue, 8 Sep 2009 18:47:19 -0500 (CDT) (envelope-from lambert@lambertfam.org) X-Authentication-Warning: sysmon.tcworks.net: lambert set sender to lambert@lambertfam.org using -f Date: Tue, 8 Sep 2009 18:47:19 -0500 From: Scott Lambert To: freebsd-stable@freebsd.org Message-ID: <20090908234719.GC418@sysmon.tcworks.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20090902160440.GA28417@sd-13813.dedibox.fr> <4A9E98AD.1070202@FreeBSD.org> <200909030808.08440.jhb@freebsd.org> <4AA6A22B.1070402@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AA6A22B.1070402@FreeBSD.org> User-Agent: Mutt/1.4.2.2i Subject: Re: Not getting an IPv6 in a jail 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, 09 Sep 2009 00:08:10 -0000 On Tue, Sep 08, 2009 at 11:27:55AM -0700, Doug Barton wrote: > John Baldwin wrote: > > On Wednesday 02 September 2009 12:09:17 pm Doug Barton wrote: > >> FLEURIOT Damien wrote: > >> > >>> BIND's now happily running in its jail and responding to public > >>> queries. > >> > >> It's up to you if you choose to do it, but there is no reason to > >> run BIND in a jail. The chroot feature provided by default by > >> rc.d/named is quite adequate security. > > > > That is debatable. One of the chief benefits of a jail is that if > > a server is compromised so that an attacker can gain root access > > that root access is limited in what it can do compared to a simple > > chroot. That is true for any server you would run under a jail, not > > just BIND. > > On a strictly intellectual level I agree that jails are in some > ways more limited than chroots. OTOH, named chroots by default into > /var/named which has no binaries at all. The most "interesting" things > in the chroot environment are /dev/null and /dev/random. Jails by > nature have a more or less complete FreeBSD system available to the > attacker. Also, in addition to being chroot'ed named runs by default > as user 'bind' which is rather limited in what it can modify in the > chroot. > > I realize that it's theoretically possible for an attacker to break > out of a chroot environment, escalate their privileges, etc. I suppose > my point is that if you're looking for things to tighten down on a > FreeBSD system the default named configuration is not the first place > I'd look. :) Some of us are just using a jail per service to make the service more portable between these massively overpowered machines these days. For me, jails are not always just about security. I use them as cheap form of virtualization. The security seperation can be a cheap side effect of the cheap virtualization. This is especially cheap with the help of sysutils/ezjail. I do not currently have named inside a jail. I still have a few P3 boxes in service handling some of the small tasks which I haven't gotten around to rolling up yet. Named inside a chroot inside a jail is not the first thing I would go after, but when I get around to moving it off the old server hardware, why not? :-) -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 00:11:44 2009 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 AB21E1065692 for ; Wed, 9 Sep 2009 00:11:44 +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 3C26E8FC1B for ; Wed, 9 Sep 2009 00:11:44 +0000 (UTC) Received: (qmail 13037 invoked by uid 399); 9 Sep 2009 00:11:37 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 9 Sep 2009 00:11:37 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4AA6F2B3.8000909@FreeBSD.org> Date: Tue, 08 Sep 2009 17:11:31 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.23 (X11/20090822) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20090902160440.GA28417@sd-13813.dedibox.fr> <4A9E98AD.1070202@FreeBSD.org> <200909030808.08440.jhb@freebsd.org> <4AA6A22B.1070402@FreeBSD.org> <20090908234719.GC418@sysmon.tcworks.net> In-Reply-To: <20090908234719.GC418@sysmon.tcworks.net> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Not getting an IPv6 in a jail 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, 09 Sep 2009 00:11:44 -0000 Scott Lambert wrote: > Some of us are just using a jail per service to make the service more > portable between these massively overpowered machines these days. Yes, that makes total sense. I'm not saying that running it in a jail is a _bad_ thing, just that perhaps it is overkill. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 00:48:15 2009 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 2B8E51065672; Wed, 9 Sep 2009 00:48:15 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 92BF18FC13; Wed, 9 Sep 2009 00:48:14 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n890mC19002556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2009 10:18:12 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Alexander Motin Date: Wed, 9 Sep 2009 10:18:03 +0930 User-Agent: KMail/1.9.10 References: <1252426982.00160755.1252414203@10.7.7.3> <4AA6860F.1020203@FreeBSD.org> In-Reply-To: <4AA6860F.1020203@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2143077.YycXeOppJp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909091018.10509.doconnor@gsoft.com.au> X-Spam-Score: -3.608 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 00:48:15 -0000 --nextPart2143077.YycXeOppJp Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Alexander Motin wrote: > Daniel O'Connor wrote: > > I recently discovered a system where the floppy drive cable was > > intermittently fouling the CPU fan - I believe this caused the CPU > > to overheat and then get throttled by the BIOS. > > > > Does anyone know if it is possible to determine if this is the > > case? ie is there a way to be informed if throttling has occurred? > > Theoretically it is possible. I know off-topic tool reporting this. > Also you can just monitor CPU temperature, depending on CPU type. Monitoring CPU temperature is a bit difficult, there are a lack of tools=20 (although I have some code it's not complete). The problem is that the CPU temperature is only a proxy measurement, I=20 would much prefer to be told directly the BIOS is throttling rather=20 than guess :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2143077.YycXeOppJp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKpvtK5ZPcIHs/zowRArRGAJ43KPHEEicOPVx7i/L7sAF51x5N3gCcCM8F OID4CKFBz4YZYvent3BPn6g= =sI8V -----END PGP SIGNATURE----- --nextPart2143077.YycXeOppJp-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 00:50:54 2009 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 C35A81065692 for ; Wed, 9 Sep 2009 00:50:54 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 344098FC0A for ; Wed, 9 Sep 2009 00:50:53 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n890opTJ002759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2009 10:20:52 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Ian Smith Date: Wed, 9 Sep 2009 10:20:48 +0930 User-Agent: KMail/1.9.10 References: <200909082209.37454.doconnor@gsoft.com.au> <20090909030624.Y89278@sola.nimnet.asn.au> In-Reply-To: <20090909030624.Y89278@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8884801.qQvL6L6gmr"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909091020.51049.doconnor@gsoft.com.au> X-Spam-Score: -3.608 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: FreeBSD Stable , Henrik Friedrichsen Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 00:50:54 -0000 --nextPart8884801.qQvL6L6gmr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Ian Smith wrote: > > > Does anyone know if it is possible to determine if this is the > > > case? ie is there a way to be informed if throttling has > > > occurred? > > Might be easier to hack powerd.c as an existing pretty lightweight > way of monitoring CPU freq (to log or signal on detected freq lowered > by throttling, say?) even if you don't need/want it to actually vary > freq according to load, eg setting idle/busy shift factors to > 'never/always'? Hmm, that could work. It seems odd to me that there is no direct way the BIOS can notify the=20 OS it's throttling the CPU though. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart8884801.qQvL6L6gmr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKpvvq5ZPcIHs/zowRAuOsAKChwb1/uiIExkaWPthf5MagdNru5wCfakgZ pqvEk736iTlwr9s2kBQdXAU= =awGz -----END PGP SIGNATURE----- --nextPart8884801.qQvL6L6gmr-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 03:42:56 2009 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 C1B541065670 for ; Wed, 9 Sep 2009 03:42:56 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 89E0B8FC08 for ; Wed, 9 Sep 2009 03:42:55 +0000 (UTC) Received: from [192.168.1.4] (adsl-146-128-114.bna.bellsouth.net [70.146.128.114]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n893goIn048289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Sep 2009 23:42:53 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: "Daniel O'Connor" In-Reply-To: <200909091020.51049.doconnor@gsoft.com.au> References: <200909082209.37454.doconnor@gsoft.com.au> <20090909030624.Y89278@sola.nimnet.asn.au> <200909091020.51049.doconnor@gsoft.com.au> Content-Type: text/plain Organization: FreeBSD Date: Tue, 08 Sep 2009 22:42:44 -0500 Message-Id: <1252467764.85394.2903.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: Henrik Friedrichsen , FreeBSD Stable , Ian Smith Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 03:42:56 -0000 On Wed, 2009-09-09 at 10:20 +0930, Daniel O'Connor wrote: > On Wed, 9 Sep 2009, Ian Smith wrote: > > > > Does anyone know if it is possible to determine if this is the > > > > case? ie is there a way to be informed if throttling has > > > > occurred? > > > > Might be easier to hack powerd.c as an existing pretty lightweight > > way of monitoring CPU freq (to log or signal on detected freq lowered > > by throttling, say?) even if you don't need/want it to actually vary > > freq according to load, eg setting idle/busy shift factors to > > 'never/always'? > > Hmm, that could work. > > It seems odd to me that there is no direct way the BIOS can notify the > OS it's throttling the CPU though. Some BIOS can and do send an ACPI event when the proc gets hot. In my experience, this was not a good thing though. The BIOS that I remember dealing with this on would continuously send the alarms, so while TCC would kick in and throttle the CPU, the event processing kept it at 100% utilization until it was powered off to cool. I have also been able to determine that TCC had kicked in by looking at the cpu frequency via sysctl and comparing that to the max frequency reported for the proc. If the BIOS sent the alarm, but throttled the rate it wouldn't have been so bad. Not that I had any active fan control on that box to do anything about it really, but TCC might have actually worked if it wasn't flooding the acpi event processor. robert. -- Robert Noland FreeBSD From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 04:21:43 2009 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 A8903106566C for ; Wed, 9 Sep 2009 04:21:43 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 30B5D8FC08 for ; Wed, 9 Sep 2009 04:21:42 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 253799936; Wed, 09 Sep 2009 07:21:40 +0300 Message-ID: <4AA72D4D.9080505@FreeBSD.org> Date: Wed, 09 Sep 2009 07:21:33 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Daniel O'Connor References: <1252426982.00160755.1252414203@10.7.7.3> <4AA6860F.1020203@FreeBSD.org> <200909091018.10509.doconnor@gsoft.com.au> In-Reply-To: <200909091018.10509.doconnor@gsoft.com.au> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 04:21:43 -0000 Daniel O'Connor wrote: > On Wed, 9 Sep 2009, Alexander Motin wrote: >> Daniel O'Connor wrote: >>> I recently discovered a system where the floppy drive cable was >>> intermittently fouling the CPU fan - I believe this caused the CPU >>> to overheat and then get throttled by the BIOS. >>> >>> Does anyone know if it is possible to determine if this is the >>> case? ie is there a way to be informed if throttling has occurred? >> Theoretically it is possible. I know off-topic tool reporting this. >> Also you can just monitor CPU temperature, depending on CPU type. > > Monitoring CPU temperature is a bit difficult, there are a lack of tools > (although I have some code it's not complete). There indeed problems with MB monitoring, as it is non-standard. But modern CPUs also include on-chip thermal sensors. For Core2Duo family coretemp module works fine and precisely. > The problem is that the CPU temperature is only a proxy measurement, I > would much prefer to be told directly the BIOS is throttling rather > than guess :) While ACPI could implement thermal throttling, AFAIK TM1/TM2 technologies of P4 and above families are working just in CPU hardware. BIOS only initializes them. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 07:03:39 2009 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 BB38C10656B0; Wed, 9 Sep 2009 07:03:39 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id F10C98FC1B; Wed, 9 Sep 2009 07:03:38 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id n8973ZCo030612; Wed, 9 Sep 2009 09:03:37 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id D715924; Wed, 9 Sep 2009 09:03:35 +0200 (CEST) Date: Wed, 9 Sep 2009 09:03:35 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Pawel Jakub Dawidek Message-Id: <20090909090335.89a071df.gerrit@pmp.uni-hannover.de> In-Reply-To: <20090908164413.GC1539@garage.freebsd.pl> References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> <20090908164413.GC1539@garage.freebsd.pl> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.9.9.64531 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zfs kernel panic 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, 09 Sep 2009 07:03:39 -0000 On Tue, 8 Sep 2009 18:44:13 +0200 Pawel Jakub Dawidek wrote about Re: zfs kernel panic: PJD> If this is amd64, add vm.kmem_size="4G" to your loader.conf back. Yes, it is amd64 (sorry I did not mention that). I will add the option back (the one I used before was set to a somewhat lower value, something like 2G afaicr). cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 07:07:18 2009 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 93B56106566C; Wed, 9 Sep 2009 07:07:18 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id C58778FC17; Wed, 9 Sep 2009 07:07:17 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id n8977FtO030720; Wed, 9 Sep 2009 09:07:16 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 3080F24; Wed, 9 Sep 2009 09:07:15 +0200 (CEST) Date: Wed, 9 Sep 2009 09:07:15 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Pawel Jakub Dawidek Message-Id: <20090909090715.9d8a58ef.gerrit@pmp.uni-hannover.de> In-Reply-To: <20090908164413.GC1539@garage.freebsd.pl> References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> <20090908164413.GC1539@garage.freebsd.pl> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.9.9.65416 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zfs kernel panic 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, 09 Sep 2009 07:07:18 -0000 On Tue, 8 Sep 2009 18:44:13 +0200 Pawel Jakub Dawidek wrote about Re: zfs kernel panic: PJD> If this is amd64, add vm.kmem_size="4G" to your loader.conf back. What about vm.kmem_size_max? Does that also need tuning? cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 07:43:39 2009 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 6D3381065692 for ; Wed, 9 Sep 2009 07:43:39 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id D00948FC28 for ; Wed, 9 Sep 2009 07:43:38 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n897hZna016595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2009 17:13:36 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Robert Noland Date: Wed, 9 Sep 2009 17:13:31 +0930 User-Agent: KMail/1.9.10 References: <200909082209.37454.doconnor@gsoft.com.au> <200909091020.51049.doconnor@gsoft.com.au> <1252467764.85394.2903.camel@balrog.2hip.net> In-Reply-To: <1252467764.85394.2903.camel@balrog.2hip.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1456758.cC50VXJilF"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909091713.34162.doconnor@gsoft.com.au> X-Spam-Score: -3.61 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Henrik Friedrichsen , FreeBSD Stable , Ian Smith Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 07:43:39 -0000 --nextPart1456758.cC50VXJilF Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Robert Noland wrote: > On Wed, 2009-09-09 at 10:20 +0930, Daniel O'Connor wrote: > > On Wed, 9 Sep 2009, Ian Smith wrote: > > > > > Does anyone know if it is possible to determine if this is > > > > > the case? ie is there a way to be informed if throttling has > > > > > occurred? > > > > > > Might be easier to hack powerd.c as an existing pretty > > > lightweight way of monitoring CPU freq (to log or signal on > > > detected freq lowered by throttling, say?) even if you don't > > > need/want it to actually vary freq according to load, eg setting > > > idle/busy shift factors to 'never/always'? > > > > Hmm, that could work. > > > > It seems odd to me that there is no direct way the BIOS can notify > > the OS it's throttling the CPU though. > > Some BIOS can and do send an ACPI event when the proc gets hot. In > my experience, this was not a good thing though. The BIOS that I > remember dealing with this on would continuously send the alarms, so > while TCC would kick in and throttle the CPU, the event processing > kept it at 100% utilization until it was powered off to cool. I have Ugh! This system seems to stall for a few seconds and then come back, I=20 haven't see any messages about it in dmesg though. > also been able to determine that TCC had kicked in by looking at the > cpu frequency via sysctl and comparing that to the max frequency > reported for the proc. Yeah, although I couldn't run ps when the CPU was stalled so I'm not=20 sure if I'd catch it or not :) > If the BIOS sent the alarm, but throttled the rate it wouldn't have > been so bad. Not that I had any active fan control on that box to do > anything about it really, but TCC might have actually worked if it > wasn't flooding the acpi event processor. Having the BIOS or CPU do it automatically is sensible since it's a time=20 critical task.. Some basic notification would be nice though. It=20 boggles my mind how difficult it is to do such basic things sometimes.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1456758.cC50VXJilF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKp1ym5ZPcIHs/zowRAktSAJ9cfj1Vp/EKaWBkdImkKr3saykGEgCfaEge wP16fcV66CI++nJXfaPhVHI= =idir -----END PGP SIGNATURE----- --nextPart1456758.cC50VXJilF-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 08:17:24 2009 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 26AF91065670; Wed, 9 Sep 2009 08:17:24 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 899898FC1F; Wed, 9 Sep 2009 08:17:23 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n898HLPq017813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 9 Sep 2009 17:47:22 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Alexander Motin Date: Wed, 9 Sep 2009 17:47:12 +0930 User-Agent: KMail/1.9.10 References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> In-Reply-To: <4AA72D4D.9080505@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2079163.TrhI4ZJgtH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909091747.19696.doconnor@gsoft.com.au> X-Spam-Score: -3.61 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 08:17:24 -0000 --nextPart2079163.TrhI4ZJgtH Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Alexander Motin wrote: > Daniel O'Connor wrote: > > On Wed, 9 Sep 2009, Alexander Motin wrote: > >> Daniel O'Connor wrote: > >>> I recently discovered a system where the floppy drive cable was > >>> intermittently fouling the CPU fan - I believe this caused the > >>> CPU to overheat and then get throttled by the BIOS. > >>> > >>> Does anyone know if it is possible to determine if this is the > >>> case? ie is there a way to be informed if throttling has > >>> occurred? > >> > >> Theoretically it is possible. I know off-topic tool reporting > >> this. Also you can just monitor CPU temperature, depending on CPU > >> type. > > > > Monitoring CPU temperature is a bit difficult, there are a lack of > > tools (although I have some code it's not complete). > > There indeed problems with MB monitoring, as it is non-standard. But > modern CPUs also include on-chip thermal sensors. For Core2Duo family > coretemp module works fine and precisely. Ahh coretemp, I had forgotten about that. I did a test on the bench (on a 7.2 system) here and realised that I=20 can't actually detect throttling. coretemp reported 72 & 78C but the=20 frequency was still 2933MHz. I am pretty sure it would be throttling but I think that works by=20 maintaining the frequency but stalling the CPU some percentage of the=20 time. I have p4tcc loaded (in GENERIC) but it doesn't show up, I only=20 get.. dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=3D\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 2933 dev.cpu.0.freq_levels: 2933/35000 2566/30625 2199/26250 1833/21875=20 1466/17500 1099/13125 733/8750 366/4375 dev.cpu.0.cx_supported: C1/0 C2/85 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% dev.cpu.0.temperature: 44 dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=3D\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=3Dnone _UID=3D0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/0 C2/85 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% dev.cpu.1.temperature: 36 I see some odd results if I disable the fan while running 'dd=20 if=3D/dev/zero bs=3D128k count=3D5000 | md5' in a loop. The throughput seem= s=20 to remain the same (odd) but the CPU idle time goes up when it gets=20 hot. > > The problem is that the CPU temperature is only a proxy > > measurement, I would much prefer to be told directly the BIOS is > > throttling rather than guess :) > > While ACPI could implement thermal throttling, AFAIK TM1/TM2 > technologies of P4 and above families are working just in CPU > hardware. BIOS only initializes them. OK. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2079163.TrhI4ZJgtH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKp2SP5ZPcIHs/zowRAvyTAJ9ATYlx0wWM0LhhK4VkLl6a3NnSwwCfS5sX gkMUWYIRrXYwALtpSvxJuIg= =dGDv -----END PGP SIGNATURE----- --nextPart2079163.TrhI4ZJgtH-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 08:33:18 2009 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 7B7121065676; Wed, 9 Sep 2009 08:33:18 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id 315C78FC08; Wed, 9 Sep 2009 08:33:16 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id A77CE45C89; Wed, 9 Sep 2009 10:33:14 +0200 (CEST) Received: from localhost (pdawidek.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id BBE8A45684; Wed, 9 Sep 2009 10:33:09 +0200 (CEST) Date: Wed, 9 Sep 2009 10:33:13 +0200 From: Pawel Jakub Dawidek To: Gerrit =?iso-8859-1?Q?K=FChn?= Message-ID: <20090909083313.GA1901@garage.freebsd.pl> References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> <20090908164413.GC1539@garage.freebsd.pl> <20090909090715.9d8a58ef.gerrit@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <20090909090715.9d8a58ef.gerrit@pmp.uni-hannover.de> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: zfs kernel panic 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, 09 Sep 2009 08:33:18 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 09, 2009 at 09:07:15AM +0200, Gerrit K=FChn wrote: > On Tue, 8 Sep 2009 18:44:13 +0200 Pawel Jakub Dawidek > wrote about Re: zfs kernel panic: >=20 > PJD> If this is amd64, add vm.kmem_size=3D"4G" to your loader.conf back. >=20 > What about vm.kmem_size_max? Does that also need tuning? No, this should be auto-tuned to some very large value. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKp2hJForvXbEpPzQRAq37AJ9KGo5hN9S7xQCyStz9oeqsBZL3qwCfeDRT zGlTYNnNtbsgEcWNstFJHIg= =67uR -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 08:44:11 2009 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 55F44106566B for ; Wed, 9 Sep 2009 08:44:11 +0000 (UTC) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (tunnel490.ipv6.xs4all.nl [IPv6:2001:888:10:1ea::2]) by mx1.freebsd.org (Postfix) with ESMTP id D39088FC1C for ; Wed, 9 Sep 2009 08:44:10 +0000 (UTC) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.14.2/8.14.2) with ESMTP id n898i6vq038036 for ; Wed, 9 Sep 2009 10:44:06 +0200 (CEST) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.14.2/8.14.2/Submit) id n898i6tO038035 for stable@freebsd.org; Wed, 9 Sep 2009 10:44:06 +0200 (CEST) (envelope-from mail25@bzerk.org) Date: Wed, 9 Sep 2009 10:44:06 +0200 From: Ruben de Groot To: stable@freebsd.org Message-ID: <20090909084406.GA37977@ei.bzerk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Delivered-To: current@freebsd.org X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ei.bzerk.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (ei.bzerk.org [127.0.0.1]); Wed, 09 Sep 2009 10:44:09 +0200 (CEST) X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0.1 (ei.bzerk.org [192.168.179.40]); Tue, 08 Sep 2009 13:55:28 +0200 (CEST) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (ei.bzerk.org [127.0.0.1]); Tue, 08 Sep 2009 13:55:03 +0200 (CEST) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Errors-To: owner-freebsd-current@freebsd.org X-Virus-Scanned: ClamAV 0.94.1/9783/Tue Sep 8 05:50:22 2009 on ei.bzerk.org X-Virus-Status: Clean Cc: Subject: 8.0-BETA2 on soekris discarding packets? X-BeenThere: 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: Wed, 09 Sep 2009 08:44:11 -0000 Hi, I'm trying 8.0-BETA2 on a 4511 soekris board, but found a problem. Outgoing networking is fine, but it looks like incoming connections are silently discarded. No firewall is configured. Here's a tcpdump of normal outgoing DNS traffic (IP address of the soekris is 192.168.179.15): listening on sis0, link-type EN10MB (Ethernet), capture size 96 bytes 10:33:50.053875 IP 192.168.179.15.23093 > ei.lan.domain: 45893+ PTR? 255.179.168.192.in-addr.arpa. (46) 10:33:50.055038 IP ei.lan.domain > 192.168.179.15.23093: 45893 NXDomain* 0/1/0 (109) 10:33:50.066917 IP 192.168.179.15.13890 > ei.lan.domain: 45894+ PTR? 9.179.168.192.in-addr.arpa. (44) 10:33:50.067834 IP ei.lan.domain > 192.168.179.15.13890: 45894* 1/1/1 (113) And here's a dump of an incoming ssh connection: listening on sis0, link-type EN10MB (Ethernet), capture size 96 bytes 10:26:40.176756 IP ei.lan.55742 > 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 1961056657 ecr 0,sackOK,eol], length 0 10:26:43.175176 IP ei.lan.55742 > 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 1961059657 ecr 0,sackOK,eol], length 0 10:26:46.374688 IP ei.lan.55742 > 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,nop,wscale 3,nop,nop,TS val 1961062857 ecr 0,sackOK,eol], length 0 10:26:49.574197 IP ei.lan.55742 > 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,sackOK,eol], length 0 10:26:52.773759 IP ei.lan.55742 > 192.168.179.15.ssh: Flags [S], seq 1547228218, win 65535, options [mss 1460,sackOK,eol], length 0 Et cetera. No replies. This goes for all tcp ports, but ping works. nmap from another host says: # nmap soekris Starting Nmap 4.85BETA7 ( http://nmap.org ) at 2009-09-08 13:31 CEST All 1000 scanned ports on 192.168.179.15 are filtered MAC Address: 00:00:24:CB:93:28 (Connect AS) Nmap done: 1 IP address (1 host up) scanned in 21.67 seconds Anyone else seeing this? Ruben kernel config is below. include GENERIC cpu I486_CPU cpu I586_CPU ident SOEKRIS machine i386 options CPU_ELAN options CPU_SOEKRIS options HZ=150 #options CPU_ELAN_XTAL options CPU_GEODE _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 08:58:02 2009 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 BC91C106566C; Wed, 9 Sep 2009 08:58:02 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (cl-858.dus-01.de.sixxs.net [IPv6:2a01:198:200:359::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7D0FC8FC13; Wed, 9 Sep 2009 08:58:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id D00203047A6; Wed, 9 Sep 2009 10:58:01 +0200 (CEST) X-Virus-Scanned: amavisd-new at gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zd9st0t3LU4F; Wed, 9 Sep 2009 10:57:58 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id 31217304736; Wed, 9 Sep 2009 10:48:08 +0200 (CEST) Date: Wed, 9 Sep 2009 10:48:07 +0200 From: Tobias Lott To: freebsd-stable@freebsd.org, freebsd-performance@freebsd.org Message-ID: <20090909104807.633418ea@sub.han.vpn.gamesnet.de> In-Reply-To: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> References: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: System crawls after Upgrade 7.0->7.2 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, 09 Sep 2009 08:58:02 -0000 On Tue, 8 Sep 2009 12:19:45 +0200 Tobias Lott wrote: > Hey Everyone, > > I upgraded a Dual Core Machine to 7.2-Stable (2 Days ago), all OS > related Stuff is located on an UFS Slice, Application is on a ZFS > Volume. > > After the Upgrade everything seemed fine, but a User noticed one PHP > Script which is basically loading a plain Textfile into Mysql times > out. PHP Timeout was set to 60 secs, that was more then enough just > one day before the upgrade. > > System-wise its like Mysql can't get get the data fast enough, process > is max at 10% cpu usage most of the time in sbwait state. > > Haven't changed any sysctl (kern.maxvnodes="200000", > vm.kmem_size="512M" vm.kmem_size_max="512M" vfs.zfs.arc_max="100M" > but had those before already) or kernel parameter at that time. But > according to the Wiki's ZFS Tuning Guide those aren't needed anymore > so I tried without but no change there either. > > I checked the following (and the current used values each): > maxproc > maxfiles > kern.ipc.somaxconn > kern.ipc.nmbclusters > > Getting no error messages dmesg, syslog wise. > > Tried moving Mysql to the UFS Slice but same thing happens happens > there. > > Some very basic testing like dd-ing: > # dd if=/dev/da0 of=/dev/null bs=1024 count=1048576 > 1048576+0 records in > 1048576+0 records out > 1073741824 bytes transferred in 157.698602 secs (6808823 bytes/sec) > > FreeBSD hostname 7.2-STABLE FreeBSD 7.2-STABLE #3 r196954: > Tue Sep 8 02:10:22 CEST 2009 > root@hostname:/usr/obj/usr/src/sys/SPIRIT amd64 > > Since I upgraded the Machines zpool to version 13 already I don't > really wanna go back to 7.0, but it seems the only way out atm. > > Hopefully someone can give me a Hint where maybe I forgot to check. > > > Somehow it feels like the last Versions, I'd say starting with 7.x > doesn't really feel that Rock-Stable as Versions Prior used to > be. Prolly cause I'm using an Experimental Feature like ZFS, so no > Offense nor Blame and this is not intended as a Flame or whatsoever! > So don't get me wrong, I always liked, used, recommended FreeBSD since > 4.0 and will continue to do so! > > Best Regards > I've tested some more it seems the Bottleneck is the HD, Raid Array is Optimal checked it. Running bonnie++ takes like forever, couldn't finish it since its a Productive Machine, cause it renders the Server useless, every try to access the server while bonnie is running times out. Weird thing is bonnie++ is using max 1-3% CPU. But according to gstat its only ~3mb/s (displayed as 100% busy) during first 3 Tests that is. savecore: reboot after panic: page fault But had no luck with the coredumb # kgdb kernel.debug /var/crash/vmcore.12 Cannot access memory at address 0x0 Or is there any other method I could try? Cause this is getting nasty unstable -- Tobias Lott From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 10:10:13 2009 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 625B3106566C; Wed, 9 Sep 2009 10:10:13 +0000 (UTC) (envelope-from fbsd@dannysplace.net) Received: from mail.dannysplace.net (mail.dannysplace.net [80.69.71.124]) by mx1.freebsd.org (Postfix) with ESMTP id 181108FC0A; Wed, 9 Sep 2009 10:10:13 +0000 (UTC) Received: from home-iinet.dannysplace.net ([203.206.171.212] helo=[192.168.10.10]) by mail.dannysplace.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MlJeD-0004LI-Iu; Wed, 09 Sep 2009 19:39:30 +1000 Message-ID: <4AA77834.1010007@dannysplace.net> Date: Wed, 09 Sep 2009 19:41:08 +1000 From: Danny Carroll User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> <20090908164413.GC1539@garage.freebsd.pl> <20090909090715.9d8a58ef.gerrit@pmp.uni-hannover.de> <20090909083313.GA1901@garage.freebsd.pl> In-Reply-To: <20090909083313.GA1901@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-User: danny X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Exim-Version: 4.69 (build at 13-Aug-2009 20:22:24) X-Date: 2009-09-09 19:39:29 X-Connected-IP: 203.206.171.212:11565 X-Message-Linecount: 45 X-Body-Linecount: 30 X-Message-Size: 1914 X-Body-Size: 1092 X-Received-Count: 1 X-Recipient-Count: 4 X-Local-Recipient-Count: 4 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-SA-Exim-Connect-IP: 203.206.171.212 X-SA-Exim-Rcpt-To: pjd@FreeBSD.org, gerrit@pmp.uni-hannover.de, freebsd-fs@freebsd.org, freebsd-stable@freebsd.org X-SA-Exim-Mail-From: fbsd@dannysplace.net X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on ferrari.dannysplace.net X-Spam-Level: X-Spam-Status: No, score=-1.3 required=8.0 tests=ALL_TRUSTED,AWL autolearn=disabled version=3.2.5 X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on mail.dannysplace.net) Cc: freebsd-fs@freebsd.org, =?ISO-8859-1?Q?Gerrit_K=FChn?= , freebsd-stable@freebsd.org Subject: Re: zfs kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd@dannysplace.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 10:10:13 -0000 On 9/09/2009 6:33 PM, Pawel Jakub Dawidek wrote: > On Wed, Sep 09, 2009 at 09:07:15AM +0200, Gerrit Kühn wrote: > >> On Tue, 8 Sep 2009 18:44:13 +0200 Pawel Jakub Dawidek >> wrote about Re: zfs kernel panic: >> >> PJD> If this is amd64, add vm.kmem_size="4G" to your loader.conf back. >> >> What about vm.kmem_size_max? Does that also need tuning? >> > No, this should be auto-tuned to some very large value. > > Pawel (et al), Would it be possible for you to post to the list your ideas of a complete set of tuning parameters for ZFS on amd64? I have used the wiki article as a reference (http://wiki.freebsd.org/ZFSTuningGuide) but it states that if you have > 2g ram and 7.2 then you do not need to tune at all. I for one would be interested in learning a little more about how the memory should be tuned. Specifically what might be interesting is to know, once a parameter is set, is there an easy way to find out how it's being used? i.e. If you start limiting the arc, is is possible to know what sort of hit/miss rate you are getting. -D From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 10:44:02 2009 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 BE03D1065696; Wed, 9 Sep 2009 10:44:02 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id 0D9028FC17; Wed, 9 Sep 2009 10:44:01 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id C008445CD9; Wed, 9 Sep 2009 12:43:59 +0200 (CEST) Received: from localhost (pdawidek.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id A205E45CA0; Wed, 9 Sep 2009 12:43:54 +0200 (CEST) Date: Wed, 9 Sep 2009 12:43:58 +0200 From: Pawel Jakub Dawidek To: Danny Carroll Message-ID: <20090909104358.GG1901@garage.freebsd.pl> References: <20090908172332.476d9e0b.gerrit@pmp.uni-hannover.de> <20090908164413.GC1539@garage.freebsd.pl> <20090909090715.9d8a58ef.gerrit@pmp.uni-hannover.de> <20090909083313.GA1901@garage.freebsd.pl> <4AA77834.1010007@dannysplace.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ahP6B03r4gLOj5uD" Content-Disposition: inline In-Reply-To: <4AA77834.1010007@dannysplace.net> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 8.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=4.5 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org, Gerrit =?iso-8859-1?Q?K=FChn?= , freebsd-stable@freebsd.org Subject: Re: zfs kernel panic 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, 09 Sep 2009 10:44:02 -0000 --ahP6B03r4gLOj5uD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 09, 2009 at 07:41:08PM +1000, Danny Carroll wrote: > On 9/09/2009 6:33 PM, Pawel Jakub Dawidek wrote: > >On Wed, Sep 09, 2009 at 09:07:15AM +0200, Gerrit K=FChn wrote: > > =20 > >>On Tue, 8 Sep 2009 18:44:13 +0200 Pawel Jakub Dawidek > >>wrote about Re: zfs kernel panic: > >> > >>PJD> If this is amd64, add vm.kmem_size=3D"4G" to your loader.conf bac= k. > >> > >>What about vm.kmem_size_max? Does that also need tuning? > >> =20 > >No, this should be auto-tuned to some very large value. > > > > =20 > Pawel (et al), >=20 > Would it be possible for you to post to the list your ideas of a=20 > complete set of tuning parameters for ZFS on amd64? I have used the=20 > wiki article as a reference (http://wiki.freebsd.org/ZFSTuningGuide) but= =20 > it states that if you have > 2g ram and 7.2 then you do not need to tune= =20 > at all. I think that was the idea, although I see no reason to have less kernel address space than physical memory (except there might be other in-kernel variables auto-tuned based on kmem size). > I for one would be interested in learning a little more about how the=20 > memory should be tuned. Specifically what might be interesting is to=20 > know, once a parameter is set, is there an easy way to find out how it's= =20 > being used? i.e. If you start limiting the arc, is is possible to know=20 > what sort of hit/miss rate you are getting. There are ARC statistics available here: # sysctl kstat.zfs --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ahP6B03r4gLOj5uD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFKp4buForvXbEpPzQRAoe2AKDFcQWjn0rVoeZSLczZmVM9BY5DEACg3whQ UK7cFH6qrKPIcHzdhAaRc7Q= =4+nt -----END PGP SIGNATURE----- --ahP6B03r4gLOj5uD-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 12:42:17 2009 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 5776A106566B; Wed, 9 Sep 2009 12:42:17 +0000 (UTC) (envelope-from sperber@deinprogramm.de) Received: from h615406.serverkompetenz.net (h615406.serverkompetenz.net [81.169.143.132]) by mx1.freebsd.org (Postfix) with ESMTP id 0FC828FC12; Wed, 9 Sep 2009 12:42:17 +0000 (UTC) Received: from h615406.serverkompetenz.net (localhost [127.0.0.1]) by h615406.serverkompetenz.net (Postfix) with ESMTP id D8A0E1701A; Wed, 9 Sep 2009 12:25:51 +0000 (UTC) Received: from eta.local (p5B2071D5.dip.t-dialin.net [91.32.113.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by h615406.serverkompetenz.net (Postfix) with ESMTPSA id A578F17017; Wed, 9 Sep 2009 12:25:51 +0000 (UTC) Received: by eta.local (Postfix, from userid 2246) id DBF5E4CD5FE; Wed, 9 Sep 2009 14:25:50 +0200 (CEST) From: Michael Sperber To: Robert Watson References: <4A8EAE86.2000108@t-online.hu> <4A8ECB9C.2020909@quip.cz> Date: Wed, 09 Sep 2009 14:25:50 +0200 In-Reply-To: (Robert Watson's message of "Sat, 22 Aug 2009 12:32:11 +0100 (BST)") Message-ID: User-Agent: Gnus/5.110011 (No Gnus v0.11) XEmacs/21.5-b29 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Mikael Bak , freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: Upgrade FreeBSD 7.1 to 7.2 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, 09 Sep 2009 12:42:17 -0000 Robert Watson writes: > FWIW, the main problem I ran into with my 8.0 upgrade is that 8.0 uses > the uart(4) driver for serial ports, and sio(4), 7.2's default, has > been removed. They require mutually exclusive lines in device.hints > and different /etc/ttys lines. If you rely on a serial console, I > would recommend first switching 7.2 to using uart, pausing for a bit, > and then switching forward to 8 so that you separate the risks > associated with changing console drivers from those associated with > sliding a major kernel version. Could you briefly elaborate on how that's done with 7.x? I.e. is changing device.hints and /etc/ttys enough (what changes?), or do I need to recompile the kernel? (I'm a bit confused because both uart and sio seem to be in GENERIC, but I haven't been able to active uart through device.hints. I couldn't find anything on freebsd.org or the internets, either.) A few hints would be much appreciated! -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 13:04:35 2009 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 B0C6110656C8; Wed, 9 Sep 2009 13:04:35 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 746D28FC1C; Wed, 9 Sep 2009 13:04:35 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:f19b:64af:edd1:b3cd] (unknown [IPv6:2001:7b8:3a7:0:f19b:64af:edd1:b3cd]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id AEAD45C43; Wed, 9 Sep 2009 15:04:33 +0200 (CEST) Message-ID: <4AA7A7E1.3040000@andric.com> Date: Wed, 09 Sep 2009 15:04:33 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.4pre) Gecko/20090904 Shredder/3.0b4pre MIME-Version: 1.0 To: Michael Sperber References: <4A8EAE86.2000108@t-online.hu> <4A8ECB9C.2020909@quip.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Mikael Bak , freebsd-stable@freebsd.org, Robert Watson , Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: Upgrade FreeBSD 7.1 to 7.2 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, 09 Sep 2009 13:04:35 -0000 On 2009-09-09 14:25, Michael Sperber wrote: >> If you rely on a serial console, I >> would recommend first switching 7.2 to using uart ...> > Could you briefly elaborate on how that's done with 7.x? I.e. is > changing device.hints and /etc/ttys enough (what changes?), or do I need > to recompile the kernel? You also need to remove device sio from your kernel configuration and recompile. If you have both sio and uart in your kernel (the default on 7.x IIRC), sio will take precedence. N.B: please exercise caution when doing this to a server in a colo 10000 km away. :) From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 13:08:33 2009 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 9AA7B106568F; Wed, 9 Sep 2009 13:08:33 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 7348E8FC0C; Wed, 9 Sep 2009 13:08:33 +0000 (UTC) Received: from [192.168.1.4] (adsl-146-128-114.bna.bellsouth.net [70.146.128.114]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n89D8TcL051388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2009 09:08:31 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: "Daniel O'Connor" In-Reply-To: <200909091747.19696.doconnor@gsoft.com.au> References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> Content-Type: text/plain Organization: FreeBSD Date: Wed, 09 Sep 2009 08:08:23 -0500 Message-Id: <1252501703.85394.3473.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: Alexander Motin , FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 13:08:33 -0000 On Wed, 2009-09-09 at 17:47 +0930, Daniel O'Connor wrote: > On Wed, 9 Sep 2009, Alexander Motin wrote: > > Daniel O'Connor wrote: > > > On Wed, 9 Sep 2009, Alexander Motin wrote: > > >> Daniel O'Connor wrote: > > >>> I recently discovered a system where the floppy drive cable was > > >>> intermittently fouling the CPU fan - I believe this caused the > > >>> CPU to overheat and then get throttled by the BIOS. > > >>> > > >>> Does anyone know if it is possible to determine if this is the > > >>> case? ie is there a way to be informed if throttling has > > >>> occurred? > > >> > > >> Theoretically it is possible. I know off-topic tool reporting > > >> this. Also you can just monitor CPU temperature, depending on CPU > > >> type. > > > > > > Monitoring CPU temperature is a bit difficult, there are a lack of > > > tools (although I have some code it's not complete). > > > > There indeed problems with MB monitoring, as it is non-standard. But > > modern CPUs also include on-chip thermal sensors. For Core2Duo family > > coretemp module works fine and precisely. > > Ahh coretemp, I had forgotten about that. > > I did a test on the bench (on a 7.2 system) here and realised that I > can't actually detect throttling. coretemp reported 72 & 78C but the > frequency was still 2933MHz. > > I am pretty sure it would be throttling but I think that works by > maintaining the frequency but stalling the CPU some percentage of the > time. I have p4tcc loaded (in GENERIC) but it doesn't show up, I only > get.. Is this a core2duo? IIRC, they generally don't go into TCC until around 100C. I did pull the c2d cpu docs at one point trying to look at cpufreq. If you are bored, you can grab the docs from intel and double check. robert. > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.freq: 2933 > dev.cpu.0.freq_levels: 2933/35000 2566/30625 2199/26250 1833/21875 > 1466/17500 1099/13125 733/8750 366/4375 > dev.cpu.0.cx_supported: C1/0 C2/85 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% > dev.cpu.0.temperature: 44 > dev.cpu.1.%desc: ACPI CPU > dev.cpu.1.%driver: cpu > dev.cpu.1.%location: handle=\_PR_.CPU1 > dev.cpu.1.%pnpinfo: _HID=none _UID=0 > dev.cpu.1.%parent: acpi0 > dev.cpu.1.cx_supported: C1/0 C2/85 > dev.cpu.1.cx_lowest: C1 > dev.cpu.1.cx_usage: 100.00% 0.00% > dev.cpu.1.temperature: 36 > > I see some odd results if I disable the fan while running 'dd > if=/dev/zero bs=128k count=5000 | md5' in a loop. The throughput seems > to remain the same (odd) but the CPU idle time goes up when it gets > hot. > > > > The problem is that the CPU temperature is only a proxy > > > measurement, I would much prefer to be told directly the BIOS is > > > throttling rather than guess :) > > > > While ACPI could implement thermal throttling, AFAIK TM1/TM2 > > technologies of P4 and above families are working just in CPU > > hardware. BIOS only initializes them. > > OK. -- Robert Noland FreeBSD From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 13:16:16 2009 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 F2794106566B; Wed, 9 Sep 2009 13:16:16 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 33FF88FC12; Wed, 9 Sep 2009 13:16:15 +0000 (UTC) Received: from orphanage.alkar.net (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPA id 253848432; Wed, 09 Sep 2009 16:16:12 +0300 Message-ID: <4AA7AA9B.9010709@FreeBSD.org> Date: Wed, 09 Sep 2009 16:16:11 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.22 (X11/20090805) MIME-Version: 1.0 To: Robert Noland References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> In-Reply-To: <1252501703.85394.3473.camel@balrog.2hip.net> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 13:16:17 -0000 Robert Noland wrote: > On Wed, 2009-09-09 at 17:47 +0930, Daniel O'Connor wrote: >> On Wed, 9 Sep 2009, Alexander Motin wrote: >>> Daniel O'Connor wrote: >>>> On Wed, 9 Sep 2009, Alexander Motin wrote: >>>>> Daniel O'Connor wrote: >>>>>> I recently discovered a system where the floppy drive cable was >>>>>> intermittently fouling the CPU fan - I believe this caused the >>>>>> CPU to overheat and then get throttled by the BIOS. >>>>>> >>>>>> Does anyone know if it is possible to determine if this is the >>>>>> case? ie is there a way to be informed if throttling has >>>>>> occurred? >>>>> Theoretically it is possible. I know off-topic tool reporting >>>>> this. Also you can just monitor CPU temperature, depending on CPU >>>>> type. >>>> Monitoring CPU temperature is a bit difficult, there are a lack of >>>> tools (although I have some code it's not complete). >>> There indeed problems with MB monitoring, as it is non-standard. But >>> modern CPUs also include on-chip thermal sensors. For Core2Duo family >>> coretemp module works fine and precisely. >> Ahh coretemp, I had forgotten about that. >> >> I did a test on the bench (on a 7.2 system) here and realised that I >> can't actually detect throttling. coretemp reported 72 & 78C but the >> frequency was still 2933MHz. >> >> I am pretty sure it would be throttling but I think that works by >> maintaining the frequency but stalling the CPU some percentage of the >> time. I have p4tcc loaded (in GENERIC) but it doesn't show up, I only >> get.. > > Is this a core2duo? IIRC, they generally don't go into TCC until around > 100C. I did pull the c2d cpu docs at one point trying to look at > cpufreq. If you are bored, you can grab the docs from intel and double > check. AFAIR C2D supports three protection technologies. When CPU is hot, it starts reducing frequency (multiplier) and voltage, alike to IEST. If it is insufficient, it starts to skip core cycles, alike to TCC. If it is still insufficient and temperature rises above about 100C, emergency shutdown happens. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 13:27:16 2009 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 07DD4106568D; Wed, 9 Sep 2009 13:27:15 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 9B6198FC1E; Wed, 9 Sep 2009 13:27:15 +0000 (UTC) Received: from [192.168.1.4] (adsl-146-128-114.bna.bellsouth.net [70.146.128.114]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n89DRDdM051489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2009 09:27:14 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Alexander Motin In-Reply-To: <4AA7AA9B.9010709@FreeBSD.org> References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> <4AA7AA9B.9010709@FreeBSD.org> Content-Type: text/plain Organization: FreeBSD Date: Wed, 09 Sep 2009 08:27:08 -0500 Message-Id: <1252502828.85394.3503.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 13:27:16 -0000 On Wed, 2009-09-09 at 16:16 +0300, Alexander Motin wrote: > Robert Noland wrote: > > On Wed, 2009-09-09 at 17:47 +0930, Daniel O'Connor wrote: > >> On Wed, 9 Sep 2009, Alexander Motin wrote: > >>> Daniel O'Connor wrote: > >>>> On Wed, 9 Sep 2009, Alexander Motin wrote: > >>>>> Daniel O'Connor wrote: > >>>>>> I recently discovered a system where the floppy drive cable was > >>>>>> intermittently fouling the CPU fan - I believe this caused the > >>>>>> CPU to overheat and then get throttled by the BIOS. > >>>>>> > >>>>>> Does anyone know if it is possible to determine if this is the > >>>>>> case? ie is there a way to be informed if throttling has > >>>>>> occurred? > >>>>> Theoretically it is possible. I know off-topic tool reporting > >>>>> this. Also you can just monitor CPU temperature, depending on CPU > >>>>> type. > >>>> Monitoring CPU temperature is a bit difficult, there are a lack of > >>>> tools (although I have some code it's not complete). > >>> There indeed problems with MB monitoring, as it is non-standard. But > >>> modern CPUs also include on-chip thermal sensors. For Core2Duo family > >>> coretemp module works fine and precisely. > >> Ahh coretemp, I had forgotten about that. > >> > >> I did a test on the bench (on a 7.2 system) here and realised that I > >> can't actually detect throttling. coretemp reported 72 & 78C but the > >> frequency was still 2933MHz. > >> > >> I am pretty sure it would be throttling but I think that works by > >> maintaining the frequency but stalling the CPU some percentage of the > >> time. I have p4tcc loaded (in GENERIC) but it doesn't show up, I only > >> get.. > > > > Is this a core2duo? IIRC, they generally don't go into TCC until around > > 100C. I did pull the c2d cpu docs at one point trying to look at > > cpufreq. If you are bored, you can grab the docs from intel and double > > check. > > AFAIR C2D supports three protection technologies. When CPU is hot, it > starts reducing frequency (multiplier) and voltage, alike to IEST. If it > is insufficient, it starts to skip core cycles, alike to TCC. If it is > still insufficient and temperature rises above about 100C, emergency > shutdown happens. Your recollection is probably more accurate than mine. My brain is full, so every new doc that I read pushes something else out. robert. -- Robert Noland FreeBSD From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 15:38:51 2009 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 BC013106566B for ; Wed, 9 Sep 2009 15:38:51 +0000 (UTC) (envelope-from pilists@c0mplx.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 78AE68FC1D for ; Wed, 9 Sep 2009 15:38:51 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MlPFz-000CUb-Sv for freebsd-stable@freebsd.org; Wed, 09 Sep 2009 17:38:51 +0200 Date: Wed, 9 Sep 2009 17:38:51 +0200 From: Kurt Jaeger To: FreeBSD Stable Message-ID: <20090909153851.GE48206@home.opsec.eu> References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> <4AA7AA9B.9010709@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AA7AA9B.9010709@FreeBSD.org> Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 15:38:51 -0000 Hi! [on coretemp module, Alexander Motin wrote:] > AFAIR C2D supports three protection technologies. When CPU is hot, it > starts reducing frequency (multiplier) and voltage, alike to IEST. If it > is insufficient, it starts to skip core cycles, alike to TCC. If it is > still insufficient and temperature rises above about 100C, emergency > shutdown happens. Cool. I just tested coretemp on some CPU here, works very nice! Any information on what can be done with AMD CPUs with respect to temperature monitoring ? Thanks! -- pi@opsec.eu +49 171 3101372 11 years to go ! From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 15:47:26 2009 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 753841065679 for ; Wed, 9 Sep 2009 15:47:26 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B72BA8FC14 for ; Wed, 9 Sep 2009 15:47:25 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA27471; Wed, 09 Sep 2009 18:47:22 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AA7CE0A.9030502@icyb.net.ua> Date: Wed, 09 Sep 2009 18:47:22 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.22 (X11/20090724) MIME-Version: 1.0 To: Kurt Jaeger References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> In-Reply-To: <20090909153851.GE48206@home.opsec.eu> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 15:47:26 -0000 on 09/09/2009 18:38 Kurt Jaeger said the following: > Hi! > > [on coretemp module, Alexander Motin wrote:] >> AFAIR C2D supports three protection technologies. When CPU is hot, it >> starts reducing frequency (multiplier) and voltage, alike to IEST. If it >> is insufficient, it starts to skip core cycles, alike to TCC. If it is >> still insufficient and temperature rises above about 100C, emergency >> shutdown happens. > > Cool. I just tested coretemp on some CPU here, works very nice! > > Any information on what can be done with AMD CPUs with respect > to temperature monitoring ? amdtemp(4) ? :-) -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 15:52:34 2009 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 D5942106566B for ; Wed, 9 Sep 2009 15:52:34 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3FE878FC16 for ; Wed, 9 Sep 2009 15:52:34 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n89FqvDK043494; Wed, 9 Sep 2009 10:52:57 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n89Fqvdt043493; Wed, 9 Sep 2009 10:52:57 -0500 (CDT) (envelope-from brooks) Date: Wed, 9 Sep 2009 10:52:57 -0500 From: Brooks Davis To: Pyun YongHyeon , freebsd-stable Message-ID: <20090909155257.GF42196@lor.one-eyed-alien.net> References: <20090904173811.GA45176@graf.pompo.net> <20090904214148.GB9950@michelle.cdnetworks.com> <20090904215747.GB82231@lor.one-eyed-alien.net> <20090905110635.GG87716@graf.pompo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090905110635.GG87716@graf.pompo.net> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 09 Sep 2009 10:52:57 -0500 (CDT) Cc: Subject: Re: ifconfig_ed0="DHCP" does not work on 8.0-BETA3 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, 09 Sep 2009 15:52:34 -0000 On Sat, Sep 05, 2009 at 01:06:35PM +0200, Thierry Thomas wrote: > Le Ven 4 sep 09 ? 23:57:47 +0200, Brooks Davis > ?crivait?: > > > This is a know issue with some devices supported by ed(4). You can work > > around it by changing DHCP to SYNCDHCP which will cause dhclient to > > alwasy start immediatly on that interface instead of waiting for a link > > state change that never happens. > > Thanks for the hint! > > What about the following patch? > > --- man4_ed.4.diff begins here --- > --- src/share/man/man4/ed.4.orig 2009-08-03 10:13:06.000000000 +0200 > +++ src/share/man/man4/ed.4 2009-09-05 12:51:51.000000000 +0200 > @@ -425,3 +425,11 @@ > .Pp > PC Card attachment supports the D-Link DMF650TX LAN/Modem card's Ethernet > port only at this time. > +.Pp > +If the line "ed0: link state changed to UP" does not show up in dmesg, the line > +.Pp > +ifconfig_ed0="DHCP" > +.Pp > +in > +.Xr rc.conf 5 > +will be ineffective. In this case, replace "DHCP" by "SYNCDHCP". > --- man4_ed.4.diff ends here --- > > Don't hesitate to reword it - my englsh can be terrible! I'd rather not mention the "link state changed" message since I'd love to see it go away. How's this? Index: ed.4 =================================================================== --- ed.4 (revision 196736) +++ ed.4 (working copy) @@ -425,3 +425,21 @@ .Pp PC Card attachment supports the D-Link DMF650TX LAN/Modem card's Ethernet port only at this time. +.Pp +Some devices supported by +.Nm +do no generate the link state change events used by +.Xr devd 8 +to start +.Xr dhclinet 8 . +If you have problems with +.Xr dhclient 8 +not starting and the device is always attached to the network it may +be possible to work around this by changing +.Dq Li DHCP +to +.Dq Li SYNCDHCP +in the +.Va ifconfig_ed0 +entry in +.Pa /etc/rc.conf . =- Brooks From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 15:59:21 2009 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 17B1B10656A8 for ; Wed, 9 Sep 2009 15:59:21 +0000 (UTC) (envelope-from pilists@c0mplx.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id C851A8FC28 for ; Wed, 9 Sep 2009 15:59:20 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MlPZp-000CaG-88 for freebsd-stable@freebsd.org; Wed, 09 Sep 2009 17:59:21 +0200 Date: Wed, 9 Sep 2009 17:59:21 +0200 From: Kurt Jaeger To: FreeBSD Stable Message-ID: <20090909155921.GG48206@home.opsec.eu> References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> <4AA7CE0A.9030502@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AA7CE0A.9030502@icyb.net.ua> Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 15:59:21 -0000 Hi! > > Any information on what can be done with AMD CPUs with respect > > to temperature monitoring ? > > amdtemp(4) ? :-) home$ man amdtemp No manual entry for amdtemp It's on 8.0-BETA4, but I have no amd64 running with that, yet. -- pi@opsec.eu +49 171 3101372 11 years to go ! From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 16:32:56 2009 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 466CA1065692 for ; Wed, 9 Sep 2009 16:32:56 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8D2B28FC28 for ; Wed, 9 Sep 2009 16:32:55 +0000 (UTC) Received: from vhoffman.lon.namesco.net (115.73-246-213.ippool.namesco.net [213.246.73.115]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.3) with ESMTP id n89Ga4ID025636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 9 Sep 2009 17:36:06 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4AA7D8B3.1010203@unsane.co.uk> Date: Wed, 09 Sep 2009 17:32:51 +0100 From: Vincent Hoffman User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: FreeBSD Stable Mailing List X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: general protection fault on 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, 09 Sep 2009 16:32:56 -0000 Hi all, I've been running the 8.0-BETAs in a xen virtual machine (hvm/fully virtualised) for testing and something between r196730 and r196746 causes a general protection fault on boot. I'll try and narrow it down if i get a chance but I'm a a bit busy at the moment. backtrace is available at http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. Let me know if I need to provide any more info. Vince From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 17:02:15 2009 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 D1221106568F; Wed, 9 Sep 2009 17:02:15 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id 88A768FC1C; Wed, 9 Sep 2009 17:02:15 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id C2C84D0510; Wed, 9 Sep 2009 07:02:14 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 0942F153882; Wed, 9 Sep 2009 07:02:13 -1000 (HST) Date: Wed, 9 Sep 2009 07:02:13 -1000 From: Clifton Royston To: Tobias Lott Message-ID: <20090909170213.GA7925@lava.net> Mail-Followup-To: Tobias Lott , freebsd-stable@freebsd.org, freebsd-performance@freebsd.org References: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> <20090909104807.633418ea@sub.han.vpn.gamesnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090909104807.633418ea@sub.han.vpn.gamesnet.de> User-Agent: Mutt/1.4.2.2i Cc: freebsd-performance@freebsd.org, freebsd-stable@freebsd.org Subject: Re: System crawls after Upgrade 7.0->7.2 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, 09 Sep 2009 17:02:15 -0000 On Wed, Sep 09, 2009 at 10:48:07AM +0200, Tobias Lott wrote: > On Tue, 8 Sep 2009 12:19:45 +0200 > Tobias Lott wrote: > > Hey Everyone, > > > > I upgraded a Dual Core Machine to 7.2-Stable (2 Days ago), all OS > > related Stuff is located on an UFS Slice, Application is on a ZFS > > Volume. > > > > After the Upgrade everything seemed fine, but a User noticed one PHP > > Script which is basically loading a plain Textfile into Mysql times > > out. PHP Timeout was set to 60 secs, that was more then enough just > > one day before the upgrade. ... > > Since I upgraded the Machines zpool to version 13 already I don't > > really wanna go back to 7.0, but it seems the only way out atm. > > > > Hopefully someone can give me a Hint where maybe I forgot to check. > > > > Somehow it feels like the last Versions, I'd say starting with 7.x > > doesn't really feel that Rock-Stable as Versions Prior used to > > be. Prolly cause I'm using an Experimental Feature like ZFS, so no > > Offense nor Blame and this is not intended as a Flame or whatsoever! > > So don't get me wrong, I always liked, used, recommended FreeBSD since > > 4.0 and will continue to do so! > > > > Best Regards > > > > I've tested some more it seems the Bottleneck is the HD, Raid Array is > Optimal checked it. Probably you already checked this, but did you go through the dmesg output relating to ata and drive detection closely? In the past from time to time I've had machines suddenly start crawling after an upgrade, and it turned out it was because some change in the driver detection caused the ata to fall back to pio mode. The symptoms are pretty much like you describe - all HD IO takes forever. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 17:07:11 2009 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 AB6E81065672; Wed, 9 Sep 2009 17:07:11 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by mx1.freebsd.org (Postfix) with ESMTP id 795A48FC14; Wed, 9 Sep 2009 17:07:08 +0000 (UTC) Received: from smtp5-g21.free.fr (localhost [127.0.0.1]) by smtp5-g21.free.fr (Postfix) with ESMTP id 443E5D480E4; Wed, 9 Sep 2009 19:07:03 +0200 (CEST) Received: from graf.pompo.net (graf.pompo.net [78.225.128.39]) by smtp5-g21.free.fr (Postfix) with ESMTP id 5D840D48125; Wed, 9 Sep 2009 19:07:01 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id 11BA5115E3; Wed, 9 Sep 2009 19:07:01 +0200 (CEST) Date: Wed, 9 Sep 2009 19:07:01 +0200 From: Thierry Thomas To: Brooks Davis Message-ID: <20090909170701.GB38292@graf.pompo.net> Mail-Followup-To: Brooks Davis , Pyun YongHyeon , freebsd-stable References: <20090904173811.GA45176@graf.pompo.net> <20090904214148.GB9950@michelle.cdnetworks.com> <20090904215747.GB82231@lor.one-eyed-alien.net> <20090905110635.GG87716@graf.pompo.net> <20090909155257.GF42196@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20090909155257.GF42196@lor.one-eyed-alien.net> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-BETA3 i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 Cc: Pyun YongHyeon , freebsd-stable Subject: Re: ifconfig_ed0="DHCP" does not work on 8.0-BETA3 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, 09 Sep 2009 17:07:11 -0000 Le Mer 9 sep 09 à 17:52:57 +0200, Brooks Davis écrivait : > I'd rather not mention the "link state changed" message since I'd love > to see it go away. How's this? Seems good, go! -- Th. Thomas. From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 17:15:40 2009 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 86924106566C for ; Wed, 9 Sep 2009 17:15:40 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by mx1.freebsd.org (Postfix) with ESMTP id 49A378FC15 for ; Wed, 9 Sep 2009 17:15:37 +0000 (UTC) Received: from smtp5-g21.free.fr (localhost [127.0.0.1]) by smtp5-g21.free.fr (Postfix) with ESMTP id 558B2D4819D for ; Wed, 9 Sep 2009 19:15:32 +0200 (CEST) Received: from graf.pompo.net (graf.pompo.net [78.225.128.39]) by smtp5-g21.free.fr (Postfix) with ESMTP id 7251FD481F8 for ; Wed, 9 Sep 2009 19:15:30 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id 23B2D115E3; Wed, 9 Sep 2009 19:15:30 +0200 (CEST) Date: Wed, 9 Sep 2009 19:15:30 +0200 From: Thierry Thomas To: FreeBSD Stable Message-ID: <20090909171530.GC38292@graf.pompo.net> Mail-Followup-To: FreeBSD Stable References: <200909082209.37454.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <200909082209.37454.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-BETA3 i386 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc; y=\ipKMNm<1J>lv@PP~7Z<.t KjAnXLs: X-PGP: 0xC71405A2 Subject: Re: Detecting CPU throttling on over temperature 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, 09 Sep 2009 17:15:40 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le Mar 8 sep 09 =E0 14:39:36 +0200, Daniel O'Connor =E9crivait=A0: > Hi, > I recently discovered a system where the floppy drive cable was=20 > intermittently fouling the CPU fan - I believe this caused the CPU to=20 > overheat and then get throttled by the BIOS. >=20 > Does anyone know if it is possible to determine if this is the case? ie= =20 > is there a way to be informed if throttling has occurred? Have you tried the ports sysutils/lmmon and sysutils/wmlmmon? Some others exist under /usr/ports/sysutils, but I don't use them. Regards, --=20 Th. Thomas. --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqn4qsACgkQc95pjMcUBaLmJwCg/0A6JxjwZ3MtyUeavxyTaf2D cWsAoPG6U6EBxol8F3UIcbouqE4259bq =4+oG -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 18:10:00 2009 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 CE2C1106566C for ; Wed, 9 Sep 2009 18:10:00 +0000 (UTC) (envelope-from bounces4s@donateshoes.org) Received: from mail.donateshoes.org (mail.donateshoes.org [75.146.12.233]) by mx1.freebsd.org (Postfix) with ESMTP id 87EAD8FC17 for ; Wed, 9 Sep 2009 18:10:00 +0000 (UTC) Received: from 192.168.112.30 [192.168.112.30] by mail.donateshoes.org with ESMTP (SMTPD-11.0) id 668f0000005e5e0e; Wed, 9 Sep 2009 10:20:41 -0500 From: "Soles4Souls and Nine West" To: stable@freebsd.org Message-Id: <20090909102041.14885625@donateshoes.org> Date: Wed, 9 Sep 2009 10:20:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Get 15% off the Vintage America Collection for Nine West by Donating to Soles4Souls X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: marketing@donateshoes.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2009 18:10:00 -0000 Get 15% off the Vintage America Collection for Nine West by Donating to Soles4Souls From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 18:24:12 2009 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 163E8106566C for ; Wed, 9 Sep 2009 18:24:12 +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 DBAD08FC1C for ; Wed, 9 Sep 2009 18:24:11 +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 7083F46B03; Wed, 9 Sep 2009 14:24:11 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id A23498A01B; Wed, 9 Sep 2009 14:24:10 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 9 Sep 2009 13:24:53 -0400 User-Agent: KMail/1.9.7 References: <20090906155154.GA8283@onelab2.iet.unipi.it> <200909081308.23345.jhb@freebsd.org> <20090908210100.GA72735@onelab2.iet.unipi.it> In-Reply-To: <20090908210100.GA72735@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909091324.53668.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 09 Sep 2009 14:24:10 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Luigi Rizzo Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 09 Sep 2009 18:24:12 -0000 On Tuesday 08 September 2009 5:01:00 pm Luigi Rizzo wrote: > On Tue, Sep 08, 2009 at 01:08:23PM -0400, John Baldwin wrote: > > On Sunday 06 September 2009 11:51:54 am Luigi Rizzo wrote: > > > [Note 3] the TSC frequency is computed reading the tsc around a > > > call to DELAY(1000000) and assuming that the i8254 runs > > > at the nominal rate, 1.193182 MHz. > > > From tests I have made, the measurement in init_TSC() returns > > > a large error when HZ is large, whereas repeating the measurement > > > at a later time returns a much more reliable value. > > > As an example, see the following: > > > > > > Sep 6 14:21:59 lr kernel: TSC clock: at init_TSC 2323045616 Hz > > > Sep 6 14:21:59 lr kernel: > > Features=0x178bfbff > > > Sep 6 14:21:59 lr kernel: AMD > > Features=0xea500800 > > > Sep 6 14:21:59 lr kernel: TSC: P-state invariant > > > Sep 6 14:21:59 lr kernel: TSC clock: at cpu_startup_end 2323056910 Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe 2311254060 Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at acpi_timer_probe_2 2311191310 > > Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300822648 Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300830946 Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_probe_start 2300840133 Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at pn_attach_start 2300835253 Hz > > > Sep 6 14:21:59 lr kernel: TSC clock: at lapic_setup_clock 2300868376 Hz > > > > > > The latter values are close to what is reported when HZ=1000. > > > > Try disabling legacy USB support in the BIOS to see if an SMI# is firing > > during the DELAY() causing the TSC freq to be too high. I have seen the USB > > legacy support cause this in other machines. > > Thanks, will try tomorrow. > Would this explain the measurement becomes better as we get > further into the initialization, and why high HZ values affect > the measurement ? It would explain why it gets better later since the uhci(4), ohci(4) and ehci(4) drivers disable the SMI# interrupts while attaching to the controllers. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 18:24:13 2009 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 31F1B106566B for ; Wed, 9 Sep 2009 18:24:13 +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 0501E8FC17 for ; Wed, 9 Sep 2009 18:24:13 +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 AA59146B2C; Wed, 9 Sep 2009 14:24:12 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id A0E3D8A01F; Wed, 9 Sep 2009 14:24:11 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 9 Sep 2009 13:38:59 -0400 User-Agent: KMail/1.9.7 References: <4AA7D8B3.1010203@unsane.co.uk> In-Reply-To: <4AA7D8B3.1010203@unsane.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909091339.00193.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 09 Sep 2009 14:24:11 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Vincent Hoffman Subject: Re: general protection fault on 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, 09 Sep 2009 18:24:13 -0000 On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: > Hi all, > I've been running the 8.0-BETAs in a xen virtual machine > (hvm/fully virtualised) for testing and something between r196730 and > r196746 causes a general protection fault on boot. I'll try and narrow > it down if i get a chance but I'm a a bit busy at the moment. > > backtrace is available at > http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif > Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from > http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. > > Let me know if I need to provide any more info. Hmm, can you try reverting 196737? Or actually, can you print out the value of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch would fix it: Index: pmap.c =================================================================== --- pmap.c (revision 196974) +++ pmap.c (working copy) @@ -999,7 +999,7 @@ * coherence domain. */ mfence(); - for (; sva < eva; sva += cpu_clflush_line_size) + for (; sva <= eva; sva += cpu_clflush_line_size) clflush(sva); mfence(); } else { -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 18:46:53 2009 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 6EFE6106568D for ; Wed, 9 Sep 2009 18:46:53 +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 4133B8FC0C for ; Wed, 9 Sep 2009 18:46:53 +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 E715B46B38; Wed, 9 Sep 2009 14:46:52 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 292128A01F; Wed, 9 Sep 2009 14:46:52 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 9 Sep 2009 14:46:46 -0400 User-Agent: KMail/1.9.7 References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> In-Reply-To: <200909091339.00193.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909091446.47077.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 09 Sep 2009 14:46:52 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Vincent Hoffman Subject: Re: general protection fault on 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, 09 Sep 2009 18:46:53 -0000 On Wednesday 09 September 2009 1:38:59 pm John Baldwin wrote: > On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: > > Hi all, > > I've been running the 8.0-BETAs in a xen virtual machine > > (hvm/fully virtualised) for testing and something between r196730 and > > r196746 causes a general protection fault on boot. I'll try and narrow > > it down if i get a chance but I'm a a bit busy at the moment. > > > > backtrace is available at > > http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif > > Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from > > http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. > > > > Let me know if I need to provide any more info. > > Hmm, can you try reverting 196737? Or actually, can you print out the value > of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch would > fix it: > > Index: pmap.c > =================================================================== > --- pmap.c (revision 196974) > +++ pmap.c (working copy) > @@ -999,7 +999,7 @@ > * coherence domain. > */ > mfence(); > - for (; sva < eva; sva += cpu_clflush_line_size) > + for (; sva <= eva; sva += cpu_clflush_line_size) > clflush(sva); > mfence(); > } else { This patch is probably bogus. I am curious what %ebx is however. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 19:02:35 2009 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 1671B106566C; Wed, 9 Sep 2009 19:02:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 821128FC0A; Wed, 9 Sep 2009 19:02:34 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n89J2TuQ034689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2009 22:02:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n89J2Tb0044024; Wed, 9 Sep 2009 22:02:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n89J2TwJ044023; Wed, 9 Sep 2009 22:02:29 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 9 Sep 2009 22:02:28 +0300 From: Kostik Belousov To: John Baldwin Message-ID: <20090909190228.GC47688@deviant.kiev.zoral.com.ua> References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w2Ze1fp8mKggy7lw" Content-Disposition: inline In-Reply-To: <200909091339.00193.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-stable@freebsd.org, Vincent Hoffman Subject: Re: general protection fault on 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, 09 Sep 2009 19:02:35 -0000 --w2Ze1fp8mKggy7lw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 09, 2009 at 01:38:59PM -0400, John Baldwin wrote: > On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: > > Hi all, > > I've been running the 8.0-BETAs in a xen virtual machine > > (hvm/fully virtualised) for testing and something between r196730 and > > r196746 causes a general protection fault on boot. I'll try and narrow > > it down if i get a chance but I'm a a bit busy at the moment. > > =20 > > backtrace is available at > > http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif=20 > > Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from > > http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. > >=20 > > Let me know if I need to provide any more info. >=20 > Hmm, can you try reverting 196737? Or actually, can you print out the va= lue=20 > of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch woul= d=20 > fix it: >=20 > Index: pmap.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- pmap.c (revision 196974) > +++ pmap.c (working copy) > @@ -999,7 +999,7 @@ > * coherence domain. > */ > mfence(); > - for (; sva < eva; sva +=3D cpu_clflush_line_size) > + for (; sva <=3D eva; sva +=3D cpu_clflush_line_size) > clflush(sva); > mfence(); > } else { Oh, no, another pointy hat to me :(. Please, try this patch instead. diff --git a/sys/i386/xen/pmap.c b/sys/i386/xen/pmap.c index 4b81aae..122318c 100644 --- a/sys/i386/xen/pmap.c +++ b/sys/i386/xen/pmap.c @@ -1004,8 +1004,8 @@ pmap_invalidate_cache_range(vm_offset_t sva, vm_offse= t_t eva) * coherence domain. */ mfence(); - for (; eva < sva; eva +=3D cpu_clflush_line_size) - clflush(eva); + for (; sva < eva; sva +=3D cpu_clflush_line_size) + clflush(sva); mfence(); } else { =20 --w2Ze1fp8mKggy7lw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqn+8IACgkQC3+MBN1Mb4iLZACfc8+868+lMdSftGZ1wH2sIcSr 0VoAnjqHi69YrBcjQlrmPgOcx9vJfBPg =wZdP -----END PGP SIGNATURE----- --w2Ze1fp8mKggy7lw-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 19:30:28 2009 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 27281106566C for ; Wed, 9 Sep 2009 19:30:28 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (cl-858.dus-01.de.sixxs.net [IPv6:2a01:198:200:359::2]) by mx1.freebsd.org (Postfix) with ESMTP id AD5888FC16 for ; Wed, 9 Sep 2009 19:30:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id 0BED0304322 for ; Wed, 9 Sep 2009 21:30:27 +0200 (CEST) X-Virus-Scanned: amavisd-new at gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sT7PozPhAIjL for ; Wed, 9 Sep 2009 21:30:23 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id 8D8F6304315 for ; Wed, 9 Sep 2009 21:30:23 +0200 (CEST) Date: Wed, 9 Sep 2009 21:30:22 +0200 From: Tobias Lott To: freebsd-stable@freebsd.org Message-ID: <20090909213022.34d64e47@sub.han.vpn.gamesnet.de> In-Reply-To: <20090909170213.GA7925@lava.net> References: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> <20090909104807.633418ea@sub.han.vpn.gamesnet.de> <20090909170213.GA7925@lava.net> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: System crawls after Upgrade 7.0->7.2 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, 09 Sep 2009 19:30:28 -0000 On Wed, 9 Sep 2009 07:02:13 -1000 Clifton Royston wrote: > On Wed, Sep 09, 2009 at 10:48:07AM +0200, Tobias Lott wrote: > > On Tue, 8 Sep 2009 12:19:45 +0200 > > Tobias Lott wrote: > > > Hey Everyone, > > > > > > I upgraded a Dual Core Machine to 7.2-Stable (2 Days ago), all OS > > > related Stuff is located on an UFS Slice, Application is on a ZFS > > > Volume. > > > > > > After the Upgrade everything seemed fine, but a User noticed one > > > PHP Script which is basically loading a plain Textfile into Mysql > > > times out. PHP Timeout was set to 60 secs, that was more then > > > enough just one day before the upgrade. > ... > > > Since I upgraded the Machines zpool to version 13 already I don't > > > really wanna go back to 7.0, but it seems the only way out atm. > > > > > > Hopefully someone can give me a Hint where maybe I forgot to > > > check. > > > > > > Somehow it feels like the last Versions, I'd say starting with 7.x > > > doesn't really feel that Rock-Stable as Versions Prior used to > > > be. Prolly cause I'm using an Experimental Feature like ZFS, so no > > > Offense nor Blame and this is not intended as a Flame or > > > whatsoever! So don't get me wrong, I always liked, used, > > > recommended FreeBSD since 4.0 and will continue to do so! > > > > > > Best Regards > > > > > > > I've tested some more it seems the Bottleneck is the HD, Raid Array > > is Optimal checked it. > > Probably you already checked this, but did you go through the dmesg > output relating to ata and drive detection closely? > > In the past from time to time I've had machines suddenly start > crawling after an upgrade, and it turned out it was because some > change in the driver detection caused the ata to fall back to pio > mode. The symptoms are pretty much like you describe - all HD IO > takes forever. > > -- Clifton > Thanks for that Hint, checked again to be sure, but thats not the Case. mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync ) mpt0:vol0(mpt0:0:0): Using Spare Pool: 0 mpt0:vol0(mpt0:0:0): 2 Members: (mpt0:1:32:0): Primary Online (mpt0:1:1:0): Secondary Online mpt0:vol0(mpt0:0:0): RAID-1 - Optimal mpt0:vol0(mpt0:0:0): Status ( Enabled ) (mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0) (mpt0:vol0:1): Online (mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0) (mpt0:vol0:0): Online acd0: CDROM at ata0-master UDMA33 acd1: CDROM at ata2-slave PIO3 da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing Enabled SdMaP0:: A1P5 1C6P3U4 M#B1 (L3a1u0n5c4h6e4d3!2 512 byte sectors: 255H 63S/T 19330C) -- Tobias Lott From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 20:00:11 2009 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 489111065694; Wed, 9 Sep 2009 20:00:11 +0000 (UTC) (envelope-from tlott@gamesnet.de) Received: from spirit.gamesnet.de (cl-858.dus-01.de.sixxs.net [IPv6:2a01:198:200:359::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0FF628FC12; Wed, 9 Sep 2009 20:00:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by spirit.gamesnet.de (Postfix) with ESMTP id EA1E0304469; Wed, 9 Sep 2009 22:00:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at gamesnet.de Received: from spirit.gamesnet.de ([127.0.0.1]) by localhost (spirit.gamesnet.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g99aQ5CYov6x; Wed, 9 Sep 2009 22:00:01 +0200 (CEST) Received: from sub.han.vpn.gamesnet.de (sub.han.vpn.gamesnet.de [192.168.1.101]) by spirit.gamesnet.de (Postfix) with ESMTPSA id 3765A304457; Wed, 9 Sep 2009 22:00:01 +0200 (CEST) Date: Wed, 9 Sep 2009 21:59:59 +0200 From: Tobias Lott To: freebsd-stable@freebsd.org, freebsd-performance@freebsd.org Message-ID: <20090909215959.6b5152f2@sub.han.vpn.gamesnet.de> In-Reply-To: <20090909213022.34d64e47@sub.han.vpn.gamesnet.de> References: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> <20090909104807.633418ea@sub.han.vpn.gamesnet.de> <20090909170213.GA7925@lava.net> <20090909213022.34d64e47@sub.han.vpn.gamesnet.de> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd7.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: System crawls after Upgrade 7.0->7.2 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, 09 Sep 2009 20:00:11 -0000 On Wed, 9 Sep 2009 21:30:22 +0200 Tobias Lott wrote: > > > On Wed, 9 Sep 2009 07:02:13 -1000 > Clifton Royston wrote: > > > On Wed, Sep 09, 2009 at 10:48:07AM +0200, Tobias Lott wrote: > > > On Tue, 8 Sep 2009 12:19:45 +0200 > > > Tobias Lott wrote: > > > > Hey Everyone, > > > > > > > > I upgraded a Dual Core Machine to 7.2-Stable (2 Days ago), all > > > > OS related Stuff is located on an UFS Slice, Application is on > > > > a ZFS Volume. > > > > > > > > After the Upgrade everything seemed fine, but a User noticed one > > > > PHP Script which is basically loading a plain Textfile into > > > > Mysql times out. PHP Timeout was set to 60 secs, that was more > > > > then enough just one day before the upgrade. > > ... > > > > Since I upgraded the Machines zpool to version 13 already I > > > > don't really wanna go back to 7.0, but it seems the only way > > > > out atm. > > > > > > > > Hopefully someone can give me a Hint where maybe I forgot to > > > > check. > > > > > > > > Somehow it feels like the last Versions, I'd say starting with > > > > 7.x doesn't really feel that Rock-Stable as Versions Prior used > > > > to be. Prolly cause I'm using an Experimental Feature like ZFS, > > > > so no Offense nor Blame and this is not intended as a Flame or > > > > whatsoever! So don't get me wrong, I always liked, used, > > > > recommended FreeBSD since 4.0 and will continue to do so! > > > > > > > > Best Regards > > > > > > > > > > I've tested some more it seems the Bottleneck is the HD, Raid > > > Array is Optimal checked it. > > > > Probably you already checked this, but did you go through the > > dmesg output relating to ata and drive detection closely? > > > > In the past from time to time I've had machines suddenly start > > crawling after an upgrade, and it turned out it was because some > > change in the driver detection caused the ata to fall back to pio > > mode. The symptoms are pretty much like you describe - all HD IO > > takes forever. > > > > -- Clifton > > > > Thanks for that Hint, checked again to be sure, but thats not the > Case. > > mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority-ReSync ) > mpt0:vol0(mpt0:0:0): Using Spare Pool: 0 > mpt0:vol0(mpt0:0:0): 2 Members: > (mpt0:1:32:0): Primary Online > (mpt0:1:1:0): Secondary Online > mpt0:vol0(mpt0:0:0): RAID-1 - Optimal > mpt0:vol0(mpt0:0:0): Status ( Enabled ) > (mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0) > (mpt0:vol0:1): Online > (mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0) > (mpt0:vol0:0): Online > acd0: CDROM at ata0-master UDMA33 > acd1: CDROM at ata2-slave PIO3 > da0 at mpt0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-5 device > da0: 300.000MB/s transfers > da0: Command Queueing Enabled > SdMaP0:: A1P5 1C6P3U4 M#B1 (L3a1u0n5c4h6e4d3!2 > 512 byte sectors: 255H 63S/T 19330C) > > Oh well just did some more research and found: http://www.mail-archive.com/freebsd-performance@freebsd.org/msg02461.html Gonna try it out later and gonna give a Report. -- Tobias Lott From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 20:26:18 2009 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 C879D106566C; Wed, 9 Sep 2009 20:26:18 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 8B13C8FC08; Wed, 9 Sep 2009 20:26:18 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 1DC8373110; Wed, 9 Sep 2009 22:32:16 +0200 (CEST) Date: Wed, 9 Sep 2009 22:32:16 +0200 From: Luigi Rizzo To: John Baldwin Message-ID: <20090909203216.GA93761@onelab2.iet.unipi.it> References: <20090906155154.GA8283@onelab2.iet.unipi.it> <200909081308.23345.jhb@freebsd.org> <20090908210100.GA72735@onelab2.iet.unipi.it> <200909091324.53668.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909091324.53668.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 09 Sep 2009 20:26:18 -0000 On Wed, Sep 09, 2009 at 01:24:53PM -0400, John Baldwin wrote: > On Tuesday 08 September 2009 5:01:00 pm Luigi Rizzo wrote: > > On Tue, Sep 08, 2009 at 01:08:23PM -0400, John Baldwin wrote: > > > On Sunday 06 September 2009 11:51:54 am Luigi Rizzo wrote: > > > > [Note 3] the TSC frequency is computed reading the tsc around a > > > > call to DELAY(1000000) and assuming that the i8254 runs > > > > at the nominal rate, 1.193182 MHz. > > > > From tests I have made, the measurement in init_TSC() returns > > > > a large error when HZ is large, whereas repeating the > measurement > > > > at a later time returns a much more reliable value. ... > > > Try disabling legacy USB support in the BIOS to see if an SMI# is firing > > > during the DELAY() causing the TSC freq to be too high. I have seen the > USB > > > legacy support cause this in other machines. > > > > Thanks, will try tomorrow. > > Would this explain the measurement becomes better as we get > > further into the initialization, and why high HZ values affect > > the measurement ? > > It would explain why it gets better later since the uhci(4), ohci(4) and > ehci(4) drivers disable the SMI# interrupts while attaching to the > controllers. ok makes sense -- if the SMI interrupts last longer than 1/HZ they will cause us to miss one or more wraps of the i8254 in $ARCH/isa/clock.c::DELAY(). I suppose with a few measurements at different HZ values and some back of the envelope calculations one could even determine estimate the frequency and duration of those SMI interrupts! thanks luigi From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 20:29:26 2009 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 6C1D51065701 for ; Wed, 9 Sep 2009 20:29:26 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id E9A178FC21 for ; Wed, 9 Sep 2009 20:29:25 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n89KTmdY045446; Wed, 9 Sep 2009 15:29:48 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n89KTmlA045445; Wed, 9 Sep 2009 15:29:48 -0500 (CDT) (envelope-from brooks) Date: Wed, 9 Sep 2009 15:29:48 -0500 From: Brooks Davis To: Pyun YongHyeon , freebsd-stable Message-ID: <20090909202948.GG42196@lor.one-eyed-alien.net> References: <20090904173811.GA45176@graf.pompo.net> <20090904214148.GB9950@michelle.cdnetworks.com> <20090904215747.GB82231@lor.one-eyed-alien.net> <20090905110635.GG87716@graf.pompo.net> <20090909155257.GF42196@lor.one-eyed-alien.net> <20090909170701.GB38292@graf.pompo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090909170701.GB38292@graf.pompo.net> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Wed, 09 Sep 2009 15:29:49 -0500 (CDT) Cc: Subject: Re: ifconfig_ed0="DHCP" does not work on 8.0-BETA3 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, 09 Sep 2009 20:29:26 -0000 On Wed, Sep 09, 2009 at 07:07:01PM +0200, Thierry Thomas wrote: > Le Mer 9 sep 09 ? 17:52:57 +0200, Brooks Davis > ?crivait?: > > > I'd rather not mention the "link state changed" message since I'd love > > to see it go away. How's this? > > Seems good, go! Thanks. I've committed it. Brooks From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 20:42:13 2009 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 A2916106568B for ; Wed, 9 Sep 2009 20:42:13 +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 73B4A8FC18 for ; Wed, 9 Sep 2009 20:42:13 +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 109FB46B38; Wed, 9 Sep 2009 16:42:13 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 49E698A01B; Wed, 9 Sep 2009 16:42:12 -0400 (EDT) From: John Baldwin To: Luigi Rizzo Date: Wed, 9 Sep 2009 16:42:05 -0400 User-Agent: KMail/1.9.7 References: <20090906155154.GA8283@onelab2.iet.unipi.it> <200909091324.53668.jhb@freebsd.org> <20090909203216.GA93761@onelab2.iet.unipi.it> In-Reply-To: <20090909203216.GA93761@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909091642.06046.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 09 Sep 2009 16:42:12 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-stable@freebsd.org Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 09 Sep 2009 20:42:13 -0000 On Wednesday 09 September 2009 4:32:16 pm Luigi Rizzo wrote: > On Wed, Sep 09, 2009 at 01:24:53PM -0400, John Baldwin wrote: > > On Tuesday 08 September 2009 5:01:00 pm Luigi Rizzo wrote: > > > On Tue, Sep 08, 2009 at 01:08:23PM -0400, John Baldwin wrote: > > > > On Sunday 06 September 2009 11:51:54 am Luigi Rizzo wrote: > > > > > [Note 3] the TSC frequency is computed reading the tsc around a > > > > > call to DELAY(1000000) and assuming that the i8254 runs > > > > > at the nominal rate, 1.193182 MHz. > > > > > From tests I have made, the measurement in init_TSC() returns > > > > > a large error when HZ is large, whereas repeating the > > measurement > > > > > at a later time returns a much more reliable value. > ... > > > > Try disabling legacy USB support in the BIOS to see if an SMI# is firing > > > > during the DELAY() causing the TSC freq to be too high. I have seen the > > USB > > > > legacy support cause this in other machines. > > > > > > Thanks, will try tomorrow. > > > Would this explain the measurement becomes better as we get > > > further into the initialization, and why high HZ values affect > > > the measurement ? > > > > It would explain why it gets better later since the uhci(4), ohci(4) and > > ehci(4) drivers disable the SMI# interrupts while attaching to the > > controllers. > > ok makes sense -- if the SMI interrupts last longer than 1/HZ > they will cause us to miss one or more wraps of the i8254 in > $ARCH/isa/clock.c::DELAY(). I suppose with a few measurements > at different HZ values and some back of the envelope calculations > one could even determine estimate the frequency and duration > of those SMI interrupts! On recent motherboards I have seen the SMI# interrupt fire every 250 ms with execution times ranging from 50 us to 1ms for the legacy USB interrupt handler. We consistently see the TSC frequency miscalculated on the motherboards with the 1ms duration interrupt. I suspect that the clock that drives the periodic SMI# interrupt is tied to the i8254 meaning that it often fires at the same time that the i8254 wraps causing the TSC frequency to often be wrong. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 20:44:34 2009 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 94E091065676 for ; Wed, 9 Sep 2009 20:44:34 +0000 (UTC) (envelope-from njm@njm.me.uk) Received: from smtp003.apm-internet.net (smtp003.apm-internet.net [85.119.248.52]) by mx1.freebsd.org (Postfix) with SMTP id 03AAF8FC1D for ; Wed, 9 Sep 2009 20:44:33 +0000 (UTC) Received: (qmail 65900 invoked from network); 9 Sep 2009 20:44:32 -0000 Received: from unknown (HELO titania.njm.me.uk) (86.141.186.210) by smtp003.apm-internet.net with SMTP; 9 Sep 2009 20:44:32 -0000 Received: from titania.njm.me.uk (localhost [127.0.0.1]) by titania.njm.me.uk (8.14.3/8.14.3) with ESMTP id n89KiWJZ092554; Wed, 9 Sep 2009 21:44:32 +0100 (BST) (envelope-from njm@njm.me.uk) Received: (from njm@localhost) by titania.njm.me.uk (8.14.3/8.14.3/Submit) id n89KiV07092553; Wed, 9 Sep 2009 21:44:31 +0100 (BST) (envelope-from njm@njm.me.uk) Date: Wed, 9 Sep 2009 21:44:31 +0100 From: "N.J. Mann" To: Michael Sperber Message-ID: <20090909204431.GB88622@titania.njm.me.uk> Mail-Followup-To: Michael Sperber , Robert Watson , Mikael Bak , freebsd-stable@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz> References: <4A8EAE86.2000108@t-online.hu> <4A8ECB9C.2020909@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 7.2-STABLE User-Agent: mutt-NJM (2009-07-16) Cc: Mikael Bak , freebsd-stable@FreeBSD.org, Robert Watson , Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: Upgrade FreeBSD 7.1 to 7.2 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, 09 Sep 2009 20:44:34 -0000 In message , Michael Sperber (sperber@deinprogramm.de) wrote: > > Robert Watson writes: > > > FWIW, the main problem I ran into with my 8.0 upgrade is that 8.0 uses > > the uart(4) driver for serial ports, and sio(4), 7.2's default, has > > been removed. They require mutually exclusive lines in device.hints > > and different /etc/ttys lines. If you rely on a serial console, I > > would recommend first switching 7.2 to using uart, pausing for a bit, > > and then switching forward to 8 so that you separate the risks > > associated with changing console drivers from those associated with > > sliding a major kernel version. > > Could you briefly elaborate on how that's done with 7.x? I.e. is > changing device.hints and /etc/ttys enough (what changes?), or do I need > to recompile the kernel? (I'm a bit confused because both uart and sio > seem to be in GENERIC, but I haven't been able to active uart through > device.hints. I couldn't find anything on freebsd.org or the internets, > either.) A few hints would be much appreciated! Robert's comment prompted me to try this on my home server which runs 7-STABLE, but which I will probably upgrade to 8-STABLE in a few months time. What I did was: 1. Replace 'device sio' with 'device uart' in the kernel configuration file. 2. In /etc/ttys change all ttydX to ttyuX, where X was 0 to 3 in my case. 3. In /boot/device.hints change all hint.sio.X.Y to hint.uart.X.Y I then rebooted with my fingers crossed since said machine is headless. I need not have worried since it worked first time. If anyone thinks I forgot something please _do_ speak up. HTH Cheers, Nick. -- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 20:57:57 2009 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 5D4961065672 for ; Wed, 9 Sep 2009 20:57:57 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from fallbackmx07.syd.optusnet.com.au (fallbackmx07.syd.optusnet.com.au [211.29.132.9]) by mx1.freebsd.org (Postfix) with ESMTP id 771848FC08 for ; Wed, 9 Sep 2009 20:57:56 +0000 (UTC) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by fallbackmx07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n89JXn7v011143 for ; Thu, 10 Sep 2009 05:33:49 +1000 Received: from server.vk2pj.dyndns.org (c122-106-217-45.belrs3.nsw.optusnet.com.au [122.106.217.45]) by mail15.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n89JXkjg031138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 05:33:47 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n89JXkSY061400; Thu, 10 Sep 2009 05:33:46 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n89JXjlr061399; Thu, 10 Sep 2009 05:33:45 +1000 (EST) (envelope-from peter) Date: Thu, 10 Sep 2009 05:33:45 +1000 From: Peter Jeremy To: =?iso-8859-1?Q?V=E1clav?= Haisman Message-ID: <20090909193345.GA55347@server.vk2pj.dyndns.org> References: <4A9D561F.5000808@sh.cvut.cz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <4A9D561F.5000808@sh.cvut.cz> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: GCC -m32 option on FreeBSD/AMD64 7.2 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, 09 Sep 2009 20:57:57 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Sep-01 19:13:03 +0200, V=E1clav Haisman wrot= e: >is C++ + GCC -m32 option officially supported by FreeBSD/AMD64 7.2? The short answer is "no" - though this is a common request and there are some PRs open for it. At present, the only supported way to build i386 code on amd64 is by installing an i386 world and compiling in either a jail or chroot. Basically, whilst '-m32' correctly generates 32-bit code, virtually all programs wind up (indirectly) #include'ing files from /usr/include/machine and this directory assumes the native machine definitions - in the case of amd64, longs and pointers are 64-bits. Whilst it's not immediately obvious what happened here, I am confident this is the underlying cause. --=20 Peter Jeremy --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqoAxkACgkQ/opHv/APuIf78ACfcqfmVlgpkjFNe9UGbJM5fXVP AuUAn0KFZe2OSwOCGYgSVRQNQctF/YR2 =ncBT -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 21:05:26 2009 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 0A1B3106566B; Wed, 9 Sep 2009 21:05:26 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id BF9098FC12; Wed, 9 Sep 2009 21:05:25 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 9B814730DA; Wed, 9 Sep 2009 23:11:23 +0200 (CEST) Date: Wed, 9 Sep 2009 23:11:23 +0200 From: Luigi Rizzo To: John Baldwin Message-ID: <20090909211123.GD93761@onelab2.iet.unipi.it> References: <20090906155154.GA8283@onelab2.iet.unipi.it> <200909091324.53668.jhb@freebsd.org> <20090909203216.GA93761@onelab2.iet.unipi.it> <200909091642.06046.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909091642.06046.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 09 Sep 2009 21:05:26 -0000 On Wed, Sep 09, 2009 at 04:42:05PM -0400, John Baldwin wrote: ... > > > It would explain why it gets better later since the uhci(4), ohci(4) and > > > ehci(4) drivers disable the SMI# interrupts while attaching to the > > > controllers. > > > > ok makes sense -- if the SMI interrupts last longer than 1/HZ > > they will cause us to miss one or more wraps of the i8254 in > > $ARCH/isa/clock.c::DELAY(). I suppose with a few measurements > > at different HZ values and some back of the envelope calculations > > one could even determine estimate the frequency and duration > > of those SMI interrupts! > > On recent motherboards I have seen the SMI# interrupt fire every 250 ms with > execution times ranging from 50 us to 1ms for the legacy USB interrupt > handler. We consistently see the TSC frequency miscalculated on the > motherboards with the 1ms duration interrupt. I suspect that the clock that > drives the periodic SMI# interrupt is tied to the i8254 meaning that it often > fires at the same time that the i8254 wraps causing the TSC frequency to > often be wrong. when or even how often it fires should not matter much -- as long as the interrupt is shorter than 1 tick we will be able to see the wrap and handle it correctly. I'll try to write a 1-sec loop around rdtsc() and log large differences in the reads to figure out whether i am getting some long interrupts. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 22:12:35 2009 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 0E0091065692; Wed, 9 Sep 2009 22:12:35 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8BC7F8FC0C; Wed, 9 Sep 2009 22:12:34 +0000 (UTC) Received: from vhoffman-macbook.local ([10.0.0.173]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.3) with ESMTP id n89MFjoQ029794 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2009 23:15:45 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4AA82851.7060306@unsane.co.uk> Date: Wed, 09 Sep 2009 23:12:33 +0100 From: Vincent Hoffman User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: John Baldwin References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> <200909091446.47077.jhb@freebsd.org> In-Reply-To: <200909091446.47077.jhb@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: general protection fault on 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, 09 Sep 2009 22:12:35 -0000 John Baldwin wrote: > On Wednesday 09 September 2009 1:38:59 pm John Baldwin wrote: > >> On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: >> >>> Hi all, >>> I've been running the 8.0-BETAs in a xen virtual machine >>> (hvm/fully virtualised) for testing and something between r196730 and >>> r196746 causes a general protection fault on boot. I'll try and narrow >>> it down if i get a chance but I'm a a bit busy at the moment. >>> >>> backtrace is available at >>> http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif >>> Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from >>> http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. >>> >>> Let me know if I need to provide any more info. >>> >> Hmm, can you try reverting 196737? Or actually, can you print out the value >> of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch would >> fix it: >> >> Index: pmap.c >> =================================================================== >> --- pmap.c (revision 196974) >> +++ pmap.c (working copy) >> @@ -999,7 +999,7 @@ >> * coherence domain. >> */ >> mfence(); >> - for (; sva < eva; sva += cpu_clflush_line_size) >> + for (; sva <= eva; sva += cpu_clflush_line_size) >> clflush(sva); >> mfence(); >> } else { >> > > This patch is probably bogus. I am curious what %ebx is however. > > p $ebx gives c25a7000 Vince From owner-freebsd-stable@FreeBSD.ORG Wed Sep 9 22:13:30 2009 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 4C6F41065670; Wed, 9 Sep 2009 22:13:30 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id AD5ED8FC1D; Wed, 9 Sep 2009 22:13:29 +0000 (UTC) Received: from vhoffman-macbook.local ([10.0.0.173]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.3) with ESMTP id n89MGeE0029809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Sep 2009 23:16:41 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4AA82888.2080707@unsane.co.uk> Date: Wed, 09 Sep 2009 23:13:28 +0100 From: Vincent Hoffman User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Kostik Belousov References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> <20090909190228.GC47688@deviant.kiev.zoral.com.ua> In-Reply-To: <20090909190228.GC47688@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: general protection fault on 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, 09 Sep 2009 22:13:30 -0000 Kostik Belousov wrote: > On Wed, Sep 09, 2009 at 01:38:59PM -0400, John Baldwin wrote: > >> On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: >> >>> Hi all, >>> I've been running the 8.0-BETAs in a xen virtual machine >>> (hvm/fully virtualised) for testing and something between r196730 and >>> r196746 causes a general protection fault on boot. I'll try and narrow >>> it down if i get a chance but I'm a a bit busy at the moment. >>> >>> backtrace is available at >>> http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif >>> Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from >>> http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. >>> >>> Let me know if I need to provide any more info. >>> >> Hmm, can you try reverting 196737? Or actually, can you print out the value >> of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch would >> fix it: >> >> Index: pmap.c >> =================================================================== >> --- pmap.c (revision 196974) >> +++ pmap.c (working copy) >> @@ -999,7 +999,7 @@ >> * coherence domain. >> */ >> mfence(); >> - for (; sva < eva; sva += cpu_clflush_line_size) >> + for (; sva <= eva; sva += cpu_clflush_line_size) >> clflush(sva); >> mfence(); >> } else { >> > > Oh, no, another pointy hat to me :(. > > Please, try this patch instead. > > diff --git a/sys/i386/xen/pmap.c b/sys/i386/xen/pmap.c > index 4b81aae..122318c 100644 > --- a/sys/i386/xen/pmap.c > +++ b/sys/i386/xen/pmap.c > @@ -1004,8 +1004,8 @@ pmap_invalidate_cache_range(vm_offset_t sva, vm_offset_t eva) > * coherence domain. > */ > mfence(); > - for (; eva < sva; eva += cpu_clflush_line_size) > - clflush(eva); > + for (; sva < eva; sva += cpu_clflush_line_size) > + clflush(sva); > mfence(); > } else { > > Ok will try this tomorrow. Vince From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 02:41:06 2009 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 E4B831065676; Thu, 10 Sep 2009 02:41:06 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3C83E8FC08; Thu, 10 Sep 2009 02:41:05 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n8A2f4UX067649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 12:11:04 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Robert Noland Date: Thu, 10 Sep 2009 12:10:59 +0930 User-Agent: KMail/1.9.10 References: <1252426982.00160755.1252414203@10.7.7.3> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> In-Reply-To: <1252501703.85394.3473.camel@balrog.2hip.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1407885.oH7L6S3sN3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909101211.01534.doconnor@gsoft.com.au> X-Spam-Score: -3.611 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Alexander Motin , FreeBSD Stable Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 02:41:07 -0000 --nextPart1407885.oH7L6S3sN3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Robert Noland wrote: > > I am pretty sure it would be throttling but I think that works by > > maintaining the frequency but stalling the CPU some percentage of > > the time. I have p4tcc loaded (in GENERIC) but it doesn't show up, > > I only get.. > > Is this a core2duo? IIRC, they generally don't go into TCC until > around 100C. I did pull the c2d cpu docs at one point trying to look > at cpufreq. If you are bored, you can grab the docs from intel and > double check. Hmm, I only managed to get it to 75C or so.. Unfortunately the remote system which was exhibiting the problem has=20 been fixed and the onsite guy doesn't have time to pull it out and=20 break it again :( The coretemp source suggests that there are 2 max junction temperatures=20 for Core2Duos - 85C & 100C. However I just realised the "faulty" system has an E2140 in it which has=20 a 65W TDP, whereas the bench system has an E7500 with a TDP of 35W - I=20 guess that could explain the difference. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1407885.oH7L6S3sN3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKqGc95ZPcIHs/zowRAkcXAJ4rSsodJlqgMNH7tkmYiU9hvDxS9wCgi7N7 n4EJZQsP6hoXti6TexQkwj0= =Volh -----END PGP SIGNATURE----- --nextPart1407885.oH7L6S3sN3-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 02:48:10 2009 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 A91EC106568B; Thu, 10 Sep 2009 02:48:10 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 011148FC0A; Thu, 10 Sep 2009 02:48:09 +0000 (UTC) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n8A2m8G5067785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 12:18:08 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Alexander Motin Date: Thu, 10 Sep 2009 12:18:03 +0930 User-Agent: KMail/1.9.10 References: <1252426982.00160755.1252414203@10.7.7.3> <1252501703.85394.3473.camel@balrog.2hip.net> <4AA7AA9B.9010709@FreeBSD.org> In-Reply-To: <4AA7AA9B.9010709@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart35789273.YECnIvQjDX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909101218.05070.doconnor@gsoft.com.au> X-Spam-Score: -3.611 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: FreeBSD Stable , Robert Noland Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 02:48:10 -0000 --nextPart35789273.YECnIvQjDX Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 9 Sep 2009, Alexander Motin wrote: > > around 100C. I did pull the c2d cpu docs at one point trying to > > look at cpufreq. If you are bored, you can grab the docs from > > intel and double check. > > AFAIR C2D supports three protection technologies. When CPU is hot, it > starts reducing frequency (multiplier) and voltage, alike to IEST. If > it is insufficient, it starts to skip core cycles, alike to TCC. If > it is still insufficient and temperature rises above about 100C, > emergency shutdown happens. Hmm, I have since realised it's an E2140 which doesn't have Core2Duo=20 branding (I don't know if it really IS one or not). On the bench here I could not observe an effect by running=20 dd if=3D/dev/zero bs=3D128k count=3D5000| md5 in a loop and checking the frequency with dev.cpu.0.freq However the idle time seemed to go up, but only to 10% or so, it was=20 quite odd.. Still, now I have been reminded of coretemp I can monitor it=20 on "suspect" systems :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart35789273.YECnIvQjDX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKqGjl5ZPcIHs/zowRArbWAJ9EYE3AtaH+QDh3nivHF4KP2LdDfQCdHFvV p7ZqB+hT5CpdwLktrQqFE78= =Ct6F -----END PGP SIGNATURE----- --nextPart35789273.YECnIvQjDX-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 10:34:26 2009 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 2191B1065670; Thu, 10 Sep 2009 10:34:26 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8DF9D8FC17; Thu, 10 Sep 2009 10:34:25 +0000 (UTC) Received: from vhoffman.lon.namesco.net (115.73-246-213.ippool.namesco.net [213.246.73.115]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.3) with ESMTP id n8AAbYJK041868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 11:37:35 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4AA8D62F.1020901@unsane.co.uk> Date: Thu, 10 Sep 2009 11:34:23 +0100 From: Vincent Hoffman User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Kostik Belousov References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> <20090909190228.GC47688@deviant.kiev.zoral.com.ua> In-Reply-To: <20090909190228.GC47688@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: general protection fault on 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, 10 Sep 2009 10:34:26 -0000 Kostik Belousov wrote: > On Wed, Sep 09, 2009 at 01:38:59PM -0400, John Baldwin wrote: > >> On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: >> >>> Hi all, >>> I've been running the 8.0-BETAs in a xen virtual machine >>> (hvm/fully virtualised) for testing and something between r196730 and >>> r196746 causes a general protection fault on boot. I'll try and narrow >>> it down if i get a chance but I'm a a bit busy at the moment. >>> >>> backtrace is available at >>> http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif >>> Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from >>> http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. >>> >>> Let me know if I need to provide any more info. >>> >> Hmm, can you try reverting 196737? Or actually, can you print out the value >> of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch would >> fix it: >> >> Index: pmap.c >> =================================================================== >> --- pmap.c (revision 196974) >> +++ pmap.c (working copy) >> @@ -999,7 +999,7 @@ >> * coherence domain. >> */ >> mfence(); >> - for (; sva < eva; sva += cpu_clflush_line_size) >> + for (; sva <= eva; sva += cpu_clflush_line_size) >> clflush(sva); >> mfence(); >> } else { >> > > Oh, no, another pointy hat to me :(. > > Please, try this patch instead. > > diff --git a/sys/i386/xen/pmap.c b/sys/i386/xen/pmap.c > index 4b81aae..122318c 100644 > --- a/sys/i386/xen/pmap.c > +++ b/sys/i386/xen/pmap.c > @@ -1004,8 +1004,8 @@ pmap_invalidate_cache_range(vm_offset_t sva, vm_offset_t eva) > * coherence domain. > */ > mfence(); > - for (; eva < sva; eva += cpu_clflush_line_size) > - clflush(eva); > + for (; sva < eva; sva += cpu_clflush_line_size) > + clflush(sva); > mfence(); > } else { > > Hi, I tried this this morning with no joy i'm afraid. not much change but new backtrace (with p $ebx) at http://www.unsane.co.uk/~jhary/freebsd/10-09-09.gif Just to check I'm not in need of more coffee as i'm still learning svn (and my coding skills such as they are lie in shell and perl) krill# svn info Path: . URL: svn://svn.freebsd.org/base/stable/8 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 196740 Node Kind: directory Schedule: normal Last Changed Author: rnoland Last Changed Rev: 196737 Last Changed Date: 2009-09-01 17:41:28 +0100 (Tue, 01 Sep 2009) krill# sed -n '1010,1017p' sys/i386/xen/pmap.c * coherence domain. */ mfence(); for (; sva < eva; sva += cpu_clflush_line_size) clflush(sva); mfence(); } else { krill# Happy to give vnc access to the console of the machine if that would help. Vince From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 11:28:58 2009 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 317D0106566B; Thu, 10 Sep 2009 11:28:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 620618FC20; Thu, 10 Sep 2009 11:28:56 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n8ABSoS4001348 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 14:28:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n8ABSotr077784; Thu, 10 Sep 2009 14:28:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n8ABSoN6077783; Thu, 10 Sep 2009 14:28:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 10 Sep 2009 14:28:50 +0300 From: Kostik Belousov To: Vincent Hoffman Message-ID: <20090910112850.GG47688@deviant.kiev.zoral.com.ua> References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> <20090909190228.GC47688@deviant.kiev.zoral.com.ua> <4AA8D62F.1020901@unsane.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YOUJ+9SC2P4ELYXZ" Content-Disposition: inline In-Reply-To: <4AA8D62F.1020901@unsane.co.uk> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: general protection fault on 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, 10 Sep 2009 11:28:58 -0000 --YOUJ+9SC2P4ELYXZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 10, 2009 at 11:34:23AM +0100, Vincent Hoffman wrote: > Kostik Belousov wrote: > > On Wed, Sep 09, 2009 at 01:38:59PM -0400, John Baldwin wrote: > > =20 > >> On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: > >> =20 > >>> Hi all, > >>> I've been running the 8.0-BETAs in a xen virtual machine > >>> (hvm/fully virtualised) for testing and something between r196730 and > >>> r196746 causes a general protection fault on boot. I'll try and narrow > >>> it down if i get a chance but I'm a a bit busy at the moment. > >>> =20 > >>> backtrace is available at > >>> http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif=20 > >>> Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from > >>> http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. > >>> > >>> Let me know if I need to provide any more info. > >>> =20 > >> Hmm, can you try reverting 196737? Or actually, can you print out the= value=20 > >> of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch w= ould=20 > >> fix it: > >> > >> Index: pmap.c > >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> --- pmap.c (revision 196974) > >> +++ pmap.c (working copy) > >> @@ -999,7 +999,7 @@ > >> * coherence domain. > >> */ > >> mfence(); > >> - for (; sva < eva; sva +=3D cpu_clflush_line_size) > >> + for (; sva <=3D eva; sva +=3D cpu_clflush_line_size) > >> clflush(sva); > >> mfence(); > >> } else { > >> =20 > > > > Oh, no, another pointy hat to me :(. > > > > Please, try this patch instead. > > > > diff --git a/sys/i386/xen/pmap.c b/sys/i386/xen/pmap.c > > index 4b81aae..122318c 100644 > > --- a/sys/i386/xen/pmap.c > > +++ b/sys/i386/xen/pmap.c > > @@ -1004,8 +1004,8 @@ pmap_invalidate_cache_range(vm_offset_t sva, vm_o= ffset_t eva) > > * coherence domain. > > */ > > mfence(); > > - for (; eva < sva; eva +=3D cpu_clflush_line_size) > > - clflush(eva); > > + for (; sva < eva; sva +=3D cpu_clflush_line_size) > > + clflush(sva); > > mfence(); > > } else { > > =20 > > =20 > Hi, > I tried this this morning with no joy i'm afraid. > not much change but new backtrace (with p $ebx) at > http://www.unsane.co.uk/~jhary/freebsd/10-09-09.gif I would need the panic message and ddb lines that are not present on your screenshot. Also, the dmesg is interesting (CPU features report). >=20 > Just to check I'm not in need of more coffee as i'm still learning svn > (and my coding skills such as they are lie in shell and perl) >=20 > krill# svn info > Path: . > URL: svn://svn.freebsd.org/base/stable/8 > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 196740 > Node Kind: directory > Schedule: normal > Last Changed Author: rnoland > Last Changed Rev: 196737 > Last Changed Date: 2009-09-01 17:41:28 +0100 (Tue, 01 Sep 2009) >=20 >=20 > krill# sed -n '1010,1017p' sys/i386/xen/pmap.c > * coherence domain. > */ > mfence(); > for (; sva < eva; sva +=3D cpu_clflush_line_size) > clflush(sva); > mfence(); > } else { >=20 > krill# >=20 > Happy to give vnc access to the console of the machine if that would help. >=20 > Vince --YOUJ+9SC2P4ELYXZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkqo4vIACgkQC3+MBN1Mb4iXfACfWtwupfpz27jM1HtX5SL/2Bp2 qSwAoPNLTaZXG9ftOou39sV4uhMpGB7s =rFA/ -----END PGP SIGNATURE----- --YOUJ+9SC2P4ELYXZ-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 12:04:51 2009 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 48FFD106568D for ; Thu, 10 Sep 2009 12:04:51 +0000 (UTC) (envelope-from sagara@tomahawk.com.sg) Received: from us1.tomahawkonline.net (us1.tomahawkonline.net [66.98.178.56]) by mx1.freebsd.org (Postfix) with SMTP id ED11F8FC18 for ; Thu, 10 Sep 2009 12:04:50 +0000 (UTC) Received: (qmail 8729 invoked from network); 10 Sep 2009 08:44:15 -0000 Received: from 219.74.242.111 (HELO tdsblack.lan) (sagara@tomahawk.com.sg@219.74.242.111) by us1.tomahawkonline.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 10 Sep 2009 08:44:15 -0000 Message-ID: <4AA8EBBD.5020709@tomahawk.com.sg> Date: Thu, 10 Sep 2009 20:06:21 +0800 From: Sagara Wijetunga User-Agent: Thunderbird 2.0.0.22 (X11/20090703) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Avahi compilation help needed 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, 10 Sep 2009 12:04:51 -0000 Dear FreeBSD community I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2 (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors. Is it possible someone to help us by compile Avahi and identify the compilations issues and propose relevant fixes. We use "./configure, gmake, gmake install" method. For an example, first compilation issue faced was does not get included because -D_XOPEN_SOURCE=500 in the configure script. We use D-Bus and Qt4 but do not use Mono. It may be doesn't matter to build on Qt3. Please help us to get Avahi compile cleanly. We can install and see whether it works or not. Many thanks in advance. Kind regards Sagara From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 12:08:45 2009 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 E8759106566C for ; Thu, 10 Sep 2009 12:08:45 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id AC1038FC12 for ; Thu, 10 Sep 2009 12:08:45 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:a495:f7c6:da21:cbdb] (unknown [IPv6:2001:7b8:3a7:0:a495:f7c6:da21:cbdb]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 729335C43; Thu, 10 Sep 2009 14:08:44 +0200 (CEST) Message-ID: <4AA8EC4D.3080800@andric.com> Date: Thu, 10 Sep 2009 14:08:45 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.4pre) Gecko/20090904 Shredder/3.0b4pre MIME-Version: 1.0 To: Sagara Wijetunga References: <4AA8EBBD.5020709@tomahawk.com.sg> In-Reply-To: <4AA8EBBD.5020709@tomahawk.com.sg> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Avahi compilation help needed 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, 10 Sep 2009 12:08:46 -0000 On 2009-09-10 14:06, Sagara Wijetunga wrote: > I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2 > (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors. Any reason why you don't use the net/avahi port instead? This will save you most compilation and installation headaches. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 12:43:49 2009 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 655CC106566B for ; Thu, 10 Sep 2009 12:43:49 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id CDEC08FC1D for ; Thu, 10 Sep 2009 12:43:48 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-198-223.lns10.adl2.internode.on.net [121.45.198.223]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n8AChd3x086353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 22:13:39 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 10 Sep 2009 22:13:28 +0930 User-Agent: KMail/1.9.10 References: <1252426982.00160755.1252414203@10.7.7.3> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> In-Reply-To: <20090909153851.GE48206@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2006232.WkdVK9bmvu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909102213.36510.doconnor@gsoft.com.au> X-Spam-Score: -1.595 () AWL,BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Kurt Jaeger Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 12:43:49 -0000 --nextPart2006232.WkdVK9bmvu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 10 Sep 2009, Kurt Jaeger wrote: > Any information on what can be done with AMD CPUs with respect > to temperature monitoring ? I thought coretemp had be modified in HEAD to support Phenoms but I=20 can't find any evidence of that in SVN so I am not sure what I am=20 thinking.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2006232.WkdVK9bmvu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKqPR45ZPcIHs/zowRAtS3AJ9qCsrogngazEtM0TbszeGr7GxjlQCdHPP9 2LzS45l0XB1BGvx/k+e76/Q= =egoM -----END PGP SIGNATURE----- --nextPart2006232.WkdVK9bmvu-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 12:47:15 2009 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 A421B106566C for ; Thu, 10 Sep 2009 12:47:15 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id 5D7BA8FC1B for ; Thu, 10 Sep 2009 12:47:15 +0000 (UTC) Received: from c83-255-48-78.bredband.comhem.se ([83.255.48.78]:51843 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1Mlj3M-0004Mo-9G for freebsd-stable@freebsd.org; Thu, 10 Sep 2009 14:47:10 +0200 Received: (qmail 93691 invoked from network); 10 Sep 2009 14:47:05 +0200 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 10 Sep 2009 14:47:05 +0200 Received: (qmail 93899 invoked by uid 1001); 10 Sep 2009 14:47:05 +0200 Date: Thu, 10 Sep 2009 14:47:05 +0200 From: Erik Trulsson To: Daniel O'Connor Message-ID: <20090910124705.GA93885@owl.midgard.homeip.net> References: <1252426982.00160755.1252414203@10.7.7.3> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> <200909102213.36510.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909102213.36510.doconnor@gsoft.com.au> User-Agent: Mutt/1.5.20 (2009-06-14) X-Originating-IP: 83.255.48.78 X-Scan-Result: No virus found in message 1Mlj3M-0004Mo-9G. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1Mlj3M-0004Mo-9G aed6c5e98f6319845ee5f5c4fdf698fe Cc: Kurt Jaeger , freebsd-stable@freebsd.org Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 12:47:15 -0000 On Thu, Sep 10, 2009 at 10:13:28PM +0930, Daniel O'Connor wrote: > On Thu, 10 Sep 2009, Kurt Jaeger wrote: > > Any information on what can be done with AMD CPUs with respect > > to temperature monitoring ? > > I thought coretemp had be modified in HEAD to support Phenoms but I > can't find any evidence of that in SVN so I am not sure what I am > thinking.. Look for amdtemp or k8temp (which it was named before K10/K11 support was added.) -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 12:48:07 2009 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 E2EC11065724 for ; Thu, 10 Sep 2009 12:48:07 +0000 (UTC) (envelope-from thomas@ronner.org) Received: from mail.knopje.net (mail.knopje.net [213.214.107.232]) by mx1.freebsd.org (Postfix) with ESMTP id A55238FC13 for ; Thu, 10 Sep 2009 12:48:07 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.knopje.net (Postfix) with ESMTP id 2A47038166; Thu, 10 Sep 2009 14:48:06 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at knopje.net Received: from mail.knopje.net ([127.0.0.1]) by localhost (hal.knopje.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B87++7Yi7zJW; Thu, 10 Sep 2009 14:48:05 +0200 (CEST) Received: from [10.0.1.173] (rtutr01.ic-s.nl [213.214.96.4]) by mail.knopje.net (Postfix) with ESMTP id 8930C380E3; Thu, 10 Sep 2009 14:48:05 +0200 (CEST) Message-Id: <94AEB920-0384-4E03-8589-8315F5DC549C@ronner.org> From: Thomas Ronner To: Daniel O'Connor In-Reply-To: <200909102213.36510.doconnor@gsoft.com.au> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 10 Sep 2009 14:48:05 +0200 References: <1252426982.00160755.1252414203@10.7.7.3> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> <200909102213.36510.doconnor@gsoft.com.au> X-Mailer: Apple Mail (2.936) Cc: freebsd-stable@freebsd.org Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 12:48:08 -0000 Hi, On 10 Sep 2009, at 14:43, Daniel O'Connor wrote: > I thought coretemp had be modified in HEAD to support Phenoms but I > can't find any evidence of that in SVN so I am not sure what I am > thinking.. How about 'k8temp'? # make search name=k8temp Port: k8temp-0.4.0 Path: /usr/ports/sysutils/k8temp Info: Athlon 64 and Opteron on-die temperature reader Maint: tom@hur.st B-deps: R-deps: WWW: http://hur.st/k8temp/ # k8temp CPU 0 Core 0 Sensor 0: 35c CPU 0 Core 1 Sensor 0: 36c This is on the amd64 version of FreeBSD 8.0 using an Athlon64 X2 4200+. Thomas From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 12:50:58 2009 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 2E4381065696 for ; Thu, 10 Sep 2009 12:50:58 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3CD498FC1E for ; Thu, 10 Sep 2009 12:50:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 2256F8035 for ; Thu, 10 Sep 2009 14:33:10 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id E229E8034 for ; Thu, 10 Sep 2009 14:33:07 +0200 (CEST) From: Alban Hertroys Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Thu, 10 Sep 2009 14:33:07 +0200 Message-Id: To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Sep 10 14:33:09 2009 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 74,4aa8f20512071992670156 X-DSPAM-Factors: 27, Online=2+Type, 0.40000, 1530457230+Providers, 0.40000, copied+the, 0.40000, 1+OK, 0.40000, 1+OK, 0.40000, but, 0.40000, Received*Sep, 0.40000, I+originally, 0.40000, From*Alban, 0.40000, just, 0.40000, solfertje+student, 0.40000, solfertje+student, 0.40000, usr/obj/usr/src/sys/ERGOPROXY+i386, 0.40000, mount+the, 0.40000, looks, 0.40000, Size(GB)+Cache, 0.40000, Size(GB)+Cache, 0.40000, output+//solfertje>, 0.40000, Mime-Version*Message, 0.40000, seemed, 0.40000, student, 0.40000, student, 0.40000, them+together, 0.40000, 44+CEST, 0.40000, Cache+AVrfy, 0.40000, Cache+AVrfy, 0.40000, Unit, 0.40000 Subject: gconcat file system damage 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, 10 Sep 2009 12:50:58 -0000 Hello, I recently added two disks to the mirror on my 3ware 9550 controller with the intend to expand my mirror. It doesn't support that with differently sized disks though, so I ended up creating a new mirror and gconcat-ed them together. Now I'm seeing lots of UNKNOWN FILETYPE and PARTIAL somethings if fsck verifies the disk, all in subsequent inodes so it looks like fsck gets some offset wrong somewhere. It started with a number of SOFTUPDATE INCONSISTENCY's, which of course went away after disabling softupdates on that FS (it's hardly ever written to anyway). I originally created the concatted disk in two steps. First I created the concat on my new mirrored disks and copied the files from my existing mirror in there. Second I appended the existing mirror to my concatted disk. It seemed to work fine, but now I'm seeing so much errors that I can only mount the concat r/o! Is there anything I can do to fix the issue? World is a stable from just after the 7.2 release, I'm building a fresh one now. Here are a few details: > uname -a FreeBSD solfertje.student.utwente.nl 7.2-STABLE FreeBSD 7.2-STABLE #1: Thu Sep 10 01:34:44 CEST 2009 dalroi@solfertje.student.utwente.nl:/ usr/obj/usr/src/sys/ERGOPROXY i386 > gconcat list Geom name: media State: UP Status: Total=2, Online=2 Type: AUTOMATIC ID: 1530457230 Providers: 1. Name: concat/media Mediasize: 819977973760 (764G) Sectorsize: 512 Mode: r1w0e1 Consumers: 1. Name: da0p1 Mediasize: 319988660736 (298G) Sectorsize: 512 Mode: r1w0e2 Start: 499989313536 End: 819977973760 2. Name: da1p1 Mediasize: 499989314048 (466G) Sectorsize: 512 Mode: r1w0e2 Start: 0 End: 499989313536 tw_cli output: //solfertje> /c0 show Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-1 OK - - - 298.013 ON OFF u1 RAID-1 OK - - - 465.651 ON OFF Port Status Unit Size Blocks Serial --------------------------------------------------------------- p0 OK u1 465.76 GB 976773168 9VM18XZY p1 OK u0 298.09 GB 625142448 5QF383J7 p2 OK u1 465.76 GB 976773168 9VM141ST p3 OK u0 298.09 GB 625142448 9QF3Z5LM //solfertje> /c0 show unitstatus Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy ------------------------------------------------------------------------------ u0 RAID-1 OK - - - 298.013 ON OFF u1 RAID-1 OK - - - 465.651 ON OFF Alban Hertroys -- Screwing up is the best way to attach something to the ceiling. !DSPAM:74,4aa8f20512071992670156! From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 13:02:15 2009 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 0839B1065676; Thu, 10 Sep 2009 13:02:15 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 79D108FC1F; Thu, 10 Sep 2009 13:02:14 +0000 (UTC) Received: from vhoffman.lon.namesco.net (115.73-246-213.ippool.namesco.net [213.246.73.115]) (authenticated bits=0) by unsane.co.uk (8.14.3/8.14.3) with ESMTP id n8AD5KMU043647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 14:05:22 +0100 (BST) (envelope-from vince@unsane.co.uk) Message-ID: <4AA8F8D1.409@unsane.co.uk> Date: Thu, 10 Sep 2009 14:02:09 +0100 From: Vincent Hoffman User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Kostik Belousov References: <4AA7D8B3.1010203@unsane.co.uk> <200909091339.00193.jhb@freebsd.org> <20090909190228.GC47688@deviant.kiev.zoral.com.ua> <4AA8D62F.1020901@unsane.co.uk> <20090910112850.GG47688@deviant.kiev.zoral.com.ua> In-Reply-To: <20090910112850.GG47688@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: general protection fault on 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, 10 Sep 2009 13:02:15 -0000 Kostik Belousov wrote: > On Thu, Sep 10, 2009 at 11:34:23AM +0100, Vincent Hoffman wrote: > >> Kostik Belousov wrote: >> >>> On Wed, Sep 09, 2009 at 01:38:59PM -0400, John Baldwin wrote: >>> >>> >>>> On Wednesday 09 September 2009 12:32:51 pm Vincent Hoffman wrote: >>>> >>>> >>>>> Hi all, >>>>> I've been running the 8.0-BETAs in a xen virtual machine >>>>> (hvm/fully virtualised) for testing and something between r196730 and >>>>> r196746 causes a general protection fault on boot. I'll try and narrow >>>>> it down if i get a chance but I'm a a bit busy at the moment. >>>>> >>>>> backtrace is available at >>>>> http://unsane.co.uk/~jhary/freebsd/GPF-09-09-09.gif >>>>> Xen dom0 is a centos5.3 box using the xen-3.3.1 rpms from >>>>> http://www.gitco.de/linux/i386/centos/5/rpms/ if thats of any use. >>>>> >>>>> Let me know if I need to provide any more info. >>>>> >>>>> >>>> Hmm, can you try reverting 196737? Or actually, can you print out the value >>>> of %ebx ('p $ebx' in ddb will work I think)? I wonder if this patch would >>>> fix it: >>>> >>>> Index: pmap.c >>>> =================================================================== >>>> --- pmap.c (revision 196974) >>>> +++ pmap.c (working copy) >>>> @@ -999,7 +999,7 @@ >>>> * coherence domain. >>>> */ >>>> mfence(); >>>> - for (; sva < eva; sva += cpu_clflush_line_size) >>>> + for (; sva <= eva; sva += cpu_clflush_line_size) >>>> clflush(sva); >>>> mfence(); >>>> } else { >>>> >>>> >>> Oh, no, another pointy hat to me :(. >>> >>> Please, try this patch instead. >>> >>> diff --git a/sys/i386/xen/pmap.c b/sys/i386/xen/pmap.c >>> index 4b81aae..122318c 100644 >>> --- a/sys/i386/xen/pmap.c >>> +++ b/sys/i386/xen/pmap.c >>> @@ -1004,8 +1004,8 @@ pmap_invalidate_cache_range(vm_offset_t sva, vm_offset_t eva) >>> * coherence domain. >>> */ >>> mfence(); >>> - for (; eva < sva; eva += cpu_clflush_line_size) >>> - clflush(eva); >>> + for (; sva < eva; sva += cpu_clflush_line_size) >>> + clflush(sva); >>> mfence(); >>> } else { >>> >>> >>> >> Hi, >> I tried this this morning with no joy i'm afraid. >> not much change but new backtrace (with p $ebx) at >> http://www.unsane.co.uk/~jhary/freebsd/10-09-09.gif >> > I would need the panic message and ddb lines that are not > present on your screenshot. > > Also, the dmesg is interesting (CPU features report). > Sorry, did need more coffee after all then. http://unsane.co.uk/~jhary/freebsd/gpf-10-09-09-1.gif http://unsane.co.uk/~jhary/freebsd/gpf-10-09-09-2.gif http://unsane.co.uk/~jhary/freebsd/dmesg.boot like I said, Console access via vnc is available if wanted. Vince >> Just to check I'm not in need of more coffee as i'm still learning svn >> (and my coding skills such as they are lie in shell and perl) >> >> krill# svn info >> Path: . >> URL: svn://svn.freebsd.org/base/stable/8 >> Repository Root: svn://svn.freebsd.org/base >> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >> Revision: 196740 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: rnoland >> Last Changed Rev: 196737 >> Last Changed Date: 2009-09-01 17:41:28 +0100 (Tue, 01 Sep 2009) >> >> >> krill# sed -n '1010,1017p' sys/i386/xen/pmap.c >> * coherence domain. >> */ >> mfence(); >> for (; sva < eva; sva += cpu_clflush_line_size) >> clflush(sva); >> mfence(); >> } else { >> >> krill# >> >> Happy to give vnc access to the console of the machine if that would help. >> >> Vince >> From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 13:21:07 2009 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 DD4D91065676 for ; Thu, 10 Sep 2009 13:21:07 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 9BA7C8FC0A for ; Thu, 10 Sep 2009 13:21:07 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MljaF-000Frq-P4 for freebsd-stable@freebsd.org; Thu, 10 Sep 2009 15:21:07 +0200 Date: Thu, 10 Sep 2009 15:21:07 +0200 From: Kurt Jaeger To: freebsd-stable@freebsd.org Message-ID: <20090910132107.GH48206@home.opsec.eu> References: <1252426982.00160755.1252414203@10.7.7.3> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> <200909102213.36510.doconnor@gsoft.com.au> <94AEB920-0384-4E03-8589-8315F5DC549C@ronner.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <94AEB920-0384-4E03-8589-8315F5DC549C@ronner.org> Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 13:21:08 -0000 Hi! > > I thought coretemp had be modified in HEAD to support Phenoms but I > > can't find any evidence of that in SVN so I am not sure what I am > > thinking.. > > How about 'k8temp'? /usr/ports/sysutils/k8temp This works, very nice! Thanks! -- pi@opsec.eu +49 171 3101372 11 years to go ! From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 13:28:46 2009 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 04F56106566C for ; Thu, 10 Sep 2009 13:28:46 +0000 (UTC) (envelope-from bap-fbsd-stable@a1.org.uk) Received: from mail.gwork.org (barney.gwork.org [85.234.141.70]) by mx1.freebsd.org (Postfix) with ESMTP id BB1838FC17 for ; Thu, 10 Sep 2009 13:28:45 +0000 (UTC) Received: by mail.gwork.org (Postfix, from userid 33) id 8664B6C210; Thu, 10 Sep 2009 14:09:46 +0100 (BST) Received: from 5acd575c.bb.sky.com (5acd575c.bb.sky.com [90.205.87.92]) by mail.gwork.org (Horde Framework) with HTTP; Thu, 10 Sep 2009 14:09:46 +0100 Message-ID: <20090910140946.95543prdehmirhc0@mail.gwork.org> X-Priority: 3 (Normal) Date: Thu, 10 Sep 2009 14:09:46 +0100 From: Bap To: freebsd-stable@freebsd.org References: <1252426982.00160755.1252414203@10.7.7.3> <200909091018.10509.doconnor@gsoft.com.au> <4AA72D4D.9080505@FreeBSD.org> <200909091747.19696.doconnor@gsoft.com.au> <1252501703.85394.3473.camel@balrog.2hip.net> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> <4AA7CE0A.9030502@icyb.net.ua> <20090909155921.GG48206@home.opsec.eu> In-Reply-To: <20090909155921.GG48206@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (5.0-cvs) X-Gwork-MailScanner-ID: 8664B6C210.E7AA1 X-Gwork-MailScanner: Found to be clean X-Gwork-MailScanner-From: bap-fbsd-stable@a1.org.uk X-Spam-Status: No Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 13:28:46 -0000 Quoting Kurt Jaeger : > Hi! > >> > Any information on what can be done with AMD CPUs with respect >> > to temperature monitoring ? >> >> amdtemp(4) ? :-) > > home$ man amdtemp > No manual entry for amdtemp > > It's on 8.0-BETA4, but I have no amd64 running with that, yet. > wise# kldload k8temp wise# sysctl -a | grep k8temp dev.k8temp.0.%desc: AMD K8 Thermal Sensors dev.k8temp.0.%driver: k8temp dev.k8temp.0.%parent: hostb3 dev.k8temp.0.sensor0.core0: 21 dev.k8temp.0.sensor0.core1: 20 dev.k8temp.0.sensor1.core0: 21 dev.k8temp.0.sensor1.core1: 18 wise# uname -a FreeBSD xxxxxxxxxxxxxxxxx 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan =20 1 08:58:24 UTC 2009 =20 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Bap. > -- > pi@opsec.eu +49 171 3101372 11 =20 > years to go ! > _______________________________________________ > 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 Sep 10 13:31:43 2009 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 32B99106566C for ; Thu, 10 Sep 2009 13:31:43 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id EA69B8FC1E for ; Thu, 10 Sep 2009 13:31:42 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 3530073106; Thu, 10 Sep 2009 15:37:41 +0200 (CEST) Date: Thu, 10 Sep 2009 15:37:41 +0200 From: Luigi Rizzo To: Kurt Jaeger Message-ID: <20090910133741.GA6000@onelab2.iet.unipi.it> References: <1252426982.00160755.1252414203@10.7.7.3> <4AA7AA9B.9010709@FreeBSD.org> <20090909153851.GE48206@home.opsec.eu> <200909102213.36510.doconnor@gsoft.com.au> <94AEB920-0384-4E03-8589-8315F5DC549C@ronner.org> <20090910132107.GH48206@home.opsec.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090910132107.GH48206@home.opsec.eu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 13:31:43 -0000 On Thu, Sep 10, 2009 at 03:21:07PM +0200, Kurt Jaeger wrote: > Hi! > > > > I thought coretemp had be modified in HEAD to support Phenoms but I > > > can't find any evidence of that in SVN so I am not sure what I am > > > thinking.. > > > > How about 'k8temp'? > > /usr/ports/sysutils/k8temp > > This works, very nice! note though that the numbers you get seem way off reality: bsd7# k8temp CPU 0 Core 0 Sensor 0: 13c CPU 0 Core 0 Sensor 1: 13c CPU 0 Core 1 Sensor 0: 16c CPU 0 Core 1 Sensor 1: 3c (they do increase with CPU load). From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 13:32:34 2009 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 618651065670; Thu, 10 Sep 2009 13:32:34 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id AE14A8FC1E; Thu, 10 Sep 2009 13:32:33 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-124-246.lns11.adl6.internode.on.net [121.45.124.246]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n8ADWT10087896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 23:02:30 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 10 Sep 2009 23:02:19 +0930 User-Agent: KMail/1.9.10 References: <20090906155154.GA8283@onelab2.iet.unipi.it> <20090909203216.GA93761@onelab2.iet.unipi.it> <200909091642.06046.jhb@freebsd.org> In-Reply-To: <200909091642.06046.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1480948.AHEMIzcntJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909102302.26318.doconnor@gsoft.com.au> X-Spam-Score: -1.598 () AWL,BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Luigi Rizzo , John Baldwin Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 10 Sep 2009 13:32:34 -0000 --nextPart1480948.AHEMIzcntJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 10 Sep 2009, John Baldwin wrote: > > $ARCH/isa/clock.c::DELAY(). I suppose with a few measurements > > at different HZ values and some back of the envelope calculations > > one could even determine estimate the frequency and duration > > of those SMI interrupts! > > On recent motherboards I have seen the SMI# interrupt fire every 250 > ms with execution times ranging from 50 us to 1ms for the legacy USB > interrupt handler. We consistently see the TSC frequency > miscalculated on the motherboards with the 1ms duration interrupt. I > suspect that the clock that drives the periodic SMI# interrupt is > tied to the i8254 meaning that it often fires at the same time that > the i8254 wraps causing the TSC frequency to often be wrong. Can the calculation code disable the SMI# interrupt? Disabling legacy=20 USB could be a problem if you want to use a USB keyboard with the=20 loader (I think). =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1480948.AHEMIzcntJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKqP/q5ZPcIHs/zowRApbKAJ0Y8SHe6RVNNgKBWgeWlQ0MY4L6zACfelI6 ugYVtZytpigqEj9XR/2ICpE= =dhSe -----END PGP SIGNATURE----- --nextPart1480948.AHEMIzcntJ-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 13:32:52 2009 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 CBA0F10656D4 for ; Thu, 10 Sep 2009 13:32:52 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5188FC25 for ; Thu, 10 Sep 2009 13:32:51 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-124-246.lns11.adl6.internode.on.net [121.45.124.246]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id n8ADWnND087907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 10 Sep 2009 23:02:50 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 10 Sep 2009 23:02:46 +0930 User-Agent: KMail/1.9.10 References: <200909082209.37454.doconnor@gsoft.com.au> <20090909171530.GC38292@graf.pompo.net> In-Reply-To: <20090909171530.GC38292@graf.pompo.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart27837417.CVUlm1m7aO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200909102302.47809.doconnor@gsoft.com.au> X-Spam-Score: -1.599 () AWL,BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Thierry Thomas Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 13:32:52 -0000 --nextPart27837417.CVUlm1m7aO Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 10 Sep 2009, Thierry Thomas wrote: > > I recently discovered a system where the floppy drive cable was > > intermittently fouling the CPU fan - I believe this caused the CPU > > to overheat and then get throttled by the BIOS. > > > > Does anyone know if it is possible to determine if this is the > > case? ie is there a way to be informed if throttling has occurred? > > Have you tried the ports sysutils/lmmon and sysutils/wmlmmon? > > Some others exist under /usr/ports/sysutils, but I don't use them. Those tools are usually very difficult to get to work unless you can get=20 information from your motherboard maker because various voltage=20 dividers are set by the mobo maker.. In any case measuring the temperature is only a proxy, direct (rate=20 limited!) notification of the throttling even would be better. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart27837417.CVUlm1m7aO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBKqP//5ZPcIHs/zowRAlUaAKCqpzFpYke/H7qw1UVqaDGl41qQIQCggP7W dQs1RftveH4u6rtnOLni93c= =jb5h -----END PGP SIGNATURE----- --nextPart27837417.CVUlm1m7aO-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 13:50:46 2009 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 0CF6C1065692; Thu, 10 Sep 2009 13:50:46 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id C40238FC15; Thu, 10 Sep 2009 13:50:45 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id BE7BB730DA; Thu, 10 Sep 2009 15:56:44 +0200 (CEST) Date: Thu, 10 Sep 2009 15:56:44 +0200 From: Luigi Rizzo To: Daniel O'Connor Message-ID: <20090910135644.GA6109@onelab2.iet.unipi.it> References: <20090906155154.GA8283@onelab2.iet.unipi.it> <20090909203216.GA93761@onelab2.iet.unipi.it> <200909091642.06046.jhb@freebsd.org> <200909102302.26318.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909102302.26318.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: incorrect usleep/select delays with HZ > 2500 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, 10 Sep 2009 13:50:46 -0000 On Thu, Sep 10, 2009 at 11:02:19PM +0930, Daniel O'Connor wrote: > On Thu, 10 Sep 2009, John Baldwin wrote: > > > $ARCH/isa/clock.c::DELAY(). I suppose with a few measurements > > > at different HZ values and some back of the envelope calculations > > > one could even determine estimate the frequency and duration > > > of those SMI interrupts! > > > > On recent motherboards I have seen the SMI# interrupt fire every 250 > > ms with execution times ranging from 50 us to 1ms for the legacy USB > > interrupt handler. We consistently see the TSC frequency > > miscalculated on the motherboards with the 1ms duration interrupt. I > > suspect that the clock that drives the periodic SMI# interrupt is > > tied to the i8254 meaning that it often fires at the same time that > > the i8254 wraps causing the TSC frequency to often be wrong. > > Can the calculation code disable the SMI# interrupt? Disabling legacy > USB could be a problem if you want to use a USB keyboard with the > loader (I think). surely I don't think disabling these interrupts is a viable option. Perhaps the best we can do in the calibration loop is alternate reads of the tsc and the i8254 counter (getit()), and if we see too many ticks between two subsequent calls to getit() it means that we have been interrupted and should discard the last measurement interval. Problem is, right now the calibration loop is start = rdtsc(); DELAY(1000000); b = rdtsc; and DELAY is unaware of the existence of the TSC. We should write some custom DELAY() code to implement the calibration as above. cheers luigi From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 14:37:57 2009 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 58D57106566B for ; Thu, 10 Sep 2009 14:37:57 +0000 (UTC) (envelope-from sagara@tomahawk.com.sg) Received: from us1.tomahawkonline.net (us1.tomahawkonline.net [66.98.178.56]) by mx1.freebsd.org (Postfix) with SMTP id 05E598FC14 for ; Thu, 10 Sep 2009 14:37:56 +0000 (UTC) Received: (qmail 10462 invoked from network); 10 Sep 2009 11:17:21 -0000 Received: from 219.74.242.111 (HELO tdsblack.lan) (sagara@tomahawk.com.sg@219.74.242.111) by us1.tomahawkonline.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 10 Sep 2009 11:17:21 -0000 Message-ID: <4AA90F9F.6080702@tomahawk.com.sg> Date: Thu, 10 Sep 2009 22:39:27 +0800 From: Sagara Wijetunga User-Agent: Thunderbird 2.0.0.22 (X11/20090703) MIME-Version: 1.0 To: Dimitry Andric References: <4AA8EBBD.5020709@tomahawk.com.sg> <4AA8EC4D.3080800@andric.com> In-Reply-To: <4AA8EC4D.3080800@andric.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Avahi compilation help needed 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, 10 Sep 2009 14:37:57 -0000 Dimitry Andric wrote: > On 2009-09-10 14:06, Sagara Wijetunga wrote: > >> I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2 >> (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors. >> > > Any reason why you don't use the net/avahi port instead? This will save > you most compilation and installation headaches. > Tomahawk Desktop uses FreeBSD sources, it is not based on the FreeBSD distribution. It doesn't have a port system. Tomahawk Desktop is designed everything to be installed simply by "./configure, [g]make, [g]make install" which FreeBSD is not designed to support. In Tomahawk Desktop, anything you compile and install, can be cleanly uninstalled without any file left out, which is not possible in FreeBSD. Here "compile and install" means you take a package, unpack, make and make install, that's it. You don't have wait until somebody prepare a port for you. Coming back to our problem, Avahi get compile errors on FreeBSD when its original build system is used. We need a help. Appreciate if somebody could give it a try to just compile (ie. download the package, unpack, ./configure and gmake). Kind regards Sagara From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 14:41:35 2009 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 D8A0F1065697 for ; Thu, 10 Sep 2009 14:41:35 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 6F09A8FC08 for ; Thu, 10 Sep 2009 14:41:35 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.1) with ESMTP id n8AEUbCg004074 for ; Thu, 10 Sep 2009 17:30:37 +0300 (EEST) (envelope-from mamalos@eng.auth.gr) Message-ID: <4AA90D88.4010004@eng.auth.gr> Date: Thu, 10 Sep 2009 17:30:32 +0300 From: George Mamalakis User-Agent: Thunderbird 2.0.0.19 (X11/20090226) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 10 Sep 2009 14:41:36 -0000 Hello everybody, Yesterday I installed FreeBSD 8.0-BETA4 on an IBM 3650, having a ServerRaid 8k adapter, and 6 sata disks on raid-6. The raid-6 volume was "synchronizing" for a day, so this syncing process was happening while I was installing fbsd on the server. During the installation I was understanding that (writing) performance was low, but this was rational, considering the fact that the raid controller had to synchronize its disks. After the system got installed, and while the controller was still syncing, I ran "portsnap fetch extract" to get the latest ports. During this process, all my terminals kept lagging when I was opening files, browsing directories, etc, and the following kernel message appeared in dmesg: lock order reversal: 1st 0xffffff807c133540 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559 2nd 0xffffff0003deb200 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e _sx_xlock() at _sx_xlock+0x55 ufsdirhash_acquire() at ufsdirhash_acquire+0x33 ufsdirhash_add() at ufsdirhash_add+0x19 ufs_direnter() at ufs_direnter+0x88b ufs_makeinode() at ufs_makeinode+0x2a7 VOP_CREATE_APV() at VOP_CREATE_APV+0x8d vn_open_cred() at vn_open_cred+0x468 kern_openat() at kern_openat+0x179 syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = 0x7fffffffe688, rbp = 0x1a4 --- lock order reversal: 1st 0xffffff00352cbd80 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2083 2nd 0xffffff807c133540 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_softdep.c:6177 3rd 0xffffff00352cbba8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2083 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xcf3 ffs_lock() at ffs_lock+0x8c VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b _vn_lock() at _vn_lock+0x47 vget() at vget+0x7b vfs_hash_get() at vfs_hash_get+0xd5 ffs_vgetf() at ffs_vgetf+0x48 softdep_sync_metadata() at softdep_sync_metadata+0x456 ffs_syncvnode() at ffs_syncvnode+0x210 ffs_fsync() at ffs_fsync+0x43 ufs_direnter() at ufs_direnter+0x315 ufs_makeinode() at ufs_makeinode+0x2a7 VOP_CREATE_APV() at VOP_CREATE_APV+0x8d vn_open_cred() at vn_open_cred+0x468 kern_openat() at kern_openat+0x179 syscall() at syscall+0x1af Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (5, FreeBSD ELF64, open), rip = 0x800e32dfc, rsp = 0x7fffffffe688, rbp = 0x1a4 --- aac0: COMMAND 0xffffff80003e08a0 TIMEOUT AFTER 40 SECONDS aac0: COMMAND 0xffffff80003d5070 TIMEOUT AFTER 40 SECONDS aac0: COMMAND 0xffffff80003e0d00 TIMEOUT AFTER 40 SECONDS aac0: COMMAND 0xffffff80003d9440 TIMEOUT AFTER 40 SECONDS .... ...and kept on like that, for many many lines, with decreasing timeouts. Once the syncing process stopped, everything came back to normal (not that I have stress-tested the machine, to be honest...). But since it happened once, during this specific procedure, then maybe it could also happen when the raid controller is reconstructing its volumes; and this would be very annoying, as far as the server's efficiency (and/or maybe stability) is concerned. The kernel is GENERIC-amd64 and untouched, if someone may need more information (eg, dmesg output) please do not hesitate to say so. Thank you all for your time in advance, mamalos -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 14:46:56 2009 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 8F423106566B for ; Thu, 10 Sep 2009 14:46:56 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 564DC8FC15 for ; Thu, 10 Sep 2009 14:46:56 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:a495:f7c6:da21:cbdb] (unknown [IPv6:2001:7b8:3a7:0:a495:f7c6:da21:cbdb]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 4A0325C43; Thu, 10 Sep 2009 16:46:55 +0200 (CEST) Message-ID: <4AA91160.40207@andric.com> Date: Thu, 10 Sep 2009 16:46:56 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.4pre) Gecko/20090904 Shredder/3.0b4pre MIME-Version: 1.0 To: Sagara Wijetunga References: <4AA8EBBD.5020709@tomahawk.com.sg> <4AA8EC4D.3080800@andric.com> <4AA90F9F.6080702@tomahawk.com.sg> In-Reply-To: <4AA90F9F.6080702@tomahawk.com.sg> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Avahi compilation help needed 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, 10 Sep 2009 14:46:56 -0000 On 2009-09-10 16:39, Sagara Wijetunga wrote: > Tomahawk Desktop uses FreeBSD sources, it is not based on the FreeBSD distribution. Please contact the Tomahawk Desktop mailing lists then. :) From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 14:51:49 2009 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 1C0B11065670 for ; Thu, 10 Sep 2009 14:51:49 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4B48FC0A for ; Thu, 10 Sep 2009 14:51:48 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mlkzx-0002aS-6X for freebsd-stable@freebsd.org; Thu, 10 Sep 2009 16:51:45 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Sep 2009 16:51:45 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 10 Sep 2009 16:51:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Thu, 10 Sep 2009 16:51:28 +0200 Lines: 57 Message-ID: References: <4AA90D88.4010004@eng.auth.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.22 (X11/20090817) In-Reply-To: <4AA90D88.4010004@eng.auth.gr> Sender: news Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 10 Sep 2009 14:51:49 -0000 George Mamalakis wrote: > Hello everybody, > > Yesterday I installed FreeBSD 8.0-BETA4 on an IBM 3650, having a 3650 M1 or M2? > ServerRaid 8k adapter, and 6 sata disks on raid-6. The raid-6 volume was > "synchronizing" for a day, so this syncing process was happening while I > was installing fbsd on the server. During the installation I was I can give you only some generic information. > lock order reversal: > 1st 0xffffff807c133540 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2559 > 2nd 0xffffff0003deb200 dirhash (dirhash) @ > /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 You have received this message because you are running a debug kernel; a normal kernel with debugging disabled would not have shown it. By the fact that you did received it and the system managed to recover from it it is likely that the issue is harmless. It's likely related to the following timeouts. > aac0: COMMAND 0xffffff80003e08a0 TIMEOUT AFTER 40 SECONDS > aac0: COMMAND 0xffffff80003d5070 TIMEOUT AFTER 40 SECONDS > aac0: COMMAND 0xffffff80003e0d00 TIMEOUT AFTER 40 SECONDS > aac0: COMMAND 0xffffff80003d9440 TIMEOUT AFTER 40 SECONDS > .... > > ...and kept on like that, for many many lines, with decreasing timeouts. It looks like the controller was too busy rebuilding to take any new requests. It is possible you have filled the controller's write cache and that is why the lag happened at this point. You can easily test this theory. > Once the syncing process stopped, everything came back to normal (not > that I have stress-tested the machine, to be honest...). But since it > happened once, during this specific procedure, then maybe it could also > happen when the raid controller is reconstructing its volumes; and this > would be very annoying, as far as the server's efficiency (and/or maybe > stability) is concerned. Yes, you are right. But if the controller is the issue here, there is not much you can do about it. If it has a "priority" setting between normal usage and rebuilding/resyncing you might alter it to favour normal usage. Initial rebuild of RAID 5/6 is also a bit specific as it touches all drives and, in some instances (don't know specifically about ServeRAID), it means all drives are rewritten in their entirety. If you determine rebuild/resync is problematic, you might consider using a RAID mode that doesn't require it to be so extensive, like RAID 10 with 4+ drives, or software RAID with ZFS. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 14:52:45 2009 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 3484F1065692 for ; Thu, 10 Sep 2009 14:52:45 +0000 (UTC) (envelope-from sagara@tomahawk.com.sg) Received: from us1.tomahawkonline.net (us1.tomahawkonline.net [66.98.178.56]) by mx1.freebsd.org (Postfix) with SMTP id D3F458FC2A for ; Thu, 10 Sep 2009 14:52:44 +0000 (UTC) Received: (qmail 10600 invoked from network); 10 Sep 2009 11:32:09 -0000 Received: from 219.74.242.111 (HELO tdsblack.lan) (sagara@tomahawk.com.sg@219.74.242.111) by us1.tomahawkonline.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 10 Sep 2009 11:32:09 -0000 Message-ID: <4AA91318.50908@tomahawk.com.sg> Date: Thu, 10 Sep 2009 22:54:16 +0800 From: Sagara Wijetunga User-Agent: Thunderbird 2.0.0.22 (X11/20090703) MIME-Version: 1.0 To: Dimitry Andric References: <4AA8EBBD.5020709@tomahawk.com.sg> <4AA8EC4D.3080800@andric.com> <4AA90F9F.6080702@tomahawk.com.sg> <4AA91160.40207@andric.com> In-Reply-To: <4AA91160.40207@andric.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Avahi compilation help needed 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, 10 Sep 2009 14:52:45 -0000 Dimitry Andric wrote: > On 2009-09-10 16:39, Sagara Wijetunga wrote: > >> Tomahawk Desktop uses FreeBSD sources, it is not based on the FreeBSD distribution. >> > > Please contact the Tomahawk Desktop mailing lists then. :) > We are Tomahawk Desktop :) From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 15:35:14 2009 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 2E956106566B for ; Thu, 10 Sep 2009 15:35:14 +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 F31BB8FC12 for ; Thu, 10 Sep 2009 15:35:13 +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 A0E2246B58; Thu, 10 Sep 2009 11:35:13 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id A40958A01B; Thu, 10 Sep 2009 11:35:12 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 10 Sep 2009 11:32:43 -0400 User-Agent: KMail/1.9.7 References: <4AA8EBBD.5020709@tomahawk.com.sg> <4AA8EC4D.3080800@andric.com> <4AA90F9F.6080702@tomahawk.com.sg> In-Reply-To: <4AA90F9F.6080702@tomahawk.com.sg> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909101132.43781.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 10 Sep 2009 11:35:12 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Dimitry Andric , Sagara Wijetunga Subject: Re: Avahi compilation help needed 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, 10 Sep 2009 15:35:14 -0000 On Thursday 10 September 2009 10:39:27 am Sagara Wijetunga wrote: > Dimitry Andric wrote: > > On 2009-09-10 14:06, Sagara Wijetunga wrote: > > > >> I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2 > >> (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors. > >> > > > > Any reason why you don't use the net/avahi port instead? This will save > > you most compilation and installation headaches. > > > Tomahawk Desktop uses FreeBSD sources, it is not based on the FreeBSD distribution. It doesn't have a port system. Tomahawk Desktop is designed everything to be installed simply by "./configure, [g]make, [g]make install" which FreeBSD is not designed to support. In Tomahawk Desktop, anything you compile and install, can be cleanly uninstalled without any file left out, which is not possible in FreeBSD. Here "compile and install" means you take a package, unpack, make and make install, that's it. You don't have wait until somebody prepare a port for you. > > Coming back to our problem, Avahi get compile errors on FreeBSD when its original build system is used. We need a help. Appreciate if somebody could give it a try to just compile (ie. download the package, unpack, ./configure and gmake). The avahi ports can still be useful to look at as they contain patches that you will probably need. For example, net/avahi-app has a patch against the configure script in files/patch-configure. In total it seems that net/avahi-app has 21 different patches to the avahi sources (you may not need all of them however). I would start by looking at those. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 15:37:33 2009 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 550CC106568D for ; Thu, 10 Sep 2009 15:37:33 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.freebsd.org (Postfix) with ESMTP id DBCB18FC17 for ; Thu, 10 Sep 2009 15:37:32 +0000 (UTC) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr15.xs4all.nl (8.13.8/8.13.8) with ESMTP id n8AFbTKn090288; Thu, 10 Sep 2009 17:37:30 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id D7E00BA7C; Thu, 10 Sep 2009 17:37:29 +0200 (CEST) Date: Thu, 10 Sep 2009 17:37:29 +0200 From: Roland Smith To: Sagara Wijetunga Message-ID: <20090910153729.GB30059@slackbox.xs4all.nl> References: <4AA8EBBD.5020709@tomahawk.com.sg> <4AA8EC4D.3080800@andric.com> <4AA90F9F.6080702@tomahawk.com.sg> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <4AA90F9F.6080702@tomahawk.com.sg> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Dimitry Andric , freebsd-stable@freebsd.org Subject: Re: Avahi compilation help needed 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, 10 Sep 2009 15:37:33 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 10, 2009 at 10:39:27PM +0800, Sagara Wijetunga wrote: > Dimitry Andric wrote: > > On 2009-09-10 14:06, Sagara Wijetunga wrote: > > =20 > >> I'm trying to compile Avahi-0.6.25 (http://avahi.org/) on FreeBSD 7.2= =20 > >> (i386) [in fact, on Tomahawk Desktop]. It develops compilation errors.= =20 > >> =20 > > > > Any reason why you don't use the net/avahi port instead? This will save > > you most compilation and installation headaches. =20 My thoughts exactly.=20 > Tomahawk Desktop uses FreeBSD sources, it is not based on the FreeBSD > distribution.=20 What does that mean? The FreeBSD sources by default make a complete _base_ distribution. > It doesn't have a port system. Tomahawk Desktop is designed > everything to be installed simply by "./configure, [g]make, [g]make insta= ll" > which FreeBSD is not designed to support.=20 This is demonstrable not correct. The FreeBSD ports system _does_ use configure and friends when available in the source of the package. E.g, eve= ry port that has 'GNU_CONFIGURE=3D yes' in its Makefile uses it. The ports sys= tem is nothing more than a wrapper to allow unmodified sources to be built on FreeBSD. > In Tomahawk Desktop, anything you compile and install, can be cleanly > uninstalled without any file left out, which is not possible in FreeBSD. Again this is demonstrable false. There are plenty of ports that deinstall cleanly. One of my own ports, graphics/stl2pov, for example. If what you are saying were true, it would come as a suprise to many ports developers. Sure, there are ports with incorrect packing lists which leave files behind, but usually that is not a big problem.=20 And the ports system (correctly, IMO) will not delete files that have been modified and non-empty directories; a ports system should _never_ delete an= y of the users' files. > Here "compile and install" means you take a package, unpack, make and make > install, that's it. You don't have wait until somebody prepare a port for > you. But you do have to wait until somebody sorts out the compile problems... Wh= ich amount to the same thing. And which can be a royal PITA as you are dicoveri= ng. :-) IMHO, what you are doing is effectively a huge duplication of effort. I wou= ld advise you to switch over to the ports system and save yourself a lot of work. If you require applications that are currently not in ports, it is easier to submit and maintain a few ports than a complete system. > Coming back to our problem, Avahi get compile errors on FreeBSD when its > original build system is used. We need a help. Appreciate if somebody cou= ld > give it a try to just compile (ie. download the package, unpack, ./config= ure > and gmake). Avahi needs patches to work properly on FreeBSD. See e.g. the files/ direct= ory in the net/avahi-app port. Applying those patches should solve most of your problem. Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkqpHTkACgkQEnfvsMMhpyWuhwCfSf5jsNhTNbSd+6XjmqskYrKB On8An3ZCXy3GfHgJBQq1rR5XSAtD2nM/ =mvvZ -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 16:06:33 2009 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 855D71065672 for ; Thu, 10 Sep 2009 16:06:33 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id 140C18FC12 for ; Thu, 10 Sep 2009 16:06:32 +0000 (UTC) Received: by ewy4 with SMTP id 4so253091ewy.36 for ; Thu, 10 Sep 2009 09:06:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=Yeg2iHVA9rDtTmaZmvW+fzoDtbnSDW2j1xj4NYeuJ7U=; b=B49vyiZ+irSXAZS7Ac3yzapMIhqIwnJacwiNTaBDCQfZsbSSo/YhbK9crF2Z+5wOP/ 4FrKHWtfkQNUEf4MOlS3Kt2SBYLqyBlHizM/u8Ic9x4VILQztcexPsr6IpnzUeER/r3R afcMycgOWE+YdAwnQPooIKXw46pkmC1D0s2AA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=vUlFpOGJ6wjMpSFmvisC4SN2PeBIcZIjHNarIAFUFp5TtuC1J2pCnknFO0zh+DoURh 6+Lg3j1tStfUf8mf12VKGxmylFM6JnaZMjN/dk2Ew26tpS4yoSd+tGq5TFM4RE5fiUR1 ZlKk7s2/5CDs9TgoCAK1P58G9KVAUSRugz+Mc= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.7.212 with SMTP id 62mr494977wep.92.1252597036478; Thu, 10 Sep 2009 08:37:16 -0700 (PDT) In-Reply-To: <1252595839.75144.26.camel@bauer.cse.buffalo.edu> References: <200909101404.n8AE41C6021588@svn.freebsd.org> <1252592951.49151.3.camel@buffy.york.ac.uk> <1252595839.75144.26.camel@bauer.cse.buffalo.edu> From: Ivan Voras Date: Thu, 10 Sep 2009 17:36:56 +0200 X-Google-Sender-Auth: 0da9531aab6da75e Message-ID: <9bbcef730909100836l3835825cy83082a2cfe4da0c3@mail.gmail.com> To: Ken Smith Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, src-committers@freebsd.org, svn-src-stable@freebsd.org, svn-src-all@freebsd.org, Gavin Atkinson , svn-src-stable-8@freebsd.org, Ken Smith Subject: Re: svn commit: r197065 - in stable/8: etc/defaults lib/libc/stdlib sys/amd64/conf sys/i386/conf sys/ia64/conf sys/pc98/conf sys/powerpc/conf sys/sparc64/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: Thu, 10 Sep 2009 16:06:33 -0000 2009/9/10 Ken Smith : > On Thu, 2009-09-10 at 15:29 +0100, Gavin Atkinson wrote: >> This seems like a step backwards to me: crash dumps have been left >> enabled in 7.x and have proved very useful from the point of view of >> improved quality of received PRs. =C2=A0I'm not aware of any problems >> relating to leaving them enabled. >> >> I'd appreciate it if this decision was reconsidered. >> > > Unfortunately as I said before there is no "Right answer" for this one. No, but there is an "80% right" one, based on the question: did the change in 7 cause known problems for any significant number of users (or one of two big users - that should be enough). After all, if users were fine with crashdumps & symbols being enabled in 7, they should be find with them being enabled in 8. > If there is (a lot) more push-back on this we'll reconsider it. But the > AUTO setting is only appropriate for machines that are "actively being > watched over". In -stable branches we start to have people using it for > large data centers full of machines that are only "partially watched > over" at best as well as machines stuffed in phone closets in remote > locations, etc. Having the AUTO setting for situations like that can > mean increased time for a reboot to happen, there is extra risk of the > machine wedging and not rebooting at all (requiring manual intervention > to get it back up), there is risk of disk space issues, etc. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 16:16:09 2009 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 39F34106566B; Thu, 10 Sep 2009 16:16:09 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-stable@FreeBSD.org Date: Thu, 10 Sep 2009 12:15:58 -0400 User-Agent: KMail/1.6.2 References: <1252426982.00160755.1252414203@10.7.7.3> <20090910132107.GH48206@home.opsec.eu> <20090910133741.GA6000@onelab2.iet.unipi.it> In-Reply-To: <20090910133741.GA6000@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_AZSqKZvEDrempLW" Message-Id: <200909101216.01423.jkim@FreeBSD.org> Cc: Kurt Jaeger , Luigi Rizzo Subject: Re: Detecting CPU throttling on over temperature 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, 10 Sep 2009 16:16:09 -0000 --Boundary-00=_AZSqKZvEDrempLW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thursday 10 September 2009 09:37 am, Luigi Rizzo wrote: > On Thu, Sep 10, 2009 at 03:21:07PM +0200, Kurt Jaeger wrote: > > Hi! > > > > > > I thought coretemp had be modified in HEAD to support Phenoms > > > > but I can't find any evidence of that in SVN so I am not sure > > > > what I am thinking.. > > > > > > How about 'k8temp'? > > > > /usr/ports/sysutils/k8temp > > > > This works, very nice! > > note though that the numbers you get seem way off reality: > > bsd7# k8temp > CPU 0 Core 0 Sensor 0: 13c > CPU 0 Core 0 Sensor 1: 13c > CPU 0 Core 1 Sensor 0: 16c > CPU 0 Core 1 Sensor 1: 3c > > (they do increase with CPU load). I bet this is a Family 0Fh Revision G processor. In fact, I (accidently) found the problem and wrote the attached patch for amdtemp(4) last night. :-) Jung-uk Kim --Boundary-00=_AZSqKZvEDrempLW Content-Type: text/plain; charset="iso-8859-1"; name="amdtemp.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="amdtemp.diff" --- sys/dev/amdtemp/amdtemp.c.orig 2009-08-20 15:43:50.000000000 -0400 +++ sys/dev/amdtemp/amdtemp.c 2009-09-09 18:44:26.000000000 -0400 @@ -360,8 +360,13 @@ amdtemp_gettemp0f(device_t dev, amdsenso } pci_write_config(dev, AMDTEMP_REG0F, cfg, 1); temp = pci_read_config(dev, AMDTEMP_REG0F, 4); - temp = ((temp >> 16) & 0xff) * 10 + AMDTEMP_OFFSET0F; - + + /* Revision G has two more bits. */ + if ((cpu_id & CPUID_EXT_MODEL) >= 0x60000) + temp = ((temp >> 14) & 0x3ff) * 10 / 4 + AMDTEMP_OFFSET; + else + temp = ((temp >> 16) & 0xff) * 10 + AMDTEMP_OFFSET; + return (temp); } --Boundary-00=_AZSqKZvEDrempLW-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 16:53:12 2009 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 0BA891065672 for ; Thu, 10 Sep 2009 16:53:12 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 847398FC15 for ; Thu, 10 Sep 2009 16:53:11 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.1) with ESMTP id n8AGrAeo070255; Thu, 10 Sep 2009 19:53:10 +0300 (EEST) (envelope-from mamalos@eng.auth.gr) Message-ID: <4AA92EF1.6010804@eng.auth.gr> Date: Thu, 10 Sep 2009 19:53:05 +0300 From: George Mamalakis User-Agent: Thunderbird 2.0.0.19 (X11/20090226) MIME-Version: 1.0 To: Ivan Voras References: <4AA90D88.4010004@eng.auth.gr> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 10 Sep 2009 16:53:12 -0000 Ivan, thank you very much for answering; and now to your comments: > > 3650 M1 or M2? > On the box it writes x3650 (I forgot the initial 'x' before, sorry). > > You have received this message because you are running a debug kernel; > a normal kernel with debugging disabled would not have shown it. > So far, I understood :) > It looks like the controller was too busy rebuilding to take any new > requests. It is possible you have filled the controller's write cache > and that is why the lag happened at this point. You can easily test > this theory. > This is the exact reason why I am asking this question. If this behavior is normal, then there is no problem with me. But I couldn't be sure whether it was a driver's problem or a controller's problem. > > If you determine rebuild/resync is problematic, you might consider > using a RAID mode that doesn't require it to be so extensive, like > RAID 10 with 4+ drives, or software RAID with ZFS. > I was thinking of using other raid modes, along with ZFS (although still labeled 'experimental', and this is going to be our department's main file server, so I still have my second thoughts about it...), since FreeBSD does not recognize my 2.8T volume during installation. This means that I 'll have to break it into more volumes in order for FreeBSD to see it. Thank you for your answer again, and (now that you mentioned it:) ) in case anyone knows whether we'll be able to see partitions > 2T in the future (or now?!), please say how :). -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 18:18:07 2009 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 EC9461065697 for ; Thu, 10 Sep 2009 18:18:07 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 471358FC08 for ; Thu, 10 Sep 2009 18:18:06 +0000 (UTC) Received: by bwz2 with SMTP id 2so279591bwz.43 for ; Thu, 10 Sep 2009 11:18:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=hcqluhMizU+7qQ20+ryutNkl0ZM0VqdO51jcZOvnZ1s=; b=jnysrDUxR5Hp/Czob5O/xOuz/8W7Pzs9r7INGSji8ShQCOeJUmlKFhUbZwHbusj2/+ IiZ4tN96fwU0aWUwmPGm+H69BcurVtguCqCOX+wYgpcdqPXTCVPXFiVnIZtnf/68vniJ y6PbodhBQJqNLeWQ24L1xr27j8fTmbcR+plSc= 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=sJ/chcyveJlY2W50VzFu2S93Ixtsgeny1cd/+wqAGUN7lXQNhvuXLoSlduOj4eioyO Q+AgRA5CS7r+CZ2szkplCiuDoSCvoedQAn39zwPZjT9EeTQwBToIVgfIeWdmGRd1RPAU CjS79n68qkdl7jB9UpdSPSiknS84bN/2CwUxI= MIME-Version: 1.0 Received: by 10.204.19.145 with SMTP id a17mr1194024bkb.64.1252606686018; Thu, 10 Sep 2009 11:18:06 -0700 (PDT) In-Reply-To: <4AA92EF1.6010804@eng.auth.gr> References: <4AA90D88.4010004@eng.auth.gr> <4AA92EF1.6010804@eng.auth.gr> Date: Thu, 10 Sep 2009 22:18:05 +0400 Message-ID: From: pluknet To: George Mamalakis Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Ivan Voras Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 10 Sep 2009 18:18:08 -0000 2009/9/10 George Mamalakis : [about aac0: COMMAND 0xffffff80003d9440 TIMEOUT AFTER 40 SECONDS] >> It looks like the controller was too busy rebuilding to take any new >> requests. It is possible you have filled the controller's write cache and >> that is why the lag happened at this point. You can easily test this theory. >> > This is the exact reason why I am asking this question. If this behavior is > normal, then there is no problem with me. But I couldn't be sure whether it > was a driver's problem or a controller's problem. > I see it from time to time on a number of boxes. You can often ignore this. It might be due to (and a symptom of) high disk workload. Btw, there was a recent change to increase command timeout to 120s. > Thank you for your answer again, and (now that you mentioned it:) ) in case > anyone knows whether we'll be able to see partitions > 2T in the future (or > now?!), please say how :). > Look at gpart(8). -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 18:39:51 2009 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 187A41065672 for ; Thu, 10 Sep 2009 18:39:51 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id A21908FC13 for ; Thu, 10 Sep 2009 18:39:50 +0000 (UTC) Received: by ewy4 with SMTP id 4so391691ewy.36 for ; Thu, 10 Sep 2009 11:39:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=n6TVWhPTXCDJ/9uqd1z/6M3UgfFvbGqWRPiG+TfCcos=; b=FNQQH3/nsieBHixq1PQpQsGkczWk+aSoPgCADu2Am0RqlIXSVUT6BrZ47BuWmg0gnZ +AtK5S0RNCWZwhzQqf26vAblJB02sNV5q3bHwb7G+qZxpkjayNUJ0XyfocXzV8vQ8x4L FYqb0NYP7CqxlkHq71QeCvTl+btwQ5hQrD1Go= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=pjYsqaG4Wn8fXmTrGEH1jUaB0wsh8ljl01eFX/BXh9KC2RKnXTGa9Mq94Kp5/1UIWg Vx96afVsJzY60YUIfLpJeNNPRGXjNg7dwRKldTxhsAqREOUlGLt8mkBRwKww6kVawLdP SVd/9WTOGm0sRdJ1FQJHW1eUjG5/52/PlJnl8= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.26.77 with SMTP id b55mr476869wea.101.1252606315122; Thu, 10 Sep 2009 11:11:55 -0700 (PDT) In-Reply-To: <4AA92EF1.6010804@eng.auth.gr> References: <4AA90D88.4010004@eng.auth.gr> <4AA92EF1.6010804@eng.auth.gr> From: Ivan Voras Date: Thu, 10 Sep 2009 20:11:35 +0200 X-Google-Sender-Auth: bebab007d7a96342 Message-ID: <9bbcef730909101111l2d3a4e31y4710175e19e3f870@mail.gmail.com> To: George Mamalakis Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 10 Sep 2009 18:39:51 -0000 2009/9/10 George Mamalakis : > Thank you for your answer again, and (now that you mentioned it:) ) in case > anyone knows whether we'll be able to see partitions > 2T in the future (or > now?!), please say how :). Actually, FreeBSD can use arbitrary sized drives and partitions (64-bit) but it's only the default partition scheme (bsdlabel) that doesn't support it. Since bsdlabel is used by the default installer (sysinstall), it means you can't install FreeBSD on such a setup, which is recognized to be a Bad Thing. The solution is to use a modern partitioning scheme like GPT (which has 64-bit limits) and then: a) partition the drive/array from a Live CD and do a manual install of FreeBSD from the installer CDs - which isn't as hard as it sounds, since it involves basically two steps: installing the boot loaders and unpacking the files or b) install on a smaller drive (or volume if your controller supports creating arbitrary volumes / partitions on top of RAID topology) and use this drive/volume for the OS, and then partition and use the larger array/volume for data. In either case, once you manually partition the drive/volume with GPT, you will encounter no further size limits. A really kludgy workaround, which I don't think you should use, is to create two partitions (I don't know if you could create more than two 2 TB partitions) and then use gconcat to concatenate them into a bigger "JBOD-style" software RAID device. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 20:26:48 2009 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 7293A1065670 for ; Thu, 10 Sep 2009 20:26:48 +0000 (UTC) (envelope-from jbozza@mindsites.com) Received: from mail.thinkburst.com (mail.thinkburst.com [204.49.104.46]) by mx1.freebsd.org (Postfix) with ESMTP id 450F58FC1B for ; Thu, 10 Sep 2009 20:26:48 +0000 (UTC) Received: from mailgate.mindsites.net (gateway.mindsites.net [204.49.104.36]) by mail.thinkburst.com (Postfix) with ESMTP id 8C65D1CC24 for ; Thu, 10 Sep 2009 15:11:20 -0500 (CDT) Received: from remote.mindsites.com (unknown [10.1.1.5]) by mailgate.mindsites.net (Postfix) with ESMTP id 66EFD17040 for ; Thu, 10 Sep 2009 15:11:20 -0500 (CDT) Received: from ATLAS.msg.local ([fe80::48f5:88b0:6093:4f67]) by ATLAS.msg.local ([fe80::48f5:88b0:6093:4f67%10]) with mapi; Thu, 10 Sep 2009 15:11:20 -0500 From: Jaime Bozza To: "freebsd-stable@freebsd.org" Date: Thu, 10 Sep 2009 15:11:20 -0500 Thread-Topic: ZFS Boot/7.2-STABLE Thread-Index: AcoyUtyHhqnNnqgUQNClsWofRZUHbQ== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: ZFS Boot/7.2-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, 10 Sep 2009 20:26:48 -0000 After much work and looking at all the different configurations, I have a r= unning 7.2-STABLE (amd64) system running ZFS only with no partitions. Unf= ortunately, this required a couple of things. First - The patch here:=20 http://lists.freebsd.org/pipermail/freebsd-stable/2009-June/050518.html (just the patch to nfs.c - the other one is already in the tree) Next, I re-enabled ZFS support in /sys/boot/i386/Makefile Finally, I rebuilt and installed libstand, then rebuilt and installed the b= oot loader. Once I had those pieces, my ZFS-only system booted fine. =20 I've read the problems that caused the ZFS support to be backed out. Could= ZFS Boot (loader) support be something optional that isn't a default? Th= is would allow those who want to use ZFS Boot the ability without needing t= o move to 8.0 (which still isn't out officially). I'd have no problems rebuilding world to enable ZFS Boot on a new system, b= ut currently I'd have to remember to re-patch libstand and the loader Makef= ile each time I updated, or move to 8.0, which I'm not quite ready to do. = =20 At the very least, can someone MFC the libstand patch? The link above is b= asically the diff between 7.x and 8.x for the nfs.c file. Jaime Bozza From owner-freebsd-stable@FreeBSD.ORG Thu Sep 10 20:31:34 2009 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 5026710656AA; Thu, 10 Sep 2009 20:31:34 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id A19D18FC08; Thu, 10 Sep 2009 20:31:33 +0000 (UTC) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n8AKVuXk056518; Thu, 10 Sep 2009 15:31:56 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n8AKVuU7056517; Thu, 10 Sep 2009 15:31:56 -0500 (CDT) (envelope-from brooks) Date: Thu, 10 Sep 2009 15:31:56 -0500 From: Brooks Davis To: Ivan Voras Message-ID: <20090910203156.GA55545@lor.one-eyed-alien.net> References: <200909101404.n8AE41C6021588@svn.freebsd.org> <1252592951.49151.3.camel@buffy.york.ac.uk> <1252595839.75144.26.camel@bauer.cse.buffalo.edu> <9bbcef730909100836l3835825cy83082a2cfe4da0c3@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: <9bbcef730909100836l3835825cy83082a2cfe4da0c3@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Thu, 10 Sep 2009 15:31:57 -0500 (CDT) Cc: stable@FreeBSD.org, src-committers@FreeBSD.org, svn-src-stable@FreeBSD.org, svn-src-all@FreeBSD.org, Gavin Atkinson , svn-src-stable-8@FreeBSD.org, Ken Smith , Ken Smith Subject: Re: svn commit: r197065 - in stable/8: etc/defaults lib/libc/stdlib sys/amd64/conf sys/i386/conf sys/ia64/conf sys/pc98/conf sys/powerpc/conf sys/sparc64/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: Thu, 10 Sep 2009 20:31:34 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 10, 2009 at 05:36:56PM +0200, Ivan Voras wrote: > 2009/9/10 Ken Smith : > > On Thu, 2009-09-10 at 15:29 +0100, Gavin Atkinson wrote: >=20 > >> This seems like a step backwards to me: crash dumps have been left > >> enabled in 7.x and have proved very useful from the point of view of > >> improved quality of received PRs. ??I'm not aware of any problems > >> relating to leaving them enabled. > >> > >> I'd appreciate it if this decision was reconsidered. > >> > > > > Unfortunately as I said before there is no "Right answer" for this one. >=20 > No, but there is an "80% right" one, based on the question: did the > change in 7 cause known problems for any significant number of users > (or one of two big users - that should be enough). Given that we've shipped three releases with it this way we should have an answer here. If we can't identify real problem instances by now, there probably aren't significant ones in practice. IMO, we have always gone too far in disabling debugging. -- Brooks --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFKqWI7XY6L6fI4GtQRApVRAJ9lNRRakKrMBkKAk7k86/LTCDc8FgCglCMY UU+/Ic0xHH2niGUX7iXKafs= =Mye5 -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 00:23:48 2009 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 3EA581065672 for ; Fri, 11 Sep 2009 00:23:48 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 002EC8FC08 for ; Fri, 11 Sep 2009 00:23:47 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id 64A6F17EDF; Fri, 11 Sep 2009 10:25:21 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-45-252.lns10.syd7.internode.on.net [121.44.45.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 1EA6A17EC0; Fri, 11 Sep 2009 10:25:12 +1000 (EST) Message-ID: <4AA99819.9000601@modulus.org> Date: Fri, 11 Sep 2009 10:21:45 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Alban Hertroys References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: gconcat file system damage 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, 11 Sep 2009 00:23:48 -0000 How did you expand the filesystem onto the new volume? UFS2 expansion is not supported. > I originally created the concatted disk in two steps. First I created > the concat on my new mirrored disks and copied the files from my > existing mirror in there. Second I appended the existing mirror to my > concatted disk. It seemed to work fine, but now I'm seeing so much > errors that I can only mount the concat r/o! From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 01:14:55 2009 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 05AAD1065672 for ; Fri, 11 Sep 2009 01:14:55 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id D81BC8FC16 for ; Fri, 11 Sep 2009 01:14:54 +0000 (UTC) Received: from ldaemon.pldrouin.net (CPE0023695b905f-CM001a666aca96.cpe.net.cable.rogers.com [99.246.67.95]) by smtp.cyberfingers.net (Postfix) with ESMTP id 0928FAB6C10 for ; Thu, 10 Sep 2009 20:57:40 -0400 (EDT) Message-ID: <4AA9A07C.4050200@pldrouin.net> Date: Thu, 10 Sep 2009 20:57:32 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: How to enable CPU turbo mode on FreeBSD? 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, 11 Sep 2009 01:14:55 -0000 Hi, I have an overclocked i7 920 CPU for which I have enabled Turbo Mode in the BIOS (21x multiplier). The base clock is set at 190 MHz, so the CPU frequency with Turbo mode activated should be 3990 MHz. However the maximum value FreeBSD amd64 shows for the CPU frequency in dmesg and sysctl is 3790 MHz. How can I enable the Turbo Mode? CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (3790.52-MHz K8-class CPU) machdep.acpi_timer_freq: 3579545 machdep.tsc_freq: 3790522507 machdep.i8254_freq: 1193182 dev.cpu.0.freq: 349 dev.cpu.0.freq_levels: 2793/130000 2443/113750 2094/97500 1745/81250 1396/65000 1047/48750 698/32500 349/16250 Thanks! From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 01:25:08 2009 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 428FE1065670 for ; Fri, 11 Sep 2009 01:25:08 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 052918FC2E for ; Fri, 11 Sep 2009 01:25:07 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id 4541C17E52; Fri, 11 Sep 2009 11:26:41 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-45-252.lns10.syd7.internode.on.net [121.44.45.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 63A211725C; Fri, 11 Sep 2009 11:26:37 +1000 (EST) Message-ID: <4AA9A67F.6060800@modulus.org> Date: Fri, 11 Sep 2009 11:23:11 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: Pierre-Luc Drouin , freebsd-stable@freebsd.org References: <4AA9A07C.4050200@pldrouin.net> In-Reply-To: <4AA9A07C.4050200@pldrouin.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: How to enable CPU turbo mode on FreeBSD? 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, 11 Sep 2009 01:25:08 -0000 Pierre-Luc Drouin wrote: > I have an overclocked i7 920 CPU for which I have enabled Turbo Mode in > the BIOS (21x multiplier). The base clock is set at 190 MHz, so the CPU > frequency with Turbo mode activated should be 3990 MHz. However the > maximum value FreeBSD amd64 shows for the CPU frequency in dmesg and > sysctl is 3790 MHz. How can I enable the Turbo Mode? The turbo mode doesn't show up in dmesg or sysctl, it dynamically overclocks inside the CPU. Also, some motherboards silently disable turbo mode when you overclock the base clock. You may need to use a benchmark running on 1 vs 4 cores to see if turbo mode is having any effect. - Andrew From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 03:42:57 2009 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 2D3FA1065670 for ; Fri, 11 Sep 2009 03:42:57 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0716D8FC20 for ; Fri, 11 Sep 2009 03:42:56 +0000 (UTC) Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com [70.86.141.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hedwig.simons-rock.edu (Postfix) with ESMTP id 86A802BB343; Thu, 10 Sep 2009 23:42:55 -0400 (EDT) Date: Thu, 10 Sep 2009 23:42:53 -0400 From: "Peter C. Lai" To: Andrew Snow Message-ID: <20090911034253.GM81123@cesium.hyperfine.info> References: <15274_1252628653_4AA998AD_15274_284_1_4AA99819.9000601@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15274_1252628653_4AA998AD_15274_284_1_4AA99819.9000601@modulus.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: gconcat file system damage 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, 11 Sep 2009 03:42:57 -0000 What is the status of growfs(8) then? On 2009-09-11 10:21:45AM +1000, Andrew Snow wrote: > > > How did you expand the filesystem onto the new volume? UFS2 expansion is > not supported. > >> I originally created the concatted disk in two steps. First I created the >> concat on my new mirrored disks and copied the files from my existing >> mirror in there. Second I appended the existing mirror to my concatted >> disk. It seemed to work fine, but now I'm seeing so much errors that I can >> only mount the concat r/o! > > _______________________________________________ > 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" -- =========================================================== Peter C. Lai | Bard College at Simon's Rock Systems Administrator | 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 =========================================================== From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 03:47:04 2009 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 DB962106566C for ; Fri, 11 Sep 2009 03:47:04 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 9BFF88FC0A for ; Fri, 11 Sep 2009 03:47:04 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id 5588517EA5; Fri, 11 Sep 2009 13:48:38 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (ppp121-44-45-252.lns10.syd7.internode.on.net [121.44.45.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 5A83F17DB1; Fri, 11 Sep 2009 13:48:34 +1000 (EST) Message-ID: <4AA9C7C3.1000007@modulus.org> Date: Fri, 11 Sep 2009 13:45:07 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: "Peter C. Lai" References: <15274_1252628653_4AA998AD_15274_284_1_4AA99819.9000601@modulus.org> <20090911034253.GM81123@cesium.hyperfine.info> In-Reply-To: <20090911034253.GM81123@cesium.hyperfine.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: gconcat file system damage 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, 11 Sep 2009 03:47:04 -0000 Peter C. Lai wrote: > What is the status of growfs(8) then? As far as I can tell, it doesn't work reliably with UFS2 partitions, and it doesn't work at all with large partitions. People who do try to use it, can end up with corrupted filesystems... and the code is currently unmaintained. - Andrew From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 07:01:24 2009 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 4F46A106568B for ; Fri, 11 Sep 2009 07:01:24 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [66.246.138.153]) by mx1.freebsd.org (Postfix) with ESMTP id E87B08FC12 for ; Fri, 11 Sep 2009 07:01:23 +0000 (UTC) Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id B9C8E81C4; Fri, 11 Sep 2009 06:41:25 +0000 (UTC) Date: Fri, 11 Sep 2009 07:41:23 +0100 From: Bruce Cran To: Pierre-Luc Drouin Message-ID: <20090911074123.00006179@unknown> In-Reply-To: <4AA9A07C.4050200@pldrouin.net> References: <4AA9A07C.4050200@pldrouin.net> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to enable CPU turbo mode on FreeBSD? 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, 11 Sep 2009 07:01:24 -0000 On Thu, 10 Sep 2009 20:57:32 -0400 Pierre-Luc Drouin wrote: > Hi, > > I have an overclocked i7 920 CPU for which I have enabled Turbo Mode > in the BIOS (21x multiplier). The base clock is set at 190 MHz, so > the CPU frequency with Turbo mode activated should be 3990 MHz. > However the maximum value FreeBSD amd64 shows for the CPU frequency > in dmesg and sysctl is 3790 MHz. How can I enable the Turbo Mode? > > CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (3790.52-MHz > K8-class CPU) > > machdep.acpi_timer_freq: 3579545 > machdep.tsc_freq: 3790522507 > machdep.i8254_freq: 1193182 > dev.cpu.0.freq: 349 > dev.cpu.0.freq_levels: 2793/130000 2443/113750 2094/97500 1745/81250 > 1396/65000 1047/48750 698/32500 349/16250 You may be able to use the cpuctl kernel module with sysutils/x86info to see when the CPUs are using Turbo mode. I haven't had any success yet but I know in Windows the System control panel reported the 2.66GHz CPU running at 2.83GHz without me doing anything, so I guess FreeBSD should be doing the same. -- Bruce Cran From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 08:07:05 2009 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 0FB78106566C for ; Fri, 11 Sep 2009 08:07:05 +0000 (UTC) (envelope-from sagara@tomahawk.com.sg) Received: from us1.tomahawkonline.net (us1.tomahawkonline.net [66.98.178.56]) by mx1.freebsd.org (Postfix) with SMTP id C81B88FC18 for ; Fri, 11 Sep 2009 08:07:04 +0000 (UTC) Received: (qmail 18409 invoked from network); 11 Sep 2009 04:46:26 -0000 Received: from 219.74.14.147 (HELO tdsblack.lan) (sagara@tomahawk.com.sg@219.74.14.147) by us1.tomahawkonline.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Sep 2009 04:46:26 -0000 Message-ID: <4AAA0580.10400@tomahawk.com.sg> Date: Fri, 11 Sep 2009 16:08:32 +0800 From: Sagara Wijetunga User-Agent: Thunderbird 2.0.0.22 (X11/20090703) MIME-Version: 1.0 To: John Baldwin References: <4AA8EBBD.5020709@tomahawk.com.sg> <4AA8EC4D.3080800@andric.com> <4AA90F9F.6080702@tomahawk.com.sg> <200909101132.43781.jhb@freebsd.org> In-Reply-To: <200909101132.43781.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Roland Smith , Dimitry Andric , freebsd-stable@freebsd.org Subject: Re: Avahi compilation help needed 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, 11 Sep 2009 08:07:05 -0000 John Baldwin wrote: > The avahi ports can still be useful to look at as they contain patches that > you will probably need. For example, net/avahi-app has a patch against the > configure script in files/patch-configure. In total it seems that > net/avahi-app has 21 different patches to the avahi sources (you may not need > all of them however). I would start by looking at those. > Here is the procedure we tried: Create system users and groups to handle Avahi daemons: - Create "avahid" for running avahi-daemon - Create "avahi-autoipd" for running the avahi-autoipd daemon Get FreeBSD patches: mkdir files cd files cp -v /sources/avahi/* . cd .. tar xzf avahi-0.6.25.tar.gz cd avahi-0.6.25 Apply FreeBSD patches: patch -Np0 -i ../files/patch-Makefile.in patch -Np0 -i ../files/patch-avahi-autoipd_main.c patch -Np0 -i ../files/patch-avahi-client.pc.in patch -Np0 -i ../files/patch-avahi-compat-howl.pc.in patch -Np0 -i ../files/patch-avahi-compat-libdns_sd.pc.in patch -Np0 -i ../files/patch-avahi-compat-libdns_sd_Makefile.in patch -Np0 -i ../files/patch-avahi-core.pc.in patch -Np0 -i ../files/patch-avahi-daemon_Makefile.in patch -Np0 -i ../files/patch-avahi-daemon_main.c patch -Np0 -i ../files/patch-avahi-discover-standalone_Makefile.in patch -Np0 -i ../files/patch-avahi-glib.pc.in patch -Np0 -i ../files/patch-avahi-qt4.pc.in patch -Np0 -i ../files/patch-avahi-qt_Makefile.in patch -Np0 -i ../files/patch-avahi-ui_Makefile.in patch -Np0 -i ../files/patch-avahi-utils_Makefile.in patch -Np0 -i ../files/patch-configure patch -Np0 -i ../files/patch-dnsconfd_Makefile.in patch -Np0 -i ../files/patch-initscript_freebsd_Makefile.in Check after patching for any rejection: find . -name "*.rej" -exec echo {} \; No rejections sed -i '' -e 's|-ldl||g ; s|netdev|network|g' \ configure \ avahi-client/Makefile.in \ avahi-daemon/Makefile.in find . -name Makefile.in | /usr/bin/xargs \ sed -i '' -e 's|(LIBINTL)|(INTLLIBS)|g ; s|(LIBICONV)|(LTLIBICONV)|g' ### sed -i '' -e 's|%%RC_SUBR%%|${RC_SUBR}| ; \ s|%%GNOME_SUBR%%|${GNOME_SUBR}|' \ initscript/freebsd/avahi-dnsconfd.sh.in \ initscript/freebsd/avahi-daemon.sh.in sed -i '' -e 's|dbus_connection_disconnect|dbus_connection_close|g' \ avahi-client/client.c \ avahi-daemon/dbus-protocol.c sed -i '' -e 's|^_||g' \ avahi-ui/*.desktop.in.in sed -i '' -e 's|-lavahi-common||g' \ avahi-qt/Makefile.in avahi-qt/Makefile CPPFLAGS="-DHAVE_KQUEUE" PTHREAD_CFLAGS="" PTHREAD_LIBS="-pthread" \ ./configure --prefix=/usr --sysconfdir=/etc \ --infodir=/usr/share/info --mandir=/usr/share/man --localstatedir=/var \ --with-distro=freebsd --with-dbus-sys=/etc/dbus-1/system.d \ --with-dbus-system-socket=unix:path=/var/run/dbus/system_bus_socket \ --with-avahi-user=avahid --with-avahi-group=avahid \ --with-avahi-priv-access-group=network --enable-compat-libdns_sd \ --disable-qt3 --disable-mono --disable-monodoc gmake >& avahi-make.log We appreciate if someone could try and let us know. Kind regards Sagara From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 08:57:26 2009 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 004A7106566B for ; Fri, 11 Sep 2009 08:57:25 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id A95638FC26 for ; Fri, 11 Sep 2009 08:57:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 9C40F8035 for ; Fri, 11 Sep 2009 10:57:24 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 07EB88034; Fri, 11 Sep 2009 10:57:23 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1075.2) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Alban Hertroys In-Reply-To: <4AA9C7C3.1000007@modulus.org> Date: Fri, 11 Sep 2009 10:57:22 +0200 Content-Transfer-Encoding: 7bit Message-Id: <0853758B-4823-49B8-B63E-B5B72FE2661B@solfertje.student.utwente.nl> References: <15274_1252628653_4AA998AD_15274_284_1_4AA99819.9000601@modulus.org> <20090911034253.GM81123@cesium.hyperfine.info> <4AA9C7C3.1000007@modulus.org> To: Andrew Snow X-Mailer: Apple Mail (2.1075.2) X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri Sep 11 10:57:24 2009 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 74,4aaa10f412071914714074 X-DSPAM-Factors: 27, Cc*, freebsd-stable@freebsd.org Subject: Re: gconcat file system damage 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, 11 Sep 2009 08:57:26 -0000 On 11 Sep 2009, at 5:45, Andrew Snow wrote: > Peter C. Lai wrote: >> What is the status of growfs(8) then? > > As far as I can tell, it doesn't work reliably with UFS2 partitions, > and it doesn't work at all with large partitions. > > People who do try to use it, can end up with corrupted > filesystems... and the code is currently unmaintained. Aha, I forgot about that step, but I did indeed use growfs to expand it. Is there any way to repair the corruption without erasing my data, or do I need to buy an external disk to backup to first (which I need for backups anyway)? If so, what's the pattern of the corruption? Is it likely to only start after a certain size? Lastly, having a tool in the base system that causes these kinds of issues doesn't seem like a very good idea. growfs does issue a warning that made me read the bugs section in the man page. That section points to an ffsinfo command that I ran on the filesystem in question, but it appears to be alright: ===== START CYLINDER SUMMARY ===== # 0@28202000: 0. csum in fscs ndir int32_t 0x00000001 nbfree int32_t 0x00002474 nifree int32_t 0x00005bfd nffree int32_t 0x0000000d ===== END CYLINDER SUMMARY ===== The filesystem is 740G, which seems to fit in the 'critical data structure'; 1480 < 0x2474... Or is this a different (and undocumented) issue? Alban Hertroys -- Screwing up is the best way to attach something to the ceiling. !DSPAM:74,4aaa10f412071914714074! From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 09:24:00 2009 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 9CE5C106566B for ; Fri, 11 Sep 2009 09:24:00 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from electron.sasknet.sk.ca (electron.sasknet.sk.ca [142.165.20.179]) by mx1.freebsd.org (Postfix) with ESMTP id 633368FC0C for ; Fri, 11 Sep 2009 09:24:00 +0000 (UTC) Received: from pps.filterd (electron [127.0.0.1]) by electron.sasknet.sk.ca (8.14.3/8.14.3) with SMTP id n8B94Psn014590 for ; Fri, 11 Sep 2009 03:04:25 -0600 Received: from bgmpomr1.sasknet.sk.ca (bgmpOMR1.sasknet.sk.ca [142.165.72.22]) by electron.sasknet.sk.ca with ESMTP id gqf2wkv8f-1 for ; Fri, 11 Sep 2009 03:04:24 -0600 Received: from ace.hurd.local (outgoing.bbsdev.net [76.202.204.46]) by bgmpomr1.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0KPS00JA0UJAFJ00@bgmpomr1.sasknet.sk.ca> for freebsd-stable@freebsd.org; Fri, 11 Sep 2009 03:04:24 -0600 (CST) Date: Fri, 11 Sep 2009 02:04:22 -0700 From: Stephen Hurd To: freebsd-stable@freebsd.org Message-id: <4AAA1296.2080705@sasktel.net> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_KuCCCBoiTOKWcjrQkN2jGw)" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.22) Gecko/20090810 SeaMonkey/1.1.17 Mnenhy/0.7.6.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-09-11_04:2009-09-01, 2009-09-11, 2009-09-11 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_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-0908210000 definitions=main-0909110015 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 8.0-B4 gstripe / GEOM_PART_* upgrade woes 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, 11 Sep 2009 09:24:00 -0000 This is a multi-part message in MIME format. --Boundary_(ID_KuCCCBoiTOKWcjrQkN2jGw) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT I've upgraded from 7.2-RELEASE_p2 to 8.0-BETA4 and using GEOM_PART_* with my sliced gstripe array causes the /dev/stripe/raid0a to disappear and the reset of the /dev/stripe/raid0[a-z] file systems to be unmountable. My gvinum array is still working fine and, after chasing the ad* slices, they can be mounted as well. It's just the gstripe slices which are corrupt/missing. When I build without GEOM_PART_* and use GEOM_BSD and GEOM_MBR, it works fine. I've attached an archive with various command outputs which may be helpfull... the 8.0 directory is 8.0 with GEOM_PART_* and 8.0-OLD is using GEOM_BSD and GEOM_MBR. I'll paste the 8.0 ones in here in case attachments are stripped: =========== dmesg ============== Copyright (c) 1992-2009 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.0-BETA4 #0: Thu Sep 10 17:00:11 PDT 2009 admin@ace.hurd.local:/tmp/obj/usr/src/sys/ACE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2394.77-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Features2=0x4400 real memory = 1342013440 (1279 MB) avail memory = 1299419136 (1239 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 2 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP/HT): APIC ID: 7 MADT: Forcing active-low polarity and level trigger for SCI ioapic2 irqs 32-47 on motherboard ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard kbd1 at kbdmux0 smbios0: at iomem 0xfdfe0-0xfdffe on motherboard smbios0: Version: 2.3, BCD Revision: 2.3 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 460, 2 (4) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 pcib0: on acpi0 pci0: on pcib0 pcm0: port 0x2200-0x223f irq 16 at device 1.0 on pci0 pcm0: pcm0: [ITHREAD] pcm0: vgapci0: port 0x2300-0x23ff mem 0xfd000000-0xfdffffff,0xfebff000-0xfebfffff irq 26 at device 9.0 on pci0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] Initialized mach64 2.0.0 20060718 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x700-0x70f at device 15.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] ohci0: mem 0xfebfe000-0xfebfefff irq 11 at device 15.2 on pci0 ohci0: [ITHREAD] usbus0: on ohci0 isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on acpi0 pci2: on pcib1 bge0: mem 0xfbff0000-0xfbffffff irq 29 at device 8.0 on pci2 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:02:55:07:57:03 bge0: [ITHREAD] pcib2: on acpi0 pci5: on pcib2 mpt0: port 0x2400-0x24ff mem 0xf9ff0000-0xf9ffffff,0xf9fe0000-0xf9feffff irq 27 at device 7.0 on pci5 mpt0: [ITHREAD] mpt0: MPI Version=1.2.15.0 mpt0: Capabilities: ( RAID-1 SAFTE ) mpt0: 0 Active Volumes (1 Max) mpt0: 0 Hidden Drive Members (6 Max) mpt1: port 0x2500-0x25ff mem 0xf9fd0000-0xf9fdffff,0xf9fc0000-0xf9fcffff irq 28 at device 7.1 on pci5 mpt1: [ITHREAD] mpt1: MPI Version=1.2.15.0 mpt1: Capabilities: ( RAID-1 SAFTE ) mpt1: 0 Active Volumes (1 Max) mpt1: 0 Hidden Drive Members (6 Max) pcib3: on acpi0 pci7: on pcib3 pcib4: on acpi0 pci9: on pcib4 fdc0: port 0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atrtc0: port 0x70-0x73 irq 8 on acpi0 cpu0: on acpi0 p4tcc0: on cpu0 cpu1: on acpi0 p4tcc1: on cpu1 cpu2: on acpi0 p4tcc2: on cpu2 cpu3: on acpi0 p4tcc3: on cpu3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppc0: [ITHREAD] ppbus0: on ppc0 lpt0: on ppbus0 lpt0: [ITHREAD] lpt0: Interrupt-driven port Timecounters tick every 0.838 msec ipfw2 (+ipv6) initialized, divert enabled, nat loadable, rule-based forwarding disabled, default to deny, logging disabled Waiting 5 seconds for SCSI devices to settle usbus0: 12Mbps Full Speed USB v1.0 driver bug: Unable to set devclass (devname: (null)) ad0: 305245MB at ata0-master UDMA100 ugen0.1: <(0x1166)> at usbus0 uhub0: <(0x1166) OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0 acd0: CDRW at ata0-slave UDMA33 uhub0: 4 ports with 4 removable, self powered ugen0.2: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0000 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 (probe0:mpt0:0:8:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:mpt0:0:8:0): CAM Status: SCSI Status Error (probe0:mpt0:0:8:0): SCSI Status: Check Condition (probe0:mpt0:0:8:0): UNIT ATTENTION asc:29,0 (probe0:mpt0:0:8:0): Power on, reset, or bus device reset occurred (probe0:mpt0:0:8:0): Retrying Command (per Sense Data) umass0:5:0:-1: Attached to scbus5 (probe2:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe2:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe2:umass-sim0:0:0:0): SCSI Status: Check Condition (probe2:umass-sim0:0:0:0): UNIT ATTENTION asc:29,0 (probe2:umass-sim0:0:0:0): Power on, reset, or bus device reset occurred (probe2:umass-sim0:0:0:0): Retrying Command (per Sense Data) (probe2:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe2:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe2:umass-sim0:0:0:0): SCSI Status: Check Condition (probe2:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe2:umass-sim0:0:0:0): Medium not present (probe2:umass-sim0:0:0:0): Unretryable error cd0 at ata0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [3315 x 2048 byte records] ses0 at mpt0 bus 0 target 8 lun 0 ses0: Fixed Processor SCSI-2 device ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) da0: Command Queueing enabled da0: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) da1 at mpt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) da1: Command Queueing enabled da1: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) da2 at mpt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) da2: Command Queueing enabled da2: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) da3 at mpt0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) da3: Command Queueing enabled da3: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! da4 at umass-sim0 bus 0 target 0 lun 0 da4: Removable Direct Access SCSI-2 device da4: 1.000MB/s transfers da4: Attempt to query device size failed: NOT READY, Medium not presentSMP: AP CPU #2 Launched! GEOM: ad0: geometry does not match label (255h,63s != 16h,63s). acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 GEOM_STRIPE: Device raid0 created (id=40432321). GEOM_STRIPE: Disk da0s2 attached to raid0. GEOM_STRIPE: Disk da1s2 attached to raid0. GEOM_STRIPE: Disk da2s2 attached to raid0. GEOM_STRIPE: Disk da3s2 attached to raid0. GEOM_STRIPE: Device raid0 activated. Trying to mount root from ufs:/dev/da0s1a <<111188>C>aCna'tn 'stta ts t/atd e/vd/aedv0s/1sgt:ri pNeo/ rsuacidh0 af:i lNeo sour directory c =========== END OF dmesg =========== =========== gstripe list =========== Geom name: raid0 State: UP Status: Total=4, Online=4 Type: AUTOMATIC Stripesize: 262144 ID: 40432321 Providers: 1. Name: stripe/raid0 Mediasize: 42934992896 (40G) Sectorsize: 512 Mode: r0w0e0 Consumers: 1. Name: da0s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r0w0e0 Number: 0 2. Name: da1s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r0w0e0 Number: 1 3. Name: da2s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r0w0e0 Number: 2 4. Name: da3s2 Mediasize: 10733990400 (10G) Sectorsize: 512 Mode: r0w0e0 Number: 3 =========== END OF gstripe list =========== =========== gstripe status =========== Name Status Components stripe/raid0 UP da0s2 da1s2 da2s2 da3s2 =========== END OF gstripe status =========== --Boundary_(ID_KuCCCBoiTOKWcjrQkN2jGw)-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 10:21:49 2009 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 D4C1D1065670 for ; Fri, 11 Sep 2009 10:21:49 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 652CC8FC12 for ; Fri, 11 Sep 2009 10:21:48 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1Mm3GF-0004Dy-O9 for freebsd-stable@freebsd.org; Fri, 11 Sep 2009 12:21:47 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Sep 2009 12:21:47 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Sep 2009 12:21:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Fri, 11 Sep 2009 12:21:39 +0200 Lines: 77 Message-ID: References: <4AAA1296.2080705@sasktel.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.22 (X11/20090817) In-Reply-To: <4AAA1296.2080705@sasktel.net> Sender: news Subject: Re: 8.0-B4 gstripe / GEOM_PART_* upgrade woes 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, 11 Sep 2009 10:21:49 -0000 Stephen Hurd wrote: > I've upgraded from 7.2-RELEASE_p2 to 8.0-BETA4 and using GEOM_PART_* > with my sliced gstripe array causes the /dev/stripe/raid0a to disappear > and the reset of the /dev/stripe/raid0[a-z] file systems to be unmountable. > > My gvinum array is still working fine and, after chasing the ad* slices, > they can be mounted as well. It's just the gstripe slices which are > corrupt/missing. Ouch. > GEOM_STRIPE: Device raid0 created (id=40432321). > GEOM_STRIPE: Disk da0s2 attached to raid0. > GEOM_STRIPE: Disk da1s2 attached to raid0. > GEOM_STRIPE: Disk da2s2 attached to raid0. > GEOM_STRIPE: Disk da3s2 attached to raid0. > GEOM_STRIPE: Device raid0 activated. > Trying to mount root from ufs:/dev/da0s1a > <<111188>C>aCna'tn 'stta ts t/atd e/vd/aedv0s/1sgt:ri pNeo/ rsuacidh0 > af:i lNeo sour directory > c > =========== END OF dmesg =========== > > =========== gstripe list =========== > Geom name: raid0 > State: UP > Status: Total=4, Online=4 > Type: AUTOMATIC > Stripesize: 262144 > ID: 40432321 > Providers: > 1. Name: stripe/raid0 > Mediasize: 42934992896 (40G) > Sectorsize: 512 > Mode: r0w0e0 > Consumers: > 1. Name: da0s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 0 > 2. Name: da1s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 1 > 3. Name: da2s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 2 > 4. Name: da3s2 > Mediasize: 10733990400 (10G) > Sectorsize: 512 > Mode: r0w0e0 > Number: 3 > =========== END OF gstripe list =========== > > =========== gstripe status =========== > Name Status Components > stripe/raid0 UP da0s2 > da1s2 > da2s2 > da3s2 > =========== END OF gstripe status =========== > When I build without GEOM_PART_* and use GEOM_BSD and GEOM_MBR, it works > fine. An interesting problem. I presume that in either case (gpart or GEOM_BSD/MBR) the output of "gstripe status" is the same? Only the interpretation of the partition tables is problematic? What is the expected ("good") structure of the partitions/file systems? Do you have a single MBR partition and inside it multiple BSD partitions? What are their partition types? From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 13:25:21 2009 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 10E84106566B for ; Fri, 11 Sep 2009 13:25:21 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 95ECA8FC12 for ; Fri, 11 Sep 2009 13:25:20 +0000 (UTC) Received: by bwz2 with SMTP id 2so730977bwz.43 for ; Fri, 11 Sep 2009 06: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:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=gzymYmwVRs26jyze/8CR6IvuEGsaUvb4R7F4lnyYS+k=; b=VDCSrSATh5JoySq9JwIGft50f7FFmrw6+oq4mWR3pijp6e3Erri+IQBPcKFW5MsyBs tzDIDtVddhXg1j6wx/dT3KH3Io1zLbyp37PXqvNggEJFw61e1iNCGoClpfEBzVZVgqsu DGeNFP9mnPF5mSFruKeuRLMP2Mqk/z2d+wvtE= 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=rU9rCOj8sgfwz4iaYmadbX2+LJYwksqbR4JkIiLJah90e+kX/acNlZ01vsNhpuOEIu touq/l+tQ8rAUEaq994bpFC4iznLucUXK3Zfr8Qut0drxMonyp0HZeDOpX5H8HRlNDe7 j8LliJiSMO6l/R8xBgwLFamrbESUn6XTIs250= MIME-Version: 1.0 Received: by 10.204.154.154 with SMTP id o26mr2028107bkw.107.1252674081769; Fri, 11 Sep 2009 06:01:21 -0700 (PDT) In-Reply-To: <4AA90D88.4010004@eng.auth.gr> References: <4AA90D88.4010004@eng.auth.gr> Date: Fri, 11 Sep 2009 16:01:21 +0300 Message-ID: <9e20d71e0909110601kaa87f2em2e4e618b8feb306b@mail.gmail.com> From: Artis Caune To: George Mamalakis Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 11 Sep 2009 13:25:21 -0000 2009/9/10 George Mamalakis : > Hello everybody, > > Yesterday I installed FreeBSD 8.0-BETA4 on an IBM 3650, having a ServerRaid > 8k adapter, and 6 sata disks on raid-6. > .... > aac0: COMMAND 0xffffff80003e08a0 TIMEOUT AFTER 40 SECONDS > aac0: COMMAND 0xffffff80003d5070 TIMEOUT AFTER 40 SECONDS > aac0: COMMAND 0xffffff80003e0d00 TIMEOUT AFTER 40 SECONDS > aac0: COMMAND 0xffffff80003d9440 TIMEOUT AFTER 40 SECONDS > .... > > ...and kept on like that, for many many lines, with decreasing timeouts. > Once the syncing process stopped, everything came back to normal (not that I > have stress-tested the machine, to be honest...). But since it happened > once, during this specific procedure, then maybe it could also happen when > the raid controller is reconstructing its volumes; and this would be very > annoying, as far as the server's efficiency (and/or maybe stability) is > concerned. Same problem here, thought we got timeouts also on idle boxes. IBM support told to switch controller channel speed from auto(3Gbps) to 1.5Gbps and update ServeRaid firmware. We are currently running 5.2.0-15429 (flashing them almost monthly :) ). You can change speed in raid bios, in Ctrl-A menu. But this issue is only with sata disks, sas works perfectly. -- Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 15:05:32 2009 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 CA57C1065672 for ; Fri, 11 Sep 2009 15:05:32 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id A6CBC8FC1C for ; Fri, 11 Sep 2009 15:05:32 +0000 (UTC) Received: from mdaemon.pldrouin.net (CPE0023695b905f-CM001a666aca96.cpe.net.cable.rogers.com [99.246.67.95]) by smtp.cyberfingers.net (Postfix) with ESMTP id CA8C2AB6C5B for ; Fri, 11 Sep 2009 11:05:31 -0400 (EDT) Message-ID: <4AAA6755.7070502@pldrouin.net> Date: Fri, 11 Sep 2009 11:05:57 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.23 (X11/20090824) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4AA9A07C.4050200@pldrouin.net> <20090911074123.00006179@unknown> In-Reply-To: <20090911074123.00006179@unknown> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: How to enable CPU turbo mode on FreeBSD? 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, 11 Sep 2009 15:05:32 -0000 Bruce Cran wrote: > On Thu, 10 Sep 2009 20:57:32 -0400 > Pierre-Luc Drouin wrote: > > >> Hi, >> >> I have an overclocked i7 920 CPU for which I have enabled Turbo Mode >> in the BIOS (21x multiplier). The base clock is set at 190 MHz, so >> the CPU frequency with Turbo mode activated should be 3990 MHz. >> However the maximum value FreeBSD amd64 shows for the CPU frequency >> in dmesg and sysctl is 3790 MHz. How can I enable the Turbo Mode? >> >> CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (3790.52-MHz >> K8-class CPU) >> >> machdep.acpi_timer_freq: 3579545 >> machdep.tsc_freq: 3790522507 >> machdep.i8254_freq: 1193182 >> dev.cpu.0.freq: 349 >> dev.cpu.0.freq_levels: 2793/130000 2443/113750 2094/97500 1745/81250 >> 1396/65000 1047/48750 698/32500 349/16250 >> > > You may be able to use the cpuctl kernel module with sysutils/x86info > to see when the CPUs are using Turbo mode. I haven't had any success > yet but I know in Windows the System control panel reported the 2.66GHz > CPU running at 2.83GHz without me doing anything, so I guess FreeBSD > should be doing the same. > > So I managed to test that the Turbo Mode is working. Here is how I tested it, if it can be useful for other people in the future: I wrote this very dumb program in C (compiled using gcc -lpthread -o test test.c): #include #include #include int main(int nargs, char* args[]); void* floop(void* args); long long int niters; int main(int nargs, char* args[]) { int nthrs; int i; pthread_t *threads; --nargs; ++args; if(nargs!=2) { fprintf(stderr,"Usage: loop nthreads niters\n"); return 1; } sscanf(args[0],"%i",&nthrs); sscanf(args[1],"%lli",&niters); printf("Number of threads: %i\n",nthrs); printf("Number of iterations: %lli\n",niters); threads=(pthread_t*)malloc(nthrs*sizeof(pthread_t)); for(i=nthrs-1; i>=0; --i) pthread_create(threads+i,NULL,floop,NULL); for(i=nthrs-1; i>=0; --i) pthread_join(threads[i],NULL); free(threads); return 0; } void* floop(void* args){ long long int i; for(i=niters-1; i>=0; --i); return NULL; } I ran it with 8 threads and 150 000 000 000 iterations/threads using time ./test 8 150000000000 I got a user time of 1827.24 sec with turbo and 1908.69 sec without, a 4.5% speed difference, which is pretty close to the expected 5% (1-21/20 where 21/20 is the ratio of CPU multipliers with and without turbo for my i7 920 CPU) From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 15:19:28 2009 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 D1720106566B for ; Fri, 11 Sep 2009 15:19:28 +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 A4C878FC1B for ; Fri, 11 Sep 2009 15:19:28 +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 567C446B23; Fri, 11 Sep 2009 11:19:28 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 8F6A08A01F; Fri, 11 Sep 2009 11:19:27 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Fri, 11 Sep 2009 11:05:01 -0400 User-Agent: KMail/1.9.7 References: <4AA9A07C.4050200@pldrouin.net> In-Reply-To: <4AA9A07C.4050200@pldrouin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909111105.01619.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 11 Sep 2009 11:19:27 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Pierre-Luc Drouin Subject: Re: How to enable CPU turbo mode on FreeBSD? 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, 11 Sep 2009 15:19:28 -0000 On Thursday 10 September 2009 8:57:32 pm Pierre-Luc Drouin wrote: > Hi, > > I have an overclocked i7 920 CPU for which I have enabled Turbo Mode in > the BIOS (21x multiplier). The base clock is set at 190 MHz, so the CPU > frequency with Turbo mode activated should be 3990 MHz. However the > maximum value FreeBSD amd64 shows for the CPU frequency in dmesg and > sysctl is 3790 MHz. How can I enable the Turbo Mode? > > CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (3790.52-MHz > K8-class CPU) > > machdep.acpi_timer_freq: 3579545 > machdep.tsc_freq: 3790522507 > machdep.i8254_freq: 1193182 > dev.cpu.0.freq: 349 > dev.cpu.0.freq_levels: 2793/130000 2443/113750 2094/97500 1745/81250 > 1396/65000 1047/48750 698/32500 349/16250 You have to enable C2/C3 sleep states (possibly in your BIOS). However, FreeBSD doesn't currently handle this but so well since that will probably turn off the local APIC timer interrupt when the CPU is idle causing FreeBSD to miss clock interrupts. -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 15:26:39 2009 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 2441D106566C for ; Fri, 11 Sep 2009 15:26:39 +0000 (UTC) (envelope-from doug@polands.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.123]) by mx1.freebsd.org (Postfix) with ESMTP id DA4F38FC12 for ; Fri, 11 Sep 2009 15:26:38 +0000 (UTC) Received: from haran.polands.org ([75.87.219.217]) by hrndva-omta01.mail.rr.com with ESMTP id <20090911151122661.OPVX11562@hrndva-omta01.mail.rr.com> for ; Fri, 11 Sep 2009 15:11:22 +0000 Received: from email.polands.org (ammon.polands.org [172.16.1.7]) by haran.polands.org (8.14.3/8.14.3) with ESMTP id n8BFBLIP077144 for ; Fri, 11 Sep 2009 10:11:21 -0500 (CDT) (envelope-from doug@polands.org) Received: from 209.103.215.99 (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Fri, 11 Sep 2009 10:11:22 -0500 Message-ID: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> Date: Fri, 11 Sep 2009 10:11:22 -0500 From: "Doug Poland" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: NFS issues on 8.0-BETA4 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, 11 Sep 2009 15:26:39 -0000 Hello, I have a 7.2-RELEASE(i386) server hosting NFSv3. I've installed 8.0-BETA4(amd64) in a VMware 6.5 workstation virtual machine. I cannot sucessfully mount exports from the NFSv3 server on the 8.0-BETA4 client. All works well with 7.2 clients. The strange thing is, the directory in which I mount the nfs filesystem disappears, and I get an error when I attempt to access the directory. On working the server, I set these knobs in /etc/rc.conf: mountd_flags="-l" nfs_reserved_port_only="NO" nfs_server_enable="YES" nfs_server_flags="-u -n 6" rpc_lockd_enable="YES" rpc_statd_enable="YES" On the client, I set these knobs in /etc/rc.conf: nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" client# mount -t nfs -o nfsv3,retrycnt=3,intr,soft,rsize=32768,wsize=32768 fs:/usr/ports /usr/ports I get a long delay (several seconds) client# echo $? 0 client# ls /usr/ports ls: /usr/ports: Permission denied client# echo $? 1 client# mount -t nfs fs:/usr/ports on /usr/ports (nfs) client# umount /usr/ports client# ls -ld /usr/ports drwxr-xr-x 2 root wheel 512 Sep 11 08:54 /usr/ports If I simplify the mount command, I get a different error: client# mount -t nfs fs:/usr/ports /usr/ports mount: /usr/ports: Permission denied client# echo $? 64 client# mount -t nfs fs:/usr/ports on /usr/ports (nfs) Any suggestions? -- Regards, Doug From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 15:45:49 2009 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 0C255106566B for ; Fri, 11 Sep 2009 15:45:49 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id DA5E78FC2B for ; Fri, 11 Sep 2009 15:45:48 +0000 (UTC) Received: from mdaemon.pldrouin.net (CPE0023695b905f-CM001a666aca96.cpe.net.cable.rogers.com [99.246.67.95]) by smtp.cyberfingers.net (Postfix) with ESMTP id 18610AB6C6F; Fri, 11 Sep 2009 11:45:47 -0400 (EDT) Message-ID: <4AAA70C5.5090408@pldrouin.net> Date: Fri, 11 Sep 2009 11:46:13 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.23 (X11/20090824) MIME-Version: 1.0 To: John Baldwin References: <4AA9A07C.4050200@pldrouin.net> <200909111105.01619.jhb@freebsd.org> In-Reply-To: <200909111105.01619.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to enable CPU turbo mode on FreeBSD? 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, 11 Sep 2009 15:45:49 -0000 John Baldwin wrote: > On Thursday 10 September 2009 8:57:32 pm Pierre-Luc Drouin wrote: > >> Hi, >> >> I have an overclocked i7 920 CPU for which I have enabled Turbo Mode in >> the BIOS (21x multiplier). The base clock is set at 190 MHz, so the CPU >> frequency with Turbo mode activated should be 3990 MHz. However the >> maximum value FreeBSD amd64 shows for the CPU frequency in dmesg and >> sysctl is 3790 MHz. How can I enable the Turbo Mode? >> >> CPU: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (3790.52-MHz >> K8-class CPU) >> >> machdep.acpi_timer_freq: 3579545 >> machdep.tsc_freq: 3790522507 >> machdep.i8254_freq: 1193182 >> dev.cpu.0.freq: 349 >> dev.cpu.0.freq_levels: 2793/130000 2443/113750 2094/97500 1745/81250 >> 1396/65000 1047/48750 698/32500 349/16250 >> > > You have to enable C2/C3 sleep states (possibly in your BIOS). However, > FreeBD doesn't currently handle this but so well since that will probably > turn off the local APIC timer interrupt when the CPU is idle causing FreeBSD > to miss clock interrupts. > > Sorry I am not sure exactly what you are referring to. Do you mean that I need to enable C2/C3 states in order to have the correct max CPU freq value displayed at boot time/in sysctl, or you mean that I need these states in order to be able to use the Turbo Mode at all? Right now in the BIOS I had the following features disabled to test the overclocking (I was following what is recommended to do for Windows users to run stress tests): -Intel SpeedStep: Use this function to enable the Intel SpeedStep technology (EIST) -CxE Function: This function allows you to select the lowest C state supported according as CPU and MB. The options are Auto, Disabled, C1, C1E, C3 and C6 Thanks! From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 16:00:33 2009 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 AA06A1065670 for ; Fri, 11 Sep 2009 16:00:33 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 30A5B8FC17 for ; Fri, 11 Sep 2009 16:00:32 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.1) with ESMTP id n8BG0Vb9093284; Fri, 11 Sep 2009 19:00:31 +0300 (EEST) (envelope-from mamalos@eng.auth.gr) Message-ID: <4AAA741A.7040105@eng.auth.gr> Date: Fri, 11 Sep 2009 19:00:26 +0300 From: George Mamalakis User-Agent: Thunderbird 2.0.0.19 (X11/20090226) MIME-Version: 1.0 To: Artis Caune References: <4AA90D88.4010004@eng.auth.gr> <9e20d71e0909110601kaa87f2em2e4e618b8feb306b@mail.gmail.com> In-Reply-To: <9e20d71e0909110601kaa87f2em2e4e618b8feb306b@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 11 Sep 2009 16:00:33 -0000 Artis, and the rest of the guys, thank you all for your answers. Ivan, I was thinking of using one of the techniques you mention (create two volumes, install fbsd on one of them, and use GTP on the second drive), but I was wondering if there would be any "incompatibility" issues with tools like df, etc. Artis, let me get to your comments now: > Same problem here, thought we got timeouts also on idle boxes. > > IBM support told to switch controller channel speed from auto(3Gbps) > to 1.5Gbps and update ServeRaid firmware. We are currently running > 5.2.0-15429 (flashing them almost monthly :) ). You can change speed > in raid bios, in Ctrl-A menu. > But this issue is only with sata disks, sas works perfectly. > > In case I do this (since I only have sata drives), will I end up with degraded disk performance? Theoretically I assume not, since 1.5 Gbps is adequate for *each* disk (it calculates to something like ~178MBps); but have you tried it on your disks, and everything works OK since (along with performance)? Thank you all again for your answers, you've been truly helpful! -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 16:18:50 2009 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 01F6F106566B for ; Fri, 11 Sep 2009 16:18:50 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7FA4F8FC18 for ; Fri, 11 Sep 2009 16:18:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 04E8A8035 for ; Fri, 11 Sep 2009 18:18:47 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 791A48034 for ; Fri, 11 Sep 2009 18:18:39 +0200 (CEST) From: Alban Hertroys Content-Type: multipart/mixed; boundary=Apple-Mail-6--499187472 Date: Fri, 11 Sep 2009 18:18:39 +0200 Message-Id: To: stable@freebsd.org Mime-Version: 1.0 (Apple Message framework v1075.2) X-Mailer: Apple Mail (2.1075.2) X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri Sep 11 18:18:47 2009 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 363,4aaa786713781058220185 X-DSPAM-Factors: 27, job+finished, 0.40000, Received*Sep, 0.40000, Content-Type*application/octet+stream, 0.40000, From*Alban, 0.40000, anyone+needs, 0.40000, just, 0.40000, Mime-Version*Message, 0.40000, Date*Fri+11, 0.40000, Received*11+Sep, 0.40000, Received*ESMTP, 0.40000, Message-Id*B095+504E8A572B34, 0.40000, Date*Fri, 0.40000, Content-Type*stream, 0.40000, Content-Type*Mail+6, 0.40000, Date*Sep+2009, 0.40000, Hello+I, 0.40000, attach+something, 0.40000, Content-Type*6+499187472, 0.40000, 2+STABLE, 0.40000, Received*2009+18, 0.40000, Alban+Hertroys, 0.40000, Received*Fri+11, 0.40000, the+vmcore, 0.40000, Received*id+791A48034, 0.40000, Mime-Version*v1075.2), 0.40000, best, 0.40000, To*stable, 0.40000 Cc: Subject: Kernel panic in ulpt 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, 11 Sep 2009 16:18:50 -0000 --Apple-Mail-6--499187472 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Hello, I just got a kernel panic on a FreeBSD 7.2 STABLE after a print job finished on ulpt. The kgdb output (ran in script) is attached. I'll keep the vmcore around in case anyone needs more info. Shout if you need more info. !DSPAM:363,4aaa786713781058220185! --Apple-Mail-6--499187472 Content-Disposition: attachment; filename=kgdb.out Content-Type: application/octet-stream; name="kgdb.out" Content-Transfer-Encoding: quoted-printable Script=20started=20on=20Fri=20Sep=2011=2018:10:51=202009=0ASOLFERTJE=20-=20= /home=0D=0Adalroi=20has=20logged=20on=20ttyu0=20from=20local.=0D=0A= dalroi:=1B[1msolfertje=20#=1B[m=20make=20= buildworld=1B[10Dupdate=1B[K=1B[6Dbuildworld=1B[15Dpwd=1B[K=08=08=08=1B[Kk= gdb=20/boo=0D=0D=0Aboot.config=20=20boot/=20=20=20=20=20=20=20=20=0D=0D=0A= dalroi:=1B[1msolfertje=20#=1B[m=20kgdb=20/boot/kernel/ker=0D=0D=0A= kernel*=20=20=20=20=20=20=20=20=20kernel.symbols*=20=0D=0D=0A= dalroi:=1B[1msolfertje=20#=1B[m=20kgdb=20/boot/kernel/kernel=20vmcore.0=20= =0D=0D=0AGNU=20gdb=206.1.1=20[FreeBSD]=0D=0ACopyright=202004=20Free=20= Software=20Foundation,=20Inc.=0D=0AGDB=20is=20free=20software,=20covered=20= by=20the=20GNU=20General=20Public=20License,=20and=20you=20are=0D=0A= welcome=20to=20change=20it=20and/or=20distribute=20copies=20of=20it=20= under=20certain=20conditions.=0D=0AType=20"show=20copying"=20to=20see=20= the=20conditions.=0D=0AThere=20is=20absolutely=20no=20warranty=20for=20= GDB.=20=20Type=20"show=20warranty"=20for=20details.=0D=0AThis=20GDB=20= was=20configured=20as=20"i386-marcel-freebsd"...=0D=0A=0D=0AUnread=20= portion=20of=20the=20kernel=20message=20buffer:=0D=0A=0D=0A=0D=0AFatal=20= trap=2012:=20page=20fault=20while=20in=20kernel=20mode=0D=0Acpuid=20=3D=20= 0;=20apic=20id=20=3D=2001=0D=0Afault=20virtual=20address=20=20=20=3D=20= 0x0=0D=0Afault=20code=20=20=20=20=20=20=20=20=20=20=20=20=20=20=3D=20= supervisor=20write,=20page=20not=20present=0D=0Ainstruction=20pointer=20=20= =20=20=20=3D=200x20:0xc051d5b9=0D=0Astack=20pointer=20=20=20=20=20=20=20=20= =20=20=20=3D=200x28:0xc43aac4c=0D=0Aframe=20pointer=20=20=20=20=20=20=20=20= =20=20=20=3D=200x28:0xc43aac4c=0D=0Acode=20segment=20=20=20=20=20=20=20=20= =20=20=20=20=3D=20base=200x0,=20limit=200xfffff,=20type=200x1b=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=3D=20= DPL=200,=20pres=201,=20def32=201,=20gran=201=0D=0Aprocessor=20eflags=20=20= =20=20=20=20=20=20=3D=20interrupt=20enabled,=20resume,=20IOPL=20=3D=200=0D= =0Acurrent=20process=20=20=20=20=20=20=20=20=20=3D=2012=20(swi4:=20= clock)=0D=0Atrap=20number=20=20=20=20=20=20=20=20=20=20=20=20=20=3D=2012=0D= =0Apanic:=20page=20fault=0D=0Acpuid=20=3D=200=0D=0AUptime:=201d3h43m14s=0D= =0APhysical=20memory:=201526=20MB=0D=0ADumping=20251=20MB:=20236=20220=20= 204=20188=20172=20156=20140=20124=20108=2092=2076=2060=2044=2028=2012=0D=0A= =0D=0AReading=20symbols=20from=20/boot/kernel/geom_concat.ko...Reading=20= symbols=20from=20/boot/kernel/geom_concat.ko.symbols...done.=0D=0Adone.=0D= =0ALoaded=20symbols=20for=20/boot/kernel/geom_concat.ko=0D=0AReading=20= symbols=20from=20/boot/kernel/geom_mirror.ko...Reading=20symbols=20from=20= /boot/kernel/geom_mirror.ko.symbols...done.=0D=0Adone.=0D=0ALoaded=20= symbols=20for=20/boot/kernel/geom_mirror.ko=0D=0AReading=20symbols=20= from=20/boot/kernel/geom_stripe.ko...Reading=20symbols=20from=20= /boot/kernel/geom_stripe.ko.symbols...done.=0D=0Adone.=0D=0ALoaded=20= symbols=20for=20/boot/kernel/geom_stripe.ko=0D=0AReading=20symbols=20= from=20/boot/kernel/acpi.ko...Reading=20symbols=20from=20= /boot/kernel/acpi.ko.symbols...done.=0D=0Adone.=0D=0ALoaded=20symbols=20= for=20/boot/kernel/acpi.ko=0D=0AReading=20symbols=20from=20= /boot/kernel/pf.ko...Reading=20symbols=20from=20= /boot/kernel/pf.ko.symbols...done.=0D=0Adone.=0D=0ALoaded=20symbols=20= for=20/boot/kernel/pf.ko=0D=0AReading=20symbols=20from=20= /boot/kernel/linux.ko...Reading=20symbols=20from=20= /boot/kernel/linux.ko.symbols...done.=0D=0Adone.=0D=0ALoaded=20symbols=20= for=20/boot/kernel/linux.ko=0D=0A#0=20=20doadump=20()=20at=20pcpu.h:196=0D= =0A196=20=20=20=20=20pcpu.h:=20No=20such=20file=20or=20directory.=0D=0A=20= =20=20=20=20=20=20=20in=20pcpu.h=0D=0A(kgdb)=20bt=0D=0A#0=20=20doadump=20= ()=20at=20pcpu.h:196=0D=0A#1=20=200xc059a627=20in=20boot=20(howto=3D260)=20= at=20/usr/src/sys/kern/kern_shutdown.c:418=0D=0A#2=20=200xc059a8fc=20in=20= panic=20(fmt=3DVariable=20"fmt"=20is=20not=20available.=0D=0A)=20at=20= /usr/src/sys/kern/kern_shutdown.c:574=0D=0A#3=20=200xc07f4bac=20in=20= trap_fatal=20(frame=3D0xc43aac0c,=20eva=3D0)=0D=0A=20=20=20=20at=20= /usr/src/sys/i386/i386/trap.c:938=0D=0A#4=20=200xc07f4e30=20in=20= trap_pfault=20(frame=3D0xc43aac0c,=20usermode=3D0,=20eva=3D0)=0D=0A=20=20= =20=20at=20/usr/src/sys/i386/i386/trap.c:851=0D=0A#5=20=200xc07f5825=20= in=20trap=20(frame=3D0xc43aac0c)=20at=20= /usr/src/sys/i386/i386/trap.c:529=0D=0A#6=20=200xc07da1cb=20in=20= calltrap=20()=20at=20/usr/src/sys/i386/i386/exception.s:166=0D=0A#7=20=20= 0xc051d5b9=20in=20usbd_setup_xfer=20(xfer=3D0x0,=20pipe=3D0x0,=20= priv=3D0xc4f0b300,=20=0D=0A=20=20=20=20buffer=3D0xc4ce4000,=20= length=3D4096,=20flags=3D5,=20timeout=3D10,=20=0D=0A=20=20=20=20= callback=3D0xc0514910=20)=20at=20= /usr/src/sys/dev/usb/usbdi.c:547=0D=0A#8=20=200xc05148f1=20in=20= ulpt_tick=20(xsc=3D0xc4f0b300)=20at=20/usr/src/sys/dev/usb/ulpt.c:773=0D=0A= #9=20=200xc05acf0c=20in=20softclock=20(dummy=3D0x0)=20at=20= /usr/src/sys/kern/kern_timeout.c:274=0D=0A#10=200xc05774db=20in=20= ithread_loop=20(arg=3D0xc4490300)=0D=0A=20=20=20=20at=20= /usr/src/sys/kern/kern_intr.c:1127=0D=0A#11=200xc0573df7=20in=20= fork_exit=20(callout=3D0xc0577330=20,=20=0D=0A=20=20=20=20= arg=3D0xc4490300,=20frame=3D0xc43aad38)=20at=20= /usr/src/sys/kern/kern_fork.c:811=0D=0A#12=200xc07da240=20in=20= fork_trampoline=20()=20at=20/usr/src/sys/i386/i386/exception.s:271=0D=0A= (kgdb)=20dalroi:=1B[1msolfertje=20#=1B[m=20^D=08=08=0AScript=20done=20on=20= Fri=20Sep=2011=2018:11:58=202009=0A= --Apple-Mail-6--499187472 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed Alban Hertroys -- Screwing up is the best way to attach something to the ceiling. !DSPAM:363,4aaa786713781058220185! --Apple-Mail-6--499187472-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 16:36:08 2009 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 87357106568B for ; Fri, 11 Sep 2009 16:36:08 +0000 (UTC) (envelope-from mamalos@eng.auth.gr) Received: from vergina.eng.auth.gr (vergina.eng.auth.gr [155.207.18.1]) by mx1.freebsd.org (Postfix) with ESMTP id 062538FC0A for ; Fri, 11 Sep 2009 16:36:07 +0000 (UTC) Received: from mamalacation.ee.auth.gr (mamalacation.ee.auth.gr [155.207.33.29]) by vergina.eng.auth.gr (8.14.3/8.14.1) with ESMTP id n8BGa6rG028619 for ; Fri, 11 Sep 2009 19:36:06 +0300 (EEST) (envelope-from mamalos@eng.auth.gr) Message-ID: <4AAA7C71.8070708@eng.auth.gr> Date: Fri, 11 Sep 2009 19:36:01 +0300 From: George Mamalakis User-Agent: Thunderbird 2.0.0.19 (X11/20090226) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: MSI GT 627 unsuccessful installation in 7-STABLE and 8-BETA4 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, 11 Sep 2009 16:36:08 -0000 Dear all, My question should maybe have be sent to some other fbsd list; if so, please someone instruct me where, and excuse me for my potential mistake. Now to my question: I just bought the MSI GT 627 Laptop, and I tried to install FreeBSD on it. First I tried with 8-BETA4 amd, then with 8-BETA4 i386, and lastly with 7.2 latest snapshot. All attempts have been unsuccessful, so I tried NetBSD 5.0.1 to see if it would install, and it did! The kernel messages I got on all FOUR attempts (even in NetBSD, although it worked finally) was something like that (in the beginning) (NetBSD excerpt, since it is the only that booted, so I could copy-paste it from dmesg, but FreeBSD gave the exact same Error messages (a few numbers differ)): Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 5.0.1 (GENERIC) #0: Thu Jul 30 00:08:07 UTC 2009 builds@b7.netbsd.org:/home/builds/ab/netbsd-5-0-1-RELEASE/amd64/200907292356Z-obj/home/builds/ab/netbsd-5-0-1-RELEASE/src/sys/arch/amd64/compile/GENERIC total memory = 4095 MB avail memory = 3954 MB timecounter: Timecounters tick every 10.000 msec timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 SMBIOS rev. 2.5 @ 0x9a400 (45 entries) Micro-Star International GT627 (Ver 1.000) mainbus0 (root) cpu0 at mainbus0 apid 0: Intel 686-class, 2394MHz, id 0x1067a cpu1 at mainbus0 apid 1: Intel 686-class, 2394MHz, id 0x1067a cpu2 at mainbus0 apid 2: Intel 686-class, 2394MHz, id 0x1067a cpu3 at mainbus0 apid 3: Intel 686-class, 2394MHz, id 0x1067a ioapic0 at mainbus0 apid 4: pa 0xfec00000, version 20, 24 pins acpi0 at mainbus0: Intel ACPICA 20080321 acpi0: X/RSDT: OemId , AslId ACPI Error (evregion-0427): No handler for Region [EC__] (0xffff800007e20400) [EmbeddedControl] [20080321] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20080321] ACPI Error (psparse-0627): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST ACPI Error (uteval-0306): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST acpi0: SCI interrupting at int 9 acpi0: fixed-feature power button present timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000 ACPI-Fast 24-bit timer ACPI Error (evregion-0427): No handler for Region [EC__] (0xffff800007e20400) [EmbeddedControl] [20080321] ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20080321] ACPI Error (psparse-0627): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST ACPI Error (uteval-0306): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST WMI1 (pnp0c14) at acpi0 not configured .... where fbsd differed, was somewhere after identifying ad4 (the disk, which is WDC WD5000BEVT-22ZAT0 01.01A1), where it stated: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05 run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config and after that it kept on repeating the last message, only increasing the seconds to wait, until nothing more happened. Does anyone know if this is something that will be fixed soon? I guess it has to do with MSI's ACPI or something like that. Thank you all for your interest. Regards, mamalos. -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 17:27:33 2009 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 D33411065676 for ; Fri, 11 Sep 2009 17:27:33 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from proton.sasknet.sk.ca (proton.sasknet.sk.ca [142.165.20.178]) by mx1.freebsd.org (Postfix) with ESMTP id 9F8B78FC1E for ; Fri, 11 Sep 2009 17:27:33 +0000 (UTC) Received: from pps.filterd (proton [127.0.0.1]) by proton.sasknet.sk.ca (8.14.3/8.14.3) with SMTP id n8BHNH6s008087; Fri, 11 Sep 2009 11:27:32 -0600 Received: from bgmpomr2.sasknet.sk.ca (bgmpOMR2.sasknet.sk.ca [142.165.72.23]) by proton.sasknet.sk.ca with ESMTP id gqs14e150-1; Fri, 11 Sep 2009 11:27:32 -0600 Received: from ace.hurd.local (outgoing.bbsdev.net [76.202.204.46]) by bgmpomr2.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0KPT006RPHTU2Q10@bgmpomr2.sasknet.sk.ca>; Fri, 11 Sep 2009 11:27:32 -0600 (CST) Date: Fri, 11 Sep 2009 10:27:29 -0700 From: Stephen Hurd In-reply-to: To: Ivan Voras Message-id: <4AAA8881.7000609@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT References: <4AAA1296.2080705@sasktel.net> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.22) Gecko/20090810 SeaMonkey/1.1.17 Mnenhy/0.7.6.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-09-11_12:2009-09-01, 2009-09-11, 2009-09-11 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_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-0908210000 definitions=main-0909110091 Cc: freebsd-stable@freebsd.org Subject: Re: 8.0-B4 gstripe / GEOM_PART_* upgrade woes 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, 11 Sep 2009 17:27:33 -0000 Ivan Voras wrote: > An interesting problem. I presume that in either case (gpart or > GEOM_BSD/MBR) the output of "gstripe status" is the same? Only the > interpretation of the partition tables is problematic? Yes, but the output of gstripe list is different in the mode lines... for GEOM_PART, the mode is r0w0e0 in all consumers and for GEOM_*, the mode is r3w3e5. > What is the expected ("good") structure of the partitions/file > systems? Do you have a single MBR partition and inside it multiple BSD > partitions? What are their partition types? Not sure the correct way to get the info, but the output of fdisk and bsdlabel follow: ==== START of fdisk ==== > fdisk /dev/stripe/raid0 ******* Working on device /dev/stripe/raid0 ******* parameters extracted from in-core disklabel are: cylinders=5219 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=5219 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 ==== END OF fdisk ==== ==== START OF bsdlabel ==== > bsdlabel /dev/stripe/raid0 # /dev/stripe/raid0: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 16777216 16 4.2BSD 2048 16384 28552 b: 16777216 16777232 4.2BSD 2048 16384 28552 c: 20964825 8385930 unused 0 0 # "raw" part, don't edit d: 50302960 33554448 4.2BSD 2048 16384 28552 bsdlabel: partition c doesn't start at 0! bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities ==== END OF bsdlabel ==== Now that I look at the bsdlabel output, I vaugely recall that I couldn't get c correct... From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 17:32:55 2009 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 3729610656B7 for ; Fri, 11 Sep 2009 17:32:55 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by mx1.freebsd.org (Postfix) with ESMTP id B675A8FC15 for ; Fri, 11 Sep 2009 17:32:54 +0000 (UTC) Received: by ewy4 with SMTP id 4so1303961ewy.36 for ; Fri, 11 Sep 2009 10:32:53 -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:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=/P4loXarH8ma/Ip6sJUX2P//uZIqm4lUf5xiIg7jJsg=; b=bf+hTu2kdL94rEA1hoUBaMIrom3ceFfbXrt0QMz7hHgEWmZLTF/xl+QpZy4tlc9JHu vu9SweXKZm5Ajfz4ml8IDeIuQxQs7hHbOqJw74Tve+MQJVokdtDEBeyq0b3WoyVwGNpE PwOCqFPuWZzEAvFBOMkP0nyoW9lqvh2Tl9b4M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=qfEV9YukdWONS7peinEpbp25wfuH0zc/umjWf/03cGpDIPgeWS92thI4nu8BvHIjf2 OAa1Mmj1hS7iw76r3smJoBYcEe5m36rEMFm2SJMuTEwLlEdZ8u6XNwFZC12C0athOybK vE1eJg/w5BQzyzI4lEKTCTdTK1kIoZ5xogIog= Received: by 10.210.9.7 with SMTP id 7mr3562900ebi.5.1252689047883; Fri, 11 Sep 2009 10:10:47 -0700 (PDT) Received: from pulstar.local (athedsl-4490856.home.otenet.gr [94.71.82.112]) by mx.google.com with ESMTPS id 28sm2609575eye.8.2009.09.11.10.10.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 11 Sep 2009 10:10:46 -0700 (PDT) Message-ID: <4AAA848C.4060707@gmail.com> Date: Fri, 11 Sep 2009 20:10:36 +0300 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: George Mamalakis References: <4AAA7C71.8070708@eng.auth.gr> In-Reply-To: <4AAA7C71.8070708@eng.auth.gr> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: MSI GT 627 unsuccessful installation in 7-STABLE and 8-BETA4 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, 11 Sep 2009 17:32:55 -0000 George Mamalakis wrote: > Dear all, > > My question should maybe have be sent to some other fbsd list; if so, > please someone instruct me where, and excuse me for my potential mistake. > > Now to my question: > > I just bought the MSI GT 627 Laptop, and I tried to install FreeBSD on > it. First I tried with 8-BETA4 amd, then with 8-BETA4 i386, and lastly > with 7.2 latest snapshot. All attempts have been unsuccessful, so I > tried NetBSD 5.0.1 to see if it would install, and it did! > > The kernel messages I got on all FOUR attempts (even in NetBSD, > although it worked finally) was something like that (in the beginning) > (NetBSD excerpt, since it is the only that booted, so I could > copy-paste it from dmesg, but FreeBSD gave the exact same Error > messages (a few numbers differ)): > > Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, > 2006, 2007, 2008, 2009 > The NetBSD Foundation, Inc. All rights reserved. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > > NetBSD 5.0.1 (GENERIC) #0: Thu Jul 30 00:08:07 UTC 2009 > > builds@b7.netbsd.org:/home/builds/ab/netbsd-5-0-1-RELEASE/amd64/200907292356Z-obj/home/builds/ab/netbsd-5-0-1-RELEASE/src/sys/arch/amd64/compile/GENERIC > > total memory = 4095 MB > avail memory = 3954 MB > timecounter: Timecounters tick every 10.000 msec > timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 > SMBIOS rev. 2.5 @ 0x9a400 (45 entries) > Micro-Star International GT627 (Ver 1.000) > mainbus0 (root) > cpu0 at mainbus0 apid 0: Intel 686-class, 2394MHz, id 0x1067a > cpu1 at mainbus0 apid 1: Intel 686-class, 2394MHz, id 0x1067a > cpu2 at mainbus0 apid 2: Intel 686-class, 2394MHz, id 0x1067a > cpu3 at mainbus0 apid 3: Intel 686-class, 2394MHz, id 0x1067a > ioapic0 at mainbus0 apid 4: pa 0xfec00000, version 20, 24 pins > acpi0 at mainbus0: Intel ACPICA 20080321 > acpi0: X/RSDT: OemId , AslId > ACPI Error (evregion-0427): No handler for Region [EC__] > (0xffff800007e20400) [EmbeddedControl] [20080321] > ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler > [20080321] > ACPI Error (psparse-0627): Method parse/execution failed > [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST > ACPI Error (uteval-0306): Method execution failed > [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST > acpi0: SCI interrupting at int 9 > acpi0: fixed-feature power button present > timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000 > ACPI-Fast 24-bit timer > ACPI Error (evregion-0427): No handler for Region [EC__] > (0xffff800007e20400) [EmbeddedControl] [20080321] > ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler > [20080321] > ACPI Error (psparse-0627): Method parse/execution failed > [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST > ACPI Error (uteval-0306): Method execution failed > [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffff800007e23760), AE_NOT_EXIST > WMI1 (pnp0c14) at acpi0 not configured > .... > > where fbsd differed, was somewhere after identifying ad4 (the disk, > which is WDC WD5000BEVT-22ZAT0 01.01A1), where it stated: > > acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05 > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config > run_interrupt_driven_hooks: still waiting after 120 seconds for > xpt_config > > and after that it kept on repeating the last message, only increasing > the seconds to wait, until nothing more happened. > > Does anyone know if this is something that will be fixed soon? I guess > it has to do with MSI's ACPI or something like that. > > Thank you all for your interest. > > Regards, > > mamalos. > Is the laptop equipped with a firewire port? I have a few Gigabyte 8IPE1000-G motherboards at school that exhibit the exact same behaviour. (Using 7.X, have not tried with 8.0 yet). Although the motherboard does not in fact have a firewire chip soldered on, the BIOS presents a firewire device (in Windows it shows in the device manager as a non-working, unknown problem device) and I believe this confuses the FreeBSD boot sequence. Other people on the lists have also suggested disabling device sbp in a custom kernel configuration file (or even removing the entire firewire section if you don't need it). One possible first step would be to try disabling firewire in the BIOS (Sadly I don't have this option at all in my case) and see if the boot continues. If you install successfully you may then try building a custom kernel and re-enabling the BIOS option. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 18:01:37 2009 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 8FDDB1065672; Fri, 11 Sep 2009 18:01:37 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 569068FC20; Fri, 11 Sep 2009 18:01:37 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n8BI1a59027881; Fri, 11 Sep 2009 11:01:36 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 11 Sep 2009 11:00:42 -0700 Message-ID: In-Reply-To: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NFS issues on 8.0-BETA4 Thread-Index: Acoy9I+eM34VDLUKS7OxiLwkzzLohwAFJ0GA References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> From: "Li, Qing" To: "Doug Poland" , Cc: FreeBSD Current Subject: RE: NFS issues on 8.0-BETA4 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, 11 Sep 2009 18:01:37 -0000 >=20 > I cannot sucessfully mount exports from the NFSv3 server on the > 8.0-BETA4 client. All works well with 7.2 clients. >=20 > The strange thing is, the directory in which I mount the nfs > filesystem disappears, and I get an error when I attempt to access the > directory. >=20 This may be a known issue that a couple of us have been working on yesterday. Would you be willing to try out a=20 temporary patch? -- Qing From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 18:45:18 2009 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 CC36D1065670 for ; Fri, 11 Sep 2009 18:45:18 +0000 (UTC) (envelope-from doug@polands.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 8ABEA8FC0C for ; Fri, 11 Sep 2009 18:45:18 +0000 (UTC) Received: from haran.polands.org ([75.87.219.217]) by hrndva-omta03.mail.rr.com with ESMTP id <20090911184517571.VOXC4372@hrndva-omta03.mail.rr.com>; Fri, 11 Sep 2009 18:45:17 +0000 Received: from email.polands.org (ammon.polands.org [172.16.1.7]) by haran.polands.org (8.14.3/8.14.3) with ESMTP id n8BIjGuR077851; Fri, 11 Sep 2009 13:45:16 -0500 (CDT) (envelope-from doug@polands.org) Received: from 209.103.215.99 (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Fri, 11 Sep 2009 13:45:17 -0500 Message-ID: In-Reply-To: References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> Date: Fri, 11 Sep 2009 13:45:17 -0500 From: "Doug Poland" To: "Li, Qing" User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-stable@freebsd.org, FreeBSD Current Subject: RE: NFS issues on 8.0-BETA4 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, 11 Sep 2009 18:45:18 -0000 On Fri, September 11, 2009 13:00, Li, Qing wrote: >> >> I cannot successfully mount exports from the NFSv3 server on the >> 8.0-BETA4 client. All works well with 7.2 clients. >> >> The strange thing is, the directory in which I mount the nfs >> filesystem disappears, and I get an error when I attempt to access >> the directory. >> > > This may be a known issue that a couple of us have been > working on yesterday. Would you be willing to try out a > temporary patch? > > -- Qing > I'd be happy to assist anyway I can. -- Regards, Doug From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 19:17:01 2009 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 9D823106568D for ; Fri, 11 Sep 2009 19:17:01 +0000 (UTC) (envelope-from artis.caune@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 325F58FC0A for ; Fri, 11 Sep 2009 19:17:01 +0000 (UTC) Received: by fxm6 with SMTP id 6so966649fxm.43 for ; Fri, 11 Sep 2009 12:17:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ayZqT+Sp7YPnKaj1YFLdMk/3cPdnHideqmTW4zdIC0s=; b=cyoA9PqmzbHE1XQFTNbve6xxwBxKIkiyB/xClOb5gZQTlTERi4es00REZ1bqX2mWJK UomJy7XurOEXBmrBONYFYW1qrqDXFJAl0ksquEN7vxqmk03fiYj9sAnOVB57B0C+HDNs YrQQ+YG5i/qgCaAAiEWRjE5go43tgfAmj9IVE= 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=I1AjC36R+iN3J42cREvrNAt2CZEIQMIr0JpJo+88PUvfodhmYcjLOh9IMLQx8elxi1 CjwhZTcdfCmXa4V/smAevarMJ7kbhcZi5PvQN3/sKYENPPxN72x9jF57Vz9fnFtGvDZW OYjs5R58WopM6/A+jjF76rViSw1UZqkZLOjpY= MIME-Version: 1.0 Received: by 10.103.50.28 with SMTP id c28mr1608405muk.17.1252696620220; Fri, 11 Sep 2009 12:17:00 -0700 (PDT) In-Reply-To: <4AAA741A.7040105@eng.auth.gr> References: <4AA90D88.4010004@eng.auth.gr> <9e20d71e0909110601kaa87f2em2e4e618b8feb306b@mail.gmail.com> <4AAA741A.7040105@eng.auth.gr> Date: Fri, 11 Sep 2009 22:17:00 +0300 Message-ID: <9e20d71e0909111217v6242c8f1ge391d72f00193344@mail.gmail.com> From: Artis Caune To: George Mamalakis Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 8.0-BETA4 IBM ServerRaid 8k issues 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, 11 Sep 2009 19:17:01 -0000 2009/9/11 George Mamalakis : > Artis, and the rest of the guys, thank you all for your answers. > > Ivan, I was thinking of using one of the techniques you mention (create two > volumes, install fbsd on one of them, and use GTP on the second drive), but > I was wondering if there would be any "incompatibility" issues with tools > like df, etc. > > > In case I do this (since I only have sata drives), will I end up with > degraded disk performance? Theoretically I assume not, since 1.5 Gbps is > adequate for *each* disk (it calculates to something like ~178MBps); but > have you tried it on your disks, and everything works OK since (along with > performance)? > We didn't tested speed much, but looks like you loose few MB (very quick tests with dd). We are hosting 40K+ mailboxes, on ZFS :), so we are more random-read/seek bound than Gbps bound. But yes, we are running at 1.5Gbps and are happy stable/7 ZFS v6 users and after few weeks we are migrating to stable/8 ZFS v13 with GPT and gptzfsboot. -- Artis Caune Everything should be made as simple as possible, but not simpler. From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 20:43:09 2009 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 269421065692; Fri, 11 Sep 2009 20:43: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 B6E3F8FC14; Fri, 11 Sep 2009 20:43:08 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAG9TqkqDaFvJ/2dsb2JhbADdWIQYBYFU X-IronPort-AV: E=Sophos;i="4.44,372,1249272000"; d="scan'208";a="45974893" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Sep 2009 16:43:08 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 06B86FB80A3; Fri, 11 Sep 2009 16:43:08 -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 F1B5J+4Mj8Vi; Fri, 11 Sep 2009 16:43:07 -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 E57C8FB80A1; Fri, 11 Sep 2009 16:43:06 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8BKmL612171; Fri, 11 Sep 2009 16:48:21 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 11 Sep 2009 16:48:21 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Doug Poland In-Reply-To: Message-ID: References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, FreeBSD Current Subject: RE: NFS issues on 8.0-BETA4 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, 11 Sep 2009 20:43:09 -0000 On Fri, 11 Sep 2009, Rick Macklem wrote: > > >>> >>> I cannot sucessfully mount exports from the NFSv3 server on the >>> 8.0-BETA4 client. All works well with 7.2 clients. >>> >>> The strange thing is, the directory in which I mount the nfs >>> filesystem disappears, and I get an error when I attempt to access the >>> directory. >>> I just took another glance at your email and see you have your server configured for UDP only, so that explains it. As noted in the last posting, the current mount_nfs.c switches to TCP for NFS by default, so... - add "udp" to your mount options OR - add "-t" to your nfs_server_flags and I think things will work better. I vaguely recall posting w.r.t. this uses UDP for the mount protocol and then TCP for NFS by default and didn't really get any responses. (I'm new to this and probably posted to freebsd-fs or freebsd-arch.) At that time, I didn't realize the change was post FreeBSD7, so I didn't do anything more about it. Good luck with it and let us know how it goes, rick From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 21:01:17 2009 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 18D581065750 for ; Fri, 11 Sep 2009 21:01:17 +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 C05608FC28 for ; Fri, 11 Sep 2009 21:01:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEABdRqkqDaFvI/2dsb2JhbADdWoQYBYFU X-IronPort-AV: E=Sophos;i="4.44,372,1249272000"; d="scan'208";a="45973473" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 11 Sep 2009 16:32:38 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 18D5E9400A6; Fri, 11 Sep 2009 16:32:38 -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 VeLkRbP3-ion; Fri, 11 Sep 2009 16:32:36 -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 D1936940078; Fri, 11 Sep 2009 16:32:36 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n8BKboE10143; Fri, 11 Sep 2009 16:37:51 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Fri, 11 Sep 2009 16:37:50 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Doug Poland In-Reply-To: Message-ID: References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, FreeBSD Current Subject: RE: NFS issues on 8.0-BETA4 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, 11 Sep 2009 21:01:17 -0000 >> >> I cannot sucessfully mount exports from the NFSv3 server on the >> 8.0-BETA4 client. All works well with 7.2 clients. >> >> The strange thing is, the directory in which I mount the nfs >> filesystem disappears, and I get an error when I attempt to access the >> directory. >> I went and looked at the message over in stable@ (I guess I have to join that mailing list, too:-). I think that the second mount attempt, which failed with errno==64 EHOSTDOWN probably gives you a better indication of what is broken and hints at a networking problem, which hopefully others can help with? mount_nfs currently has the quirk that, if you don't specify either "udp" or "tcp", it will use UDP for the mount protocol and then switch to TCP for NFS. (I didn't make it that way, but noticed it when I was adding changes for the experimental client.) So, you might want to try adding "udp" or "tcp" to the mount options for your "simplified mount" and see what happens? (I suggest this, since it seems to have been able to talk to mountd on the server, but not NFS on the server and the only explanation I can think of is the switch to TCP for that.) I think the first case failed after the retrycnt, due to the "soft" option, but hadn't succeeded in doing any NFS Getattr, so the mount point's type wasn't VDIR--> returning errno==1 EPERM for the "ls -l". If the mount attempts with "udp" or "tcp" specified give you the same behaviour, you could try using wireshark to capture the traffic. (Wireshark is pretty good at decoding NFS traffic.) If you don't have wireshark, you can use "tcpdump -w -s 0 " to capture the traffic in a file that can be fed to wireshark later. (I'd be happy to look at the traffic, if you were to email me the above .) Good luck with it, rick ps: I'll assume that the client can talk to the server for other stuff ok. pss: A big change between 7 and 8 is use of a new kernel RPC layer that handles the RPC transport (again, I wasn't the author, but am somewhat familiar with it). From owner-freebsd-stable@FreeBSD.ORG Fri Sep 11 21:37:31 2009 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 D2884106566B for ; Fri, 11 Sep 2009 21:37:31 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 24A498FC12 for ; Fri, 11 Sep 2009 21:37:30 +0000 (UTC) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 80CE61B16815; Fri, 11 Sep 2009 23:21:37 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on malcho.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.5 Received: from maylo.moneybookers.com (maylo.dev.moneybookers.net [192.168.3.20]) by blah.sun-fish.com (Postfix) with ESMTP id E061E1B16814; Fri, 11 Sep 2009 23:21:36 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by maylo.moneybookers.com (Postfix) with ESMTP id DB94A37BF843; Fri, 11 Sep 2009 23:21:36 +0200 (CEST) Received: from maylo.moneybookers.com ([127.0.0.1]) by localhost (maylo.dev.moneybookers.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id qn2RkKCZJI-p; Fri, 11 Sep 2009 23:21:34 +0200 (CEST) Received: from [10.1.1.3] (unknown [192.168.25.6]) by maylo.moneybookers.com (Postfix) with ESMTP id 175AC37BF83E; Fri, 11 Sep 2009 23:21:34 +0200 (CEST) Message-Id: From: Stefan Lambrev To: Tobias Lott In-Reply-To: <20090909215959.6b5152f2@sub.han.vpn.gamesnet.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Sat, 12 Sep 2009 00:21:33 +0300 References: <20090908121945.43ba3976@sub.han.vpn.gamesnet.de> <20090909104807.633418ea@sub.han.vpn.gamesnet.de> <20090909170213.GA7925@lava.net> <20090909213022.34d64e47@sub.han.vpn.gamesnet.de> <20090909215959.6b5152f2@sub.han.vpn.gamesnet.de> X-Mailer: Apple Mail (2.936) X-Virus-Scanned: ClamAV 0.94/9797/Fri Sep 11 15:59:58 2009 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-performance@freebsd.org, freebsd-stable@freebsd.org Subject: Re: System crawls after Upgrade 7.0->7.2 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, 11 Sep 2009 21:37:31 -0000 Hi Tobias, This is the "pseudo" RAID controller that comes by default with most Dell, low cost HP servers and probably others? If you depend on I/O I would recommend you to change this raid with PERC6/i (looks like this is Dell server) which is little more expensive, but comes with 256MB battery backed cache. In my experience mpt devices are crap, and their performance is worse then software mirror. PERC6/i is something totally different :) It's again LSI product branded from Dell and it works with mfi driver. The only problem in the past with them was the management utility which was linux binary, but today there is official native tool in ports, and in 8.0 in base install there will be a tool to manage your controller. Well this wasn't that big problem compared to mpt which cannot be managed under FreeBSD at all? On Sep 9, 2009, at 10:59 PM, Tobias Lott wrote: > > > On Wed, 9 Sep 2009 21:30:22 +0200 > Tobias Lott wrote: > >> >> >> On Wed, 9 Sep 2009 07:02:13 -1000 >> Clifton Royston wrote: >> >>> On Wed, Sep 09, 2009 at 10:48:07AM +0200, Tobias Lott wrote: >>>> On Tue, 8 Sep 2009 12:19:45 +0200 >>>> Tobias Lott wrote: >>>>> Hey Everyone, >>>>> >>>>> I upgraded a Dual Core Machine to 7.2-Stable (2 Days ago), all >>>>> OS related Stuff is located on an UFS Slice, Application is on >>>>> a ZFS Volume. >>>>> >>>>> After the Upgrade everything seemed fine, but a User noticed one >>>>> PHP Script which is basically loading a plain Textfile into >>>>> Mysql times out. PHP Timeout was set to 60 secs, that was more >>>>> then enough just one day before the upgrade. >>> ... >>>>> Since I upgraded the Machines zpool to version 13 already I >>>>> don't really wanna go back to 7.0, but it seems the only way >>>>> out atm. >>>>> >>>>> Hopefully someone can give me a Hint where maybe I forgot to >>>>> check. >>>>> >>>>> Somehow it feels like the last Versions, I'd say starting with >>>>> 7.x doesn't really feel that Rock-Stable as Versions Prior used >>>>> to be. Prolly cause I'm using an Experimental Feature like ZFS, >>>>> so no Offense nor Blame and this is not intended as a Flame or >>>>> whatsoever! So don't get me wrong, I always liked, used, >>>>> recommended FreeBSD since 4.0 and will continue to do so! >>>>> >>>>> Best Regards >>>>> >>>> >>>> I've tested some more it seems the Bottleneck is the HD, Raid >>>> Array is Optimal checked it. >>> >>> Probably you already checked this, but did you go through the >>> dmesg output relating to ata and drive detection closely? >>> >>> In the past from time to time I've had machines suddenly start >>> crawling after an upgrade, and it turned out it was because some >>> change in the driver detection caused the ata to fall back to pio >>> mode. The symptoms are pretty much like you describe - all HD IO >>> takes forever. >>> >>> -- Clifton >>> >> >> Thanks for that Hint, checked again to be sure, but thats not the >> Case. >> >> mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares High-Priority- >> ReSync ) >> mpt0:vol0(mpt0:0:0): Using Spare Pool: 0 >> mpt0:vol0(mpt0:0:0): 2 Members: >> (mpt0:1:32:0): Primary Online >> (mpt0:1:1:0): Secondary Online >> mpt0:vol0(mpt0:0:0): RAID-1 - Optimal >> mpt0:vol0(mpt0:0:0): Status ( Enabled ) >> (mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:0:0) >> (mpt0:vol0:1): Online >> (mpt0:vol0:0): Physical (mpt0:0:32:0), Pass-thru (mpt0:1:1:0) >> (mpt0:vol0:0): Online >> acd0: CDROM at ata0-master UDMA33 >> acd1: CDROM at ata2-slave PIO3 >> da0 at mpt0 bus 0 target 0 lun 0 >> da0: Fixed Direct Access SCSI-5 device >> da0: 300.000MB/s transfers >> da0: Command Queueing Enabled >> SdMaP0:: A1P5 1C6P3U4 M#B1 (L3a1u0n5c4h6e4d3!2 >> 512 byte sectors: 255H 63S/T 19330C) >> >> > > Oh well just did some more research and found: > http://www.mail-archive.com/freebsd-performance@freebsd.org/msg02461.html > > Gonna try it out later and gonna give a Report. > > -- > Tobias Lott > _______________________________________________ > 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 > " -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 04:57:19 2009 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 436571065670 for ; Sat, 12 Sep 2009 04:57:19 +0000 (UTC) (envelope-from graham@menhennitt.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.freebsd.org (Postfix) with ESMTP id D6D158FC18 for ; Sat, 12 Sep 2009 04:57:18 +0000 (UTC) Received: from maxwell.mencon.com.au (c220-239-199-115.chirn1.vic.optusnet.com.au [220.239.199.115]) by mail03.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n8C4v9Ij011861; Sat, 12 Sep 2009 14:57:15 +1000 Received: from [203.2.73.73] (chief.mencon.com.au [203.2.73.73]) by maxwell.mencon.com.au (Postfix) with ESMTP id 1CE315C93; Sat, 12 Sep 2009 14:57:09 +1000 (EST) Message-ID: <4AAB2A2C.2000803@menhennitt.com.au> Date: Sat, 12 Sep 2009 14:57:16 +1000 From: Graham Menhennitt User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG, Soekris-tech@lists.soekris.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: problem booting FreeBSD 8-Beta4 on Soekris net5501 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, 12 Sep 2009 04:57:19 -0000 G'day, I'm upgrading a Soekris net5501 from FreeBSD 7-Stable to 8-Beta4 (via source). I've done a buildworld, buildkernel, and installkernel. When I try to boot the new kernel, it stops very early on in the boot sequence. The serial console shows: /boot/kernel/kernel text=0x32f9f0 data=0x36374+0x1e580 syms=[0x4+0x40720+0x4+0x592a3] - Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... / The slash at the end is the first character of the spinner as it's loading the kernel. It never shows the second character. I've tried two different kernel configs - my own (from 7 modified to build with 8) and aragon's from http://www.nabble.com/no-time-of-day-clock-registered-on-net5501,-FreeBSD-8-td24544248.html (with the line "options STOP_NMI" removed to get it to build). They both do the same thing. My loader.conf is the same as in 7: beastie_disable="YES" comconsole_speed="19200" console="comconsole" My kernel config is below. Does anybody have any clues please? Thanks for any help, Graham cpu I586_CPU ident maxwell options CPU_GEODE options CPU_SOEKRIS options SCHED_ULE # ULE scheduler 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 NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options COMPAT_FREEBSD7 # Compatible with FreeBSD7 options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # Posix P1003_1B real-time extensions options IPFIREWALL options IPFIREWALL_VERBOSE options IPDIVERT options IPFIREWALL_NAT # ipfw kernel nat support options LIBALIAS device pci device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device uart # Generic UART driver device miibus # MII bus support device vr # VIA Rhine, Rhine II device wlan # 802.11 support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device ath # Atheros pci/cardbus NIC's device ath_hal # pci/cardbus chip support options AH_SUPPORT_AR5416 # enable AR5416 tx/rx descriptors device ath_rate_sample # SampleRate tx rate control for ath device loop # Network loopback device random # Entropy device device ether # Ethernet support device tap # Ethernet tunnel. device tun # Packet tunnel. device pty # BSD-style compatibility pseudo ttys device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device bpf # Berkeley packet filter device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 14:41:15 2009 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 C36EA1065696; Sat, 12 Sep 2009 14:41:15 +0000 (UTC) (envelope-from doug@polands.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.125]) by mx1.freebsd.org (Postfix) with ESMTP id 6A6418FC21; Sat, 12 Sep 2009 14:41:14 +0000 (UTC) Received: from haran.polands.org ([75.87.219.217]) by hrndva-omta01.mail.rr.com with ESMTP id <20090912144114123.WHNK11562@hrndva-omta01.mail.rr.com>; Sat, 12 Sep 2009 14:41:14 +0000 Received: from email.polands.org (ammon.polands.org [172.16.1.7]) by haran.polands.org (8.14.3/8.14.3) with ESMTP id n8CEfBsi081786; Sat, 12 Sep 2009 09:41:11 -0500 (CDT) (envelope-from doug@polands.org) Received: from 172.16.1.1 (SquirrelMail authenticated user djp) by email.polands.org with HTTP; Sat, 12 Sep 2009 09:41:13 -0500 Message-ID: <19c32ef4263ed3c2ab1624a43ae86c78.squirrel@email.polands.org> In-Reply-To: References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> Date: Sat, 12 Sep 2009 09:41:13 -0500 From: "Doug Poland" To: "Rick Macklem" User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: "Li, Qing" , freebsd-stable@freebsd.org, FreeBSD Current , Andrzej Tobola Subject: RE: NFS issues on 8.0-BETA4 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, 12 Sep 2009 14:41:15 -0000 On Fri, September 11, 2009 15:37, Rick Macklem wrote: > >>> >>> I cannot sucessfully mount exports from the NFSv3 server on the >>> 8.0-BETA4 client. All works well with 7.2 clients. >>> >>> The strange thing is, the directory in which I mount the nfs >>> filesystem disappears, and I get an error when I attempt to >>> access the directory. >>> > > I went and looked at the message over in stable@ (I guess I have to > join that mailing list, too:-). > > I think that the second mount attempt, which failed with errno==64 > EHOSTDOWN probably gives you a better indication of what is broken > and hints at a networking problem, which hopefully others can help > with? > > mount_nfs currently has the quirk that, if you don't specify either > "udp" or "tcp", it will use UDP for the mount protocol and then > switch to TCP for NFS. (I didn't make it that way, but noticed it > when I was adding changes for the experimental client.) So, you might > want to try adding "udp" or "tcp" to the mount options for your > "simplified mount" and see what happens? (I suggest this, since it > seems to have been able to talk to mountd on the server, but not NFS > on the server and the only explanation I can think of is the switch > to TCP for that.) > > I think the first case failed after the retrycnt, due to the "soft" > option, but hadn't succeeded in doing any NFS Getattr, so the mount > point's type wasn't VDIR--> returning errno==1 EPERM for the "ls -l". > > > If the mount attempts with "udp" or "tcp" specified give you the same > behaviour, you could try using wireshark to capture the traffic. > (Wireshark is pretty good at decoding NFS traffic.) If you don't have > wireshark, you can use "tcpdump -w -s 0 " to capture > the traffic in a file that can be fed to wireshark later. (I'd be > happy to look at the traffic, if you were to email me the above > .) > > Good luck with it, rick ps: I'll assume that the client can talk to > the server for other stuff ok. pss: A big change between 7 and 8 is > use of a new kernel RPC layer that handles the RPC transport (again, > I wasn't the author, but am somewhat familiar with it). > > Simply adding -o udp to my mount command made the NFS mount work correctly. Qing, would it be beneficial to attempt the patch in light of these findings? Thanks all for the help, sorry for the noise. -- Regards, Doug From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 18:51:03 2009 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 D5916106566B; Sat, 12 Sep 2009 18:51:03 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id B9B918FC0C; Sat, 12 Sep 2009 18:51:03 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n8CIp1OK017936; Sat, 12 Sep 2009 11:51:01 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sat, 12 Sep 2009 11:50:52 -0700 Message-ID: In-Reply-To: <19c32ef4263ed3c2ab1624a43ae86c78.squirrel@email.polands.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: NFS issues on 8.0-BETA4 Thread-Index: AcoztxUv2JquA1NTSJGTKEOhBVZWHgAIsefg References: <9ef3bf09fa0e081eca3965e3f0e84f82.squirrel@email.polands.org> <19c32ef4263ed3c2ab1624a43ae86c78.squirrel@email.polands.org> From: "Li, Qing" To: "Doug Poland" , "Rick Macklem" Cc: freebsd-stable@freebsd.org, FreeBSD Current , Andrzej Tobola Subject: RE: NFS issues on 8.0-BETA4 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, 12 Sep 2009 18:51:03 -0000 Hi Doug, > > > Simply adding -o udp to my mount command made the NFS mount work > correctly. Qing, would it be beneficial to attempt the patch in light > of these findings? >=20 Have you tried the patch that I sent you privately? Does it work for you? Thanks, -- Qing From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 20:42:30 2009 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 38D491065670 for ; Sat, 12 Sep 2009 20:42:30 +0000 (UTC) (envelope-from gausus@gausus.net) Received: from dagobah.intersec.pl (dagobah.intersec.pl [91.192.226.10]) by mx1.freebsd.org (Postfix) with ESMTP id E27898FC19 for ; Sat, 12 Sep 2009 20:42:29 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dagobah.intersec.pl (Postfix) with ESMTP id A746A254002 for ; Sat, 12 Sep 2009 22:34:46 +0200 (CEST) X-Virus-Scanned: amavisd-new at intersec.pl Received: from dagobah.intersec.pl ([127.0.0.1]) by localhost (dagobah.intersec.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5IGv+KUaJ9sr for ; Sat, 12 Sep 2009 22:34:42 +0200 (CEST) Received: from dagobah.intersec.pl (dagobah.intersec.pl [91.192.226.10]) by dagobah.intersec.pl (Postfix) with ESMTP id EB19C254001 for ; Sat, 12 Sep 2009 22:34:41 +0200 (CEST) Date: Sat, 12 Sep 2009 22:34:41 +0200 (CEST) From: Maciej Jan Broniarz To: freebsd-stable@freebsd.org Message-ID: <1704894341.63251252787681862.JavaMail.root@dagobah.intersec.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [85.222.122.69] X-Mailer: Zimbra 5.0.16_GA_2921.UBUNTU8_64 (ZimbraWebClient - FF3.0 (Mac)/5.0.16_GA_2921.UBUNTU8_64) Subject: problem with link aggregation failover 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, 12 Sep 2009 20:42:30 -0000 Hello, I am trying to configure lagg failover mode on 7.2. I do: # ifconfig xl0 up # ifconfig fxp0 up # ifconfig lagg0 create # ifconfig lagg0 up laggproto failover laggport xl0 laggport fxp0 # dhclient lagg0 And all seems to work ok. Still I disconnect the cable from the master card the connection stops. Although fxp0 becomes active the connection is still dead. If I start pinging any host from that machine the conection comes back to live, but having ping in background all the time is not the solution. Am I doing something wrong or have I missed something in the configuration? Best regards, mjb From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 21:32:52 2009 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 B89D91065670 for ; Sat, 12 Sep 2009 21:32:52 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id 45E8B8FC16 for ; Sat, 12 Sep 2009 21:32:51 +0000 (UTC) Received: by bwz2 with SMTP id 2so1334268bwz.43 for ; Sat, 12 Sep 2009 14:32:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=z+5MjJAG0qJ9YBcjvLSDUv5v38S7WcvveMktZnLzxic=; b=WQwPVcw7v5I+wIMTg4wGfi1KWzIGxS1nhoRfQL9iJVcvr2kQgI/aL82Hs4nVuOgJFo u68ZKfR+kUmVOftTQycU5keMKTJItOVffJVqSaG1Am7zIfp38JtPN9zj/IASnjamMU2g 9Mg7TNwSVVClkLXnh744fxzI3wPsGW55pcDGs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=q4yMYyIoE+44vtmNDLhb7t3fxsw3NkpRH0CEORDzbaxFXKAP72h3fQDfyELRauzVC4 Jif6emDYG1vojeKiLMLckcI3X1f376PLXEehvS2uKrh4pBG8quhhs7peYkvTwfMALqAg AvUCFl2gkFrXJsSmGTphjiDUpeee00AMiI1ag= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.54.15 with SMTP id o15mr1711319fag.96.1252791170995; Sat, 12 Sep 2009 14:32:50 -0700 (PDT) In-Reply-To: References: Date: Sat, 12 Sep 2009 23:32:50 +0200 X-Google-Sender-Auth: 56b95be0a9e4b209 Message-ID: <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com> From: Attilio Rao To: Dan Naumov Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD-STABLE Mailing List Subject: Re: 7.2-release/amd64: panic, spin lock held too long 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, 12 Sep 2009 21:32:52 -0000 2009/7/7 Dan Naumov : > I just got a panic following by a reboot a few seconds after running > "portsnap update", /var/log/messages shows the following: > > Jul 7 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel > Jul 7 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock > 1) held by 0xffffff00017d8370 (tid 100054) too long > Jul 7 03:49:38 atom kernel: panic: spin lock held too long > > /var/crash looks empty. This is a system running official 7.2-p1 > binaries since I am using freebsd-update to keep up with the patches > (just updated to -p2 after this panic) running with very low load, > mostly serving files to my home network over Samba and running a few > irssi instances in a screen. What do I need to do to catch more > information if/when this happens again? Dan, is that machine equipped with Hyperthreading? Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 21:51:32 2009 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 A376D1065670 for ; Sat, 12 Sep 2009 21:51:32 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from mail.stillbilde.net (d80.iso100.no [81.175.61.195]) by mx1.freebsd.org (Postfix) with ESMTP id 6713C8FC0C for ; Sat, 12 Sep 2009 21:51:32 +0000 (UTC) Received: from [192.168.4.6] (unknown [192.168.4.6]) (Authenticated sender: svein) by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id 30C3B21 for ; Sat, 12 Sep 2009 23:35:11 +0200 (CEST) Message-ID: <4AAC140F.2070203@stillbilde.net> Date: Sat, 12 Sep 2009 23:35:11 +0200 From: "Svein Skogen (listmail account)" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Question regarding vlans and lagg 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, 12 Sep 2009 21:51:32 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can the vlan "vlandev" be a lagg port of multiple physical interfaces (for redundancy)? //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg Østli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- If you really are in a hurry, mail me at svein-mobile@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqsFA8ACgkQODUnwSLUlKQNNACgscocpg6X5c6s7Wm2eF8JyyMg jV8AnjE8B4BzGn9/pSVrkB9MLJBY5SDR =lZ9v -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 22:02:37 2009 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 696FD106566B; Sat, 12 Sep 2009 22:02:37 +0000 (UTC) (envelope-from dan.naumov@gmail.com) Received: from mail-yx0-f193.google.com (mail-yx0-f193.google.com [209.85.210.193]) by mx1.freebsd.org (Postfix) with ESMTP id 0D0EA8FC08; Sat, 12 Sep 2009 22:02:36 +0000 (UTC) Received: by yxe31 with SMTP id 31so2682822yxe.29 for ; Sat, 12 Sep 2009 15:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YtMzH1mSV9YEVUWRMcanHxoCfJdH5KJUICNIm0eDZC4=; b=ArRBWI8vxGn17Z6DAFFhsrmVoIpLNgH34A2UrV72LGqsc665c8SnK9DvmKHgpZ/AZy WNWnYhd0DvDmnJ9GB7vWEuP2oCUt8TnuzS2bWKKZKoRu+MLJGK4XKwVyG+ijp8vkhyCi Xzq6boT9+Yc5hbB1j1fSFK0ctfh9Sqfv6ENdk= 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=j3tCf3B9JS0PvGlYtpRADZIBQq8Br6H1YFoMy1XPPydQjH07uBq5tLEDfAyI70t54F jg97CVniPYfs6PV+NJXypCcsr+SJwwbkJVxHkscDSeHl9AwSWOToJ4YVvnD/IZyEtBEM BSaJB/aLe+I9Xlt4Cha2DdwERYLazOK5Fo7r0= MIME-Version: 1.0 Received: by 10.101.52.13 with SMTP id e13mr5058357ank.0.1252792956152; Sat, 12 Sep 2009 15:02:36 -0700 (PDT) In-Reply-To: <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com> References: <3bbf2fe10909121432x7bd4f7es497e9431c4e520d6@mail.gmail.com> Date: Sun, 13 Sep 2009 01:02:36 +0300 Message-ID: From: Dan Naumov To: Attilio Rao Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD-STABLE Mailing List Subject: Re: 7.2-release/amd64: panic, spin lock held too long 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, 12 Sep 2009 22:02:37 -0000 On Sun, Sep 13, 2009 at 12:32 AM, Attilio Rao wrote: > 2009/7/7 Dan Naumov : >> I just got a panic following by a reboot a few seconds after running >> "portsnap update", /var/log/messages shows the following: >> >> Jul =A07 03:49:38 atom syslogd: kernel boot file is /boot/kernel/kernel >> Jul =A07 03:49:38 atom kernel: spin lock 0xffffffff80b3edc0 (sched lock >> 1) held by 0xffffff00017d8370 (tid 100054) too long >> Jul =A07 03:49:38 atom kernel: panic: spin lock held too long >> >> /var/crash looks empty. This is a system running official 7.2-p1 >> binaries since I am using freebsd-update to keep up with the patches >> (just updated to -p2 after this panic) running with very low load, >> mostly serving files to my home network over Samba and running a few >> irssi instances in a screen. What do I need to do to catch more >> information if/when this happens again? > > Dan, is that machine equipped with Hyperthreading? > > Attilio Yes. It's an Intel Atom 330, which is a dualcore CPU with HT (4 cores visible in "top" as a result) - Dan From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 23:33:25 2009 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 734CB106566C for ; Sat, 12 Sep 2009 23:33:25 +0000 (UTC) (envelope-from gelraen.ua@gmail.com) Received: from mail-bw0-f206.google.com (mail-bw0-f206.google.com [209.85.218.206]) by mx1.freebsd.org (Postfix) with ESMTP id F00C48FC08 for ; Sat, 12 Sep 2009 23:33:24 +0000 (UTC) Received: by bwz2 with SMTP id 2so1356408bwz.43 for ; Sat, 12 Sep 2009 16:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type:content-transfer-encoding; bh=xJqKb7xoQGQfbdATrEP5OmMiGSZOByz00GMO8wY9ON8=; b=oYFi8vFBANJVcfM2FARPLo+xhraU1rzmNUf0P9Be9LM3tDbN0FNUm0o2ABEy1Tc/TP 1I9/fl2+BlztYDiuY0P6pliRhZwrTg+5y1D/KFiAUoc0ZV/ol529q/i9iXd0ciQRBCXC 2PGCZqsjKAM5xNe1qgim4MVYF3OLN/K+URGRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; b=pCXy8v2b87de6/xzuD0mwmAe61QzHP8tBP1ZLpblAoG8sZPsFR6M2WAXmBcQb5Cwuu V6eKmyFIQyHtVdf09LRYfRHqPIDr/aLpEMrUy8lZucx8WwPl2NAqYO9Nx0c+uFv8N7EO aNYKBVNjhy8AHS/AfO4S9aDobDV+iLzLEuFYs= Received: by 10.204.34.5 with SMTP id j5mr3455156bkd.5.1252797122876; Sat, 12 Sep 2009 16:12:02 -0700 (PDT) Received: from imax ([91.202.129.130]) by mx.google.com with ESMTPS id 21sm3826674fkx.4.2009.09.12.16.12.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 12 Sep 2009 16:12:02 -0700 (PDT) Date: Sun, 13 Sep 2009 02:11:52 +0300 From: Maxim Ignatenko To: "Svein Skogen (listmail account)" Message-ID: <20090913021152.5b16bb8d@imax> In-Reply-To: <4AAC140F.2070203@stillbilde.net> References: <4AAC140F.2070203@stillbilde.net> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: base64 Cc: freebsd-stable@freebsd.org Subject: Re: Question regarding vlans and lagg 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, 12 Sep 2009 23:33:25 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpPbiBTYXQs IDEyIFNlcCAyMDA5IDIzOjM1OjExICswMjAwDQoiU3ZlaW4gU2tvZ2VuIChsaXN0bWFpbCBhY2Nv dW50KSIgPHN2ZWluLWxpc3RtYWlsQHN0aWxsYmlsZGUubmV0PiB3cm90ZToNCg0KPiBDYW4gdGhl IHZsYW4gInZsYW5kZXYiIGJlIGEgbGFnZyBwb3J0IG9mIG11bHRpcGxlIHBoeXNpY2FsIGludGVy ZmFjZXMNCj4gKGZvciByZWR1bmRhbmN5KT8NCj4gDQpBRkFJSywgbm8sIGJ1dCB5b3UgY2FuIHRy eSB0byBhY2hpZXZlIHRoZSBzYW1lIGVmZmVjdCB3aXRoIG5nX29uZTJtYW55KDQpK25nX3ZsYW4o NCkNCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9uOiBHbnVQRyB2Mi4wLjEy IChGcmVlQlNEKQ0KDQppUUVjQkFFQkFnQUdCUUpLckNxK0FBb0pFREtuMlhyTXFRam92amdILzJH dnYrbjd1YTZ1M0Flck9tQS83K3RSDQp5ZzRzaXJUYzE1WjBDakl3c2pwbW9ZYTRKMVV2VUxySjJw ZEJDYTZJQUhQYmRTSUM3LzNTVXZLOTFNL2cvd0tXDQprUTVRaStpdHdJQXA3cXBDeHNQanlNaVNP YkxuODdOcy9qOWZUSkhBN2ptdnZ3YkczZlVPMzdxL0NpTDhUcm9YDQpnWTRETzFIa3pFbjNxNnQ2 NTRsdklCQ0NHNGJCZENSZmxta3RkWjV5S1VFbitibVZtT0kyaVJwWVY0Y3p3R1ZFDQovdVZVdlNJ WmgybDRHc0lDY0NYMmtnK2ZCQUo3VjB6cm5JMmVyTjFVbys3RGRrZldzV0kwZjFXR1Zsb0Q5Z0hX DQpzWUNvbjIzUlRUemN0cWIzOXB3OW1tWU5oTkxHd0xOalk4eFRac1pyZTBxdTZEZkp1dlhEWkw1 OEc0TEMxbGs9DQo9QU55Qg0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-stable@FreeBSD.ORG Sat Sep 12 23:49:07 2009 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 54E4F106566C for ; Sat, 12 Sep 2009 23:49:07 +0000 (UTC) (envelope-from amarat@ksu.ru) Received: from mx.kzn.ru (mx.kzn.ru [194.85.243.38]) by mx1.freebsd.org (Postfix) with ESMTP id 515958FC12 for ; Sat, 12 Sep 2009 23:49:06 +0000 (UTC) Authentication-Results: iout.kzn.ru; dkim=neutral (message not signed) header.i=none Received-SPF: None identity=pra; client-ip=193.232.252.56; receiver=iout.kzn.ru; envelope-from="amarat@ksu.ru"; x-sender="amarat@ksu.ru"; x-conformance=sidf_compatible Received-SPF: None identity=mailfrom; client-ip=193.232.252.56; receiver=iout.kzn.ru; envelope-from="amarat@ksu.ru"; x-sender="amarat@ksu.ru"; x-conformance=sidf_compatible Received-SPF: None identity=helo; client-ip=193.232.252.56; receiver=iout.kzn.ru; envelope-from="amarat@ksu.ru"; x-sender="postmaster@ruby.ksu.ru"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuAEAIfQq0rCVfWh/2dsb2JhbACBU8lGCI4rgkAIHoEyBYFWYg X-IronPort-AV: E=Sophos;i="4.44,377,1249243200"; d="p7s'?scan'208";a="5067065" Received: from mail.ksu.ru (HELO ruby.ksu.ru) ([193.232.252.56]) by iout.kzn.ru with ESMTP; 13 Sep 2009 03:49:02 +0400 X-Pass-Through: Kazan State University Network Received: from zealot.ksu.ru ([194.85.245.161]) by ksu.ru (8.13.4/8.13.4) with ESMTP id n8CMpPmt009644; Sat, 12 Sep 2009 22:51:25 GMT Received: from zealot.ksu.ru (localhost.lnet [127.0.0.1]) by zealot.ksu.ru (8.14.3/8.14.3) with ESMTP id n8CNmPKD070117; Sun, 13 Sep 2009 03:48:25 +0400 (MSD) (envelope-from amarat@ksu.ru) Message-ID: <4AAC3343.5030806@ksu.ru> Date: Sun, 13 Sep 2009 03:48:19 +0400 From: "Marat N.Afanasyev" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.22) Gecko/20090704 SeaMonkey/1.1.17 MIME-Version: 1.0 To: "Svein Skogen (listmail account)" References: <4AAC140F.2070203@stillbilde.net> In-Reply-To: <4AAC140F.2070203@stillbilde.net> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090506060404070004030604" Cc: freebsd-stable@freebsd.org Subject: Re: Question regarding vlans and lagg 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, 12 Sep 2009 23:49:07 -0000 This is a cryptographically signed message in MIME format. --------------ms090506060404070004030604 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Svein Skogen (listmail account) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Can the vlan "vlandev" be a lagg port of multiple physical interfaces > (for redundancy)? > > //Svein > > i think that you should try the following: 1. join two ports on switch to trunk, say vport1 2. assign allowed vlans to this vport1 3. create lagg0 on freebsd 4. create vlan interfaces on freebsd using vlandev lagg0 and i suppose it just should work ;) -- SY, Marat --------------ms090506060404070004030604 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII8zCC AtQwggI9oAMCAQICEHpsMo6nkbUVegxjAzzxYCkwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDQwMTE5MTUxOFoX DTEwMDQwMTE5MTUxOFowPzEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEcMBoG CSqGSIb3DQEJARYNYW1hcmF0QGtzdS5ydTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC ggEBALqa7MfgjbsxmgpTOKxAN7w+cFViFA8NrULAARwVQJQJCnVRGf3i97EwNdLE8VTNniU4 ybS4gtLsy9gfNuuyPV2AJESpgrxaG+KZyHu1f6P4e31YBbnbtWVTUxZ3U/vWoL+BOAOI4S84 Cx834a4uYK75WhpZKd56qet5loyn9N1wBZNgCh9AwU31lA/Q0iCSKpEIxuhbElNXHNnqAlts CtNXsKgsT8mP7QI52h0cBOPSZqvz++e/wruJGgKeCECqo8ftwwya3CYkH1lhH2Q1zeXwez1E 1+solM48odH+odn29ctmOqr3PzZfmBJyGFf5FagTKNia/ys48yBtVU/RXHsCAwEAAaMqMCgw GAYDVR0RBBEwD4ENYW1hcmF0QGtzdS5ydTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUA A4GBAG4Pj7KRSJ/M28KNynJOPCHg26L15S9OfQ+ckMaPPDRAejtdlUdCgkoyD9d1Du/amAk6 A3NcY2I/MsFW2vSonQfU+7cJZiyuhfw7wQlOovCx7USw1dmF6u3EljWZV+Kg4Vi3vN2dPyJx tv8li9McWQoMLmm5zzFGGRaSRnnrnZFsMIIC1DCCAj2gAwIBAgIQemwyjqeRtRV6DGMDPPFg KTANBgkqhkiG9w0BAQUFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1 bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElz c3VpbmcgQ0EwHhcNMDkwNDAxMTkxNTE4WhcNMTAwNDAxMTkxNTE4WjA/MR8wHQYDVQQDExZU aGF3dGUgRnJlZW1haWwgTWVtYmVyMRwwGgYJKoZIhvcNAQkBFg1hbWFyYXRAa3N1LnJ1MIIB IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuprsx+CNuzGaClM4rEA3vD5wVWIUDw2t QsABHBVAlAkKdVEZ/eL3sTA10sTxVM2eJTjJtLiC0uzL2B8267I9XYAkRKmCvFob4pnIe7V/ o/h7fVgFudu1ZVNTFndT+9agv4E4A4jhLzgLHzfhri5grvlaGlkp3nqp63mWjKf03XAFk2AK H0DBTfWUD9DSIJIqkQjG6FsSU1cc2eoCW2wK01ewqCxPyY/tAjnaHRwE49Jmq/P757/Cu4ka Ap4IQKqjx+3DDJrcJiQfWWEfZDXN5fB7PUTX6yiUzjyh0f6h2fb1y2Y6qvc/Nl+YEnIYV/kV qBMo2Jr/KzjzIG1VT9FcewIDAQABoyowKDAYBgNVHREEETAPgQ1hbWFyYXRAa3N1LnJ1MAwG A1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEFBQADgYEAbg+PspFIn8zbwo3Kck48IeDbovXlL059 D5yQxo88NEB6O12VR0KCSjIP13UO79qYCToDc1xjYj8ywVba9KidB9T7twlmLK6F/DvBCU6i 8LHtRLDV2YXq7cSWNZlX4qDhWLe83Z0/InG2/yWL0xxZCgwuabnPMUYZFpJGeeudkWwwggM/ MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMM V2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25z dWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYD VQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNv bmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5 WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRk LjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2 vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9 A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEw EgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0 ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0R BCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GB AEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZ Ohl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVN d+NWIXiC3CEZNd4ksdMdRv9dX2VPMYIDZDCCA2ACAQEwdjBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEHpsMo6nkbUVegxjAzzxYCkwCQYFKw4DAhoF AKCCAcMwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDkwOTEy MjM0ODE5WjAjBgkqhkiG9w0BCQQxFgQUJDBY5PnBLlFACLrzKnS3XX/W1igwUgYJKoZIhvcN AQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYF Kw4DAgcwDQYIKoZIhvcNAwICASgwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhB6bDKOp5G1FXoMYwM88WApMIGHBgsq hkiG9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0 aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1 aW5nIENBAhB6bDKOp5G1FXoMYwM88WApMA0GCSqGSIb3DQEBAQUABIIBAIzcStBD9M0AkbM0 eam1Wxec3AJ0GJBHLA4Ir7JpKaaD+bx/60UoY/DK+MNS93elM5Bb2GvZaKxFp91Ux0x4s9lc 5PVyoA+4K+KZlXs8y1RZDf7OVRXkVv8Te7wCI3bUegOYTELHpwVLzD9XZMaPsRd/TvI+reRF SRM0GzPNcf5VdxuPA3DLLAImWGKa1Bh3XVMVON+n/gccQMnU3uXtRBsDwRMKEfOtCgOItlzE px97M07A+lb6h1Nx3Z4IUKUnujOTBIqHmrKjqrhpGsVuti9EAKYI1DGiAoTWTQ2C+8gIOBxZ lGA/d1Z+LhfwEP9a0CC6mwzVpI+HCCJLB9xf5toAAAAAAAA= --------------ms090506060404070004030604--