linux-kernel - Re: 2.6.24.X: SATA/AHCI related boot delay.

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]

Message-ID: <47E0FC47.8040902@gmail.com>
Date:	Wed, 19 Mar 2008 20:43:03 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Volker Armin Hemmann <volker.armin.hemmann@...clausthal.de>
CC:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3

Volker Armin Hemmann wrote:
> On Mittwoch, 19. März 2008, Tejun Heo wrote:
>> x UDMA/133 abar m8192@...9dfc000 port 0xf9dfc200
>>
>>> irq 315
>>> [   38.125479] ata4: SATA max UDMA/133 abar m8192@...9dfc000 port
>>> 0xf9dfc280 irq 315
>>> [   38.597035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>> [   38.597732] ata1.00: ATA-7: WDC WD1600JS-00MHB1, 10.02E01, max
>>> UDMA/133 [   38.597775] ata1.00: 312581808 sectors, multi 16: LBA48
>>> [   38.598405] ata1.00: configured for UDMA/133
>>> [   39.069342] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>> [   39.084225] ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-12, max UDMA7
>>> [   39.084264] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth
>>> 0/32) [   39.086268] ata2.00: configured for UDMA/133
>> So, just to confirm.  With the updated patch, you don't see any problem,
>> right?
> 
> Correct. With the updated patch I don't see problems in 'non-raid' mode. AHCI 
> mode still has problems without nosmi. But that is an entirely different 
> problem, right?

Yeap, can you please post the result of "lspci -nn"?

-- 
tejun
--
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/