From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753462Ab3KGBxj (ORCPT ); Wed, 6 Nov 2013 20:53:39 -0500 Received: from mail-pd0-f171.google.com ([209.85.192.171]:42613 "EHLO mail-pd0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752515Ab3KGBxh (ORCPT ); Wed, 6 Nov 2013 20:53:37 -0500 Message-ID: <1383789208.5970.1.camel@phoenix> Subject: kernel BUG at kernel/kallsyms.c:222! From: Axel Lin To: Rusty Russell , Ming Lei Cc: Russell King , Michal Marek , linux-kernel@vger.kernel.org Date: Thu, 07 Nov 2013 09:53:28 +0800 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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