[Bug 222927] usr.bin/procstat/procstat_test:command_line_arguments failing periodically; procstat -c is failing intermittently with ENOMEM

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222927 Ngie Cooper changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org

[Bug 222927] usr.bin/procstat/procstat_test:command_line_arguments failing periodically; procstat -c is failing intermittently with ENOMEM

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222927 Bug ID: 222927 Summary: usr.bin/procstat/procstat_test:command_line_arguments failing periodically; procstat -c is failing intermittently with ENOMEM Product: Base

[Bug 221356] [patch] Improve swapon_check_swzone() function in swap_pager.c

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356 --- Comment #11 from o...@j.email.ne.jp --- Created attachment 187071 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187071=edit set vm_swap_enabled=1 after swap zones are initialized This is a proposal and not an complete

[Bug 221356] [patch] Improve swapon_check_swzone() function in swap_pager.c

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356 --- Comment #10 from o...@j.email.ne.jp --- Thank you for taking few pieces of the 1st patch. After your announced changes and these patches got into 11-stable, I've been experimenting with swap. I prepared 2 additional patch sets; one is

[Bug 221356] [patch] Improve swapon_check_swzone() function in swap_pager.c

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221356 --- Comment #9 from o...@j.email.ne.jp --- Created attachment 187070 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187070=edit NO_SWAPPING in vm_pageout() After some experiments and reading swap_pager.c, we can put NO_SWAPPING

[Bug 222922] bsdinstall(8) does not format efi partitions as msdosfs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222922 --- Comment #1 from Trix Farrar --- Changing the efi partition, in the definition of the PARTITIONS variable, to freebsd-ufs results in successful completion, but it can't be used for UEFI until the partition type is

[Bug 222922] bsdinstall(8) does not format efi partitions as msdosfs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222922 Bug ID: 222922 Summary: bsdinstall(8) does not format efi partitions as msdosfs Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any

[Bug 222874] symbol 'KERNBASE' can not be undefined in a subtraction expression in mpboot.s

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222874 --- Comment #2 from o...@j.email.ne.jp --- I tried switching revisions between these 2 to find a trigger. Somehow, after "rm /usr/obj/usr/src/sys/GENERIC/mpboot.o"、mpboot.s started compiling okay. I updated back to HEAD of 11-stable and

[Bug 206990] powerpc (32-bit), projects/clang380-import vs. 11.0-CURRENT's sendsig: need to avoid signal delivery trashing the stack and so causing SIGSEGV

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206990 --- Comment #17 from Mark Millard --- (In reply to Justin Hibbits from comment #16) I've recently finally updated my powerpc contexts, including 32-bit without so-called red-zone use. It is working so far (G5, G4,

[Bug 206990] powerpc (32-bit), projects/clang380-import vs. 11.0-CURRENT's sendsig: need to avoid signal delivery trashing the stack and so causing SIGSEGV

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206990 Justin Hibbits changed: What|Removed |Added Resolution|--- |FIXED

[Bug 214718] x86bios panics at boot if it cannot obtain memory

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214718 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: emaste Date: Wed Oct 11 00:31:54 UTC 2017 New revision: 324510 URL: https://svnweb.freebsd.org/changeset/base/324510 Log: MFC r309151: Use explicit

[Bug 222916] [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 --- Comment #1 from kari...@gmail.com --- And while I remember, hyperthreading on the host is disabled, sysutils/devcpu-data is installed and microcode_update_enable="YES" is present in /etc/rc.conf . -- You are receiving this mail

[Bug 222916] [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 Bug ID: 222916 Summary: [bhyve] Debian guest kernel panics with message "CPU#0 stuck for Xs!" Product: Base System Version: 11.1-RELEASE Hardware: amd64

[Bug 222891] /usr/bin/tar exits with INTERNAL ERROR: Function 'archive_read_disk_open'

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891 --- Comment #4 from Martin Matuska --- Dear papow...@astart.com, to reproduce this bug I need more information: 1. Could you provide me with the filelist /tmp/rmis_save.tmp49784? Or at least a minimal part of it to

[Bug 222891] /usr/bin/tar exits with INTERNAL ERROR: Function 'archive_read_disk_open'

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891 Martin Matuska changed: What|Removed |Added Status|New |Open -- You

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 Mark Millard changed: What|Removed |Added Severity|Affects Some People |Affects Only

[Bug 222876] growfs messes with ufs filesystem size and checkums

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222876 --- Comment #7 from Sylvain Garrigues --- Thanks guys! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org

[Bug 222876] growfs messes with ufs filesystem size and checkums

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222876 Warner Losh changed: What|Removed |Added Resolution|--- |FIXED

[Bug 222908] Boot hangs on HPET on Intel Apollo Lake

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222908 Bug ID: 222908 Summary: Boot hangs on HPET on Intel Apollo Lake Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #10 from Heinz N. Gies --- I see I totally missunderstood your ticket then, but you're right it'd make sense if the toolchain itself would do that! -- You are receiving this mail because: You are the

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #9 from Mark Millard --- (In reply to Heinz N. Gies from comment #8) buildworld creates the files below in the build directory tree involved: ./contrib/libstdc++/include/tr1/stdint.h

[Bug 222876] growfs messes with ufs filesystem size and checkums

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222876 Ed Maste changed: What|Removed |Added Component|arm |bin

[Bug 213155] possible kernel regression when running 11.x-RELEASE on KVM on AMD Opterons

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155 Torfinn Ingolfsen changed: What|Removed |Added CC|

[Bug 221920] local_unbound NOT working

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221920 jo...@a1poweruser.com changed: What|Removed |Added Status|New |Closed

[Bug 74127] [patch] patch(1) may misapply hunks with too little context

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=74127 Kyle Evans changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|kev...@freebsd.org

[Bug 222904] Moxa C168H/PCI not sending/receiving data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222904 Bug ID: 222904 Summary: Moxa C168H/PCI not sending/receiving data Product: Base System Version: 10.3-RELEASE Hardware: i386 OS: Any Status: New

[Bug 220727] Cannot reboot Lenovo X1 Carbon (5th gen/2017)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220727 stefanw changed: What|Removed |Added CC|

[Bug 222079] [ichwd] New Intel TCO Watchdog Timer (Skylake/Sunrise Point and newer) is not supported

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222079 --- Comment #1 from Konstantin Belousov --- I have some WIP but it is far from being able to drive the hardware. The current state is that I have attachments for the power controller, added code which understands

[Bug 222902] local_unbound interfering with port version and other problems

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222902 Bug ID: 222902 Summary: local_unbound interfering with port version and other problems Product: Base System Version: 11.1-RELEASE Hardware: Any OS:

[Bug 222901] `make buildworld' fails if $NO_OBJ is set

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222901 --- Comment #1 from Dimitry Andric --- I'm not sure if using NO_OBJ for buildworld is supported at all. :) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 222901] `make buildworld' fails if $NO_OBJ is set

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222901 Bug ID: 222901 Summary: `make buildworld' fails if $NO_OBJ is set Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity:

[Bug 222899] After lease expiration dhclient-script mess up network

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222899 Bug ID: 222899 Summary: After lease expiration dhclient-script mess up network Product: Base System Version: 10.4-RELEASE Hardware: Any OS: Any Status: New

[Bug 222898] [iscsi]: panic: page fault - system crashes while working as iSCSI target

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222898 Bug ID: 222898 Summary: [iscsi]: panic: page fault - system crashes while working as iSCSI target Product: Base System Version: 11.0-STABLE Hardware: Any

[Bug 202712] System doesn't recognize older hdd after boot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712 cab...@yahoo.com changed: What|Removed |Added Status|Closed |Open

[Bug 221990] panic: Assertion reclaimable == delta failed at ../../../net/iflib.c:1947

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221990 --- Comment #3 from Peter Holm --- Yes, Index: /usr/src/sys/net/iflib.c === --- /usr/src/sys/net/iflib.c(revision 323151) +++ /usr/src/sys/net/iflib.c

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #8 from Heinz N. Gies --- Hmm interesting, I must have done something wrong. To double check, I ran build world again and then re-build the kernel after removing the stdint.h I copied, it build cleaninly

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #7 from Heinz N. Gies --- Oh yes I wasn't cross compiling I was compiling a kernel on the host with slightly modified config (RCTL/VNET) so the stdint.h should be the same I guess. -- You are receiving

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #6 from Mark Millard --- (In reply to Heinz N. Gies from comment #5) If the build-host system type is the same as the build-target system type and stdint.h has not actually changed then

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #5 from Heinz N. Gies --- I admit I've no idea what I'm doing ;), I'm just trying to bang my head around getting it to work. But what you say makes sense. I'm just happy it worked! -- You are receiving

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #4 from Mark Millard --- (In reply to Heinz N. Gies from comment #3) I do not expect that the working "buildworld" puts a stdint.h in /usr/lib/clang/5.0.0/include/ so I do not expect that that is the right

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #3 from Heinz N. Gies --- This is most likely not a good solution but I could get the kernel to compile with this: cp /usr/lib/include/stdint.h /usr/lib/clang/5.0.0/include/ it seems the

[Bug 220125] head -r320059 (e.g.) arm64: buildkernel after kernel-toolchain: crypto/armv8/armv8_crypto_wrap.c compile fails with .../lib/clang/4.0.0/include/arm_neon.h: fatal error: 'stdint.h' file no

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125 --- Comment #2 from Heinz N. Gies --- I think Mark is right, it's a toolchain issue. Some googling later it looks like the issue is also present on non BSD systems that use NEON: -

[Bug 209468] aacraid run_interrupt_driven_hooks: still waiting after 60-300 seconds for xpt_config panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209468 --- Comment #30 from Maxim --- (In reply to Ed Maste from comment #28) Since the 7 generation model and below are different from the 8 generation, does it just make different drivers? Do you think it is possible to

[Bug 209468] aacraid run_interrupt_driven_hooks: still waiting after 60-300 seconds for xpt_config panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209468 --- Comment #29 from Maxim --- I have one more question, in drivers 3.3.2 from site adaptec.com we see (New comm. interface type3 enabled): aacraidu0: port 0x6000-0x60ff mem 0xc710-0xc71f,0xc728-0xc72803ff

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

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399 --- Comment #273 from SF --- I've read of people who fixed it by doing similiar things like you did, someone printed himself an case for an aircooler with an 3d-printer to improve cooling on his ryzen-motherboard.

[Bug 222892] gcc compilation errors with mlx4_en and mlx5

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222892 Ngie Cooper changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org

[Bug 222892] gcc compilation errors with mlx4_en and mlx5

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222892 Bug ID: 222892 Summary: gcc compilation errors with mlx4_en and mlx5 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New