Description of problem: 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 Version-Release number of selected component (if applicable): F25 and F26 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. Additional info: Please let me know what info I can provide or if you need me to make any tests.
This was a huge pain of 13 builds on that very slow laptop but here you have the culprit: 282a4e4ce5f99e3c166abac929498885a711e19f is the first bad commit commit 282a4e4ce5f99e3c166abac929498885a711e19f Author: Irina Tirdea <irina.tirdea> 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> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart.com> Acked-by: Andy Shevchenko <andriy.shevchenko.com> Signed-off-by: Stephen Boyd <sboyd>
Hi, (In reply to Ignacio Casal Quinteiro (nacho) from comment #1) > This was a huge pain of 13 builds on that very slow laptop but here you have > the culprit: > > 282a4e4ce5f99e3c166abac929498885a711e19f is the first bad commit > commit 282a4e4ce5f99e3c166abac929498885a711e19f > Author: Irina Tirdea <irina.tirdea> > Date: Mon Jan 23 12:07:44 2017 -0600 Thank you for bi-secting this, can you please file a bug for this at: bugzilla.kernel.org and then send a mail with the text from the bug (and a link to the bug) to: Darren Hart <dvhart> Irina Tirdea <irina.tirdea> Pierre-Louis Bossart <pierre-louis.bossart.com> Andy Shevchenko <andriy.shevchenko.com> Hans de Goede <hdegoede> platform-driver-x86.org Regards, Hans
Here is the upstream bug report for reference: https://bugzilla.kernel.org/show_bug.cgi?id=196819
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
As I wrote on the upstream bug, this was fixed already with a newer version of the kernel.
Thanks for letting us know.