From: Peter Zijlstra <peterz@infradead.org>
To: Fabio Coatti <fabio.coatti@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, eranian@google.com, mingo@elte.hu,
acme@redhat.com, ak@linux.intel.com, zheng.z.yan@intel.com
Subject: Re: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x290/0x2fa()
Date: Thu, 10 Jul 2014 10:52:08 +0200 [thread overview]
Message-ID: <20140710085208.GD12054@laptop.lan> (raw)
In-Reply-To: <20140710084421.GT3935@laptop>
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
next prev parent reply other threads:[~2014-07-10 8:52 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 [this message]
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=20140710085208.GD12054@laptop.lan \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=fabio.coatti@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.