Unclaimed register detected after reading register 0x65f10

Bug #1586046 reported by Dawid Wróbel on 2016-05-26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

After booting to newest kernel, I see following in dmesg:

[ 28.156951] WARNING: CPU: 3 PID: 2005 at /build/linux-FvcHlK/linux-4.4.0/ubuntu/i915/intel_uncore.c:649 __unclaimed_reg_debug+0x80/0x90 [i915_bpo]()
[ 28.156953] Unclaimed register detected after reading register 0x65f10

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
 /dev/snd/pcmC0D3p: cromo 1941 F...m pulseaudio
 /dev/snd/controlC0: cromo 1941 F.... pulseaudio
 /dev/snd/seq: timidity 1020 F.... timidity
Date: Thu May 26 09:46:38 2016
HibernationDevice: RESUME=UUID=3cd6beac-9b2b-4af8-9004-fdec2b01f2df
InstallationDate: Installed on 2013-04-24 (1128 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 0c45:670c Microdia
 Bus 001 Device 004: ID 04f3:20d0 Elan Microelectronics Corp.
 Bus 001 Device 003: ID 0a5c:6412 Broadcom Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=50ed3eed-05f6-4dce-b5d6-86a6519d89c1 ro quiet splash i8042.nopnp
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-03-23 (64 days ago)
dmi.bios.date: 03/01/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.3
dmi.board.name: 0VM5NC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

Dawid Wróbel (dawidw) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Medium

Dawid Wróbel, thank you for reporting this and helping make Ubuntu better.

To clarify, do you have an actual functionality issue?

tags: added: latest-bios-1.3.3
Changed in linux (Ubuntu):
status: Confirmed → Incomplete

There's a number of strange behaviors I observe, e.g. screen flickering,
networking issues, but I don't know if these can be attributed to this
specific kernel issue.

On Sun, Jun 5, 2016 at 11:20 PM Christopher M. Penalver <
<email address hidden>> wrote:

> Dawid Wróbel, thank you for reporting this and helping make Ubuntu
> better.
> To clarify, do you have an actual functionality issue?
> ** Tags added: latest-bios-1.3.3
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1586046
> Title:
> Unclaimed register detected after reading register 0x65f10
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1586046/+subscriptions

Shengjing Zhu (zhsj) wrote :
information type: Public → Public Security
information type: Public Security → Public
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Dawid Wróbel, 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:

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:

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Czikus (czikus-gmail) wrote :

I confirm that this problem exists on Dell Precision 5510 with kernels 4.6.3 and 4.7rc6. Also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573386 looks like a duplicate of this bug.

Czikus (czikus-gmail) wrote :
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6 kernel-bug-exists-upstream-4.7-rc6

Czikus, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

tags: removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.6 kernel-bug-exists-upstream-4.7-rc6
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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