From: CAI Qian <caiqian@redhat.com>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kasan inline + CONFIG_DEBUG_TEST_DRIVER_REMOVE kernel panic
Date: Mon, 10 Oct 2016 16:09:45 -0400 (EDT) [thread overview]
Message-ID: <1067379191.120724.1476130185335.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAL_JsqLPnXC8WQR2wb82M0BqFTEoH=YughMLoJxdMyfq4oB_7Q@mail.gmail.com>
> Is the backtrace the same in that case?
Very close. I saw "intel" there, and here is the list those modules on the system.
# lsmod | grep intel
intel_rapl 20480 0
intel_powerclamp 16384 0
kvm_intel 208896 0
kvm 630784 1 kvm_intel
ghash_clmulni_intel 16384 0
aesni_intel 167936 0
lrw 16384 1 aesni_intel
glue_helper 16384 1 aesni_intel
ablk_helper 16384 1 aesni_intel
cryptd 24576 3 ablk_helper,ghash_clmulni_intel,aesni_intel
crc32c_intel 24576 1
[ 17.884926] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 17.893700] IP: [<ffffffff81546ff7>] device_del+0x17/0x280
[ 17.899848] PGD 0
[ 17.902109] Oops: 0000 [#1] PREEMPT SMP
[ 17.906394] Modules linked in:
[ 17.909823] CPU: 68 PID: 1 Comm: swapper/0 Not tainted 4.8.0-remove-nokasan+ #5
[ 17.917985] Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS GRRFSDP1.86B.0271.R00.1510301446 10/30/2015
[ 17.929347] task: ffff8810556c8000 task.stack: ffffc90000078000
[ 17.935955] RIP: 0010:[<ffffffff81546ff7>] [<ffffffff81546ff7>] device_del+0x17/0x280
[ 17.944811] RSP: 0000:ffffc9000007bc00 EFLAGS: 00010286
[ 17.950742] RAX: 0000000000000000 RBX: ffff88085c8e3c00 RCX: 0000000000000001
[ 17.958708] RDX: ffff881059d60000 RSI: 000000000000000b RDI: 0000000000000000
[ 17.966675] RBP: ffffc9000007bc38 R08: 00000000d38c0f63 R09: 0000000000000000
[ 17.974640] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 17.982606] R13: ffff881054099000 R14: 0000000000000001 R15: 0000000000000000
[ 17.990574] FS: 0000000000000000(0000) GS:ffff88105e400000(0000) knlGS:0000000000000000
[ 17.999606] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 18.006022] CR2: 0000000000000000 CR3: 0000000001c06000 CR4: 00000000003406e0
[ 18.013989] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 18.021954] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 18.029919] Stack:
[ 18.032163] 0000000000000000 00000000dd652bd0 ffff88085c8e3c00 ffff88085c8e3c00
[ 18.040475] ffff88085c8e3400 ffff881054099000 0000000000000001 ffffc9000007bc58
[ 18.048788] ffffffff811c9680 ffff88085c8e3c00 ffff88085c8e3400 ffffc9000007bc88
[ 18.057090] Call Trace:
[ 18.059819] [<ffffffff811c9680>] perf_pmu_unregister+0x90/0x150
[ 18.066529] [<ffffffff81017678>] uncore_pci_remove+0xc8/0x160
[ 18.073044] [<ffffffff814428c9>] pci_device_remove+0x39/0xc0
[ 18.079468] [<ffffffff8154bf4e>] driver_probe_device+0xbe/0x4d0
[ 18.086176] [<ffffffff8154c443>] __driver_attach+0xe3/0xf0
[ 18.092399] [<ffffffff8154c360>] ? driver_probe_device+0x4d0/0x4d0
[ 18.099400] [<ffffffff81549b43>] bus_for_each_dev+0x73/0xc0
[ 18.105722] [<ffffffff8154b7de>] driver_attach+0x1e/0x20
[ 18.111752] [<ffffffff8154b290>] bus_add_driver+0x200/0x270
[ 18.118078] [<ffffffff8154d160>] driver_register+0x60/0xe0
[ 18.124303] [<ffffffff81440ee0>] __pci_register_driver+0x60/0x70
[ 18.131117] [<ffffffff81f1e6e1>] intel_uncore_init+0x277/0x2df
[ 18.137728] [<ffffffff81f1e46a>] ? uncore_type_init+0x15f/0x15f
[ 18.144441] [<ffffffff81002190>] do_one_initcall+0x50/0x190
[ 18.150768] [<ffffffff810c5bf1>] ? parse_args+0x2d1/0x490
[ 18.156894] [<ffffffff81f19243>] kernel_init_freeable+0x1ff/0x29e
[ 18.163801] [<ffffffff817dd840>] ? rest_init+0x140/0x140
[ 18.169831] [<ffffffff817dd84e>] kernel_init+0xe/0x100
[ 18.175668] [<ffffffff817e957a>] ret_from_fork+0x2a/0x40
[ 18.181695] Code: e8 cf d4 29 00 5b 5d c3 66 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 53 49 89 fc 48 83 ec 18 <4c> 8b 2f 65 48 8b 04 25 28 00 00 00 48 89 45 d8 31 c0 48 8b 87
[ 18.203631] RIP [<ffffffff81546ff7>] device_del+0x17/0x280
[ 18.209867] RSP <ffffc9000007bc00>
[ 18.213759] CR2: 0000000000000000
[ 18.217548] ---[ end trace 91188545987fc9d9 ]---
[ 18.222706] Kernel panic - not syncing: Fatal exception
[ 18.228692] ---[ end Kernel panic - not syncing: Fatal exception
next prev parent reply other threads:[~2016-10-10 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <907882571.66590.1476113724660.JavaMail.zimbra@redhat.com>
2016-10-10 15:37 ` kasan inline + CONFIG_DEBUG_TEST_DRIVER_REMOVE kernel panic CAI Qian
2016-10-10 17:09 ` Rob Herring
2016-10-10 18:25 ` CAI Qian
2016-10-10 17:20 ` Greg Kroah-Hartman
2016-10-10 18:15 ` Rob Herring
2016-10-10 18:22 ` CAI Qian
2016-10-10 19:34 ` Rob Herring
2016-10-10 20:09 ` CAI Qian [this message]
2016-10-19 14:45 ` [4.9-rc1+] intel_uncore builtin " CAI Qian
2016-10-19 19:19 ` Jiri Olsa
2016-10-19 20:18 ` CAI Qian
2016-10-20 5:39 ` Peter Zijlstra
2016-10-20 8:58 ` Jiri Olsa
2016-10-20 9:04 ` Peter Zijlstra
2016-10-20 9:42 ` Jiri Olsa
2016-10-20 11:10 ` [PATCH] perf: Protect pmu device removal with pmu_bus_running check " Jiri Olsa
2016-10-20 14:30 ` CAI Qian
2016-10-28 10:10 ` [tip:perf/urgent] perf/core: Protect PMU device removal with a 'pmu_bus_running' check, to fix CONFIG_DEBUG_TEST_DRIVER_REMOVE=y " tip-bot for Jiri Olsa
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=1067379191.120724.1476130185335.JavaMail.zimbra@redhat.com \
--to=caiqian@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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 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.