All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince Weaver <vincent.weaver@maine.edu>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Stephane Eranian <eranian@google.com>,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	ak@linux.intel.com, kan.liang@intel.com, mingo@elte.hu,
	sonnyrao@chromium.org
Subject: Re: [PATCH] perf/x86/intel/uncore: fix IMC missing box initialization
Date: Fri, 24 Apr 2015 10:03:04 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.11.1504241001040.20552@vincent-weaver-1.umelst.maine.edu> (raw)
In-Reply-To: <alpine.DEB.2.11.1504240935110.20357@vincent-weaver-1.umelst.maine.edu>

On Fri, 24 Apr 2015, Vince Weaver wrote:

> [   79.473121] kernel BUG at mm/vmalloc.c:1335!
> [   79.477705] invalid opcode: 0000 [#1] SMP 
...
> [   79.694391] Call Trace:
> [   79.696997]  <IRQ> 
> [   79.699090]  [<ffffffff811b2130>] get_vm_area_caller+0x40/0x50
> [   79.705505]  [<ffffffff81039f4d>] ? snb_uncore_imc_init_box+0x6d/0x90

This maps to:

	static void snb_uncore_imc_init_box(struct intel_uncore_box *box) {
		...
	        box->io_addr = ioremap(addr, SNB_UNCORE_PCI_IMC_MAP_SIZE);

The machine I am seeing this on is a Haswell desktop, Intel 6/60/3.

Vince

  reply	other threads:[~2015-04-24 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  5:47 [PATCH] perf/x86/intel/uncore: fix IMC missing box initialization Stephane Eranian
2015-04-24 13:38 ` Vince Weaver
2015-04-24 14:03   ` Vince Weaver [this message]
2015-04-24 14:38     ` Stephane Eranian
2015-04-24 19:22       ` Bjorn Helgaas
2015-04-24 19:29         ` Stephane Eranian
2015-04-25  4:38           ` Andi Kleen
2015-04-27  3:43             ` Liang, Kan
2015-04-28  6:23               ` Stephane Eranian
2015-04-28 10:52               ` Peter Zijlstra
2015-05-11 10:00                 ` Ingo Molnar
2015-06-08 17:45                   ` Vince Weaver
2015-06-09  7:20                     ` Ingo Molnar
2015-06-09  8:33                   ` Peter Zijlstra

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.11.1504241001040.20552@vincent-weaver-1.umelst.maine.edu \
    --to=vincent.weaver@maine.edu \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sonnyrao@chromium.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.