Mailinglist Archive: opensuse-bugs (4256 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=738604

https://bugzilla.novell.com/show_bug.cgi?id=738604#c0


           Summary: systemd corrupts disk and dumps core when ntp is
                    started
    Classification: openSUSE
           Product: openSUSE 12.1
           Version: Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Basesystem
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: devel@xxxxxxxxxx
         QAContact: qa@xxxxxxx
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:12.0a1) Gecko/20111223
Firefox/12.0a1

root@kegel:~ # /etc/init.d/ntp start
redirecting to systemctl
[  126.021306] systemd[1]: systemd-modules-load.service: main process exited,
code=exited, status=1
[  126.040162] udevd[715]: starting version 173
[  126.044096] systemd[1]: Unit systemd-modules-load.service entered failed
state.
[  126.151598] systemd-readahead-collect[739]: Disabling readahead collector
due to execution in virtualized environment.
systemd-fsck[725]: /dev/sda1: Superblock last mount time (Mon Dec 26 18:53:00
2011,[  126.244629] systemd-fsck[725]: /dev/sda1: Superblock last mount time
(Mon Dec 26 18:53:00 2011,

systemd-fsck[725]: now = Mon Nov  7 00:02:04 2011) is in the future.[ 
126.247586] systemd-fsck[725]: now = Mon Nov  7 00:02:04 2011) is in the
future.

systemd-fsck[725]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.[ 
126.252062] systemd-fsck[725]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck
MANUALLY.

systemd-fsck[725]: (i.e., without -a or -p options)
[  126.263233] systemd-fsck[725]: (i.e., without -a or -p options)
[  126.355229] systemd-fsck[725]: fsck failed with error code 4.
[  126.357360] systemd-fsck[725]: Running request
emergency.target/start/isolate
[  126.391924] systemd[766]: Failed at step EXEC spawning /bin/plymouth: No
such file or directory
Welcome to emergency mode. Use "systemctl default" or ^D to activate default
mode.
udevd[715]: worker [756] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [757] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [759] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [763] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [764] did not accept message -1 (Connection refused), kill
it

Give root password for login: [  126.568785] udevd[715]: segfault at 24 ip
0000000000404574 sp 00007fffe92090f0 error 6 in udevd[400000+21000]
[  126.575152] systemd[1]: udev.service: main process exited, code=killed,
status=11
[  126.579137] systemd[1]: Unit udev.service entered failed state.


Reproducible: Always

Steps to Reproduce:
1. Have a system with a relatively slower clock
2. Boot, fsck will report the super block from the future
3. Go to the emergency shell, set up the network
4. Trigger the ntp service
Actual Results:  
Fsck is started, some udev voodoo is performed -> segfault, system becomes
unusable.


Expected Results:  
The clock should have been set according to an ntp reference time.

root@kegel:~ # /etc/init.d/ntp start
redirecting to systemctl
[  126.021306] systemd[1]: systemd-modules-load.service: main process exited,
code=exited, status=1
[  126.040162] udevd[715]: starting version 173
[  126.044096] systemd[1]: Unit systemd-modules-load.service entered failed
state.
systemd-fsck[725]: /dev/sda1: Superblock last mount time (Mon Dec 26 18:53:00
2011,[  126.244629] systemd-fsck[725]: /dev/sda1: Superblock last mount time
(Mon Dec 26 18:53:00 2011,

systemd-fsck[725]: now = Mon Nov  7 00:02:04 2011) is in the future.[ 
126.247586] systemd-fsck[725]: now = Mon Nov  7 00:02:04 2011) is in the
future.

systemd-fsck[725]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.[ 
126.252062] systemd-fsck[725]: /dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck
MANUALLY.

systemd-fsck[725]: (i.e., without -a or -p options)
[  126.263233] systemd-fsck[725]: (i.e., without -a or -p options)
[  126.355229] systemd-fsck[725]: fsck failed with error code 4.
[  126.357360] systemd-fsck[725]: Running request
emergency.target/start/isolate
[  126.391924] systemd[766]: Failed at step EXEC spawning /bin/plymouth: No
such file or directory
Welcome to emergency mode. Use "systemctl default" or ^D to activate default
mode.
udevd[715]: worker [756] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [757] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [759] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [763] did not accept message -1 (Connection refused), kill
it

udevd[715]: worker [764] did not accept message -1 (Connection refused), kill
it

Give root password for login: [  126.568785] udevd[715]: segfault at 24 ip
0000000000404574 sp 00007fffe92090f0 error 6 in udevd[400000+21000]
[  126.575152] systemd[1]: udev.service: main process exited, code=killed,
status=11
[  126.579137] systemd[1]: Unit udev.service entered failed state.

Will report the bug upstream as well.

-- 
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.