https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224496
--- Comment #47 from elij <elij+free...@wundrd.net> ---
I have a SAS9305-16i, and was seeing similar errors to some of the folks here.
The comment about NCQ got me thinking, and sure enough.. looks like broadcom
had a new firmware out (I had 16.00.11.00 where I saw the errors).
16.00.12.00 has these two as the fixed "defect list":
ID:
DCSG00398894
Headline: SATA only:
WRITE SAME NCQ encapsulation assumes NonData NCQ is supported if Zero
EXT is Supported
Description Of Change:
Disable NCQ encapsulation if Zero EXT is supported but Non Data NCQ is
not supported
Issue Description:
In case if Zero EXT is supported but Non Data NCQ is not supported by
drive, WRITE SAME NCQ encapsulation would send Non Data NCQ command to
the drive.
Drive would fail the command as Non Data NCQ is not supported by drive.
This will cause command failure to host.
Steps To Reproduce:
IO errors are observed when mkfs.ext4 operation is done on drives that
support Zero EXT but do not support Non Data NCQ.
ID:
DCSG00411882 (Port Of Defect DCSG00139294)
Headline:
SATA only : Controller hang is observed due to recursive function call.
Description Of Change:
Avoid starting of pended commands to SATA drive from completion
functions of a command to avoid recursion.
Issue Description:
Controller hang is observed with ATA pass through command followed by a
pended command that fails.
At the completion of pass through command, PL starts the pended IOs if
any.
If the pended IO is failed due to invalid CDB, then immediately
completion function is called causing recursion. This causes controller
hang.
Steps To Reproduce:
Install the FreeNAS and try to create ZFS pool(Storage -> Pools -> Add)
of the direct attached SSDs.
- ATA command completes when there are IOs in pendlist.
- The pended IO has invalid CDB
I have installed the firmware, and am keeping an eye on it. My system is
lightly loaded though, so my sightings of the issue have been rather spurious.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
