[Bug 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #207 from Nils Beyer  ---
(In reply to Nils Beyer from comment #206)

answering myself: yes, maybe I should just listen to what Don said: I do need
that origin patch because without it the programm is not able to MMAP at
0x7f(...) - as Don instructed. And at 0x4f(...) there seems to be no problem.

Using "cpuset -l 0 ./ryzen_provoke_crash" it freezes exactly where my first
system did:

[...]
executing at 0x7f3a ..
executing at 0x7f3b ..
executing at 0x7f3c ..
executing at 0x7f3d ..
executing at 0x7f3e ..
executing at 0x7f3f ..
executing at 0x7f40 ..


Without using "cpuset -l 0" the program seems to pass the 0x7f40 mark,
but becomes very, very slow - don't know if it freezes because I aborted it;
took too long for one row...

-- 
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 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #206 from Nils Beyer  ---
(In reply to Nils Beyer from comment #205)

sorry, mass confusion in my brain; I accidentially executed that program on my
first Ryzen system with 32GB of RAM and your origin patch applied. The SSH
session to my second Ryzen system timed out, and because I do SSH there via SSH
to my first Ryzen system I was therefore thrown back to my first system which I
didn't notice. :-(

Sorry for the confusion, but the result stays the same. Freeze at the
suspicious location.

At the moment, I really try to get the same freeze on my second Ryzen system
(using another SSH hop) with 16GB of RAM. There, I had to use the second
"WHERE"-define as well. And there's vanilla 11.1-RELEASE indeed running, so I
assume that this freeze won't happen because I need your origin patch, right?

-- 
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 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #205 from Nils Beyer  ---
(In reply to Don Lewis from comment #204)

absolutely wonderful test case you've created - despite your instructions I've
run that program on a vanilla 11.1-RELEASE (no patches) on my second Ryzen
system (the one with 16GB where I've never poudriered), and it freezes exactly
there where you have experienced it (done it via SSH, so output is still
visible):
---
[...]
executing at 0x7f30 ..
executing at 0x7f31 ..
executing at 0x7f32 ..
executing at 0x7f33 ..
executing at 0x7f34 ..
executing at 0x7f35 ..
executing at 0x7f36 ..
executing at 0x7f37 ..
executing at 0x7f38 ..
executing at 0x7f39 ..
executing at 0x7f3a ..
executing at 0x7f3b ..
executing at 0x7f3c ..
executing at 0x7f3d ..
executing at 0x7f3e ..
executing at 0x7f3f ..
executing at 0x7f40 ...
---

tried that on my Intel Xeon E3-1220 v3 system, but had to use the second
"WHERE"-define because it couldn't mmap at 0x7f(...) - ENOMEM. Anyways, the
result is that it didn't freeze 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 220462] ar(1): while building emulators/virtualbox-ose ar(1) coredumps

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220462

--- Comment #8 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mm
Date: Fri Aug  4 23:34:40 UTC 2017
New revision: 322072
URL: https://svnweb.freebsd.org/changeset/base/322072

Log:
  MFH r321674:
  Sync libarchive with vendor.

  Relevant vendor changes:
PR #926: ensure ar strtab is null terminated

  PR:   220462

Changes:
_U  stable/10/
  stable/10/contrib/libarchive/libarchive/archive_cryptor_private.h
  stable/10/contrib/libarchive/libarchive/archive_write_set_format_ar.c

-- 
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 220462] ar(1): while building emulators/virtualbox-ose ar(1) coredumps

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220462

--- Comment #7 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mm
Date: Fri Aug  4 23:34:25 UTC 2017
New revision: 322071
URL: https://svnweb.freebsd.org/changeset/base/322071

Log:
  MFH r321674:
  Sync libarchive with vendor.

  Relevant vendor changes:
PR #926: ensure ar strtab is null terminated

  PR:   220462

Changes:
_U  stable/11/
  stable/11/contrib/libarchive/libarchive/archive_cryptor_private.h
  stable/11/contrib/libarchive/libarchive/archive_write_set_format_ar.c

-- 
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 221234] ZFS diff does not properly display files that have been moved to a new directory.

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221234

--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:

Author: asomers
Date: Fri Aug  4 23:01:14 UTC 2017
New revision: 322069
URL: https://svnweb.freebsd.org/changeset/base/322069

Log:
  Add a regression test for PR 221234

  etc/mtree/BSD.tests.dist
  tests/sys/cddl/zfs/tests/cli_root/Makefile
  tests/sys/cddl/zfs/tests/cli_root/zfs_diff/...
Add an automated test that checks the typical output of "zfs diff".
The is the first and only automated test for "zfs diff".  It
currently fails for a file that gets moved to a new directory.

  PR:   221234
  Sponsored by: Spectra Logic Corp

Changes:
  projects/zfsd/head/etc/mtree/BSD.tests.dist
  projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/Makefile
  projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/
  projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/Makefile
  projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/cleanup.ksh
  projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/setup.ksh
  projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/zfs_diff.cfg
 
projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/zfs_diff_001_pos.golden
 
projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/zfs_diff_001_pos.ksh
 
projects/zfsd/head/tests/sys/cddl/zfs/tests/cli_root/zfs_diff/zfs_diff_test.sh

-- 
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 221234] ZFS diff does not properly display files that have been moved to a new directory.

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221234

Bug ID: 221234
   Summary: ZFS diff does not properly display files that have
been moved to a new directory.
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: asom...@freebsd.org

The "zfs diff" command does not properly display a file that has moved to a new
directory.  Instead, it shows a moved file as a modified file.

Steps to reproduce:

# zpool create tank da0
# touch /tank/foo
# mkdir /tank/bar
# zfs snapshot tank@1
# mv /tank/foo /tank/bar/
# zfs snapshot tank@2
# zfs diff tank@1 tank@2
M   /tank/
M   /tank/foo
M   /tank/bar

OpenZFS has already fixed this issue in git revision
aab04418a72c0a29040a5da7eec08efe19dbef04 back in Oct-2015.  We should import it
into FreeBSD.

-- 
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 221224] setlocale.c does not properly detect if locale contains too many slashes

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221224

Bug ID: 221224
   Summary: setlocale.c does not properly detect if locale
contains too many slashes
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: leonard.r.koe...@googlemail.com

Overview
There's a loop at [1] which tries to find the first character after a number of
consecutive slashes.  In line 164 i == _LC_LAST is checked which should be
always false at this location, since it was set to 1 a few lines before and
never changed since.
But even if i was not set in this loop, it'd still wouldn't make any sense,
since then i would always have the value _LC_LAST because of the very first
loop in the function.

Steps to Reproduce
call setlocale(LC_ALL, "/somestring/");

Actual Results / Expected results:
Unclear



[1]
https://svnweb.freebsd.org/base/head/lib/libc/locale/setlocale.c?revision=314436=markup#l157

-- 
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 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen...

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399

--- Comment #204 from Don Lewis  ---
Created attachment 185022
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185022=edit
program to cause Ryzen hang/reboot on tweaked FreeBSD by executing code in high
memory

If you modify the FreeBSD kernel to lower the shared page, but leave sv_maxuser
at its original value so that a user program can mmap the page at
0x7000, the  attached program will fill that page with RET instructions
and perform calls to those in a loop.  I have not observed any issues with
calls to the RET instructions at 0x7f3f or below.  When the RET
instruction at 0x7f40 is executed, my machine will typically silently
reboot without a panic message, or it will sometimes hang with the screen
blanked.  This test is the most sensitive on core 0, which handles most
interrupts, so run under "cpuset -l 0" for best results.  The problem appears
to be triggered when the RET instruction is interrupted.

It is possible to load and execute arbitrary code for other experiments.

-- 
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 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029

--- Comment #51 from Don Lewis  ---
(In reply to Conrad Meyer from comment #46)
r321919 looks very promising.  I upgraded to r322026 and the only "unexpected"
failure during my poudriere run was the lang/ghc sigbus failure, which has
always failed for me on Ryzen.  It doesn't fix the hang/crash problem caused by
executing  code just under the top of user memory.

I'll re-enable SMT for my next poudriere run to see if my luck holds.

-- 
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 221221] netboot: shutting down netbooted machine hangs at "syncing disks... 1 1 1 1 1"

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221221

Bug ID: 221221
   Summary: netboot: shutting down netbooted machine hangs at
"syncing disks... 1 1 1 1 1"
   Product: Base System
   Version: 11.1-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: la5lb...@aon.at

Scenario:
- netboot installation upgraded from releng/11.0 to releng/11.1
- booted in latest VirtualBox
- shutdown -p now

Result:
- the shutdown hangs at "syncing disks... 1 1 1 1"
- the value 0 is never reached
- the process eventually times out

Expected result:
- Syncing disks should reach 0 remaining dirty blocks

-- 
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 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220

John  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Many People
   Hardware|Any |amd64

-- 
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 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220

--- Comment #3 from John  ---
Created attachment 185019
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185019=edit
info.0 from /var/crash

-- 
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 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220

--- Comment #2 from John  ---
Created attachment 185018
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185018=edit
minfree from /var/crash

-- 
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 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220

--- Comment #4 from John  ---
Created attachment 185020
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185020=edit
bounds from /var/crash

-- 
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 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220

--- Comment #1 from John  ---
Created attachment 185017
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185017=edit
textdump.tar from /var/crash

-- 
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 221220] panic when running as PVHVM under Xen with 4 cores and 4+ network interfaces

2017-08-04 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221220

Bug ID: 221220
   Summary: panic when running as PVHVM under Xen with 4 cores and
4+ network interfaces
   Product: Base System
   Version: 11.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: j...@keates.nl

Created attachment 185015
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185015=edit
serial console log

When running FreeBSD 11.0 in a Xen virtual machine with PVHVM support on, 4 cpu
cores and 4+ VIF network interfaces, the system always kernel panics. Using
less cpu cores or less interfaces never panics. (using 'always', and 'never' in
the context of this bug)

Attached is a boot log with 5 virtual interfaces and 4 CPU cores, at db> I
typed bt as that's about as much I can do regarding FreeBSD kernel debugging.

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