All of lore.kernel.org
 help / color / mirror / Atom feed
From: p.pisati@gmail.com (Paolo Pisati)
To: linux-arm-kernel@lists.infradead.org
Subject: 3.16rc3 multiplatform, Armada 370 and IOMMU: unbootable kernel
Date: Thu, 3 Jul 2014 15:51:46 +0200	[thread overview]
Message-ID: <20140703135146.GA6898@luxor.wired.org> (raw)

I can't boot 3.16rc3 on my Globalscale Mirabox (Armada 370):

Linus 3.16rc3 tree, mvebu_v7_defconfig + another multiplatform soc
(e.g. omap3/4), enable IOMMU and the soc specific backend (IOMMU + OMAP_IOMMU)
and it gives a solid hang at boot - no output on console, so i can't debug
further.

The same multiplatform kernel, with support for a wide range of socs and iommu
(omap, exynos, imx, versatile, calxeda, tegra, etcetc), boots fine with
every other board, but hangs on armada: am i the only experiencing this?
is this a known issue?
-- 
bye,
p.

             reply	other threads:[~2014-07-03 13:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 13:51 Paolo Pisati [this message]
2014-07-03 14:27 ` 3.16rc3 multiplatform, Armada 370 and IOMMU: unbootable kernel Thomas Petazzoni
2014-07-03 14:57   ` Paolo Pisati
2014-07-03 20:22   ` Gregory CLEMENT
2014-07-03 20:52     ` Thomas Petazzoni
2014-07-03 20:57       ` Gregory CLEMENT
2014-07-03 21:01         ` Thomas Petazzoni
2014-07-03 21:07           ` Gregory CLEMENT
2014-07-03 21:24             ` Gregory CLEMENT
     [not found]               ` <53B5CA26.7050405-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-07-04  8:47                 ` Laurent Pinchart
2014-07-04  8:47                   ` Laurent Pinchart
2014-07-05 15:03                   ` Ezequiel Garcia
2014-07-05 15:03                     ` Ezequiel Garcia
     [not found]                     ` <20140705150308.GA28791-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>
2014-07-05 20:59                       ` Greg Kroah-Hartman
2014-07-05 20:59                         ` Greg Kroah-Hartman
2014-07-05 20:59                         ` Greg Kroah-Hartman
2014-07-07 10:58                         ` Ezequiel Garcia
2014-07-07 10:58                           ` Ezequiel Garcia
     [not found]                           ` <20140707105818.GA1101-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>
2014-07-07 18:30                             ` Greg Kroah-Hartman
2014-07-07 18:30                               ` Greg Kroah-Hartman
2014-07-07 18:30                               ` Greg Kroah-Hartman
2014-07-07 23:37                               ` Ezequiel Garcia
2014-07-07 23:37                                 ` Ezequiel Garcia
     [not found]                                 ` <20140707233758.GA1456-nAQHv47ARr+vIlHkl8J1cg@public.gmane.org>
2014-07-07 23:47                                   ` Greg Kroah-Hartman
2014-07-07 23:47                                     ` Greg Kroah-Hartman
2014-07-07 23:47                                     ` Greg Kroah-Hartman
2014-07-08  7:41                                 ` Thomas Petazzoni
2014-07-08  7:41                                   ` Thomas Petazzoni
2014-07-08  9:20                                   ` Paolo Pisati
2014-07-08  9:20                                     ` Paolo Pisati
2014-07-08 12:01                                 ` Jason Cooper
2014-07-08 12:01                                   ` Jason Cooper

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=20140703135146.GA6898@luxor.wired.org \
    --to=p.pisati@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.