Date: Fri, 12 Apr 2024 18:22:36 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 278311] amdtemp: Does not recognize AMD Threadripper 7960X Message-ID: <bug-278311-227-Izy8OMPJKK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-278311-227@https.bugs.freebsd.org/bugzilla/> References: <bug-278311-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278311 --- Comment #11 from Xin LI <delphij@FreeBSD.org> --- (In reply to Joel Bodenmann from comment #10) > could you elaborate what kind of information would show up in dmesg that = would be considered sensitive? Well, I'm just trying to remind you that you should filter out what _you_ w= ould consider sensitive, as the kernel message buffer (`dmseg`) could contain a = lot of things, because bugzilla data is generally accessible by anyone. Example of "sensitive data" can include e.g. build host name, ethernet addr= ess, hard drive serial number, file system mounted, etc. Some people feel uncomfortable to share some of these information with the Internet, which is totally understandable and should always be respected, and usually these PI= Is are not useful for debugging anyways (but information like the which other drivers were loaded, or e.g. what drivers said without indicating them in t= he same line, especially in verbose boot, are very important for debugging, so= I generally attach a full dmesg output when reporting driver issues with only minimal redaction). --=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-278311-227-Izy8OMPJKK>