From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] arm64: dts: zx: Fix gic GICR property
Date: Sat, 3 Dec 2016 18:55:37 +0800 [thread overview]
Message-ID: <20161203105533.GB17375@dragon> (raw)
In-Reply-To: <6379358.TRgYEOKGM8@wuerfel>
On Fri, Dec 02, 2016 at 05:38:01PM +0100, Arnd Bergmann wrote:
> On Monday, November 28, 2016 10:08:18 PM CET Shawn Guo wrote:
> > On Sat, Nov 26, 2016 at 6:03 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > > On Monday, October 17, 2016 1:49:19 PM CET Olof Johansson wrote:
> > >> On Thu, Oct 13, 2016 at 08:31:20PM +0800, Jun Nie wrote:
> > >> > GICR for multiple CPU can be described with start address and stride,
> > >> > or with multiple address. Current multiple address and stride are
> > >> > both used. Fix it.
> > >> >
> > >> > vmalloc patch 727a7f5a9 triggered this bug:
> > >> > [ 0.097146] Unable to handle kernel paging request at virtual address ffff000008060008
> > >> > [ 0.097150] pgd = ffff000008602000
> > >> > [ 0.097160] [ffff000008060008] *pgd=000000007fffe003, *pud=000000007fffd003, *pmd=000000007fffc003, *pte=0000000000000000
> > >> > [ 0.097165] Internal error: Oops: 96000007 [#1] PREEMPT SMP
> > >> > [ 0.097170] Modules linked in:
> > >> > [ 0.097177] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0+ #1474
> > >> > [ 0.097179] Hardware name: ZTE zx296718 evaluation board (DT)
> > >> > [ 0.097183] task: ffff80003e8c8b80 task.stack: ffff80003e8d0000
> > >> > [ 0.097197] PC is at gic_populate_rdist+0x74/0x15c
> > >> > [ 0.097202] LR is at gic_starting_cpu+0xc/0x20
> > >> > [ 0.097206] pc : [<ffff0000082b1b18>] lr : [<ffff0000082b26e0>] pstate: 600001c5
> > >> >
> > >> > Signed-off-by: Jun Nie <jun.nie@linaro.org>
> > >>
> > >> A Fixes: tag would be useful on a patch like this, to tell what patch
> > >> introduced the problem. Please consider using them in the future.
> > >>
> > >> I've applied this one to fixes now.
> > >
> > > Hi Olof,
> > >
> > > I happened to still have this one in my todo folder as I must have
> > > missed your reply, and I stumbled over it while looking for things
> > > that may have gone missing.
> > >
> > > I don't see it in v4.9-rc6, did it get dropped accidentally?
> >
> > Please help get this into v4.9 if possible, as it is required to get
> > v4.9 kernel boot up on ZTE ZX296718 SoC. Thanks.
> >
> > Shawn
> >
>
> Ok, applied both. Thanks,
Patch 2/2 already went to you in the pull request[1]:
[GIT PULL] ZTE arm64 device tree updates for 4.10
Shawn
[1] http://www.spinics.net/lists/arm-kernel/msg545640.html
next prev parent reply other threads:[~2016-12-03 10:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 12:31 [PATCH v2 0/2] Fix and add more zx dt nodes Jun Nie
2016-10-13 12:31 ` [PATCH v2 1/2] arm64: dts: zx: Fix gic GICR property Jun Nie
2016-10-17 20:49 ` Olof Johansson
2016-11-25 22:03 ` Arnd Bergmann
2016-11-28 14:08 ` Shawn Guo
2016-12-02 16:38 ` Arnd Bergmann
2016-12-03 10:55 ` Shawn Guo [this message]
2016-12-02 17:02 ` Marc Zyngier
2016-12-02 20:28 ` Arnd Bergmann
2016-12-05 2:24 ` Shawn Guo
2016-12-06 0:55 ` Olof Johansson
2016-12-06 1:12 ` Shawn Guo
2016-12-07 20:34 ` Olof Johansson
2016-12-07 21:44 ` Arnd Bergmann
2016-12-07 22:12 ` Olof Johansson
2016-12-07 23:25 ` Arnd Bergmann
2016-12-03 9:22 ` Shawn Guo
2016-12-03 10:11 ` Marc Zyngier
2016-10-13 12:31 ` [PATCH v2 2/2] arm64: dts: zx: Add clock controller nodes Jun Nie
2016-10-17 20:48 ` Olof Johansson
2016-10-24 8:56 ` Shawn Guo
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=20161203105533.GB17375@dragon \
--to=shawnguo@kernel.org \
--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