All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Clemens Ladisch <clemens@ladisch.de>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Failed to initialize MSI interrupts && ioremap reserve_memtype  failed -22
Date: Thu, 8 Apr 2010 12:01:28 -0700	[thread overview]
Message-ID: <j2s5bdc1c8b1004081201odd560a13z3a00c5c2325b4293@mail.gmail.com> (raw)
In-Reply-To: <k2t51f3faa71004081040l326458e4zf89854ec32a57940@mail.gmail.com>

On Thu, Apr 8, 2010 at 10:40 AM, Robert Hancock <hancockrwd@gmail.com> wrote:
> On Thu, Apr 8, 2010 at 10:24 AM, Mark Knecht <markknecht@gmail.com> wrote:
>> On Thu, Apr 8, 2010 at 8:00 AM, Clemens Ladisch <clemens@ladisch.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

  reply	other threads:[~2010-04-08 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 20:55 Failed to initialize MSI interrupts && ioremap reserve_memtype failed -22 Mark Knecht
2010-04-07 14:54 ` Clemens Ladisch
2010-04-07 15:57   ` Mark Knecht
2010-04-07 23:46     ` Robert Hancock
2010-04-08  3:51       ` Mark Knecht
2010-04-08  3:54         ` Robert Hancock
2010-04-08  4:01           ` Mark Knecht
2010-04-08  6:37           ` Clemens Ladisch
2010-04-08 14:53             ` Mark Knecht
2010-04-08 15:00               ` Clemens Ladisch
2010-04-08 16:24                 ` Mark Knecht
2010-04-08 17:40                   ` Robert Hancock
2010-04-08 19:01                     ` Mark Knecht [this message]
2010-04-08 19:51                       ` Mark Knecht

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=j2s5bdc1c8b1004081201odd560a13z3a00c5c2325b4293@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.