From: Tejun Heo <htejun@gmail.com>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Regression: kernel 2.6.24{,.1} ahci problem, does not boot (resend)
Date: Fri, 15 Feb 2008 08:35:10 +0900 [thread overview]
Message-ID: <47B4D02E.9030101@gmail.com> (raw)
In-Reply-To: <20080214184700.0bd3837d@highlander.home.lan>
Malte Schröder wrote:
> Hello,
> on one of my machines neither 2.6.24 nor 2.6.24.1 work.
> The system is 64bit on Athlon X2 and ATI-Chipset (SB600).
>
> Extract from the kernel messages during boot:
>
> [ 66.943103] ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
> [ 66.950374] ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP
> [ 67.956470] ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
> [ 67.964996] ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pio slum part
> [ 67.972820] scsi0 : ahci
> [ 67.975699] scsi1 : ahci
> [ 67.978445] scsi2 : ahci
> [ 67.981178] scsi3 : ahci
> [ 67.983949] ata1: SATA max UDMA/133 abar m1024@0xfadffc00 port 0xfadffd00 irq 509
> [ 67.991825] ata2: SATA max UDMA/133 abar m1024@0xfadffc00 port 0xfadffd80 irq 509
> [ 67.999729] ata3: SATA max UDMA/133 abar m1024@0xfadffc00 port 0xfadffe00 irq 509
> [ 68.007619] ata4: SATA max UDMA/133 abar m1024@0xfadffc00 port 0xfadffe80 irq 509
> [ 68.470669] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 98.431945] ata1.00: qc timeout (cmd 0xec)
> [ 98.454907] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> [ 98.461296] ata1: failed to recover some devices, retrying in 5 secs
> [ 103.916773] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 133.878045] ata1.00: qc timeout (cmd 0xec)
> [ 133.882371] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> [ 133.888797] ata1: failed to recover some devices, retrying in 5 secs
> [ 139.343901] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 169.305174] ata1.00: qc timeout (cmd 0xec)
> [ 169.309534] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> [ 169.315926] ata1: failed to recover some devices, retrying in 5 secs
> [ 174.771030] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>
> The complete boot-log (captured via serial console), lspci output,
> output of hdparm -I and the kernel config are attached.
>
> The PC has one IDE-drive and four SATA-drives (see hdparm.txt).
> If I wait long enough, the IDE-drive get's recognized and I can
> continue the boot process, but the SATA-drives are never recognized.
> The system work's fine with kernel 2.6.23.11 (later kernels not tested).
Does irqpoll kernel parameter help?
--
tejun
next prev parent reply other threads:[~2008-02-14 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 17:47 Regression: kernel 2.6.24{,.1} ahci problem, does not boot (resend) Malte Schröder
2008-02-14 23:35 ` Tejun Heo [this message]
2008-02-15 18:12 ` Malte Schröder
2008-02-21 2:51 ` Tejun Heo
2008-02-21 16:27 ` Malte Schröder
2008-03-17 21:00 ` Jan Kasprzak
2008-03-18 14:01 ` Jan Kasprzak
2008-03-19 3:24 ` Tejun Heo
2008-03-19 6:19 ` Jan Kasprzak
2008-03-19 6:36 ` Tejun Heo
2008-03-21 16:43 ` Jan Kasprzak
2008-03-22 8:13 ` Tejun Heo
2008-03-22 8:14 ` Tejun Heo
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=47B4D02E.9030101@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maltesch@gmx.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).