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, 8 Apr 2010 12:01:28 -0700
From:	Mark Knecht <markknecht@...il.com>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	Clemens Ladisch <clemens@...isch.de>,
	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: Failed to initialize MSI interrupts && ioremap reserve_memtype 
	failed -22

On Thu, Apr 8, 2010 at 10:40 AM, Robert Hancock <hancockrwd@...il.com> wrote:
> On Thu, Apr 8, 2010 at 10:24 AM, Mark Knecht <markknecht@...il.com> wrote:
>> On Thu, Apr 8, 2010 at 8:00 AM, Clemens Ladisch <clemens@...isch.de> wrote:
>>> Mark Knecht wrote:
>>>> ioremap reserve_memtype failed -22
>>>> phys_addr: 0xcf7fe000, size: 0x2000
>>>
>>> What is at this address in /proc/iomem?
>>>
>>>> Call Trace:
>>>>  [<ffffffff8101b7ee>] ? __ioremap_caller+0x1e2/0x30e
>>>>  [<ffffffffa052345b>] ? _nv006553rm+0x3a/0x40 [nvidia]
>>>
>>> I didn't find this function name in the kernel source ...
>>>
>>>
>>> Regards,
>>> Clemens
>>>
>>
>> Is there a serious chance this is somehow related to the closed source
>> nvidia driver? I could investigate switching to the in kernel driver
>> although that might take me a little time to get to.
>
> Yeah, those symbols are from the NVIDIA driver. Seems like it's trying
> to reserve part of memory in ACPI tables somehow?
>
> You might want to make sure you have the latest version (or just use
> nouveau instead..)
>

I spent a few minutes looking at the Gentoo nouveau guide. I think I
won't be able to do that before Sunday so if there's nothing else to
reasonably look at and you're >50% sure that's the reason then I'll
probably have to get back to you guys next Monday or so. (Assuming the
guides are correct and it actually works.

One question: If I simply remove the nvidia driver (either emerge -C
or blacklist it) then assuming it doesn't load if I don't see the
message we at least know it's involved in the problem, correct? That's
very easy to do right now as a test.

- Mark
--
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/