Bug 1403140

Summary:	System hangs and reports unable to handle kernel NULL pointer dereference after reset
Product:	[Fedora] Fedora	Reporter:	vafr <rf.av>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, rfe.gen
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-20 21:44:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description vafr 2016-12-09 08:16:48 UTC

Description of problem:
System hangs. Can only be resolved by hw reset. Reports oops after reset.

Version-Release number of selected component (if applicable):


How reproducible:
Happened twice in two weeks (approximately) both while working with Firefox  

Steps to Reproduce:
1. Unknown
2.
3.

Actual results:


Expected results:


Additional info:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000013

BOOT_IMAGE=/vmlinuz-4.8.11-100.fc23.x86_64 root=/dev/mapper/fedora_linux-root ro rd.lvm.lv=fedora_linux/root rd.lvm.lv=fedora_linux/swap rhgb quiet LANG=nl_NL.UTF-8

4.8.11-100.fc23.x86_64

Comment 1 Fedora End Of Life 2016-12-20 21:44:50 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Comment 2 vafr 2016-12-21 19:20:55 UTC

Seems there is a relation to bios upset here so I don't think OS is the culprit anyway.

Also got messages that 'AI Overclocking failed' before booting. Checked the bios backup battery which was 2,5V. Guess this still should be sufficient (no specification on this in mobo user manual). Replaced the battery with a new one. Restored safe bios settings without auto overclocking feature and did not see this problem again since...

Anyone that did see the same problem with ASUS mobo?

Comment 3 rfge 2017-05-30 18:08:13 UTC

Turns out to be power supply after all.

Bloated capacitors on 3v3 and -12v output.

After replacement of ps problem is gone.

Measurement shows that capacitor on 3v3 only has 10% of rated capacity left.