[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug was fixed in the package linux - 4.4.0-24.43 --- linux (4.4.0-24.43) xenial; urgency=low [ Kamal Mostafa ] * CVE-2016-1583 (LP: #1588871) - ecryptfs: fix handling of directory opening - SAUCE: proc: prevent stacking filesystems on top - SAUCE: ecryptfs: forbid opening files without mmap handler - SAUCE: sched: panic on corrupted stack end * arm64: statically link rtc-efi (LP: #1583738) - [Config] Link rtc-efi statically on arm64 -- Kamal Mostafa Fri, 03 Jun 2016 10:02:16 -0700 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug was fixed in the package linux - 3.19.0-61.69 --- linux (3.19.0-61.69) vivid; urgency=low [ Kamal Mostafa ] * CVE-2016-1583 (LP: #1588871) - ecryptfs: fix handling of directory opening - SAUCE: proc: prevent stacking filesystems on top - SAUCE: ecryptfs: forbid opening files without mmap handler - SAUCE: sched: panic on corrupted stack end -- Andy Whitcroft Wed, 08 Jun 2016 22:25:58 +0100 ** Changed in: linux (Ubuntu Vivid) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-1583 ** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug was fixed in the package linux - 4.2.0-38.45 --- linux (4.2.0-38.45) wily; urgency=low [ Kamal Mostafa ] * CVE-2016-1583 (LP: #1588871) - ecryptfs: fix handling of directory opening - SAUCE: proc: prevent stacking filesystems on top - SAUCE: ecryptfs: forbid opening files without mmap handler - SAUCE: sched: panic on corrupted stack end -- Andy Whitcroft Wed, 08 Jun 2016 22:10:39 +0100 ** Changed in: linux (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug was fixed in the package linux - 4.4.0-23.41 --- linux (4.4.0-23.41) xenial; urgency=low [ Kamal Mostafa ] * Release Tracking Bug - LP: #1582431 * zfs: disable module checks for zfs when cross-compiling (LP: #1581127) - [Packaging] disable zfs module checks when cross-compiling * Xenial update to v4.4.10 stable release (LP: #1580754) - Revert "UBUNTU: SAUCE: (no-up) ACPICA: Dispatcher: Update thread ID for recursive method calls" - Revert "UBUNTU: SAUCE: nbd: ratelimit error msgs after socket close" - Revert: "powerpc/tm: Check for already reclaimed tasks" - RDMA/iw_cxgb4: Fix bar2 virt addr calculation for T4 chips - ipvs: handle ip_vs_fill_iph_skb_off failure - ipvs: correct initial offset of Call-ID header search in SIP persistence engine - ipvs: drop first packet to redirect conntrack - mfd: intel-lpss: Remove clock tree on error path - nbd: ratelimit error msgs after socket close - ata: ahci_xgene: dereferencing uninitialized pointer in probe - mwifiex: fix corner case association failure - CNS3xxx: Fix PCI cns3xxx_write_config() - clk-divider: make sure read-only dividers do not write to their register - soc: rockchip: power-domain: fix err handle while probing - clk: rockchip: free memory in error cases when registering clock branches - clk: meson: Fix meson_clk_register_clks() signature type mismatch - clk: qcom: msm8960: fix ce3_core clk enable register - clk: versatile: sp810: support reentrance - clk: qcom: msm8960: Fix ce3_src register offset - lpfc: fix misleading indentation - ath9k: ar5008_hw_cmn_spur_mitigate: add missing mask_m & mask_p initialisation - mac80211: fix statistics leak if dev_alloc_name() fails - tracing: Don't display trigger file for events that can't be enabled - MD: make bio mergeable - Minimal fix-up of bad hashing behavior of hash_64() - mm, cma: prevent nr_isolated_* counters from going negative - mm/zswap: provide unique zpool name - ARM: EXYNOS: Properly skip unitialized parent clock in power domain on - ARM: SoCFPGA: Fix secondary CPU startup in thumb2 kernel - xen: Fix page <-> pfn conversion on 32 bit systems - xen/balloon: Fix crash when ballooning on x86 32 bit PAE - xen/evtchn: fix ring resize when binding new events - HID: wacom: Add support for DTK-1651 - HID: Fix boot delay for Creative SB Omni Surround 5.1 with quirk - Input: zforce_ts - fix dual touch recognition - proc: prevent accessing /proc//environ until it's ready - mm: update min_free_kbytes from khugepaged after core initialization - batman-adv: fix DAT candidate selection (must use vid) - batman-adv: Check skb size before using encapsulated ETH+VLAN header - batman-adv: Fix broadcast/ogm queue limit on a removed interface - batman-adv: Reduce refcnt of removed router when updating route - writeback: Fix performance regression in wb_over_bg_thresh() - MAINTAINERS: Remove asterisk from EFI directory names - x86/tsc: Read all ratio bits from MSR_PLATFORM_INFO - ARM: cpuidle: Pass on arm_cpuidle_suspend()'s return value - ARC: Add missing io barriers to io{read,write}{16,32}be() - x86/sysfb_efi: Fix valid BAR address range check - ACPICA: Dispatcher: Update thread ID for recursive method calls - powerpc: Fix bad inline asm constraint in create_zero_mask() - libahci: save port map for forced port map - ata: ahci-platform: Add ports-implemented DT bindings. - USB: serial: cp210x: add ID for Link ECU - USB: serial: cp210x: add Straizona Focusers device ids - nvmem: mxs-ocotp: fix buffer overflow in read - gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading - drm/amdgpu: make sure vertical front porch is at least 1 - drm/amdgpu: set metadata pointer to NULL after freeing. - iio: ak8975: Fix NULL pointer exception on early interrupt - iio: ak8975: fix maybe-uninitialized warning - drm/radeon: make sure vertical front porch is at least 1 - drm/i915/ddi: Fix eDP VDD handling during booting and suspend/resume - drm/i915: Fix eDP low vswing for Broadwell - drm/i915: Make RPS EI/thresholds multiple of 25 on SNB-BDW - drm/i915: Fake HDMI live status - lib/test-string_helpers.c: fix and improve string_get_size() tests - drm/i915/skl: Fix DMC load on Skylake J0 and K0 - Linux 4.4.10 * HDMI audio playback noise observed on AMD Polaris 10/11 GPU (LP: #1577288) - ALSA: hda: add AMD Polaris-10/11 AZ PCI IDs with proper driver caps * [i915_bpo] Update i915 backport driver (LP: #1580114) - SAUCE: i915_bpo: Drop is_preliminary from BXT/KBL. - SAUCE: i915_bpo: Sync with v4.6-rc7 * CVE-2016-4486 (LP: #1578497) - net: fix infoleak in rtnetlink * CVE-2016-4485 (LP: #1578496) - net: fix infoleak in llc * drm.ko < kernel version 4.5 has a dead lock bug (LP: #1579610)
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
I have not been able to replicate the issue with Xenial and the proposed kernel (yet). Tagged it just in case. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- wily' to 'verification-done-wily'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- vivid' to 'verification-done-vivid'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-vivid ** Tags added: verification-needed-wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Wily) Status: New => Fix Committed ** Changed in: linux (Ubuntu Vivid) Status: New => Fix Committed ** Changed in: linux (Ubuntu Vivid) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Fix Committed Status in linux source package in Vivid: Fix Committed Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: In Progress Status in linux source package in Vivid: New Status in linux source package in Wily: New Status in linux source package in Xenial: New Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1577748] Re: OOPS on wily+ for Haswell-ULT and Broadwell
apport-collect crashes: [nlb-glaptop](0) $ apport-collect 1577748 Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 594, in app.run_argv() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 653, in run_argv return self.run_update_report() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 525, in run_update_report pkgs = self.crashdb.get_affected_packages(self.options.update_report) File "/usr/lib/python2.7/dist-packages/apport/crashdb_impl/memory.py", line 79, in get_affected_packages return [self.reports[id]['report']['SourcePackage']] IndexError: list index out of range [nlb-glaptop](1) $ Manually Confirming ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1577748 Title: OOPS on wily+ for Haswell-ULT and Broadwell Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to the wily 4.2 kernel, we see early OOPSes similar to the following on Haswell-ULT and Broadwell processors: [ 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 81a91c80 88023522bad8 817b5fed 0001 88023522bb28 88023522bb18 8107799a c9cbe000 c9cb8000 c9cb8000 6000 880230297040 Call Trace: [] dump_stack+0x45/0x57 [] warn_slowpath_common+0x8a/0xc0 [] warn_slowpath_fmt+0x46/0x50 [] __ioremap_caller+0x2a2/0x360 [] ioremap_nocache+0x17/0x20 [] snb_uncore_imc_init_box+0x65/0x90 [] uncore_pci_probe+0xd5/0x1c0 [] local_pci_probe+0x45/0xa0 [] ? pci_match_device+0xf4/0x120 [] pci_device_probe+0xca/0x110 [] driver_probe_device+0x213/0x460 [] __driver_attach+0x90/0xa0 [] ? driver_probe_device+0x460/0x460 [] bus_for_each_dev+0x5d/0x90 [] driver_attach+0x1e/0x20 [] bus_add_driver+0x1d0/0x290 [] ? uncore_cpu_setup+0x12/0x12 [] driver_register+0x60/0xe0 [] __pci_register_driver+0x4c/0x50 [] intel_uncore_init+0xe6/0x2fc [] ? uncore_cpu_setup+0x12/0x12 [] do_one_initcall+0xcd/0x1f0 [] ? parse_args+0x120/0x470 [] ? __wake_up+0x48/0x60 [] kernel_init_freeable+0x199/0x226 [] ? initcall_blacklist+0xc0/0xc0 [] ? rest_init+0x80/0x80 [] kernel_init+0xe/0xe0 [] ret_from_fork+0x3f/0x70 [] ? rest_init+0x80/0x80 ---[ end trace 5f5beae5b9d2dc45 ]--- the issue is fixed in upstream kernels, via two patches: https://lkml.org/lkml/2015/12/11/165 http://lkml.iu.edu/hypermail/linux/kernel/1601.3/03815.html each is a one-liner against the mch_quirk_devices[] structure. [nlb-glaptop](0) $ cat /proc/version_signature Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 [nlb-glaptop](0) $ [nlb-glaptop](0) $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 [nlb-glaptop](0) $ [nlb-glaptop](0) $ apt-cache policy linux-generic-lts-wily linux-generic-lts-wily: Installed: 4.2.0.35.28 Candidate: 4.2.0.35.28 Version table: *** 4.2.0.35.28 0 600 https://rapture-prod.corp.google.com/ goobuntu-trusty-testing-lap...@nlb-glaptop.roam.corp.google.com/main amd64 Packages 100 /var/lib/dpkg/status [nlb-glaptop](0) $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp