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>] [day] [month] [year] [list]
Message-ID: <BANLkTiniZQovB6mYwfi4x1=JYuGMh1y6Cw@mail.gmail.com>
Date:	Fri, 6 May 2011 21:47:30 -0400
From:	Andrew Lutomirski <luto@....edu>
To:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: [2.6.39 regression] Cougar Point ahci COMRESET on boot

(This is only a regression in the sense that the bug exists in 2.6.38
but is much worse in 2.6.39-rc6.)

I have two Sandy Bridge / Cougar Point machines: one H67 desktop and
one QM67 laptop.  They have disks from different manufacturers.  Both
of them have trouble loading ahci on bootup.  On 2.6.38.5, the symptom
is that, on boot, the system waits 10 seconds or so, then generates a
COMRESET failed (errno=-16) error, then works.  On 2.6.39-rc6, it's
worse: it gives the COMRESET error three times and then brings up the
disk at 1.5Gbps.  That means that my bootup time goes from 10 seconds
or so on 2.6.38 to 56 seconds on 2.6.39-rc6.

On the desktop on 2.6.38, dmesg |egrep -i 'ata|ahci' says:

[    0.857245] libata version 3.00 loaded.
[    2.036680] ahci 0000:00:1f.2: version 3.0
[    2.036707] ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    2.036768] ahci 0000:00:1f.2: irq 44 for MSI/MSI-X
[    2.047240] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6
Gbps 0xd impl SATA mode
[    2.047245] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio
slum part ems apst
[    2.047252] ahci 0000:00:1f.2: setting latency timer to 64
[    2.052019] scsi0 : ahci
[    2.052135] scsi1 : ahci
[    2.052241] scsi2 : ahci
[    2.052329] scsi3 : ahci
[    2.052421] scsi4 : ahci
[    2.052509] scsi5 : ahci
[    2.052722] ata1: SATA max UDMA/133 abar m2048@...e625000 port
0xfe625100 irq 44
[    2.052724] ata2: DUMMY
[    2.052727] ata3: SATA max UDMA/133 abar m2048@...e625000 port
0xfe625200 irq 44
[    2.052731] ata4: SATA max UDMA/133 abar m2048@...e625000 port
0xfe625280 irq 44
[    2.052734] ata5: DUMMY
[    2.052735] ata6: DUMMY
[    2.357095] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.357125] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.358782] ata4.00: ATAPI: ATAPI   iHAS124   Y, BL0V, max UDMA/100
[    2.360261] ata3.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
[    2.360266] ata3.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth
31/32), AA
[    2.360706] ata4.00: configured for UDMA/100
[    2.363496] ata3.00: configured for UDMA/133
[    7.405154] ata1: link is slow to respond, please be patient (ready=0)
[   12.094412] ata1: COMRESET failed (errno=-16)
[   12.401242] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   12.514036] ata1.00: ATA-9: OCZ-VERTEX3, 2.02, max UDMA/133
[   12.514041] ata1.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[   12.665431] ata1.00: configured for UDMA/133
[   12.665585] scsi 0:0:0:0: Direct-Access     ATA      OCZ-VERTEX3
  2.02 PQ: 0 ANSI: 5
[   12.666026] scsi 2:0:0:0: Direct-Access     ATA      WDC
WD20EARS-00M 51.0 PQ: 0 ANSI: 5
[   12.667587] scsi 3:0:0:0: CD-ROM            ATAPI    iHAS124   Y
  BL0V PQ: 0 ANSI: 5

The laptop looks pretty much the same, as does 2.6.39-rc6.
--
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