From: Rusty Russell <rusty@rustcorp.com.au>
To: Ming Lei <tom.leiming@gmail.com>, Axel Lin <axel.lin@ingics.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Michal Marek <mmarek@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: kernel BUG at kernel/kallsyms.c:222!
Date: Mon, 11 Nov 2013 10:53:23 +1030 [thread overview]
Message-ID: <87y54vzszo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CACVXFVMAnewCkSNNke3kf1-yO+JCc_HBRp8iaLBPJ+14G79Haw@mail.gmail.com>
Ming Lei <tom.leiming@gmail.com> writes:
> Hi Axel,
>
> On Fri, Nov 8, 2013 at 12:20 PM, Axel Lin <axel.lin@ingics.com> wrote:
>>
>>
>> Hi Ming,
>>
>> I have patches on top of 3.12 to support gpl32700 SoC.
>> So you cannot find this platform on mainline kernel.
>
> OK, I see.
>
>> I havn't tried perf, below is my config for your reference:
>> (to make the config smaller, I grep out disabled config entries.)
>
> I doubt CONFIG_VMSPLIT_3G/CONFIG_PAGE_OFFSET isn't
> used at all in your unmerged patchset, also your link script should
> be different with in-tree arch/arm/kernel/vmlinux.lds.S, otherwise
> you may put all your kernel symbols after 0xC00000000.
>
> Maybe you need to not define PAGE_OFFSET and let it be
> PHYS_OFFSET at default, also VMSPLIT_3G shouldn't have
> been there on non-MMU linux.
OK, unless there are other platforms which have this issue, I'll
leave it with you to hold this patch for merge with your SoC.
Cheers,
Rusty.
next prev parent reply other threads:[~2013-11-11 2:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 1:53 kernel BUG at kernel/kallsyms.c:222! Axel Lin
2013-11-07 2:04 ` Ming Lei
2013-11-07 2:18 ` Axel Lin
2013-11-07 2:36 ` Ming Lei
2013-11-07 2:47 ` Axel Lin
2013-11-07 4:37 ` Ming Lei
2013-11-07 8:36 ` Axel Lin
2013-11-07 23:44 ` Rusty Russell
2013-11-08 0:45 ` Ming Lei
2013-11-08 4:20 ` Axel Lin
2013-11-08 7:13 ` Ming Lei
2013-11-11 0:23 ` Rusty Russell [this message]
2013-11-11 6:43 ` Axel Lin
2013-11-11 7:53 ` Ming Lei
2013-11-11 8:37 ` Axel Lin
2013-11-11 9:57 ` Ming Lei
2013-11-11 10:41 ` Ming Lei
2013-11-11 17:15 ` Jonathan Austin
2013-11-11 19:32 ` Russell King - ARM Linux
2013-11-12 3:22 ` Ming Lei
2013-11-12 17:36 ` Jonathan Austin
2013-11-13 4:41 ` Ming Lei
2013-11-13 9:58 ` Axel Lin
2013-11-13 11:30 ` Ming Lei
2013-12-02 1:57 ` Axel Lin
2013-12-02 2:08 ` Ming Lei
2013-12-10 6:17 ` Rusty Russell
2013-11-11 8:01 ` Uwe Kleine-König
2013-11-08 3:56 ` Axel Lin
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=87y54vzszo.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=axel.lin@ingics.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mmarek@suse.cz \
--cc=tom.leiming@gmail.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