#
97ad52ca |
| 24-Jun-2019 |
Warner Losh <imp@FreeBSD.org> |
Use the cam_ed copy of ata_params rather than malloc and freeing memory for it. This reaches into internal bits of xpt a little, and I'll clean that up later.
|
#
2afaed2d |
| 24-Jun-2019 |
Warner Losh <imp@FreeBSD.org> |
Create ata_param_fixup
Create a common fixup routine to do the canonical fixup of the ata_param fixup. Call it from both the ATA and the ATA over SCSI paths.
|
#
7648bc9f |
| 13-May-2019 |
Alan Somers <asomers@FreeBSD.org> |
MFHead @347527
Sponsored by: The FreeBSD Foundation
|
#
5a9170aa |
| 22-Apr-2019 |
Alexander Motin <mav@FreeBSD.org> |
Report DIF protection type the disk is formatted with.
Some disks formatted with protection report errors if written without protection used. This should help to diagnose the problem.
MFC after: 2
Report DIF protection type the disk is formatted with.
Some disks formatted with protection report errors if written without protection used. This should help to diagnose the problem.
MFC after: 2 weeks
show more ...
|
#
2aaf9152 |
| 18-Mar-2019 |
Alan Somers <asomers@FreeBSD.org> |
MFHead@r345275
|
#
eb1761b0 |
| 11-Mar-2019 |
Enji Cooper <ngie@FreeBSD.org> |
MFhead@r345025
|
#
3899afd3 |
| 11-Mar-2019 |
Warner Losh <imp@FreeBSD.org> |
Upgrade Chipfancier SLC quirk to all versions
The 16GB, 32GB and 128GB versions of this product all have the same problem. For some reason, the RC10 size is correct, while the RC16 size is larger (o
Upgrade Chipfancier SLC quirk to all versions
The 16GB, 32GB and 128GB versions of this product all have the same problem. For some reason, the RC10 size is correct, while the RC16 size is larger (oddly by the capacity size / 1024 bytes). Using the RC16 size results in illegal LBA range errors when geom tastes the device. So, expand the quirk to cover all versions of this chip.
Ideally, we'd get both READ CAPACITY 10 and READ CAPACITY 16 sizes and print a warnnig if they differ and use the smaller of the two numbers, though that may be problematical as well. Furthermore, SBC-4 encourages users transition to RC16 only, which suggests that in the future RC10 may disappear from some drives. It's unclear how to cope with these drives generically.
PR: 234503 MFC After: 1 week
show more ...
|
#
9e43c218 |
| 10-Feb-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r343807 through r343955.
|
#
a49077d3 |
| 05-Feb-2019 |
Warner Losh <imp@FreeBSD.org> |
Add quirk for Sansisk X400 drives
Certain versions of Sandisk x400 firmware can hang under extremely heavly load of large I/Os for prolonged periods of time. Newer / current versions work fine, and
Add quirk for Sansisk X400 drives
Certain versions of Sandisk x400 firmware can hang under extremely heavly load of large I/Os for prolonged periods of time. Newer / current versions work fine, and should be used where possible. Where not possible, this quirk ensures that I/O requests are limited to 128k to avoids the bug, even under extreme load. Since MAXPHYS is 128k, only users with custom kernels are at risk on the older firmware. Once all known users of the older firmware have upgraded, this quirk will be removed.
Sponsored by: Netflix, Inc.
show more ...
|
#
c2c227a5 |
| 03-Feb-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r343571 through r343711.
|
#
441a6b69 |
| 30-Jan-2019 |
Alexander Motin <mav@FreeBSD.org> |
Remove stale now comment, forgotten in r343582.
MFC after: 2 weeks
|
#
a5fde7ef |
| 30-Jan-2019 |
Alexander Motin <mav@FreeBSD.org> |
Relax BIO_FLUSH ordering in da(4), respecting BIO_ORDERED.
r212160 tightened this from always using MSG_SIMPLE_Q_TAG to always MSG_ORDERED_Q_TAG. Since it also marked all BIO_FLUSH requests with BI
Relax BIO_FLUSH ordering in da(4), respecting BIO_ORDERED.
r212160 tightened this from always using MSG_SIMPLE_Q_TAG to always MSG_ORDERED_Q_TAG. Since it also marked all BIO_FLUSH requests with BIO_ORDERED, this commit changes nothing immediately, but it returns BIO_FLUSH callers ability to actually specify ordering they really need, alike to other request types.
MFC after: 2 weeks Sponsored by: iXsystems, Inc.
show more ...
|
#
7e565c55 |
| 30-Jan-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r343320 through r343570.
|
#
4dafe01e |
| 27-Jan-2019 |
Andriy Voskoboinyk <avos@FreeBSD.org> |
Add NO_6_BYTE / NO_SYNC_CACHE quirks for (C|D|E).* Olympus digital cameras
PR: 97472 Submitted by: Fabio Luis Girardi <papelhigienico@gmail.com> Reviewed by: imp MFC after: 3 weeks
|
#
3f41bec2 |
| 08-Jan-2019 |
Warner Losh <imp@FreeBSD.org> |
Add NO_SYNC_CACHE quirk for PENTAX cameras
PR: 93389 Submitted by: Demin Alexander
|
#
e11ed26a |
| 31-Dec-2018 |
Warner Losh <imp@FreeBSD.org> |
Add NO_RC16 quirk for Chipfancier 16GB USB stick...
Submitted by: osef.lar@gmail.com PR: 234503
|
#
5b7f9fad |
| 17-Dec-2018 |
Andriy Gapon <avg@FreeBSD.org> |
add a knob that disables detection of write protected disks
It has been reported that on some systems (with real hardware passed through to a virtual machine) the WP detection causes USB disk probin
add a knob that disables detection of write protected disks
It has been reported that on some systems (with real hardware passed through to a virtual machine) the WP detection causes USB disk probing failures.
While here, also fix the selection of the next state in the case of malloc failure in DA_STATE_PROBE_WP. It was DA_STATE_PROBE_RC unconditionally even when it should have been DA_STATE_PROBE_RC16.
PR: 225794 Reported by: David Boyd <David.Boyd49@twc.com> MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D18496
show more ...
|
#
67350cb5 |
| 09-Dec-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r340918 through r341763.
|
#
2e2b365e |
| 07-Dec-2018 |
Andriy Gapon <avg@FreeBSD.org> |
daprobedone: announce if a disk is write-protected
MFC after: 2 weeks
|
Revision tags: release/12.0.0 |
|
#
3d5db455 |
| 24-Nov-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r340427 through r340868.
|
#
ee7eba24 |
| 15-Nov-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove trailing white space in advance of other changes.
|
#
c06e7b66 |
| 07-Nov-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r340126 through r340212.
|
#
74c0112f |
| 05-Nov-2018 |
Warner Losh <imp@FreeBSD.org> |
Only assert locked for many async events.
Many async events that we see are called for this specific path. When calling an async callback for a targetted device, XTP will lock that specific device's
Only assert locked for many async events.
Many async events that we see are called for this specific path. When calling an async callback for a targetted device, XTP will lock that specific device's path lock (same as what cam_periph_lock does). For those AC_ events, assert we have the lock rather than trying to recusrively take it (which causes panics since it's not recursive).
Add annotations about this and about the fact that AC_SCSI_AEN events are generated now only in the ata stack (which cannot have a scsi_da attachment). Leave it in place in case I've overlooked something as the code is harmless.
This is fallout from my attempts to "fix" locking for softc->flags in r330796 that's not been triggered often enough to get my attention until now.
Sponsored by: Netflix MFC After: 3 days Differential Revision: https://reviews.freebsd.org/D17837
show more ...
|
#
2a22df74 |
| 04-Nov-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r339813 through r340125.
|
#
9385e92b |
| 01-Nov-2018 |
Warner Losh <imp@FreeBSD.org> |
Add comments explaining what hold/unhold do
They act as a simple one-deep semaphore to keep open/close/probe from running at the same time to avoid races that creates.
|