https://bugzilla.kernel.org/show_bug.cgi?id=203529
--- Comment #43 from Andy Shevchenko (andy.shevche...@gmail.com) --- (In reply to secan from comment #42) > So this is what I did. Due to the fact that Redhat is very peculiar when it > comes to patching, I went the kpatch way (the method that RH recommends). kpatch sounds to me the like incorrect method for testing most of the early boot / boot stage problems. You need to recompile the kernel. > Unfortunately the patch provided by you wasn't helpful. Not sure I understood this comment. The patch I shared is not going to fix anything, it's pure for debugging purposes to understand better the cause of the issue. > lspci -vvx -s 00:15 > > 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH > Serial IO I2C Controller #0 (rev 10) > DeviceName: Onboard - Other > Subsystem: Dell Device 095b > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- > <MAbort- >SERR- <PERR- INTx- > Interrupt: pin A routed to IRQ 255 This line make me think about other causes. Can you boot your kernel with 'initcall_debug ignore_loglevel pci=earlydump' added to the kernel command line and attach the output of `dmesg`? > Any other hints/tips/tricks/workarounds/patches ? :) -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
