lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 3 Dec 2008 22:22:57 -0800
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.27 - swncq problem with nforce 570 and ST3320620AS?

I was receiving the { DRDY }
thing with some .config option
  from Some distro I was using,
Then revered to my f*^%ed
Up .config and all was good.
Try experimenting if this helps.

justin P. Mattock



On Dec 3, 2008, at 9:45 PM, Robert Hancock <hancockr@...w.ca> wrote:

> Jan De Luyck wrote:
>> Hello,
>> I switched not too long ago to 2.6.27-series, and since then I've  
>> been getting this now and then at bootup:
>> This was with 2.6.27.4, upgraded today to 2.6.27.7.
>> Disk in question is:
>> ATA device, with non-removable media
>>        Model Number:        
>> ST3320620AS                                   Serial Number:       
>> 9QF1QMGA
>>        Firmware Revision:  3.AAE   whocares kernel: ata4: EH in  
>> SWNCQ mode,QC:qc_active 0x6 sactive 0x6
>> whocares kernel: ata4: SWNCQ:qc_active 0x6 defer_bits 0x0  
>> last_issue_tag 0x2
>> whocares kernel:   dhfis 0x6 dmafis 0x2 sdbfis 0x0
>> whocares kernel: ata4: ATA_REG 0x40 ERR_REG 0x0
>> whocares kernel: ata4: tag : dhfis dmafis sdbfis sacitve
>> whocares kernel: ata4: tag 0x1: 1 1 0 1
>> whocares kernel: ata4: tag 0x2: 1 0 0 1
>> whocares kernel: ata4.00: exception Emask 0x0 SAct 0x6 SErr  
>> 0x1800000 action 0x6 frozen
>> whocares kernel: ata4: SError: { LinkSeq TrStaTrns }
>> whocares kernel: ata4.00: cmd 60/3e:08:61:00:00/00:00:00:00:00/40  
>> tag 1 ncq 31744 in
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 60/02:10:bf:d6:42/00:00:25:00:00/40  
>> tag 2 ncq 1024 in
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4: hard resetting link
>> whocares kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl  
>> 300)
>> whocares kernel: ata4.00: configured for UDMA/133
>> whocares kernel: ata4: EH complete
>> whocares kernel: sd 3:0:0:0: [sdd] 625142448 512-byte hardware  
>> sectors (320073 MB)
>> whocares kernel: sd 3:0:0:0: [sdd] Write Protect is off
>> whocares kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
>> whocares kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read  
>> cache: enabled, doesn't support DPO or FUA
>> ...
>> whocares kernel: XFS mounting filesystem sdd1
>> whocares kernel: ata4: EH in SWNCQ mode,QC:qc_active 0xF sactive 0xF
>> whocares kernel: ata4: SWNCQ:qc_active 0x1 defer_bits 0xE  
>> last_issue_tag 0x0
>> whocares kernel:   dhfis 0x1 dmafis 0x1 sdbfis 0x0
>> whocares kernel: ata4: ATA_REG 0x40 ERR_REG 0x0
>> whocares kernel: ata4: tag : dhfis dmafis sdbfis sacitve
>> whocares kernel: ata4: tag 0x0: 1 1 0 1
>> whocares kernel: ata4.00: exception Emask 0x0 SAct 0xf SErr  
>> 0x400000 action 0x6 frozen
>> whocares kernel: ata4: SError: { Handshk }
>> whocares kernel: ata4.00: cmd 61/00:00:9f:8d:a2/04:00:12:00:00/40  
>> tag 0 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/40  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 61/00:08:9f:91:a2/04:00:12:00:00/40  
>> tag 1 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 61/00:10:9f:95:a2/04:00:12:00:00/40  
>> tag 2 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 61/00:18:9f:99:a2/04:00:12:00:00/40  
>> tag 3 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4: hard resetting link
>> whocares kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl  
>> 300)
>> whocares kernel: ata4.00: configured for UDMA/133
>> whocares kernel: ata4: EH complete
>> whocares kernel: sd 3:0:0:0: [sdd] 625142448 512-byte hardware  
>> sectors (320073 MB)
>> whocares kernel: sd 3:0:0:0: [sdd] Write Protect is off
>> whocares kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
>> whocares kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read  
>> cache: enabled, doesn't support DPO or FUA
>> whocares kernel: ata4: EH in SWNCQ mode,QC:qc_active 0xF sactive 0xF
>> whocares kernel: ata4: SWNCQ:qc_active 0x1 defer_bits 0xE  
>> last_issue_tag 0x0
>> whocares kernel:   dhfis 0x1 dmafis 0x1 sdbfis 0x0
>> whocares kernel: ata4: ATA_REG 0x40 ERR_REG 0x0
>> whocares kernel: ata4: tag : dhfis dmafis sdbfis sacitve
>> whocares kernel: ata4: tag 0x0: 1 1 0 1
>> whocares kernel: ata4.00: exception Emask 0x0 SAct 0xf SErr  
>> 0x400000 action 0x6 frozen
>> whocares kernel: ata4: SError: { Handshk }
>> whocares kernel: ata4.00: cmd 61/00:00:9f:99:a2/04:00:12:00:00/40  
>> tag 0 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/40  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 61/00:08:9f:95:a2/04:00:12:00:00/40  
>> tag 1 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 61/00:10:9f:91:a2/04:00:12:00:00/40  
>> tag 2 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4.00: cmd 61/00:18:9f:8d:a2/04:00:12:00:00/40  
>> tag 3 ncq 524288 out
>> whocares kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00  
>> Emask 0x4 (timeout)
>> whocares kernel: ata4.00: status: { DRDY }
>> whocares kernel: ata4: hard resetting link
>> whocares kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl  
>> 300)
>> whocares kernel: ata4.00: configured for UDMA/133
>> whocares kernel: ata4: EH complete
>> whocares kernel: sd 3:0:0:0: [sdd] 625142448 512-byte hardware  
>> sectors (320073 MB)
>> whocares kernel: sd 3:0:0:0: [sdd] Write Protect is off
>> whocares kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
>> whocares kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read  
>> cache: enabled, doesn't support DPO or FUA
>> whocares kernel: Ending clean XFS mount for filesystem: sdd1
>> ...
>> Anyone any idea what might be causing this?
>> I have several disks of the same type in my PC, with different  
>> firmwares though - this is the only one exhibiting this problem.
>
> This fact and the fact that those SError bits are showing up does  
> potentially point to a hardware issue.. perhaps a problem with the  
> cable, or this drive is somehow getting worse power than the others?
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux- 
> kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