Bug 1303990 - kernel oops intel video
Summary: kernel oops intel video
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-02 16:00 UTC by Stuart D Gathman
Modified: 2016-07-19 18:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:41:56 UTC
Type: Bug


Attachments (Terms of Use)
Initial oops that taints kernel (3.71 KB, text/plain)
2016-02-02 16:02 UTC, Stuart D Gathman
no flags Details
Subsequent oops (4.58 KB, text/plain)
2016-02-02 16:03 UTC, Stuart D Gathman
no flags Details
fpaste --sysinfo (25.46 KB, text/plain)
2016-02-02 16:30 UTC, Stuart D Gathman
no flags Details
Actually, broken in 4.2.8 also (25.91 KB, text/plain)
2016-02-19 16:23 UTC, Stuart D Gathman
no flags Details
dmesg 4.3.5-200.fc22.i686 (86.80 KB, text/plain)
2016-02-26 06:27 UTC, Lars Alexandersen
no flags Details
oops from 4.4.3 (30.15 KB, text/plain)
2016-02-27 19:05 UTC, Stuart D Gathman
no flags Details

Description Stuart D Gathman 2016-02-02 16:00:15 UTC
Description of problem:
kernel oops that taints kernel

Version-Release number of selected component (if applicable):
kernel-4.3.4-200.fc22.i686

How reproducible:
always

Steps to Reproduce:
1. boot 4.3 kernel
2.
3.

Actual results:
tainted kernel

Expected results:
clean kernel log

Additional info:
Possibly the underlying cause of bug#1303979

Comment 1 Stuart D Gathman 2016-02-02 16:02:53 UTC
Created attachment 1120487 [details]
Initial oops that taints kernel

Comment 2 Stuart D Gathman 2016-02-02 16:03:47 UTC
Created attachment 1120488 [details]
Subsequent oops

Comment 3 Stuart D Gathman 2016-02-02 16:04:47 UTC
None of this happens with kernel-4.2.8.  That is the last working kernel.

Comment 4 Stuart D Gathman 2016-02-02 16:30:58 UTC
Created attachment 1120511 [details]
fpaste --sysinfo

Run with kernel-4.2.8 so that the system is stable enough to actually, like, post stuff to bugzilla.

Comment 5 Stuart D Gathman 2016-02-19 05:22:24 UTC
Still broken with 4.3.5-200 in updates-testing.

Comment 6 Stuart D Gathman 2016-02-19 16:23:37 UTC
Created attachment 1128575 [details]
Actually, broken in 4.2.8 also

It can happen in 4.2.8 also.  So not a regression.

Comment 7 Stuart D Gathman 2016-02-24 00:06:04 UTC
Still broken in kernel-4.3.6-201.fc22.i686

Comment 8 Lars Alexandersen 2016-02-26 06:14:41 UTC
Possibly same problem here, at least symptoms look familiar.
fpaste --sysinfo
4.2.8-200.fc22.i686
http://paste.fedoraproject.org/328962/14563814
(no problems for me)

4.3.5-200.fc22.i686
http://paste.fedoraproject.org/328973/45638186
(problems galore - display restart after log in and subsequent hangs again and again)

To me it looks like problem is display related but do not let it lead you astray.
Machine is Genuine Intel® CPU T2400 @ 1.83GHz × 2, 32-bit with Intel® 945GM

Comment 9 Lars Alexandersen 2016-02-26 06:27:25 UTC
Created attachment 1130719 [details]
dmesg 4.3.5-200.fc22.i686

Comment 10 Stuart D Gathman 2016-02-27 18:58:31 UTC
Still broken in kernel-4.4.3-200.fc22.i686

Comment 11 Stuart D Gathman 2016-02-27 19:05:32 UTC
Created attachment 1131153 [details]
oops from 4.4.3

An update of the oops for latest f22 kernel.

Comment 12 Stuart D Gathman 2016-06-04 17:46:35 UTC
Still broken in kernel-4.4.11-200.fc22.i686

Comment 13 Fedora End Of Life 2016-07-19 18:41:56 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.