Netboot PPC crashes with"Fixing recursive fault but reboot is needed!"

[Jackson Doak]

On the first boot after install the netboot system doesn't reach the command prompt instead showing the error "Fixing recursive fault but reboot is needed!", no amount of reboots stop this. I know this doesn't affect all PPC computers or even all G4's as wxl's works fine. i will upload a hardware profile soon. As a result i don't think netboot quantal was released for ppc.

[Jackson Doak (noskcaj)]

I was told to make this by people in the other bug, please dont make as a duplicate

[penalvch (penalvch)]

Jackson Doak, thank you for reporting this and helping make Ubuntu better. Could you please boot into a live CD environment and execute the following:
apport-collect 1071880

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[ojordan (ojordan12345)]

This is obviously (and always has been) a duplicate of bug 1066435 .I don't know why you were told to create a new bug, it is wasting your time and others. The workaround is here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066435/comments/62

[penalvch (penalvch)]

ojordan, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071880/comments/3 :
>"This is obviously (and always has been) a duplicate of bug 1066435 ."

First, to maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/project/about-ubuntu/conduct . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind.

Now, it is not obvious, nor always has been, for everyone who reads bug 1066435 to know that the problem they experience is a duplicate. Not everyone is a developer or advanced triager.

>"I don't know why you were told to create a new bug, it is wasting your time and others."

See above. As well, as per Ubuntu Kernel team and Ubuntu Bug Control policy, it is desired for those who have or may have a linux (Ubuntu) bug to file a new report to document the hardware and logs. This prevents "Me too!" and other unhelpful comments, keeps the report focused on the original reporter and their hardware, and expedites the issue they are experiencing. As is known, the same error message may be caused by different underlying problems, due to disparate hardware, requiring different fixes to address. For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

>"The workaround is here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066435/comments/62"

Jackson Doak, in addition to providing the information requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071880/comments/2 could you also please try the WORKAROUND noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066435/comments/62 to see if your problem is addressed by this?

Thank you for your understanding.