Kexec - Not working - Please help

[HackCandy]

Hello All,

I have compiled kexec <kexec-tools-2.0.0> using
the following commands:

./configure --host=arm-angstrom-linux
. /usr/local/openmoko/arm/setup-env
make

And, got the following error:
asm/page.h no such file or directory.

So, I removed the header file and added
<unistd.h> instead of <asm/page.h> & then compiled
and got the kexec binary.

In GTA02 ssh, I tried the following:
root@om-gta02:/# ./kexec -l zImage
Unsupported machine type: armv4tl

What may be the problem? Please help.

Is there any pre-built images for kexec?

Thank you,
- HHC

[Werner Almesberger]

HackCandy wrote:
> Is there any pre-built images for kexec?

Like this ?

http://downloads.openmoko.org/repository/testing/armv4t/kexec-tools_1.101-r5_armv4t.opk

I gave it a quick try a few days ago and it seems to work. (The
kernel panicked because I didn't give it the right command line,
though. You'll have to pay attention to that little detail.)

- Werner

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[HackCandy]

Hi Werner,

Thank you. Yes, that is what I need
I will try with command line. :)

- HHC

Werner Almesberger wrote

HackCandy wrote:
> Is there any pre-built images for kexec?

Like this ?

http://downloads.openmoko.org/repository/testing/armv4t/kexec-tools_1.101-r5_armv4t.opk

I gave it a quick try a few days ago and it seems to work. (The
kernel panicked because I didn't give it the right command line,
though. You'll have to pay attention to that little detail.)

- Werner

_______________________________________________
devel mailing list
[e-mail]
https://lists.openmoko.org/mailman/listinfo/devel

[HackCandy]

Hi Werner,

I was able to load and run a Kernel using kexec by doing
the following:

a) Booted using Om 2008.12
b) Placed a zImage in / directory.
c) kexec -l zImage
d) kexec -e

Kernel panic saying no root file system.

So, I tried the following:

kexec -l zImage -append="root=/dev/mmcblk0p1" <==== Hangs here
kexec -e

/dev/mmcblk0p1 -> contains 2008.9 rfs

Is it the right way to do?

Please clarify.
- HHC

HackCandy wrote

Hi Werner,

Thank you. Yes, that is what I need
I will try with command line. :)

- HHC

Werner Almesberger wrote

HackCandy wrote:
> Is there any pre-built images for kexec?

Like this ?

http://downloads.openmoko.org/repository/testing/armv4t/kexec-tools_1.101-r5_armv4t.opk

I gave it a quick try a few days ago and it seems to work. (The
kernel panicked because I didn't give it the right command line,
though. You'll have to pay attention to that little detail.)

- Werner

_______________________________________________
devel mailing list
[e-mail]
https://lists.openmoko.org/mailman/listinfo/devel

[andy green-3]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Hi Werner,
|
| I was able to load and run a Kernel using kexec by doing
| the following:
|
| a) Booted using Om 2008.12
| b) Placed a zImage in / directory.
| c) kexec -l zImage
| d) kexec -e
|
| Kernel panic saying no root file system.
|
| So, I tried the following:
|
| kexec -l zImage -append="root=/dev/mmcblk0p1" <==== Hangs here

You might want to add "console=tty0 console=ttySAC2,115200 loglevel=8"
to the appended commandline if the problem is you're not getting enough
feedback to see what's happening.

- -Andy


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmBeXIACgkQOjLpvpq7dMpA5gCfQaq0qidAPhfdbDq4TxYSNQEB
evUAn2XQJf8dOficXBXRkV+RbKcOPvQe
=rJAx
-----END PGP SIGNATURE-----

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[Werner Almesberger]

HackCandy wrote:
> kexec -l zImage -append="root=/dev/mmcblk0p1" <==== Hangs here

It hangs ? That's odd.

This works for me:

kexec -l --command-line="`cat /proc/cmdline`" zImage
kexec -e

