Description of problem: System does not boot, and it gives the following message: Kernel panic - not syncing: Attempted to kill init! ------------------------------ Hardware Configuration:RX3600 ------------------------------ SYSTEM INFORMATION Date/Time: Jul 30, 2007 21:58:57 (20:07:07:30:21:58:57) Manufacturer: hp Product Name: server rx3600 Product Number: AB596A Serial Number: USE0609KLC UUID: 8CF4AA42-C3E3-11DA-9048-E246ADD8402C System Bus Frequency: 333 MHz -------------------------- Current firmware revisions MP FW : F.02.09 BMC FW : 70.59 EFI FW : ROM A 05.66, ROM B 06.15 System FW : ROM A 02.03, ROM B 82.01, Boot ROM B PDH FW : 50.07 DHPC FW : 01.23 UCIO FW : 03.0b PRS FW : 00.08 UpSeqRev: 0c, DownSeqRev: 08 HFC FW : 00.04 SetRev: 00 ------------------------------ PROCESSOR MODULE INFORMATION # of L3 L4 Family/ CPU Logical Cache Cache Model Processor Module CPUs Speed Size Size (hex.) Rev State ------ ------- -------- ------ ------ ------- --- ------------ 0 4 1.66 GHz 9 MB None 20/01 A1 Active 1 4 1.66 GHz 9 MB None 20/01 A1 Active CPU threads are turned on. CPU pstates are turned on -------------------------- MEMORY INFORMATION Extender 0: ---- DIMM A ----- ---- DIMM B ----- DIMM Current DIMM Current --- ------ ---------- ------ ---------- 0 512MB Active 512MB Active 1 512MB Active 512MB Active Extender 1: ---- DIMM A ----- ---- DIMM B ----- DIMM Current DIMM Current --- ------ ---------- ------ ---------- 0 ---- ---- 1 ---- ---- Active Memory : 2048 MB Installed Memory : 2048 MB ----------------------------- - Intent of the test and software setup: - cpuconfig threads on - use a default installation onto one of the internal storage drives (SAS RAID 1+0), HP Smart Array P600 - include at least one of each HBA (and devices on all ports): Redstone (core I/O), plug-in Redstone, A7173A, AD167A, AD168A, AB429A, (RAID cards must have at least one each RAID 0, RAID 1+0, and RAID 5 or ADG volume connected) - use an additional Redstone as core I/O (AB352A moves to slot 10) - a Qlogic card was placed in a shared slot 9 for this test, After the hardware was setup and the OS installed the system did not boot, Examples of messages: cciss: out of memory cciss/c0d0: cciss: out of memory cciss/c0d1: cciss: out of memory cciss/c0d2: cciss: out of memory cciss/c0d3: ------------and: setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys ------------------- elilo.conf prompt timeout=20 default=linux relocatable image=vmlinuz-2.6.18-36.el5xen vmm=xen.gz-2.6.18-36.el5 label=linux initrd=initrd-2.6.18-36.el5xen.img read-only root=/dev/cciss/c1d0p3 append="dom_mem=1G -- rhgb" ------------------------------------------------------------ Version-Release number of selected component (if applicable): RHEL 5.1 Partner Beta, vmm=xen.gz-2.6.18-36.el5 How reproducible: always Steps to Reproduce: - follow test intent, Actual results: - Kernel panic - not syncing: Attempted to kill init! Expected results: - System boots to OS Additional info: will reinstall the OS to different storage
It appears that this is probably a dup of 249104 which will be fixed in the next kernel. The fix for that issue was not in in time for the beta.
Looks like a core kernel problem, not xen-specific; reassigning for now.
Marilise, I think what you are seeing is directly related to the "cciss: out of memory" errors which is fixed. Can you grab the latest kernel from: http://people.redhat.com/dzickus/el5 and verify the problem goes away? thanks, - Doug
Hello, Marilise. Could you please retest on the kernel described above in comment #3? We think this is a dup of bug 249104, which has been fixed in that kernel. Thanks in advance.
Marilise, I believe this issue is resolved. Let me know ASAP if you think otherwise. thanks, - Doug
This has been verifed as being fixed. It is the same issue as 249104. *** This bug has been marked as a duplicate of 249104 ***