Results 1 to 9 of 9

Thread: Boot hangs after recent update

  1. #1

    Default Boot hangs after recent update

    Hello,

    I need a little help with finding what is wrong. I manually installed the recent kernel update (4.1.31-30-default) yesterday and rebooted the machine (A rack-mounted HP ProLiant server with openSUSE Leap 42.1). The boot process hangs. The last messages are:

    Code:
    [ OK ] Reached Target Initrd Default File Systems.
    [ OK ] Reached Target Initrd Default Target.
    [ 23.555361] systemd-journald[379]: Received sigterm from PID 1 (systemd).
    [ 23.653023] random: non-blocking pool is initialized
    
    Welcome to openSUSE Leap 42.1 (x86_64)!
    Notes:
    • The messages above were obtained by removing "splash=silent quiet" in Grub2
    • Ctrl-Alt F1 works, but there is no login prompt. Ctrl-Alt Del does not work.
    • An older system (openSUSE 13.1) installed on a different partition boots OK so the hardware is OK.
    • The latest system logs are from the last shutdown; the boot does not produce any logs. At least I haven't found any by using the journalctl command on the Leap 42.1 logs from openSUSE 13.1.
    • The older kernel (4.1.27-27-default selected via the advanced options in Grub2) also hangs, the messages are similar.
    • The system doesn't boot to the single user mode (option "single") in Grub2.


    Any ideas how to continue? I'm going to get a list of updates that were installed since the last successful reboot.

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,076

    Default Re: Boot hangs after recent update

    Video card and driver???

  3. #3

    Default Re: Boot hangs after recent update

    Quote Originally Posted by gogalthorp View Post
    Video card and driver???
    Matrox G200 SE A and mga, see below.

    According to the "Journal", the last successful reboot was on August 17 2016. Many updates have been installed since this date. The mga_drv.so file is from 2013.

    Videocard ("hwinfo --gfxcard" in openSUSE 13.1):
    Code:
    27: PCI 200.0: 0300 VGA compatible controller (VGA)
      [Created at pci.319]
      Unique ID: B35A.eB9+Xpshw95
      Parent ID: QSNP.80FKr5NvfaC
      SysFS ID: /devices/pci0000:00/0000:00:1c.4/0000:02:00.0
      SysFS BusID: 0000:02:00.0
      Hardware Class: graphics card
      Model: "Matrox G200 SE A (PCI)"
      Vendor: pci 0x102b "Matrox Graphics, Inc."
      Device: pci 0x0522 "G200 SE A (PCI)"
      SubVendor: pci 0x103c "Hewlett-Packard Company"
      SubDevice: pci 0x0100 
      Revision: 0x02
      Driver: "mgag200"
      Driver Modules: "drm"
      Memory Range: 0xf9000000-0xf9ffffff (ro,non-prefetchable)
      Memory Range: 0xfb9fc000-0xfb9fffff (rw,non-prefetchable)
      Memory Range: 0xfb000000-0xfb7fffff (rw,non-prefetchable)
      Memory Range: 0xfb9e0000-0xfb9effff (ro,non-prefetchable,disabled)
      IRQ: 16 (no events)
      I/O Ports: 0x3c0-0x3df (rw)
      Module Alias: "pci:v0000102Bd00000522sv0000103Csd00000100bc03sc00i00"
      Driver Info #0:
        XFree86 v4 Server Module: mga
        Extensions: 
        Options: NoHal
        XF86Config Entry: Option "XaaNoScreenToScreenCopy"
      Config Status: cfg=no, avail=yes, need=no, active=unknown
      Attached to: #19 (PCI bridge)
    
    Primary display adapter: #27
    Video driver (taken from Xorg.0.log in Leap 42.1)
    Code:
    [    24.442] 
    X.Org X Server 1.17.2
    Release Date: 2015-06-16
    [    24.442] X Protocol Version 11, Revision 0
    [    24.442] Build Operating System: openSUSE SUSE LINUX
    [    24.442] Current Operating System: Linux photon 4.1.27-27-default #1 SMP PREEMPT Fri Jul 15 12:46:41 UTC 2016 (84ae57e) x86_64
    [    24.442] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.1.27-27-default root=UUID=f315b3a0-223f-4898-9b3f-56b692bd4e19 resume=/dev/disk/by-uuid/8a8ce957-5f58-4002-bec3-e5d4ef2303ae splash=silent quiet show
    opts
    ...
    [    24.482] (II) LoadModule: "mga"
    [    24.482] (II) Loading /usr/lib64/xorg/modules/drivers/mga_drv.so
    [    24.482] (II) Module mga: vendor="X.Org Foundation"
    [    24.482]    compiled for 1.17.2, module version = 1.6.4
    [    24.482]    Module class: X.Org Video Driver
    [    24.482]    ABI class: X.Org Video Driver, version 19.0
    [    24.482] (II) LoadModule: "modesetting"
    [    24.483] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
    [    24.483] (II) Module modesetting: vendor="X.Org Foundation"
    [    24.483]    compiled for 1.17.2, module version = 1.17.2
    [    24.483]    Module class: X.Org Video Driver
    [    24.483]    ABI class: X.Org Video Driver, version 19.0
    [    24.483] (II) LoadModule: "fbdev"
    [    24.483] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    [    24.483] (II) Module fbdev: vendor="X.Org Foundation"
    [    24.483]    compiled for 1.17.2, module version = 0.4.4
    [    24.483]    Module class: X.Org Video Driver
    [    24.483]    ABI class: X.Org Video Driver, version 19.0
    [    24.483] (II) LoadModule: "vesa"
    [    24.483] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    [    24.483] (II) Module vesa: vendor="X.Org Foundation"
    [    24.483]    compiled for 1.17.2, module version = 2.3.4
    [    24.483]    Module class: X.Org Video Driver
    [    24.483]    ABI class: X.Org Video Driver, version 19.0
    [    24.483] (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
            mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI,
            mgag200 SE A PCI, mgag200 SE B PCI, mgag200 EV Maxim,
            mgag200 ER SH7757, mgag200 eW Nuvoton, mgag200eH, mgag400, mgag550
    [    24.483] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [    24.483] (II) FBDEV: driver for framebuffer: fbdev
    [    24.483] (II) VESA: driver for VESA chipsets: vesa
    ...

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,076

    Default Re: Boot hangs after recent update

    Ouch matrox is least supported GPU hardware there is IMO. Maybe drop back to previous kernel???

  5. #5

    Default Re: Boot hangs after recent update

    Quote Originally Posted by gogalthorp View Post
    Maybe drop back to previous kernel???
    The previous kernel (4.1.27-27-default) has the same problem. It hangs at the same place. Anyway, the system is a computational server so it does not need any graphics.

    I've turned on systemd's debug messages and redirected them to the console by adding "systemd.log_target=console systemd.log_level=debug" (and removing "splash=silent quiet") in Grub2. The last messages are (I used OCR on a screen photo so some letters may be incorrectly recognised):
    Code:
    Set up TFD_TIMER_CANCEL_ON_SET timerfd.
     Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 582
    Spawned /usr/lib/systemd/systen-generators/ibft-rule-generator as 583
     Spawned /usr/lib/systemd/system-generators/systemd-system-update generator as 584
     Spawned /usr/lib/systemd/system-generators/systemd-insserv-generator as 585
     Spawned /usr/lib/systemd/system-generators/systemd-gpt-auto-generator as 586
     Spawned /usr/lib/systend/system-generators/systemd-efi-boot-generator as 587
     Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 588
     Spawned /usr/lib/systemd/systen-generators/systemd-fstab-generator as 589
     Spawned /usr/lib/systemd/system-generators/systemd-rc-local-generator as 590
     Spawned /usr/lib/systemd/system-generators/nfs-server-generator as 591
     Spawned /usr/lib/systend/system-generators/lvm2-activation-generator as 597
    /usr/lib/systemd/system-generators/systemd-getty-generator exited successfully.
     /usr/lib/systemd/system-generators/ibft-rule-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-system-update-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-insserv-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-gpt-auto-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-efi-boot-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-cryptsetup-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-fstab-generator exited successfully.
     /usr/lib/systemd/system-generators/systemd-rc-local-generator exited successfully.
    All the spawned generators finished except of the nfs-server-generator and lvm2-activation-generator. The nfs-kernel-server RPM was updated on September 26 (according to /var/log/zypp/history). I suspect this package may cause the problem. I'm going to look at it.

  6. #6

    Default Re: Boot hangs after recent update

    Systemd has a problem with the new NFS server; the NFS server seems to wait for something that is not available at the moment when the server starts. I'll investigate the problem during the weekend and, if needed, I'll send a bug report.

    I used the following workaround: I moved /etc/exports to /etc/exports.org and started Leap 42.1. (The boot process did not not hang in this case; it continued as expected.) In the running system, I restored /etc/exports and manually started the NFS server using "systemctl restart nfs-server.service". The NFS server seems to work OK now.

    Anyway, I'm surprised that this problem hasn't been reported by more people. Perhaps I use an unusual configuration.

  7. #7

    Default Re: Boot hangs after recent update

    Quote Originally Posted by amalusek View Post
    Anyway, I'm surprised that this problem hasn't been reported by more people. Perhaps I use an unusual configuration.
    I've failed to replicate the problem in VirtualBox; the boot process does not hang there. I can't experiment with the HP server now, it is a production machine. I'll update this thread when I know more about the problem.

  8. #8
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,882
    Blog Entries
    14

    Default Re: Boot hangs after recent update

    Quote Originally Posted by amalusek View Post
    Systemd has a problem with the new NFS server; the NFS server seems to wait for something that is not available at the moment when the server starts. I'll investigate the problem during the weekend and, if needed, I'll send a bug report.

    I used the following workaround: I moved /etc/exports to /etc/exports.org and started Leap 42.1. (The boot process did not not hang in this case; it continued as expected.) In the running system, I restored /etc/exports and manually started the NFS server using "systemctl restart nfs-server.service". The NFS server seems to work OK now.

    Anyway, I'm surprised that this problem hasn't been reported by more people. Perhaps I use an unusual configuration.
    You can find out what it is the system is waiting for:
    Code:
    systemd-analyze blame
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  9. #9

    Default Re: Boot hangs after recent update

    The problem is gone. After an unplanned power outage, the computer booted up without hanging. Most likely an update (I haven't investigated which one) fixed the problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •