Hello,
I am trying to build the upstream kernel like linux-linaro-3.0, linux(linus), linux-next, linux-arm-soc for next builds with omap2plus defconfig, Create a kernel debian package and use this debian package to verify the build. The builds are enabled with ext3 file system.
The scripts that is used to build the kernel for example is http://bazaar.launchpad.net/~linaro-infrastructure/linaro-ci/lci-build-tools... . The builddeb used contains modifications submitted to work for cross compilation and the changes are available at http://permalink.gmane.org/gmane.linux.linaro.devel/7443. Other than that there is no hand made changes to any files.
An example hwpack that I created using the linaro-hwpack-replace can be downloaded from http://ci.linaro.org/kernel_hwpack/panda/hwpack_linaro-panda_20110927-0741_a... . This consists of the kernel debian package built from linux-linaro-3.0 with omap2 defconfig to work on a panda board.
[PS: linaro-hwpack-replace which is part of the linaro-image-tools is a tool that replaces the old kernel debian package in a given hwpack with the supplied kernel debian package ]
I see that the kernel builds successfully, and the hwpack containing this newly built kernel debian package boots fine on the boards, but it fails to execute the reboot command and it hangs with the following message:
#################################################################
The system is going down for reboot NOW! root@linaro-nano:~# init: tty4 main process (3205) killed by TERM signal
init: tty5 main process (3211) killed by TERM signal init: auto-serial-console main process (3213) killed by TERM signal init: tty2 main process (3215) killed by TERM signal init: tty3 main process (3218) killed by TERM signal
init: tty6 main process (3224) killed by TERM signal init: openvt main process (3276) killed by TERM signal init: plymouth-upstart-bridge main process (3341) terminated with status 1 [ OK ]ing all remaining processes to terminate...
[ OK ] processes ended within 1 seconds.... [ OK ]onfiguring network interfaces... [ OK ]ctivating swap... [ OK ]ounting weak filesystems... * Will now restart [ 2216.347167] Restarting system.
#################################################################
The board needs to be hard reset to boot back to the system. Has anyone seen this issue before, or do you suspect some problem with the kernel I built ?? I would be very thankful if someone can help me triage the problem.
Thanks and Regards, Deepti.
Just out of curiosity, have you tried building an image locally using this hwpack and booting it?
Thanks, Paul Larson
On Tue, Sep 27, 2011 at 8:55 AM, Deepti Kalakeri <deepti.kalakeri@linaro.org
wrote:
Hello,
I am trying to build the upstream kernel like linux-linaro-3.0, linux(linus), linux-next, linux-arm-soc for next builds with omap2plus defconfig, Create a kernel debian package and use this debian package to verify the build. The builds are enabled with ext3 file system.
The scripts that is used to build the kernel for example is http://bazaar.launchpad.net/~linaro-infrastructure/linaro-ci/lci-build-tools... . The builddeb used contains modifications submitted to work for cross compilation and the changes are available at http://permalink.gmane.org/gmane.linux.linaro.devel/7443. Other than that there is no hand made changes to any files.
An example hwpack that I created using the linaro-hwpack-replace can be downloaded from http://ci.linaro.org/kernel_hwpack/panda/hwpack_linaro-panda_20110927-0741_a... . This consists of the kernel debian package built from linux-linaro-3.0 with omap2 defconfig to work on a panda board.
[PS: linaro-hwpack-replace which is part of the linaro-image-tools is a tool that replaces the old kernel debian package in a given hwpack with the supplied kernel debian package ]
I see that the kernel builds successfully, and the hwpack containing this newly built kernel debian package boots fine on the boards, but it fails to execute the reboot command and it hangs with the following message:
#################################################################
The system is going down for reboot NOW! root@linaro-nano:~# init: tty4 main process (3205) killed by TERM signal
init: tty5 main process (3211) killed by TERM signal init: auto-serial-console main process (3213) killed by TERM signal init: tty2 main process (3215) killed by TERM signal init: tty3 main process (3218) killed by TERM signal
init: tty6 main process (3224) killed by TERM signal init: openvt main process (3276) killed by TERM signal init: plymouth-upstart-bridge main process (3341) terminated with status 1 [ OK ]ing all remaining processes to terminate...
[ OK ] processes ended within 1 seconds.... [ OK ]onfiguring network interfaces... [ OK ]ctivating swap... [ OK ]ounting weak filesystems...
- Will now restart
[ 2216.347167] Restarting system.
#################################################################
The board needs to be hard reset to boot back to the system. Has anyone seen this issue before, or do you suspect some problem with the kernel I built ?? I would be very thankful if someone can help me triage the problem.
Thanks and Regards, Deepti.
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Hello Paul,
On Wed, Sep 28, 2011 at 7:05 AM, Paul Larson paul.larson@linaro.org wrote:
Just out of curiosity, have you tried building an image locally using this hwpack and booting it?
I have not tried this specifically, but I have tried other hwpacks coming out of the same job.
Thanks, Paul Larson
Thanks and Regards, Deepti.
On Tue, Sep 27, 2011 at 8:55 AM, Deepti Kalakeri < deepti.kalakeri@linaro.org> wrote:
Hello,
I am trying to build the upstream kernel like linux-linaro-3.0, linux(linus), linux-next, linux-arm-soc for next builds with omap2plus defconfig, Create a kernel debian package and use this debian package to verify the build. The builds are enabled with ext3 file system.
The scripts that is used to build the kernel for example is http://bazaar.launchpad.net/~linaro-infrastructure/linaro-ci/lci-build-tools... . The builddeb used contains modifications submitted to work for cross compilation and the changes are available at http://permalink.gmane.org/gmane.linux.linaro.devel/7443. Other than that there is no hand made changes to any files.
An example hwpack that I created using the linaro-hwpack-replace can be downloaded from http://ci.linaro.org/kernel_hwpack/panda/hwpack_linaro-panda_20110927-0741_a... . This consists of the kernel debian package built from linux-linaro-3.0 with omap2 defconfig to work on a panda board.
[PS: linaro-hwpack-replace which is part of the linaro-image-tools is a tool that replaces the old kernel debian package in a given hwpack with the supplied kernel debian package ]
I see that the kernel builds successfully, and the hwpack containing this newly built kernel debian package boots fine on the boards, but it fails to execute the reboot command and it hangs with the following message:
#################################################################
The system is going down for reboot NOW! root@linaro-nano:~# init: tty4 main process (3205) killed by TERM signal
init: tty5 main process (3211) killed by TERM signal init: auto-serial-console main process (3213) killed by TERM signal init: tty2 main process (3215) killed by TERM signal init: tty3 main process (3218) killed by TERM signal
init: tty6 main process (3224) killed by TERM signal init: openvt main process (3276) killed by TERM signal init: plymouth-upstart-bridge main process (3341) terminated with status 1 [ OK ]ing all remaining processes to terminate...
[ OK ] processes ended within 1 seconds.... [ OK ]onfiguring network interfaces... [ OK ]ctivating swap... [ OK ]ounting weak filesystems...
- Will now restart
[ 2216.347167] Restarting system.
#################################################################
The board needs to be hard reset to boot back to the system. Has anyone seen this issue before, or do you suspect some problem with the kernel I built ?? I would be very thankful if someone can help me triage the problem.
Thanks and Regards, Deepti.
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On Wed, Sep 28, 2011 at 7:10 AM, Deepti Kalakeri <deepti.kalakeri@linaro.org
wrote:
Hello Paul,
On Wed, Sep 28, 2011 at 7:05 AM, Paul Larson paul.larson@linaro.orgwrote:
Just out of curiosity, have you tried building an image locally using this hwpack and booting it?
I have not tried this specifically, but I have tried other hwpacks coming out of the same job.
Can you please try and report if this issue is reproducible locally?
On Wed, Sep 28, 2011 at 8:43 PM, Alexander Sack asac@linaro.org wrote:
On Wed, Sep 28, 2011 at 7:10 AM, Deepti Kalakeri < deepti.kalakeri@linaro.org> wrote:
Hello Paul,
On Wed, Sep 28, 2011 at 7:05 AM, Paul Larson paul.larson@linaro.orgwrote:
Just out of curiosity, have you tried building an image locally using this hwpack and booting it?
I have not tried this specifically, but I have tried other hwpacks coming out of the same job.
Can you please try and report if this issue is reproducible locally?
Did you mean to say to use the hwpack and try to boot it locally on the board and verify if the reboot fails. If yes, then I have tested the hwpack locally. I created the SD image using the lmc and then booted the board with the image. Once the system was up and running I tried to reboot it. And it stalled at the error I pointed in the first mail.
Thanks and Regards, Deepti.
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Wed, Sep 28, 2011 at 5:35 PM, Deepti Kalakeri <deepti.kalakeri@linaro.org
wrote:
On Wed, Sep 28, 2011 at 8:43 PM, Alexander Sack asac@linaro.org wrote:
On Wed, Sep 28, 2011 at 7:10 AM, Deepti Kalakeri < deepti.kalakeri@linaro.org> wrote:
Hello Paul,
On Wed, Sep 28, 2011 at 7:05 AM, Paul Larson paul.larson@linaro.orgwrote:
Just out of curiosity, have you tried building an image locally using this hwpack and booting it?
I have not tried this specifically, but I have tried other hwpacks coming out of the same job.
Can you please try and report if this issue is reproducible locally?
Did you mean to say to use the hwpack and try to boot it locally on the board and verify if the reboot fails. If yes, then I have tested the hwpack locally. I created the SD image using the lmc and then booted the board with the image. Once the system was up and running I tried to reboot it. And it stalled at the error I pointed in the first mail.
Right. that's a good confirm that this is a real bug/regression in the upstream kernel trees :). \o/
Deepak, where do we file/track such issues seen in the lab? Will you take this over from here?
-
Alexander Sack -
Deepti Kalakeri -
Paul Larson