Bug 1062915

Summary: Kernel panic not syncing; attempted to kill init
Product: [Fedora] Fedora Reporter: David <davidmenhur>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---Flags: jforbes: needinfo?
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-03-17 18:41:55 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
Screenshot of the panice
none
Content of /var/log/messages none

Description David 2014-02-08 16:19:27 UTC
Created attachment 860896 [details]
Screenshot of the panice

Description of problem:
Kernel panic.

Version-Release number of selected component (if applicable):
# uname -a
Linux LCARS 3.12.9-301.fc20.x86_64 #1 SMP Wed Jan 29 15:56:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Using Fedora 20 LXDE.


How reproducible:
In the last few days, happened four times at random moments. I was running Firefox, and VLC in at least, some of them.


Additional info:
See attached an image of the screen after the failure and the content of /var/log/messages around the failure.

I don't know how to diagnose this further, please tell me what should I do in case this happens again, or where to dig for more info.

Comment 1 David 2014-02-08 16:21:11 UTC
Created attachment 860897 [details]
Content of /var/log/messages

The first part, with the NetworkManager warnings, appear repeated many times.

Comment 2 Justin M. Forbes 2014-02-24 13:51:50 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2014-03-17 18:41:55 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for several weeks and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 20, please feel free to reopen the bug and provide the additional information requested.