From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Koelsch boot broken on 3.18-rc1 ?
Date: Thu, 23 Oct 2014 11:19:01 +0000 [thread overview]
Message-ID: <1859424.eZJcJgnv8e@avalon> (raw)
In-Reply-To: <2292868.3VDUqTO9A7@avalon>
Hi Geert,
On Thursday 23 October 2014 14:00:31 Laurent Pinchart wrote:
> On Thursday 23 October 2014 12:59:03 Geert Uytterhoeven wrote:
> > On Thu, Oct 23, 2014 at 12:53 PM, Laurent Pinchart wrote:
> >> While rebasing my rcar-dmac patches on top of 3.18-rc1 I ran into issues
> >> booting the Koelsch board.
> >>
> >> Bisecting the problem pointed to
> >>
> >> commit 95b0e655f9148881907fdbe5baba6a9f5d094fee
> >> Author: Marek Szyprowski <m.szyprowski@samsung.com>
> >> Date: Thu Oct 9 15:26:49 2014 -0700
> >>
> >> ARM: mm: don't limit default CMA region only to low memory
> >>
> >> With LPAE enabled this results in the sh-eth driver failing with
> >>
> >> [ 1.170000] irq 194: nobody cared (try booting with the "irqpoll"
> >> option)
> >>
> >> and from time to time with an Address Error message as well (which got
> >> pushed out of my console log, I'll try to reproduce that again to get
> >> the exact message).
> >
> > renesas-drivers-2014-10-23-v3.18-rc1 works on Koelsch for me, with LPAE.
>
> I'll test it.
Both problems still occur for me with renesas-drivers-2014-10-23-v3.18-rc1.
What kernel configuration do you use ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-23 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 10:53 Koelsch boot broken on 3.18-rc1 ? Laurent Pinchart
2014-10-23 10:57 ` Laurent Pinchart
2014-10-23 10:59 ` Geert Uytterhoeven
2014-10-23 11:00 ` Laurent Pinchart
2014-10-23 11:19 ` Laurent Pinchart [this message]
2014-10-23 11:50 ` Geert Uytterhoeven
2014-10-23 12:01 ` Maxime Coquelin
2014-10-23 12:03 ` Geert Uytterhoeven
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=1859424.eZJcJgnv8e@avalon \
--to=laurent.pinchart@ideasonboard.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 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).