From owner-freebsd-ports-bugs@freebsd.org Thu May 2 03:39:00 2019 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66564158711D for ; Thu, 2 May 2019 03:39:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F3A5573056 for ; Thu, 2 May 2019 03:38:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B6F16158711C; Thu, 2 May 2019 03:38:59 +0000 (UTC) Delivered-To: ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94855158711B for ; Thu, 2 May 2019 03:38:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 182AB73055 for ; Thu, 2 May 2019 03:38:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 46A7D1CA12 for ; Thu, 2 May 2019 03:38:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x423cw4D090526 for ; Thu, 2 May 2019 03:38:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x423cwJw090525 for ports-bugs@FreeBSD.org; Thu, 2 May 2019 03:38:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 237701] sysutils/smartmontools: Causing controller resets Date: Thu, 02 May 2019 03:38:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: danmcgrath.ca@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 May 2019 03:39:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237701 Bug ID: 237701 Summary: sysutils/smartmontools: Causing controller resets Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: danmcgrath.ca@gmail.com CC: samm@os2.kiev.ua Flags: maintainer-feedback?(samm@os2.kiev.ua) CC: samm@os2.kiev.ua After updating to 2019Q2 (v7.0), I noticed that a pair of Dell PowerEdge 41= 0's that have smartd running, not start adding some smartctl status to the daily logs. Unfortunately, it also seems like that are generating a bunch of dmesg errors recently too: -- +[6527952] mpt0: request 0xfffffe00012a2610:49251 timed out for ccb 0xfffff8074e2ea000 (req->ccb 0xfffff8074e2ea000) +[6527952] mpt0: attempting to abort req 0xfffffe00012a2610:49251 function 0 +[6527952] mpt0: request 0xfffffe00012a5888:49256 timed out for ccb 0xfffff800133f2800 (req->ccb 0xfffff800133f2800) +[6527952] mpt0: request 0xfffffe00012b0d08:49257 timed out for ccb 0xfffff80013452000 (req->ccb 0xfffff80013452000) +[6527952] mpt0: request 0xfffffe00012aeb30:49262 timed out for ccb 0xfffff802a97d2000 (req->ccb 0xfffff802a97d2000) +[6527953] mpt0: mpt_wait_req(1) timed out +[6527953] mpt0: mpt_recover_commands: abort timed-out. Resetting controller +[6527953] mpt0: EvtLogData: IOCLogInfo: 0x00000000 +[6527953] mpt0: EvtLogData: Event Data: +[6527953] mpt0: mpt_cam_event: 0x1 +[6527953] mpt0: completing timedout/aborted req 0xfffffe00012a2610:49251 +[6527953] mpt0: completing timedout/aborted req 0xfffffe00012a5888:49256 +[6527953] mpt0: completing timedout/aborted req 0xfffffe00012b0d08:49257 +[6527953] mpt0: completing timedout/aborted req 0xfffffe00012aeb30:49262 --- Smart itself shows: SMART overall-health self-assessment test result: PASSED but there is an error in the output: Read SMART Thresholds failed: Input/output error I can only assume that whatever it is that is running to add the info to the daily report is querying the system in a way that appears to possibly be resetting the disk controller. Any ideas or suggestions? Thought that I would point it out in case you wer= en't aware of the new change affecting older systems. --=20 You are receiving this mail because: You are the assignee for the bug.=