public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
* populate_rootfs fail
@ 2008-02-12  8:53 jay_chen
  2008-02-12  9:36 ` [Spam Mail] populate_rootfs fail (This message should be blocked: ctfkl59804) jay_chen
  2008-02-12 12:46 ` populate_rootfs fail Marco Stornelli
  0 siblings, 2 replies; 4+ messages in thread
From: jay_chen @ 2008-02-12  8:53 UTC (permalink / raw)
  To: linuxppc-embedded

Hello all:

I am using mpc8548, kernel 2.6.14.5, and uboot as boot loader.
When I upgrade ram from 512MB to 2G, my kernel can't boot anymore.
(I pass mem=2048M to kernel in uboot now)

It always dies in exec sys_write( ) in populate_rootfs( ).
I did more tests about this and I found that sys_write( ) could write only
about 4MB in 2G ram case.
(My initrd is about 19MB, initrd_start  : 0xCE7C7000, initrd_end  :
0xCFAAF289, initrd_end - initrd_start  : 0x012E8289 ==> about 19MB)
Could anybody give me some hints?
Is this issue related to the location of  "/initrd.image"? Could I control
it?
Is there any size limit in ppc arch about ramdisk/initrd?

Thanks for help.

                  Jay...

void __init populate_rootfs(void)
{
	char *err;
               ...
#ifdef CONFIG_BLK_DEV_INITRD
	if (initrd_start) {
                                 ...
		printk("it isn't (%s); looks like an initrd\n", err);
		fd = sys_open("/initrd.image", O_WRONLY|O_CREAT, 700);
		if (fd >= 0) {
			sys_write(fd, (char *)initrd_start,
					initrd_end - initrd_start);
			sys_close(fd);
			free_initrd();
		}
	}
#endif
}

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: [Spam Mail] populate_rootfs fail (This message should be blocked: ctfkl59804)
  2008-02-12  8:53 populate_rootfs fail jay_chen
@ 2008-02-12  9:36 ` jay_chen
  2008-02-12 12:46 ` populate_rootfs fail Marco Stornelli
  1 sibling, 0 replies; 4+ messages in thread
From: jay_chen @ 2008-02-12  9:36 UTC (permalink / raw)
  To: linuxppc-embedded-bounces+jay_chen=alphanetworks.com,
	linuxppc-embedded

One more thing:
I had changed default ramdisk size to about 80MB in kernel config.
(CONFIG_BLK_DEV_RAM_SIZE) 

I am so curious about the size limit and location in ram of "/initrd.image".
Which c file/document should I read?

                                         Jay...

-----Original Message-----
From: linuxppc-embedded-bounces+jay_chen=alphanetworks.com@ozlabs•org
[mailto:linuxppc-embedded-bounces+jay_chen=alphanetworks.com@ozlabs•org] 
Sent: Tuesday, February 12, 2008 4:54 PM
To: linuxppc-embedded@ozlabs•org
Subject: [Spam Mail] populate_rootfs fail (This message should be blocked:
ctfkl59804)

Hello all:

I am using mpc8548, kernel 2.6.14.5, and uboot as boot loader.
When I upgrade ram from 512MB to 2G, my kernel can't boot anymore.
(I pass mem=2048M to kernel in uboot now)

It always dies in exec sys_write( ) in populate_rootfs( ).
I did more tests about this and I found that sys_write( ) could write only
about 4MB in 2G ram case.
(My initrd is about 19MB, initrd_start  : 0xCE7C7000, initrd_end  :
0xCFAAF289, initrd_end - initrd_start  : 0x012E8289 ==> about 19MB) Could
anybody give me some hints?
Is this issue related to the location of  "/initrd.image"? Could I control
it?
Is there any size limit in ppc arch about ramdisk/initrd?

Thanks for help.

                  Jay...

void __init populate_rootfs(void)
{
	char *err;
               ...
#ifdef CONFIG_BLK_DEV_INITRD
	if (initrd_start) {
                                 ...
		printk("it isn't (%s); looks like an initrd\n", err);
		fd = sys_open("/initrd.image", O_WRONLY|O_CREAT, 700);
		if (fd >= 0) {
			sys_write(fd, (char *)initrd_start,
					initrd_end - initrd_start);
			sys_close(fd);
			free_initrd();
		}
	}
#endif
}

_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs•org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: populate_rootfs fail
  2008-02-12  8:53 populate_rootfs fail jay_chen
  2008-02-12  9:36 ` [Spam Mail] populate_rootfs fail (This message should be blocked: ctfkl59804) jay_chen
@ 2008-02-12 12:46 ` Marco Stornelli
  2008-02-13  1:52   ` [Spam Mail] Re: populate_rootfs fail (This message should be blocked: bkdh372119) jay_chen
  1 sibling, 1 reply; 4+ messages in thread
From: Marco Stornelli @ 2008-02-12 12:46 UTC (permalink / raw)
  To: jay_chen; +Cc: linuxppc-embedded

jay_chen ha scritto:
> Hello all:
> 
> I am using mpc8548, kernel 2.6.14.5, and uboot as boot loader.
> When I upgrade ram from 512MB to 2G, my kernel can't boot anymore.
> (I pass mem=2048M to kernel in uboot now)
> 
> It always dies in exec sys_write( ) in populate_rootfs( ).
> I did more tests about this and I found that sys_write( ) could write only
> about 4MB in 2G ram case.
> (My initrd is about 19MB, initrd_start  : 0xCE7C7000, initrd_end  :
> 0xCFAAF289, initrd_end - initrd_start  : 0x012E8289 ==> about 19MB)
> Could anybody give me some hints?
> Is this issue related to the location of  "/initrd.image"? Could I control
> it?
> Is there any size limit in ppc arch about ramdisk/initrd?
> 
> Thanks for help.
> 
>                   Jay...
> 
> void __init populate_rootfs(void)
> {
> 	char *err;
>                ...
> #ifdef CONFIG_BLK_DEV_INITRD
> 	if (initrd_start) {
>                                  ...
> 		printk("it isn't (%s); looks like an initrd\n", err);
> 		fd = sys_open("/initrd.image", O_WRONLY|O_CREAT, 700);
> 		if (fd >= 0) {
> 			sys_write(fd, (char *)initrd_start,
> 					initrd_end - initrd_start);
> 			sys_close(fd);
> 			free_initrd();
> 		}
> 	}
> #endif
> }
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
I think can be a problem with the u-boot initrd_high option. Have you
been enabled the highmem support to use 2G of ram, right? You can try to
set this option to 0x30000000.

Marco

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: [Spam Mail] Re: populate_rootfs fail (This message should be blocked: bkdh372119)
  2008-02-12 12:46 ` populate_rootfs fail Marco Stornelli
@ 2008-02-13  1:52   ` jay_chen
  0 siblings, 0 replies; 4+ messages in thread
From: jay_chen @ 2008-02-13  1:52 UTC (permalink / raw)
  To: linuxppc-embedded-bounces+jay_chen=alphanetworks.com; +Cc: linuxppc-embedded

 -----Original Message-----
From: linuxppc-embedded-bounces+jay_chen=alphanetworks.com@ozlabs•org
[mailto:linuxppc-embedded-bounces+jay_chen=alphanetworks.com@ozlabs•org] 
Sent: Tuesday, February 12, 2008 8:47 PM
To: jay_chen
Cc: linuxppc-embedded@ozlabs•org
Subject: [Spam Mail] Re: populate_rootfs fail (This message should be
blocked: bkdh372119)

jay_chen ha scritto:
> Hello all:
> 
> I am using mpc8548, kernel 2.6.14.5, and uboot as boot loader.
> When I upgrade ram from 512MB to 2G, my kernel can't boot anymore.
> (I pass mem=2048M to kernel in uboot now)
> 
> It always dies in exec sys_write( ) in populate_rootfs( ).
> I did more tests about this and I found that sys_write( ) could write 
> only about 4MB in 2G ram case.
> (My initrd is about 19MB, initrd_start  : 0xCE7C7000, initrd_end  :
> 0xCFAAF289, initrd_end - initrd_start  : 0x012E8289 ==> about 19MB) 
> Could anybody give me some hints?
> Is this issue related to the location of  "/initrd.image"? Could I 
> control it?
> Is there any size limit in ppc arch about ramdisk/initrd?
> 
> Thanks for help.
> 
>                   Jay...
> 
> void __init populate_rootfs(void)
> {
> 	char *err;
>                ...
> #ifdef CONFIG_BLK_DEV_INITRD
> 	if (initrd_start) {
>                                  ...
> 		printk("it isn't (%s); looks like an initrd\n", err);
> 		fd = sys_open("/initrd.image", O_WRONLY|O_CREAT, 700);
> 		if (fd >= 0) {
> 			sys_write(fd, (char *)initrd_start,
> 					initrd_end - initrd_start);
> 			sys_close(fd);
> 			free_initrd();
> 		}
> 	}
> #endif
> }
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
I think can be a problem with the u-boot initrd_high option. Have you been
enabled the highmem support to use 2G of ram, right? You can try to set this
option to 0x30000000.

Marco
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs•org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

0x30000000 doesn't work in my system, but 0x08000000 does.
I am not quiet understand the function of initrd_high and how to set it.
Since it may helps, I will try to figure out the whole story.
Thanks for your help.

                    Jay...

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-02-13  1:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-12  8:53 populate_rootfs fail jay_chen
2008-02-12  9:36 ` [Spam Mail] populate_rootfs fail (This message should be blocked: ctfkl59804) jay_chen
2008-02-12 12:46 ` populate_rootfs fail Marco Stornelli
2008-02-13  1:52   ` [Spam Mail] Re: populate_rootfs fail (This message should be blocked: bkdh372119) jay_chen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox