From: Meelis Roos <mroos@linux.ee>
To: Myron Stowe <mstowe@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: x86: runtime waring in pcibios_fwaddrmap_lookup
Date: Sat, 28 Apr 2012 08:36:33 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1204280819270.14507@math.ut.ee> (raw)
In-Reply-To: <1335557685.2386.62.camel@zim.stowe>
> So, somehow, your system hit the assertion (WARN_ON) in
> pcibios_fwaddrmap_lookup(). From the dmesg log you provided I can see
> why pcibios_save_fw_addr() was called - there is a resource collision
> with the video device's GART - but what I don't understand is how the
> assertion is being triggered.
>
> There are only two callers of pcibios_fwaddrmap_lookup()
> (see ./arch/x86/pci/i386.c:: pcibios_save_fw_addr(), and
> pcibios_retrieve_fw_addr()) and both of those are acquiring the lock
> before making the call - so triggering the assertion just doesn't seem
> possible but obviously it is getting triggered.
>
> I don't have any ideas currently but do have some questions that
> hopefully will start to enlighten us.
>
> Does your system encounter this consistently upon every boot or
> is it hit intermittently?
Every time.
> Do you know of any kernel versions that do not encounter it?
Checked my logs, no kernel up to 3.3.0 included gave it, next tested
kernel was 3.4.0-rc2 and that had the warning and every kernel since has
had it.
> Are you running a para-virtualized kernel?
No.
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
next prev parent reply other threads:[~2012-04-28 5:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 19:41 Meelis Roos
2012-04-13 1:38 ` Bjorn Helgaas
2012-04-27 20:14 ` Myron Stowe
2012-04-28 5:36 ` Meelis Roos [this message]
2012-05-01 20:54 ` Myron Stowe
2012-05-07 22:44 ` Myron Stowe
2012-05-13 15:15 ` Meelis Roos
2012-05-14 20:21 ` Bjorn Helgaas
2012-05-14 20:53 ` Meelis Roos
2012-05-15 23:02 ` Bjorn Helgaas
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.SOC.1.00.1204280819270.14507@math.ut.ee \
--to=mroos@linux.ee \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mstowe@redhat.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
all inboxes | Powered by JetHome®