• Kernel 4.13 makes me panic ;)

    So - whenever I update to Kernel 4.13 my system crashes with kernel panic. Here are the last journalctl-outputs. I absolutely have no idea, why antergos suddenly hates me :) http://dev.trancefish.de/errors.tar.gz

  • Switched to LTS by:

    sudo pacman -S linux-lts
    sudo pacman -R linux
    sudo grub-mkconfig -o /boot/grub/grub.cfg

    This does not solve the problem for now but at least I can work again

  • @trancefish
    Might have something to do with these non-LTS kernels being less tested and slightly experimental (in my book). That’s why I always use LTS kernels if possible.

  • @trancefish and the logs looking clean…
    But 4.13 is not the best kernel from the last ones… hopefully we will get a new one soon!

  • @joekamprad LTS is for me currently the best solution :) Funny coincedence: Neither debian nor ubuntu wanted to be installed on that machine, so I stay with antergos :)

  • 4.13 is the worst kernel I’ve ever used, 4.14-rc3 in AUR is a good choice now.

  • @s9209122222 yes right… lets blame on this very bad 13 kernel!

  • @joekamprad at least it’s the first kernel my system doesn’t like :) And when searching this board, I am not alone. Flickering GFX and other weird stuff. Anyway. Case closed. LTS for me, works. Yippieeh

  • @trancefish Same here. Switched to LTS. My system had been freezing after about 5 minutes.

  • There are a few similar threads on the arch linux forum, e.g. arch linux forum post#1. You might try to set intel_iommu=off as proposed in the bug report. Please let me know if that does not solve the problem, as I face a similar one right now.

    @joekamprad If that’s true we should blame Intel… ;)

  • For a long time I get used to have the absolutely clean boot ups, without any errors or warnings. Only two messages are displayed:

    • systemd reporting its current version
    • fsck reporting the clean filesystem

    With kernel 4.13, all of a sudden and without any changes in the system, I started to get three “intel underrun” error messages on boot ups:

    $ journalctl -xb | grep underrun
    Oct 09 09:14:01 alexasm.net kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
    Oct 09 09:14:01 alexasm.net kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
    Oct 09 09:14:01 alexasm.net kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun

    Apparently, it doesn’t cause any graphical problems or performance degradation. For the first time these errors were discussed in Internet during 2014-2015. It was said they are only debug messages, and shouldn’t affect the system in any way.

    Nevertheless, it was unpleasant to see them. I wanted to get clean boot ups back again. Adding the intel_iommu=off boot parameter solved the issue. Three fake errors disappeared.

    Hopefully, kernel 4.14 won’t have this issue, and it’ll be possible to remove intel_iommu=off parameter.

  • @rfor I don’t want to get away from LTS at this point. This fix might probably help. It seems logical to do so. H had the same CPU pipe A FIFO underrun-fake errors @just was writing about. For now, my system runs quite good, although I had to switch from lightdm to gdm (but this seems to be coming from another bug ;) )

kernel141 panic10 makes3 4.132 Posts 12Views 2174
Log in to reply
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.