From owner-freebsd-amd64@FreeBSD.ORG Sun May 26 23:40:28 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 32B91D57; Sun, 26 May 2013 23:40:28 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 36E0D29C; Sun, 26 May 2013 23:40:27 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4QNeQHt076516; Sun, 26 May 2013 23:40:26 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4QNeQ0w076515; Sun, 26 May 2013 23:40:26 GMT (envelope-from linimon) Date: Sun, 26 May 2013 23:40:26 GMT Message-Id: <201305262340.r4QNeQ0w076515@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: ports/178957: graphics/png fails to extract archive after download X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2013 23:40:28 -0000 Old Synopsis: Fails to extract archive after download New Synopsis: graphics/png fails to extract archive after download Responsible-Changed-From-To: freebsd-amd64->freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 26 23:40:02 UTC 2013 Responsible-Changed-Why: ports PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=178957 From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 10:58:55 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8BC80FB0; Mon, 27 May 2013 10:58:55 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 00BF15ED; Mon, 27 May 2013 10:58:54 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r4RAwix8018563; Mon, 27 May 2013 13:58:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r4RAwix8018563 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r4RAwi4N018562; Mon, 27 May 2013 13:58:44 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 27 May 2013 13:58:44 +0300 From: Konstantin Belousov To: arch@freebsd.org, amd64@freebsd.org Subject: x86 IOMMU support (DMAR) Message-ID: <20130527105844.GC3047@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QMUNogrXulKRzqi3" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 10:58:55 -0000 --QMUNogrXulKRzqi3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline For the several months, I worked (and continue the work now) on the driver for the Intel VT-d for FreeBSD. The VT-d is sold as the I/O Virtualization technology, but in essence it is a DMA addresses remapping engine, i.e. it is advanced and improved I/O MMU, as also found on other big-iron machines, e.g. PowerPC or Sparc. See the Intel document titled 'Intel Virtualization Technology for Directed I/O Architecture Specification' and chipsets datasheets for the description of the facility. The development was greatly facilitated by Jim Harris from Intel who provided me the access to the Sandy and Ivy Bridge north bridge documentation. John Baldwin patiently educated me about newbus and helped developing required hooks for integration with the existing code. The core hardware element of the VT-d is DMA remap unit, referenced as DMAR both in the documentation and in the source code. Besides DMA remap, VT-d also allows to do remapping of the MSI/MSI-X interrupt messages. FreeBSD could utilize the functionality for the interrupt rebalancing, instead of reprogramming msi registers of the PCI devices, but this part is not (yet) implemented. For the FreeBSD architecture, DMAR naturally fits as busdma engine, making it possible to eliminate bounce page copying. Another great benefit of the DMAR use is the reliability and security improvements, since DMA transfers are only allowed to the memory areas explicitely designated by the device driver as buffers. As noted by Jim Harris, this security angle could find a use in the NTB driver. The existing busdma code for x86 was split into generic interface, kept in the busdma_machdep.c, and bouncing implementation in the busdma_bounce.c. The DMAR-based implementation, which calls the DMAR core, is located in the busdma_dmar.c. There is no KPI provided to manage DMARs, but I plan to implement the proper interface after discussing the needs of the bhyve. I tried to support both i386 and amd64, but for i386 the limited KVA, together with the busdma interface structure of never sleeping from the driver calls, make some promises of IOMMU less strict. For instance, to unload the map, code needs to transiently map the DMAR page table pages, which require sleepable allocations of sf buffers. As result, map unload on i386 is done asynchronously in the taskqueue context, which makes it possible for the buggy device driver or hardware to perform the transfer to freed pages for some time after unload. This problem is not present for amd64 port. For the same reason of busdma KPI, I cannot use queued invalidation both for i386 and amd64. At the moment the code makes the 1:1 relations between device contexts and domains, which is fine for busdma. To support PCI pass-through into the virtualized machines, the relations should be changed to N:1 contexts to domains, which is planned but currently is not yet done. Overall state of the code is that I can boot multiuser over the network from if_igb(4) or if_bce(4), and can use ahci(4) and ata(4) attached disks without corrupting UFS volumes. Uhci(4) has known issues due to too late establishment of the RMRR mappings. Extensive testing of the already written code is not done yet. Plans include - providing the external KPI for the VMM consumers - support ATS - making it possible to select busdma_dmar or busdma_bounce for individual PCI functions - the stabilization work. Also, by converting the ISA DMA implementation to use the busdma KPI, it is possible to make the floppies work reliably again ! It is known that IOMMU adds overhead due to the mapping and unmapping for each I/O. DMAR implementations usually have some erratas, as well as PCIe devices sometime do not completely follow the specification, causing misbehaviour with remapping enabled. For this reason I do not plan to enable IOMMU by default, and intend to provide a possibility to route individual PCI devices to the bounce busdma implementation. http://people.freebsd.org/~kib/misc/DMAR.1.patch --QMUNogrXulKRzqi3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRozxjAAoJEJDCuSvBvK1BrFgP/0g7HlYUyg27GjeBy/s7iBsr 1Q3j6gSZM89us0r7wGKAw/DtNWaggD5aahxeab2ZJkDxZIojGAnEDDsEPo42KLAc 9ez/gvLH2AMNXZGkfG90MyP6GFg312ohSwCYfrMwFrU4YG5Hi147JlHy6iUw0wrY Pny/3iYDn/PChwsoRVq8D6wCdy1nXypGUSCc8kbViKOPAxUTDtqL+lZnvtfaOGHZ cqbc78f9izPewPWj5xTcC+lnd8v0kql4+qPCuSZorj2ZjQEbSKsPMW5ZcureGcFV pnwH+49zcn6Ej9deSJEK+tYdWqonTf3liYyhHv8Uu7MNVZ6swEUObgLHWjbvGkxs O0m7sanOvDJ1gLNcmoQvzj24T5F3WExOAHnMq7AermdnpJHFu3Z05J/eCwVFNkR8 srhvl3/P5L5N+o71uV+FoLE7JDf3qwlB77QJqeuPcYp3mVwWhhWohgPNSjle4Nob O1EsLBW7YAoN992nm48DIbG40qdrpOjkEVWc1pqL0tFOZSUc6xF9HrXNKa/jVlEo AJLhJII/0nDrzKhrLPqY4hGZVYyiucbh41Lk5dCuPnc0BEP4x2ZKmzVnWSbXvuIx 86QpsGl9+S4p/HdZfUzU/3NZ/IbSTAwzxQdymH+L0AhTXD/rF8XQeyJ85gr19MbS iz23xjIkWBh5jR5oPUlb =9e72 -----END PGP SIGNATURE----- --QMUNogrXulKRzqi3-- From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 11:06:42 2013 Return-Path: Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A05622ED for ; Mon, 27 May 2013 11:06:42 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 90CE86AF for ; Mon, 27 May 2013 11:06:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4RB6gNf015939 for ; Mon, 27 May 2013 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4RB6g0k015937 for freebsd-amd64@FreeBSD.org; Mon, 27 May 2013 11:06:42 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 May 2013 11:06:42 GMT Message-Id: <201305271106.r4RB6g0k015937@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 11:06:42 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/178792 amd64 -march=native fails with clang on certain CPU's o amd64/178357 amd64 [patch] export CPU physical and virtual address sizes o amd64/178247 amd64 linker.hints erroneously included in 9.1-RELEASE-p3 bi o amd64/176835 amd64 Fatal trap 12: page fault while in kernel mode o amd64/176474 amd64 kernel panic o amd64/175725 amd64 Audio through USB has not as good hi quality as it has o amd64/175655 amd64 When enabled tty console OS hang during boot o amd64/175370 amd64 kernel panic the rebuild kernel with vimage options in o amd64/175282 amd64 Freebsd 9.1 release amd64, mb Intel D525MW, not worked o amd64/175129 amd64 laptop won't suspend on lid close o amd64/174679 amd64 Intel i5 laptop overheats and shuts down [regression] o amd64/173869 amd64 buildworld breaks with clang o amd64/173680 amd64 9.1rc3 installer hangs at "rootpass" o amd64/173502 amd64 Patch inhibition of warnings that appear in the combin o amd64/173465 amd64 FreeBSD 9.1 restarts in random fashion after upgrade t o amd64/173311 amd64 FreeBSD 9.1 RC2 , 12 servers restart in random fashion o amd64/173235 amd64 Have received two crashes within 1 day after installin o amd64/172926 amd64 [boot] booting hangs after 9.1-RC2 install in 2nd (MBR o amd64/171835 amd64 bsdinstall abort on Dell PowerEdge R420 with PERC H310 o amd64/171814 amd64 [panic] bioq_init or bioq_remove (unsure which) o amd64/171701 amd64 [install] 9.0-rel amd64 installer 'guided' or 'manual' o amd64/171250 amd64 ldd32 cannot find some i386 libraries o amd64/171110 amd64 Upgrade 9.1-BETA1 > RC1 issue o amd64/170487 amd64 [boot] Thinkpad X61s cannot boot 9.1-BETA1 o amd64/170351 amd64 [kernel] [patch] amd64: 64-bit process can't always ge o amd64/170115 amd64 Serial boot broken in 9.0 o amd64/168659 amd64 [boot] FreeBSD 9 - Crash upon booting off install CD ( o amd64/167582 amd64 Compile of MySQL NDB Cluster Fails 8.2 AMD64 o amd64/167543 amd64 [kernel] Install FreeBSD can show error message with c o amd64/167393 amd64 [boot] MacBook4,1 hangs on SMP boot o amd64/166639 amd64 [boot] Syscons issue Intel D2700 o amd64/166229 amd64 [boot] Unable to install FreeBSD 9 on Acer Extensa 522 o amd64/165850 amd64 [build] 8.3-RC1 (amd64): world doesn't build with CPUT o amd64/165845 amd64 [build] Unable to build kernel on 8.2-STABLE o amd64/165351 amd64 [boot] Error while installing or booting the freeBSD O o amd64/164773 amd64 [boot] 9.0 amd64 fails to boot on HP DL145 G3 [regress o amd64/164707 amd64 FreeBSD 9 installer does not work with IBM uefi o amd64/164643 amd64 Kernel Panic at 9.0-RELEASE o amd64/164619 amd64 when logged in as root the user and group applications o amd64/164457 amd64 [install] Can't install FreeBSD 9.0 (amd64) on HP Blad o amd64/164301 amd64 [install] 9.0 - Can't install, no DHCP lease o amd64/164136 amd64 after fresh install 8.1 release or 8.2 release the har o amd64/164116 amd64 [boot] FreeBSD 9.0-RELEASE installations mediums fails o amd64/164089 amd64 FreeBSD-9.0-RELEASE-amd64-memstick.img does not boot o amd64/164073 amd64 /etc/rc warning after booting o amd64/164036 amd64 [keyboard] Moused fails on 9_0_RELENG o amd64/163736 amd64 Freebsd 8.2 with MPD5 and about 100 PPPoE clients pani o amd64/163710 amd64 setjump in userboot.so causes stack corruption o amd64/163625 amd64 Install problems of RC3 amd64 on ASRock N68 GE3 UCC o amd64/163568 amd64 hard drive naming o amd64/163285 amd64 when installing gnome2-lite not all dependent packages o amd64/163284 amd64 print manager failed to install correctly o amd64/163114 amd64 no boot on Via Nanao netbook Samsung NC20 o amd64/163092 amd64 FreeBSD 9.0-RC2 fails to boot from raid-z2 if AHCI is o amd64/163048 amd64 normal user cant mount ntfs-3g o amd64/162936 amd64 fails boot and destabilizes other OSes on FreeBSD 9 RC o amd64/162489 amd64 After some time X blanks the screen and does not respo o amd64/162314 amd64 not able to install FreeBSD-8.2-RELEASE-amd64-dvd1 as o amd64/162170 amd64 Unable to install due to freeze at "run_interrupt_driv o amd64/161974 amd64 FreeBSD 9 new installer installs succesful, renders ma o kern/160833 amd64 Keyboard USB doesn't work o amd64/157386 amd64 [powerd] Enabling powerd(8) with default settings on I o amd64/156106 amd64 [boot] boot0 fails to start o amd64/155135 amd64 [boot] Does Not Boot On a Very Standard Hardware o amd64/154957 amd64 [boot] Install boot CD won't boot up - keeps rebooting o amd64/154629 amd64 [panic] Fatal trap 9: general protection fault while i o amd64/153935 amd64 [hang] system hangs while trying to do 'shutdown -h no o amd64/153831 amd64 [boot] CD bootloader won't on Tyan s2912G2nr o amd64/153496 amd64 [hyper-v] [install] Install on Hyper-V leaves corrupt o amd64/153372 amd64 [panic] kernel panic o amd64/153175 amd64 [amd64] Kernel Panic on only FreeBSD 8 amd64 o amd64/152874 amd64 [install] 8.1 install fails where 7.3 works due to lac o amd64/152430 amd64 [boot] HP ProLiant Microserver n36l cannot boot into i o amd64/145991 amd64 [NOTES] [patch] Add a requires line to /sys/amd64/conf o amd64/144405 amd64 [build] [patch] include /usr/obj/lib32 in cleanworld t s amd64/143173 amd64 [ata] Promise FastTrack TX4 + SATA DVD, installer can' p amd64/141413 amd64 [hang] Tyan 2881 m3289 SMDC freeze o amd64/137942 amd64 [pci] 8.0-BETA2 having problems with Asus M2N-SLI-delu o amd64/127640 amd64 [amd64] gcc(1) will not build shared libraries with -f o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c 80 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 12:27:07 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 82EBEC44; Mon, 27 May 2013 12:27:07 +0000 (UTC) (envelope-from jlh@FreeBSD.org) Received: from caravan.chchile.org (caravan.chchile.org [178.32.125.136]) by mx1.freebsd.org (Postfix) with ESMTP id 504C8EDC; Mon, 27 May 2013 12:27:07 +0000 (UTC) Received: by caravan.chchile.org (Postfix, from userid 1000) id 8071FBC3D1; Mon, 27 May 2013 12:27:00 +0000 (UTC) Date: Mon, 27 May 2013 14:27:00 +0200 From: Jeremie Le Hen To: Konstantin Belousov Subject: Re: x86 IOMMU support (DMAR) Message-ID: <20130527122700.GD70224@caravan.chchile.org> Mail-Followup-To: Konstantin Belousov , arch@freebsd.org, amd64@freebsd.org References: <20130527105844.GC3047@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130527105844.GC3047@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Mon, 27 May 2013 13:35:24 +0000 Cc: amd64@freebsd.org, arch@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 12:27:07 -0000 Hi kib, On Mon, May 27, 2013 at 01:58:44PM +0300, Konstantin Belousov wrote: > For the several months, I worked (and continue the work now) on the > driver for the Intel VT-d for FreeBSD. The VT-d is sold as the I/O > Virtualization technology, but in essence it is a DMA addresses > remapping engine, i.e. it is advanced and improved I/O MMU, as also > found on other big-iron machines, e.g. PowerPC or Sparc. See the > Intel document titled 'Intel Virtualization Technology for Directed > I/O Architecture Specification' and chipsets datasheets for the > description of the facility. > > [...] > > http://people.freebsd.org/~kib/misc/DMAR.1.patch Which CPU flag is needed to be able to test this? My -CURRENT machine has: CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1869.90-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Family = 0x6 Model = 0xf Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 16:15:21 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E49CBD19; Mon, 27 May 2013 16:15:21 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 5C909CCC; Mon, 27 May 2013 16:15:21 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r4RGF5Wp083361; Mon, 27 May 2013 19:15:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r4RGF5Wp083361 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r4RGF5fE083359; Mon, 27 May 2013 19:15:05 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 27 May 2013 19:15:05 +0300 From: Konstantin Belousov To: arch@freebsd.org, amd64@freebsd.org Subject: Re: x86 IOMMU support (DMAR) Message-ID: <20130527161505.GE3047@kib.kiev.ua> References: <20130527105844.GC3047@kib.kiev.ua> <20130527122700.GD70224@caravan.chchile.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/liuGKheDV9E18bs" Content-Disposition: inline In-Reply-To: <20130527122700.GD70224@caravan.chchile.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 16:15:22 -0000 --/liuGKheDV9E18bs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 27, 2013 at 02:27:00PM +0200, Jeremie Le Hen wrote: > Hi kib, >=20 > On Mon, May 27, 2013 at 01:58:44PM +0300, Konstantin Belousov wrote: > > For the several months, I worked (and continue the work now) on the > > driver for the Intel VT-d for FreeBSD. The VT-d is sold as the I/O > > Virtualization technology, but in essence it is a DMA addresses > > remapping engine, i.e. it is advanced and improved I/O MMU, as also > > found on other big-iron machines, e.g. PowerPC or Sparc. See the > > Intel document titled 'Intel Virtualization Technology for Directed > > I/O Architecture Specification' and chipsets datasheets for the > > description of the facility. > >=20 > > [...] > >=20 > > http://people.freebsd.org/~kib/misc/DMAR.1.patch >=20 > Which CPU flag is needed to be able to test this? >=20 > My -CURRENT machine has: >=20 > CPU: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz (1869.90-MHz K8-clas= s CPU) > Origin =3D "GenuineIntel" Id =3D 0x6f6 Family =3D 0x6 Model =3D 0xf = Stepping =3D 6 > Features=3D0xbfebfbff > Features2=3D0xe3bd > AMD Features=3D0x20100800 > AMD Features2=3D0x1 The feature is announced by the ACPI table. You should use recent HEAD, and do acpidump -t | grep DMAR. If the DMAR table is present, you have VT-d enabled. Presence of VT-d is determined by: - north bridge. In other words, for older machines with Core2 and earlier CPUs, north bridge chip of the chipset should support VT-d, for newer Core iX, the north bridge inside the CPU. - motherboard manufacturer, by the way of BIOS properly configuring the DMARs and filling the right table. Some motherboard vendors offer the knob in the BIOS setup, which enables VT-d. One note: KMS-enabled Intel GPU driver is completely incompatible with VT-d right now. Besides the fact the GPU MMU does not make the calls to configure remapper, there are many erratas regarding interaction between IOMMU and GPU, for all generations of chipsets, except possible Ivy Bridge. --/liuGKheDV9E18bs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRo4aIAAoJEJDCuSvBvK1BupEP/jrkM4UbYL67/r58ctSVHFOJ o+yIn44QieqkVZ6TTx8FpR2kMaRM/oOf1gJrIETXtcUOXE7b38mPmnECnVMUyBUN l2PGXuBNud0qzzkESWnY/Kvgh7oYq8mCUC7E2c8hIgrpNrbgsbOBFO6neozI3ice eUlLCA6nXSl3NSbM3kGwGEMimqoCGZvNFNOJPr+8sDvW4LSmYduJ92afwcbYCm7E TxekMNC/PbqXGCyP6nFLmYSZvpNa3rJdAYX9AIjIrBfjINg14MNaTxNj/qanR2kS /vqEhEjsnhPK7ulwexWmT17wRqDGkT8BPaAd+Qh8+yWw98UrwFlDuOkPQ6YqYlV0 YOAiVoXjUvsFtBi4Mac/rUjnzdKj2eq9K/w38alK4DZEwScXDHAtPS2EPP/sBb2M 8VAssK6qL+LifdGSBycOwJboUykCgdvxkmpGEMXWwkHhqqE5OncfEm+R9udCUrqK S3eTNv9nffxv9T8cHzwtwAFU1auUUhTNpS3heQAWv4KqQnJ+EkJZPRBmCewFEX6I NlqllWD4mbuT5Y1nMv90Dd8yzZ/kQZZKxfizszKtlY04n/OvqSGZPH/Sbti/UYw9 dpF4wgY3QGD/g7IrjoPX3T4r8YSqAJOsfOWaUO5WGxz6zxwRzBvxyxQCWp0pK3no UISgUlaIR3SfhodbRTmQ =JkOh -----END PGP SIGNATURE----- --/liuGKheDV9E18bs-- From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 16:44:44 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6F4DE91C for ; Mon, 27 May 2013 16:44:44 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm15-vm3.bullet.mail.ne1.yahoo.com (nm15-vm3.bullet.mail.ne1.yahoo.com [98.138.91.145]) by mx1.freebsd.org (Postfix) with ESMTP id 84D39DE7 for ; Mon, 27 May 2013 16:44:43 +0000 (UTC) Received: from [98.138.90.54] by nm15.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2013 16:41:36 -0000 Received: from [98.138.226.62] by tm7.bullet.mail.ne1.yahoo.com with NNFMP; 27 May 2013 16:41:36 -0000 Received: from [127.0.0.1] by smtp213.mail.ne1.yahoo.com with NNFMP; 27 May 2013 16:41:36 -0000 X-Yahoo-Newman-Id: 138852.57184.bm@smtp213.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 8alcDPsVM1kdWbBua3_zcDGe4M1X.sUZdfMtHuepiuXlkgD uwu0Y1aaG3_hAhvVxsmCJBrEb_IOCR9WH6aHh.JNkqRBkg8hA6x2NZ2RhsDV 1nTi3y7oLLLqyCI1ovPgUcHJUbNWb3GBMwZ_lLySYTvOboGlUCrIpy_NfHFC X8OHBD_jgbLTowNv1V6QMgCH3.HRTIipw2jpGjAk0PtIw8AhJbjEJFPLpIdj LFpy39WWLWGGwXzXKsCzvRHfcj.qk_fmt3roFa0arJUj8L6S74uUt.wdR769 5dlfYnchrC7LLtP8W3BMfbEvt0IB.i6pVTlZ3UBHyioO9IXBROhz6pyP7Oy8 _3jJQjCPVHQVii3Pkh.bZoAFaksX3OswW26qSjD1OMnNmNYxdtTqSox0GJkk .5Jmhsw4WZvoAv5rV536IwainyF3Ua_o7BkjDdJxr56hmLC5MG2xOlHF1QNi .vqFdc9jIhmY.FflhHDpxZobrgVN5qzd_dAlNGbBxWs81vRyMCBOaj6riDfU MwMjAMIdwgffGhenAQH83iaom5iqOMG5UIkyYeyBOIqFV4R44Pl4rxFP7w47 XfGpo.hZVrA-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf X-Rocket-Received: from [192.168.0.102] (pfg@190.157.126.109 with ) by smtp213.mail.ne1.yahoo.com with SMTP; 27 May 2013 09:41:35 -0700 PDT Message-ID: <51A38CBD.6000702@FreeBSD.org> Date: Mon, 27 May 2013 11:41:33 -0500 From: Pedro Giffuni User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: toolchain@FreeBSD.org, amd64@FreeBSD.org Subject: [CFT] gcc: support for barcelona Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 27 May 2013 17:24:13 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 16:44:44 -0000 Hello; Almost a year ago I tried to bring in the support for AMD's barcelona chipset into our gcc. This actually filled a lot of holes in that were left when similar intel support was brought in. Unfortunately I had to revert rapidly such support as it broke building some C++ ports even when it was not being used. jkim@ did some cleanup of the support and the patch has been gathering rust here: http://people.freebsd.org/~jkim/reworked-r236962-3.diff The patch still applies cleanly and there is a good chance it will work since there have been other fixes merged since the last time. I did some basic testing and so far it works for me but I don't have the specific chipset. Additional testing would be welcome. regards, Pedro. From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 19:12:49 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C7E539C3; Mon, 27 May 2013 19:12:49 +0000 (UTC) (envelope-from rpaulo@felyko.com) Received: from felyko.com (felyko.com [IPv6:2607:f2f8:a528::3:1337:ca7]) by mx1.freebsd.org (Postfix) with ESMTP id B2DB3776; Mon, 27 May 2013 19:12:46 +0000 (UTC) Received: from [IPv6:2601:9:4d00:c2:8d3b:6227:5cf7:eac7] (unknown [IPv6:2601:9:4d00:c2:8d3b:6227:5cf7:eac7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id 973E93983B; Mon, 27 May 2013 12:12:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=felyko.com; s=mail; t=1369681965; bh=5BfB/UtPUI0m2Phfa38e8U69ozWu7w/ppqC2ak0Vh0M=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=cT2zr/Dhm9BRZ0ByIScyc2+LxcbS6OS2P+iOtoQeC7NrrIzFAExZGMZofLgH3yO+u oqxrGyLvddxEdwlfp0X4u2Z8/HmfFXTHogwFMmLNeFInOVBHjdgrFfMI6w/fNEnfWv CBZucEkhFesftEcy8/wxdkUwi9pkrhMh7wxu61u4= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [CFT] gcc: support for barcelona From: Rui Paulo In-Reply-To: <51A38CBD.6000702@FreeBSD.org> Date: Mon, 27 May 2013 12:12:44 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51A38CBD.6000702@FreeBSD.org> To: Pedro Giffuni X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Mon, 27 May 2013 22:54:22 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 19:12:49 -0000 On 27 May 2013, at 09:41, Pedro Giffuni wrote: > Hello; >=20 > Almost a year ago I tried to bring in the support for AMD's barcelona > chipset into our gcc. This actually filled a lot of holes in that were = left > when similar intel support was brought in. >=20 > Unfortunately I had to revert rapidly such support as it broke = building > some C++ ports even when it was not being used. >=20 > jkim@ did some cleanup of the support and the patch has been > gathering rust here: >=20 > http://people.freebsd.org/~jkim/reworked-r236962-3.diff >=20 > The patch still applies cleanly and there is a good chance it will = work > since there have been other fixes merged since the last time. >=20 > I did some basic testing and so far it works for me but I don't have > the specific chipset. Additional testing would be welcome. I have to question the general direction of this work. We switched to = Clang as the default compiler for i386/amd64 some months ago and now = you're working on improving our base GCC especially for amd64? I don't = really understand how useful this is. It doesn't strike me as a good = idea to see people working on things that will eventually be replaced / = removed. Regards, -- Rui Paulo From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 19:38:10 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3ACB5DD8; Mon, 27 May 2013 19:38:10 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id 00917841; Mon, 27 May 2013 19:38:10 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::ddfd:5c8d:86c3:f815] (unknown [IPv6:2001:7b8:3a7:0:ddfd:5c8d:86c3:f815]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 50A075C44; Mon, 27 May 2013 21:38:03 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [CFT] gcc: support for barcelona From: Dimitry Andric In-Reply-To: Date: Mon, 27 May 2013 21:38:01 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4BD4D414-8281-4127-A520-565CF28FF5E5@FreeBSD.org> References: <51A38CBD.6000702@FreeBSD.org> To: Rui Paulo X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Mon, 27 May 2013 22:54:36 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 19:38:10 -0000 On May 27, 2013, at 21:12, Rui Paulo wrote: > On 27 May 2013, at 09:41, Pedro Giffuni wrote: >> Almost a year ago I tried to bring in the support for AMD's barcelona >> chipset into our gcc. This actually filled a lot of holes in that = were left >> when similar intel support was brought in. >>=20 >> Unfortunately I had to revert rapidly such support as it broke = building >> some C++ ports even when it was not being used. >>=20 >> jkim@ did some cleanup of the support and the patch has been >> gathering rust here: >>=20 >> http://people.freebsd.org/~jkim/reworked-r236962-3.diff >>=20 >> The patch still applies cleanly and there is a good chance it will = work >> since there have been other fixes merged since the last time. >>=20 >> I did some basic testing and so far it works for me but I don't have >> the specific chipset. Additional testing would be welcome. >=20 > I have to question the general direction of this work. We switched to = Clang as the default compiler for i386/amd64 some months ago and now = you're working on improving our base GCC especially for amd64? I don't = really understand how useful this is. It doesn't strike me as a good = idea to see people working on things that will eventually be replaced / = removed. It is probably a better use of time to work on getting the tree to build with an out-of-tree gcc 4.7 or 4.8 instead. Why spend more effort on a completely dead branch of gcc? Newer gcc's have better code generation, support for more modern CPUs, and better diagnostics (including even those controversial carets ;-). That said, if it is a particular itch somebody wants to scratch, I see no reason not to, as long as it doesn't break anything else... -Dimitry From owner-freebsd-amd64@FreeBSD.ORG Mon May 27 19:51:04 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E059B4CB for ; Mon, 27 May 2013 19:51:04 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm47-vm8.bullet.mail.bf1.yahoo.com (nm47-vm8.bullet.mail.bf1.yahoo.com [216.109.115.143]) by mx1.freebsd.org (Postfix) with ESMTP id 703738EE for ; Mon, 27 May 2013 19:51:04 +0000 (UTC) Received: from [98.139.212.153] by nm47.bullet.mail.bf1.yahoo.com with NNFMP; 27 May 2013 19:49:01 -0000 Received: from [98.139.211.193] by tm10.bullet.mail.bf1.yahoo.com with NNFMP; 27 May 2013 19:49:01 -0000 Received: from [127.0.0.1] by smtp202.mail.bf1.yahoo.com with NNFMP; 27 May 2013 19:49:01 -0000 X-Yahoo-Newman-Id: 721313.29520.bm@smtp202.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: m42velcVM1mVPQyBMFNm0gtioVKm57OqmpY5WsXGBkPn4Iv _zvx4VJ70cXoWxZ7A8d7eYRPIDRkmL9qPEGqw6X_8I8RhcopvBOmmUNjjDuV FNeELvm05cQmm3mriKwTlJflVS_JZa2eMIL0DGbUqCKNGdQWgSFyZRhuO4E5 6s0Kq1fx1PHoLyZqiIHnvC0zG2d4znxSXrMIrBenw7XOjEGe5uOJmFQ_GMg3 sLc35xmowiEBYeXW_ow5iDQcUGgf1fcT6fkcRP6aF9QCX_earQcsBE94.eCq V_3YqL0_d7s1vgU4O_l6S3ZMHZwXRjWuwYVWAZlteDX2NCNx9IO_GPPjCvyE yXWsfe2TeUwLJXJtJqyDMROyY_HAoNMxKjFT863gKHXB6P_qvyX1n8Lm4wXy TxLcWWnbJ6KjjEKB32PiVS0ujHJzfx86w2kk4YcTeFLnQok5J8IUn9kYve06 6mopq6EWQgHYrg7doyBMreEvOLQ-- X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf X-Rocket-Received: from [192.168.0.102] (pfg@190.157.126.109 with ) by smtp202.mail.bf1.yahoo.com with SMTP; 27 May 2013 12:49:01 -0700 PDT Message-ID: <51A3B8AB.5080808@FreeBSD.org> Date: Mon, 27 May 2013 14:48:59 -0500 From: Pedro Giffuni User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: Rui Paulo Subject: Re: [CFT] gcc: support for barcelona References: <51A38CBD.6000702@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 27 May 2013 22:54:51 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 May 2013 19:51:04 -0000 On 27.05.2013 14:12, Rui Paulo wrote: > On 27 May 2013, at 09:41, Pedro Giffuni wrote: > >> Hello; >> >> Almost a year ago I tried to bring in the support for AMD's barcelona >> chipset into our gcc. This actually filled a lot of holes in that were left >> when similar intel support was brought in. >> >> Unfortunately I had to revert rapidly such support as it broke building >> some C++ ports even when it was not being used. >> >> jkim@ did some cleanup of the support and the patch has been >> gathering rust here: >> >> http://people.freebsd.org/~jkim/reworked-r236962-3.diff >> >> The patch still applies cleanly and there is a good chance it will work >> since there have been other fixes merged since the last time. >> >> I did some basic testing and so far it works for me but I don't have >> the specific chipset. Additional testing would be welcome. > > I have to question the general direction of this work. We switched to Clang as the default compiler for i386/amd64 some months ago and now you're working on improving our base GCC especially for amd64? I don't really understand how useful this is. It doesn't strike me as a good idea to see people working on things that will eventually be replaced / removed. I have absolutely no intention to give gcc a second air: it's dead and I am anxious to see it axed from -current (soon?). This said, there are still many FreeBSD users trapped with the base gcc for at least as long as 9.x is alive. If you look at the ChangeLog.gcc43 in the above patch, you will notice I am just completing some code that was incompletely merged in previous revisions. The basic work was done almost a year ago, and I have no hurry to merge it but given that the effort was done already it would seem a pity to just throw it away. Of course I may be completely wrong here. Pedro. From owner-freebsd-amd64@FreeBSD.ORG Tue May 28 02:40:01 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 19E11C25 for ; Tue, 28 May 2013 02:40:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 013DBF4D for ; Tue, 28 May 2013 02:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4S2e0lq012464 for ; Tue, 28 May 2013 02:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4S2e02d012463; Tue, 28 May 2013 02:40:00 GMT (envelope-from gnats) Resent-Date: Tue, 28 May 2013 02:40:00 GMT Resent-Message-Id: <201305280240.r4S2e02d012463@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Patrick FRy Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A5047C0D for ; Tue, 28 May 2013 02:36:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.FreeBSD.org (oldred.freebsd.org [8.8.178.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7E186F3F for ; Tue, 28 May 2013 02:36:05 +0000 (UTC) Received: from oldred.FreeBSD.org ([127.0.1.6]) by oldred.FreeBSD.org (8.14.5/8.14.5) with ESMTP id r4S2a5ss019108 for ; Tue, 28 May 2013 02:36:05 GMT (envelope-from nobody@oldred.FreeBSD.org) Received: (from nobody@localhost) by oldred.FreeBSD.org (8.14.5/8.14.5/Submit) id r4S2a5If019107; Tue, 28 May 2013 02:36:05 GMT (envelope-from nobody) Message-Id: <201305280236.r4S2a5If019107@oldred.FreeBSD.org> Date: Tue, 28 May 2013 02:36:05 GMT From: Patrick FRy To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: amd64/179038: instant reboot doesnt even try too install X-Mailman-Approved-At: Tue, 28 May 2013 03:17:13 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 02:40:01 -0000 >Number: 179038 >Category: amd64 >Synopsis: instant reboot doesnt even try too install >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 28 02:40:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Patrick FRy >Release: any >Organization: n/a >Environment: everytime i try too install any version of freebsd it just reboots never had this problem before same hardware as before except for new vid card >Description: amd 965 8 gig ddr 3 1600 mem 1950 amd vid card .., try too boot from cd it gets too the boot loader im use too seeing then just reboots before i can make a choice on what too do >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue May 28 17:41:03 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1A5C0DE9 for ; Tue, 28 May 2013 17:41:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by mx1.freebsd.org (Postfix) with ESMTP id DA1B6AB8 for ; Tue, 28 May 2013 17:41:02 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id tb18so9428671obb.17 for ; Tue, 28 May 2013 10:41:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=j5iWK9Qo7/92eE70KTgobPFv2CUHGWxuulRuLADs8N4=; b=LI8q6E9w8KFPEuitgVeEGmrWm4B17pFUts7RiFYWu5ZZ9YDQmtq1PJxYWbyZa9Bmd3 GF0MFKsHKGaGAmWG1TiS/5qITra6zRU0pyJkRQHReXdCRM/ZCTj6QT4V+XGtXYX8+Bbr 8lANaIahVwZDZogtGCryGVySi0/k4eQApLX3uDgpdtsGluCbqLs8hKA1D4Nat2LK/wZJ r3Bqki9wzEqwPPuS1aBThKPOQx6om4qHexTH+Om1/pXTgItSLsGq3WjUcSvqsaYege9f xsZ/gaoKx2d+NDoY4PwdUJO1I5W/mk5Fa3Gi7n8jc/OhEUzqpzPGgesX+ekXexh3Zx0F 06yQ== X-Received: by 10.60.142.67 with SMTP id ru3mr21810638oeb.44.1369762862366; Tue, 28 May 2013 10:41:02 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id hv3sm35667287obb.7.2013.05.28.10.41.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 10:41:01 -0700 (PDT) Sender: Warner Losh Subject: Re: [CFT] gcc: support for barcelona Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <51A3B8AB.5080808@FreeBSD.org> Date: Tue, 28 May 2013 11:40:59 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> To: Pedro Giffuni X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQkJ9pUYVtWm1uLu9TessLR3LkItNnqd0BP5MMfuyCqzZH8WPs08BpbkGS+8KNRPq6iJ1wvu X-Mailman-Approved-At: Tue, 28 May 2013 19:20:14 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Rui Paulo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 17:41:03 -0000 On May 27, 2013, at 1:48 PM, Pedro Giffuni wrote: > On 27.05.2013 14:12, Rui Paulo wrote: >> On 27 May 2013, at 09:41, Pedro Giffuni wrote: >>=20 >>> Hello; >>>=20 >>> Almost a year ago I tried to bring in the support for AMD's = barcelona >>> chipset into our gcc. This actually filled a lot of holes in that = were left >>> when similar intel support was brought in. >>>=20 >>> Unfortunately I had to revert rapidly such support as it broke = building >>> some C++ ports even when it was not being used. >>>=20 >>> jkim@ did some cleanup of the support and the patch has been >>> gathering rust here: >>>=20 >>> http://people.freebsd.org/~jkim/reworked-r236962-3.diff >>>=20 >>> The patch still applies cleanly and there is a good chance it will = work >>> since there have been other fixes merged since the last time. >>>=20 >>> I did some basic testing and so far it works for me but I don't have >>> the specific chipset. Additional testing would be welcome. >>=20 >> I have to question the general direction of this work. We switched to = Clang as the default compiler for i386/amd64 some months ago and now = you're working on improving our base GCC especially for amd64? I don't = really understand how useful this is. It doesn't strike me as a good = idea to see people working on things that will eventually be replaced / = removed. >=20 > I have absolutely no intention to give gcc a second air: it's dead > and I am anxious to see it axed from -current (soon?). That's not going to happen soon. While it works OK for amd64, there's = still many bugs in its ARM support and even more in its MIPS support. = There's 0 chance it will be gone in 10... > This said, > there are still many FreeBSD users trapped with the base gcc for > at least as long as 9.x is alive. >=20 > If you look at the ChangeLog.gcc43 in the above patch, you will > notice I am just completing some code that was incompletely > merged in previous revisions. >=20 > The basic work was done almost a year ago, and I have no hurry > to merge it but given that the effort was done already it would > seem a pity to just throw it away. >=20 > Of course I may be completely wrong here. I see some value in adding this stuff. While we have made clang the = default, it still isn't fully vetted by surviving a release with it = enabled. the fallback plan will continue to be gcc. While it would ALSO be good to cleanup the tree so it can compile = cleanly with 4.7 or 4.8, this effort won't stand in the way of that. = Excluding it seems more like a political or emotional one than a = practical one. Warner From owner-freebsd-amd64@FreeBSD.ORG Tue May 28 18:10:49 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 684C7B04; Tue, 28 May 2013 18:10:49 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3B09CCC5; Tue, 28 May 2013 18:10:48 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r4SIASrA043367 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 May 2013 18:10:29 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [CFT] gcc: support for barcelona From: David Chisnall In-Reply-To: <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> Date: Tue, 28 May 2013 19:10:23 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <3C29AD82-077D-4E6B-94C7-5D069A130348@FreeBSD.org> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Tue, 28 May 2013 19:37:26 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 18:10:49 -0000 On 28 May 2013, at 18:40, Warner Losh wrote: > That's not going to happen soon. While it works OK for amd64, there's = still many bugs in its ARM support and even more in its MIPS support. = There's 0 chance it will be gone in 10... I disagree. There is a significant chance that gcc in base will be gone = for all Tier 1 platforms in 10.0. There are still some reasons to want = gcc installed, but there are no compelling reasons to want an ancient = version of gcc installed on x86[-64] or ARM. For people who need gcc, = the ports collection provides a selection of recent versions. David From owner-freebsd-amd64@FreeBSD.ORG Tue May 28 19:55:00 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AA7DA918; Tue, 28 May 2013 19:55:00 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 72E4C234; Tue, 28 May 2013 19:55:00 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r4SJsv6Q052304; Tue, 28 May 2013 12:54:57 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r4SJsv20052303; Tue, 28 May 2013 12:54:57 -0700 (PDT) (envelope-from sgk) Date: Tue, 28 May 2013 12:54:57 -0700 From: Steve Kargl To: David Chisnall Subject: Re: [CFT] gcc: support for barcelona Message-ID: <20130528195457.GA52250@troutmask.apl.washington.edu> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C29AD82-077D-4E6B-94C7-5D069A130348@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 19:55:00 -0000 On Tue, May 28, 2013 at 07:10:23PM +0100, David Chisnall wrote: > On 28 May 2013, at 18:40, Warner Losh wrote: > > > That's not going to happen soon. While it works OK for amd64, there's still many bugs in its ARM support and even more in its MIPS support. There's 0 chance it will be gone in 10... > > I disagree. There is a significant chance that gcc in base > will be gone for all Tier 1 platforms in 10.0. There are > still some reasons to want gcc installed, but there are no > compelling reasons to want an ancient version of gcc installed > on x86[-64] or ARM. For people who need gcc, the ports > collection provides a selection of recent versions. > > David I surely hope not! Until the individuals pushing the change to clang actually tests clang on floating point intensive applications, it is IMHO dubious to even have clang as the default compiler. Just the latest example: http://lists.freebsd.org/pipermail/freebsd-numerics/2013-May/000354.html -- Steve From owner-freebsd-amd64@FreeBSD.ORG Tue May 28 20:25:44 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 23DEA459; Tue, 28 May 2013 20:25:44 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 04E4037C; Tue, 28 May 2013 20:25:43 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r4SKPgGn052533; Tue, 28 May 2013 13:25:42 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r4SKPgLu052532; Tue, 28 May 2013 13:25:42 -0700 (PDT) (envelope-from sgk) Date: Tue, 28 May 2013 13:25:42 -0700 From: Steve Kargl To: Rui Paulo Subject: Re: [CFT] gcc: support for barcelona Message-ID: <20130528202542.GA52507@troutmask.apl.washington.edu> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348@FreeBSD.org> <20130528195457.GA52250@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , David Chisnall , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 20:25:44 -0000 On Tue, May 28, 2013 at 01:01:00PM -0700, Rui Paulo wrote: > On 28 May 2013, at 12:54, Steve Kargl wrote: > > On Tue, May 28, 2013 at 07:10:23PM +0100, David Chisnall wrote: > >> On 28 May 2013, at 18:40, Warner Losh wrote: > >> > >>> That's not going to happen soon. While it works OK for amd64, there's still many bugs in its ARM support and even more in its MIPS support. There's 0 chance it will be gone in 10... > >> > >> I disagree. There is a significant chance that gcc in base > >> will be gone for all Tier 1 platforms in 10.0. There are > >> still some reasons to want gcc installed, but there are no > >> compelling reasons to want an ancient version of gcc installed > >> on x86[-64] or ARM. For people who need gcc, the ports > >> collection provides a selection of recent versions. > >> > > > > I surely hope not! Until the individuals pushing the > > change to clang actually tests clang on floating point > > intensive applications, it is IMHO dubious to even have > > clang as the default compiler. Just the latest example: > > > > http://lists.freebsd.org/pipermail/freebsd-numerics/2013-May/000354.html > > Have you, or anyone else, filed bug reports at http://llvm.org/bugs/ ? > I haven't submitted this bug. Given the attention that another bug that I pointed out, I have little interest in submitting other bugs. Ed Schouten submitted the bug report after I pointed out clang cannot do complex arithmetic correctly under certain circumstances. http://llvm.org/bugs/show_bug.cgi?id=8532 -- Steve From owner-freebsd-amd64@FreeBSD.ORG Tue May 28 20:01:08 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 14947BA9; Tue, 28 May 2013 20:01:08 +0000 (UTC) (envelope-from rpaulo@felyko.com) Received: from felyko.com (felyko.com [174.136.100.2]) by mx1.freebsd.org (Postfix) with ESMTP id EFE5C271; Tue, 28 May 2013 20:01:07 +0000 (UTC) Received: from [IPv6:2601:9:4d00:c2:bd70:2451:66e7:97d] (unknown [IPv6:2601:9:4d00:c2:bd70:2451:66e7:97d]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id 2E28D3981E; Tue, 28 May 2013 13:01:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=felyko.com; s=mail; t=1369771261; bh=ODUF8au/zAisiwpokd1l5aCGhbVXsQeF6fsrr/orwH4=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=cPyk7WViibOR3Rt9x1MedF2m1u6sV0AtIeiScbZvU8QGA3ZBx3UeWTJclcgX26G4H 8wAokYH8/Z1SPY2x5ULxeQQsWh6/qIXgLS8TaCano+tsGOjg50jFlVfgYQbJIrAmB9 B7BmP0xsJ27PiY/kx2bxrNLgy7eZc0rY0Cm50IyE= Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [CFT] gcc: support for barcelona From: Rui Paulo In-Reply-To: <20130528195457.GA52250@troutmask.apl.washington.edu> Date: Tue, 28 May 2013 13:01:00 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348@FreeBSD.org> <20130528195457.GA52250@troutmask.apl.washington.edu> To: Steve Kargl X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Tue, 28 May 2013 21:34:56 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , David Chisnall , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 20:01:08 -0000 On 28 May 2013, at 12:54, Steve Kargl = wrote: > On Tue, May 28, 2013 at 07:10:23PM +0100, David Chisnall wrote: >> On 28 May 2013, at 18:40, Warner Losh wrote: >>=20 >>> That's not going to happen soon. While it works OK for amd64, = there's still many bugs in its ARM support and even more in its MIPS = support. There's 0 chance it will be gone in 10... >>=20 >> I disagree. There is a significant chance that gcc in base >> will be gone for all Tier 1 platforms in 10.0. There are >> still some reasons to want gcc installed, but there are no >> compelling reasons to want an ancient version of gcc installed >> on x86[-64] or ARM. For people who need gcc, the ports >> collection provides a selection of recent versions. >>=20 >> David >=20 > I surely hope not! Until the individuals pushing the > change to clang actually tests clang on floating point > intensive applications, it is IMHO dubious to even have > clang as the default compiler. Just the latest example: >=20 > = http://lists.freebsd.org/pipermail/freebsd-numerics/2013-May/000354.html Have you, or anyone else, filed bug reports at http://llvm.org/bugs/ ? Regards, -- Rui Paulo From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 06:58:39 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5132A742; Wed, 29 May 2013 06:58:39 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E9882F23; Wed, 29 May 2013 06:58:37 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA09154; Wed, 29 May 2013 09:58:29 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1UhaL7-000GdY-5y; Wed, 29 May 2013 09:58:29 +0300 Message-ID: <51A5A6F4.8000501@FreeBSD.org> Date: Wed, 29 May 2013 09:57:56 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: David Chisnall Subject: Re: [CFT] gcc: support for barcelona References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> In-Reply-To: <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 29 May 2013 11:38:57 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 06:58:39 -0000 on 28/05/2013 21:10 David Chisnall said the following: > On 28 May 2013, at 18:40, Warner Losh wrote: > >> That's not going to happen soon. While it works OK for amd64, there's still >> many bugs in its ARM support and even more in its MIPS support. There's 0 >> chance it will be gone in 10... > > I disagree. There is a significant chance that gcc in base will be gone for > all Tier 1 platforms in 10.0. There are still some reasons to want gcc > installed, but there are no compelling reasons to want an ancient version of > gcc installed on x86[-64] or ARM. For people who need gcc, the ports > collection provides a selection of recent versions. I will try to veto any attempt to do so until at least this bug is fixed: http://llvm.org/bugs/show_bug.cgi?id=15662 I am sure that other developers have their favorite bugs too. In fact, I am of opinion that while such bugs exist gcc should be crowned back as a default compiler. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 08:48:14 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6A029543; Wed, 29 May 2013 08:48:14 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3A7F96BB; Wed, 29 May 2013 08:48:14 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r4T8lvdG047507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 08:48:00 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [CFT] gcc: support for barcelona From: David Chisnall In-Reply-To: <51A5A6F4.8000501@FreeBSD.org> Date: Wed, 29 May 2013 09:47:52 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Wed, 29 May 2013 11:39:09 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 08:48:14 -0000 On 29 May 2013, at 07:57, Andriy Gapon wrote: > In fact, I am of opinion that while such bugs exist gcc should be = crowned back > as a default compiler. Seriously? Your show stopper bug is that, very occasionally, clang = emits incorrect debug info? And Steve's is that clang emits code that = is fully compliant with the C standard, but gives more floating point = precision than he wanted? If those are the most serious problems we have with clang, then it's = time to remove gcc 4.2.1 from the tree right now. I wish the problems = that we had with it were so trivial... David From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 08:51:48 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 89EA45E9; Wed, 29 May 2013 08:51:48 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 263526E0; Wed, 29 May 2013 08:51:46 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA11944; Wed, 29 May 2013 11:51:45 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Uhc6i-000Gop-Ma; Wed, 29 May 2013 11:51:44 +0300 Message-ID: <51A5C17C.1070403@FreeBSD.org> Date: Wed, 29 May 2013 11:51:08 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130405 Thunderbird/17.0.5 MIME-Version: 1.0 To: David Chisnall Subject: Re: [CFT] gcc: support for barcelona References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 29 May 2013 11:39:17 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 08:51:48 -0000 on 29/05/2013 11:47 David Chisnall said the following: > Seriously? Your show stopper bug is that, very occasionally, clang emits incorrect debug info? Yes, that bug breaks some DTrace scripts that are critical to me. Otherwise I would not have noticed the issue. -- Andriy Gapon From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 08:56:19 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B5F7283E; Wed, 29 May 2013 08:56:19 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) by mx1.freebsd.org (Postfix) with ESMTP id 85E00774; Wed, 29 May 2013 08:56:19 +0000 (UTC) Received: from [192.168.0.2] (cpc27-cmbg15-2-0-cust235.5-4.cable.virginmedia.com [86.27.188.236]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r4T8uFZG047546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 08:56:16 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: [CFT] gcc: support for barcelona From: David Chisnall In-Reply-To: <51A5C17C.1070403@FreeBSD.org> Date: Wed, 29 May 2013 09:56:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5FE9094B-5B25-4E87-9674-669011C4DABF@FreeBSD.org> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> <51A5C17C.1070403@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1503) X-Mailman-Approved-At: Wed, 29 May 2013 11:39:25 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 08:56:19 -0000 On 29 May 2013, at 09:51, Andriy Gapon wrote: >=20 > Yes, that bug breaks some DTrace scripts that are critical to me. > Otherwise I would not have noticed the issue. Looking at the bug report, you filed it against clang 3.2, just after = 3.3 was branched. Did you test 3.3? Is it fixed? I can only assume = that, since the bug has been present in the system compiler for 6 months = without your noticing that it can't be that critical... David From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 13:25:20 2013 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0AA3238F; Wed, 29 May 2013 13:25:20 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id D96BCDCF; Wed, 29 May 2013 13:25:19 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r4TDPALe057913; Wed, 29 May 2013 06:25:10 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r4TDPARl057912; Wed, 29 May 2013 06:25:10 -0700 (PDT) (envelope-from sgk) Date: Wed, 29 May 2013 06:25:10 -0700 From: Steve Kargl To: David Chisnall Subject: Re: [CFT] gcc: support for barcelona Message-ID: <20130529132510.GA57733@troutmask.apl.washington.edu> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Andriy Gapon , toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , amd64@FreeBSD.org, Warner Losh X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 13:25:20 -0000 On Wed, May 29, 2013 at 09:47:52AM +0100, David Chisnall wrote: > On 29 May 2013, at 07:57, Andriy Gapon wrote: > > > In fact, I am of opinion that while such bugs exist gcc should be crowned back > > as a default compiler. > > Seriously? Your show stopper bug is that, very occasionally, clang emits incorrect debug info? And Steve's is that clang emits code that is fully compliant with the C standard, but gives more floating point precision than he wanted? > Ah, no. I just pointed to the last example of poor floating point support from clang. The other bug I mentioned has sat in the llvm bug database for nearly 2 years. But, to be blunt, clang cannot do complex arithmetic correctly. > If those are the most serious problems we have with clang, then > it's time to remove gcc 4.2.1 from the tree right now. I wish > the problems that we had with it were so trivial... The most serious problems IMNSHO are: 1) The dismal compile time of clang. My buildworlds are 3 to 4 times slower with clang than gcc. I certainly understand the recent explosion in tinderbox messages. No one wants to wait the better part of a day to do a make world and make universe must be painful. 2) Last time I checked, clang could not build a functioning X11 environment. Perhaps, having the xserver blow chunks when she's starting is consider to a Good Thing. When I reported the problem, I was dutifully informed that the problem wasn't clang, it was the x11 loader. Oddly, gcc does not have this issue. May be this has been fix. Don't know, don't care, because the last time I tried clang as the default compiler it took a week to recover a working environment. 3) Last time I benchmarked a libm built by clang against a libm built by gcc. gcc produced smaller, faster code and in one case a gcc compiled function produced a correct result while the clang compiled functions produced NaN for all inputs in a specific range. Yeah, I reported that too. I was told the test case was too complicated. PS: That extra precision can be a big headache when one is trying to write high quality software. -- Steve From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 15:10:00 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C021E605 for ; Wed, 29 May 2013 15:10:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8D859BE3 for ; Wed, 29 May 2013 15:10:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4TFA0xL058866 for ; Wed, 29 May 2013 15:10:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4TFA0oQ058865; Wed, 29 May 2013 15:10:00 GMT (envelope-from gnats) Resent-Date: Wed, 29 May 2013 15:10:00 GMT Resent-Message-Id: <201305291510.r4TFA0oQ058865@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Heinrich Niemeyer Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3B5D096 for ; Wed, 29 May 2013 15:02:09 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.FreeBSD.org (oldred.freebsd.org [8.8.178.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2DC34AC0 for ; Wed, 29 May 2013 15:02:09 +0000 (UTC) Received: from oldred.FreeBSD.org ([127.0.1.6]) by oldred.FreeBSD.org (8.14.5/8.14.5) with ESMTP id r4TF28Qa077383 for ; Wed, 29 May 2013 15:02:08 GMT (envelope-from nobody@oldred.FreeBSD.org) Received: (from nobody@localhost) by oldred.FreeBSD.org (8.14.5/8.14.5/Submit) id r4TF28Ms077382; Wed, 29 May 2013 15:02:08 GMT (envelope-from nobody) Message-Id: <201305291502.r4TF28Ms077382@oldred.FreeBSD.org> Date: Wed, 29 May 2013 15:02:08 GMT From: Heinrich Niemeyer To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: amd64/179080: shared folders unter vmware workstation X-Mailman-Approved-At: Wed, 29 May 2013 15:46:28 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 15:10:00 -0000 >Number: 179080 >Category: amd64 >Synopsis: shared folders unter vmware workstation >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed May 29 15:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Heinrich Niemeyer >Release: 9.1 >Organization: privat >Environment: >Description: Ich habe in der neuesten VMware Workstion Version FreeBSD 9.1 installiert. Auch die VMware Tools sind installiert. In Gnome funkioniert Copy und Past. Ein gemeinsames Verzeichnis ist in Workstation eingerichtet sagen wir freebsd_shared. FreeBSD erkennt dieses Verzeichnis nicht. Beim Versuch mit mount das freebsd_shared einzubinden, kommt die Meldung: Operation not supported by device. Eine beständige Einbindung sollte wohl über /etc/fstab erfolgen!? Wie lautet die korrekte Syntax für mount bzw. fstab. Muss eventuell noch etwas installiert werden? Für eine Antwort wäre ich dankbar. Mit freundlichen Grüssen Heinrich Niemeyer >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Wed May 29 16:06:47 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 631B9541 for ; Wed, 29 May 2013 16:06:47 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) by mx1.freebsd.org (Postfix) with ESMTP id 2CE3C688 for ; Wed, 29 May 2013 16:06:46 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id f4so11888871oah.10 for ; Wed, 29 May 2013 09:06:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=KQfJZcCTovTv3LoyiUc8IpdEJ0fUljqZMYMIToPGUeo=; b=NALuB9bpQrYmaCOK6A97r5S/nr3/0wYHFPM8IWNLmAqF5JYPGWVMvJOz+mZv+T8oI9 dw/FIfW/znSgrt0nIMf2ND201YKvQhOvaSWQ7HG5VypDUbFTHI0WKoXA2vr0qk1BKbLz OfbQtmnL5JNOCazhVKeLIzFFwonU9E4rr03XjbjxxagV+5M8WZCT24K81gU6PzBHGUyj fh4k7R7IEjGly8DabKval4u4yarRiwzi9/1ygJDIXGmeDXlgtd9g0wOLf87UxjlsU78M TyMLhcQ1/WYtYe1pgCb9vHCFXwyo1w9a/WOtVXJbWR/adWKBupUJEmrj82Kpe/R6LH2T Chvg== X-Received: by 10.60.34.135 with SMTP id z7mr2051708oei.68.1369843606284; Wed, 29 May 2013 09:06:46 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id sa2sm11157904oeb.1.2013.05.29.09.06.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 09:06:45 -0700 (PDT) Sender: Warner Losh Subject: Re: [CFT] gcc: support for barcelona Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Wed, 29 May 2013 10:06:40 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com> References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> To: David Chisnall X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQkY2Oy7bcFMhx3WjBm6SODzzDLJWrBCXG6ds3uN7kM7n9KjxGhSdmq3QDIzHnRLWjY7g0U9 X-Mailman-Approved-At: Wed, 29 May 2013 17:58:16 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, Pedro Giffuni , Rui Paulo , Andriy Gapon X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 16:06:47 -0000 On May 29, 2013, at 2:47 AM, David Chisnall wrote: > On 29 May 2013, at 07:57, Andriy Gapon wrote: >=20 >> In fact, I am of opinion that while such bugs exist gcc should be = crowned back >> as a default compiler. >=20 > Seriously? Your show stopper bug is that, very occasionally, clang = emits incorrect debug info? And Steve's is that clang emits code that = is fully compliant with the C standard, but gives more floating point = precision than he wanted? >=20 > If those are the most serious problems we have with clang, then it's = time to remove gcc 4.2.1 from the tree right now. I wish the problems = that we had with it were so trivial... NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = . There are serious problems with clang on arm right now. And it doesn't = support mips. Removing gcc is way premature. Warner From owner-freebsd-amd64@FreeBSD.ORG Thu May 30 14:30:01 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B26D9223 for ; Thu, 30 May 2013 14:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A5119823 for ; Thu, 30 May 2013 14:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4UEU1G5077068 for ; Thu, 30 May 2013 14:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4UEU1JW077067; Thu, 30 May 2013 14:30:01 GMT (envelope-from gnats) Date: Thu, 30 May 2013 14:30:01 GMT Message-Id: <201305301430.r4UEU1JW077067@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org Cc: From: Mark Saad Subject: Re: amd64/164073: /etc/rc warning after booting X-Mailman-Approved-At: Thu, 30 May 2013 15:42:47 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Saad List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 14:30:01 -0000 The following reply was made to PR amd64/164073; it has been noted by GNATS. From: Mark Saad To: bug-followup@FreeBSD.org, jotawski@gmail.com Cc: Subject: Re: amd64/164073: /etc/rc warning after booting Date: Thu, 30 May 2013 10:25:38 -0400 --e89a8f3ba2f3c0feff04ddf0452d Content-Type: text/plain; charset=UTF-8 Hello Can you let us know if this issue is still happining. Can you submit a follow up with the following information. The contents of /etc/rc.conf , /etc/rc.conf.local . From your description it looks like you are using an obsolete config option for IPv6 support. -- mark saad | nonesuch@longcount.org --e89a8f3ba2f3c0feff04ddf0452d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello
=C2=A0Can you let us know if this= issue is still happining. Can you submit a follow up with the following in= formation.

