mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Malte Schröder" <maltesch@gmx.de>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: [FIXED] Re: kernel 2.6.24{,.1} ahci problem, does not boot
Date: Sun, 17 Feb 2008 18:49:10 +0100	[thread overview]
Message-ID: <20080217184910.2e0b5da1@highlander.home.lan> (raw)
In-Reply-To: <20080209133021.45377af4@highlander.home.lan>

[-- Attachment #1: Type: text/plain, Size: 2682 bytes --]

Okay, I updated the BIOS and the problem disappeared. The mainboard is
an Asus M2R32-MVP by the way.


On Sat, 9 Feb 2008 13:30:21 +0100
Malte Schröder <maltesch@gmx.de> 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).
> 
> I hope someone can help ...
> 
> Regards


-- 
---------------------------------------
Malte Schröder
MalteSch@gmx.de
ICQ# 68121508
---------------------------------------


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-02-17 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09 12:30 Malte Schröder
2008-02-17 17:49 ` Malte Schröder [this message]

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=20080217184910.2e0b5da1@highlander.home.lan \
    --to=maltesch@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®