[Bug 218517] ppp fails adding route with error Value too large to be stored in data type

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218517

Eugene Grosbein  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 218517] ppp fails adding route with error Value too large to be stored in data type

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218517

Eugene Grosbein  changed:

   What|Removed |Added

 Status|Closed  |Open
 Resolution|Unable to Reproduce |---
   Assignee|eu...@freebsd.org   |freebsd-bugs@FreeBSD.org

--- Comment #11 from Eugene Grosbein  ---
Reopen as problem reproduced.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225755] Panic after make core

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225755

Bug ID: 225755
   Summary: Panic after make core
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: laa8...@gmail.com

Created attachment 190423
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190423&action=edit
Screen

Hello.

I have problem with boot system after make kernel (kernel panic).

How to.

cd /usr/src/sys/amd64/conf
cp GENERIC www1

Append www1:
device  pf
device  pflog

options ALTQ
options ALTQ_CBQ# Class Bases Queueing
options ALTQ_RED# Random Early Detection
options ALTQ_RIO# RED In/Out
options ALTQ_HFSC   # Hierarchical Packet Scheduler
options ALTQ_CDNR   # Traffic conditioner
options ALTQ_PRIQ   # Priority Queueing
options ALTQ_NOPCC  # Required for SMP build

SAVE

cd /usr/src/

make buildkernel KERNCONF=www1
make installkernel KERNCONF=www1

After reboot I have picture (in attach). Core not dumped.

Sorry for my english.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #51 from Konstantin Belousov  ---
(In reply to mike from comment #50)
It is not the abort line that was printed for the core analyzed.  I expect that
the first address printed is 0x80146cd10.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #52 from Konstantin Belousov  ---
Created attachment 190428
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190428&action=edit
Disable RDFSBASE on zens.

This is a pure guess based on the _impression_ I get from looking at the
provided logs.  Try the patch, it might change the things, or it can just panic
at boot since the documentation about zens is non-existing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #53 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #52)

No luck. It survived a lot of builds, but still dumped core

funlockfile 0x80146ce48 0x80bcd1500 0x0
Bus error (core dumped)



BTW, DragonFly and Linux seem to have noticed Ryzen issues as well. Not sure if
its related to what I am seeing on FreeBSD ?

https://utcc.utoronto.ca/~cks/space/blog/linux/KernelRcuNocbsMeaning

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #54 from m...@sentex.net ---
Created attachment 190430
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190430&action=edit
latest backtrace post kernel patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #55 from Konstantin Belousov  ---
(In reply to mike from comment #53)
The article you linked does not provide any useful information.  Nobody knows
why this knob helped.

That said, I am both disappointed and relieved that the path did not helped. So
it is not the problem with the %fs/%gs handling, but the issue is completely
mysterious then.

Can you provide me with your libc.so.7 with the debugging patch applied, used
to obtain the logs ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #56 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #55)
The DragonFly commit mentioned here
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/b48dd28447fc8ef62fbc963accd301557fd9ac20
But I FreeBSD already have this set ?

libc.tgz is in your account on zoo.freebsd.org.  If there are other files you
need, the box is 192.168.5.191

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225762] diff truncate function name with --show-function-line

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225762

Bug ID: 225762
   Summary: diff truncate function name with --show-function-line
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: easy, feature
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: uzs...@uzsolt.hu

I noticed that diff truncates the "function name" if using -F
(--show-function-line) option. I think this problem is similar to this
stackoverflow question:
https://stackoverflow.com/questions/11232461/unix-diff-show-function-line-truncates-output
Are any reason to truncate or can enlarge it (or maybe user-definied with an
option)?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 159665] [patch] ctm(1) does not work with bzip2 or xz compressed files.

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=159665

j...@berklix.com changed:

   What|Removed |Added

 CC||j...@berklix.com

--- Comment #8 from j...@berklix.com ---
4 to 6 years on :-)
Please forget the old patches from same author, & instead commit 
step...@missouri.edu 's latest patches, namely:
ftp://ctm.berklix.org/pub/FreeBSD/development/CTM/svn-cur/
  16221 Nov 15  2014 patch-for-ctm-v09
878 Sep 24  2012 patch-for-ctm_rmail
583 Dec 25  2011 patch-for-ctm_smail
   8655 Nov 15  2014 patch-for-mkctm-v05

