From owner-freebsd-bugs@FreeBSD.ORG  Thu Nov 27 19:08:26 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8F663D3F
 for <freebsd-bugs@FreeBSD.org>; Thu, 27 Nov 2014 19:08:26 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 77073F46
 for <freebsd-bugs@FreeBSD.org>; Thu, 27 Nov 2014 19:08:26 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sARJ8Qlk016665
 for <freebsd-bugs@FreeBSD.org>; Thu, 27 Nov 2014 19:08:26 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194522] smartmontools misbehaving (self-test timestamps do not
 match reality)
Date: Thu, 27 Nov 2014 19:08:26 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jdc@koitsu.org
X-Bugzilla-Status: Open
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status resolution
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Nov 2014 19:08:26 -0000

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.