Re: Leaving the Desktop Market
El día Saturday, May 03, 2014 a las 04:59:48PM -0700, Kevin Oberman escribió: Available is not required. Set it to C8. That guarantees that you will use the lowest available. The correct incantation in rc.conf is Cmax. performance_cx_lowest=Cmax economy_cx_lowest=Cmax But, unless you want laggy performance, you will probably also want: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 in /boot/loader.conf. Low Cx states and TCC/throttling simply don't mix well and TCC is not effective, as mentioned earlier in this thread. In the output of: $ sysctl -a | fgrep dev.cpu.0.freq_ dev.cpu.0.freq_levels: 1600/2000 1333/1533 1066/1066 800/600 what does mean the value after the slash .../ ? Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Leaving the Desktop Market
Am 05.05.2014 11:17, schrieb Matthias Apitz: El día Saturday, May 03, 2014 a las 04:59:48PM -0700, Kevin Oberman escribió: Available is not required. Set it to C8. That guarantees that you will use the lowest available. The correct incantation in rc.conf is Cmax. performance_cx_lowest=Cmax economy_cx_lowest=Cmax But, unless you want laggy performance, you will probably also want: hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 in /boot/loader.conf. Low Cx states and TCC/throttling simply don't mix well and TCC is not effective, as mentioned earlier in this thread. In the output of: $ sysctl -a | fgrep dev.cpu.0.freq_ dev.cpu.0.freq_levels: 1600/2000 1333/1533 1066/1066 800/600 what does mean the value after the slash .../ ? This is the nominal power consumption (TDP) in mW for that level. These numbers correspond to 2W at 1600MHz and 0.6W at 800MHz. Is this an Atom or some other ultra-low power CPU? Regards, STefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
gfortran48: compiler issue with f77 code: configure: error: Fortran 77 compiler cannot create executables
I have some F77 code that compiled fine using the GNU autotool environment, having the macro AC_PROG_F77 in configure.ac. The project compiles fine on Linux Ubuntu 14.04 LTS (gfortran version 4.8). But since a while it doesn't on FreeBSD 9.2/10/11 anymore! I miss something here and I do not know what. I use Fortran not on a regular basis, so this problem caught me, again, on the wrong foor. Further details see below. Regards, Oliver -- Before I start reporting the issue, this is what I have installed as the base: language ports: gcc-4.7.3_1 gcc48-4.8.3.s20140424 autotools: autoconf-2.69 autoconf-wrapper-20131203 autoconf213-2.13.000227_6 autogen-5.12_2 automake-1.14 automake-wrapper-20131203 automake14-1.4.6_6 automoc4-0.9.88_3 autotools-20130627 As shown below, the autotools are incapable of detecting installed compilers. As also reported below, gfortran48 miscompiles (while the gfortran 4.8.2 on Ubuntu 14.04 LTS does not have a problem with the very same code!) and gfortran47 is missing obviously the correct path to its libraries. My configure.ac file of the project contains this lines: #AC_PROG_F77([gfortran48 gfortran47 gfortran46 gfortran f77]) AC_PROG_F77 # Checks for header files. #AC_HEADER_STDC AC_CHECK_HEADERS([stdlib.h string.h]) # LT_INIT([disable-shared]) # AM_INIT_AUTOMAKE # AC_CONFIG_FILES([Makefile src/Makefile doc/Makefile ]) # AC_OUTPUT The command sequence to prepare the source is: aclocal ; autoheader ; autoconf ; libtoolize -c ; automake -ac And ./configure then dies with this: checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgfortran... no checking for pgf95... no checking for lf95... no checking for ftn... no checking for nagfor... no checking whether the Fortran 77 compiler works... no configure: error: in `/home/ohartmann/Projects/oepik': configure: error: Fortran 77 compiler cannot create executables See `config.log' for more details Well, this looks pretty nice! If the usage of the compiler is selected to be gfortran48 via AC_PROG_F77([gfortran48 gfortran47 gfortran46 gfortran f77]) the I receive this crap: checking for gfortran48... gfortran48 checking whether the Fortran 77 compiler works... no configure: error: in `/home/ohartmann/Projects/oepik': configure: error: Fortran 77 compiler cannot create executables See `config.log' for more details Checking config.log as suggested I find this portion: [...] configure:2426: $? = 1 configure:2415: gfortran48 -qversion 5 gfortran48: error: unrecognized command line option '-qversion' gfortran48: fatal error: no input files compilation terminated. configure:2426: $? = 1 configure:2441: checking whether the Fortran 77 compiler works configure:2463: gfortran48 conftest.f 5 f951: internal compiler error: Illegal instruction Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. configure:2467: $? = 1 configure:2505: result: no configure: failed program was: | program main | | end configure:2510: error: in `/home/ohartmann/Projects/oepik': configure:2513: error: Fortran 77 compiler cannot create executables See `config.log' for more details [...] This is funny - the FreeBSD port can not compile simple F77 code? With gfortran47 using, I get this: [...] configure:2527: checking for suffix of executables configure:2534: gfortran47 -o conftest conftest.f 5 configure:2538: $? = 0 configure:2560: result: configure:2576: checking whether we are cross compiling configure:2584: gfortran47 -o conftest conftest.f 5 configure:2588: $? = 0 configure:2595: ./conftest /lib/libgcc_s.so.1: version GCC_4.6.0 required by /usr/local/lib/gcc47/libgfortran.so.3 not found configure:2599: $? = 1 configure:2606: error: in `/home/ohartmann/Projects/oepik': configure:2610: error: cannot run Fortran 77 compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details [...] signature.asc Description: PGP signature
Re: Leaving the Desktop Market
El día Monday, May 05, 2014 a las 12:09:02PM +0200, Stefan Esser escribió: In the output of: $ sysctl -a | fgrep dev.cpu.0.freq_ dev.cpu.0.freq_levels: 1600/2000 1333/1533 1066/1066 800/600 what does mean the value after the slash .../ ? This is the nominal power consumption (TDP) in mW for that level. These numbers correspond to 2W at 1600MHz and 0.6W at 800MHz. Thanks. Is this an Atom or some other ultra-low power CPU? dmesg shows: ... CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1596.22-MHz 686-class CPU) Origin = GenuineIntel Id = 0x106c2 Family = 0x6 Model = 0x1c Stepping = 2 Features=0xbfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x40c39dSSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 1073741824 (1024 MB) avail memory = 1004568576 (958 MB) Event timer LAPIC quality 400 ACPI APIC Table: ACRSYS ACRPRDCT FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP/HT): APIC ID: 1 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard ... Btw: the values in /etc/rc.conf performance_cx_lowest=Cmax economy_cx_lowest=Cmax to which launched process they belong as config values? Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: gfortran48: compiler issue with f77 code: configure: error: Fortran 77 compiler cannot create executables
Am Mon, 5 May 2014 12:26:21 +0200 O. Hartmann ohart...@zedat.fu-berlin.de schrieb: Following some reports and recall myself an earlier issue with this, I remember to have to provide -Wl,-rpath=/usr/local/lib/gcc48 to the FFLAGS. This is also the case for the gcc/gfortran in 11.0-CURRENT which defaults to gcc 4.7. I'm used not to provide the -Wl,-rpath= option when using different C compilers along with FreeBSD, why is that so for Fortran? And why is the autotool suite in FreeBSD not recognising the proper Fortran? Is there a way to make the -Wl,-rpath option a default in the configure.ac? Since I use the autotools on several platforms (Linux and FreeBSD) I get really confused this behaviour. Maybe I'm missing something important here and I would appreciate if someone can shed some light onto it. Thanks in advance, Oliver I have some F77 code that compiled fine using the GNU autotool environment, having the macro AC_PROG_F77 in configure.ac. The project compiles fine on Linux Ubuntu 14.04 LTS (gfortran version 4.8). But since a while it doesn't on FreeBSD 9.2/10/11 anymore! I miss something here and I do not know what. I use Fortran not on a regular basis, so this problem caught me, again, on the wrong foor. Further details see below. Regards, Oliver -- Before I start reporting the issue, this is what I have installed as the base: language ports: gcc-4.7.3_1 gcc48-4.8.3.s20140424 autotools: autoconf-2.69 autoconf-wrapper-20131203 autoconf213-2.13.000227_6 autogen-5.12_2 automake-1.14 automake-wrapper-20131203 automake14-1.4.6_6 automoc4-0.9.88_3 autotools-20130627 As shown below, the autotools are incapable of detecting installed compilers. As also reported below, gfortran48 miscompiles (while the gfortran 4.8.2 on Ubuntu 14.04 LTS does not have a problem with the very same code!) and gfortran47 is missing obviously the correct path to its libraries. My configure.ac file of the project contains this lines: #AC_PROG_F77([gfortran48 gfortran47 gfortran46 gfortran f77]) AC_PROG_F77 # Checks for header files. #AC_HEADER_STDC AC_CHECK_HEADERS([stdlib.h string.h]) # LT_INIT([disable-shared]) # AM_INIT_AUTOMAKE # AC_CONFIG_FILES([Makefile src/Makefile doc/Makefile ]) # AC_OUTPUT The command sequence to prepare the source is: aclocal ; autoheader ; autoconf ; libtoolize -c ; automake -ac And ./configure then dies with this: checking for g77... no checking for xlf... no checking for f77... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for xlf90... no checking for f90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for xlf95... no checking for f95... no checking for fort... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgfortran... no checking for pgf95... no checking for lf95... no checking for ftn... no checking for nagfor... no checking whether the Fortran 77 compiler works... no configure: error: in `/home/ohartmann/Projects/oepik': configure: error: Fortran 77 compiler cannot create executables See `config.log' for more details Well, this looks pretty nice! If the usage of the compiler is selected to be gfortran48 via AC_PROG_F77([gfortran48 gfortran47 gfortran46 gfortran f77]) the I receive this crap: checking for gfortran48... gfortran48 checking whether the Fortran 77 compiler works... no configure: error: in `/home/ohartmann/Projects/oepik': configure: error: Fortran 77 compiler cannot create executables See `config.log' for more details Checking config.log as suggested I find this portion: [...] configure:2426: $? = 1 configure:2415: gfortran48 -qversion 5 gfortran48: error: unrecognized command line option '-qversion' gfortran48: fatal error: no input files compilation terminated. configure:2426: $? = 1 configure:2441: checking whether the Fortran 77 compiler works configure:2463: gfortran48 conftest.f 5 f951: internal compiler error: Illegal instruction Please submit a full bug report, with preprocessed source if appropriate. See http://gcc.gnu.org/bugs.html for instructions. configure:2467: $? = 1 configure:2505: result: no configure: failed program was: | program main | | end configure:2510: error: in `/home/ohartmann/Projects/oepik': configure:2513: error: Fortran 77 compiler cannot create executables See `config.log' for more details [...] This is funny - the FreeBSD port can not compile simple F77 code? With gfortran47 using, I get this: [...] configure:2527: checking for suffix of executables configure:2534: gfortran47 -o
Re: Leaving the Desktop Market
El día Monday, May 05, 2014 a las 12:36:08PM +0200, Matthias Apitz escribió: Btw: the values in /etc/rc.conf performance_cx_lowest=Cmax economy_cx_lowest=Cmax to which launched process they belong as config values? Forget the question. The values are used by /etc/rc.d/power_profile which is launched when AC goes away or comes back. Maybe we should have a note about this in rc.conf(5) that these values are passed to this script or the names should be changed to power_profile_performance_cx_lowest power_profile_economy_cx_lowest matthias matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: need info about newcons in jails
On Sat, 03 May 2014 07:15:14 -0400 Fbsd8 fb...@a1poweruser.com wrote: Hello list. Hi, Looking for information about using newcons as the terminal driver in xorg for desktop in a jail. I don't really understand how that can be related. software running in jail doing output to same terminal in which jail started. So if you open xterm, and start jail from it, jailed s/w will output into xterm window. If you run jail from system virtual terminal syscons or vt(a.k.a. newcons), jailed s/w will output to that virtual terminal, no matter which one it is (syscons or vt(4)) Can only find this https://wiki.freebsd.org/Newcons Has anybody gotten it to work in a jail? Thanks ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Just try what you want to try, and if it will behave bad, report it to us. And we will try to help you. Thanks! WBW -- Aleksandr Rybalko r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: need info about newcons in jails
Hi, On Sat, 03 May 2014 07:15:14 -0400 Fbsd8 fb...@a1poweruser.com wrote: Hello list. Looking for information about using newcons as the terminal driver in xorg for desktop in a jail. Can only find this https://wiki.freebsd.org/Newcons Has anybody gotten it to work in a jail? I just used my FreeBSD 10 machine to test this. It works as expected. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Leaving the Desktop Market
On Sunday, May 04, 2014 4:40:02 pm Adrian Chadd wrote: Hm, I was hoping for a little more discussion. Mostly around the which older CPUs do we leave this on for? crowd. I have Pentium-M class hardware that I was going to spin up -HEAD on. So I'll go install -HEAD on said older hardware and get a list of what does and doesn't work. I'm totally fine with disabling p4tcc and acpi_throttle if P states for cpu frequency adjustment are available. I just want to ensure that the temperature throttling stuff is going to get automatically engaged (by whichever magical BIOS/ACPI/SMI thing does it) and clock things down if the CPU gets way too hot. The only things that should use throttling are really old machines where ACPI asks the OS to do passive cooling by exposing the TC1 and TC2 constants. (I have an old P4 laptop where this is the case, I think Pentium-M is too new to need this.) If we keep TCC at all, it should not be tied into cpufreq but be a separate thing that only acpi_thermal.c uses. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: need info about newcons in jails
Aleksandr Rybalko wrote: On Sat, 03 May 2014 07:15:14 -0400 Fbsd8 fb...@a1poweruser.com wrote: Hello list. Hi, Looking for information about using newcons as the terminal driver in xorg for desktop in a jail. I don't really understand how that can be related. software running in jail doing output to same terminal in which jail started. So if you open xterm, and start jail from it, jailed s/w will output into xterm window. If you run jail from system virtual terminal syscons or vt(a.k.a. newcons), jailed s/w will output to that virtual terminal, no matter which one it is (syscons or vt(4)) Can only find this https://wiki.freebsd.org/Newcons Has anybody gotten it to work in a jail? Thanks It has been a long time known fact that a jail with xorg/what-ever-desktop does not work when trying to login to that jail from the host. Reason is xorg uses kernel to access syscons and the jail don't allow it that access just like its suppose to do. Now remotely ssh into that xorg jail works. So the question is when newcoms is on the host and the jail has xorg/what-ever-desktop installed can a host user login to that jail and have xorg/desktop work on the hosts screen? Host user means someone setting at the host computer console video device. Login means execute jexec jailname tcsh to open console to that jail. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
CURRENT: jemalloc_jemalloc.c:(.text+0xcb7): relocation truncated to fit: R_X86_64_PC32 against symbol `__je_ctl_boot'
It seems that I can not build anymore a kernel or world. I had an accident in a truncated /usr/libc while installing the last buildworld/kernel with mixed up sources. Is there a way to revert this mess? I think I installed lib/libc with more recent sources than the last installed system ( FreeBSD 11.0-CURRENT #7 r265358: Mon May 5 14:12:21 CEST 2014 amd64). Any help welcome. Regards, Oliver [...] c++ -O2 -pipe -O3 -pipe -O3 -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/include -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/tools/clang/include -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/utils/TableGen -I. -I/usr/src/usr.bin/clang/tblgen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd11.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd11.0\ -DDEFAULT_SYSROOT=\\ -I/usr/obj/usr/src/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -static -L/usr/obj/usr/src/tmp/legacy/usr/lib -o tblgen AsmMatcherEmitter.o AsmWriterEmitter.o AsmWriterInst.o CTagsEmitter.o CallingConvEmitter.o CodeEmitterGen.o CodeGenDAGPatterns.o CodeGenInstruction.o CodeGenMapTable.o CodeGenRegisters.o CodeGenSchedule.o CodeGenTarget.o DAGISelEmitter.o DAGISelMatcher.o DAGISelMatcherEmitter.o DAGISelMatcherGen.o DAGISelMatcherOpt.o DFAPacketizerEmitter.o DisassemblerEmitter.o FastISelEmitter.o FixedLenDecoderEmitter.o InstrInfoEmitter.o IntrinsicEmitter.o OptParserEmitter.o PseudoLoweringEmitter.o RegisterInfoEmitter.o SetTheory.o SubtargetEmitter.o TGValueTypes.o TableGen.o X86DisassemblerTables.o X86ModRMFilters.o X86RecognizableInstr.o /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmtablegen/libllvmtablegen.a /usr/obj/usr/src/tmp/usr/src/usr.bin/clang/tblgen/../../../lib/clang/libllvmsupport/libllvmsupport.a -lncurses -legacy /usr/lib/libc.a(jemalloc_jemalloc.o): In function `malloc': jemalloc_jemalloc.c:(.text+0xcb7): relocation truncated to fit: R_X86_64_PC32 against symbol `__je_ctl_boot' defined in .text section in /usr/lib/libc.a(jemalloc_ctl.o) c++: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 Stop. make[3]: stopped in /usr/src/usr.bin/clang/tblgen signature.asc Description: PGP signature
Should we make WITHOUT_LIB32=yes the default for 11-RELEASE?
On most amd64 systems I run, I usually set WITHOUT_LIB32=yes in /etc/src.conf because I don't need them. This weekend I did a stock install on an older AMD64 Core 2 Duo minipc and a buildworld of 10-STABLE took almost two hours with LIB32 and CLANG since much of it gets compiled twice. Is it time to deprecate LIB32 in -current for 11-RELEASE? I realize some ports may need it, but I hope that need is waning and we are just spending a lot of compile time by default for little gain. We could save a lot of compile time for a lot of users, and they could still opt-in if needed. Putting it up for discussion, not insisting it should be done. Thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Should we make WITHOUT_LIB32=yes the default for 11-RELEASE?
Hi, On Mon, 5 May 2014 22:07:06 -0400 Adam McDougall mcdou...@egr.msu.edu wrote: On most amd64 systems I run, I usually set WITHOUT_LIB32=yes in /etc/src.conf because I don't need them. This weekend I did a stock install on an older AMD64 Core 2 Duo minipc and a buildworld of 10-STABLE took almost two hours with LIB32 and CLANG since much of it gets compiled twice. Is it time to deprecate LIB32 in -current for 11-RELEASE? I realize this is a good idea. Just document it properly. So everybody can still use it. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
