klog.json: Add some miscellaneous messages to klog database

From: Colin Ian King <colin.king@canonical.com>

Just a few odds and ends from various drivers need adding.

Signed-off-by: Colin Ian King <colin.king@canonical.com>
---
 data/klog.json | 42 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

On 2017-02-10 07:38 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Just a few odds and ends from various drivers need adding.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  data/klog.json | 42 ++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
>
> diff --git a/data/klog.json b/data/klog.json
> index cc936fd..55ff2f3 100644
> --- a/data/klog.json
> +++ b/data/klog.json
> @@ -4,6 +4,48 @@
>    {
>     "compare_mode": "string",
>     "log_level": "LOG_LEVEL_CRITICAL",
> +   "pattern": "e820: cannot find a gap in the 32bit address range",
> +   "advice": "A search for the biggest gap in the low 32 bit E820 memory space for PCI MMIO resources failed to find any free gaps large enough. PCI devices with unassigned 32 bit Base Address Registers (BARs) are very likely to break.",
> +   "label": "KlogBiosE820NoGapAvailable",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_HIGH",
> +   "pattern": "AcpiDisable failed",
> +   "advice": "The ACPI core driver cannot disable ACPI when returning back to legacy mode.",
> +   "label": "KlogAcpiDisableFailed",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_HIGH",
> +   "pattern": "DSDT is not in memory",
> +   "advice": "The ACPI core driver has attempted to load the ACPI namespace but failed because there is no ACPI Differentiated System Description Table (DSDT) available.",
> +   "label": "KlogAcpiDsdtNotInMemory",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_MEDIUM",
> +   "pattern": "CPPC data invalid or not present",
> +   "advice": "The ACPI processor driver has detected missing or invalid Collaborative Processor Performance Control (CPPC) data.  The ACPI per CPU _CPC objects may be missing or broken.",
> +   "label": "KlogAcpiCppcDataInvalid",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_MEDIUM",
> +   "pattern": "The _BIX method is broken, using _BIF",
> +   "advice": "The ACPI battery driver has detected that the Battery Information Extended (_BIX) object seems to be broken and has fallen back to using the less modern Battery Information (_BIF) object instead to get battery specific data.",
> +   "label": "KlogAcpiBixBroken",
> +  },
> +  {
> +   "compare_mode": "regex",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "pattern": "BIOS reported wrong ACPI id .* for the processor",
> +   "advice": "The ACPI processor enumaration detected an invalid ACPI ID for a specific processor. This is not fatal, but the kernel will not trust the ACPI data for this specific processor.",
> +   "label": "KlogAcpiProcessorInvalidId",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_CRITICAL",
>     "pattern": "VA address range overflow",
>     "advice": "The EFI virtual address has wrapped around and overflowed and may cause random or unexplicable faulty EFI behaviour.",
>     "label": "KlogEfiVaAddrRangeOverflow",
>
Acked-by: Alex Hung <alex.hung@canonical.com>

On 2017年02月10日 19:38, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Just a few odds and ends from various drivers need adding.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   data/klog.json | 42 ++++++++++++++++++++++++++++++++++++++++++
>   1 file changed, 42 insertions(+)
>
> diff --git a/data/klog.json b/data/klog.json
> index cc936fd..55ff2f3 100644
> --- a/data/klog.json
> +++ b/data/klog.json
> @@ -4,6 +4,48 @@
>     {
>      "compare_mode": "string",
>      "log_level": "LOG_LEVEL_CRITICAL",
> +   "pattern": "e820: cannot find a gap in the 32bit address range",
> +   "advice": "A search for the biggest gap in the low 32 bit E820 memory space for PCI MMIO resources failed to find any free gaps large enough. PCI devices with unassigned 32 bit Base Address Registers (BARs) are very likely to break.",
> +   "label": "KlogBiosE820NoGapAvailable",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_HIGH",
> +   "pattern": "AcpiDisable failed",
> +   "advice": "The ACPI core driver cannot disable ACPI when returning back to legacy mode.",
> +   "label": "KlogAcpiDisableFailed",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_HIGH",
> +   "pattern": "DSDT is not in memory",
> +   "advice": "The ACPI core driver has attempted to load the ACPI namespace but failed because there is no ACPI Differentiated System Description Table (DSDT) available.",
> +   "label": "KlogAcpiDsdtNotInMemory",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_MEDIUM",
> +   "pattern": "CPPC data invalid or not present",
> +   "advice": "The ACPI processor driver has detected missing or invalid Collaborative Processor Performance Control (CPPC) data.  The ACPI per CPU _CPC objects may be missing or broken.",
> +   "label": "KlogAcpiCppcDataInvalid",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_MEDIUM",
> +   "pattern": "The _BIX method is broken, using _BIF",
> +   "advice": "The ACPI battery driver has detected that the Battery Information Extended (_BIX) object seems to be broken and has fallen back to using the less modern Battery Information (_BIF) object instead to get battery specific data.",
> +   "label": "KlogAcpiBixBroken",
> +  },
> +  {
> +   "compare_mode": "regex",
> +   "log_level": "LOG_LEVEL_LOW",
> +   "pattern": "BIOS reported wrong ACPI id .* for the processor",
> +   "advice": "The ACPI processor enumaration detected an invalid ACPI ID for a specific processor. This is not fatal, but the kernel will not trust the ACPI data for this specific processor.",
> +   "label": "KlogAcpiProcessorInvalidId",
> +  },
> +  {
> +   "compare_mode": "string",
> +   "log_level": "LOG_LEVEL_CRITICAL",
>      "pattern": "VA address range overflow",
>      "advice": "The EFI virtual address has wrapped around and overflowed and may cause random or unexplicable faulty EFI behaviour.",
>      "label": "KlogEfiVaAddrRangeOverflow",


Acked-by: Ivan Hu <ivan.hu@canonical.com>