Bug 746585

Summary:	Kernel panic - not syncing: Attempted to kill init!
Product:	[Fedora] Fedora	Reporter:	Hongqing Yang <hoyang>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
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:	2011-10-18 06:10:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Hongqing Yang 2011-10-17 07:11:08 UTC

Description of problem:

This is to run the test cases:
https://fedoraproject.org/wiki/QA:Testcase_anaconda_btrfs_rootfs_on_disk_partition
https://fedoraproject.org/wiki/QA:Testcase_anaconda_ext3_rootfs_on_disk_partition

which root partition with ext3 and btrfs format.
After installation with the first reboot, the following error occured:
 
Kernel panic - not syncing: Attempted to kill init!
Pid:1,comm: switch_root Not tainted 3.1.0-0.rc9.git0.0.fc16.i6866.PAE #1
Call Trace:
[<c081e9db>] ? printk+0x2d/0x2f
 
Version-Release number of selected component (if applicable):


How reproducible:

100%

Steps to Reproduce:
1. install system with minimal 
2. root / with format ext3 or btrfs
3. reboot after installation
  
Actual results:


Expected results:


Additional info:

Comment 1 Chuck Ebbert 2011-10-17 14:08:04 UTC

We really need to see the backtraces from that.

Also, it's not even clear which filesystem was in use from reading the bug report. I would guess btrfs?

Comment 2 Hongqing Yang 2011-10-18 06:10:32 UTC

I cannot reproduce it. close it as it is not a bug.