The contents of /etc/rc.conf , /etc/rc.conf.local .
<= br>
From your description it looks like you are using an obsolete config option= for IPv6 support.

--
mark sa= ad | nonesuch@l= ongcount.org
--e89a8f3ba2f3c0feff04ddf0452d-- From owner-freebsd-amd64@FreeBSD.ORG Thu May 30 14:30:02 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A2EDB224 for ; Thu, 30 May 2013 14:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 95E59824 for ; Thu, 30 May 2013 14:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4UEU28F077074 for ; Thu, 30 May 2013 14:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4UEU2BI077073; Thu, 30 May 2013 14:30:02 GMT (envelope-from gnats) Date: Thu, 30 May 2013 14:30:02 GMT Message-Id: <201305301430.r4UEU2BI077073@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org Cc: From: Mark Saad Subject: Re: amd64/171110: Upgrade 9.1-BETA1 > RC1 issue X-Mailman-Approved-At: Thu, 30 May 2013 15:43:12 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Saad List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 14:30:02 -0000 The following reply was made to PR amd64/171110; it has been noted by GNATS. From: Mark Saad To: bug-followup@FreeBSD.org, mail@psvlan.com Cc: Subject: Re: amd64/171110: Upgrade 9.1-BETA1 > RC1 issue Date: Thu, 30 May 2013 10:27:28 -0400 --f46d04389247498d1404ddf04c16 Content-Type: text/plain; charset=UTF-8 All This issue was resolved , after 9.1-RELEASE and the posting about the breakin. This pr can be closed. -- mark saad | nonesuch@longcount.org --f46d04389247498d1404ddf04c16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
All
=C2=A0 This issue was resolved , after 9= .1-RELEASE and the posting about the breakin. This pr can be closed.

