All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: Stefano Stabellini <sstabellini@kernel.org>,
	boris.ostrovsky@oracle.com, jgross@suse.com
Cc: Peng Fan <peng.fan@nxp.com>, "minyard@acm.org" <minyard@acm.org>,
	roman@zededa.com,
	"jeff.kubascik@dornerworks.com" <jeff.kubascik@dornerworks.com>,
	Julien Grall <julien.grall@arm.com>,
	Nataliya Korovkina <malus.brandywine@gmail.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Stefano Stabellini <stefano.stabellini@xilinx.com>
Subject: Re: Troubles running Xen on Raspberry Pi 4 with 5.6.1 DomU
Date: Wed, 13 May 2020 11:11:17 +0100	[thread overview]
Message-ID: <42253259-9663-67e8-117f-8ba631243585@xen.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2005121723240.26167@sstabellini-ThinkPad-T480s>

Hi,

On 13/05/2020 01:33, Stefano Stabellini wrote:
> I worked with Roman to do several more tests and here is an update on
> the situation. We don't know why my patch didn't work when Boris' patch
> [1] worked.  Both of them should have worked the same way.
> 
> Anyway, we continued with Boris patch to debug the new mmc error which
> looks like this:
> 
> [    3.084464] mmc0: unrecognised SCR structure version 15
> [    3.089176] mmc0: error -22 whilst initialising SD card
> 
> I asked to add a lot of trancing, see attached diff.

Please avoid attachment on mailing list and use pastebin for diff.

> We discovered a bug
> in xen_swiotlb_init: if io_tlb_start != 0 at the beginning of
> xen_swiotlb_init, start_dma_addr is not set correctly. This oneline
> patch fixes it:
> 
> diff --git a/drivers/xen/swiotlb-xen.c b/drivers/xen/swiotlb-xen.c
> index 0a40ac332a4c..b75c43356eba 100644
> --- a/drivers/xen/swiotlb-xen.c
> +++ b/drivers/xen/swiotlb-xen.c
> @@ -191,6 +191,7 @@ int __ref xen_swiotlb_init(int verbose, bool early)
>           * IO TLB memory already allocated. Just use it.
>           */
>          if (io_tlb_start != 0) {
> +               start_dma_addr = io_tlb_start;
>                  xen_io_tlb_start = phys_to_virt(io_tlb_start);
>                  goto end;
>          }
> 
> Unfortunately it doesn't solve the mmc0 error.
> 
> 
> As you might notice from the logs, none of the other interesting printks
> printed anything, which seems to mean that the memory allocated by
> xen_swiotlb_alloc_coherent and mapped by xen_swiotlb_map_page should be
> just fine.
> 
> I am starting to be out of ideas. Do you guys have any suggestions on
> what could be the issue or what could be done to discover it?

Sorry if my suggestions are going to be obvious, but I can't confirm 
whether this was already done:
     1) Does the kernel boot on baremetal (i.e without Xen)? This should 
help to confirm whether the bug is Xen is related.
     2) Swiotlb should not be necessary for basic dom0 boot on Arm. Did 
you try to disable it? This should help to confirm whether swiotlb is 
the problem or not.
     3) Did you track down how the MMC read the SCR structure?

Cheers,

-- 
Julien Grall


  reply	other threads:[~2020-05-13 10:11 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01  2:20 Troubles running Xen on Raspberry Pi 4 with 5.6.1 DomU Roman Shaposhnik
2020-05-01 11:42 ` Corey Minyard
2020-05-02  1:06   ` Roman Shaposhnik
2020-05-02  2:16     ` Corey Minyard
2020-05-02 11:46       ` Julien Grall
2020-05-02 17:35         ` Corey Minyard
2020-05-02 17:48           ` Julien Grall
2020-05-04 12:44             ` Corey Minyard
2020-05-04 20:54               ` Roman Shaposhnik
2020-05-05  3:52                 ` Stefano Stabellini
2020-05-05  5:36                   ` Roman Shaposhnik
2020-05-05 22:34                     ` Stefano Stabellini
2020-05-06  1:25                       ` Boris Ostrovsky
2020-05-06  4:19                       ` Roman Shaposhnik
2020-05-06  5:41                       ` Jürgen Groß
2020-05-06  8:54                         ` Peng Fan
2020-05-06 13:08                           ` Nataliya Korovkina
2020-05-06 13:42                             ` Boris Ostrovsky
2020-05-06 16:14                               ` Nataliya Korovkina
2020-05-06 17:34                                 ` Stefano Stabellini
2020-05-06 21:12                                   ` Roman Shaposhnik
2020-05-13  0:33                                     ` Stefano Stabellini
2020-05-13 10:11                                       ` Julien Grall [this message]
2020-05-13 15:11                                         ` Stefano Stabellini
2020-05-13 18:19                                           ` Julien Grall
2020-05-13 18:26                                             ` Julien Grall
2020-05-13 19:51                                               ` Stefano Stabellini
2020-06-02 18:34                                                 ` Corey Minyard
2020-06-02 19:24                                                   ` Stefano Stabellini
2020-06-03 15:29                                                     ` Corey Minyard
2020-06-03 15:37                                                       ` Stefano Stabellini
2020-06-03 19:49                                                         ` Corey Minyard
2020-06-03 19:55                                                         ` Roman Shaposhnik
2020-05-13 19:13                                             ` Roman Shaposhnik
2020-05-13 19:49                                             ` Stefano Stabellini
2020-05-06 17:35                                 ` Boris Ostrovsky
2020-05-06 21:10                                   ` Roman Shaposhnik
2020-05-06 17:16                           ` Stefano Stabellini
2020-05-06 17:32                         ` Stefano Stabellini
2020-05-02 18:48           ` Elliott Mitchell
2020-05-02 19:43             ` Julien Grall
2020-05-06 13:48         ` Corey Minyard
2020-05-06 13:56           ` Julien Grall
2020-05-02  0:05 ` Stefano Stabellini
2020-05-02  1:12   ` Roman Shaposhnik

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=42253259-9663-67e8-117f-8ba631243585@xen.org \
    --to=julien@xen.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jeff.kubascik@dornerworks.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=malus.brandywine@gmail.com \
    --cc=minyard@acm.org \
    --cc=peng.fan@nxp.com \
    --cc=roman@zededa.com \
    --cc=sstabellini@kernel.org \
    --cc=stefano.stabellini@xilinx.com \
    --cc=xen-devel@lists.xenproject.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.