linux-kernel - Re: Failed to initialize MSI interrupts && ioremap reserve

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 08 Apr 2010 08:37:11 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Mark Knecht <markknecht@...il.com>
CC:	Robert Hancock <hancockrwd@...il.com>,
	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: Failed to initialize MSI interrupts && ioremap reserve_memtype
 failed -22

Robert Hancock wrote:
> Hmm, not really clear to me why MSI wouldn't be used.. there aren't
> any kernel messages that seem to say why MSI would be disabled or
> unsupported. Unless maybe that particular model doesn't support MSI?

This Intel onboard adapter always supports MSI, and AFAICS there is no
MSI quirk for this chipset.

Mark, is CONFIG_PCI_MSI actually enabled?

> > ioremap reserve_memtype failed -22

ioremap is used by drivers (and sometimes by the kernel itself) to get
access to some device's memory-mapped I/O range.  "-22" is -EINVAL and
is returned by reserve_memtype to indicate that the requested memory
range includes both RAM and not-RAM.

Without a following error message, it's not possible to find out which
device that is, and where that funny address range comes from.  The fact
that there is no error message might indicate that this is harmless, but
if you want to find out more, add the following lines to
arch/x86/mm/ioremap.c directly after the error message:

		printk(KERN_ERR "phys_addr: %#Lx, size: %#Lx\n",
		       (u64)phys_addr, (u64)size);
		dump_stack();

Regards,
Clemens
--
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/