--
mark saad | nonesuch@longcount.org
--f46d04389247498d1404ddf04c16-- From owner-freebsd-amd64@FreeBSD.ORG Thu May 30 14:30:03 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C3041225 for ; Thu, 30 May 2013 14:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B5CC4825 for ; Thu, 30 May 2013 14:30:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4UEU3vs077082 for ; Thu, 30 May 2013 14:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4UEU3Zl077081; Thu, 30 May 2013 14:30:03 GMT (envelope-from gnats) Date: Thu, 30 May 2013 14:30:03 GMT Message-Id: <201305301430.r4UEU3Zl077081@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org Cc: From: Mark Saad Subject: Re: amd64/170115: Serial boot broken in 9.0 X-Mailman-Approved-At: Thu, 30 May 2013 15:43:22 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Saad List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 14:30:03 -0000 The following reply was made to PR amd64/170115; it has been noted by GNATS. From: Mark Saad To: bug-followup@FreeBSD.org, paul@ifdnrg.com Cc: Subject: Re: amd64/170115: Serial boot broken in 9.0 Date: Thu, 30 May 2013 10:22:28 -0400 --047d7b5d656e63692b04ddf03a0d Content-Type: text/plain; charset=UTF-8 Paul Is this issue still happening ? Is this only an issue with 57.6Kbps . Can you submit a follow up with the output from pciconf -lv , the contents of /var/run/dmesg.boot and details about the make model and vendor of the system. -- mark saad | nonesuch@longcount.org --047d7b5d656e63692b04ddf03a0d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Paul
=C2=A0 Is this issue still ha= ppening ? Is this only an issue with 57.6Kbps .

Can you submit= a follow up with the output from pciconf -lv ,=C2=A0 the contents of /var/= run/dmesg.boot
=C2=A0and details about the make model and vendor of the system.

--
mark saad | nonesuch@longcount.org
--047d7b5d656e63692b04ddf03a0d-- From owner-freebsd-amd64@FreeBSD.ORG Thu May 30 16:16:40 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 783BBD6F for ; Thu, 30 May 2013 16:16:40 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from nm30-vm1.bullet.mail.ne1.yahoo.com (nm30-vm1.bullet.mail.ne1.yahoo.com [98.138.90.46]) by mx1.freebsd.org (Postfix) with ESMTP id 098252B2 for ; Thu, 30 May 2013 16:16:39 +0000 (UTC) Received: from [98.138.90.51] by nm30.bullet.mail.ne1.yahoo.com with NNFMP; 30 May 2013 16:11:18 -0000 Received: from [98.138.226.60] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 30 May 2013 16:11:18 -0000 Received: from [127.0.0.1] by smtp211.mail.ne1.yahoo.com with NNFMP; 30 May 2013 16:11:18 -0000 X-Yahoo-Newman-Id: 224586.39253.bm@smtp211.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Z2xGMyMVM1kXujRXmM3oZCVDuUSqnz5604WjKLZZViklP51 oxaiGSqOH68tx_U94MixSj0OyFGWG5_hwlKLlsTs6xNMVBwjQFWedXukbiwo Jh74J16x95N93T_U0mRUJW.MhoUnwiCYzjAELtLPVjvPLSnXQvkhxUka6y.I Vn6dAMRKiwXSv0F18rG2CesxVQ.veVVW0wRMgdA8fCUUvhWT4qjcww7w7DDm HCTx3fxikJPS7zYac3C1tGf8zrshBFjt3o9MKn7GT7rtEh54jJz1LDPXBLMl WZFrozByDlQa0n5VgD9fXqE_cgJzJbPF5QZyYVKwiBJ.1C8ioH3psSni8tFq t1rP5VqOln6lTjSxD_DWLc4W4VyojCn.rdNKIGOxTK6vCgJUbRy6PPHWjy9S VbTgxpIbhLtkjdfo05tpKWiXZ_JFVonzvp9JKjGquiMMpPmj3q85FLUhBUVu YAtuVglfIUgU61tEJNDYR1sJ5KRSHWzIOsMkgQ1LNjosM6eDJPesyVeWH X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf X-Rocket-Received: from [192.168.0.102] (pfg@190.157.126.109 with ) by smtp211.mail.ne1.yahoo.com with SMTP; 30 May 2013 09:11:18 -0700 PDT Message-ID: <51A77A22.3040103@FreeBSD.org> Date: Thu, 30 May 2013 11:11:14 -0500 From: Pedro Giffuni User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: Warner Losh Subject: Re: [CFT] gcc: support for barcelona References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com> In-Reply-To: <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 30 May 2013 17:11:57 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, David Chisnall , Rui Paulo , Andriy Gapon X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 16:16:40 -0000 On 29.05.2013 11:06, Warner Losh wrote: > On May 29, 2013, at 2:47 AM, David Chisnall wrote: > >> On 29 May 2013, at 07:57, Andriy Gapon wrote: >> >>> In fact, I am of opinion that while such bugs exist gcc should be crowned back >>> as a default compiler. >> Seriously? Your show stopper bug is that, very occasionally, clang emits incorrect debug info? And Steve's is that clang emits code that is fully compliant with the C standard, but gives more floating point precision than he wanted? >> >> If those are the most serious problems we have with clang, then it's time to remove gcc 4.2.1 from the tree right now. I wish the problems that we had with it were so trivial... > NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO > ... > There are serious problems with clang on arm right now. And it doesn't support mips. Removing gcc is way premature. > > Warner > I didn't meant to start a clang vs gcc thread but it's evident that we were actually in need of expressing the issues about clang and the future of the tool chain. IMHO: - gcc has to go. It is old and, despite the scotch tape, unmaintained. libstdc++ in particular really has to go first: it is too confusing to have two C++ libraries where one of them is simply obsolete. OpenOffice, for example was recently ported to clang and libc++ however it will not work with the libstdc++ in base due to lack of C++11 support. - clang is not ready but it is getting there: I appreciate greatly having compiler_rt and the new C++ stack available. Unfortunately I do agree with the opinion that clang is taking too long to build and has become a bottleneck for buildworld. Now I would really like to see both gcc and clang living as packages outside of base. This would also mean that the installer has to start learning about pkgng (which is one of the things I miss about sysinstall). It's all wishful thinking though so I just want to thank everyone that is doing the real work both making an external toolchain possible and improving clang support. Regards, Pedro. From owner-freebsd-amd64@FreeBSD.ORG Thu May 30 17:03:25 2013 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2D00B9B6 for ; Thu, 30 May 2013 17:03:25 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id F17E36CF for ; Thu, 30 May 2013 17:03:24 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id k13so1205826iea.18 for ; Thu, 30 May 2013 10:03:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=oYtv7qsTyACIwJQOg3cgKill3wzWP1qKviemq82E7rI=; b=RiMTzgzS9LjaGr7VGuzjOHr0X1qDP8OWcYbh7+6wHxAvlHHNXzTpYFrT/aHg7Ge9E7 Z8N35J3PetVi/2XeUai7UyDGnuQ4pX2MeB3lhuygQT9UB0hHm9ixFD6cT90U+IlE3Omo +lVzKjyXpAj10iENv2Nb26gHwJTPBUD/7HT0QChFi+wtxNd4fArJyBQFzX7wZU+MlJAq qo/QIaGmkELUpAS0gzkYgPW3sw6F4w0U1LizNCzQmDHk9mtdic9Sg2clk40wRZJ0+gyW gE3T6YEXckW61LFI8hsXysfFonfkvuQdU8cC+AXmGI9x36Gu50Sj1IOavfzL4zKdd4kW v4xQ== X-Received: by 10.42.50.202 with SMTP id b10mr3532709icg.7.1369933404601; Thu, 30 May 2013 10:03:24 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id w8sm28106076igl.9.2013.05.30.10.03.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 10:03:23 -0700 (PDT) Sender: Warner Losh Subject: Re: [CFT] gcc: support for barcelona Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <51A77A22.3040103@FreeBSD.org> Date: Thu, 30 May 2013 11:03:20 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51A38CBD.6000702@FreeBSD.org> <51A3B8AB.5080808@FreeBSD.org> <521EEFA1-E116-41F5-B618-238E7AA092A8@bsdimp.com> <3C29AD82-077D-4E6B-94C7-5D069A130348__27528.1591726982$1369769859$gmane$org@FreeBSD.org> <51A5A6F4.8000501@FreeBSD.org> <65AA3A88-7B5E-439F-950D-47EDCDC3EAD1@bsdimp.com> <51A77A22.3040103@FreeBSD.org> To: Pedro Giffuni X-Mailer: Apple Mail (2.1085) X-Gm-Message-State: ALoCoQniqlalJdM+f9VuXvtyy70n9ezUUcGOMaAX4ZGP8273qRBhgu1mQ/v+hjhXdJ8FhYn2nwgU X-Mailman-Approved-At: Thu, 30 May 2013 17:21:28 +0000 Cc: amd64@FreeBSD.org, toolchain@FreeBSD.org, David Chisnall , Rui Paulo , Andriy Gapon X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 17:03:25 -0000 On May 30, 2013, at 10:11 AM, Pedro Giffuni wrote: > On 29.05.2013 11:06, Warner Losh wrote: >> On May 29, 2013, at 2:47 AM, David Chisnall wrote: >>=20 >>> On 29 May 2013, at 07:57, Andriy Gapon wrote: >>>=20 >>>> In fact, I am of opinion that while such bugs exist gcc should be = crowned back >>>> as a default compiler. >>> Seriously? Your show stopper bug is that, very occasionally, clang = emits incorrect debug info? And Steve's is that clang emits code that = is fully compliant with the C standard, but gives more floating point = precision than he wanted? >>>=20 >>> If those are the most serious problems we have with clang, then it's = time to remove gcc 4.2.1 from the tree right now. I wish the problems = that we had with it were so trivial... >> NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO = NO NO NO BTW, this was over the top for me, and I shouldn't have done this. >> ... >> There are serious problems with clang on arm right now. And it = doesn't support mips. Removing gcc is way premature. >>=20 >> Warner >>=20 >=20 > I didn't meant to start a clang vs gcc thread but it's evident that > we were actually in need of expressing the issues about clang > and the future of the tool chain. >=20 > IMHO: >=20 > - gcc has to go. It is old and, despite the scotch tape, unmaintained. > libstdc++ in particular really has to go first: it is too confusing to > have two C++ libraries where one of them is simply obsolete. > OpenOffice, for example was recently ported to clang and libc++ > however it will not work with the libstdc++ in base due to lack of > C++11 support. gcc is slated to be removed in 11. It is still useful in 10 to bootstrap = the external toolchain solution for non-tier 1 ports which otherwise = would be hard to build since we have no useful packages yet. Some ports = won't even build gcc by default in 10. Our external toolchain support is = brand new and shiny, but hasn't been through an end-to-end test yet on = all the platforms. Warner= From owner-freebsd-amd64@FreeBSD.ORG Thu May 30 20:29:15 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 27E55123 for ; Thu, 30 May 2013 20:29:15 +0000 (UTC) (envelope-from k.oikonomou@att.net) Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by mx1.freebsd.org (Postfix) with ESMTP id E5D583F5 for ; Thu, 30 May 2013 20:29:14 +0000 (UTC) Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-pink.research.att.com (Postfix) with ESMTP id E1209120702 for ; Thu, 30 May 2013 16:29:06 -0400 (EDT) Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.177.180]) by mail-blue.research.att.com (Postfix) with ESMTP id 1A574F0362 for ; Thu, 30 May 2013 16:29:08 -0400 (EDT) Received: from [135.207.130.101] ([135.207.130.101]) by bigmail.research.att.com (8.13.8+Sun/8.11.6) with ESMTP id r4UKT775016968 for ; Thu, 30 May 2013 16:29:08 -0400 (EDT) Message-ID: <51A7B693.8050705@att.net> Date: Thu, 30 May 2013 16:29:07 -0400 From: Kostas Oikonomou User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 To: freebsd-amd64@freebsd.org Subject: idle process keeping cpu 150% busy in freebsd 9.1-amd64 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 20:29:15 -0000 Hello, I am new to FreeBSD. I just installed 9.1-RELEASE-p3 (comes with PC-BSD 9.1) on an HP Pavilion s5100z. The machine has a dual-core AMD Athlon 7750 processor. What happens is that when I am doing nothing on the machine, one core is about 150% busy running the idle process: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11 152.9 0.0 0 32 ?? RL 8:19AM 2:14.50 [idle] root 0 0.0 0.1 0 2672 ?? DLs 8:19AM 0:00.36 [kernel] root 1 0.0 0.0 6276 416 ?? SLs 8:19AM 0:00.05 /sbin/init -- I have read [1]http://forums.freebsd.org/showthread.php?t=38757, which seems to be relevant, and I tried sysctl -w kern.eventtimer.timer= as they suggest, but to no avail. The same problem also on my Dell E6510 laptop, which has an Intel Core i7: the idle process is making one core run at about 400%. Any help would be greatly appreciated. Kostas References 1. http://forums.freebsd.org/showthread.php?t=38757 From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 12:03:39 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 66CCA4CA; Fri, 31 May 2013 12:03:39 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 40B05B31; Fri, 31 May 2013 12:03:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4VC3d8S038749; Fri, 31 May 2013 12:03:39 GMT (envelope-from jhb@freefall.freebsd.org) Received: (from jhb@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4VC3cY8038748; Fri, 31 May 2013 12:03:38 GMT (envelope-from jhb) Date: Fri, 31 May 2013 12:03:38 GMT Message-Id: <201305311203.r4VC3cY8038748@freefall.freebsd.org> To: mail@psvlan.com, jhb@FreeBSD.org, freebsd-amd64@FreeBSD.org From: jhb@FreeBSD.org Subject: Re: amd64/171110: Upgrade 9.1-BETA1 > RC1 issue X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 12:03:39 -0000 Synopsis: Upgrade 9.1-BETA1 > RC1 issue State-Changed-From-To: open->closed State-Changed-By: jhb State-Changed-When: Fri May 31 12:03:18 UTC 2013 State-Changed-Why: No longer an issue. http://www.freebsd.org/cgi/query-pr.cgi?pr=171110 From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 13:27:44 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 04E34942 for ; Fri, 31 May 2013 13:27:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id D5EF619C for ; Fri, 31 May 2013 13:27:43 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 2F77FB917; Fri, 31 May 2013 09:27:42 -0400 (EDT) From: John Baldwin To: freebsd-amd64@freebsd.org Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 Date: Fri, 31 May 2013 08:36:02 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <51A7B693.8050705@att.net> In-Reply-To: <51A7B693.8050705@att.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201305310836.02815.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 31 May 2013 09:27:42 -0400 (EDT) Cc: Kostas Oikonomou X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 13:27:44 -0000 On Thursday, May 30, 2013 4:29:07 pm Kostas Oikonomou wrote: > Hello, > I am new to FreeBSD. I just installed 9.1-RELEASE-p3 (comes with PC-BSD > 9.1) on an HP Pavilion s5100z. The machine has a dual-core AMD Athlon > 7750 processor. > What happens is that when I am doing nothing on the machine, one core > is about 150% > busy running the idle process: > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME > COMMAND > root 11 152.9 0.0 0 32 ?? RL 8:19AM 2:14.50 [idle] > root 0 0.0 0.1 0 2672 ?? DLs 8:19AM 0:00.36 > [kernel] > root 1 0.0 0.0 6276 416 ?? SLs 8:19AM 0:00.05 > /sbin/init -- > I have read [1]http://forums.freebsd.org/showthread.php?t=38757, which > seems to be relevant, and I tried > sysctl -w kern.eventtimer.timer= > as they suggest, but to no avail. > The same problem also on my Dell E6510 laptop, which has an Intel Core > i7: the idle process is making one core run at about 400%. > Any help would be greatly appreciated. > Kostas This is normal. The idle process has a thread per-CPU that the scheduler runs when the CPU is idle. Even if the CPU is actually asleep in a Cx state, the time it is asleep is accounted to the idle thread. I added a 'Z' flag to hide the idle threads in top (they are especially noisy on an idle machine with a lot of CPUs if you use top -SH). -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 14:47:35 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EAC14E91; Fri, 31 May 2013 14:47:35 +0000 (UTC) (envelope-from k.oikonomou@att.net) Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by mx1.freebsd.org (Postfix) with ESMTP id B31E58AB; Fri, 31 May 2013 14:47:35 +0000 (UTC) Received: from mail-green.research.att.com (unknown [135.207.178.10]) by mail-pink.research.att.com (Postfix) with ESMTP id 54968120614; Fri, 31 May 2013 10:47:33 -0400 (EDT) Received: from bigmail.research.att.com (bigmail.research.att.com [135.207.177.180]) by mail-green.research.att.com (Postfix) with ESMTP id 89BA7E01C9; Fri, 31 May 2013 10:46:54 -0400 (EDT) Received: from [135.207.130.101] ([135.207.130.101]) by bigmail.research.att.com (8.13.8+Sun/8.11.6) with ESMTP id r4VElYUD017010; Fri, 31 May 2013 10:47:34 -0400 (EDT) Message-ID: <51A8B806.5090100@att.net> Date: Fri, 31 May 2013 10:47:34 -0400 From: Kostas Oikonomou User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: John Baldwin Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 References: <51A7B693.8050705@att.net> <201305310836.02815.jhb@freebsd.org> In-Reply-To: <201305310836.02815.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:47:36 -0000 Thanks very much for the reply. Being new to FreeBSD, this still seems weird to me. (My background is Solaris.) On both machines, the core that's running at 150% in the case of the HP machine, and at 400% in the case of the Dell laptop, is causing the fans to come on. Would you call that "idle"? I'm worried that the cores will eventually be damaged. Kostas On 05/31/13 08:36 AM, John Baldwin wrote: > On Thursday, May 30, 2013 4:29:07 pm Kostas Oikonomou wrote: >> Hello, >> I am new to FreeBSD. I just installed 9.1-RELEASE-p3 (comes with PC-BSD >> 9.1) on an HP Pavilion s5100z. The machine has a dual-core AMD Athlon >> 7750 processor. >> What happens is that when I am doing nothing on the machine, one core >> is about 150% >> busy running the idle process: >> USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME >> COMMAND >> root 11 152.9 0.0 0 32 ?? RL 8:19AM 2:14.50 [idle] >> root 0 0.0 0.1 0 2672 ?? DLs 8:19AM 0:00.36 >> [kernel] >> root 1 0.0 0.0 6276 416 ?? SLs 8:19AM 0:00.05 >> /sbin/init -- >> I have read [1]http://forums.freebsd.org/showthread.php?t=38757, which >> seems to be relevant, and I tried >> sysctl -w kern.eventtimer.timer= >> as they suggest, but to no avail. >> The same problem also on my Dell E6510 laptop, which has an Intel Core >> i7: the idle process is making one core run at about 400%. >> Any help would be greatly appreciated. >> Kostas > This is normal. The idle process has a thread per-CPU that the scheduler runs > when the CPU is idle. Even if the CPU is actually asleep in a Cx state, the > time it is asleep is accounted to the idle thread. > > I added a 'Z' flag to hide the idle threads in top (they are especially > noisy on an idle machine with a lot of CPUs if you use top -SH). > From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 16:06:23 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DB5CA43D for ; Fri, 31 May 2013 16:06:23 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id B8124DAF for ; Fri, 31 May 2013 16:06:23 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9FBBBB915; Fri, 31 May 2013 12:06:22 -0400 (EDT) From: John Baldwin To: Kostas Oikonomou Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 Date: Fri, 31 May 2013 11:27:13 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <51A7B693.8050705@att.net> <201305310836.02815.jhb@freebsd.org> <51A8B806.5090100@att.net> In-Reply-To: <51A8B806.5090100@att.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201305311127.13846.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 31 May 2013 12:06:22 -0400 (EDT) Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 16:06:23 -0000 On Friday, May 31, 2013 10:47:34 am Kostas Oikonomou wrote: > Thanks very much for the reply. > > Being new to FreeBSD, this still seems weird to me. (My > background is Solaris.) > > On both machines, the core that's running at 150% in the > case of the HP machine, and at 400% in the case > of the Dell laptop, is causing the fans to come on. Would > you call that "idle"? I'm worried that the cores will > eventually be damaged. Do you have deeper Cx states enabled? By default FreeBSD will only enter C1. Try setting 'performance_cx_lowest=LOW' in /etc/rc.conf and either rebooting or running '/etc/rc.d/power_profile start' to see if that helps. You can see which Cx states are being used by running 'sysctl dev.cpu | grep cx_'. For example: dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 324us dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 300us dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% 0.00% 0.00% last 192us dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% 0.00% 0.00% last 157us This is on a machine with the default setup. After changing it to use the lowest setting: dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 5.84% 92.86% 1.28% last 145us dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.99% 94.92% 4.08% last 293us dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 dev.cpu.2.cx_lowest: C3 dev.cpu.2.cx_usage: 0.45% 88.50% 11.04% last 174us dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 dev.cpu.3.cx_lowest: C3 dev.cpu.3.cx_usage: 6.40% 86.89% 6.69% last 203us Another option is to run powerd which will throttle your CPUs down to lower clock speeds when they are idle. You can enable this by setting powerd_enable="YES" in /etc/rc.conf and running '/etc/rc.d/powerd start'. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 16:44:27 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BD050EEF for ; Fri, 31 May 2013 16:44:27 +0000 (UTC) (envelope-from k.oikonomou@att.net) Received: from nm7.access.bullet.mail.mud.yahoo.com (nm7.access.bullet.mail.mud.yahoo.com [66.94.237.208]) by mx1.freebsd.org (Postfix) with ESMTP id 65279F27 for ; Fri, 31 May 2013 16:44:27 +0000 (UTC) Received: from [66.94.237.193] by nm7.access.bullet.mail.mud.yahoo.com with NNFMP; 31 May 2013 16:38:33 -0000 Received: from [98.139.221.48] by tm4.access.bullet.mail.mud.yahoo.com with NNFMP; 31 May 2013 16:38:33 -0000 Received: from [127.0.0.1] by smtp101.sbc.mail.bf1.yahoo.com with NNFMP; 31 May 2013 16:38:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1370018313; bh=zb1mQ9Q91fnADkZ8tIZZjvRJYiLU4jjhjx7NvA2TxtA=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=okzQ5cXXVhxFLwf/qJUjX2S+Wcct+DheUxsqzjcGEDCun1yGy+rn6E73GcU4eIU/fgdZvglvGRZssRwMxrlDq1ZYLWHyN27gT3uLXR6PFwOmgdYiJUhFmAbfBuFJmgshyTsrzvRjHq2+WfFe3xGUpNqJfbWOU2CYCg1zTVeIrQ8= X-Yahoo-Newman-Id: 36217.94842.bm@smtp101.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 7RKogu0VM1k34lvSRDt7IPRpH6KrABV6tF6ukebgD14LmBH PC8pUrg0EMbycKJdqIZ4cXH7G4_PLhu.4L77s2wAdfOnq_rO6XAwi5WV2nuy Cod4u27oXzX0MTI37VO1TM0OYIqdJfWFe.hFewiHOxRJ5CjQHM4FXRt56_jJ eq3lt.lZWV7k1XqeLnKuIP6stYdw02jIaCVKOQK8IdkTj3eQZfU4MzCO9H8I YvVxLPVObArAtmPH03jO2sEQLnnt7v15GFT3IVluauaHrwCsl1tmlij1hyJl FsbgvtpjvWIddFlLunmMkI69E7D5x6hAXpOYf9wtnqEetNKOaGPQ6F7u5vKR GCwTDiT8pLXHGX.ONC4PQAVyDGlLgV27DvfGHdWU70lN2kivKnTOzFqFLH7W zsB3_mo2F8EBL_zQgi5IgAduHv.DX89h22ntzQhONiU4lysQ0G_u_1naJI7t mBTRwLiL28NY38aAJSrioI97doiub9bA- X-Yahoo-SMTP: dQDeuIqswBBZlqxPL_idatjeqZFsZlQC4MQ5I3DYpsI- X-Rocket-Received: from [135.207.130.55] (k.oikonomou@135.207.130.55 with plain) by smtp101.sbc.mail.bf1.yahoo.com with SMTP; 31 May 2013 09:38:32 -0700 PDT Message-ID: <51A8D208.2040702@att.net> Date: Fri, 31 May 2013 12:38:32 -0400 From: Kostas Oikonomou Organization: Home User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: John Baldwin Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 References: <51A7B693.8050705@att.net> <201305310836.02815.jhb@freebsd.org> <51A8B806.5090100@att.net> <201305311127.13846.jhb@freebsd.org> In-Reply-To: <201305311127.13846.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 16:44:27 -0000 John, Thanks. I am trying your suggestions on my Dell laptop (Intel Core i7, 4 cores). First off, my /etc/rc.conf already had ------------------------------------------------------------------------ # powerd: adaptive speed while on AC power, adaptive while on battery power powerd_enable="YES" powerd_flags="-a hiadaptive -b adaptive" # set CPU frequency ------------------------------------------------------------------------ and powerd was running. With that, the output of sysctl was like what you sent (the default). Now my /etc/rc.conf reads ------------------------------------------------------------------------ # powerd: adaptive speed while on AC power, adaptive while on battery power powerd_enable="YES" powerd_flags="-a hiadaptive -b adaptive" # set CPU frequency # per John Baldwin email performance_cx_lowest=LOW ------------------------------------------------------------------------ and I rebooted. This is what sysctl shows now: [ko@hui-neng ~]$ sysctl dev.cpu | grep cx_ dev.cpu.0.cx_supported: C1/3 C2/205 C3/245 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 18.65% 3.89% 77.44% last 2564us dev.cpu.1.cx_supported: C1/3 C2/205 C3/245 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 18.05% 3.42% 78.52% last 2426us dev.cpu.2.cx_supported: C1/3 C2/205 C3/245 dev.cpu.2.cx_lowest: C3 dev.cpu.2.cx_usage: 16.73% 3.63% 79.62% last 6272us dev.cpu.3.cx_supported: C1/3 C2/205 C3/245 dev.cpu.3.cx_lowest: C3 dev.cpu.3.cx_usage: 15.78% 3.42% 80.78% last 2413us But still one core is at 400%, and the fan started running: [ko@hui-neng ~]$ ps -aux | head USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11 398.0 0.0 0 64 ?? RL 12:28PM 5:24.77 [idle] root 0 0.0 0.1 0 2832 ?? DLs 12:28PM 0:00.54 [kernel] root 1 0.0 0.0 6276 416 ?? SLs 12:28PM 0:00.05 /sbin/init -- root 2 0.0 0.0 0 16 ?? DL 12:28PM 0:00.00 [crypto] root 3 0.0 0.0 0 16 ?? DL 12:28PM 0:00.00 [crypto return root 4 0.0 0.0 0 16 ?? DL 12:28PM 0:00.00 [ctl_thrd] root 5 0.0 0.0 0 16 ?? DL 12:28PM 0:00.00 [cbb0 event th root 6 0.0 0.0 0 16 ?? IL 12:28PM 0:00.00 [fw0_probe] root 7 0.0 0.0 0 96 ?? DL 12:28PM 0:00.02 [zfskern] [ko@hui-neng ~]$ Kostas On 05/31/2013 11:27, John Baldwin wrote: > On Friday, May 31, 2013 10:47:34 am Kostas Oikonomou wrote: >> Thanks very much for the reply. >> >> Being new to FreeBSD, this still seems weird to me. (My >> background is Solaris.) >> >> On both machines, the core that's running at 150% in the >> case of the HP machine, and at 400% in the case >> of the Dell laptop, is causing the fans to come on. Would >> you call that "idle"? I'm worried that the cores will >> eventually be damaged. > Do you have deeper Cx states enabled? By default FreeBSD will only enter C1. > Try setting 'performance_cx_lowest=LOW' in /etc/rc.conf and either rebooting > or running '/etc/rc.d/power_profile start' to see if that helps. You can see > which Cx states are being used by running 'sysctl dev.cpu | grep cx_'. For > example: > > dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 324us > dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.1.cx_lowest: C1 > dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 300us > dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.2.cx_lowest: C1 > dev.cpu.2.cx_usage: 100.00% 0.00% 0.00% last 192us > dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.3.cx_lowest: C1 > dev.cpu.3.cx_usage: 100.00% 0.00% 0.00% last 157us > > This is on a machine with the default setup. After changing it to use the > lowest setting: > > dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.0.cx_lowest: C3 > dev.cpu.0.cx_usage: 5.84% 92.86% 1.28% last 145us > dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.1.cx_lowest: C3 > dev.cpu.1.cx_usage: 0.99% 94.92% 4.08% last 293us > dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.2.cx_lowest: C3 > dev.cpu.2.cx_usage: 0.45% 88.50% 11.04% last 174us > dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.3.cx_lowest: C3 > dev.cpu.3.cx_usage: 6.40% 86.89% 6.69% last 203us > > Another option is to run powerd which will throttle your CPUs down to lower > clock speeds when they are idle. You can enable this by setting > powerd_enable="YES" in /etc/rc.conf and running '/etc/rc.d/powerd start'. > From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 16:16:30 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 509EB8B4; Fri, 31 May 2013 16:16:30 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2B865E1F; Fri, 31 May 2013 16:16:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4VGGUm6091128; Fri, 31 May 2013 16:16:30 GMT (envelope-from miwi@freefall.freebsd.org) Received: (from miwi@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4VGGTmQ091127; Fri, 31 May 2013 16:16:29 GMT (envelope-from miwi) Date: Fri, 31 May 2013 16:16:29 GMT Message-Id: <201305311616.r4VGGTmQ091127@freefall.freebsd.org> To: h.niemeyer@t-online.de, miwi@FreeBSD.org, freebsd-amd64@FreeBSD.org From: miwi@FreeBSD.org Subject: Re: amd64/179080: shared folders unter vmware workstation X-Mailman-Approved-At: Fri, 31 May 2013 17:15:23 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 16:16:30 -0000 Synopsis: shared folders unter vmware workstation State-Changed-From-To: open->closed State-Changed-By: miwi State-Changed-When: Fri May 31 16:16:29 UTC 2013 State-Changed-Why: i http://www.freebsd.org/cgi/query-pr.cgi?pr=179080 From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 16:16:41 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E77EC8BA; Fri, 31 May 2013 16:16:41 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C12B3E20; Fri, 31 May 2013 16:16:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4VGGfJi091225; Fri, 31 May 2013 16:16:41 GMT (envelope-from miwi@freefall.freebsd.org) Received: (from miwi@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4VGGfDM091224; Fri, 31 May 2013 16:16:41 GMT (envelope-from miwi) Date: Fri, 31 May 2013 16:16:41 GMT Message-Id: <201305311616.r4VGGfDM091224@freefall.freebsd.org> To: h.niemeyer@t-online.de, miwi@FreeBSD.org, freebsd-amd64@FreeBSD.org From: miwi@FreeBSD.org Subject: Re: amd64/179080: shared folders unter vmware workstation X-Mailman-Approved-At: Fri, 31 May 2013 17:15:30 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 16:16:42 -0000 Synopsis: shared folders unter vmware workstation State-Changed-From-To: closed->open State-Changed-By: miwi State-Changed-When: Fri May 31 16:16:41 UTC 2013 State-Changed-Why: reopen http://www.freebsd.org/cgi/query-pr.cgi?pr=179080 From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 17:20:41 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5C8F8ABC for ; Fri, 31 May 2013 17:20:41 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id 37564DC for ; Fri, 31 May 2013 17:20:40 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 959372767A for ; Fri, 31 May 2013 13:20:34 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVptLtwkZ1cU for ; Fri, 31 May 2013 13:20:34 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <51A8DBE2.2030901@egr.msu.edu> Date: Fri, 31 May 2013 13:20:34 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 References: <51A7B693.8050705@att.net> <201305310836.02815.jhb@freebsd.org> <51A8B806.5090100@att.net> <201305311127.13846.jhb@freebsd.org> <51A8D208.2040702@att.net> In-Reply-To: <51A8D208.2040702@att.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 17:20:41 -0000 On 05/31/13 12:38, Kostas Oikonomou wrote: > John, > > Thanks. I am trying your suggestions on my Dell laptop (Intel Core i7, > 4 cores). > > First off, my /etc/rc.conf already had > > ------------------------------------------------------------------------ > # powerd: adaptive speed while on AC power, adaptive while on battery power > powerd_enable="YES" > powerd_flags="-a hiadaptive -b adaptive" # set CPU frequency > ------------------------------------------------------------------------ > > and powerd was running. With that, the output of sysctl was like what > you sent (the default). > > Now my /etc/rc.conf reads > ------------------------------------------------------------------------ > # powerd: adaptive speed while on AC power, adaptive while on battery power > powerd_enable="YES" > powerd_flags="-a hiadaptive -b adaptive" # set CPU frequency > > # per John Baldwin email > performance_cx_lowest=LOW > ------------------------------------------------------------------------ Take a look at this excellent guide too: https://wiki.freebsd.org/TuningPowerConsumption From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 16:20:42 2013 Return-Path: Delivered-To: freebsd-amd64@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4794BA11; Fri, 31 May 2013 16:20:42 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2191EE58; Fri, 31 May 2013 16:20:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4VGKgd1092889; Fri, 31 May 2013 16:20:42 GMT (envelope-from miwi@freefall.freebsd.org) Received: (from miwi@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4VGKfLD092888; Fri, 31 May 2013 16:20:41 GMT (envelope-from miwi) Date: Fri, 31 May 2013 16:20:41 GMT Message-Id: <201305311620.r4VGKfLD092888@freefall.freebsd.org> To: h.niemeyer@t-online.de, miwi@FreeBSD.org, freebsd-amd64@FreeBSD.org From: miwi@FreeBSD.org Subject: Re: amd64/179080: shared folders unter vmware workstation X-Mailman-Approved-At: Fri, 31 May 2013 17:26:43 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 16:20:42 -0000 Synopsis: shared folders unter vmware workstation State-Changed-From-To: open->closed State-Changed-By: miwi State-Changed-When: Fri May 31 16:16:46 UTC 2013 State-Changed-Why: Hi, Ich wuerde dir empfehlen den port emulators/open-vm-tools-nox11 zu installieren und es mit mount -t vmhgfs .host: /mnt probieren. Ich hoffe das hilft dir weiter :-). Ich moechte dich bitten das naechste mal die fragen an eine der vielen mailinglisten zu schicken. Wir haben es auch einige mailinglisten in Deutsch. Das Projekt selbst ist komplett in english so sollten auch probleme reports in english gehalten werden. Danke fuer dein Verstaendniss. LG Martin http://www.freebsd.org/cgi/query-pr.cgi?pr=179080 From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 19:00:40 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D26DE6BF for ; Fri, 31 May 2013 19:00:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id B24A57EF for ; Fri, 31 May 2013 19:00:40 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DF0D5B918; Fri, 31 May 2013 15:00:39 -0400 (EDT) From: John Baldwin To: Kostas Oikonomou Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 Date: Fri, 31 May 2013 14:52:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <51A7B693.8050705@att.net> <201305311127.13846.jhb@freebsd.org> <51A8D208.2040702@att.net> In-Reply-To: <51A8D208.2040702@att.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201305311452.04674.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 31 May 2013 15:00:40 -0400 (EDT) Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 19:00:40 -0000 On Friday, May 31, 2013 12:38:32 pm Kostas Oikonomou wrote: > John, > > Thanks. I am trying your suggestions on my Dell laptop (Intel Core i7, > 4 cores). > > First off, my /etc/rc.conf already had > > ------------------------------------------------------------------------ > # powerd: adaptive speed while on AC power, adaptive while on battery power > powerd_enable="YES" > powerd_flags="-a hiadaptive -b adaptive" # set CPU frequency > ------------------------------------------------------------------------ > > and powerd was running. With that, the output of sysctl was like what > you sent (the default). > > Now my /etc/rc.conf reads > ------------------------------------------------------------------------ > # powerd: adaptive speed while on AC power, adaptive while on battery power > powerd_enable="YES" > powerd_flags="-a hiadaptive -b adaptive" # set CPU frequency > > # per John Baldwin email > performance_cx_lowest=LOW > ------------------------------------------------------------------------ > > and I rebooted. This is what sysctl shows now: > > > [ko@hui-neng ~]$ sysctl dev.cpu | grep cx_ > dev.cpu.0.cx_supported: C1/3 C2/205 C3/245 > dev.cpu.0.cx_lowest: C3 > dev.cpu.0.cx_usage: 18.65% 3.89% 77.44% last 2564us > dev.cpu.1.cx_supported: C1/3 C2/205 C3/245 > dev.cpu.1.cx_lowest: C3 > dev.cpu.1.cx_usage: 18.05% 3.42% 78.52% last 2426us > dev.cpu.2.cx_supported: C1/3 C2/205 C3/245 > dev.cpu.2.cx_lowest: C3 > dev.cpu.2.cx_usage: 16.73% 3.63% 79.62% last 6272us > dev.cpu.3.cx_supported: C1/3 C2/205 C3/245 > dev.cpu.3.cx_lowest: C3 > dev.cpu.3.cx_usage: 15.78% 3.42% 80.78% last 2413us > > > But still one core is at 400%, and the fan started running: The core will always look like it is "running" in top, even when it is asleep. That is just how FreeBSD accounts for idle CPU time. The only thing I was hoping would change is the fan having to run. You can try kldload'ing coretemp and seeing if the processor temperatures are different when deeper CX states are enabled (or when powerd is running) to see if it is having any affect on the temperatures in your box. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Fri May 31 23:38:14 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 387E162F for ; Fri, 31 May 2013 23:38:14 +0000 (UTC) (envelope-from k.oikonomou@att.net) Received: from nm12.access.bullet.mail.mud.yahoo.com (nm12.access.bullet.mail.mud.yahoo.com [66.94.237.213]) by mx1.freebsd.org (Postfix) with ESMTP id 02EC71BE for ; Fri, 31 May 2013 23:38:13 +0000 (UTC) Received: from [66.94.237.196] by nm12.access.bullet.mail.mud.yahoo.com with NNFMP; 31 May 2013 23:38:07 -0000 Received: from [98.139.221.48] by tm7.access.bullet.mail.mud.yahoo.com with NNFMP; 31 May 2013 23:38:07 -0000 Received: from [127.0.0.1] by smtp101.sbc.mail.bf1.yahoo.com with NNFMP; 31 May 2013 23:38:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1370043487; bh=7Zk4AmPdGjnHLy317rmorR/lMtsy3gzcgctZ70t63kY=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:Message-ID:Date:From:Organization:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=PVOFUGGfaV5lIC6wDpmpOKPzcwvRrWA9nS1Vla7A5rcha46jAJEBf4ICm2qxmXlh5bPl7QVDsyvZ17Oavn7XStq4bf97LmJGXJG0lfxb/CFZMV9Sm+2xp0pI83sbd2D8W5AoNaHbwvUw11aJQEvQaL17XFLdiCp1hk/et5TMKfA= X-Yahoo-Newman-Id: 162676.98797.bm@smtp101.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: WBog1jkVM1kRGkMy9hJHK4vq9Gw06E0dYdLf5akagJfS2oc ow0cxR6oDGEXiOYydzxKx1K_3VhJq7Z7JdQ6w5gwEVTfCIsIoaCH7jYbUUmj LvN0wpxZYVT1nj.DtRojdjXvJZKLmLmpSH_UfxzUIn1LP114msJiO.G9D.We .j0wA362LqZFA3PHz0dRbWyWs8UZaWxTFTwz_eKGXo5uypv0zJdaiylzr4FV HepAmqto0Z2j0BrnZz6CBV1XmnQCfezHY5twNeoqimMM02uT.q_nGg0O1V7h yH0z.AJT9vms7IfJCYLSNgL5LLITJx3TsGOmP4F2XFYZpPByx6PNowvhgizl Wao026ZPz6ketXgepmAaEJkFRj.c4VXUUswLcua2yqGWAgp3cOzeSvTx_UGe MxHyl2F80pc6YStGb2vRoQ7IcKpZX1ww1rsOudSnxcb1bE4crHYG6fTeL2t9 euDw3WztEGFHaEyDkoQtSFabVE06eUj3cw_W1opas_y03pv3RsJGFdbIQjuM ._2Sd X-Yahoo-SMTP: dQDeuIqswBBZlqxPL_idatjeqZFsZlQC4MQ5I3DYpsI- X-Rocket-Received: from [135.207.38.76] (k.oikonomou@67.84.197.59 with plain) by smtp101.sbc.mail.bf1.yahoo.com with SMTP; 31 May 2013 16:38:06 -0700 PDT Message-ID: <51A90CBE.4020508@att.net> Date: Fri, 31 May 2013 16:49:02 -0400 From: Kostas Oikonomou Organization: Home User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: John Baldwin Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 References: <51A7B693.8050705@att.net> <201305311127.13846.jhb@freebsd.org> <51A8D208.2040702@att.net> <201305311452.04674.jhb@freebsd.org> In-Reply-To: <201305311452.04674.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 23:38:14 -0000 The core will always look like it is "running" in top, even when it is asleep. That is just how FreeBSD accounts for idle CPU time. The only thing I was hoping would change is the fan having to run. You can try kldload'ing coretemp and seeing if the processor temperatures are different when deeper CX states are enabled (or when powerd is running) to see if it is having any affect on the temperatures in your box. First the good news. It looks like the problem is solved on the laptop (Core i7). It took one more reboot after I put "performance_cx_lowest=LOW" in /etc/rc.conf. However, the problem is still there on the HP desktop (AMD 7550). This has only Cx state, C1, so "performance_cx_lowest=LOW" had no effect. The symptoms with this machine are that top does not show anything running besides idle, and neither does ps -aux. Yet the Gnome System monitor applet that I have on the bottom panel shows significant cpu activity. And the fan starts running within 5 minutes after the system finishes booting. Here is what top -S -H says: last pid: 2645; load averages: 1.14, 0.78, 0.34 up 0+00:02:17 19:31:35 356 processes: 3 running, 338 sleeping, 15 waiting CPU: 0.2% user, 0.0% nice, 18.9% system, 0.0% interrupt, 80.9% idle Mem: 187M Active, 36M Inact, 354M Wired, 13M Cache, 3323M Free Swap: 2048M Total, 2048M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 155 ki31 0K 32K CPU0 0 1:45 89.99% idle{idle: cpu0} 11 root 155 ki31 0K 32K RUN 1 1:40 83.98% idle{idle: cpu1} 0 root -16 0 0K 2672K sched 0 1:03 0.00% kernel{swapper} 462 root -21 r31 912M 33216K select 0 0:10 0.00% Xorg 1968 ko 52 0 209M 7144K select 0 0:04 0.00% pulseaudio{pulseaudio} 1968 ko 52 0 209M 7144K select 1 0:03 0.00% pulseaudio{pulseaudio} 7 root -16 - 0K 16K ccb_sc 0 0:02 0.00% xpt_thrd 12 root -84 - 0K 240K WAIT 1 0:01 0.00% intr{irq1: atkbd0} 12 root -60 - 0K 240K WAIT 0 0:01 0.00% intr{swi4: clock} 1969 ko 20 0 323M 21968K select 0 0:00 0.00% gnome-panel{gnome-panel} 12 root -96 - 0K 240K WAIT 1 0:00 0.00% intr{irq16: vgapci0+} 2196 ko 20 0 294M 18052K select 0 0:00 0.00% gnome-netstatus-app{gnome- 1811 ko 20 0 320M 19116K select 1 0:00 0.00% gnome-settings-daem{gnome- 15 root -68 - 0K 128K - 1 0:00 0.00% usb{usbus0} 2200 ko 20 0 360M 21808K select 1 0:00 0.00% clock-applet{clock-applet} 1458 root 30 10 10376K 3448K select 0 0:00 0.00% devd 2028 ko 20 0 218M 25652K select 0 0:00 0.00% python 2272 ko 20 0 280M 20044K select 1 0:00 0.00% gnome-terminal{gnome-termi 2198 ko 20 0 295M 20552K select 1 0:00 0.00% stickynotes_applet{stickyn 1405 ko 20 0 156M 13152K select 0 0:00 0.00% gnome-session{gnome-sessio 417 haldaemon 20 0 56952K 6136K select 0 0:00 0.00% hald{hald} And ps -aux | head: [ko@wiley ~]$ ps -aux | head USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 11 175.9 0.0 0 32 ?? RL 7:29PM 6:53.36 [idle] root 0 0.0 0.1 0 2672 ?? DLs 7:29PM 0:00.37 [kernel] root 1 0.0 0.0 6276 416 ?? SLs 7:29PM 0:00.07 /sbin/init -- root 2 0.0 0.0 0 16 ?? DL 7:29PM 0:00.00 [crypto] root 3 0.0 0.0 0 16 ?? DL 7:29PM 0:00.00 [crypto returns] root 4 0.0 0.0 0 16 ?? DL 7:29PM 0:00.00 [ctl_thrd] root 5 0.0 0.0 0 96 ?? DL 7:29PM 0:00.03 [zfskern] I don't understand what is going on. Kostas From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 1 08:57:51 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 447D43C9; Sat, 1 Jun 2013 08:57:51 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) by mx1.freebsd.org (Postfix) with ESMTP id 907A77A6; Sat, 1 Jun 2013 08:57:50 +0000 (UTC) Received: by mail-bk0-f41.google.com with SMTP id jc10so1124797bkc.14 for ; Sat, 01 Jun 2013 01:57:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; bh=eaUlf1g8c0yNeKxVT8fvLU+8QQORPe1Rt8dIwuxh898=; b=lVZXYlxAOJWRYWy+ezlLJ8oOFdYZ3h6iCci5RZd8M4AzDrXEloluDj21GVz1pdWRfW lfAeQIchn8B2MtNGknQOCSQSlNS4WlL/DukLXm+DJxcwxXoq7UrCgno6UZa2RONWpJiM djYZyIBRR5n7V6SDu7PXP5C+M6igWcA7on3TyCIUzrMXPWjS3KEEE/Pl5p1jsr3UcsVp ppmeQkjIzSRY94rGSeBWVE2hkfDUOwmuJ7h2aoH4HB5kqdXDvSx04oPAtSxZGfYk4Jds tUo156w735FLtWSc60JmQMBX2lfe5csHqutf8Myy1hfRpLwREQm3z6ptDIvFYWVfq5FW 5nHg== X-Received: by 10.205.103.134 with SMTP id di6mr4398605bkc.178.1370077069427; Sat, 01 Jun 2013 01:57:49 -0700 (PDT) Received: from ernst.home (p578E0D3F.dip0.t-ipconnect.de. [87.142.13.63]) by mx.google.com with ESMTPSA id fz10sm16294347bkc.9.2013.06.01.01.57.47 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 01 Jun 2013 01:57:48 -0700 (PDT) Date: Sat, 1 Jun 2013 10:57:46 +0200 From: Gary Jennejohn To: John Baldwin Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 Message-ID: <20130601105746.6e3dc51d@ernst.home> In-Reply-To: <201305311127.13846.jhb@freebsd.org> References: <51A7B693.8050705@att.net> <201305310836.02815.jhb@freebsd.org> <51A8B806.5090100@att.net> <201305311127.13846.jhb@freebsd.org> X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.17; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Kostas Oikonomou , freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jun 2013 08:57:51 -0000 On Fri, 31 May 2013 11:27:13 -0400 John Baldwin wrote: > On Friday, May 31, 2013 10:47:34 am Kostas Oikonomou wrote: > > Thanks very much for the reply. > > > > Being new to FreeBSD, this still seems weird to me. (My > > background is Solaris.) > > > > On both machines, the core that's running at 150% in the > > case of the HP machine, and at 400% in the case > > of the Dell laptop, is causing the fans to come on. Would > > you call that "idle"? I'm worried that the cores will > > eventually be damaged. > > Do you have deeper Cx states enabled? By default FreeBSD will only enter C1. > Try setting 'performance_cx_lowest=LOW' in /etc/rc.conf and either rebooting > or running '/etc/rc.d/power_profile start' to see if that helps. You can see > which Cx states are being used by running 'sysctl dev.cpu | grep cx_'. For > example: > > dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 324us > dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.1.cx_lowest: C1 > dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 300us > dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.2.cx_lowest: C1 > dev.cpu.2.cx_usage: 100.00% 0.00% 0.00% last 192us > dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.3.cx_lowest: C1 > dev.cpu.3.cx_usage: 100.00% 0.00% 0.00% last 157us > > This is on a machine with the default setup. After changing it to use the > lowest setting: > > dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.0.cx_lowest: C3 > dev.cpu.0.cx_usage: 5.84% 92.86% 1.28% last 145us > dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.1.cx_lowest: C3 > dev.cpu.1.cx_usage: 0.99% 94.92% 4.08% last 293us > dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.2.cx_lowest: C3 > dev.cpu.2.cx_usage: 0.45% 88.50% 11.04% last 174us > dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 > dev.cpu.3.cx_lowest: C3 > dev.cpu.3.cx_usage: 6.40% 86.89% 6.69% last 203us > > Another option is to run powerd which will throttle your CPUs down to lower > clock speeds when they are idle. You can enable this by setting > powerd_enable="YES" in /etc/rc.conf and running '/etc/rc.d/powerd start'. > powerd works. I have: CPU: AMD Phenom(tm) II X6 1090T Processor (3214.70-MHz K8-class CPU) FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs with a modified powerd running all the time and my cores run mostly at 800MHz. -- Gary Jennejohn From owner-freebsd-amd64@FreeBSD.ORG Sat Jun 1 11:26:14 2013 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 121BD497; Sat, 1 Jun 2013 11:26:14 +0000 (UTC) (envelope-from prvs=18641c54ab=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 861EBB68; Sat, 1 Jun 2013 11:26:13 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50004107974.msg; Sat, 01 Jun 2013 12:26:06 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 01 Jun 2013 12:26:06 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=18641c54ab=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: From: "Steven Hartland" To: "Kostas Oikonomou" , "John Baldwin" References: <51A7B693.8050705@att.net> <201305311127.13846.jhb@freebsd.org> <51A8D208.2040702@att.net> <201305311452.04674.jhb@freebsd.org> <51A90CBE.4020508@att.net> Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 Date: Sat, 1 Jun 2013 12:25:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-amd64@freebsd.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jun 2013 11:26:14 -0000 ----- Original Message ----- From: "Kostas Oikonomou" To: "John Baldwin" Cc: Sent: Friday, May 31, 2013 9:49 PM Subject: Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 > The core will always look like it is "running" in top, even when it is asleep. That is just how FreeBSD accounts for idle CPU > time. The only thing I was hoping would change is the fan having to run. You can try kldload'ing coretemp and seeing if the > processor temperatures are different when deeper CX states are enabled (or when powerd is running) to see if it is having any > affect on the temperatures in your box. > > First the good news. It looks like the problem is solved on the laptop (Core i7). It took one more reboot after I put > "performance_cx_lowest=LOW" in /etc/rc.conf. > > However, the problem is still there on the HP desktop (AMD 7550). This has only > Cx state, C1, so "performance_cx_lowest=LOW" had no effect. > > The symptoms with this machine are that top does not show anything running besides idle, and neither does ps -aux. Yet the > Gnome System monitor applet that I have on the bottom panel shows significant cpu activity. > And the fan starts running within 5 minutes after the system finishes booting. > > Here is what top -S -H says: > > > last pid: 2645; load averages: 1.14, 0.78, 0.34 up 0+00:02:17 19:31:35 > 356 processes: 3 running, 338 sleeping, 15 waiting > CPU: 0.2% user, 0.0% nice, 18.9% system, 0.0% interrupt, 80.9% idle > Mem: 187M Active, 36M Inact, 354M Wired, 13M Cache, 3323M Free > Swap: 2048M Total, 2048M Free > > PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 11 root 155 ki31 0K 32K CPU0 0 1:45 89.99% idle{idle: cpu0} > 11 root 155 ki31 0K 32K RUN 1 1:40 83.98% idle{idle: cpu1} > 0 root -16 0 0K 2672K sched 0 1:03 0.00% kernel{swapper} > 462 root -21 r31 912M 33216K select 0 0:10 0.00% Xorg > 1968 ko 52 0 209M 7144K select 0 0:04 0.00% pulseaudio{pulseaudio} > 1968 ko 52 0 209M 7144K select 1 0:03 0.00% pulseaudio{pulseaudio} > 7 root -16 - 0K 16K ccb_sc 0 0:02 0.00% xpt_thrd > 12 root -84 - 0K 240K WAIT 1 0:01 0.00% intr{irq1: atkbd0} > 12 root -60 - 0K 240K WAIT 0 0:01 0.00% intr{swi4: clock} > 1969 ko 20 0 323M 21968K select 0 0:00 0.00% gnome-panel{gnome-panel} > 12 root -96 - 0K 240K WAIT 1 0:00 0.00% intr{irq16: vgapci0+} > 2196 ko 20 0 294M 18052K select 0 0:00 0.00% gnome-netstatus-app{gnome- > 1811 ko 20 0 320M 19116K select 1 0:00 0.00% gnome-settings-daem{gnome- > 15 root -68 - 0K 128K - 1 0:00 0.00% usb{usbus0} > 2200 ko 20 0 360M 21808K select 1 0:00 0.00% clock-applet{clock-applet} > 1458 root 30 10 10376K 3448K select 0 0:00 0.00% devd > 2028 ko 20 0 218M 25652K select 0 0:00 0.00% python > 2272 ko 20 0 280M 20044K select 1 0:00 0.00% gnome-terminal{gnome-termi > 2198 ko 20 0 295M 20552K select 1 0:00 0.00% stickynotes_applet{stickyn > 1405 ko 20 0 156M 13152K select 0 0:00 0.00% gnome-session{gnome-sessio > 417 haldaemon 20 0 56952K 6136K select 0 0:00 0.00% hald{hald} Assuming this is a dual core machine, your missing ~25% of your overall CPU time, identifying where this is might help. Does the following give any hints to this: top -S -H -I -C -s1 Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk.