[Bug 252894] Fix public key derivation if WireGuard implementation

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252894 --- Comment #3 from shamaz.ma...@gmail.com --- Peter, did you test your patch with any of VPN service providers? -- You are receiving this mail because: You are the assignee for the bug. ___ free

[Bug 252894] Fix public key derivation if WireGuard implementation

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252894 --- Comment #4 from Peter Grehan --- I didn't test traffic against service providers, but I verified the generated public key was correct using the private key from your test case posted to freebsd-net. The change is functionally identical

[Bug 252894] Fix public key derivation if WireGuard implementation

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252894 --- Comment #5 from shamaz.ma...@gmail.com --- Uh, OK. If public keys derived by if_wg and by Mullvad match, then it should work. I think so. -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 252894] Fix public key derivation if WireGuard implementation

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252894 --- Comment #6 from Peter Grehan --- I believe it will be ok. Many thanks for diagnosing this issue. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@f

[Bug 226673] real memory > physical memory (amd64 Virtualbox guest)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226673 --- Comment #6 from Helge Oldach --- (In reply to Helge Oldach from comment #5) Still the same with FreeBSD 13.0-ALPHA2 #3 stable/13-c256213-g03d837b565a and virtualbox-ose-additions-5.2.44_3: 4096 MB memory allocated to the VM shows up as

[Bug 226673] real memory > physical memory (amd64 Virtualbox guest)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226673 Helge Oldach changed: What|Removed |Added Version|11.1-STABLE |13.0-STABLE -- You are receiving t

[Bug 253048] unionfs shows old file with link count of zero

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253048 Bug ID: 253048 Summary: unionfs shows old file with link count of zero Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New

[Bug 253051] panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253051 Bug ID: 253051 Summary: panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression) Product: Base System Version: CURRENT Hardware: mips

[Bug 253051] panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253051 Mitchell Horne changed: What|Removed |Added CC||mho...@freebsd.org --- Comment #1

[Bug 253051] panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253051 --- Comment #2 from Michał Górny --- I'm afraid not: db> bt Tracing pid 0 tid 0 td 0x80900240 --- swapped out Not even if I swapped kernel.full in place of kernel. -- You are receiving this mail because: You are the assignee for

[Bug 253051] panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253051 --- Comment #3 from Mitchell Horne --- Created attachment 221970 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=221970&action=edit delay call to cpu_init_interrupts (In reply to Michał Górny from comment #2) That's unfortunate.

[Bug 253051] panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253051 --- Comment #4 from Michał Górny --- It still fails but I can get some backtrace now ;-). --- entry: platform_start() cmd line: kernel envp: memsize = 134217728 ememsize = 134217728 modetty0 = 38400n8r memsize = 1

[Bug 250580] VMware UEFI guests crash in virtual hardware after r366691

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 --- Comment #19 from Daniel Morante --- Here's what I'm observing: VMWare Workstation: 15.5.7 build-17171714 Host: Windows 7 Enterprise, 64-bit 6.1.7601, Service Pack 1 Guest OS ISO: FreeBSD-12.2-RELEASE-amd64-bootonly.iso 1) Create a new

[Bug 250580] VMware UEFI guests crash in virtual hardware after r366691

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 --- Comment #20 from Daniel Morante --- Created attachment 221977 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=221977&action=edit Sample VMX file -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 253051] panic: mips_intrcnt_setname: NULL counter ; on qemu-system-mips64 (regression)

2021-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253051 --- Comment #5 from Oleksandr Tymoshenko --- Ooops, sorry for the breakage. Mitchell, are you looking into this or should I take this PR? -- You are receiving this mail because: You are the assignee for the bug. __