- Werner

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[andy green-3]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| root@om-gta02:~# kexec -l --command-line="rootfstype=jffs2
| root=/dev/mmcblk0p1 c

It's really jffs2 on partition 1 of the SD Card?

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmB50IACgkQOjLpvpq7dMrSbwCdEH87hFNMfRBdA68BaWbelsYy
whoAn0QsNtyCaK4yZ12Qtuf4+ss1i/gw
=bNPX
-----END PGP SIGNATURE-----

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[HackCandy]

Hi Werner,

---------------------
kexec -l --command-line="`cat /proc/cmdline`" zImage
kexec -e
---------------------
The above commands work fine. That is, booting a different kernel
& the same Root File System (from where you execute kexec) works well.

But when I try to use the RFS from SD card and executing the
kexec command (I m running kexec from RFS present in NAND flash)
using the following: Kernel panics saying

Unable to mount rootfs on unknown block(179,1)

---------------------
root@om-gta02:~# kexec -l --command-line="rootfstype=ext3 root=/dev/mmcblk0p1 c
onsole=ttySAC2,115200 console=tty0 loglevel=4 regular_boot mtdparts=physmap-flas
h:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kerne
l),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)" zImage
root@om-gta02:~# kexec -e  ==== Kernel Panics
---------------------

Please help.

-HHC.

Werner Almesberger wrote

HackCandy wrote:
> kexec -l zImage -append="root=/dev/mmcblk0p1" <==== Hangs here

It hangs ? That's odd.

This works for me:

kexec -l --command-line="`cat /proc/cmdline`" zImage
kexec -e

- Werner

_______________________________________________
devel mailing list
[e-mail]
https://lists.openmoko.org/mailman/listinfo/devel

[HackCandy]

Hi Andy,

Its not jffs2 partition. Its ext3 only.
First, I tried --command-line="rootfstype=jffs2 ...
and posted. Then I realized that its ext3 and
deleted the post without seeing your response.
Sorry for that.

I tried ext3 also. It didn't work.

-HHC.

Andy Green wrote

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| root@om-gta02:~# kexec -l --command-line="rootfstype=jffs2
| root=/dev/mmcblk0p1 c

It's really jffs2 on partition 1 of the SD Card?

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmB50IACgkQOjLpvpq7dMrSbwCdEH87hFNMfRBdA68BaWbelsYy
whoAn0QsNtyCaK4yZ12Qtuf4+ss1i/gw
=bNPX
-----END PGP SIGNATURE-----

_______________________________________________
devel mailing list
[e-mail]
https://lists.openmoko.org/mailman/listinfo/devel

[andy green-3]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:

| Its not jffs2 partition. Its ext3 only.
| I tried ext3 also. It didn't work.

If your partition is actually ext2 somehow with no journal, it can also
fail that way.

If you have loglevel=8 and console=tty0, you should get a dmesg type
spew on the LCM... what is that showing?

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmCsWYACgkQOjLpvpq7dMocuQCfeC+Sa0hgvgyicT3X5l83Ix49
M4gAnjbxqgUBe8mTpzLuxgD2XI1qOEB1
=OLla
-----END PGP SIGNATURE-----

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[Radek Polak]

> If you have loglevel=8 and console=tty0, you should get a dmesg type
> spew on the LCM... what is that showing?
>  
I also try appending: rootdelay=1
For me this is needed to boot from SD card.

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[HackCandy]

Hi Radek / Andy,

I tried with rootdelay=1 and did not succeed

kexec -l --command-line="rootfstype=ext3 root=/dev/mmcblk0p1 console=ttySAC2,115200 console=tty0 loglevel=4 rootdelay=1 regular_boot mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)" zImage

The following are the outputs on the LCM:

With 2GB SD card: rootdelay=1

lis302dl lis302dl.1: device BOOT reload failed
lis302dl lis302dl.2: device BOOT reload failed
Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(179,1)

