From: Axel Lin <axel.lin@ingics.com>
To: Rusty Russell <rusty@rustcorp.com.au>, Ming Lei <tom.leiming@gmail.com>
Cc: Russell King <linux@arm.linux.org.uk>,
Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org
Subject: kernel BUG at kernel/kallsyms.c:222!
Date: Thu, 07 Nov 2013 09:53:28 +0800 [thread overview]
Message-ID: <1383789208.5970.1.camel@phoenix> (raw)
Hi,
I got below oops while debugging a sd controller driver:
[ 4.032026] ------------[ cut here ]------------
[ 4.036730] kernel BUG at kernel/kallsyms.c:222!
[ 4.041501] Internal error: Oops - BUG: 0 [#1] ARM
[ 4.046847] CPU: 0 PID: 6 Comm: kworker/u2:0 Not tainted 3.12.0-00061-g0835d93-dirty #1657
I can avoid the oops by either revert commit f6537f2f0eba4eba
"scripts/kallsyms: filter symbols not in kernel address space",
or comment out below line in drivers/mmc/core/sdio.c.
dev_dbg(&card->dev, "calling %pF\n", f->vendor_fixup);
The f->vendor_fixup points to add_quirk_for_sdio_devices.
It looks like the symbol add_quirk_for_sdio_devices is missing.
So I revert commit f6537f2f and check /proc/kallsyms:
~ # grep add_quirk_for_sdio_devices /proc/kallsyms
00157bf8 t add_quirk_for_sdio_devices
If I don't revert commit f6537f2f and just comment out above dev_dbg line,
Checking /proc/kallsyms then I got:
~ # grep add_quirk_for_sdio_devices /proc/kallsyms
[sched_delayed] sched: RT throttling activated
BUG: soft lockup - CPU#0 stuck for 21s! [grep:59]
CPU: 0 PID: 59 Comm: grep Not tainted 3.12.0-00061-g0835d93-dirty #1675
task: 01d36320 ti: 008be000 task.ti: 008be000
BTW, I'm testing it on a noMMU platform (arm7tdmi).
Regards,
Axel
next reply other threads:[~2013-11-07 1:53 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 1:53 Axel Lin [this message]
2013-11-07 2:04 ` kernel BUG at kernel/kallsyms.c:222! Ming Lei
2013-11-07 2:18 ` Axel Lin
2013-11-07 2:36 ` Ming Lei
2013-11-07 2:36 ` Ming Lei
2013-11-07 2:47 ` Axel Lin
2013-11-07 2:47 ` Axel Lin
2013-11-07 4:37 ` Ming Lei
2013-11-07 4:37 ` Ming Lei
2013-11-07 8:36 ` Axel Lin
2013-11-07 8:36 ` Axel Lin
2013-11-07 23:44 ` Rusty Russell
2013-11-07 23:44 ` Rusty Russell
2013-11-08 0:45 ` Ming Lei
2013-11-08 0:45 ` Ming Lei
2013-11-08 4:20 ` Axel Lin
2013-11-08 4:20 ` Axel Lin
2013-11-08 7:13 ` Ming Lei
2013-11-08 7:13 ` Ming Lei
2013-11-11 0:23 ` Rusty Russell
2013-11-11 0:23 ` Rusty Russell
2013-11-11 6:43 ` Axel Lin
2013-11-11 6:43 ` Axel Lin
2013-11-11 7:53 ` Ming Lei
2013-11-11 7:53 ` Ming Lei
2013-11-11 8:37 ` Axel Lin
2013-11-11 8:37 ` Axel Lin
2013-11-11 9:57 ` Ming Lei
2013-11-11 9:57 ` Ming Lei
2013-11-11 10:41 ` Ming Lei
2013-11-11 10:41 ` Ming Lei
2013-11-11 17:15 ` Jonathan Austin
2013-11-11 17:15 ` Jonathan Austin
2013-11-11 19:32 ` Russell King - ARM Linux
2013-11-11 19:32 ` Russell King - ARM Linux
2013-11-12 3:22 ` Ming Lei
2013-11-12 3:22 ` Ming Lei
2013-11-12 17:36 ` Jonathan Austin
2013-11-12 17:36 ` Jonathan Austin
2013-11-13 4:41 ` Ming Lei
2013-11-13 4:41 ` Ming Lei
2013-11-13 9:58 ` Axel Lin
2013-11-13 9:58 ` Axel Lin
2013-11-13 11:30 ` Ming Lei
2013-11-13 11:30 ` Ming Lei
2013-12-02 1:57 ` Axel Lin
2013-12-02 1:57 ` Axel Lin
2013-12-02 2:08 ` Ming Lei
2013-12-02 2:08 ` Ming Lei
2013-12-10 6:17 ` Rusty Russell
2013-12-10 6:17 ` Rusty Russell
2013-11-11 8:01 ` Uwe Kleine-König
2013-11-11 8:01 ` Uwe Kleine-König
2013-11-08 3:56 ` Axel Lin
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=1383789208.5970.1.camel@phoenix \
--to=axel.lin@ingics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mmarek@suse.cz \
--cc=rusty@rustcorp.com.au \
--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 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.