Date: Thu, 27 Nov 2014 19:08:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194522] smartmontools misbehaving (self-test timestamps do not match reality) Message-ID: <bug-194522-8-avuzC3lR5B@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194522-8@https.bugs.freebsd.org/bugzilla/> References: <bug-194522-8@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=194522 Jeremy Chadwick <jdc@koitsu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Closed |Open Resolution|Overcome By Events |--- --- Comment #3 from Jeremy Chadwick <jdc@koitsu.org> --- Reopening -- this issue has returned. Again to recap: rebooting (not power-cycling) the system into Linux alleviates the problem, but it appears again once FreeBSD is running. So the issue does appear specific to FreeBSD, and is affecting all drives of different versions/models so it isn't a drive-firmware-specific thing. My gut feeling is that one of these commits is responsible for the problem, particularly r249850, but I have no actual proof/evidence to back that up, it's purely speculation on my part. http://www.freshbsd.org/commit/freebsd/r249850 http://www.freshbsd.org/commit/freebsd/r251874 http://www.freshbsd.org/commit/freebsd/r251897 Can someone CC mav@ on this ticket? I'd like to get his insights into this. -- 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-194522-8-avuzC3lR5B>