Activity log for bug #1732990

Date Who What changed Old value New value Message
2017-11-17 20:42:42 Manoj Iyer bug added bug
2017-11-17 21:00:06 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2017-11-17 21:00:08 Ubuntu Kernel Bot tags qdf2400 artful qdf2400
2017-11-20 23:59:22 Manoj Iyer linux (Ubuntu): assignee Manoj Iyer (manjo) Canonical Kernel Team (canonical-kernel-team)
2017-11-21 16:47:41 Joseph Salisbury nominated for series Ubuntu Zesty
2017-11-21 16:47:41 Joseph Salisbury bug task added linux (Ubuntu Zesty)
2017-11-21 16:47:41 Joseph Salisbury nominated for series Ubuntu Artful
2017-11-21 16:47:41 Joseph Salisbury bug task added linux (Ubuntu Artful)
2017-11-21 16:48:06 Joseph Salisbury linux (Ubuntu): status Incomplete In Progress
2017-11-21 16:48:10 Joseph Salisbury linux (Ubuntu Zesty): status New In Progress
2017-11-21 16:48:14 Joseph Salisbury linux (Ubuntu Artful): status New In Progress
2017-11-21 16:48:17 Joseph Salisbury linux (Ubuntu Zesty): importance Undecided Critical
2017-11-21 16:48:20 Joseph Salisbury linux (Ubuntu Artful): importance Undecided Critical
2017-11-21 16:48:33 Joseph Salisbury linux (Ubuntu Zesty): assignee Manoj Iyer (manjo)
2017-11-21 16:48:43 Joseph Salisbury linux (Ubuntu Artful): assignee Manoj Iyer (manjo)
2017-11-21 16:48:58 Joseph Salisbury linux (Ubuntu): assignee Canonical Kernel Team (canonical-kernel-team) Manoj Iyer (manjo)
2017-11-22 15:19:49 Manoj Iyer bug added subscriber Sean Feole
2017-11-22 15:24:34 Manoj Iyer bug added subscriber Jeffrey Hugo
2017-11-24 16:31:15 Manoj Iyer description [Impact] Error records which have multiple errors in them will incorrectly report all errors after the first one. This results in garbage non-standard error trace events to be generated, and for AER and MC errors there will be no kernel action to help recover from these errors in the AER and EDAC drivers. [Fix] Patches in Linus tree fixes this issue: aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block [Testing] Insert a e1000 pcie card into the system, run the following command that should generate PCIe correctable errors, you will see only the first error in each GHES report go to the AER driver rather than all errors from the GHES reports. $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s 0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0 CAP_EXP+0x10.B=0x48 Where "0002:00:00.0" being the root hub for the card. [Regression Potential] The two patches to ACPI APEI driver was cleanly cherry picked from linus's tree and applied to Artful and Zesty. The patches were tested on QDF2400 platform where it was found to issue and don't introduce any regressions. [Impact] Error records which have multiple errors in them will incorrectly report all errors after the first one. This results in garbage non-standard error trace events to be generated, and for AER and MC errors there will be no kernel action to help recover from these errors in the AER and EDAC drivers. [Fix] Patches in Linus tree fixes this issue: aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block [Testing] Insert a e1000 pcie card into the system, run the following command that should generate PCIe correctable errors, you will see only the first error in each GHES report go to the AER driver rather than all errors from the GHES reports. $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s 0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0 CAP_EXP+0x10.B=0x48 Where "0002:00:00.0" being the root hub for the card. Used JTAG to trigger multiple concurrent errors, and observed that all errors were parsed, instead of just the first one. As mentioned in comment #3. So, the poster of comment #3 will do the verification once the patch lands in -proposed. [Regression Potential] The two patches to ACPI APEI driver was cleanly cherry picked from linus's tree and applied to Artful and Zesty. The patches were tested on QDF2400 platform where it was found to issue and don't introduce any regressions.
2018-02-04 01:17:02 Khaled El Mously linux (Ubuntu Artful): status In Progress Fix Committed
2018-02-13 17:06:17 Manoj Iyer linux (Ubuntu Zesty): status In Progress Won't Fix
2018-02-13 17:06:23 Andrew Cloke linux (Ubuntu): status In Progress Fix Committed
2018-02-14 09:38:17 Kleber Sacilotto de Souza tags artful qdf2400 artful qdf2400 verification-needed-artful
2018-02-21 18:56:18 Launchpad Janitor linux (Ubuntu Artful): status Fix Committed Fix Released
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-15115
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-17712
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-5715
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-5753
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-5754
2018-02-21 18:56:18 Launchpad Janitor cve linked 2017-8824
2018-10-03 14:30:03 Joseph Salisbury linux (Ubuntu): status Fix Committed Fix Released
2019-07-24 20:17:34 Brad Figg tags artful qdf2400 verification-needed-artful artful cscc qdf2400 verification-needed-artful