Hi all,
the attached patch tries to fix SATA ATAPI error handling.
The original code invokes scsi_finish_command() regardless whether this
command is processed normally or by scsi_eh.
This looks quite dangerous to me as this might trigger a recovery for a
command which already is in recovery (as
This patch set default values for the FIFO PCI Bus Arbitration to avoid data
corruption. The root cause is due to our PCI bus master handling mismatch with
the chipset PCI bridge during DMA xfer (write data to the device). The patch is
to setup the DMA fifo threshold so that there is no chance
Carlos Pardo wrote:
This patch set default values for the FIFO PCI Bus Arbitration to avoid data
corruption. The root cause is due to our PCI bus master handling mismatch with
the chipset PCI bridge during DMA xfer (write data to the device). The patch is
to setup the DMA fifo threshold so that
Sorry I'm rather late to the Linux game. I have searched the archive for
references to csfo and cache but I have not found anything to explain
the issue I am looking at, though there are discussions in the immediate
area.
If I am referring to outdated information please let me know and I can
03_libata_rework-cc-generation.patch
This patch refactors the check condition creation within
libata. Changes include:
- ata_to_sense_error() now *only* performs the translation
from an ATA status/error register combination to a SCSI
SK/ASC/ASCQ
These patches are a resubmit of patch 5/5 of the first series
submitted 2005-03-17. Jeff requested that the single patch be split
into a suggested 3 smaller patches; the results are below. I also
took this opportunity to further clean up the changes.
[ Start of patch descriptions ]
Jeff,
This fixes the compile warning below:
drivers/scsi/ahci.c:199: warning: overflow in implicit constant
conversion
This has been sitting in my dir for a while now, sorry for not sending
it sooner. It turns out that moving the AHCI_DMA_BOUNDARY to the
*bottom* of the current enum also works,
