Linux 4.19.7 Released With Important PCI Express Fix, New & Improved STIBP

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • birdie
    replied
    Originally posted by hussam View Post
    Hey guys, I updated to linux 4.14.86 and multithreading slowed down considerably. How do I turn it off (the new protection thing in this release) from kernel boot line without recompiling arch's linux-lts package?
    Thank you!
    4.14.85 was rocket fast.
    Revert to 4.14.85 and be happy. It's not like .86 update fixes any security issues.

    Leave a comment:


  • Guest
    Guest replied
    Hey guys, I updated to linux 4.14.86 and multithreading slowed down considerably. How do I turn it off (the new protection thing in this release) from kernel boot line without recompiling arch's linux-lts package?
    Thank you!
    4.14.85 was rocket fast.

    Leave a comment:


  • arokh
    replied
    Originally posted by SkyWarrior View Post
    First I thought that kernel 4.19 was a good one to stay with. But I realized that it messed up with my docker containers as well as some of the proprietary illumina software that was installed way back. Reverting back to 4.14 LTS fixed all the issues. I am using all these on Manjaro stable.

    Docker problem seems to arise from the overlayfs but those suggested fixed did not help me at all.
    Don't blame the kernel for your own inability to maintain your system. Docker working great here on 4.19.7, it's a longterm stable kernel.

    Leave a comment:


  • birdie
    replied
    Originally posted by bearoso View Post
    It looks like the blk-mq corruption fix actually is in it.
    No.

    When was the last time you had your eyesight checked? ;-)

    Leave a comment:


  • SkyWarrior
    replied
    Thanks for the suggestion. I will note that. I need to see the reason for the illumina software segfaulting now. (They clearly do not segfault in 4.14 but they segfault in 4.19)

    Leave a comment:


  • lichtenstein
    replied
    Regarding docker, for me it worked to delete (well, move away) the /var/lib/docker dir. Restart docker after that and pull. I found this to be the prudent approach when updating kernels and docker wouldn't start afterwards.

    Leave a comment:


  • bitman
    replied
    Patch releases for 4.19 are piling up fast.

    Leave a comment:


  • SkyWarrior
    replied
    First I thought that kernel 4.19 was a good one to stay with. But I realized that it messed up with my docker containers as well as some of the proprietary illumina software that was installed way back. Reverting back to 4.14 LTS fixed all the issues. I am using all these on Manjaro stable.

    Docker problem seems to arise from the overlayfs but those suggested fixed did not help me at all.

    Leave a comment:


  • davidbepo
    replied
    Originally posted by bearoso View Post
    It looks like the blk-mq corruption fix actually is in it.
    its not, but manjaro for example has a patch for it

    Leave a comment:


  • bearoso
    replied
    It looks like the blk-mq corruption fix actually is in it.

    Leave a comment:

Working...
X