https://bugzilla.novell.com/show_bug.cgi?id=642289
https://bugzilla.novell.com/show_bug.cgi?id=642289#c30
--- Comment #30 from Moritz Duge 2011-03-22 19:34:30 UTC ---
Created an attachment (id=420761)
--> (http://bugzilla.novell.com/attachment.cgi?id=420761)
Bootup after update to sysvinit(-tools) v2.88-37.43.1 from main update repo,
with AppArmor disabled
Why chmod 755? After a
zypper in -f sysvinit-tools
the file /sbin/blogd had the permissions 700 !
Nevertheless, I tried it with both permissions modes and had the same results.
I also tried it a second time with AppArmor disabled (just had that idea - it's
that boot-screen you can see on the second picture). But it didn't worked
either.
Just this time it initialized my FritzCard ISDN-Controller and the "random
number generator" after the blogd error. But I remember that it initialized
some services of runlevel 5 some on some startup tests I did before a few days.
So it doesn't seem to be a certain point on startup, when blogd kills the
runlevel initialization!
My boot.msg:
..
<6>[ 9.517406] em28xx driver loaded
<6>[ 9.552242] em28xx-audio.c: probing for em28x1 non standard usbaudio
<6>[ 9.552312] em28xx-audio.c: Copyright (C) 2006 Markus Rechberger
<6>[ 9.552468] Em28xx: Initialized (Em28xx Audio Extension) extension
<6>[ 9.666632] usbcore: registered new interface driver hdj_mod
<4>[ 9.680674] zl10353_read_register: readreg error (reg=127, ret==-19)
<3>[ 9.680790] em28xx #0: /2: dvb frontend not attached. Can't attach xc3028
<6>[ 9.680864] Em28xx: Initialized (Em28xx dvb Extension) extension
<6>[ 9.759913] tvp5150 2-005c: tvp5150am1 detected.
<6>[ 9.945596] Adding 4192928k swap on /dev/sda5. Priority:-1 extents:1
across:4192928k
<4>[ 10.541152] device-mapper: ioctl: device doesn't appear to be in the dev
hash table.
<6>[ 10.805352] kjournald starting. Commit interval 15 seconds
<6>[ 10.805595] EXT3-fs (dm-2): using internal journal
<6>[ 10.805672] EXT3-fs (dm-2): mounted filesystem with ordered data mode
<6>[ 10.852203] fuse init (API version 7.15)
Kernel logging (ksyslog) stopped.
Kernel log daemon terminating.
Boot logging started on /dev/tty1(/dev/console) at Tue Mar 22 20:02:40 2011
Trying manual resume from
/dev/disk/by-uuid/7f41bc7c-0132-4a1a-b3de-45d5b3a2fd58
Invoking userspace resume from
/dev/disk/by-uuid/7f41bc7c-0132-4a1a-b3de-45d5b3a2fd58
resume: libgcrypt version: 1.4.6
Trying manual resume from
/dev/disk/by-uuid/7f41bc7c-0132-4a1a-b3de-45d5b3a2fd58
Invoking in-kernel resume from
/dev/disk/by-uuid/7f41bc7c-0132-4a1a-b3de-45d5b3a2fd58
Waiting for device /dev/disk/by-uuid/ea23481c-7061-4b71-9fc0-d18af2829156 to
appear: ok
fsck from util-linux 2.19
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -C0 /dev/sda1
root: clean, 410618/1640160 files, 3286852/6554512 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-uuid/ea23481c-7061-4b71-9fc0-d18af2829156
mount -o rw,acl,user_xattr -t ext3
/dev/disk/by-uuid/ea23481c-7061-4b71-9fc0-d18af2829156 /root
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.