Bug 1373026 - kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Summary: kernel: BUG: unable to handle kernel NULL pointer dereference at 000000000000...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-amd
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-04 21:54 UTC by Bruno Rafael
Modified: 2017-08-08 17:00 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 17:00:55 UTC
Type: Bug


Attachments (Terms of Use)
Full kernel log with the error at line 30258 (4.93 MB, text/plain)
2016-09-04 21:54 UTC, Bruno Rafael
no flags Details

Description Bruno Rafael 2016-09-04 21:54:36 UTC
Created attachment 1197699 [details]
Full kernel log with the error at line 30258

Description of problem:
Using the AMDGPU driver for R9 Fury (sapphire tri-x) causes a intermitent kernel crash during boot while using kernel version 4.7.2. The bug does not happen when using kernel 4.6.7-300.


Version-Release number of selected component (if applicable):
Kernel 4.7.2-201.fc24


How reproducible:
Intermitent, sometimes it crashes during boot, sometimes it crashes right after x login and sometimes it doesn't crash at all.


Steps to Reproduce:
1. Using an AMD Fiji card (in my case AMD R9 Fury Tri-x with UEFI Firmware provided by sapphire) install kernel 4.7.2
2. Boot and wait

Actual results:
In the worst case, it crashes during boot, before the Graphical.target starts the X server.

Expected results:
System boots as usual.


Additional info:
Hardware config:
Motherboard: Asus M5A99FX PRO R2.0
Processor: AMD FX 9590
Ram: 32GB Kingstom BEAST 1866Mhz (I run a lot of VMS)
/boot Drive: Samsung 850 EVO
/home Drive: 2X Western Digital Caviar Black using MD Software RAID 1
Video: 2X Sapphire R9 Fury Tri-x with UEFI Firmware

Fedora 24 Using the xfce spin, with a few packages from RPMFUSION and SELINUX ON
There is another Hard Disk with windows Installed where I use all that GPU Horsepower to Game.
Fedora is my Main OS, where I work and do my everyday computing.

I'll be glad to run any debugging steps using my hardware to help funnel down the problem, I'm somewhat familiar with custom kernels and low level debugging tools

Comment 1 Veteran 2016-09-07 18:51:11 UTC
I am getting this error on a fedora 24 virtualbox VM lxde spin. I realize the kernel is tainted (and no one likes 32bit), but I hate downgrading kernels.

Comment 2 Fedora End Of Life 2017-07-25 22:49:55 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-08-08 17:00:55 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.