Removing append="quiet" from yaboot.conf causes kernel oops

Bug #83089 reported by grazie
0
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

Hardware PPC G4 1.25GHz with 1.75G memory.
Using xubuntu feisty herd 3 candidate released 01/02/07
linux-source-2.6.20 version 2.6.20-5.7 (specifically linux-image-2.6.20-5-powerpc)

Booting the kernel without append="quiet splash" parameters (as generated by install process) from /etc/yaboot.conf causes a kernel oops. It's the 'quiet' removal that causes the oops.

I do not currently have access to digital camera, but if the trace details are required I can probably borrow one.

Removing append="quiet splash" parameters from /etc/yaboot.conf on edgy release with linux-image-2.6.17-10-powerpc causes no problems.

Revision history for this message
didier (did447-deactivatedaccount) wrote :

Hi,

If you've installed ubuntu can you upgrade your kernel to 2.6.20.6?

I can't reproduce it, on the other hand I hadn't this bug with 2.6.20.5 either.

Without taking a picture where did it oops?

Changed in linux-source-2.6.20:
assignee: nobody → did447
status: Unconfirmed → Needs Info
Revision history for this message
grazie (grazie-deactivatedaccount) wrote :

Although the problem was repeatable, since the tests were run I've upgraded

2007-02-03 13:48:34 status installed volumeid 103-0ubuntu6
2007-02-03 13:49:01 status installed udev 103-0ubuntu6
g

This appears to have fixed the problem. I cannot force a downgrade of volumeid and udev back to 103-0ubuntu5, so would need to start from scratch and give you the oops location.

Revision history for this message
didier (did447-deactivatedaccount) wrote :

thanks but don't bother with it, Feisty is a work in progress. I'm closing this bug as fix released.

Changed in linux-source-2.6.20:
assignee: did447 → nobody
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.