Re: Leaving the Desktop Market

2014-05-13 Thread Adrian Chadd
Did you set cx_lowest on hw.acpi.cpu ?


-a


On 12 May 2014 20:07, Allan Jude free...@allanjude.com wrote:
 Before and after cx_lowest=c8 on an E5-2620v2

 before:

 # pcm.x 1

  Intel(r) Performance Counter Monitor V2.6 (2013-11-04 13:43:31 +0100
 ID=db05e43)

  Copyright (c) 2009-2013 Intel Corporation

 Number of physical cores: 12
 Number of logical cores: 24
 Threads (logical cores) per physical core: 2
 Num sockets: 2
 Core PMU (perfmon) version: 3
 Number of core PMU generic (programmable) counters: 4
 Width of generic (programmable) counters: 48 bits
 Number of core PMU fixed counters: 3
 Width of fixed counters: 48 bits
 Nominal core frequency: 21 Hz
 Package thermal spec power: 80 Watt; Package minimum power: 51 Watt;
 Package maximum power: 110 Watt;
 ERROR: QPI LL monitoring device (0:127:8:2) is missing. The QPI
 statistics will be incomplete or missing.
 ERROR: QPI LL monitoring device (0:127:9:2) is missing. The QPI
 statistics will be incomplete or missing.
 Socket 0: 1 memory controllers detected with total number of 4 channels.
 0 QPI ports detected.
 ERROR: QPI LL monitoring device (0:255:8:2) is missing. The QPI
 statistics will be incomplete or missing.
 ERROR: QPI LL monitoring device (0:255:9:2) is missing. The QPI
 statistics will be incomplete or missing.
 Socket 1: 1 memory controllers detected with total number of 4 channels.
 0 QPI ports detected.
 Max QPI link speed: 14.4 GBytes/second (7.2 GT/second)

 Detected Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz Intel(r)
 microarchitecture codename Ivy Bridge-EP/EN/EX/Ivytown

  EXEC  : instructions per nominal CPU cycle
  IPC   : instructions per CPU cycle
  FREQ  : relation to nominal CPU frequency='unhalted clock
 ticks'/'invariant timer ticks' (includes Intel Turbo Boost)
  AFREQ : relation to nominal CPU frequency while in active state (not in
 power-saving C state)='unhalted clock ticks'/'invariant timer ticks
 while in C0-state'  (includes Intel Turbo Boost)
  L3MISS: L3 cache misses
  L2MISS: L2 cache misses (including other core's L2 cache *hits*)
  L3HIT : L3 cache hit ratio (0.00-1.00)
  L2HIT : L2 cache hit ratio (0.00-1.00)
  L3CLK : ratio of CPU cycles lost due to L3 cache misses (0.00-1.00), in
 some cases could be 1.0 due to a higher memory latency
  L2CLK : ratio of CPU cycles lost due to missing L2 cache but still
 hitting L3 cache (0.00-1.00)
  READ  : bytes read from memory controller (in GBytes)
  WRITE : bytes written to memory controller (in GBytes)
  TEMP  : Temperature reading in 1 degree Celsius relative to the TjMax
 temperature (thermal headroom): 0 corresponds to the max temperature


  Core (SKT) | EXEC | IPC  | FREQ  | AFREQ | L3MISS | L2MISS | L3HIT |
 L2HIT | L3CLK | L2CLK  | READ  | WRITE | TEMP

00 0.06   1.02   0.060.992451 K   3421 K0.28
 0.850.360.03 N/A N/A 56
10 0.03   1.07   0.030.99 649 K   1331 K0.51
 0.930.180.04 N/A N/A 56
20 0.06   1.27   0.050.991020 K   1738 K0.41
 0.920.190.03 N/A N/A 47
30 0.05   1.20   0.040.981057 K   2256 K0.53
 0.870.200.05 N/A N/A 47
40 0.06   1.28   0.050.991115 K   1942 K0.43
 0.910.200.03 N/A N/A 56
50 0.08   1.31   0.060.991046 K   1932 K0.46
 0.940.150.03 N/A N/A 56
60 0.06   1.27   0.050.991167 K   1866 K0.37
 0.920.200.02 N/A N/A 53
70 0.12   1.45   0.090.991256 K   2263 K0.45
 0.950.120.02 N/A N/A 53
80 0.05   1.05   0.050.982372 K   3072 K0.23
 0.870.400.02 N/A N/A 53
90 0.03   1.19   0.030.94 968 K   1521 K0.36
 0.480.290.04 N/A N/A 53
   100 0.09   1.27   0.070.991773 K   3184 K0.44
 0.890.210.03 N/A N/A 52
   110 0.14   1.33   0.100.991745 K   2808 K0.38
 0.960.140.02 N/A N/A 52
   121 0.04   1.21   0.030.981116 K   1867 K0.40
 0.690.280.04 N/A N/A 49
   131 0.09   1.24   0.070.992248 K   3901 K0.42
 0.810.270.04 N/A N/A 49
   141 0.10   1.35   0.070.981668 K   2603 K0.36
 0.920.200.02 N/A N/A 49
   151 0.05   1.26   0.040.991435 K   2286 K0.37
 0.680.330.04 N/A N/A 49
   161 0.11   1.29   0.080.991887 K   3232 K0.42
 0.920.190.03 N/A N/A 44
   171 0.06   1.28   0.050.99 966 K   1626 K0.41
 0.930.180.02 N/A N/A 44
   181 0.07   1.30   0.050.991040 K   1870 K0.44
 0.920.180.03 N/A N/A 47
   191 0.12   1.30   0.090.991973 K   3133 K0.37
 0.93 

ports/INDEX building broken on 11.0-CURRENT

2014-05-13 Thread Don Lewis
Please excuse the crosspost.  I'm not sure if this is a ports problem or
a CURRENT problem.

I just updated my 11.0-CURRENT machine to r265940 and can no longer
build ports/INDEX-11.  My ports tree is r353903.  I think this problem
is being caused by the recent changes to /usr/share/mk/*.

# make index
Generating INDEX-11 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmarks ---
--- describe.biology ---
--- describe.cad ---
--- describe.chinese ---
--- describe.comms ---
--- describe.converters ---
--- describe.databases ---
--- describe.deskutils ---
--- describe.devel ---
clang33: not found
make[5]: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 --version 
returned non-zero status
make[5]: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine compiler 
type for clang33.  Consider setting COMPILER_TYPE.
=== devel/ccons failed
*** [describe.devel] Error code 1

make[2]: stopped in /usr/ports
1 error

make[2]: stopped in /usr/ports


Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection.  (INDEX builds are
not supported with partial or out-of-date ports collections.
If that is the case, then
report the failure to po...@freebsd.org together with relevant
details of your ports configuration (including FreeBSD version,
your architecture, your environment, and your /etc/make.conf
settings, especially compiler flags and OPTIONS_SET/UNSET settings).

Note: the latest pre-generated version of INDEX may be fetched
automatically with make fetchindex.


*** Error code 1

Stop.
make[1]: stopped in /usr/ports
*** Error code 1

Stop.
make: stopped in /usr/ports


If I go to the offending port:

# cd /usr/ports/devel/ccons/
# make describe
clang33: not found
make: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 --version 
returned non-zero status
make: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine compiler 
type for clang33.  Consider setting COMPILER_TYPE.


I don't have any problems building the INDEX file on 9.3-PRERELEASE
r265940.


___
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


r 265947: relocation truncated to fit: R_X86_64_PC32 against symbol `__error' defined in .text

2014-05-13 Thread O. Hartmann
On FreeBSD 11.0-CURRENT,

FreeBSD 11.0-CURRENT #1 r265924: Mon May 12 20:38:01 CEST 2014 amd64

The system is working so far, but when trying to compile the ost recent sources
(buildworld), I get the following error:

cc -O2 -pipe -O3  -I/usr/src/usr.bin/xinstall/../../contrib/mtree
-I/usr/src/usr.bin/xinstall/../../lib/libnetbsd
-I/usr/src/usr.bin/xinstall/../../lib/libmd -std=gnu99  -Qunused-arguments
-I/usr/obj/usr/src/tmp/legacy/usr/include  -static 
-L/usr/obj/usr/src/tmp/legacy/usr/lib
-o xinstall xinstall.o getid.o -lmd -legacy /usr/lib/libc.a(posix_spawn.o): In 
function
`posix_spawn_file_actions_addopen': 
/usr/src/lib/libc/gen/posix_spawn.c:(.text+0x438):
relocation truncated to fit: R_X86_64_PC32 against symbol `__error' defined in 
.text
section in /usr/lib/libc.a(__error.o) cc: error: linker command failed with 
exit code 1
(use -v to see invocation) *** [xinstall] Error code 1

Just for fun, I also tried to recompile (not install!) libc via

make -C lib/libc depend obj all

make: /usr/src/lib/libc/Makefile line 6: Could not find src.opts.mk
make: /usr/src/lib/libc/Makefile line 32: Malformed conditional (${MK_NLS} != 
no)
make: /usr/src/lib/libc/Makefile line 51: Malformed conditional (${MK_SSP} != 
no)
make: /usr/src/lib/libc/Makefile line 72: Malformed conditional (${MK_ICONV} 
!= no)
make: /usr/src/lib/libc/locale/Makefile.inc line 26: Malformed conditional
(${MK_ICONV} != no) make: /usr/src/lib/libc/net/Makefile.inc line 19: 
Malformed
conditional (${MK_NS_CACHING} != no) make: 
/usr/src/lib/libc/net/Makefile.inc line
25: Malformed conditional (${MK_INET6_SUPPORT} != no) make:
/usr/src/lib/libc/net/Makefile.inc line 125: Malformed conditional 
(${MK_HESIOD} !=
no) make: /usr/src/lib/libc/amd64/sys/Makefile.inc line 14: Malformed 
conditional
(${MK_SYSCALL_COMPAT} != no) make: /usr/src/lib/libc/sys/Makefile.inc line 
24:
Malformed conditional (${MK_SYSCALL_COMPAT} != no) make: 
/usr/src/lib/libc/Makefile
line 105: Malformed conditional (${MK_NIS} != no) make: 
/usr/src/lib/libc/Makefile
line 110: Malformed conditional (${MK_HESIOD} != no) make: 
/usr/src/lib/libc/Makefile
line 113: Malformed conditional (${MK_FP_LIBC} == no) make:
/usr/src/lib/libc/Makefile line 116: Malformed conditional (${MK_NS_CACHING} 
!= no)
make: Fatal errors encountered -- cannot continue make: stopped in 
/usr/src/lib/libc



Well, there is something wrong on this and I have no clue what is going on. I 
recompiled
yesterday's world without problems (r265924).

oh




signature.asc
Description: PGP signature


Re: RFT vidcontrol for vt(4)

2014-05-13 Thread Aleksandr Rybalko
On Mon, 12 May 2014 19:51:21 -0400
George Mitchell george+free...@m5p.com wrote:

 On 05/12/14 11:25, Nathan Whitehorn wrote:
  [...]
 
  Is there any reason not to have kbdmux be mandatory at this point?
  [...]
 
 Does this mean mandatory in the sense that the kbdmux driver always
 gets built and loaded, or that the kbdmux driver must always be in
 operation (treating all keyboard-like devices as a single unified
 source of keystrokes)?  I could live with the first, but there are
 definitely times that I want multiple independent keyboards on a
 system to be considered unrelated to one another. -- George

kbdmux able to manage keyboard set, so you can attach and detach some
keyboards.
(But I did not test it long ago for vt(4))

 
 ___
 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

Thanks!

WBW
-- 
Aleksandr Rybalko r...@freebsd.org
___
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


fsck bug in replaying partial frag truncate journal on UFS SU+J?

2014-05-13 Thread takehara . mikihito
Hello,

I think fsck_ffs has a bug in replaying partial frag truncate journal on UFS 
SU+J.
Bellow I tested about the issue.

I tested blocksize==4KB, fragsize=512byte UFS SU+J. But I think these 
parameters are not related to 
this issue.
1) Preparing 4096byte(1block) test file.
2) Use truncate to shorten filesize to 3584byte(7frags).
3) Shutdown without unmount after journal is written and before inode size 
ufs2_dinode is written.
4) Run fsck_ffs with journal.
5) Mount again and remove test file. Then I face panic.
   panic: ffs_blkfree_cg: freeing free block

This seems to be caused by fsck_ffs to replay JOP_FREEBLK whose blkno is not 
block-aligned.
The above case 2), JOP_FREEBLK journal is like this:
   FREEBLK ino=5, blkno=1727, lbn=0, frags=1, oldfrags=0  ---(a)
fsck_ffs handles JOP_NEWBLK almost same as JOP_FREEBLK. But my understanding is 
that in case of 
JOP_NEWBLK kernel always create block-aligned blkno. So this issue is only in 
case of JOP_FREEBLK.

To analyze this issue, I also tested that using the above test file 
3584byte(7frags) and write 
512byte with append to largen to 4096byte(1block). In this case JOP_NEWBLK 
journal is like this:
   JOP_NEWBLK ino=5, blkno=1720, lbn=0, frags=8, oldfrags=7  ---(b)

I think the bug is in fsck_ffs suj.c's arround blk_check(). My understanding is 
that blk_check() 
cannot handle non-block-aligned blkno so there is a little trick in blk_build() 
bellow.

/*  

 * Rewrite the record using oldfrags to indicate the offset into

 * the block.  Leave jb_frags as the actual allocated count.

 */
blkrec-jb_blkno -= frag;
blkrec-jb_oldfrags = frag; 


By this trick, (a) is modified like:
   JOP_FREEBLK ino=5, blkno=1720, lbn=0, frags=1, oldfrags=7  ---(a')
and (b) is modified like:
   JOP_NEWBLK ino=5, blkno=1720, lbn=0, frags=8, oldfrags=0  ---(b')
But blk_check() cannot handle the case oldfrags!=0. If oldfrags!=0, 
blk_check()'s isat comes 
to be 0 even though the blk is present. So (a) should be modified same as (b')
The following is my patch to fix like this. According to my test, this patch 
works fine.
===
diff --git a/sbin/fsck_ffs/suj.c b/sbin/fsck_ffs/suj.c
index e21ffc6..2512522 100644
--- a/sbin/fsck_ffs/suj.c
+++ b/sbin/fsck_ffs/suj.c
@@ -2503,11 +2503,11 @@ blk_build(struct jblkrec *blkrec)
frag = fragnum(fs, blkrec-jb_blkno);
sblk = blk_lookup(blk, 1);
/*
-* Rewrite the record using oldfrags to indicate the offset into
-* the block.  Leave jb_frags as the actual allocated count.
+* Rewrite the record to indicate the offset into the block.
 */
blkrec-jb_blkno -= frag;
-   blkrec-jb_oldfrags = frag;
+   blkrec-jb_frags += frag;
+   blkrec-jb_oldfrags = 0;
if (blkrec-jb_oldfrags + blkrec-jb_frags  fs-fs_frag)
err_suj(Invalid fragment count %d oldfrags %d\n,
blkrec-jb_frags, frag);
===

I think we can fix this by changing kernel code not to create non-block-aligned 
JOP_FREEBLK.
But I also think it is better to change fsck by considering compatibility.


___
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: r 265947: relocation truncated to fit: R_X86_64_PC32 against symbol `__error' defined in .text

2014-05-13 Thread Ian Lepore
On Tue, 2014-05-13 at 11:28 +0200, O. Hartmann wrote:
 On FreeBSD 11.0-CURRENT,
 
 FreeBSD 11.0-CURRENT #1 r265924: Mon May 12 20:38:01 CEST 2014 amd64
 
 The system is working so far, but when trying to compile the ost recent 
 sources
 (buildworld), I get the following error:
 
 cc -O2 -pipe -O3  -I/usr/src/usr.bin/xinstall/../../contrib/mtree
 -I/usr/src/usr.bin/xinstall/../../lib/libnetbsd
 -I/usr/src/usr.bin/xinstall/../../lib/libmd -std=gnu99  -Qunused-arguments
 -I/usr/obj/usr/src/tmp/legacy/usr/include  -static 
 -L/usr/obj/usr/src/tmp/legacy/usr/lib
 -o xinstall xinstall.o getid.o -lmd -legacy /usr/lib/libc.a(posix_spawn.o): 
 In function
 `posix_spawn_file_actions_addopen': 
 /usr/src/lib/libc/gen/posix_spawn.c:(.text+0x438):
 relocation truncated to fit: R_X86_64_PC32 against symbol `__error' defined 
 in .text
 section in /usr/lib/libc.a(__error.o) cc: error: linker command failed with 
 exit code 1
 (use -v to see invocation) *** [xinstall] Error code 1
 
 Just for fun, I also tried to recompile (not install!) libc via
 
 make -C lib/libc depend obj all
 
 make: /usr/src/lib/libc/Makefile line 6: Could not find src.opts.mk
 make: /usr/src/lib/libc/Makefile line 32: Malformed conditional (${MK_NLS} 
 != no)
 make: /usr/src/lib/libc/Makefile line 51: Malformed conditional (${MK_SSP} 
 != no)
 make: /usr/src/lib/libc/Makefile line 72: Malformed conditional 
 (${MK_ICONV} != no)
 make: /usr/src/lib/libc/locale/Makefile.inc line 26: Malformed conditional
 (${MK_ICONV} != no) make: /usr/src/lib/libc/net/Makefile.inc line 19: 
 Malformed
 conditional (${MK_NS_CACHING} != no) make: 
 /usr/src/lib/libc/net/Makefile.inc line
 25: Malformed conditional (${MK_INET6_SUPPORT} != no) make:
 /usr/src/lib/libc/net/Makefile.inc line 125: Malformed conditional 
 (${MK_HESIOD} !=
 no) make: /usr/src/lib/libc/amd64/sys/Makefile.inc line 14: Malformed 
 conditional
 (${MK_SYSCALL_COMPAT} != no) make: /usr/src/lib/libc/sys/Makefile.inc 
 line 24:
 Malformed conditional (${MK_SYSCALL_COMPAT} != no) make: 
 /usr/src/lib/libc/Makefile
 line 105: Malformed conditional (${MK_NIS} != no) make: 
 /usr/src/lib/libc/Makefile
 line 110: Malformed conditional (${MK_HESIOD} != no) make: 
 /usr/src/lib/libc/Makefile
 line 113: Malformed conditional (${MK_FP_LIBC} == no) make:
 /usr/src/lib/libc/Makefile line 116: Malformed conditional 
 (${MK_NS_CACHING} != no)
 make: Fatal errors encountered -- cannot continue make: stopped in 
 /usr/src/lib/libc
 
 
 
 Well, there is something wrong on this and I have no clue what is going on. I 
 recompiled
 yesterday's world without problems (r265924).
 
 oh
 
 

The 20140505 entry in UPDATING covers this, I think.  You need to set
MAKESYSPATH to point to the right share/mk directory (the one associated
with the source you're building) when you build individual directories
within the tree.

-- Ian


___
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

2014-05-13 Thread Allan Jude
On 2014-05-13 02:06, Adrian Chadd wrote:
 Did you set cx_lowest on hw.acpi.cpu ?


 -a


 On 12 May 2014 20:07, Allan Jude free...@allanjude.com wrote:
 Before and after cx_lowest=c8 on an E5-2620v2

 before:

 # pcm.x 1

 Intel(r) Performance Counter Monitor V2.6 (2013-11-04 13:43:31
 +0100 ID=db05e43)

 Copyright (c) 2009-2013 Intel Corporation

 Number of physical cores: 12 Number of logical cores: 24 Threads
 (logical cores) per physical core: 2 Num sockets: 2 Core PMU
 (perfmon) version: 3 Number of core PMU generic (programmable)
 counters: 4 Width of generic (programmable) counters: 48 bits
 Number of core PMU fixed counters: 3 Width of fixed counters: 48
 bits Nominal core frequency: 21 Hz Package thermal spec
 power: 80 Watt; Package minimum power: 51 Watt; Package maximum
 power: 110 Watt; ERROR: QPI LL monitoring device (0:127:8:2) is
 missing. The QPI statistics will be incomplete or missing. ERROR:
 QPI LL monitoring device (0:127:9:2) is missing. The QPI statistics
 will be incomplete or missing. Socket 0: 1 memory controllers
 detected with total number of 4 channels. 0 QPI ports detected.
 ERROR: QPI LL monitoring device (0:255:8:2) is missing. The QPI
 statistics will be incomplete or missing. ERROR: QPI LL monitoring
 device (0:255:9:2) is missing. The QPI statistics will be
 incomplete or missing. Socket 1: 1 memory controllers detected with
 total number of 4 channels. 0 QPI ports detected. Max QPI link
 speed: 14.4 GBytes/second (7.2 GT/second)

 Detected Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz Intel(r)
 microarchitecture codename Ivy Bridge-EP/EN/EX/Ivytown

 EXEC  : instructions per nominal CPU cycle IPC   : instructions per
 CPU cycle FREQ  : relation to nominal CPU frequency='unhalted
 clock ticks'/'invariant timer ticks' (includes Intel Turbo Boost)
 AFREQ : relation to nominal CPU frequency while in active state
 (not in power-saving C state)='unhalted clock ticks'/'invariant
 timer ticks while in C0-state'  (includes Intel Turbo Boost)
 L3MISS: L3 cache misses L2MISS: L2 cache misses (including other
 core's L2 cache *hits*) L3HIT : L3 cache hit ratio (0.00-1.00)
 L2HIT : L2 cache hit ratio (0.00-1.00) L3CLK : ratio of CPU cycles
 lost due to L3 cache misses (0.00-1.00), in some cases could be
 1.0 due to a higher memory latency L2CLK : ratio of CPU cycles
 lost due to missing L2 cache but still hitting L3 cache
 (0.00-1.00) READ  : bytes read from memory controller (in GBytes)
 WRITE : bytes written to memory controller (in GBytes) TEMP  :
 Temperature reading in 1 degree Celsius relative to the TjMax
 temperature (thermal headroom): 0 corresponds to the max
 temperature


 Core (SKT) | EXEC | IPC  | FREQ  | AFREQ | L3MISS | L2MISS | L3HIT
 | L2HIT | L3CLK | L2CLK  | READ  | WRITE | TEMP

 00 0.06   1.02   0.060.992451 K   3421 K0.28
 0.850.360.03 N/A N/A 56 10 0.03   1.07
 0.030.99 649 K   1331 K0.51 0.930.180.04
 N/A N/A 56 20 0.06   1.27   0.050.991020 K
 1738 K0.41 0.920.190.03 N/A N/A 47 30
 0.05   1.20   0.040.981057 K   2256 K0.53 0.870.20
 0.05 N/A N/A 47 40 0.06   1.28   0.050.99
 1115 K   1942 K0.43 0.910.200.03 N/A N/A
 56 50 0.08   1.31   0.060.991046 K   1932 K
 0.46 0.940.150.03 N/A N/A 56 60 0.06
 1.27   0.050.991167 K   1866 K0.37 0.920.200.02
 N/A N/A 53 70 0.12   1.45   0.090.991256 K
 2263 K0.45 0.950.120.02 N/A N/A 53 80
 0.05   1.05   0.050.982372 K   3072 K0.23 0.870.40
 0.02 N/A N/A 53 90 0.03   1.19   0.030.94
 968 K   1521 K0.36 0.480.290.04 N/A N/A 53
 100 0.09   1.27   0.070.991773 K   3184 K0.44
 0.890.210.03 N/A N/A 52 110 0.14   1.33
 0.100.991745 K   2808 K0.38 0.960.140.02
 N/A N/A 52 121 0.04   1.21   0.030.981116 K
 1867 K0.40 0.690.280.04 N/A N/A 49 131
 0.09   1.24   0.070.992248 K   3901 K0.42 0.810.27
 0.04 N/A N/A 49 141 0.10   1.35   0.070.98
 1668 K   2603 K0.36 0.920.200.02 N/A N/A
 49 151 0.05   1.26   0.040.991435 K   2286 K
 0.37 0.680.330.04 N/A N/A 49 161 0.11
 1.29   0.080.991887 K   3232 K0.42 0.920.190.03
 N/A N/A 44 171 0.06   1.28   0.050.99 966 K
 1626 K0.41 0.930.180.02 N/A N/A 44 181
 0.07   1.30   0.050.991040 K   1870 K0.44 0.920.18
 0.03 N/A N/A 47 191 0.12   1.30   0.090.99
 1973 K   3133 K0.37 0.930.180.02 N/A N/A
 47 201 0.05   1.33   0.040.99 898 K   1531 K
 0.41 0.910.190.03 

Locking console with Ctrl-S hangs various processes (ttydcd)

2014-05-13 Thread Mikhail T.
Hello!

A fellow FreeBSD user was recently confounded by a problem: various processes on
his 10.0 system were hanging or otherwise misbehaving: su, certain daemons, 
syslogd.

They were all hung in the ttydcd-state. Searching
https://www.google.com/search?q=FreeBSD+ttydcd for that revealed only, that
other people have seen the problem, but nobody (including the entire
freebsd-stable@ on 2012
http://lists.freebsd.org/pipermail/freebsd-stable/2012-June/068281.html) was
able to offer a solution.

Apparently, the problem stems from the ttyv0 (which moonlights as /dev/console
for the vast majority of installs) being locked -- such as by pressing Ctrl-S.
One needs not be a root to do it...

After that, any attempts to write to /dev/console -- which even syslog(3) often
does -- would hang the calling process until the tty is unlocked (such as with
Ctrl-Q).

This may be the desired behavior for normal ttys, but, perhaps, /dev/console
should act differently?

-mi

___
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: ports/INDEX building broken on 11.0-CURRENT

2014-05-13 Thread Don Lewis
On 13 May, To: po...@freebsd.org wrote:
 Please excuse the crosspost.  I'm not sure if this is a ports problem or
 a CURRENT problem.
 
 I just updated my 11.0-CURRENT machine to r265940 and can no longer
 build ports/INDEX-11.  My ports tree is r353903.  I think this problem
 is being caused by the recent changes to /usr/share/mk/*.
 
 # make index
 Generating INDEX-11 - please wait..--- describe.accessibility ---
 --- describe.arabic ---
 --- describe.archivers ---
 --- describe.astro ---
 --- describe.audio ---
 --- describe.benchmarks ---
 --- describe.biology ---
 --- describe.cad ---
 --- describe.chinese ---
 --- describe.comms ---
 --- describe.converters ---
 --- describe.databases ---
 --- describe.deskutils ---
 --- describe.devel ---
 clang33: not found
 make[5]: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 
 --version returned non-zero status
 make[5]: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine 
 compiler type for clang33.  Consider setting COMPILER_TYPE.
 === devel/ccons failed
 *** [describe.devel] Error code 1
 
 make[2]: stopped in /usr/ports
 1 error
 
 make[2]: stopped in /usr/ports
 
 
 Before reporting this error, verify that you are running a supported
 version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
 have a complete and up-to-date ports collection.  (INDEX builds are
 not supported with partial or out-of-date ports collections.
 If that is the case, then
 report the failure to po...@freebsd.org together with relevant
 details of your ports configuration (including FreeBSD version,
 your architecture, your environment, and your /etc/make.conf
 settings, especially compiler flags and OPTIONS_SET/UNSET settings).
 
 Note: the latest pre-generated version of INDEX may be fetched
 automatically with make fetchindex.
 
 
 *** Error code 1
 
 Stop.
 make[1]: stopped in /usr/ports
 *** Error code 1
 
 Stop.
 make: stopped in /usr/ports
 
 
 If I go to the offending port:
 
 # cd /usr/ports/devel/ccons/
 # make describe
 clang33: not found
 make: /usr/share/mk/bsd.compiler.mk line 24: warning: clang33 --version 
 returned non-zero status
 make: /usr/share/mk/bsd.compiler.mk line 37: Unable to determine compiler 
 type for clang33.  Consider setting COMPILER_TYPE.
 
 
 I don't have any problems building the INDEX file on 9.3-PRERELEASE
 r265940.

Various ports were setting CC to the following, which was causing the
bsd.compiler.mk to barf:
clang32
clang33
/usr/bin/gcc
mingw32-gcc
gcc

The patch below allowed me to successfully run make index and reduced
the error spewage.  It also greatly reduces the need to run
${CC} --version
in order to set COMPILER_TYPE.

It still seems like a great waste to run
${CC} --version
for each port to set COMPILER_VERSION since only a handful of ports need
this information.

Then there is this sort of circular dependency in some ports, like this
one in textproc/ibus/Makefile:

.if ${COMPILER_TYPE} == gcc  ${COMPILER_VERSION}  46
USE_GCC=yes
.endif

This will cause CC to be redefined, but COMPILER_TYPE and
COMPILER_VERSION will still retain their old values.



Index: share/mk/bsd.compiler.mk
===
--- share/mk/bsd.compiler.mk(revision 265940)
+++ share/mk/bsd.compiler.mk(working copy)
@@ -21,23 +21,28 @@
 .if !target(__bsd.compiler.mk__)
 __bsd.compiler.mk__:
 
-_v!=   ${CC} --version
 .if !defined(COMPILER_TYPE)
-. if ${CC:T:Mgcc*}
+. if ${CC:T:M*gcc*}
 COMPILER_TYPE:=gcc  
-. elif ${CC:T:Mclang}
+. elif ${CC:T:Mclang*}
 COMPILER_TYPE:=clang
-. elif ${_v:Mgcc}
+. else
+_v!=   ${CC} --version
+.  if ${_v:Mgcc}
 COMPILER_TYPE:=gcc
-. elif ${_v:M\(GCC\)}
+.  elif ${_v:M\(GCC\)}
 COMPILER_TYPE:=gcc
-. elif ${_v:Mclang}
+.  elif ${_v:Mclang}
 COMPILER_TYPE:=clang
-. else
+.  else
 .error Unable to determine compiler type for ${CC}.  Consider setting 
COMPILER_TYPE.
+.  endif
 . endif
 .endif
 .if !defined(COMPILER_VERSION)
+. if !defined(_v)
+_v!=   ${CC} --version || echo 'unknown'
+. endif
 COMPILER_VERSION!=echo ${_v:M[1-9].[0-9]*} | awk -F. '{print $$1 * 1 + $$2 
* 100 + $$3;}'
 .endif
 .undef _v


___
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: Locking console with Ctrl-S hangs various processes (ttydcd)

2014-05-13 Thread Adrian Chadd
Hi!

This sounds rather silly and should be fixed. Yes, hanging the vty
shouldn't hang the console device.

Would you / your friend mind filing a PR?

Thanks!


-a


On 13 May 2014 15:42, Mikhail T. mi+t...@aldan.algebra.com wrote:
 Hello!

 A fellow FreeBSD user was recently confounded by a problem: various processes 
 on
 his 10.0 system were hanging or otherwise misbehaving: su, certain daemons, 
 syslogd.

 They were all hung in the ttydcd-state. Searching
 https://www.google.com/search?q=FreeBSD+ttydcd for that revealed only, that
 other people have seen the problem, but nobody (including the entire
 freebsd-stable@ on 2012
 http://lists.freebsd.org/pipermail/freebsd-stable/2012-June/068281.html) was
 able to offer a solution.

 Apparently, the problem stems from the ttyv0 (which moonlights as /dev/console
 for the vast majority of installs) being locked -- such as by pressing Ctrl-S.
 One needs not be a root to do it...

 After that, any attempts to write to /dev/console -- which even syslog(3) 
 often
 does -- would hang the calling process until the tty is unlocked (such as with
 Ctrl-Q).

 This may be the desired behavior for normal ttys, but, perhaps, /dev/console
 should act differently?

 -mi

 ___
 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
___
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