From: Sachin Sant <sachinp@in.ibm.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Sharyathi Nagesh <sharyath@in.ibm.com>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: Bug while executing : cat /proc/iomem on 2.6.17-rc1/rc2
Date: Thu, 11 May 2006 14:08:12 +0530 [thread overview]
Message-ID: <4462F7F4.7050908@in.ibm.com> (raw)
In-Reply-To: <20060511073205.GA28693@flint.arm.linux.org.uk>
Russell King wrote:
>Only the root should have a NULL parent, so this is just covering up some
>other problem - you have a resource which somehow has illegally ended up
>with a NULL parent pointer while it's been registered.
>
>Maybe try adding:
>
> if (p->parent == NULL) {
> printk("resource with null parent: %lx-%lx: %s\n",
> p->start, p->end, p->name);
> break;
> }
>
>just before the test in that loop, and then finding out why that resource
>is becoming invalid.
>
>
>
I get this output in dmesg with the above code.
resource with null parent: 0-57ffffff: System RAM
resource with null parent: 0-57ffffff: System RAM
x236:/home/sharyathi/linux-2.6.17-rc1/kernel # cat /proc/iomem
00000000-0009dbff : System RAM
0009dc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cafff : Video ROM
000cb000-000cc5ff : Adapter ROM
000f0000-000fffff : System ROM
00100000-c7fcb5ff : System RAM
00100000-004ff436 : Kernel code
004ff437-0068881f : Kernel data
x236:/home/sharyathi/linux-2.6.17-rc1/kernel #
next prev parent reply other threads:[~2006-05-11 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 10:43 Bug while executing : cat /proc/iomem on 2.6.17-rc1/rc2 Sachin Sant
2006-04-25 10:48 ` Arjan van de Ven
2006-05-11 7:27 ` Sharyathi Nagesh
2006-05-11 7:32 ` Russell King
2006-05-11 8:38 ` Sachin Sant [this message]
2006-05-13 10:30 ` Maneesh Soni
2006-05-13 14:56 ` Linus Torvalds
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=4462F7F4.7050908@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sharyath@in.ibm.com \
/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).