Kernel 4.10.15-200.fc25 boots as expected, instead the following new kernels do not: - 4.11.12-200.fc25 - 4.12.8-200.fc25 - 4.12.8-300.fc26 How reproducible: If I try to boot the laptop nothing happens, it stays black. Instead with the kernel 4.10.15-200.fc25 the fedora logo appears and boots without any problems. If it matters the laptop has an intel celeron and after bisecting I've found that the culprit is the following commit: 282a4e4ce5f99e3c166abac929498885a711e19f is the first bad commit commit 282a4e4ce5f99e3c166abac929498885a711e19f Author: Irina Tirdea <irina.tirdea@intel.com> Date: Mon Jan 23 12:07:44 2017 -0600 platform/x86: Enable Atom PMC platform clocks The BayTrail and CherryTrail platforms provide platform clocks through their Power Management Controller (PMC). The SoC supports up to 6 clocks (PMC_PLT_CLK[0..5]) with a frequency of either 19.2 MHz (PLL) or 25 MHz (XTAL) for BayTrail and a frequency of 19.2 MHz (XTAL) for CherryTrail. These clocks are available for general system use, where appropriate. For example, the usage for platform clocks suggested in the datasheet is the following: PLT_CLK[0..2] - Camera PLT_CLK[3] - Audio Codec PLT_CLK[4] - PLT_CLK[5] - COMMs Signed-off-by: Irina Tirdea <irina.tirdea@intel.com> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> For reference here you have also the downstream bug report I've filed: https://bugzilla.redhat.com/show_bug.cgi?id=1486005
Please, check if the commit d31fd43c0f9a ("clk: x86: Do not gate clocks enabled by the firmware") fixes your issue. Otherwise it might be DMI quirks needed, so, just in case, attach output of % dmesg # add 'ignore_loglevel initcall_debug' to the kernel command line % lspci -vv -nn % grep -H 15 /sys/bus/acpi/devices/*/status % dmidecode % acpidump -o table.dat # table.dat is point of interest
Unfortunately I don't have access to that laptop anymore. Thought I guess this can be reproduced with any intel celeron.
(In reply to Ignacio Casal from comment #2) > Unfortunately I don't have access to that laptop anymore. Than the solution would be going to stall... > Thought I guess > this can be reproduced with any intel celeron. I think it's not true. First of all, the mentioned patch is related to BayTrail / CherryTrail SoCs only, I dunno it covers "any Celeron".
I finally had the chance to test this again and I can confirm that with 4.13 it boots perfectly again. Thanks
Closing now, thanks!