From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Ayan Kumar Halder <ayan.kumar.halder@xilinx.com>,
linux-ide@vger.kernel.org
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
Stefano Stabellini <sstabellini@kernel.org>,
Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: Need help to debug ata errors
Date: Mon, 6 Dec 2021 09:12:50 +0900 [thread overview]
Message-ID: <022c3fad-ca0b-50c9-79f7-2bfa3de75a0d@opensource.wdc.com> (raw)
In-Reply-To: <df61e958-7bd6-94df-0da2-56aa1084350d@xilinx.com>
On 2021/12/03 20:11, Ayan Kumar Halder wrote:
> Hi All,
>
> I am trying to run linux as a DomU guest on Xen with AHCI assigned to it.
> I can confirm that SATA works (ie able to detect sdb) as a Dom0 guest.
> However, it does not work as a DomU guest.
>
> Hardware :- ZCU102 board and it has two sata ports
> Kernel :- 5.10
>
> I have enabled the debug logs in drivers/ata
>
> 1. Logs from dom0 (where SATA works) https://pastebin.com/2BhMDq47
> 2. Logs from domU (where SATA does not work) https://pastebin.com/fE8WZnZ0
>
> Can some help me to answer these questions
> 1. What does this mean "1st FIS failed" ?
>
> 2. In the dom0 logs, PORT_SCR_ERR = 0x41d0002 whereas in domU logs,
> PORT_SCR_ERR = 0. Does it give some hints ?
>
> 3. Any other issues or hints to debug this ?
>
> I can confirm that in domU scenario, we do not get any interrupts from
> the device. What might be going wrong here ?
That would be the first thing to check since without interrupts you will not get
any command completion. Commands will timeout and probe will not work.
And this IRQ problem is Xen territory, not ata.
The 1st FIS failed error may be due to some problems with AHCI PCI bar/register
accesses, which may not be working. This I think points again to Xen setup with
domU, which may not have the necessary access rights to get IRQ and PCI bar
accesses ? (I have no experience with Xen)
>
> Thanks in advance.
>
> Kind regards,
> Ayan
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2021-12-06 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 11:11 Need help to debug ata errors Ayan Kumar Halder
2021-12-06 0:12 ` Damien Le Moal [this message]
2021-12-06 11:18 ` Ayan Kumar Halder
2021-12-06 11:57 ` Damien Le Moal
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=022c3fad-ca0b-50c9-79f7-2bfa3de75a0d@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=axboe@kernel.dk \
--cc=ayan.kumar.halder@xilinx.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@xilinx.com \
/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).