Bug 728674 - sporadic boot failure, systemd race condition?
Summary: sporadic boot failure, systemd race condition?
Status: RESOLVED DUPLICATE of bug 724912
Alias: None
Product: openSUSE 12.1
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: x86-64 Other
: P2 - High : Normal (vote)
Target Milestone: ---
Assignee: Frederic Crozat
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-07 15:17 UTC by Roland Genske
Modified: 2011-11-30 11:51 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roland Genske 2011-11-07 15:17:21 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23

I get sporadic boot failures on a md-raid1 lvm server installation.
Here are the console boot messages in case of such failure:

root (hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-3.1.0-1.1-desktop  root=/dev/vg00/root console=tty0 console=tty
S0,57600 noresume splash=silent quiet
   [Linux-bzImage, setup=0x4200, size=0x4ba3d0]
initrd /initrd-3.1.0-1.1-desktop
   [Linux-initrd @ 0x375a2000, 0xa4d1ac bytes]
savedefault

[    0.356583] pci 0000:00:14.0: BAR 1: error updating (0xde000004 != 0x8000a014)
[    1.394057] ata1: softreset failed (device not ready)
[    1.404207] ata2: softreset failed (device not ready)
doing fast boot
Creating device nodes with udev
udevd[247]: failed to execute '/etc/sysconfig/network/scripts/ifup-sysctl' '/etc/sysconfig/network/scripts/ifup-sysctl lo -o hotplug': No such file or directory

  4 logical volume(s) in volume group "vg00" now active
  4 logical volume(s) in volume group "vg00" now active
  4 logical volume(s) in volume group "vg00" now active
resume device  not found (ignoring)
Waiting for device /dev/vg00/root to appear:  ok
fsck from util-linux 2.20.1
[/sbin/fsck.xfs (1) -- /] fsck.xfs -a /dev/mapper/vg00-root 
/sbin/fsck.xfs: XFS file system.
fsck succeeded. Mounting root device read-write.
Mounting root /dev/vg00/root
mount -o rw,defaults -t xfs /dev/vg00/root /root
fsck from util-linux 2.20.1
[/sbin/fsck.xfs (1) -- /usr] fsck.xfs -a /dev/dm-2 
/sbin/fsck.xfs: XFS file system.
Mounting /usr
[    7.079692] k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled
[    7.318958] SP5100 TCO timer: mmio address 0xfec000f0 already in use
systemd-fsck[746]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[749]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[740]: /dev/md0: clean, 40/66264 files, 43145/264180 blocks
[    8.806396] systemd[1]: Failed to enqueue OnFailure= job: Exec format error

Reproducible: Sometimes
Comment 1 Frederic Crozat 2011-11-07 16:07:03 UTC
although it is not crypto related, it is similar to bnc#724912

*** This bug has been marked as a duplicate of bug 724912 ***
Comment 2 Roland Genske 2011-11-30 10:48:01 UTC
Problem still happens in openSUSE 12.1 final.
System fails to boot about 3 times of 5. Very annoying. This is a remote server located in a datacenter.

Here are the console boot messages of the current system:

root (hd0,0)
 Filesystem type is ext2fs, partition type 0xfd
kernel /vmlinuz-3.1.0-1.2-default  root=/dev/vg00/root console=tty0 console=tty
S0,57600 noresume splash=silent quiet
   [Linux-bzImage, setup=0x4200, size=0x478630]
initrd /initrd-3.1.0-1.2-default
   [Linux-initrd @ 0x37550000, 0xa9f9ed bytes]

[    0.436423] pci 0000:00:14.0: BAR 1: error updating (0xde000004 != 0x8000a014)
[    1.680033] ata1: softreset failed (device not ready)
[    1.690187] ata2: softreset failed (device not ready)
doing fast boot
Creating device nodes with udev
udevd[288]: failed to execute '/etc/sysconfig/network/scripts/ifup-sysctl' '/etc/sysconfig/network/scripts/ifup-sysctl lo -o hotplug': No such file or directory

  26 logical volume(s) in volume group "vg00" now active
  26 logical volume(s) in volume group "vg00" now active
  26 logical volume(s) in volume group "vg00" now active
Waiting for device /dev/vg00/root to appear:  ok
fsck from util-linux 2.20.1
[/sbin/fsck.xfs (1) -- /] fsck.xfs -a /dev/mapper/vg00-root 
/sbin/fsck.xfs: XFS file system.
fsck succeeded. Mounting root device read-write.
Mounting root /dev/vg00/root
mount -o rw,defaults -t xfs /dev/vg00/root /root
fsck from util-linux 2.20.1
[/sbin/fsck.xfs (1) -- /usr] fsck.xfs -a /dev/dm-2 
/sbin/fsck.xfs: XFS file system.
Mounting /usr
[    8.172410] SP5100 TCO timer: mmio address 0xfec000f0 already in use
[    8.440633] k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled
systemd-fsck[971]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[973]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[986]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[996]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1006]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1018]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1020]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1034]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1037]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1041]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1055]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1058]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1063]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1067]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1139]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1142]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1146]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1149]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1176]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1179]: /sbin/fsck.xfs: XFS file system.
systemd-fsck[1181]: /sbin/fsck.xfs: XFS file system.
[   12.524536] systemd[1]: Failed to enqueue OnFailure= job: Exec format error
Comment 3 Frederic Crozat 2011-11-30 11:51:23 UTC
marking back as duplicate, it still looks like duplicate from 724912

please test the package from home:fcrozat:systemd / systemd

*** This bug has been marked as a duplicate of bug 724912 ***