An easy, long awaited commit, these are addresses a
commiter can check back with if wanted:
  CTM User list:   
  CTM Orginal Author:  "Poul-Henning Kamp" 
  CTM diffs, gen & tools:  "Stephen Montgomery-Smith," 
  CTM repository:  "Julian H. Stacey" 
  More URLshttp://berklix.org/ctm/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #57 from Konstantin Belousov  ---
(In reply to mike from comment #56)
Yes, that was already handled.  And, the hang there is the whole system hang.

Please apply this debugging patch and try reproduce the issue one more time.

diff --git a/lib/libc/stdio/_flock_stub.c b/lib/libc/stdio/_flock_stub.c
index 069ed64c4e9..99e1af6fbfb 100644
--- a/lib/libc/stdio/_flock_stub.c
+++ b/lib/libc/stdio/_flock_stub.c
@@ -45,6 +45,8 @@ __FBSDID("$FreeBSD$");
 #include 
 #include 
 #include "un-namespace.h"
+#include 
+#include 

 #include "local.h"

@@ -116,6 +118,8 @@ _funlockfile(FILE *fp)
/*
 * Check if this file is owned by the current thread:
 */
+   while (*(volatile struct thread * volatile *)&fp->_fl_owner == NULL)
+   ;
if (fp->_fl_owner == curthread) {
/*
 * Check if this thread has locked the FILE
@@ -138,4 +142,11 @@ _funlockfile(FILE *fp)
_pthread_mutex_unlock(&fp->_fl_mutex);
}
}
+   else {
+   char x[120];
+   snprintf(x, sizeof(x), "funlockfile %p %p %p\n", fp,
+curthread, fp->_fl_owner);
+   write(2, x, strlen(x));
+   raise(SIGBUS);
+   }
 }

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #58 from m...@sentex.net ---
Created attachment 190431
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190431&action=edit
with while loop patch

funlockfile 0x80146caa0 0x80c83b800 0x0
Bus error (core dumped)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #59 from Konstantin Belousov  ---
(In reply to mike from comment #58)
Lets try a slight variation.

diff --git a/lib/libc/stdio/_flock_stub.c b/lib/libc/stdio/_flock_stub.c
index 069ed64c4e9..935bf18b529 100644
--- a/lib/libc/stdio/_flock_stub.c
+++ b/lib/libc/stdio/_flock_stub.c
@@ -39,12 +39,16 @@
 #include 
 __FBSDID("$FreeBSD$");

+#include 
+#include 
 #include "namespace.h"
 #include 
 #include 
 #include 
 #include 
 #include "un-namespace.h"
+#include 
+#include 

 #include "local.h"

@@ -112,11 +116,14 @@ void
 _funlockfile(FILE *fp)
 {
pthread_t   curthread = _pthread_self();
+   pthread_t fl_owner;

/*
 * Check if this file is owned by the current thread:
 */
-   if (fp->_fl_owner == curthread) {
+   while ((fl_owner = (pthread_t)atomic_load_ptr(&fp->_fl_owner)) == NULL)
+   ;
+   if (fl_owner == curthread) {
/*
 * Check if this thread has locked the FILE
 * more than once:
@@ -138,4 +145,11 @@ _funlockfile(FILE *fp)
_pthread_mutex_unlock(&fp->_fl_mutex);
}
}
+   else {
+   char x[120];
+   snprintf(x, sizeof(x), "funlockfile %p %p %p %p\n", fp,
+curthread, fl_owner, fp->_fl_owner);
+   write(2, x, strlen(x));
+   raise(SIGBUS);
+   }
 }

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692

--- Comment #8 from jkerian+freebsdb...@gmail.com ---
(In reply to Conrad Meyer from comment #7)

Is UTF-8.src pulled from CLDR in some scripted way? Or is that a custom file?

If custom, I have other codepoints that should probably be added as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692

--- Comment #9 from Conrad Meyer  ---
(In reply to jkerian+freebsdbugs from comment #8)
I believe it is an automated tool, but bapt knows much more about this process
than I do.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #60 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #59)
I have to confess, I might have borked the previous patch and left the while
loop commented out :(  I have made sure its right this time.  Five builds so
far

root@amdtestr12:/usr/src/lib/libc/stdio # uname -a
FreeBSD amdtestr12.sentex.ca 12.0-CURRENT FreeBSD 12.0-CURRENT #2 r328667M: Thu
Feb  8 07:14:25 EST 2018
mdtan...@amdtestr12.sentex.ca:/usr/obj/usr/src/amd64.amd64/sys/DEBUG  amd64
root@amdtestr12:/usr/src/lib/libc/stdio # rm _flock_stub.c
root@amdtestr12:/usr/src/lib/libc/stdio # cd /usr/src
root@amdtestr12:/usr/src # 
root@amdtestr12:/usr/src # svnlite update -r328667
Updating '.':
Restored 'lib/libc/stdio/_flock_stub.c'
At revision 328667.
root@amdtestr12:/usr/src #
root@amdtestr12:/usr/src # patch -p1 < p
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--
|--- a/lib/libc/stdio/_flock_stub.c
|+++ b/lib/libc/stdio/_flock_stub.c
--
Patching file lib/libc/stdio/_flock_stub.c using Plan A...
Hunk #1 succeeded at 39 with fuzz 2.
Hunk #2 succeeded at 116.
Hunk #3 succeeded at 145.
done
root@amdtestr12:/usr/src #cd lib/libc;  make depend;make

root@amdtestr12:/usr/src/lib/libc # date
Thu Feb  8 13:23:36 EST 2018
root@amdtestr12:/usr/src/lib/libc # ldd /usr/local/bin/python2.7
/usr/local/bin/python2.7:
libthr.so.3 => /usr/obj/usr/src/amd64.amd64/lib/libthr/libthr.so.3.full
(0x800645000)
libpython2.7.so.1 => /usr/local/lib/libpython2.7.so.1 (0x800a0)
libdl.so.1 => /usr/obj/usr/src/amd64.amd64/lib/libdl/libdl.so.1.full
(0x800878000)
libintl.so.8 => /usr/local/lib/libintl.so.8 (0x800e71000)
libutil.so.9 =>
/usr/obj/usr/src/amd64.amd64/lib/libutil/libutil.so.9.full (0x80087c000)
libm.so.5 => /usr/obj/usr/src/amd64.amd64/lib/msun/libm.so.5.full
(0x800892000)
libc.so.7 => /usr/obj/usr/src/amd64.amd64/lib/libc/libc.so.7.full
(0x80107c000)
root@amdtestr12:/usr/src/lib/libc # ls -l
/usr/obj/usr/src/amd64.amd64/lib/libc/libc.so.7.full
-rwxr-xr-x  1 root  wheel  7919824 Feb  8 13:23
/usr/obj/usr/src/amd64.amd64/lib/libc/libc.so.7.full
root@amdtestr12:/usr/src/lib/libc #

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225771] [icmp] members of icmpstat are still u_long, why not uint64_t?

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225771

Bug ID: 225771
   Summary: [icmp] members of icmpstat are still u_long, why not
uint64_t?
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: k...@xiplink.com

Created attachment 190441
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190441&action=edit
replace u_long to uint64_t in icmpstat

r253081 changed all fields of many stat structures to uint64_t to adapt with
the PCPU counters, but icmpstat's all fields are still u_long. And then r253084
migrate many structs including icmpstat to PCPU.

There is no error while building it because the number of the fields is even,
so it might be forgotten, but if a new u_long field is added into the struct,
then there will be an build error.

A patch to change all fields to uint64_t is attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #61 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #59)


Its managed 22 builds now without issue. Prior, I could only do 10 at most.  I
have a separate RELENG_11 box as well. I take it the same patch will work there
too ? It applies cleanly and builds. I will install it and test there too.  I
am curious to see if this fixes the other builds like openjdk. It didnt involve
python, but it too would hang.  I will let things run for 24hrs, unless there
is another crash.



Thank you again for all your work with this!  Next week we get an Epyc based
system to eval and I will test against it too.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


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

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584

--- Comment #62 from Konstantin Belousov  ---
(In reply to mike from comment #61)
Do not consider it a fix.  I do not have any explanation what is going on
there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 224825] Screen corruption booting 20171227 snapshot

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224825

D. Ebdrup  changed:

   What|Removed |Added

 CC||debd...@gmail.com

--- Comment #11 from D. Ebdrup  ---
I don't think it'd be a problem if you bumped this from 'Affects Only Me' to
'Affects Other People', since I can confirm that I see this exact same
behaviour on my T420, and it has been reported at least once (and I seem to
recall more times, though I can't find them) on various social media like [1].

Once I get the Intel ME password removed, I'll try and see if I can add more
information.

[1]: https://twitter.com/v_mfm_yss/status/961685497398558722

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225775] btxld does not handle input with other than 2 PT_LOAD segments

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775

Bug ID: 225775
   Summary: btxld does not handle input with other than 2 PT_LOAD
segments
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ema...@freebsd.org

Linking e.g. zfsloader reports (whitespace added for clarity):

cc -O2 -pipe -I/usr/home/emaste/src/freebsd-wip/stand/i386/btx/lib -nostdinc
-I/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/libsa32
-I/usr/home/emaste/src/freebsd-wip/stand/libsa -D_STANDALONE
-I/usr/home/emaste/src/freebsd-wip/sys -DLOADER_GELI_SUPPORT
-I/usr/home/emaste/src/freebsd-wip/stand/geli -DLOADER_DISK_SUPPORT -m32
-mcpu=i386 -ffreestanding -mno-mmx -mno-sse -mno-avx -mno-avx2 -msoft-float
-march=i386 -I. -I/usr/home/emaste/src/freebsd-wip/stand/common
-I/usr/home/emaste/src/freebsd-wip/stand/ficl
-I/usr/home/emaste/src/freebsd-wip/stand/ficl/i386
-I/usr/home/emaste/src/freebsd-wip/stand/common -DBF_DICTSIZE=15000
-DLOADER_UFS_SUPPORT -DLOADER_GZIP_SUPPORT -DLOADER_BZIP2_SUPPORT
-DLOADER_NET_SUPPORT -DLOADER_NFS_SUPPORT -DLOADER_TFTP_SUPPORT
-DLOADER_GPT_SUPPORT -DLOADER_MBR_SUPPORT -DLOADER_ZFS_SUPPORT
-I/usr/home/emaste/src/freebsd-wip/stand/zfs
-I/usr/home/emaste/src/freebsd-wip/sys/cddl/boot/zfs -Wall
-I/usr/home/emaste/src/freebsd-wip/stand/i386 -DLOADER_PREFER_AMD64 -std=gnu99
-Wsystem-headers -Werror -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value
-Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion
-Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch
-Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses
-Qunused-arguments  -nostdlib -Wl,-z,norelro -static -Ttext 0x0 -Wl,-z,norelro
-o zfsloader.sym
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/i386/btx/lib/crt0.o
main.o conf.o vers.o chain.o boot.o commands.o console.o devopen.o interp.o
interp_backslash.o interp_parse.o ls.o misc.o module.o load_elf32.o
load_elf32_obj.o reloc_elf32.o load_elf64.o load_elf64_obj.o reloc_elf64.o
disk.o part.o dev_net.o bcache.o isapnp.o pnp.o interp_forth.o 
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/ficl32/libficl.a 
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/zfs32/libzfsboot.a
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/i386/libi386/libi386.a
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/geli/libgeliboot.a
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/libsa32/libsa32.a

strip -R .comment -R .note -o zfsloader.bin zfsloader.sym

btxld -v -f aout -e 0x20 -o zfsloader -l
/usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/i386/btx/btxldr/btxldr
 -b /usr/obj/usr/home/emaste/src/freebsd-wip/amd64.amd64/stand/i386/btx/btx/btx
zfsloader.bin

btxld: zfsloader.bin: Warning: Ignoring extra elf PT_LOAD segments

kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=0:59
client: fmt=elf size=6bcd0 text=58834 data=afec bss=0 entry=0
output: fmt=aout size=6f000 text=1000 data=6d000 org=20 entry=20

btxld has:

case 2:
Warn(fname,
 "Ignoring extra %s PT_LOAD segments",
 fmtlist[fmt]);

i.e., it expects two PT_LOADs with a specific format, and just ignores the
third or later ones.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225778] ntpd fails to stay running

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225778

Bug ID: 225778
   Summary: ntpd fails to stay running
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: lcr...@gmail.com

ntpd fails to stay running on my brand new bhyve vm.   I've edited the config
file to point to my local server which syncs to the ntp pools so as to reduce
traffic to their servers.  I also tried it with a configuration offered by the
ntpd developers at their site with the same results.


truss output of ntpd

https://pastebin.com/9GHNV0Bz


the host is a bhyve VM running FreeBSD 11.1-RELEASE under UEFI, on a FreeNAS
11.1 server.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 224825] Screen corruption booting 20171227 snapshot

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224825

--- Comment #12 from D. Ebdrup  ---
Turns out it was a lot less effort to reset the ME password, so in case any
additional information needs to be had, I can provide it easily.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225775] btxld does not handle input with other than 2 PT_LOAD segments

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775

--- Comment #1 from Andriy Gapon  ---
Just curious, why the boot code may need more than two segments.
It would be interesting to see readelf or objdump output for zfsloader.bin.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225782] Ryzen: unable to set cpu freq

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225782

Bug ID: 225782
   Summary: Ryzen: unable to set cpu freq
   Product: Base System
   Version: 11.1-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: rozhuk...@gmail.com

After boot was:
dev.hwpstate.0.freq_settings: 3500/-1 3500/-1 1550/-1
dev.cpu.0.freq_levels: 3500/-1 3500/-1 1550/-1
dev.cpu.0.freq: 1550

After set:
dev.cpu.0.freq=3500
perfomance degraded to ~50%

Returning dev.cpu.0.freq=1550 does not help with performance.
11.1-STABLE FreeBSD 11.1-STABLE  r328439M  amd64
Ryzen 1300X, no overclock, fixed freq and Voltage in BIOS.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 206420] boot to white screen with Haswell graphics enabled

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206420

m...@luckie.org.nz changed:

   What|Removed |Added

 CC||m...@luckie.org.nz

--- Comment #2 from m...@luckie.org.nz ---
This issue is present in 11.1R, but wasn't present in 10.3R.  This is on a Dell
Optiplex 9020 with an Nvidia card installed.  To remove the white screen I had
to select "auto" in the Video options in the BIOS (rather than select the
Nvidia card).  The auto apparently disables the onboard graphics.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225782] Ryzen: unable to set cpu freq

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225782

--- Comment #1 from Conrad Meyer  ---
If this is also true on CURRENT, it looks like a buggy BIOS.  Your BIOS isn't
reporting P-states via ACPI or you would see a second positive number instead
of "/-1".  It's possible the BIOS bug also breaks P-state setting.  If a BIOS
update is available from your vendor, consider applying it.

If this works on CURRENT, great.  I don't support stable branches, so I would
just unsubscribe from this bug in that case.

In either case, I'd suggest rebooting and just not setting dev.cpu.0.freq
(leaving the machine in P0).  At idle, FreeBSD enters power-saving C-states and
won't consume any more power than if you were also downclocked.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225775] btxld does not handle input with other than 2 PT_LOAD segments

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775

--- Comment #2 from Ed Maste  ---
It is because lld collects read-only contents into a separate segment, for
example:

% readelf -l zfsloader.sym

Elf file type is EXEC (Executable file)
Entry point 0x0
There are 5 program headers, starting at offset 52

Program Headers:
  Type   Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  LOAD   0x001000 0x 0x 0x58694 0x58694 R E 0x1000
  LOAD   0x05a000 0x00059000 0x00059000 0x0afcc 0x0afcc R   0x1000
  LOAD   0x065000 0x00064000 0x00064000 0x07854 0x14c9c RW  0x1000
  GNU_RELRO  0x06c000 0x0006b000 0x0006b000 0x00854 0x01000 R   0x1
  GNU_STACK  0x00 0x 0x 0x0 0x0 RW  0

 Section to Segment mapping:
  Segment Sections...
   00 .text .gnu_debuglink .comment .debug_str .debug_loc .debug_abbrev
.debug_info .debug_ranges .debug_macinfo .debug_pubnames .debug_pubtypes
.debug_frame .debug_line .debug_aranges .symtab .shstrtab .strtab 
   01 .rodata set_Xcommand_set 
   02 .data set_Xficl_compile_set .data.rel.ro .got .bss 
   03 .data.rel.ro .got 
   04 

Linking with -z norelro leaves the three PT_LOADs, just the PT_GNU_RELRO is not
emitted. From the output above btxld should coalesce two PT_LOADs, and
discarding a PT_LOAD should be an error not a warning.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 225771] [icmp] members of icmpstat are still u_long, why not uint64_t?

2018-02-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225771

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"