From: Fabio Coatti <fabio.coatti@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x290/0x2fa()
Date: Wed, 09 Jul 2014 20:41:17 +0200 [thread overview]
Message-ID: <1502740.TF1NxA0qsa@calvin> (raw)
In-Reply-To: <20140707204747.GA24934@kroah.com>
In data lunedì 7 luglio 2014 13:47:47, Greg Kroah-Hartman ha scritto:
> On Mon, Jul 07, 2014 at 10:32:56PM +0200, Fabio Coatti wrote:
> > I'm seeing this message in latest kernels (this is from 3.15.4, but I have
> > same
> > message starting from 3.15.0, IIRC):
> So 3.14.0 didn't show this?
>
> If so, can you run 'git bisect' between those two kernel versions to try
> to track down the issue?
>
> thanks,
>
> greg k-h
ok, I tried to bisect as suggested and got the commit reported below. However
I'm not really sure to have got the right one, as one kernel refused to
compile during the last steps. However I post here the result, maybe they can
be useful.
Tomorrow I can retry the whole process again starting from different commits.
b9e1ab6d4c0582cad97699285a6b3cf992251b00 is the first bad commit
commit b9e1ab6d4c0582cad97699285a6b3cf992251b00
Author: Stephane Eranian <eranian@google.com>
Date: Tue Feb 11 16:20:12 2014 +0100
perf/x86/uncore: add SNB/IVB/HSW client uncore memory controller support
This patch adds a new uncore PMU for Intel SNB/IVB/HSW client
CPUs. It adds the Integrated Memory Controller (IMC) PMU. This
new PMU provides a set of events to measure memory bandwidth utilization.
The IMC on those processor is PCI-space based. This patch
exposes a new uncore PMU on those processor: uncore_imc
Two new events are defined:
- name: data_reads
- code: 0x1
- unit: 64 bytes
- number of full cacheline read requests to the IMC
- name: data_writes
- code: 0x2
- unit: 64 bytes
- number of full cacheline write requests to the IMC
Documentation available at:
http://software.intel.com/en-us/articles/monitoring-integrated-memory-controller-requests-in-the-2nd-3rd-and-4th-generation-intel
Cc: mingo@elte.hu
Cc: acme@redhat.com
Cc: ak@linux.intel.com
Cc: zheng.z.yan@intel.com
Cc: peterz@infradead.org
Signed-off-by: Stephane Eranian <eranian@google.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1392132015-14521-7-git-send-email-eranian@google.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
:040000 040000 2d628022cbc4b8969a2ec311082053510cf6eed5
79b2a1cc3ed29e4820a5ae4221b4cf603c138887 M arch
--
Fabio
next prev parent reply other threads:[~2014-07-09 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADpTngUm7d88RJS9OV=64t6QrJU4r3M_Z8eV1QYWPeeB5SX5-w@mail.gmail.com>
2014-07-07 20:47 ` WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x290/0x2fa() Greg Kroah-Hartman
2014-07-07 20:51 ` Fabio Coatti
2014-07-09 18:41 ` Fabio Coatti [this message]
2014-07-09 18:54 ` Greg Kroah-Hartman
2014-07-09 19:48 ` Fabio Coatti
2014-07-10 8:44 ` Peter Zijlstra
2014-07-10 8:52 ` Peter Zijlstra
2014-07-10 8:54 ` Peter Zijlstra
2014-07-10 12:13 ` Fabio Coatti
2014-07-10 19:12 ` Stephane Eranian
2014-07-10 20:05 ` Bjorn Helgaas
2014-07-11 7:38 ` Fabio Coatti
2014-07-11 18:11 ` Bjorn Helgaas
2014-07-15 20:33 ` Bjorn Helgaas
2014-07-15 23:40 ` Yinghai Lu
2014-07-15 23:54 ` H. Peter Anvin
2014-07-16 0:56 ` Yinghai Lu
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=1502740.TF1NxA0qsa@calvin \
--to=fabio.coatti@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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.