Just posted this on the systemd mailing list.
It seems that I didn't go through enough testing on the
systemd-gnome-image built by OE. The success I reported with boot SD
card instead of over NFS was just a got-lucky case. So SD Card and NFS
alike, the boot still hangs.
Koen and others, could you try my image?
http://www.beagleboard.org/~joelf/images/Angstrom-systemd-GNOME-image-eglibc-ipk-v2011.08-core-beagleboard.rootfs.tar.bz2
This is built from meta-angstrom master HEAD
(7c54f644aaf7a5cade2b405bd4a2a7316d3a9dfb).
"bitbake systemd-gnome-image".
Also, Is there a simple way to switch to sysvinit so that I can
atleast be able to boot an oe-core built image and use it as a
baseline? I tried setting IMAGE_INIT_MANAGER = "sysvinit" and removing
all systemd dependent packages, but the image failed to build at the
opkg install sysvinit stage saying that certain directories such as
"/var/cache" already exist.
Note: every once in a while with 3.0.1 that's in this image, I get the
power management lookup table kernel-panic. But I can live that for
now.
Thanks,
Joel
Just posted this on the systemd mailing list.
Are these the right lists on this thread? Just not sure if some folks
on the CC might consider this too off-topic.
It seems that I didn't go through enough testing on the
systemd-gnome-image built by OE. The success I reported with boot SD
card instead of over NFS was just a got-lucky case. So SD Card and NFS
alike, the boot still hangs.
Koen and others, could you try my image?
http://www.beagleboard.org/~joelf/images/Angstrom-systemd-GNOME-image-eglibc-ipk-v2011.08-core-beagleboard.rootfs.tar.bz2
Can you provide an SD card image as well? Running mkcard.txt or
linaro-create-image is often error prone and time consuming.
This is built from meta-angstrom master HEAD
(7c54f644aaf7a5cade2b405bd4a2a7316d3a9dfb).
"bitbake systemd-gnome-image".
Also, Is there a simple way to switch to sysvinit so that I can
atleast be able to boot an oe-core built image and use it as a
baseline? I tried setting IMAGE_INIT_MANAGER = "sysvinit" and removing
all systemd dependent packages, but the image failed to build at the
opkg install sysvinit stage saying that certain directories such as
"/var/cache" already exist.
Note: every once in a while with 3.0.1 that's in this image, I get the
power management lookup table kernel-panic. But I can live that for
now.
Thanks,
Joel
Hi, I'm using kernel 3.0.1 and systemd, the boot process hangs. I am
booting from an SD Card using the BeagleBoard.
I am passing "systemd.log_target=kmsg systemd.log_level=debug" in my
boot arguments but I don't see any debug messages.
Could anyone help me out? Thanks
Starting udev Coldplug all Devices...
Starting udev Kernel Device Manager...
Started Load Kernel Modules.
Started Set Up Additional Binary Formats.
[ 4.701141] udevd[52]: starting version 173
Started Apply Kernel Variables.
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Starting /var/volatile...
Starting /tmp...
Starting Setup Virtual Console...
Started Opkg first boot configure.
Starting Remount API VFS...
Starting File System Check on Root Device...
Starting Lock Directory...
Starting Media Directory...
Started Runtime Directory.
Started udev Kernel Device Manager.
Started /var/volatile.
[ 4.932647] systemd-fsck[61]: Root directory is writable, skipping check.
Started /tmp.
Started File System Check on Root Device.
Started Lock Directory.
Started Remount API VFS.
Started Media Directory.
Starting Remount Root FS...
Starting /var/tmp...
Started /var/tmp.
Starting Stdio Syslog Bridge...
[ 5.081146] systemd-vconsole-setup[57]: /usr/bin/loadkeys failed
with error code 1.
Started Stdio Syslog Bridge.
[ 5.135314] systemd-vconsole-setup[57]: cannot open file us
Started udev Coldplug all Devices.
Started Setup Virtual Console.
Started Remount Root FS.
Starting Load Random Seed...
Starting Recreate Volatile Files and Directories...
Started Load Random Seed.
Started Recreate Volatile Files and Directories.
Starting Console System Startup Logging...
Starting ntpd.service...
Starting xinetd.service...
Started SSH Key Generation.
Starting D-Bus System Message Bus...
Starting Login Service...
Starting Permit User Sessions...
Started Permit User Sessions.
Starting ntpd: Started Console System Startup Logging.
Started D-Bus System Message Bus.
Starting internet superserver: xinetd.
[ 5.773284] ntpd[137]: ntpd 4.2.6p3@1.2290 Fri Jul 29 17:35:18 UTC 2011 (2)
done
[ 5.809906] ntpd[154]: proto: precision = 30.517 usec
[ 5.829437] ntpd[154]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
[ 5.849182] xinetd[156]: 156 {init_services} no services. Exiting...
[ 5.864044] ntpd[154]: Listen and drop on 1 v6wildcard :: UDP 123
[ 5.882141] ntpd[154]: Listen normally on 2 lo 127.0.0.1 UDP 123
[ 5.906188] ntpd[154]: Listen normally on 3 lo ::1 UDP 123
[ 5.935424] ntpd[154]: peers refreshed
[ 5.939361] ntpd[154]: Deferring DNS for pool.ntp.org 1
[ 6.385498] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
[ 7.948211] ntpd_intres[162]: host name not found: pool.ntp.org
How long did you wait here for a timeout of some kind? What happens
here different when it works? Did you try SysRq? What is the state
of the board and native console?
Just posted this on the systemd mailing list.
Are these the right lists on this thread? Just not sure if some folks
on the CC might consider this too off-topic.
It seems that I didn't go through enough testing on the
systemd-gnome-image built by OE. The success I reported with boot SD
card instead of over NFS was just a got-lucky case. So SD Card and NFS
alike, the boot still hangs.
Koen and others, could you try my image?
http://www.beagleboard.org/~joelf/images/Angstrom-systemd-GNOME-image-eglibc-ipk-v2011.08-core-beagleboard.rootfs.tar.bz2
Can you provide an SD card image as well? Running mkcard.txt or
linaro-create-image is often error prone and time consuming.
Could you untar the file I uploaded into the FS partition?
You could use the image from here:
http://circuitco.com/support/files/BeagleboardxM/xMc_4_25.zip
[..]
Starting Login Service...
Starting Permit User Sessions...
Started Permit User Sessions.
Starting ntpd: Started Console System Startup Logging.
Started D-Bus System Message Bus.
Starting internet superserver: xinetd.
[ 5.773284] ntpd[137]: ntpd 4.2.6p3@1.2290 Fri Jul 29 17:35:18 UTC 2011 (2)
done
[ 5.809906] ntpd[154]: proto: precision = 30.517 usec
[ 5.829437] ntpd[154]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
[ 5.849182] xinetd[156]: 156 {init_services} no services. Exiting...
[ 5.864044] ntpd[154]: Listen and drop on 1 v6wildcard :: UDP 123
[ 5.882141] ntpd[154]: Listen normally on 2 lo 127.0.0.1 UDP 123
[ 5.906188] ntpd[154]: Listen normally on 3 lo ::1 UDP 123
[ 5.935424] ntpd[154]: peers refreshed
[ 5.939361] ntpd[154]: Deferring DNS for pool.ntp.org 1
[ 6.385498] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
[ 7.948211] ntpd_intres[162]: host name not found: pool.ntp.org
How long did you wait here for a timeout of some kind? What happens
here different when it works? Did you try SysRq? What is the state
of the board and native console?
I waited for 15 minutes. The MMC card LED doesn't glow indicating no
activity. The console has hung with the messages above. I tried sysrq
but there is no response. CONFIG_MAGIC_SYSRQ=y in my .config
Thanks,
Joel
It seems the rtc twl patch was causing problems so I've removed it and
uploaded a new image [1]. Could you try it?
Steve has suggested to apply a newer version patch but for the
purposes of debugging systemd so I will try that, but for now I've
dropped it.
Thanks,
Joel
[1] http://www.beagleboard.org/~joelf/images/Angstrom-systemd-GNOME-image-eglibc-ipk-v2011.08-core-beagleboard.rootfs-no-rtctwl.tar.bz2
Sorry, I meant that for the purposes of debugging the boot hang issues
we're seeing, I've dropped the patch from my tree for now.
Thanks,
Joel