[Bug 222960] Installer suggests GPT+Active when booting in EFI mode

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222960 --- Comment #3 from Eric van Gyzen --- My coworker's CPU is exactly the same. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list

[Bug 222960] Installer suggests GPT+Active when booting in EFI mode

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222960 --- Comment #2 from Eric van Gyzen --- The EFI spec says the active flag must not be set on the PMBR pseudo-partition. I imagine the machine is just enforcing the spec. This very issue is the reason I added this machine to the blacklist.

[Bug 222960] Installer suggests GPT+Active when booting in EFI mode

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222960 --- Comment #1 from Allan Jude --- (In reply to Eric van Gyzen from comment #0) That is interesting, because if booting EFI it should not even look at the partition active flag. It should just run boot1.efi from the ESP. This hardware is o

[Bug 222632] connect(2) not available in capability mode

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 Ed Maste changed: What|Removed |Added Summary|Enable Capsicum for |connect(2) not available in

[Bug 222960] Installer suggests GPT+Active when booting in EFI mode

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222960 Bug ID: 222960 Summary: Installer suggests GPT+Active when booting in EFI mode Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 222632] Enable Capsicum for connect(2)

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632 --- Comment #12 from Ed Maste --- > There does seem to be a discrepancy across the documentation and what is > actually implemented, as CAP_CONNECT explicitly states that connect(2) is > allowed and the check is in place in the actual imple

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222898 Edward Tomasz Napierala changed: What|Removed |Added CC||tr...@freebsd.org --- Co

[Bug 222948] LOR Panic in disk access

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222948 --- Comment #1 from Conrad Meyer --- Can you paste the actual panic message here too? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org maili

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155 --- Comment #23 from Martin Waschbüsch --- (In reply to Oliver Böttcher from comment #22) Hi Oliver, thank you for adding these details. When you say that "enabling all features and model=qemu64 booted", does that include xsave? Also, do y

[Bug 222953] ipfw fwd tablearg & ipfw -q bugs

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222953 Bug ID: 222953 Summary: ipfw fwd tablearg & ipfw -q bugs Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Af

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155 --- Comment #22 from Oliver Böttcher --- (In reply to Oliver Böttcher from comment #20) Sorry I lost track of my own comment. I forgot to tell that enabling all features and model=qemu64 booted. -- You are receiving this mail because: You

[Bug 222951] Re-starting a jail with mount.devfs mounts devfs multiple times

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222951 Bug ID: 222951 Summary: Re-starting a jail with mount.devfs mounts devfs multiple times Product: Base System Version: 11.1-RELEASE Hardware: Any OS: A

[Bug 222948] LOR Panic in disk access

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222948 Bug ID: 222948 Summary: LOR Panic in disk access Product: Base System Version: 11.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Som

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155 --- Comment #21 from Oliver Böttcher --- Created attachment 187097 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187097&action=edit Screenshot of kernel panic when enabling xsave -- You are receiving this mail because: You are

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155 --- Comment #20 from Oliver Böttcher --- I don't know if this is of any interest but I want to help to track down this issue. I started to enable and disable several features in libvirt's machine config to find out when it starts to hang.

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222898 --- Comment #3 from e...@norma.perm.ru --- Seems like I have planned to add the debug kernel configuration later but totally forgot to do it. So, here it is: ident SANDEBUG include GENERIC options WITNESS options WITNESS_SKIPSPIN options I

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222898 --- Comment #2 from e...@norma.perm.ru --- This very system, being boot up with debug kernel, built with crashes somewhere withing 30 seconds after the ctld is started: WARNING: 10.0.3.211 (iqn.1991-05.com.microsoft:worker379): no ping rep

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

2017-10-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222898 --- Comment #1 from e...@norma.perm.ru --- Environment: Uname: FreeBSD san1.lynx.playkey.net 11.0-STABLE FreeBSD 11.0-STABLE #1 r310734M: Thu Sep 21 18:40:08 +05 2017 e...@san1.lynx.playkey.net:/usr/obj-11-r310734/usr/src-11-r310734/sy