https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283815
--- Comment #8 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=6ba2c036a0117ac02f9979b7dc49f15e9c1ea9c9
commit 6ba2c036a0117ac02f9979b7dc49f15e9c1ea9c9
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283815
Ed Maste changed:
What|Removed |Added
Assignee|b...@freebsd.org|k...@freebsd.org
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190787
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #7 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283747
--- Comment #4 from Matthew L. Dailey ---
I just had this happen this morning on two machines running 14.2-RELEASE. In
both cases, I had used pkg to upgrade telegraf from 1.32.3 to 1.33.0. After
restarting telegraf, both panicked.
Unfortun
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283747
--- Comment #5 from Matthew L. Dailey ---
Created attachment 256501
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256501&action=edit
Screenshot of panic
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283747
--- Comment #6 from Matthew L. Dailey ---
Created attachment 256502
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256502&action=edit
Telegraf config
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283747
--- Comment #7 from Matthew L. Dailey ---
I should also add that the two machines that panicked for us this morning were
both Intel, not AMD - Xeon Gold 5215 and Xeon E5-2650v3
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275086
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=254a2b767f9a39f1541e0a07a70bbe269e86ad70
commit 254a2b767f9a39f1541e0a07a70bbe269e86ad70
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275086
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275086
--- Comment #5 from Mark Johnston ---
(In reply to ben from comment #3)
Thanks for the analysis. I committed a modified version of the patch.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173301
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #4 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283909
Bug ID: 283909
Summary: bsnmpget/walk: coredump when SNMPPASSWD is empty
Product: Base System
Version: 13.3-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283815
--- Comment #7 from Anton Saietskii ---
(In reply to Konstantin Belousov from comment #6)
Thanks for prompt response.
I can confirm that with the patch applied, getting OID in question doesn't hang
anymore -- I can see 'dev.vgapci.0.%iommu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283818
--- Comment #1 from Zhenlei Huang ---
I think we should do sanity check within `rtnl_handle_getroute()`. Meanwhile we
can give netlink client a meaningful error message.
--
You are receiving this mail because:
You are the assignee for the
14 matches
Mail list logo
