4.15 based test kernel for PVE 5.x available

Discussion in 'Proxmox VE: Installation and configuration' started by fabian, Mar 12, 2018.

  1. Sibul

    Sibul New Member

    Joined:
    May 3, 2018
    Messages:
    5
    Likes Received:
    0
    So do I, but for history: an Fujitsu Primergy TX150 S7 booted.
     
  2. timota

    timota New Member

    Joined:
    Oct 14, 2011
    Messages:
    9
    Likes Received:
    0
    after latest upgrade to 4.15.15-1-pve kernel on server DL180 G6, with Array HP410 - server wont start.
    some console messages on screenshot
     

    Attached Files:

  3. rezzo

    rezzo New Member

    Joined:
    Oct 9, 2015
    Messages:
    2
    Likes Received:
    0
    I can confirm the regression. I can't boot a HP DL380 G7 with a LSI SAS2008 controller (mpt2sas) on 4.15.15-1-pve kernel.

    Boot fails and the busybox prompt appears. The manual `zpool import` command doesn't work because the rpool cannot be found, so it doesn't seem a timeout problem. The busybox shell is also littered by the same "Tainted IO" timeout errors as reported by @timota, at regular intervals.

    I had to rollback to 4.13.16-2-pve, which works fine.
     
  4. jeronimo89

    jeronimo89 New Member

    Joined:
    May 3, 2018
    Messages:
    1
    Likes Received:
    0
    the same problem here with DELL Poweredge R720/Perc H710mini
     
  5. tkitops

    tkitops New Member

    Joined:
    May 3, 2018
    Messages:
    1
    Likes Received:
    3
    Rendering one of the most common server raid adapters out there unbootable (as evidenced by the wide range of very common server types already reported to have issues) is not exactly to be dismissed as "any issues on all possible hardware" so yeah, I do question how obvious the choice was to promote this one to default.

    Still, some of the 4.13 issues were biting us too, so the flight forward to 4.15.17 is much anticipated :) Do you have an ETA on public availability of that one?
     
    rezzo, elmacus and Hartwin like this.
  6. janos

    janos Member

    Joined:
    Aug 24, 2017
    Messages:
    148
    Likes Received:
    13
    Me too, HP BL460c G7 with P410i.
     
  7. Hartwin

    Hartwin New Member

    Joined:
    May 4, 2018
    Messages:
    4
    Likes Received:
    1
    Me too, HP ML350p G8 with P420i.
    This happens with both of the two machines I'm running.
    The screen looks exactly like the one attached by timota to #62.
    Additionally, the first message after power on was
    error parsing pcc subspaces from pcct
    Couldn't get size: [...]
    reading all physical volumes. This may take a while...
     
    #67 Hartwin, May 4, 2018
    Last edited: May 4, 2018
  8. Ivelok

    Ivelok New Member

    Joined:
    Feb 7, 2017
    Messages:
    3
    Likes Received:
    1
    +1. HP BL460c gen8 + HP SA p220i.

    Bug in kernel.
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765232

    Fixed in Kernel 4.15.0-19.20.
     
    #68 Ivelok, May 4, 2018
    Last edited: May 4, 2018
    Hartwin likes this.
  9. martin

    martin Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    633
    Likes Received:
    319
    We just uploaded a new 4.15 kernel (pve-kernel-4.15.17-1-pve: 4.15.17-8) to pvetest, should fix your issue.

    Please test and give feedback, thx.
     
    chrone and fireon like this.
  10. Cyrgia

    Cyrgia New Member

    Joined:
    May 4, 2018
    Messages:
    3
    Likes Received:
    0
    It works perfectly for me.
    hardware: HP Proliant ML350p G8 with Smart Array P420i, 2 x E5-2680 v2
    Thanks a lot
     
  11. Ivelok

    Ivelok New Member

    Joined:
    Feb 7, 2017
    Messages:
    3
    Likes Received:
    1
    Yes! It works :)
     
  12. Anatolii

    Anatolii New Member

    Joined:
    May 4, 2018
    Messages:
    4
    Likes Received:
    0
    prnt.sc/jdo8rb

    Works.
    Hardware: IBM x3550 M3, LSI megaraid_sas
     
  13. Dark26

    Dark26 Member

    Joined:
    Nov 27, 2017
    Messages:
    71
    Likes Received:
    3
    I test the 4.15.15-1-pve kernel.

    And i can't compile the driver fore the network module realtek r8168

    Nehad a problem beforce with other kernel :

    root@prox7:~/Compilation/r8168-8.045.08# ./autorun.sh

    Check old driver and unload it.
    rmmod r8169
    Build the module and install
    make[3]: *** Aucune règle pour fabriquer la cible « /root/Compilation/r8168-8.045.08/src/r8168_n.o », nécessaire pour « /root/Compilation/r8168-8.045.08/src/r8168.o ». Arrêt.
    make[2]: *** [_module_/root/Compilation/r8168-8.045.08/src] Erreur 2
    make[1]: *** [modules] Erreur 2
    make: *** [modules] Erreur 2
    root@prox7:~/Compilation/r8168-8.045.08#

    in the log :
    vendredi 4 mai 2018, 19:10:54 (UTC+0200)
    make -C src/ clean
    make[1] : on entre dans le répertoire « /root/Compilation/r8168-8.045.08/src »
    make -C /lib/modules/4.15.15-1-pve/build SUBDIRS=/root/Compilation/r8168-8.045.08/src clean
    make[2] : on entre dans le répertoire « /usr/src/linux-headers-4.15.15-1-pve »
    CLEAN /root/Compilation/r8168-8.045.08/src/.tmp_versions
    make[2] : on quitte le répertoire « /usr/src/linux-headers-4.15.15-1-pve »
    make[1] : on quitte le répertoire « /root/Compilation/r8168-8.045.08/src »
    make -C src/ modules
    make[1] : on entre dans le répertoire « /root/Compilation/r8168-8.045.08/src »
    make -C /lib/modules/4.15.15-1-pve/build SUBDIRS=/root/Compilation/r8168-8.045.08/src modules
    make[2] : on entre dans le répertoire « /usr/src/linux-headers-4.15.15-1-pve »
    Makefile:1552 : la recette pour la cible « _module_/root/Compilation/r8168-8.045.08/src » a échouée
    make[2] : on quitte le répertoire « /usr/src/linux-headers-4.15.15-1-pve »
    Makefile:104 : la recette pour la cible « modules » a échouée
    make[1] : on quitte le répertoire « /root/Compilation/r8168-8.045.08/src »
    Makefile:40 : la recette pour la cible « modules » a échouée



    i try with r8168-dkms but the same


    Paramétrage de r8168-dkms (8.043.02-1) ...
    Loading new r8168-8.043.02 DKMS files...
    Building for 4.15.15-1-pve
    Building initial module for 4.15.15-1-pve
    Error! Bad return status for module build on kernel: 4.15.15-1-pve (x86_64)
    Consult /var/lib/dkms/r8168/8.043.02/build/make.log for more information.
    dpkg: erreur de traitement du paquet r8168-dkms (--configure) :
    le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
    Des erreurs ont été rencontrées pendant l'exécution :
    r8168-dkms
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    Paramétrage de r8168-dkms (8.043.02-1) ...
    Removing old r8168-8.043.02 DKMS files...

    ------------------------------
    Deleting module version: 8.043.02
    completely from the DKMS tree.
    ------------------------------
    Done.
    Loading new r8168-8.043.02 DKMS files...
    Building for 4.15.15-1-pve
    Building initial module for 4.15.15-1-pve
    Error! Bad return status for module build on kernel: 4.15.15-1-pve (x86_64)
    Consult /var/lib/dkms/r8168/8.043.02/build/make.log for more information.
    dpkg: erreur de traitement du paquet r8168-dkms (--configure) :
    le sous-processus script post-installation installé a retourné une erreur de sortie d'état 10
    Des erreurs ont été rencontrées pendant l'exécution :
    r8168-dkms
     
    #73 Dark26, May 4, 2018
    Last edited: May 4, 2018
  14. Dark26

    Dark26 Member

    Joined:
    Nov 27, 2017
    Messages:
    71
    Likes Received:
    3
    No a very good batch. A kernel panic this morning. back to the 4.13.16-2.
     
  15. raytracy

    raytracy New Member

    Joined:
    Mar 31, 2016
    Messages:
    19
    Likes Received:
    0
    I cannot boot with 4.15.15, and kernel stuck with reading my lvm root volume:
    (Dell R730xd + H730P mini)
    upload_2018-5-6_1-24-9.png

    BTW, I cannot find 4.15.17 with no-subscription repo?
    How can I skip the 4.15.15 and go forward to 4.15.17?
     
  16. GadgetPig

    GadgetPig Member

    Joined:
    Apr 26, 2016
    Messages:
    138
    Likes Received:
    19
    It's currently in pvetest repo only. If you wait awhile it should be in no-subscription repo soon. Otherwise use 4.13.16-2 for now
     
  17. fireon

    fireon Well-Known Member
    Proxmox Subscriber

    Joined:
    Oct 25, 2010
    Messages:
    2,962
    Likes Received:
    175
    So, not solved...
    Code:
    May 06 01:07:37 virtu01 pct[2340]: <root@pam> end task UPID:virtu01:00000A21:025B1AEF:5AEE3938:vzstart:104:root@pam: command 'systemctl start pve-container@104' failed: exit code 1
    May 06 01:07:37 virtu01 pct[2593]: command 'systemctl start pve-container@104' failed: exit code 1
    May 06 01:07:37 virtu01 systemd[1]: pve-container@104.service: Failed with result 'exit-code'.
    May 06 01:07:37 virtu01 systemd[1]: pve-container@104.service: Unit entered failed state.
    May 06 01:07:37 virtu01 systemd[1]: Failed to start PVE LXC Container: 104.
    May 06 01:07:37 virtu01 systemd[1]: pve-container@104.service: Killing process 2597 (lxc-start) with signal SIGKILL.
    May 06 01:07:37 virtu01 systemd[1]: pve-container@104.service: Control process exited, code=exited status=1
    May 06 01:07:37 virtu01 lxc-start[2595]: Additional information can be obtained by setting the --logfile and --logpriority options.
    May 06 01:07:37 virtu01 lxc-start[2595]: To get more details, run the container in foreground mode.
    May 06 01:07:37 virtu01 lxc-start[2595]: The container failed to start.
    May 06 01:07:37 virtu01 lxc-start[2595]: lxc-start: 104: lxccontainer.c: wait_on_daemonized_start: 824 Received container state "STOPPING" instead of "RUNNING"
    May 06 01:07:37 virtu01 zed[3233]: eid=257 class=history_event pool_guid=0x8BF9CFD7A2BDFFE2
    
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. janos

    janos Member

    Joined:
    Aug 24, 2017
    Messages:
    148
    Likes Received:
    13
    You can download and install it manually if you dont want to use pvetest repo otherwise::

    Code:
    wget http://download.proxmox.com/debian/pve/dists/stretch/pvetest/binary-amd64/pve-kernel-4.15.17-1-pve_4.15.17-8_amd64.deb
    dpkg -i pve-kernel-4.15.17-1-pve_4.15.17-8_amd64.deb
     
    GadgetPig likes this.
  19. udo

    udo Well-Known Member
    Proxmox Subscriber

    Joined:
    Apr 22, 2009
    Messages:
    5,835
    Likes Received:
    158
    Hi,
    with pve-kernel-4.15.17-1-pve_4.15.17-8_amd64.deb the Dell R620 boot perc raid-volumes again.

    Udo
     
    elmacus, GadgetPig and chrone like this.
  20. Tonmoy

    Tonmoy New Member

    Joined:
    Apr 27, 2018
    Messages:
    3
    Likes Received:
    0
    I've had kernel panic with HP DL360 G7 - P410i upgrading to 4.15.15, so running back to 4.15.13 now.

    Since 4.15.17 is available, anyone tried on similar hardware and had the issue fixed?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice