[Bug 251081] Grep Crashes with both «--after-context» «--max-count» Switches are Used

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251081 Igor Kolesnik changed: What|Removed |Added CC||igorkoles...@posteo.net --- Commen

[Bug 251081] Grep Crashes with both «--after-context» «--max-count» Switches are Used

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251081 --- Comment #2 from Igor Kolesnik --- Created attachment 219672 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219672&action=edit Include eol when calling execute in prpending -- You are receiving this mail because: You are the

[Bug 251121] rc.d/zfsbe can't properly mount child datasets

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251121 Bug ID: 251121 Summary: rc.d/zfsbe can't properly mount child datasets Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New

[Bug 250015] diff -purw fails with 'error: conflicting output format options.'

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250015 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: kevans Date: Sat Nov 14 00:59:55 UTC 2020 New revision: 367656 URL: https://svnweb.freebsd.org/changeset/base/367656 Log: MFC r367076: diff: don't forc

[Bug 200459] [nvme] Ioctl for passthrough can hang if called during nvme reset.

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200459 Juraj Lutter changed: What|Removed |Added CC||ju...@lutter.sk --- Comment #1 from

[Bug 251112] Compiling C++ with asan fails by default because libclang_rt.asan-x86_64.so uses symbol pthread_attr_get_np but doesn't link to libpthread.so

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251112 Bug ID: 251112 Summary: Compiling C++ with asan fails by default because libclang_rt.asan-x86_64.so uses symbol pthread_attr_get_np but doesn't link to libpthread.so P

[Bug 251083] Kernel built WITH_INIT_ALL_ZERO results in exception in UEFI during boot

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251083 --- Comment #8 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Fri Nov 13 18:34:13 UTC 2020 New revision: 367646 URL: https://svnweb.freebsd.org/changeset/base/367646 Log: Disable kernel INIT_ALL_ZERO

[Bug 250921] [nfs] linker_load_file: /boot/kernel/nfslockd.ko - unsupported file type

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250921 --- Comment #6 from Mark Johnston --- (In reply to Dan Lukes from comment #5) Committers are generally not in a position to fix bugs in an existing release. Binary patches are issued by secteam, usually only for severe problems without a w

[Bug 250921] [nfs] linker_load_file: /boot/kernel/nfslockd.ko - unsupported file type

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250921 --- Comment #5 from Dan Lukes --- I fully understand the matter. You closed this PR while the bug 249378 is (and remain) closed as well. As a result of your influence, all reports related to the bug are closed while issue is still unsolved.

[Bug 250921] [nfs] linker_load_file: /boot/kernel/nfslockd.ko - unsupported file type

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250921 --- Comment #4 from Mark Johnston --- (In reply to Dan Lukes from comment #3) It is the same root cause. The problem was fixed in stable/12, but not before the 12.2 branch was frozen, so unfortunately it is expected that the problem is sti

[Bug 251083] Kernel built WITH_INIT_ALL_ZERO results in exception in UEFI during boot

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251083 --- Comment #7 from Ed Maste --- Andy pointed out https://reviews.freebsd.org/D23499. I forgot about this review :( -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 251083] Kernel built WITH_INIT_ALL_ZERO results in exception in UEFI during boot

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251083 --- Comment #6 from Ed Maste --- Using QEMU's `-d exec` option I see last instructions before the exception are in these regions: Chain 0: 0x18a5f40 [/8105176a/0x40c2b0] ^M Chain 0: 0x18a60c0 [/f

[Bug 251083] Kernel built WITH_INIT_ALL_ZERO results in exception in UEFI during boot

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251083 Ed Maste changed: What|Removed |Added Summary|WITH_INIT_ALL_ZERO results |Kernel built |in exce

[Bug 251097] Error in /etc/mail/Makefile error message

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251097 e...@transbay.net changed: What|Removed |Added Severity|Affects Only Me |Affects Some People -- You are

[Bug 251097] Error in /etc/mail/Makefile error message

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251097 Bug ID: 251097 Summary: Error in /etc/mail/Makefile error message Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Sever

[Bug 250015] diff -purw fails with 'error: conflicting output format options.'

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250015 --- Comment #8 from fehmi noyan isi --- The conflicting output error must have been introduced by the bug report below https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243975 -- You are receiving this mail because: You are on the CC lis

[Bug 215611] Missing mq_unlink(2) man page (and broken xrefs)

2020-11-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215611 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added CC||0...@freebsd