[Bug 229745] ahcich: CAM status: Command timeout

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Apr 13 18:57:35 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745

--- Comment #43 from Daniel Bell <daniel at belltech.it> ---
(In reply to sec from comment #38)

I'm sorry I didn't respond sooner, but for my issue, sec was 100% right: a cold
power cycle, as bizarre as that sounded to me, along with the loader.conf
tweaks mentioned elsewhere, completely solved my problem despite having the
problematic drive/controller combo here. Reboots after editing loader.conf did
not help, which is why I originally replied here.

As of today, the box in question has been up 60 days with zero errors, zero
problems, and a healthy IO load—multiple VMs including Windows VMs, multiple
active jails and database engines. I'm no longer planning to add a friendlier
HBA unless something changes.

I realize this isn't solving everyone's problem, but I thought I should mention
this worked for me.

% uname -a
FreeBSD wyn2018.office.wynnecap.com 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2
GENERIC  amd64
% uptime
 2:47PM  up 60 days, 23:45, 1 user, load averages: 0.29, 0.67, 0.76
% dmesg | grep DRDY || echo Groovy.
Groovy.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list