From: rusty@rustcorp•com.au (Rusty Russell)
To: linux-arm-kernel@lists•infradead.org
Subject: kernel BUG at kernel/kallsyms.c:222!
Date: Fri, 08 Nov 2013 10:14:44 +1030 [thread overview]
Message-ID: <87zjpf4w0j.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAFRkauDe7V3N0AbfvE_=GEXHZ_Fw62VsA8p50wSUYE1-TRqMfw@mail.gmail.com>
Axel Lin <axel.lin@ingics•com> writes:
> 2013/11/7 Ming Lei <tom.leiming@gmail•com>:
>> Hi,
>>
>> On Thu, Nov 7, 2013 at 10:47 AM, Axel Lin <axel.lin@ingics•com> wrote:
>>>
>>> hi Ming,
>>> Seems CONFIG_PAGE_OFFSET is not configurabe in "make menuconfig".
>>> And I found CONFIG_PAGE_OFFSET=0xC0000000 for all below configs...
>>> $ make at91_dt_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> $ make ep93xx_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> $ make imx_v4_v5_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> $ make mxs_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> $ make omap2plus_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> $ make s3c6400_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> $ make at91x40_defconfig; grep CONFIG_PAGE_OFFSET .config
>>> ( at91x40_defconfig is also arm7tdmi )
>>
>> Firstly it can be configured via VMSPLIT_3GVMSPLIT_2G/VMSPLIT_1G.
>>
>> Secondly, configurable or not isn't the point, and maybe some uclinux
>> platforms do not use CONFIG_PAGE_OFFSET at all, but they should
>> set it as a reasonable value or at least be below than the start link
>> address of vmlinux.
>
> Hi Ming,
>
> I found in arch/arm/include/asm/memory.h:
> CONFIG_PAGE_OFFSET is not used if !CONFIG_MMU.
> So looks like setting CONFIG_PAGE_OFFSET to other value still won't work.
This seems like the simplest solution, but it may mean you still have
crap in /proc/kallsyms.
Does it work for you?
Thanks,
Rusty.
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index 32b10f53d0b4..c3bd3efec4cc 100644
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -82,7 +82,9 @@ kallsyms()
kallsymopt="${kallsymopt} --all-symbols"
fi
- kallsymopt="${kallsymopt} --page-offset=$CONFIG_PAGE_OFFSET"
+ if [ -n "${CONFIG_MMU}" ]; then
+ kallsymopt="${kallsymopt} --page-offset=$CONFIG_PAGE_OFFSET"
+ fi
local aflags="${KBUILD_AFLAGS} ${KBUILD_AFLAGS_KERNEL} \
${NOSTDINC_FLAGS} ${LINUXINCLUDE} ${KBUILD_CPPFLAGS}"
next prev parent reply other threads:[~2013-11-07 23:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1383789208.5970.1.camel@phoenix>
[not found] ` <CACVXFVMn6RSXchQ8u47F35_J+YSnp1bwF1tr-8uCEYwvFsOfgQ@mail.gmail.com>
[not found] ` <CAFRkauAEt-YhBt11opj_GVCLrxGsTSd2LowWGmukTSmGuJkd3A@mail.gmail.com>
2013-11-07 2:36 ` kernel BUG at kernel/kallsyms.c:222! 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 [this message]
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
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=87zjpf4w0j.fsf@rustcorp.com.au \
--to=rusty@rustcorp$(echo .)com.au \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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