1002:9802 The Linux kernel is no longer able to page the graphics processor, making the system to boot with a blank screen

[Solitaire]

******************
 HOW TO REPRODUCE
******************
1. Upgrade the system.
2. Install an affected graphics processor in your system.

********************
 EXPECTED BEHAVIOUR
********************
- The system to boot normally.

****************
 REAL BEHAVIOUR
****************
- After showing the splash screen, the monitor doesn't detect any signal and goes blank.

************
 WORKAROUND
************
In the "Terminal" application, paste the following line:

mkdir kernel && cd kernel && wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-utopic/linux-headers-3.16.7-031607-generic_3.16.7-031607.201410301735_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-utopic/linux-headers-3.16.7-031607_3.16.7-031607.201410301735_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-utopic/linux-image-3.16.7-031607-generic_3.16.7-031607.201410301735_amd64.deb && sudo dpkg -i *3.16*deb && cd .. && rm -r kernel && sudo update-grub && sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get autoremove -y

*******************
 TECHNICAL DETAILS
*******************
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-26-generic 3.16.0-26.34
ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
Uname: Linux 3.16.0-26-generic x86_64
Annotation: Your system might become unstablenow and might need to be restarted.
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: bill 12160 F.... pulseaudio
 /dev/snd/controlC0: bill 12160 F.... pulseaudio
Date: Thu Nov 27 13:56:47 2014
DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: 0010:location location kfree+0x56/0x150
Failure: oops
HibernationDevice: RESUME=UUID=d06d77c1-468d-41ec-8365-bdbd9dd870ed
InstallationDate: Installed on 2014-09-21 (66 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140921)
MachineType: MotherBoard By ZOTAC MotherBoard Fusion350-B-B/E/J/U
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=ca668714-f82b-4132-afea-4ae2931e8f56 ro recovery nomodeset
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at ffffec2000000900
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: NA
dmi.board.name: Fusion350-B-B/E/J/U
dmi.board.vendor: ZOTAC
dmi.board.version: 01
dmi.chassis.asset.tag: NA
dmi.chassis.type: 3
dmi.chassis.vendor: NA
dmi.chassis.version: NA
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd11/14/2011:svnMotherBoardByZOTAC:pnMotherBoardFusion350-B-B/E/J/U:pvrMotherBoard01:rvnZOTAC:rnFusion350-B-B/E/J/U:rvr01:cvnNA:ct3:cvrNA:
dmi.product.name: MotherBoard Fusion350-B-B/E/J/U
dmi.product.version: MotherBoard 01
dmi.sys.vendor: MotherBoard By ZOTAC

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Solitaire, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Solitaire (bill-s0l)]

Sorry for the delay.

I installed kernel 3.17.1-031701-generic #201410150735

System boots fine with this kernel.

Their is an update for kernel 3.16.0-26 issued today.

Should I install that or just wait?

[penalvch (penalvch)]

Solitaire, the next step is to fully reverse commit bisect from kernel 3.16 to 3.17.1 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Solitaire (bill-s0l)]

Hi

Can't get the error to show up again. Every 3.16.#-31 kernel listed works.

It seems only to be the 3.16.0-26 34 kernel that has the problem.

Do you want me to install the update for 3.16.0-26 and see if that version works ?

[penalvch (penalvch)]

Solitaire, it appears 3.16.0-26.34 was a Proposed repository kernel, which has been superceded ~3 hours ago with 3.16.0-26.35. Could you please clarify if the issue is reproducible in both the current update kernel 3.16.0-25.33, and the latest Proposed kernel?

[Solitaire (bill-s0l)]

The problem happened with BOTH 3.16.0-26.34 and 3.16.0-26.35

Previous kernel 3.16.0-25.33 works fine.

Kernel Main Line build 3.16.0-031 works fine as well.

[Solitaire (bill-s0l)]

Also all the 3.17 work fine and 3.18-RC7 kernel works as well.

[penalvch (penalvch)]

Solitaire, just to clarify, which 3.16.0-031 mainline kernel did you test specifically?

[Solitaire (bill-s0l)]

The specific kernel was: linux-image-3.16.0-031600-generic

[penalvch (penalvch)]

Solitaire, if the issue is not reproducible in mainline (which the Utopic kernel is rebased off of) but is in Proposed, then it would appear a downstream (Ubuntu) issue, not an upstream one. Hence, I'll mark this Triaged for now as bisecting the downstream Ubuntu kernel to a specific commit tends to end in a merge base issue noted in https://wiki.ubuntu.com/Kernel/KernelBisection .

Thank you for your understanding.

[Solitaire (bill-s0l)]

Thanks for your help.

I'll remove the problematic 'Proposed' kernel now and stick to a known working Kernel for now.

[Alberto Salvia Novella (es20490446e)]

After upgrading Linux 3.16.0-25 to 3.16.0-28 the problem appeared to me, rendering my system unusable.

[penalvch (penalvch)]

Alberto Salvia Novella, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Alberto Salvia Novella (es20490446e)]

@ Christopher M. Penalver:
For the title, I think it's more relevant to mention that it concerns the graphics processor than its control register number 2.

@ Joseph Salisbury:
As said in <https://wiki.ubuntu.com/Bugs/Bug%20importances>, bugs that renders the system temporarily or permanently unusable shall have a priority of "critical".

[Alberto Salvia Novella (es20490446e)]

The new report is <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401826>.

[penalvch (penalvch)]

Alberto Salvia Novella, thanks for filing a report against your hardware. Regarding the title, saying its a radeon processor issue is premature, and over reaching. For example, I have a radeon processor, and this problem is not reproducible.

[Alberto Salvia Novella (es20490446e)]

@ Christopher M. Penalver:

Okay, but control register 2 is a piece of hardware in the graphics card. So mentioning it without saying it is from the graphics is meaningless, as the control register could belong to any hardware.

[Benoe (benoe77)]

I have the same problem, in Ubuntu 14.04 with kernel 3.13.0-43-generic

Foxconn R30-A1
Motherboard AHD1S-K
Processors Supported EME350GBB22GTD;Support Zacate Dual Core APU, Max processor power up to 18w
VGA Graphics AMD Radeon HD 6310 Graphics

http://paste.ubuntu.com/9519447/

[Joseph Salisbury (jsalisbury)]

I'd like to perform a reverse bisect to figure out which commit upstream fixes this regression. It would be very helpful to know the last kernel that had this issue and the first kernel that did not.

Can you test the following kernels and report back:

v3.16.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-utopic/
v3.16.7-ckt1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt1-utopic/

The Ubuntu 3.16.0-26.34 kernel is based off of upstream v3.16.7-ckt1, and the Ubuntu 3.16.0-25.33 kernel is based off of upstream v3.16.7. If v3.16.7 is good and v3.16.7-ckt1 is bad, I can bisect between those two versions.

Thanks in advance!

[Sslaxx (stuart-sslaxx)]

As of the latest kernel update (3.16.0-28.38) I am still getting this error happening.

My graphics hardware is an AMD Radeon HD 6670 using the open source drivers. Sabertooth 990FX R2.0 motherboard.

[Benoe (benoe77)]

Linux kernel v3.16.7 as of linux-image-3.16.7-031607-generic_3.16.7-031607.201410301735_amd64.deb is working.
This workaround is taken from Kodi forums: http://forum.kodi.tv/showthread.php?tid=174854&page=225

[Alberto Salvia Novella (es20490446e)]

@ Joseph Salisbury:

3.16.7 is not affected.
v3.16.7-ckt1 is affected.

[Joseph Salisbury (jsalisbury)]

It appears the regression was introduced in v3.16.7-ckt1. Can you also see if v3.16.7-ckt2 exhibits this bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.7-ckt2-utopic/

[Alberto Salvia Novella (es20490446e)]

@ Joseph Salisbury:

ckt2 kernel works! :-o

[Joseph Salisbury (jsalisbury)]

That is great news. That means Utopic will pick up the fix when the v3.16.7-ckt2 updates are applied in the next SRU cycle.

[ATAKAMA (atakama)]

This bug also affects the latest Trusty kernel, 3.13.0-43 on an AMD E-350 with a Radeon 6310 GPU.
Should I file another bug report for Trusty?

[Sslaxx (stuart-sslaxx)]

Please, do.

[Joseph Salisbury (jsalisbury)]

Utopic will pick up the fix when it gets the 3.16.7-ckt2 updates. Those updates have now been applied to the -proposed repository. Would it be possible for you to test this latest kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Thank you in advance!

[Solitaire (bill-s0l)]

I'll try it as soon as I can.
Due to other problems (I.e. I messed up my system) I did a wipe and feel back to using 14.04LTS
(Which also has the same bug with the default installed kernel)

I'll reinstall 14.10 on a spare drive in the machine and get the proposed kernel a test.

[Alberto Salvia Novella (es20490446e)]

If the correct kernel version is 3.16.7-031607, I confirm it is working.

[Solitaire (bill-s0l)]

I can confirm that kernel 3.16.7-031607 works on my system as well.

[Rolf Leggewie (r0lf)]

utopic has seen the end of its life and is no longer receiving any updates. Marking the utopic task for this ticket as "Won't Fix".