From: Tejun Heo <htejun@gmail.com>
To: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.24.X: SATA/AHCI related boot delay.
Date: Mon, 10 Mar 2008 22:05:18 +0900 [thread overview]
Message-ID: <47D5320E.8020107@gmail.com> (raw)
In-Reply-To: <200803091922.33083.volker.armin.hemmann@tu-clausthal.de>
[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]
Volker Armin Hemmann wrote:
> Hi,
>
> I have an Alive -NF5-esata2+. AM2 board with dual core AMD64 cpu.
>
> Problem exists with latest bios 1.90 and its predecessor 1.80.
>
> This board with nforce 520 chipset (MCP65) has three possible settings for the
> sata controller:
> non-raid
> raid
> ahci.
>
> My default is non-raid.
>
> With 2.6.24 based kernels I get this on cold boot:
>
> [ 50.808824] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 80.743754] ata1.00: qc timeout (cmd 0xec)
> [ 80.743792] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Does "irqpoll" make any difference? Also, does the attached patch help?
> and this on reboots:
>
> [ 36.619135] ata1: port is slow to respond, please be patient (Status 0xd0)
> [ 40.982984] ata1: softreset failed (device not ready)
Is this consistent? Do you always get IDENTIFY timeout on cold boots
and softreset failure on reboots?
> with 2.6.23.11 it looks like this:
Hmmm...
> I removed the pata-disk and the drivers some days ago - but that has had no
> influence on the problem. The delay was there with the pata-drive and drivers
> too. There are some changes in the config - but even with the 2.6.3.11 config
> on a 2.6.24 and make oldconfig showed the delays.
>
> If I change from 'non raid' to AHCI (because the handbook says that is the way
> to get NCQ working) boot hangs for looong time and no harddisks are found:
> (dmesg from systemrescuecd 1.0)
> ahci 0000:00:0a.0: version 3.0
> ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LSA0] -> GSI 23 (level, low) ->
> IRQ 18
> ahci 0000:00:0a.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
> ahci 0000:00:0a.0: flags: 64bit sntf led clo pmp pio
> PCI: Setting latency timer of device 0000:00:0a.0 to 64
> scsi3 : ahci
> scsi4 : ahci
> scsi5 : ahci
> scsi6 : ahci
> ata1: SATA max UDMA/133 abar m8192@0xf9dfc000 port 0xf9dfc100 irq 218
> ata2: SATA max UDMA/133 abar m8192@0xf9dfc000 port 0xf9dfc180 irq 218
> ata3: SATA max UDMA/133 abar m8192@0xf9dfc000 port 0xf9dfc200 irq 218
> ata4: SATA max UDMA/133 abar m8192@0xf9dfc000 port 0xf9dfc280 irq 218
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> APIC error on CPU0: 00(40)
> scsi_scan_2 used greatest stack depth: 2868 bytes left
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: failed to recover some devices, retrying in 5 secs
This one definitely looks like a misrouted IRQ. irqpoll should help.
This failure is the same for 2.6.23 and 24, right?
--
tejun
[-- Attachment #2: debug --]
[-- Type: text/plain, Size: 506 bytes --]
---
drivers/ata/ahci.c | 1 +
1 file changed, 1 insertion(+)
Index: tree2/drivers/ata/ahci.c
===================================================================
--- tree2.orig/drivers/ata/ahci.c
+++ tree2/drivers/ata/ahci.c
@@ -397,6 +397,7 @@ static const struct ata_port_operations
static const struct ata_port_info ahci_port_info[] = {
/* board_ahci */
{
+ AHCI_HFLAGS (AHCI_HFLAG_NO_PMP),
.flags = AHCI_FLAG_COMMON,
.link_flags = AHCI_LFLAG_COMMON,
.pio_mask = 0x1f, /* pio0-4 */
next prev parent reply other threads:[~2008-03-10 13:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 18:22 2.6.24.X: SATA/AHCI related boot delay Volker Armin Hemmann
2008-03-10 13:05 ` Tejun Heo [this message]
2008-03-10 16:57 ` Volker Armin Hemmann
2008-03-16 8:34 ` Volker Armin Hemmann
2008-03-17 7:16 ` 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3 Volker Armin Hemmann
2008-03-18 7:36 ` Tejun Heo
2008-03-18 10:59 ` Volker Armin Hemmann
2008-03-18 12:56 ` Tejun Heo
2008-03-18 13:33 ` Volker Armin Hemmann
2008-03-19 3:26 ` Tejun Heo
2008-03-19 3:27 ` Tejun Heo
2008-03-19 7:53 ` Volker Armin Hemmann
2008-03-19 8:58 ` Tejun Heo
2008-03-19 10:08 ` Volker Armin Hemmann
2008-03-19 11:43 ` Tejun Heo
2008-03-19 13:55 ` Volker Armin Hemmann
2008-04-02 3:57 ` Tejun Heo
2008-04-02 17:09 ` Volker Armin Hemmann
2008-04-03 1:48 ` Tejun Heo
2008-04-03 5:04 ` Volker Armin Hemmann
2008-04-03 5:26 ` Tejun Heo
2008-04-03 11:47 ` Volker Armin Hemmann
2008-04-11 6:05 ` Tejun Heo
2008-04-11 11:55 ` Volker Armin Hemmann
2008-04-12 1:27 ` Tejun Heo
2008-04-12 1:42 ` Jeff Garzik
2008-04-14 4:02 ` Peer Chen
2008-04-14 6:41 ` Volker Armin Hemmann
2008-04-14 8:11 ` Peer Chen
2008-04-14 21:12 ` Volker Armin Hemmann
2008-04-15 12:57 ` Peer Chen
2008-04-15 16:20 ` Volker Armin Hemmann
2008-04-18 5:51 ` Peer Chen
2008-04-19 13:48 ` Volker Armin Hemmann
2008-04-22 10:10 ` Peer Chen
2008-04-22 12:44 ` Volker Armin Hemmann
2008-04-22 14:11 ` Tejun Heo
2008-04-22 15:12 ` Volker Armin Hemmann
2008-05-29 14:54 ` Hemmann, Volker Armin
2008-05-30 4:19 ` Tejun Heo
2008-05-30 10:43 ` Hemmann, Volker Armin
2008-05-31 0:49 ` Tejun Heo
2008-06-03 7:56 ` Peer Chen
2008-06-09 9:17 ` Tejun Heo
2008-06-09 9:43 ` Tejun Heo
2008-06-09 14:49 ` Hemmann, Volker Armin
2008-04-03 10:44 ` Peer Chen
2008-04-11 6:06 ` Tejun Heo
2008-04-11 9:50 ` Peer Chen
2008-04-11 11:46 ` Volker Armin Hemmann
2008-03-27 16:40 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47D5320E.8020107@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=volker.armin.hemmann@tu-clausthal.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).