With 256MB SD card: rootdelay=1

lis302dl lis302dl.1: device BOOT reload failed
lis302dl lis302dl.2: device BOOT reload failed
Kernel panic - not syncing: Attempted to kill init!

- HHC.

Radek Polak wrote

> If you have loglevel=8 and console=tty0, you should get a dmesg type
> spew on the LCM... what is that showing?
>  
I also try appending: rootdelay=1
For me this is needed to boot from SD card.

_______________________________________________
devel mailing list
[e-mail]
https://lists.openmoko.org/mailman/listinfo/devel

[Radek Polak]

> Hi Radek / Andy,
>
> I tried with rootdelay=1 and did not succeed :confused:
>
> The following are the outputs on the LCM:
>
> With 2GB SD card: rootdelay=1
>
> lis302dl lis302dl.1: device BOOT reload failed
> lis302dl lis302dl.2: device BOOT reload failed
> Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(179,1)
>
> With 256MB SD card: rootdelay=1
>
> lis302dl lis302dl.1: device BOOT reload failed
> lis302dl lis302dl.2: device BOOT reload failed
> Kernel panic - not syncing: Attempted to kill init!
>
> - HHC.
>
>  

Maybe stupid question... can you boot the system on SD card
with normal bootloader (qi, u-boot)?

Radek

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[andy green-3]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Hi Radek / Andy,
|
| I tried with rootdelay=1 and did not succeed :confused:
|
| The following are the outputs on the LCM:
|
| With 2GB SD card: rootdelay=1
|
| lis302dl lis302dl.1: device BOOT reload failed
| lis302dl lis302dl.2: device BOOT reload failed
| Kernel panic - not syncing: VFS: Unable to mount root fs
| on unknown-block(179,1)

I think you get better information with loglevel=8, this still looks
like loglevel=4

For example, why is 179,1 "unknown"... presumably failure to start up
the card.  Did kexec leave the card powered, addressed and up?  Then
maybe we need to adapt glamo-mci startup to be more defensive about
forcing the card down...

- -Andy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmC2j4ACgkQOjLpvpq7dMpYPgCggTzbucu4IBIK2qQq6V3qEIYi
w9sAn3/8N0O7eoWXIETHciuKd8fzG4UZ
=+iQF
-----END PGP SIGNATURE-----

_______________________________________________
devel mailing list
[hidden email]
https://lists.openmoko.org/mailman/listinfo/devel

[HackCandy]

Hi Werner/Andy/Radek,

It worked. Thank you all for helping me.

Radek - Not a stupid question though. I did
the stupidity of messing up ext2/ext3
along with u-boot/Qi. Once I did everyting
from the scratch, it worked.

Also, I tried without rootdelay= it didn't work.
So its needed for RFS from SD.

-HHC

Andy Green wrote

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Hi Radek / Andy,
|
| I tried with rootdelay=1 and did not succeed :confused:
|
| The following are the outputs on the LCM:
|
| With 2GB SD card: rootdelay=1
|
| lis302dl lis302dl.1: device BOOT reload failed
| lis302dl lis302dl.2: device BOOT reload failed
| Kernel panic - not syncing: VFS: Unable to mount root fs
| on unknown-block(179,1)

I think you get better information with loglevel=8, this still looks
like loglevel=4

For example, why is 179,1 "unknown"... presumably failure to start up
the card.  Did kexec leave the card powered, addressed and up?  Then
maybe we need to adapt glamo-mci startup to be more defensive about
forcing the card down...

- -Andy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmC2j4ACgkQOjLpvpq7dMpYPgCggTzbucu4IBIK2qQq6V3qEIYi
w9sAn3/8N0O7eoWXIETHciuKd8fzG4UZ
=+iQF
-----END PGP SIGNATURE-----

_______________________________________________
devel mailing list
[e-mail]
https://lists.openmoko.org/mailman/listinfo/devel