lkml.org 
[lkml]   [2010]   [Jan]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: [PATCH 2.6.32.3] ahci: AHCI and RAID mode SATA patch for Intel Cougar Point DeviceIDs
    From
    On Fri, Jan 15, 2010 at 3:43 PM, Krzysztof Halasa <khc@pm.waw.pl> wrote:
    > Robert Hancock <hancockrwd@gmail.com> writes:
    >
    >> It would be interesting to see what happens if you actually plug
    >> something into that port that's having the issues, and see what
    >> happens. I'm kind of inclined to suspect it's a hardware fault, though
    >> it would likely require a report from someone else with the same or
    >> similar board model to confirm that..
    >
    > 2.6.32.3 with the patch disabling JMB363 and "catch all AHCI" applied.
    > Nothing connected to SATA, only PATA in use.
    >
    > I understand the following doesn't set the AHCI_HFLAG_IGN_IRQ_IF_ERR
    > and thus doesn't ignore PORT_IRQ_IF_ERR, but the latter doesn't seem to
    > be set.
    >
    > # echo -n 197b 2363 > new_id
    >
    > ahci 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    > ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
    > ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part
    > ahci 0000:02:00.0: setting latency timer to 64
    > scsi9 : ahci
    > scsi10 : ahci
    > ata9: SATA max UDMA/133 abar m8192@0xfe9fe000 port 0xfe9fe100 irq 16
    > ata10: SATA max UDMA/133 abar m8192@0xfe9fe000 port 0xfe9fe180 irq 16
    > ata10: SATA link down (SStatus 0 SControl 300)
    > ata9: SATA link down (SStatus 0 SControl 300)
    >
    > ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    > ata10: irq_stat 0x00000040, connection status changed
    > ata10: SError: { CommWake DevExch }
    > ata10: hard resetting link
    > ata10: SATA link down (SStatus 0 SControl 300)
    > ata10: EH complete
    > ata10: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    > ata10: irq_stat 0x00000040, connection status changed
    > ata10: SError: { CommWake DevExch }
    > ata10: limiting SATA link speed to 1.5 Gbps
    > ata10: hard resetting link
    > ata10: SATA link down (SStatus 0 SControl 310)
    > ata10: EH complete
    > ...
    >
    > sometimes the two lines become:
    >
    > ata10: exception Emask 0x10 SAct 0x0 SErr 0x4060000 action 0xe frozen
    > ata10: SError: { PHYInt CommWake DevExch }
    >
    > Now plugging something into the mb connector (1.5 Gbps device, the same
    > which my VT6421A-based miniPCI card doesn't like):
    >
    > ata10: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
    > ata10: irq_stat 0x00400040, connection status changed
    > ata10: SError: { PHYRdyChg CommWake DevExch }
    > ata10: hard resetting link
    > ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    > ata10.00: ATA-7: Kingston SSDNow V Series 64GB, B090428a, max UDMA/100
    > ata10.00: 125045424 sectors, multi 1: LBA
    > ata10.00: configured for UDMA/100
    > ata10: EH complete
    > scsi 10:0:0:0: Direct-Access     ATA      Kingston SSDNow  B090 PQ: 0 ANSI: 5
    > sd 10:0:0:0: Attached scsi generic sg8 type 0
    > sd 10:0:0:0: [sdh] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
    > sd 10:0:0:0: [sdh] Write Protect is off
    > sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00
    > sd 10:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    > sd 10:0:0:0: [sdh] Attached SCSI disk
    >
    > Absolutely no problems with fs access, expected linear transfer speed
    > etc.
    >
    > Well, let's unplug it. Power down first:
    >
    > ata10: exception Emask 0x10 SAct 0x0 SErr 0x990000 action 0xe frozen
    > ata10: irq_stat 0x00400000, PHY RDY changed
    > ata10: SError: { PHYRdyChg 10B8B Dispar LinkSeq }
    > ata10: hard resetting link
    > ata10: SATA link down (SStatus 0 SControl 300)
    > ata10: hard resetting link
    > ata10: SATA link down (SStatus 0 SControl 300)
    > ata10: limiting SATA link speed to 1.5 Gbps
    > ata10: hard resetting link
    > ata10: SATA link down (SStatus 0 SControl 310)
    > ata10.00: disabled
    > ata10: EH complete
    > ata10.00: detaching (SCSI 10:0:0:0)
    > sd 10:0:0:0: [sdh] Stopping disk
    > sd 10:0:0:0: [sdh] START_STOP FAILED
    > sd 10:0:0:0: [sdh] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
    >
    > Seems stable at this point, no additional messages.
    >
    > Then removing the plug from (unpowered) SSD - IRQs start appearing again
    > every few seconds. Mostly:
    >
    > ata10: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen
    > ata10: irq_stat 0x00000040, connection status changed
    > ata10: SError: { DevExch }
    > ata10: limiting SATA link speed to 1.5 Gbps
    > ata10: hard resetting link
    > ata10: SATA link down (SStatus 0 SControl 310)
    > ata10: EH complete
    >
    > sometimes SErr 0x4060000 and 0x4040000
    >
    > Fine, so let's connect it again (device still not powered):
    > Messages stopped.
    >
    > Disconnected again, messages started, reconnected, stopped.
    >
    > Am I to use the SSD as a passive SATA terminator?
    >
    > Any further ideas welcome :-)

    Hmm.. From those test results I really suspect some kind of hardware
    fault. Could be a defective motherboard - I don't know if that chip
    needs any terminating resistors on the motherboard for the SATA signal
    lines or something, if so, could be they weren't installed properly..
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2010-01-16 02:41    [W:0.029 / U:95.628 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site