[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.SOC.1.00.1204280819270.14507@math.ut.ee>
Date: Sat, 28 Apr 2012 08:36:33 +0300 (EEST)
From: Meelis Roos <mroos@...ux.ee>
To: Myron Stowe <mstowe@...hat.com>
cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: x86: runtime waring in pcibios_fwaddrmap_lookup
> 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@...ee) http://www.cs.ut.ee/~mroos/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists