WARNING: CPU: 2 PID: 1 at /build/linux-WmE1Ft/linux-4.4.0/arch/x86/mm/ioremap.c:198 __ioremap_caller+0x2c5/0x380()

Bug #1550908 reported by Timo Harmonen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

Xenial beta, Lenovo t440s with latest bios, happens on every restart, newer saw on 15.10.

Feb 28 14:07:49 timoha-ll kernel: [ 0.826558] WARNING: CPU: 2 PID: 1 at /build/linux-WmE1Ft/linux-4.4.0/arch/x86/mm/ioremap.c:198 __ioremap_caller+0x2c5/0x380()
Feb 28 14:07:49 timoha-ll kernel: [ 0.826559] Info: mapping multiple BARs. Your kernel is fine.
Feb 28 14:07:49 timoha-ll kernel: [ 0.826560] Modules linked in:
Feb 28 14:07:49 timoha-ll kernel: [ 0.826564] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.0-8-generic #23-Ubuntu
Feb 28 14:07:49 timoha-ll kernel: [ 0.826565] Hardware name: LENOVO 20AQ007SMS/20AQ007SMS, BIOS GJET87WW (2.37 ) 01/12/2016
Feb 28 14:07:49 timoha-ll kernel: [ 0.826567] 0000000000000000 000000009f756ef0 ffff880310263b38 ffffffff813dbba4
Feb 28 14:07:49 timoha-ll kernel: [ 0.826569] ffff880310263b80 ffff880310263b70 ffffffff8107ec12 00000000fed10000
Feb 28 14:07:49 timoha-ll kernel: [ 0.826572] ffffc900018f8000 0000000000006000 0000000000000000 ffff88030ff7a580
Feb 28 14:07:49 timoha-ll kernel: [ 0.826574] Call Trace:
Feb 28 14:07:49 timoha-ll kernel: [ 0.826580] [<ffffffff813dbba4>] dump_stack+0x44/0x60
Feb 28 14:07:49 timoha-ll kernel: [ 0.826583] [<ffffffff8107ec12>] warn_slowpath_common+0x82/0xc0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826586] [<ffffffff8107ecac>] warn_slowpath_fmt+0x5c/0x80
Feb 28 14:07:49 timoha-ll kernel: [ 0.826589] [<ffffffff8108548a>] ? iomem_map_sanity_check+0xba/0xd0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826591] [<ffffffff81069ba5>] __ioremap_caller+0x2c5/0x380
Feb 28 14:07:49 timoha-ll kernel: [ 0.826593] [<ffffffff81069c77>] ioremap_nocache+0x17/0x20
Feb 28 14:07:49 timoha-ll kernel: [ 0.826596] [<ffffffff8103c429>] snb_uncore_imc_init_box+0x79/0xb0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826598] [<ffffffff8103b138>] uncore_pci_probe+0xd8/0x1f0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826602] [<ffffffff8142b8c5>] local_pci_probe+0x45/0xa0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826605] [<ffffffff8142cd03>] pci_device_probe+0x103/0x150
Feb 28 14:07:49 timoha-ll kernel: [ 0.826609] [<ffffffff8153dc92>] driver_probe_device+0x222/0x4a0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826612] [<ffffffff8153df94>] __driver_attach+0x84/0x90
Feb 28 14:07:49 timoha-ll kernel: [ 0.826614] [<ffffffff8153df10>] ? driver_probe_device+0x4a0/0x4a0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826617] [<ffffffff8153b8bc>] bus_for_each_dev+0x6c/0xc0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826619] [<ffffffff8153d44e>] driver_attach+0x1e/0x20
Feb 28 14:07:49 timoha-ll kernel: [ 0.826621] [<ffffffff8153cf8b>] bus_add_driver+0x1eb/0x280
Feb 28 14:07:49 timoha-ll kernel: [ 0.826624] [<ffffffff81f691bb>] ? uncore_cpu_setup+0x12/0x12
Feb 28 14:07:49 timoha-ll kernel: [ 0.826627] [<ffffffff8153e830>] driver_register+0x60/0xe0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826630] [<ffffffff8142b1ec>] __pci_register_driver+0x4c/0x50
Feb 28 14:07:49 timoha-ll kernel: [ 0.826632] [<ffffffff81f692b0>] intel_uncore_init+0xf5/0x306
Feb 28 14:07:49 timoha-ll kernel: [ 0.826634] [<ffffffff81f691bb>] ? uncore_cpu_setup+0x12/0x12
Feb 28 14:07:49 timoha-ll kernel: [ 0.826637] [<ffffffff81002123>] do_one_initcall+0xb3/0x200
Feb 28 14:07:49 timoha-ll kernel: [ 0.826641] [<ffffffff8109d4a1>] ? parse_args+0x161/0x4b0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826644] [<ffffffff81f591a5>] kernel_init_freeable+0x173/0x212
Feb 28 14:07:49 timoha-ll kernel: [ 0.826647] [<ffffffff81807990>] ? rest_init+0x80/0x80
Feb 28 14:07:49 timoha-ll kernel: [ 0.826650] [<ffffffff8180799e>] kernel_init+0xe/0xe0
Feb 28 14:07:49 timoha-ll kernel: [ 0.826653] [<ffffffff8181420f>] ret_from_fork+0x3f/0x70
Feb 28 14:07:49 timoha-ll kernel: [ 0.826655] [<ffffffff81807990>] ? rest_init+0x80/0x80

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: timoha 3021 F.... pulseaudio
 /dev/snd/controlC1: timoha 3021 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Feb 28 14:08:55 2016
HibernationDevice: RESUME=UUID=a397ec47-ee9c-46cb-af31-3f2880b00e85
InstallationDate: Installed on 2015-03-07 (358 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150304)
MachineType: LENOVO 20AQ007SMS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-8-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-8-generic N/A
 linux-backports-modules-4.4.0-8-generic N/A
 linux-firmware 1.156
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-02-27 (1 days ago)
dmi.bios.date: 01/12/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET87WW (2.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQ007SMS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 PRO
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGJET87WW(2.37):bd01/12/2016:svnLENOVO:pn20AQ007SMS:pvrThinkPadT440s:rvnLENOVO:rn20AQ007SMS:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQ007SMS
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

Revision history for this message
Timo Harmonen (timo-harmonen) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
penalvch (penalvch) wrote :

Timo Harmonen, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-2.37
tags: added: regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.