I held off upgrading the kernel for a while, but I recently took the jump from 3.14.22 to 3.17.1 and found that when gdm started I had a kernel crash. Unfortunately I cannot grab the stack trace right now and I don't see the crash because I have tried with and without a framebuffer in the config. Starting X on its own is not a problem. Starting gdm or a gnome session results in a kernel crash. Downgrading the kernel fixed the problem. The hardware is an HD4000 with the following: x11-base/xorg-drivers-1.16 x11-base/xorg-server-1.16.1 x11-drivers/xf86-video-intel-2.99.916 Reproducible: Always
ssh? dmesg? emerge --info? what is "kernel crash" mean? lockup? machine turns off? panic?
So many questions... I think that you forgot a more important question, where is the kernel config. Yes the kernel panics. I guess if the kernel panics it can do many things, like produce a stack trace, and dump some information on the console. Unfortunately because I started removing the framebuffer from the kernel config I was having a little bit of trouble finding out exactly what went wrong. I will try and get more information when it comes to hand.
1) Please post your `emerge --info' output in a comment. 2) Please post relevant information pertaining to what crashed, including output and configuration, and the steps leading up to the crash.
Here is the emerge --info. There is nothing exciting here. The problem is when running this version with the 3.17.1 kernel. Portage 2.2.14 (python 2.7.8-final-0, unavailable, gcc-4.8.3, glibc-2.19-r1, 3.15.9 x86_64) ================================================================= System uname: Linux-3.15.9-x86_64-with-gentoo-2.2 KiB Mem: 3746864 total, 213772 free KiB Swap: 0 total, 0 free Timestamp of tree: Unknown ld GNU gold (Linux/GNU Binutils 2.24.51.0.3.20140127) 1.11 dev-lang/python: 2.7.8, 3.3.5-r1, 3.4.2 sys-devel/autoconf: 2.13, 2.69 sys-devel/automake: 1.11.6, 1.14.1 sys-devel/binutils: 2.24.51.0.3 sys-devel/libtool: 2.4.2-r1 sys-kernel/linux-headers: 3.17 (virtual/os-headers) Repositories: ACCEPT_KEYWORDS="~amd64" ACCEPT_LICENSE="* -@EULA" CFLAGS="-O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync metadata-transfer news nodoc noinfo noman notitles parallel-fetch preserve-libs protect-owned sandbox sfperms sign strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync webrsync-gpg" GENTOO_MIRRORS="http://distfiles.gentoo.org" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/build/portage" PORTDIR_OVERLAY="" USE="bluetooth caps clang cryptsetup dconf dhclient dri3 fontconfig git gold graphite icu ldns lto mmxext mpeg2 multitarget mysql nss opengl openmp pulseaudio resolvconf sqlite sse2 sse4_1 sse4_2 ssse3 systemd threads xvmc" Unset: EMERGE_DEFAULT_OPTS, PORTAGE_BUNZIP2_COMMAND
(In reply to Jeroen Roovers from comment #3) > 1) Please post your `emerge --info' output in a comment. Done. Nothing exciting there. The problem is running the same system with different kernel. > 2) Please post relevant information pertaining to what crashed, including > output and configuration, and the steps leading up to the crash. The only configuration that changes is the kernel and modules. There is an i915 kernel module and the like. I can run X with the 3.17.1 kernel. There appears to be a kernel panic with the same user space system when using gnome/gdm.
(In reply to Vlad Horko from comment #4) > Here is the emerge --info. There is nothing exciting here. The problem is That's not the entire thing.
Created attachment 387258 [details] Working 3.15.9 config
Created attachment 387260 [details] Config which has an exception to gdm/gnome
(In reply to Jeroen Roovers from comment #6) > (In reply to Vlad Horko from comment #4) > > Here is the emerge --info. There is nothing exciting here. The problem is > > That's not the entire thing. Can you please tell me what is missing?
(In reply to Vlad Horko from comment #9) > (In reply to Jeroen Roovers from comment #6) > > (In reply to Vlad Horko from comment #4) > > > Here is the emerge --info. There is nothing exciting here. The problem is > > > > That's not the entire thing. > > Can you please tell me what is missing? Most of it. It seems to have been edited quite heavily.