[Bug 224414] 'kldload pf' or 'pf_enable="YES"' triggers immediate panic

2017-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224414

Bug ID: 224414
   Summary: 'kldload pf' or 'pf_enable="YES"' triggers immediate
panic
   Product: Base System
   Version: 11.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: freebsd-bugzi...@senator.net

Adding
   pf_enable="YES"

to /boot/loader.conf or /boot/loader.conf.local or, after a full boot,
   modload pf
causes an immediate kernel panic. This is reproducible on the (FreeBSD Mall
11.1 purchased) installation CD by selecting 'Shell' and then executing:
modload pf

This system was reliably in service for >3+ years running FreeBSD 9.0-RELEASE.
Upgrading to 11.1-RELEASE appears to have introduced this symptom.
1
# ls -l /boot/kernel/pf.ko
 ... 348024 July 21 02:20 /boot/kernel/pf.ko

# sum /boot/kernel/pf.ko
 13544 340 /boot/kernel/pf.ko

Kernel version: 11.1-RELEASE r321309 Fri Jul 21 02:08:28 UTC 2017
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64

Motherboard: SuperMicro X7DB8-X
http://www.supermicro.com/products/motherboard/xeon1333/5000P/X7DB8-X.cfm

NICs: Intel Pro/1000 (quantity 3) - detected as em[0-2]

Disk controllers: 3Ware 9550SXU-4LP (quantity 2) - detected as twa[0-1]

I am in the process of reinstalling this with a larger /var so as to enable
crash dumps.

-- 
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 211713] NVME controller failure: resetting (Samsung SM961 SSD Drives)

2017-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211713

Martin Stafford  changed:

   What|Removed |Added

 CC||mar...@humeco.com

--- Comment #41 from Martin Stafford  ---
Same problem here.
Works fine under Debian Stretch 9.2 with same hardware.

Supermicro X10DRL-I-O motherboard
ASUS Hyper M.2 x16 NVMe card
2 X Samsung PM961 256gb
1 X Samsung PM961 128gb

I've disabled the hw.nvme.per_cpu_io_queues and it's working but slow I think.

Here's some dmesg lines with hw.nvme.per_cpu_io_queues=0:

FreeBSD 11.1-STABLE #0 r321665+d4625dcee3e(freenas/11.1-stable): Wed Dec 13
16:33:42 UTC 2017
CPU: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz (2100.04-MHz K8-class CPU)
FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs
FreeBSD/SMP: 2 package(s) x 8 core(s) x 2 hardware threads
nvme0:  mem 0xc780-0xc7803fff irq 40 at device 0.0
numa-domain 0 on pci6
nvme1:  mem 0xc770-0xc7703fff irq 40 at device 0.0
numa-domain 0 on pci7
nvme2:  mem 0xc760-0xc7603fff irq 40 at device 0.0
numa-domain 0 on pci8
nvd0:  NVMe namespace
nvd0: 122104MB (250069680 512 byte sectors)
nvd1:  NVMe namespace
nvd1: 244198MB (500118192 512 byte sectors)
nvd2:  NVMe namespace
nvd2: 244198MB (500118192 512 byte sectors)

-- 
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 224415] 460.status-mail-rejects and 520.pfdenied appear broken

2017-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224415

Bug ID: 224415
   Summary: 460.status-mail-rejects and 520.pfdenied appear broken
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: conf
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: portmas...@bsdforge.com

On a fresh build/install on
FreeBSD dev-box 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Wed Dec 13 06:07:59 PST
2017 root@dev-box:/usr/obj/usr/src/amd64.amd64/sys/DEVBOX (r326056)

460.status-mail-rejects returns:
Checking for rejected mail hosts:
usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
   [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
   [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
   [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer]
   [-o file] [--referer=URL] [-S bytes] [-T seconds]
   [--user-agent=agent-string] [-w seconds] URL ...
   fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host]
   [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file]
   [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list]
   [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer]
   [-o file] [--referer=URL] [-S bytes] [-T seconds]
   [--user-agent=agent-string] [-w seconds] -h host -f file [-c dir]

in the daily logs

and 520.pfdenied
doesn't even show up.

Both worked fine on 9, and early 11.

Thanks!

--Chris

-- 
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 224415] 460.status-mail-rejects and 520.pfdenied appear broken

2017-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224415

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression

-- 
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 224414] 'kldload pf' or 'pf_enable="YES"' triggers immediate panic

2017-12-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224414

Mark Linimon  changed:

   What|Removed |Added

   Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org

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