Forums

An0nimen
An0nimen
Offline
Resolved
0 votes
ClearOS 7.4 ren fine until this big update came after that Kernel panic - not syncing: Fatal exception. If I manually select original kernel in grub boot menu it boots fine so I am wondering what can be done here? I have already tried fresh install in case there would be a problem during update that would cause new kernel not to be installed properly but same deal so it must be the new kernel in some way. My question is this fixable manually if I still have access trough old kernel that boots normally or is it OK to just keep on using old kernel and just set it as default in grub and ignore new kernel updates or is there a better solution?


In advance thanx for any pointer into how to fix this problem.


TY, An0nimen
Sunday, July 08 2018, 11:14 PM
Share this post:
Responses (8)
  • Accepted Answer

    Monday, July 09 2018, 12:27 PM - #Permalink
    Resolved
    0 votes
    Fixed mine before :) you fixed yours... thanks... just a comment that we both had the same issue...

    See my appends earlier in this thread and also https://www.clearos.com/clearfoundation/social/community/clearos-7-5-community-release#reply-224451
    The reply is currently minimized Show
  • Accepted Answer

    An0nimen
    An0nimen
    Offline
    Monday, July 09 2018, 11:49 AM - #Permalink
    Resolved
    0 votes
    Try to update your bios or maybe just reset it to default majbe it will help :) It is a simple and almost unbelievable fix but it seems to be working :) Wish I had tried that before I whipped old installation with all my custom settings tho ;) but I am already reinstalling it and it works no problem restarted and rebooted it bunch of times and with all updated installed being up to date all seems to be fine now.


    Good luck hope u fix your problem asap.


    an0nimen
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 09 2018, 11:41 AM - #Permalink
    Resolved
    0 votes
    Interesting TY, an0nimen

    I also took a photo using my phone of my screen showing the panic with kernel 3.10.0-862.6.3.v7.x86_64 - comparing it with yours, it is almost identical. Exact same call trace! Our boards have different manufacturers - but a common factor - both have an Intel J1X00 SoC installed...
    The reply is currently minimized Show
  • Accepted Answer

    An0nimen
    An0nimen
    Offline
    Monday, July 09 2018, 11:22 AM - #Permalink
    Resolved
    0 votes
    As of this moment the problem is now resolved for me! Turns out for me it was a bios related problem after all :) As I stated before i updated to latest bios to update CPU Microcode and that itself did not fix the problem but resetting the BIOS to bios defaults did fix it with no additional steps needed. So in my case it was BIOS related maybe even only needed a rest to BIOS defaults but I cant say that for sure since I already updated the bios before I reset to defaults.


    Anyway system boots/reboots with new kernel no problem all seems to be fine so thank all of you again for helping me find a solution!


    TY, an0nimen
    The reply is currently minimized Show
  • Accepted Answer

    An0nimen
    An0nimen
    Offline
    Monday, July 09 2018, 10:56 AM - #Permalink
    Resolved
    0 votes
    This is all I can get from my screen after booting new kernel. (screen linked)



    I also updated my bios on my GA-J1900N-D3V as somebody suggested it might help but no luck same error. If i use the workaround to set old kernel as default is there any major downsides to this and what would that mean for future updates of kernel and stability of the system?

    TY, an0nimen.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 09 2018, 08:59 AM - #Permalink
    Resolved
    0 votes
    I also get a kernel panic on a VM where I have kmod-tpe installed. In my case it panics with a message indicating it tpe so I am following up on the ElRepo mailing lists and the github tpe site. The panic is intermittent and it boots successfully more often than not. It has happened with all three 7.5 kernels since the beta was released. Annoyingly I cannot capture the text from the screen - only a screendump.

    @An0nimen, can you get any more info from the panic? Any form of dump?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 09 2018, 08:44 AM - #Permalink
    Resolved
    0 votes
    The reply is currently minimized Show
  • Accepted Answer

    Monday, July 09 2018, 05:12 AM - #Permalink
    Resolved
    0 votes
    Kernel panic on one of my systems here as well... see https://www.clearos.com/clearfoundation/social/community/clearos-7-5-community-release#reply-224401

    Here is my cheat sheet for setting the default kernel for booting...

    List kernels available (starts with zero)
    # grep '^menuentry' /boot/grub2/grub.cfg

    The /boot/grub2/grubenv file cannot be manually edited. Use the following command instead;
    x is the kernel number starting from 0
    # grub2-set-default x

    Check it
    # grub2-editenv list

    Save it
    # grub2-mkconfig -o /boot/grub2/grub.cfg
    Like
    1
    The reply is currently minimized Show
Your Reply