All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: [x86/rapl] BUG: unable to handle kernel paging request at 000000000000d968
Date: Thu, 25 Sep 2014 11:03:55 +0800	[thread overview]
Message-ID: <20140925030355.GA13564@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 898 bytes --]

Hi Christoph,

FYI, we noticed the below changes on

git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 89cbc76768c2fa4ed95545bf961f3a14ddfeed21 ("x86: Replace __get_cpu_var uses")


+-----------------------------+------------+------------+
|                             | 532d0d0690 | 89cbc76768 |
+-----------------------------+------------+------------+
| boot_successes              | 5          | 4          |
| boot_failures               | 0          | 6          |
| BUG:unable_to_handle_kernel | 0          | 6          |
+-----------------------------+------------+------------+

[   36.889742] BUG: unable to handle kernel paging request at 000000000000d968
[   36.897739] IP: [<ffffffff81038282>] rapl_event_update+0x82/0xb0

Thanks,
Fengguang

_______________________________________________
LKP mailing list
LKP(a)linux.intel.com

[-- Attachment #2: dmesg.obj --]
[-- Type: application/octet-stream, Size: 212998 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Christoph Lameter <cl@linux.com>
Cc: Dave Hansen <dave.hansen@intel.com>, Tejun Heo <tj@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: [x86/rapl] BUG: unable to handle kernel paging request at 000000000000d968
Date: Thu, 25 Sep 2014 11:03:55 +0800	[thread overview]
Message-ID: <20140925030355.GA13564@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

Hi Christoph,

FYI, we noticed the below changes on

git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 89cbc76768c2fa4ed95545bf961f3a14ddfeed21 ("x86: Replace __get_cpu_var uses")


+-----------------------------+------------+------------+
|                             | 532d0d0690 | 89cbc76768 |
+-----------------------------+------------+------------+
| boot_successes              | 5          | 4          |
| boot_failures               | 0          | 6          |
| BUG:unable_to_handle_kernel | 0          | 6          |
+-----------------------------+------------+------------+

[   36.889742] BUG: unable to handle kernel paging request at 000000000000d968
[   36.897739] IP: [<ffffffff81038282>] rapl_event_update+0x82/0xb0

Thanks,
Fengguang

[-- Attachment #2: .dmesg --]
[-- Type: application/octet-stream, Size: 212998 bytes --]

[-- Attachment #3: Type: text/plain, Size: 85 bytes --]

_______________________________________________
LKP mailing list
LKP@linux.intel.com

             reply	other threads:[~2014-09-25  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  3:03 Fengguang Wu [this message]
2014-09-25  3:03 ` [x86/rapl] BUG: unable to handle kernel paging request at 000000000000d968 Fengguang Wu
2014-09-25 18:45 ` Christoph Lameter
2014-09-25 18:45   ` Christoph Lameter

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=20140925030355.GA13564@localhost \
    --to=fengguang.wu@intel.com \
    --cc=lkp@lists.01.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.