summaryrefslogtreecommitdiffstats
path: root/ObsoleteFiles.inc
diff options
context:
space:
mode:
authorrstone <rstone@FreeBSD.org>2012-09-25 19:12:12 +0000
committerrstone <rstone@FreeBSD.org>2012-09-25 19:12:12 +0000
commit95b43675385916a51b0631b412c1affc748126a0 (patch)
tree7e0d1e1097fc5ed201a3d7c3e4bf6fbd7ca2f71d /ObsoleteFiles.inc
parentcabd8b8de74ed56244621b305e859bf472197ae1 (diff)
downloadFreeBSD-src-95b43675385916a51b0631b412c1affc748126a0.zip
FreeBSD-src-95b43675385916a51b0631b412c1affc748126a0.tar.gz
Some aac(4) adapters will always report that a direct access device is
offline in response to a INQUIRY command that does not retreive vital product data(I personally have observed the behaviour on an Adaptec 2405 and a 5805). Force the peripheral qualifier to "connected" so that upper layers correctly recognize that a disk is present. This bug was uncovered by r216236. Prior to that fix, aac(4) was accidentally clearing the peripheral qualifier for all inquiry commands. This fixes an issue where passthrough devices were not created for disks behind aac(4) controllers suffering from the bug. I have verified that if a disk is not present that we still properly detect that and not create the passthrough device. Sponsored by: Sandvine Incorporated MFC after: 1 week
Diffstat (limited to 'ObsoleteFiles.inc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud