From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>,
Don Zickus <dzickus@redhat.com>, Ingo Molnar <mingo@kernel.org>,
wfg@linux.intel.com, Peter Zijlstra <peterz@infradead.org>
Subject: Re: d57108d4f6 ("watchdog/core: Get rid of the thread .."): BUG: unable to handle kernel NULL pointer dereference at 0000000000000208
Date: Fri, 15 Sep 2017 09:50:19 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1709150947550.1890@nanos> (raw)
In-Reply-To: <59baf8db.Rfy+1ZsQ37PfCiRH%fengguang.wu@intel.com>
On Fri, 15 Sep 2017, kernel test robot wrote:
> [ 0.035023] CPU: Intel Common KVM processor (family: 0xf, model: 0x6, stepping: 0x1)
> [ 0.042302] Performance Events: unsupported Netburst CPU model 6 no PMU driver, software events only.
Cute. So there is no supported PMU, but for some unknown reason the lockup
detector can create an event, otherwise the perf availaibility check in
lockup_detector_init() would fail ....
Peter???
> [ 0.051650] BUG: unable to handle kernel NULL pointer dereference at 0000000000000208
> [ 0.052000] IP: perf_event_release_kernel+0x14/0x1ed
> [ 0.052000] PGD 0 P4D 0
> [ 0.052000] Oops: 0000 [#1]
> [ 0.052000] CPU: 0 PID: 1 Comm: swapper Not tainted 4.13.0-11828-gd57108d #1
> [ 0.052000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014
> [ 0.052000] task: ffff88001e532000 task.stack: ffffc90000008000
> [ 0.052000] RIP: 0010:perf_event_release_kernel+0x14/0x1ed
> [ 0.052000] RSP: 0000:ffffc9000000be38 EFLAGS: 00010292
> [ 0.052000] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 000000000313fa45
> [ 0.052000] RDX: 0000000000000001 RSI: ffffffff828265e0 RDI: 0000000000000000
> [ 0.052000] RBP: ffffc9000000beb8 R08: ffffc9000000bdc8 R09: 0000000000000000
> [ 0.052000] R10: ffff88001e532000 R11: ffffc9000000bd68 R12: 0000000000000000
> [ 0.052000] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> [ 0.052000] FS: 0000000000000000(0000) GS:ffffffff8262f000(0000) knlGS:0000000000000000
> [ 0.052000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 0.052000] CR2: 0000000000000208 CR3: 0000000002618000 CR4: 00000000000006b0
> [ 0.052000] Call Trace:
> [ 0.052000] ? trace_hardirqs_on_caller+0x162/0x198
> [ 0.052000] hardlockup_detector_perf_cleanup+0x20/0x2d
> [ 0.052000] __lockup_detector_cleanup+0x2c/0x2e
> [ 0.052000] softlockup_update_smpboot_threads+0x48/0x4a
> [ 0.052000] softlockup_reconfigure_threads+0x21/0x5a
> [ 0.052000] lockup_detector_init+0x75/0x83
> [ 0.052000] kernel_init_freeable+0x67/0xf0
> [ 0.052000] ? rest_init+0x13a/0x13a
> [ 0.052000] kernel_init+0xe/0xf8
> [ 0.052000] ret_from_fork+0x2a/0x40
> [ 0.052000] Code: df e8 0c b2 ff ff 4c 89 e7 e8 89 13 bd 00 41 5b 5b 41 5c 41 5d c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 83 ec 58 <48> 83 bf 08 02 00 00 00 75 14 f6 87 8c 00 00 00 03 0f 84 9b 01
> [ 0.052000] RIP: perf_event_release_kernel+0x14/0x1ed RSP: ffffc9000000be38
> [ 0.052000] CR2: 0000000000000208
> [ 0.052000] ---[ end trace ed0d2c92e47d08db ]---
> [ 0.052000] Kernel panic - not syncing: Fatal exception
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: lkp@lists.01.org
Subject: Re: d57108d4f6 ("watchdog/core: Get rid of the thread .."): BUG: unable to handle kernel NULL pointer dereference at 0000000000000208
Date: Fri, 15 Sep 2017 09:50:19 +0200 [thread overview]
Message-ID: <alpine.DEB.2.20.1709150947550.1890@nanos> (raw)
In-Reply-To: <59baf8db.Rfy+1ZsQ37PfCiRH%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2745 bytes --]
On Fri, 15 Sep 2017, kernel test robot wrote:
> [ 0.035023] CPU: Intel Common KVM processor (family: 0xf, model: 0x6, stepping: 0x1)
> [ 0.042302] Performance Events: unsupported Netburst CPU model 6 no PMU driver, software events only.
Cute. So there is no supported PMU, but for some unknown reason the lockup
detector can create an event, otherwise the perf availaibility check in
lockup_detector_init() would fail ....
Peter???
> [ 0.051650] BUG: unable to handle kernel NULL pointer dereference at 0000000000000208
> [ 0.052000] IP: perf_event_release_kernel+0x14/0x1ed
> [ 0.052000] PGD 0 P4D 0
> [ 0.052000] Oops: 0000 [#1]
> [ 0.052000] CPU: 0 PID: 1 Comm: swapper Not tainted 4.13.0-11828-gd57108d #1
> [ 0.052000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014
> [ 0.052000] task: ffff88001e532000 task.stack: ffffc90000008000
> [ 0.052000] RIP: 0010:perf_event_release_kernel+0x14/0x1ed
> [ 0.052000] RSP: 0000:ffffc9000000be38 EFLAGS: 00010292
> [ 0.052000] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 000000000313fa45
> [ 0.052000] RDX: 0000000000000001 RSI: ffffffff828265e0 RDI: 0000000000000000
> [ 0.052000] RBP: ffffc9000000beb8 R08: ffffc9000000bdc8 R09: 0000000000000000
> [ 0.052000] R10: ffff88001e532000 R11: ffffc9000000bd68 R12: 0000000000000000
> [ 0.052000] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> [ 0.052000] FS: 0000000000000000(0000) GS:ffffffff8262f000(0000) knlGS:0000000000000000
> [ 0.052000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 0.052000] CR2: 0000000000000208 CR3: 0000000002618000 CR4: 00000000000006b0
> [ 0.052000] Call Trace:
> [ 0.052000] ? trace_hardirqs_on_caller+0x162/0x198
> [ 0.052000] hardlockup_detector_perf_cleanup+0x20/0x2d
> [ 0.052000] __lockup_detector_cleanup+0x2c/0x2e
> [ 0.052000] softlockup_update_smpboot_threads+0x48/0x4a
> [ 0.052000] softlockup_reconfigure_threads+0x21/0x5a
> [ 0.052000] lockup_detector_init+0x75/0x83
> [ 0.052000] kernel_init_freeable+0x67/0xf0
> [ 0.052000] ? rest_init+0x13a/0x13a
> [ 0.052000] kernel_init+0xe/0xf8
> [ 0.052000] ret_from_fork+0x2a/0x40
> [ 0.052000] Code: df e8 0c b2 ff ff 4c 89 e7 e8 89 13 bd 00 41 5b 5b 41 5c 41 5d c9 c3 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 83 ec 58 <48> 83 bf 08 02 00 00 00 75 14 f6 87 8c 00 00 00 03 0f 84 9b 01
> [ 0.052000] RIP: perf_event_release_kernel+0x14/0x1ed RSP: ffffc9000000be38
> [ 0.052000] CR2: 0000000000000208
> [ 0.052000] ---[ end trace ed0d2c92e47d08db ]---
> [ 0.052000] Kernel panic - not syncing: Fatal exception
next prev parent reply other threads:[~2017-09-15 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 21:47 d57108d4f6 ("watchdog/core: Get rid of the thread .."): BUG: unable to handle kernel NULL pointer dereference at 0000000000000208 kernel test robot
2017-09-14 21:47 ` kernel test robot
2017-09-15 7:50 ` Thomas Gleixner [this message]
2017-09-15 7:50 ` Thomas Gleixner
2017-09-15 12:54 ` Thomas Gleixner
2017-09-15 12:54 ` Thomas Gleixner
2017-09-15 16:24 ` Thomas Gleixner
2017-09-15 16:24 ` Thomas Gleixner
2017-09-16 12:46 ` Fengguang Wu
2017-09-16 12:46 ` Fengguang Wu
2017-09-16 17:35 ` Thomas Gleixner
2017-09-16 17:35 ` Thomas Gleixner
2017-09-16 17:55 ` Linus Torvalds
2017-09-16 17:55 ` Linus Torvalds
2017-09-16 18:12 ` Thomas Gleixner
2017-09-16 18:12 ` Thomas Gleixner
2017-09-16 18:23 ` Linus Torvalds
2017-09-16 18:23 ` Linus Torvalds
2017-09-16 21:47 ` Thomas Gleixner
2017-09-16 21:47 ` Thomas Gleixner
2017-09-16 22:02 ` Linus Torvalds
2017-09-16 22:02 ` Linus Torvalds
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=alpine.DEB.2.20.1709150947550.1890@nanos \
--to=tglx@linutronix.de \
--cc=dzickus@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=wfg@linux.intel.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.