linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	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 09:24:31 -0700	[thread overview]
Message-ID: <z2i5bdc1c8b1004080924q1b8d3994vd69c9c9dd0bb2f78@mail.gmail.com> (raw)
In-Reply-To: <4BBDEF93.6070306@ladisch.de>

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.

Being that I'm not 100% sure which address you meant here's everything:

k2 ~ # cat /proc/iomem
00000000-0008efff : System RAM
0008f000-0008ffff : reserved
00090000-0009cfff : System RAM
0009d000-0009ffff : reserved
000e0000-000fffff : reserved
00100000-cf4bcfff : System RAM
  01000000-013466b6 : Kernel code
  013466b7-0166ab1f : Kernel data
  016e3000-01737eb3 : Kernel bss
cf4bd000-cf4befff : reserved
cf4bf000-cf4c3fff : System RAM
cf4c4000-cf7befff : ACPI Non-volatile Storage
cf7bf000-cf7defff : System RAM
cf7df000-cf7fefff : ACPI Tables
cf7ff000-cf7fffff : System RAM
cf800000-cfffffff : reserved
d0000000-d2ffffff : PCI Bus 0000:02
  d0000000-d1ffffff : 0000:02:00.0
  d2000000-d2ffffff : 0000:02:00.0
    d2000000-d2ffffff : nvidia
d3000000-d30fffff : PCI Bus 0000:07
  d3000000-d3003fff : 0000:07:03.0
  d3004000-d30047ff : 0000:07:03.0
    d3004000-d30047ff : firewire_ohci
d3100000-d31fffff : PCI Bus 0000:06
  d3100000-d31003ff : 0000:06:00.0
    d3100000-d31003ff : ahci
d3200000-d321ffff : 0000:00:19.0
  d3200000-d321ffff : e1000e
d3220000-d32207ff : 0000:00:1f.2
  d3220000-d32207ff : ahci
d3221000-d32213ff : 0000:00:1d.7
  d3221000-d32213ff : ehci_hcd
d3222000-d32223ff : 0000:00:1a.7
  d3222000-d32223ff : ehci_hcd
d3223000-d3223fff : 0000:00:19.0
  d3223000-d3223fff : e1000e
e0000000-efffffff : PCI Bus 0000:02
  e0000000-efffffff : 0000:02:00.0
f0000000-f0003fff : 0000:00:1b.0
  f0000000-f0003fff : ICH HD audio
f0004000-f00040ff : 0000:00:1f.3
f8000000-fcffffff : reserved
  f8000000-fbffffff : PCI MMCONFIG 0000 [bus 00-3f]
fec00000-fec003ff : IOAPIC 0
fed00000-fed003ff : HPET 0
fee00000-fee00fff : Local APIC
ffe00000-ffffffff : reserved
100000000-1afffffff : System RAM
k2 ~ #

Cheers,
Mark

  reply	other threads:[~2010-04-08 16:24 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 [this message]
2010-04-08 17:40                   ` Robert Hancock
2010-04-08 19:01                     ` Mark Knecht
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=z2i5bdc1c8b1004080924q1b8d3994vd69c9c9dd0bb2f78@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).