Date: Wed, 22 Feb 2017 18:14:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 217299] Periodic Kernel Panic with FreeBSD 10.3-RELEASE and Myricom cards. Message-ID: <bug-217299-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217299 Bug ID: 217299 Summary: Periodic Kernel Panic with FreeBSD 10.3-RELEASE and Myricom cards. Product: Base System Version: 10.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: mshirk@daemon-security.com In working with members of the Bro community that run FreeBSD, an issue was brought to my attention with a user running a large setup of FreeBSD systems running Bro NSM. The issue appears to be between FreeBSD and Myricom. Myricom support has stated this is a known issue in FreeBSD. I am submitting this bug on behalf of Keith (attached as a CC to this bug) to try to figure this out.=20 He is not able to catch the kernel panic, but below are syslog messages that lead up to the panic. Sep 30 06:23:11 gulp9 devd: Processing event '!system=3DDEVFS subsystem=3DC= DEV type=3DCREATE cdev=3Dmyri_fake.1048575' Sep 30 06:23:11 gulp9 devd: Pushing table Sep 30 06:23:11 gulp9 devd: Processing notify event Sep 30 06:23:11 gulp9 devd: Popping table Sep 30 06:23:12 gulp9 dev 0xfffff80139c8b400 (myri_fake.0) is on clonelist Sep 30 06:23:12 gulp9 unit=3D0, low=3D1048576, extra=3D0x0 Sep 30 06:23:12 gulp9 0xfffff80139c8b400 myri_fake.0 Sep 30 06:23:12 gulp9 0xfffff8022dbb2000 myri_fake.1 Sep 30 06:23:12 gulp9 0xfffff8022dd00800 myri_fake.2 Sep 30 06:23:12 gulp9 0xfffff801a7244c00 myri_fake.3 Sep 30 06:23:12 gulp9 0xfffff801a7243000 myri_fake.4 Sep 30 06:23:12 gulp9 0xfffff80139650e00 myri_fake.5 Sep 30 06:23:12 gulp9 0xfffff80139bebe00 myri_fake.6 Sep 30 06:23:12 gulp9 0xfffff801390f1200 myri_fake.7 Sep 30 06:23:12 gulp9 0xfffff8013904cc00 myri_fake.8 Basically the myri_counters tool tries to open several devices that don=E2= =80=99t exist in an attempt to find the device for this NIC. Each failed open raises a CREATE event. Like clockwork, the box will panic after a few weeks. Every= box in the cluster will panic in roughly the order they were booted. He has not found a way to configure devfs to just ignore these events. In the Bro sens= e, the cluster is a group of servers setup as worker nodes, with the function = of processing up do 10Gb/s of network traffic for network monitoring.=20 Keith is currently running 10.3-RELEASE-p7 (when I received the info), and = he is looking to do a test with FreeBSD 11.0-RELEASE. The same Myricom card did not exhibit this issue on FreeBSD 9. (additional details about the hardware are available from Keith). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217299-8>