Need backport short kernel patch for oops on Wily kernels with haswell/broadwell

[Kamal Mostafa]

On Wed, Apr 27, 2016 at 01:06:47PM -0400, Nick Black wrote:
> Hello there!
> 
> We're seeing a lot of (seemingly harmless) oops using Wily 4.2 kernels with
> Haswell-ULT and Broadwell x86 processors. The fix seems a simple backport
> from 4.5, adding two elements to the mch_quirk_devices[] table from
> drivers/pnp/quirks.c.
> I've included a sample oops below from a Haswell-ULT machine. The most
> recent patch appears to be here:
> 
>   https://lkml.org/lkml/2015/12/11/165
> 
> Could we get this included in the Wily kernel? Thanks!
> 

Hi Nick-

That patch looks fine and will apply to Vivid, Wily, and Xenial.

However, you mention "adding two elements" but that patch only adds one:
+       0x1604, /* Broadwell */
Clarify that please, and ...

Please file a launchpad bug against the 'linux' package so we can track
the issue and have you verify the fix when we apply it.

Thanks!

 -Kamal

> 
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 1 at
> /build/linux-lts-wily-MVxxD8/linux-lts-wily-4.2.0/arch/x86/mm/ioremap.c:198
> __ioremap_caller+0x2a2/0x360()
> Info: mapping multiple BARs. Your kernel is fine.
> Modules linked in:
> CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0-34-generic
> #39~14.04.1-Ubuntu
> Hardware name: Hewlett-Packard HP EliteBook Folio 1040 G1/213E, BIOS L83
> Ver. 01.07 03/28/2014
>  ffffffff81a91c80 ffff88023522bad8 ffffffff817b5fed 0000000000000001
>  ffff88023522bb28 ffff88023522bb18 ffffffff8107799a ffffc90000cbe000
>  ffffc90000cb8000 ffffc90000cb8000 0000000000006000 ffff880230297040
> Call Trace:
>  [<ffffffff817b5fed>] dump_stack+0x45/0x57
>  [<ffffffff8107799a>] warn_slowpath_common+0x8a/0xc0
>  [<ffffffff81077a16>] warn_slowpath_fmt+0x46/0x50
>  [<ffffffff81064942>] __ioremap_caller+0x2a2/0x360
>  [<ffffffff81064a17>] ioremap_nocache+0x17/0x20
>  [<ffffffff810393c5>] snb_uncore_imc_init_box+0x65/0x90
>  [<ffffffff81037955>] uncore_pci_probe+0xd5/0x1c0
>  [<ffffffff813f3a75>] local_pci_probe+0x45/0xa0
>  [<ffffffff813f4c34>] ? pci_match_device+0xf4/0x120
>  [<ffffffff813f4d6a>] pci_device_probe+0xca/0x110
>  [<ffffffff814f6293>] driver_probe_device+0x213/0x460
>  [<ffffffff814f6570>] __driver_attach+0x90/0xa0
>  [<ffffffff814f64e0>] ? driver_probe_device+0x460/0x460
>  [<ffffffff814f409d>] bus_for_each_dev+0x5d/0x90
>  [<ffffffff814f5c0e>] driver_attach+0x1e/0x20
>  [<ffffffff814f5760>] bus_add_driver+0x1d0/0x290
>  [<ffffffff81d606cf>] ? uncore_cpu_setup+0x12/0x12
>  [<ffffffff814f6f30>] driver_register+0x60/0xe0
>  [<ffffffff813f33dc>] __pci_register_driver+0x4c/0x50
>  [<ffffffff81d607b5>] intel_uncore_init+0xe6/0x2fc
>  [<ffffffff81d606cf>] ? uncore_cpu_setup+0x12/0x12
>  [<ffffffff8100213d>] do_one_initcall+0xcd/0x1f0
>  [<ffffffff81094e00>] ? parse_args+0x120/0x470
>  [<ffffffff810b7528>] ? __wake_up+0x48/0x60
>  [<ffffffff81d512c5>] kernel_init_freeable+0x199/0x226
>  [<ffffffff81d509a1>] ? initcall_blacklist+0xc0/0xc0
>  [<ffffffff817a5f50>] ? rest_init+0x80/0x80
>  [<ffffffff817a5f5e>] kernel_init+0xe/0xe0
>  [<ffffffff817bd81f>] ret_from_fork+0x3f/0x70
>  [<ffffffff817a5f50>] ? rest_init+0x80/0x80
> ---[ end trace 5f5beae5b9d2dc45 ]---

> -- 
> kernel-team mailing list
> kernel-team at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team