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
Created attachment 1120487 [details] Initial oops that taints kernel
Created attachment 1120488 [details] Subsequent oops
None of this happens with kernel-4.2.8. That is the last working kernel.
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.
Still broken with 4.3.5-200 in updates-testing.
Created attachment 1128575 [details] Actually, broken in 4.2.8 also It can happen in 4.2.8 also. So not a regression.
Still broken in kernel-4.3.6-201.fc22.i686
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
Created attachment 1130719 [details] dmesg 4.3.5-200.fc22.i686
Still broken in kernel-4.4.3-200.fc22.i686
Created attachment 1131153 [details] oops from 4.4.3 An update of the oops for latest f22 kernel.
Still broken in kernel-4.4.11-200.fc22.i686
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.