Neil Schemenauer wrote:
Not sure if this helps. I'm getting this reset with 2.6.21-rc4.
After the reset the controller seems to work again.
...
ata2.00: ATA-7: Maxtor 6V300F0, VA111630, max UDMA/133
ata2.00: 586114704 sectors, multi 16: LBA48 NCQ (depth 31/32)
...
ata2: EH in ADMA mode, n
Not sure if this helps. I'm getting this reset with 2.6.21-rc4.
After the reset the controller seems to work again.
sata_nv :00:07.0: version 3.3
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 22
ACPI: PCI Interrupt :00:07.0[A] -> Link [APSI] -> GSI 22 (level, low) ->
IRQ 22
sata_nv
Jeff Garzik wrote:
Robert Hancock wrote:
It's curious that only the post-cache-flush command is having issues,
and normal NCQ operation seems fine. Maybe it's related to that tag 0
being reused repeatedly?
If you take cache flush out of the equation, what happens when NCQ is
enabled with a q
Robert Hancock wrote:
It's curious that only the post-cache-flush command is having issues,
and normal NCQ operation seems fine. Maybe it's related to that tag 0
being reused repeatedly?
If you take cache flush out of the equation, what happens when NCQ is
enabled with a queue depth of 1 (to
While testing out some libata FUA changes I was working on, I was
inadvertently able to reproduce the kind of NCQ command timeouts in
sata_nv that a few people have reported. I since verified that the FUA
stuff had nothing to do with it as it still happens even with FUA
disabled. However I'm so
5 matches
Mail list logo
