Fajun Chen wrote:
The following problem was observed occasionally: the test program uses 99% of cpu and other programs slowed down dramatically: telnet session
How much is in user and how much is in kernel?
was very slow to respond, ip connection was almost time out... It seems the slowness was related to the dmesg traces below (just an observation which may not be true). Has anyone seen similar problem before? Is there any place or hot spot I should look closely? --------- ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/100 ata2: EH complete SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back ata1: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0x2 frozen ata1: (irq_stat 0x01100010, PHY RDY changed) ata1: waiting for device to spin up (8 secs) ata2: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0x2 frozen ata2: (irq_stat 0x01100010, PHY RDY changed) ata2: waiting for device to spin up (8 secs) ata1: soft resetting port ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete
PHY RDY changed on both ata1 and 2 meaning SATA connections are broken on both channels simultaneously. Was there anything special going on?
[--snip--]
ata2: exception Emask 0x10 SAct 0x0 SErr 0x40d0000 action 0x2 frozen ata2: (irq_stat 0x01100010, PHY RDY changed) ata2: waiting for device to spin up (8 secs) ata2: soft resetting port ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata2.00: configured for UDMA/100 ata2: EH complete
Another PHY RDY changed on ata2. This repeats a number of times. What's going on? How fast are these exceptions happening? Can you post long w/ timestamps?
SCSI device sdb: 1465149168 512-byte hdwr sectors (750156 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back ata2: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen ata2: (irq_stat 0x01100010, PHY RDY changed) ata2: soft resetting port ata2: SATA link down (SStatus 0 SControl 300) ata2: failed to recover some devices, retrying in 5 secs ata1: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen ata1: (irq_stat 0x01100010, PHY RDY changed) ata1: soft resetting port ata1: SATA link down (SStatus 0 SControl 300) ata1: failed to recover some devices, retrying in 5 secs ata2: hard resetting port ata2: SATA link down (SStatus 0 SControl 300) ata2: failed to recover some devices, retrying in 5 secs ata1: hard resetting port ata1: SATA link down (SStatus 0 SControl 300) ata1: failed to recover some devices, retrying in 5 secs ata2: hard resetting port ata2: SATA link down (SStatus 0 SControl 300) ata2.00: disabled sd 1:0:0:0: rejecting I/O to offline device ata2: EH complete ata2.00: detaching (SCSI 1:0:0:0) ata1: hard resetting port ata1: SATA link down (SStatus 0 SControl 300) ata1.00: disabled ata1: EH complete ata1.00: detaching (SCSI 0:0:0:0)
Another concurrent PHY RDY changed on ata1 and 2, and both drives decided not to respond this time. I'm really intrigued. Can you explain in deeper detail about the situation?
Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
