From: Robert Hancock <hancockr@shaw.ca>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help interpreting AHCI failure messages
Date: Fri, 12 Dec 2008 21:52:28 -0600 [thread overview]
Message-ID: <4943317C.8000807@shaw.ca> (raw)
In-Reply-To: <4942D651.1050306@goop.org>
Jeremy Fitzhardinge wrote:
> Hi,
>
> I'm trying to bring up the AHCI driver on a Xen dom0 kernel. There's
> almost certainly some problem with my DMA handling somewhere - or
> perhaps interrupt routing - which is causing the AHCI driver to fail thus:
>
> xen_set_ioapic_routing: irq 31 gsi 18 vector 184 ioapic 0 pin 18
> triggering 0 polarity 1ahci 0000:00:1f.2: PCI INT C -> GSI 18 (level,
> low) -> IRQ 31
> xen: PCI device 0000:00:1f.2 pin 3 -> irq 31
> ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x27 impl SATA
> mode
> ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pmp pio slum part ems
> scsi0 : ahci
> scsi1 : ahci
> scsi2 : ahci
> scsi3 : ahci
> scsi4 : ahci
> scsi5 : ahci
> ata1: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970100 irq 31
> ata2: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970180 irq 31
> ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 31
> ata4: DUMMY
> ata5: DUMMY
> ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 31
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2.00: ATAPI: HL-DT-ST DVD+/-RW GSA-H73N, B103, max UDMA/100
> ata2.00: configured for UDMA/100
> ata3: SATA link down (SStatus 4 SControl 300)
> ata6: SATA link down (SStatus 4 SControl 300)
> scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+-RW GSA-H73N B103 PQ: 0
> ANSI: 5
> sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> sr 1:0:0:0: Attached scsi generic sg0 type 5
>
>
> I'm wondering if you can give me a clue as to what might be failing on
> the AHCI side to give these symptoms, so I have some idea where I need
> to fix things in my code?
The timeouts would tend to suggest interrupts aren't getting through,
you can check /proc/interrupts and see if that IRQ has gotten any
interrupts at all..
WARNING: multiple messages have this Message-ID (diff)
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Cc: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Help interpreting AHCI failure messages
Date: Fri, 12 Dec 2008 21:52:28 -0600 [thread overview]
Message-ID: <4943317C.8000807@shaw.ca> (raw)
In-Reply-To: <4942D651.1050306@goop.org>
Jeremy Fitzhardinge wrote:
> Hi,
>
> I'm trying to bring up the AHCI driver on a Xen dom0 kernel. There's
> almost certainly some problem with my DMA handling somewhere - or
> perhaps interrupt routing - which is causing the AHCI driver to fail thus:
>
> xen_set_ioapic_routing: irq 31 gsi 18 vector 184 ioapic 0 pin 18
> triggering 0 polarity 1ahci 0000:00:1f.2: PCI INT C -> GSI 18 (level,
> low) -> IRQ 31
> xen: PCI device 0000:00:1f.2 pin 3 -> irq 31
> ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x27 impl SATA
> mode
> ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pmp pio slum part ems
> scsi0 : ahci
> scsi1 : ahci
> scsi2 : ahci
> scsi3 : ahci
> scsi4 : ahci
> scsi5 : ahci
> ata1: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970100 irq 31
> ata2: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970180 irq 31
> ata3: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970200 irq 31
> ata4: DUMMY
> ata5: DUMMY
> ata6: SATA max UDMA/133 abar m2048@0xff970000 port 0xff970380 irq 31
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: qc timeout (cmd 0xec)
> ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata2.00: ATAPI: HL-DT-ST DVD+/-RW GSA-H73N, B103, max UDMA/100
> ata2.00: configured for UDMA/100
> ata3: SATA link down (SStatus 4 SControl 300)
> ata6: SATA link down (SStatus 4 SControl 300)
> scsi 1:0:0:0: CD-ROM HL-DT-ST DVD+-RW GSA-H73N B103 PQ: 0
> ANSI: 5
> sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> sr 1:0:0:0: Attached scsi generic sg0 type 5
>
>
> I'm wondering if you can give me a clue as to what might be failing on
> the AHCI side to give these symptoms, so I have some idea where I need
> to fix things in my code?
The timeouts would tend to suggest interrupts aren't getting through,
you can check /proc/interrupts and see if that IRQ has gotten any
interrupts at all..
next prev parent reply other threads:[~2008-12-13 3:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 21:23 Help interpreting AHCI failure messages Jeremy Fitzhardinge
2008-12-13 3:52 ` Robert Hancock [this message]
2008-12-13 3:52 ` Robert Hancock
[not found] ` <49434EC9.4070408@goop.org>
[not found] ` <49446DD0.3030600@gmail.com>
2008-12-19 16:30 ` Jeremy Fitzhardinge
2008-12-22 4:05 ` Tejun Heo
2008-12-22 9:17 ` Andrew Lyon
2008-12-22 9:17 ` Andrew Lyon
2008-12-22 9:54 ` Tejun Heo
2008-12-22 18:52 ` Andrew Lyon
2008-12-22 19:56 ` Boris Derzhavets
2008-12-22 20:02 ` Boris Derzhavets
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=4943317C.8000807@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.