public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fabio Coatti <fabio.coatti@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Stephane Eranian <eranian@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	"Yan, Zheng" <zheng.z.yan@intel.com>
Subject: Re: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x290/0x2fa()
Date: Fri, 11 Jul 2014 09:38:56 +0200	[thread overview]
Message-ID: <3524198.dm6HbYTJqK@calvin> (raw)
In-Reply-To: <20140710200527.GA15190@google.com>

In data giovedì 10 luglio 2014 14:05:27, Bjorn Helgaas ha scritto:
> On Thu, Jul 10, 2014 at 09:12:44PM +0200, Stephane Eranian wrote:
> > On Thu, Jul 10, 2014 at 2:13 PM, Fabio Coatti <fabio.coatti@gmail.com> 
wrote:
> > > In data giovedì 10 luglio 2014 10:54:48, Peter Zijlstra ha scritto:
> > >> On Thu, Jul 10, 2014 at 10:52:08AM +0200, Peter Zijlstra wrote:
> > >> > On Thu, Jul 10, 2014 at 10:44:21AM +0200, Peter Zijlstra wrote:
> > >> > > On Wed, Jul 09, 2014 at 12:48:05PM -0700, Fabio Coatti wrote:
> > >> > > > In data mercoledì 9 luglio 2014 11:54:21, Greg Kroah-Hartman ha
> > > 
> > > scritto:
> > >> > > > > Try cc:ing everyone on that patch, with the original
> > >> > > > > information you
> > >> > > > > provided, and the linux-kernel mailing list.  Those developers
> > >> > > > > should be
> > >> > > > > able to help you out properly.
> > >> > > > 
> > >> > > > Ok, here you can find the description of a problem that I'm
> > >> > > > experiencing on
> > >> > > > latest kernels, since 3.15.0.  (this report comes from 3.15.4)
> > >> > > > 
> > >> > > > lug 07 22:08:00 calvin kernel: resource map sanity check
> > >> > > > conflict:
> > >> > > > 0xfed10000 0xfed15fff 0xfed10000 0xfed13fff reserved
> > >> > > > lug 07 22:08:00 calvin kernel: ------------[ cut here
> > >> > > > ]------------
> > >> > > 
> > >> > > I think this is a 'known' issue on Thinkpad (iirc). For some
> > >> > > obscure
> > >> > > reason its BIOS has funny ideas about resources etc.
> > >> > > 
> > >> > > I couldn't quickly find the prvious thread, maybe Stephane knows.
> > >> > 
> > >> > Found it:
> > >> >   lkml.kernel.org/r/20140224162400.GE16457@pd.tnic
> > >> 
> > >> Ok, reread that thread and no definite conclusion was found I think.
> > >> Just Thinkpad firmware having overlapping resources.
> > > 
> > > So I guess that this happens also for HP Folio 9470m, not only in
> > > thinkpads. I wonder how many machines shares this behaviour...
> > 
> > Somehow, I thought that Bjorn had proposed a fix for this.
> 
> Yep, this [1]:
> 
>     cb171f7abb9a PNP: Work around BIOS defects in Intel MCH area reporting
> 
> which appeared in v3.15, so it should be in your kernel.  But apparently
> it didn't work.  Fabio, can you pastebin your complete dmesg log?
> 
> [1]
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c
> b171f7abb9a

Sure, here you go:

http://pastebin.com/FiL7N64b


-- 
Fabio

  reply	other threads:[~2014-07-11  7:39 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
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 [this message]
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=3524198.dm6HbYTJqK@calvin \
    --to=fabio.coatti@gmail.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=eranian@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=zheng.z.yan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox