Public bug reported: Requesting Canonical kernel team apply 5b8255dd55f61ff1f65774a2084823415ec09a90 from upstream for 16.04
Recent bug activity recap: == Comment: #17 - Guo Wen Shan - 2016-02-08 22:40:35 == Tentative patch sent to Andrew for verification. I'm putting a note here about the root cause: Each PE (struct eeh_pe) instance is tracking the primary bus by "pbus". When we have full hotplug as EEH recovery, the PE instance won't be refreshed. So the "pbus" is still dereferencing the stale PCI bus. Access to that at later pointer will cause kernel crash. The fix, as the patch sent to Andrew for verification, introduces another EEH PE flag (EEH_PE_PRI_BUS). That flag represents the validity of eeh_pe::pbus. Before unplugging in full hotplug case, the flag is cleared so that the eeh_pe::pbus can be updated at plugging time. I will send the patch to linux-ppc-dev for review after Andrew verified it helps. == Comment: #18 - Guo Wen Shan - 2016-02-08 23:55:00 == The patch was sent to linux-ppc-dev for review/pickup: https://patchwork.ozlabs.org/patch/580626/ which reads "[v2,1/4] powerpc/eeh: Fix stale cached primary bus". == Comment: #19 - Andrew Donnellan - 2016-02-09 00:19:33 == Patch has been submitted as per Gavin's comment. Please test! == Comment: #22 - Andrew Donnellan - 2016-02-11 01:41:06 == Requesting Canonical kernel team apply 5b8255dd55f61ff1f65774a2084823415ec09a90 from upstream for 16.04 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Taco Screen team (taco-screen-team) Status: New ** Tags: architecture-ppc64le bugnameltc-134013 severity-critical targetmilestone-inin--- ** Tags added: architecture-ppc64le bugnameltc-134013 severity-critical targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545037 Title: Surelock-GA2:kernel panic/ exception @ pcibios_set_pcie_reset_state+0x118/0x280 + cxl_reset+0x5c/0xc0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545037/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
