Date: Mon, 13 Apr 2020 23:04:08 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229745] ahcich: CAM status: Command timeout Message-ID: <bug-229745-227-xyM7VhVZeI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229745-227@https.bugs.freebsd.org/bugzilla/> References: <bug-229745-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745 --- Comment #44 from Warner Losh <imp@FreeBSD.org> --- (In reply to Wayne Willcox from comment #42) I ask because we have many thousands of machines deployed, and a thousand or so of those have intermittent power supply issues which means at any time we have a hundred or two machines that drop connections from time to time and a couple dozen that do it consistently... But there it's not a timeout, but the PHY goes down or we get some other signal from the drive that there's been trouble. However, having said that, we should instrument the code that does that, and maybe look at improving 'recovery' operations in the face of a timeout to see if there are things we can do to 'wakeup' a drive that's otherwise stopped responding to commands. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229745-227-xyM7VhVZeI>