Bug 615878
| Summary: | Kernel panic - not syncing: Attempted to kill init! | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Attila <bugs.kde.attila> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 15 | CC: | anton, gansalmon, gavinflower, itamar, jonathan, jwboyer, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-12 12:28:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Attila
2010-07-19 08:06:42 UTC
Fedora 14 Aplha AMD 4200+ dual core 64 bit 4 GB After the last set of yum updates, a few hours ago. after a seg faults got the message: 'Kernel panic - not syncing: Attempted to kill init!' Note that the after the stack trace the right most 2 lights on the keyboard were flashing and the keyboard was unresponsive. Not sure how to capture the details, so the following is manually transcribed (may have transcription errors): [...] dracut: Switching root init[1]: segfault @ 364be1fbf8 ip 000000364bc033c7 sp 00007fffcd4967d0 error 7 in 1d-2.12.90.so[364bc00000+1f000] init used greatest stack depth: 2856 bytes left Kernel panic - not syncing: Attempted to kill init!' Pid: 1 , comm: init Not tainted 2.6.35.4-28.fc14.x86_64 #1 Call Trace: [...] panic occurred, switching back to text console This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed. The bug is still there in Fedora 14 and 15. Therefore i reopened this bug. The initrd is getting a segfault on your machine and exiting. That isn't really a kernel problem. You should probably try running memtest86+ overnight to see if any memory errors show up. The memtest86+ went through with no error. Before I wrote this report, I have tested the system already with different RAM to make sure that this is not a memory bug. Like I mentioned before the kernel panic appears only using the RocketRaid controller and 4GB of RAM instead of 2GB. The combination of the NVidia-Onboard-Raid and 4GB of RAM is OK. Are you still seeing this with the 2.6.43/3.3 kernel updates in F15/F16? If so, the driver being used for the RocketRAID controller is hptiop.ko, correct? Not seen this in Fedora 16, in either my original AMD4200+, or my newer quad core AMD. Nivag, was your bug identical to the original report? In that you were using the RocketRAID card with more than 4GB of DRAM? |