Hi Andi,
On Sat, Mar 29, 2008 at 07:15:35PM +0100, Andreas B. Mundt wrote:
thanks for your hint, but a search for CONFIG_ASH_READ_TIMEOUT gives:
...buildrom-devel$ egrep -r CONFIG_ASH_READ_TIMEOUT * deploy/config/busybox/.config:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/.svn/text-base/defconfig.svn-base:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/.svn/text-base/defconfig-serengeti_cheetah-x86_64.svn-base:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/defconfig-serengeti_cheetah-x86_64:CONFIG_ASH_READ_TIMEOUT=y packages/busybox/conf/defconfig:CONFIG_ASH_READ_TIMEOUT=y work/busybox/busybox-1.1.3/.config:CONFIG_ASH_READ_TIMEOUT=y work/busybox/busybox-1.1.3/include/bb_config.h:#define CONFIG_ASH_READ_TIMEOUT 1 work/busybox/busybox-1.1.3/include/config/config/ash/read/timeout.h:#define CONFIG_ASH_READ_TIMEOUT 1 work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_NCHARS) && defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#elif defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/ash.c:#if defined(CONFIG_ASH_READ_TIMEOUT) work/busybox/busybox-1.1.3/shell/Config.in:config CONFIG_ASH_READ_TIMEOUT work/busybox/busybox-1.1.3/.config.old:CONFIG_ASH_READ_TIMEOUT=y work/busybox/logs/build.log: Enable 'read -t S' support. (CONFIG_ASH_READ_TIMEOUT) [Y/n/?] y ....
so this seems not to be the reason.
Hmm, ok. Can you debug the lab environment? You could try to chroot into it on your build system, or else just comment out the kexec line and start a busybox shell instead on your target. You should then see what error 'read' is throwing.
Thanks, Ward.