what about these boot problems

Hi,
I frequently face problems when booting the beagle board and want to
know whether this may be a hardware issue or is it related (and perhaps
known) to the kernel and/or toolchain.

I am using Angstrom's 2.6.25+2.6.26-rc9+r41+g linux kernel and boot
problems can appear at 3 different stages.

1) Execution (seemingly) stops after the kernel is uncompressed:

Uncompressing
Linux.............................................................

2) Sometimes it stops after this:
Freeing init memory: 172K

INIT: version 2.86 booting

Starting the hotplug events dispatcher udevd

Synthesizing the initial hotplug events

3) Sometimes I can start until the login appears (on the serial console)
but then the serial connection fails (no I/O any more) and the NOHZ
warning (?) is printed.

Angstrom 2008.1-test-20080704 beagleboard ttyS2

beagleboard login: NOHZ: local_softirq_pending 100

NOHZ: local_softirq_pending 100

NOHZ: local_softirq_pending 100

NOHZ: local_softirq_pending 100

NOHZ: local_softirq_pending 100

NOHZ: local_softirq_pending 100

This can also happen after being logged into the system. Interestingly
this allowed me to confirm that the system is not hung: If I manage to
configure usb0 I can still log in via SSH when the serial console does
not work any more. Some problem in the Kernel's serial driver then?

Please write whether one or more of these issues are known and whether
someone else is experiencing them, too. Please also state whether I
should file a bug and/or start investigating an issue in detail.

Regards
Robert

You should see i2c errors in uboot (if you use sakomans 1.3.x uboot,
'bitbake u-boot' to build it) if the above happens. A cold boot
usually makes these go away.

regards,

Koen

Robert Schuster wrote:

Hi,
I frequently face problems when booting the beagle board and want to
know whether this may be a hardware issue or is it related (and perhaps
known) to the kernel and/or toolchain.

I am using Angstrom's 2.6.25+2.6.26-rc9+r41+g linux kernel and boot
problems can appear at 3 different stages.

1) Execution (seemingly) stops after the kernel is uncompressed:

Uncompressing
Linux.............................................................

If you like to compile your own kernel, you could enable CONFIG_DEBUG_LL what might give some more details. Not sure if it is already enabled in the image you use, though.

2) Sometimes it stops after this:
Freeing init memory: 172K
INIT: version 2.86 booting
Starting the hotplug events dispatcher udevd
Synthesizing the initial hotplug events

I see this, too.

Cheers

Dirk