Bug 1046141

Summary: Kerneloops
Product: [Fedora] Fedora Reporter: KitchM <tech>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: cebbert, collura, extras-orphan, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, tech
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-12 17:16:01 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:
Embargoed:
Attachments:
Description Flags
ABRT Shows Kerneloops
none
dmesg from boot of different version on kernel than got error none

Description KitchM 2013-12-23 20:15:03 UTC
Created attachment 840943 [details]
ABRT Shows Kerneloops

Description of problem:
Many Kerneloops are reported in ABRT.

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


How reproducible:
Unknown


Steps to Reproduce:
1. Unknown
2.
3.

Actual results:


Expected results:


Additional info:
EDAC DEBUG: edac_mc_sysfs_init: device mc created

The problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out. In order to provide valuable problem reports, ABRT will not allow you to submit this problem. If you have time and want to help the developers in their effort to sort out this problem, please contact them directly.

Comment 1 Josh Boyer 2014-01-06 21:28:08 UTC
Please attach the full dmesg output from a fresh boot after this happens.

Comment 2 collura 2014-02-06 09:59:26 UTC
Created attachment 860084 [details]
dmesg from boot of different version on kernel than got error

have been running kernel3.14.0-0.rc1.git0.1.fc21.x86_64 for a few days but some updates just went through and now it doesnt boot so booted to kernel-3.12.9-301.fc20.x86_64 and ran dmesg from that.  if i figure what update caused the breakage i will post here.

Comment 3 Josh Boyer 2014-02-12 17:16:01 UTC
(In reply to collura from comment #2)
> Created attachment 860084 [details]
> dmesg from boot of different version on kernel than got error
> 
> have been running kernel3.14.0-0.rc1.git0.1.fc21.x86_64 for a few days but
> some updates just went through and now it doesnt boot so booted to
> kernel-3.12.9-301.fc20.x86_64 and ran dmesg from that.  if i figure what
> update caused the breakage i will post here.

Not sure what this has to do with the original bug.  Please open a new one.

This bug has been sitting in NEEDINFO for a month, so closing it out.

Comment 4 KitchM 2014-06-09 14:21:29 UTC
Please explain the procedure.