On Thu, May 11, 2006 at 02:08:12PM +0530, Sachin Sant wrote:
> 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 #
>
Backing out
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=10dbe196a8da6b3196881269c6639c0ec11c36cb
solves this problem for me. This patch adds memory more than 4G to /proc/iomem
but without 64-bit fields for struct resource it ends up in confusing
iomem_resource list. I think this patch needs the core 64-bit struct resource
related changes also.
Thanks
Maneesh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
