Red Hat Bugzilla – Bug 150837
Bad: Kernel panic
Last modified: 2015-01-04 17:17:39 EST
Same behaviour on fc3 and with kernel
Fedora Core (2.6.10-1.766_FC3)
If you add "ide=nodma" in /etc/grub.conf Linux boot just ok.
My motherboard is Soyo SY-P4I 845PE Lite (if that matters).
+++ This bug was initially created as a clone of Bug #147723 +++
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)
Description of problem:
Kernel 2.6.9-1.6_FC2 was the last working kernel version that work with my
Next last one's folowing give kernel panic pointing to harddisks lock.
Could'n add fc3. That gave me same result. So what can i do now ? Stuck with
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Kernel 2.6.9-1.6_FC2 was the last working kernel version
2.Next one's folowing give kernel panic pointing to harddisks lock
latest erratas have a bunch of ide layer fixes, can you confirm this bug still
exists with the 2.6.11-1.27_FC3 ? (if not,
http://people.redhat.com/davej/kernels/Fedora/FC3/ has further updates).
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
I haven't tried with kernel-2.6.12-1.1372_FC3, but kernel 2.6.11-1.35_FC3 has
the panics in the same way as 2.6.10-1.766_FC3.
Please retry with the latest errata.
This bug has been mass-closed along with all other bugs that
have been in NEEDINFO state for several months.
Due to the large volume of inactive bugs in bugzilla, this
is the only method we have of cleaning out stale bug reports
where the reporter has disappeared.
If you can reproduce this bug with current FC3 updates, please
reopen this bug.
If you are not the reporter, you can add a comment requesting
it be reopened, and someone will get to it asap.
If you are not the reporter, but can reproduce this problem against
FC4, please open a new bug.