Red Hat Bugzilla – Bug 521703
kernel panic: powerpc coherency mismatch: 184.108.40.206-43 setup-common.c:653
Last modified: 2009-10-12 17:43:18 EDT
Created attachment 360016 [details]
kernel panic at boot time
Description of problem:
A kernel panic appears as soon as the yaboot boot manager loads the kernel.
Version-Release number of selected component (if applicable):
I've included a "screenshot" done via my quite old camera ... the focus hmm yeah the focus sucks ;-)
kernel coherency:on != device tree_coherency: off
kernel BUG at arch/powerpc/kernel/setup-common.c:653!
Caused by having Amiga One support enabled. Fixed in 220.127.116.11-50
*** Bug 521597 has been marked as a duplicate of this bug. ***
Created attachment 360868 [details]
higher quality screenshot of concerned kernel panic
I wasn't sure if this would help, but I was able to photograph it more legibly.
(In reply to comment #4)
> Created an attachment (id=360868) [details]
> higher quality screenshot of concerned kernel panic
> I wasn't sure if this would help, but I was able to photograph it more legibly.
Actually the bug should be already fixed (see comment #2). I will close this bug as soon as a new kernel release is made public and I could test that release.
*** Bug 522963 has been marked as a duplicate of this bug. ***
*** Bug 522876 has been marked as a duplicate of this bug. ***
kernel-18.104.22.168-64.fc11 has been submitted as an update for Fedora 11.
The new version (22.214.171.124-64) works fine. Thanks!
How do you get 126.96.36.199-64?
I try yum update, and it doesn't see it. And yum info only shows to 5-43.fc11 .
(In reply to comment #10)
> How do you get 188.8.131.52-64?
> I try yum update, and it doesn't see it. And yum info only shows to 5-43.fc11 .
It takes some time until the package is shipped completely. For example at the moment it is only available in the testing tree. Additionally it takes some time to sync the mirrors.
If you still want to update (take note that it is still in the testing tree), then you have two options:
- run "yum update --enablerepo=updates-testing kernel"
- or you can use the link from comment #8, click on builds and download all the needed RPMs manually. Then run "rpm -Uvh kernel-*" and the new ones get installed.
Or just wait until it gets pushed to the stable tree.
But until now, no one can install fedora on ppc because of this bug. How long we have to wait?
(In reply to comment #12)
> But until now, no one can install fedora on ppc because of this bug. How long
> we have to wait?
This is a valid point. The anaconda bug on the Fedora 11 ppc DVD forces even full dvds to netinst, unless you use an additional dvd as a repo (which is a problem in certain systems). This means that any new installations on such machines will fail until this bugfix is put through the system. Basically, atm fedora 11 stable is *BROKEN* for ppc users who only have one internal dvd-rom drive and no external dvd-rom drive.
(In reply to comment #13)
> This is a valid point. The anaconda bug on the Fedora 11 ppc DVD forces even
> full dvds to netinst, unless you use an additional dvd as a repo (which is a
> problem in certain systems). This means that any new installations on such
> machines will fail until this bugfix is put through the system. Basically, atm
> fedora 11 stable is *BROKEN* for ppc users who only have one internal dvd-rom
> drive and no external dvd-rom drive.
Thanks, as i read here, the kernel update is in updates-testing, i added it as additional repository, but still missing at all, at least on italian repository.
update still not in testing repo, and here is no official itallian one
ups, it here....
kernel-184.108.40.206-64.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
Maybe I did something wrong, but I still can't boot with this kernel. Now I get a "vmlinuz-220.127.116.11-64.fc11.ppc: Not a valid ELF image" when I try to boot my iMac with the latest F11 kernel. Before I had the problem described in #522876 (now a duplicate of this bug).
A rough fix for installation process is to start installing FC10 and after moving to FC11 with the new 18.104.22.168-64 and work perfect!
Indeed I had done something wrong when I reported the problem with the kernel image (2009-09-30), a mistake in my handwritten yaboot.conf bootloader configuration file. Now I have a working F11 setup. I still had to slightly change the kernel 'append' line, though: with the default 'append="rhgb quiet"' I always got a non-fatal "kernel failure" in the nvidiafb driver, which extremely slowed down the boot process (to more than four minutes). I fixed that by changing the 'append' line to "quiet video=ofonly".