[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 --- Comment #15 from Eugene Grosbein --- (In reply to Konstantin Belousov from comment #14) Thanks. I personally do not have such problem nor AMD hardware to reproduce that but hope Mike will benefit from this hint. -- You are receiving

[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 --- Comment #14 from Konstantin Belousov --- (In reply to Eugene Grosbein from comment #12) Compile everything with debugging symbols, i.e. rtld/libc/libthr, and the application (python interpreter). Than take the backtrace, and print out

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 --- Comment #7 from Conrad Meyer --- Notably, FULLWIDTH LEFT PARENTHESIS (\uFF08) is missing from every relevant copy of UTF-8.src I see. -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 --- Comment #13 from m...@sentex.net --- (In reply to Eugene Grosbein from comment #11) Re: timing issues, I did try it on a number of different Intel CPUs ( eg Xeon(R) CPU E5-1650) of various core densities and speeds and was not able to re

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 Conrad Meyer changed: What|Removed |Added CC||b...@freebsd.org --- Comment #6 fro

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 --- Comment #5 from Conrad Meyer --- RuneLocale data comes from _Read_RuneMagi() on a path derived from the encoding and LC_CTYPE, e.g., /usr/share/locale/en_US.UTF-8/LC_CTYPE . Where does this data come from? -- You are receiving this m

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 --- Comment #4 from Conrad Meyer --- Oh, I see, I didn't properly setlocale(). With: setlocale(LC_ALL, getenv("LANG")); and an appropriate LANG environment variable value set (e.g., en_US.UTF-8), I do see characters beyond 0x80. The tab

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 --- Comment #3 from Conrad Meyer --- I find that in the default C locale, output stops after 126 ('~'). Curiously, also with LANG or LC_CTYPE set. H. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 --- Comment #2 from Conrad Meyer --- By the way, it might be interesting to play with nextwctype(3) to enumerate the current table. wint_t wc = 0; wctype_t wct = wctype("print"); while (wc < 0x10 && wc >= 0) { wc = nextwctype(wc, wc

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 --- Comment #1 from Conrad Meyer --- iswprint(wc) is a thin shim around __istype(wc, _CTYPE_R); __istype(wc, type) is a thin shim in include/_ctype.h: return (!!__maskrune(wc, _CTYPE_R)); __maskrune() is defined earlier in the same file

[Bug 225658] /etc/regdomain.xml has "Russia" misspellt as "Rusia"

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225658 Ed Maste changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|ema...@freebsd.org Status|N

[Bug 225658] /etc/regdomain.xml has "Russia" misspellt as "Rusia"

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225658 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Mon Feb 5 18:45:21 UTC 2018 New revision: 328895 URL: https://svnweb.freebsd.org/changeset/base/328895 Log: Correct Russia spelling in re

[Bug 225639] FreeBSD's tar produces .tgz files that can not be read by other tar implementations (e.g windows 7-zip)

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225639 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #2 from

[Bug 225692] iswprint() wrong for some FULL WIDTH characters in UTF-8 locale

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692 Bug ID: 225692 Summary: iswprint() wrong for some FULL WIDTH characters in UTF-8 locale Product: Base System Version: 11.1-RELEASE Hardware: Any OS: A

[Bug 225689] [igb] I350 VF doesn't work with vlans

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225689 Andrey V. Elsukov changed: What|Removed |Added Keywords||IntelNetworking

[Bug 225689] [igb] I350 VF doesn't work with vlans

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225689 Bug ID: 225689 Summary: [igb] I350 VF doesn't work with vlans Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affe

[Bug 225688] ppc64: Unable to read timebase

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225688 --- Comment #2 from Breno Leitao --- I also created a diff at phabricator. Since this is my first time using this system, it might not be in the appropriate format: https://reviews.freebsd.org/D14204 -- You are receiving this mail becaus

[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 Eugene Grosbein changed: What|Removed |Added CC||k...@freebsd.org --- Comment #12

[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 --- Comment #11 from Eugene Grosbein --- (In reply to mike from comment #9) These threads locked in "umtxn" state remind me of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 that revealed long-standing bugs in our libc being not

[Bug 225688] ppc64: Unable to read timebase

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225688 --- Comment #1 from Breno Leitao --- Please find the patch that fix this issue attached. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org ma

[Bug 225688] ppc64: Unable to read timebase

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225688 Bug ID: 225688 Summary: ppc64: Unable to read timebase Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Onl

[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 --- Comment #10 from Ed Maste --- (In reply to mike from comment #9) > Hi, apart from > KDB_UNATTENDED > these options are all part of a standard GENERIC kernel on HEAD, no ? They are, yes. I suspect we're going to add debugging (e.g. KTR

[Bug 225584] Various compile process hang on Ryzen, but not on Intel

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584 --- Comment #9 from m...@sentex.net --- (In reply to Eugene Grosbein from comment #7) Hi, apart from KDB_UNATTENDED these options are all part of a standard GENERIC kernel on HEAD, no ? I added that as well as BREAK_TO_DEBUGGER. The kernel

[Bug 225182] devel/powerpc64-xtoolchain-gcc: SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225182 --- Comment #11 from Breno Leitao --- (In reply to Kenneth Salerno from comment #10) Hi Kenneth, I think this now is fixed, since this problem seems to be the same as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225323, which is fixed

[Bug 225586] ftruncate+mmap+fsync fails for small maps

2018-02-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225586 --- Comment #7 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Mon Feb 5 10:29:58 UTC 2018 New revision: 328879 URL: https://svnweb.freebsd.org/changeset/base/328879 Log: MFC r328773: On pageout, in vn