Feisty (2.6.20-13) boot crc error

Bug #101884 reported by Dada Priyatosh
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After upgrade from Edgy occasionally got a CRC error message when booting (both normal and restricted). Same with 2.6.20-12.
But sometimes after repeating with a same kernel I could manage to boot without problem. Re-download/re-install wont fix.
Not a SATA installation.

Tags: feisty
Dada Priyatosh (dada-p)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. What exactly is the content of that CRC error message? Thanks in advance.

Revision history for this message
Dada Priyatosh (dada-p) wrote :

After "Starting up..." message it gives "crc failed" and then "System halted". Same with recovery kernel (no any additional messages). Old kernel from Edgy (2.6.17-10) booting ok. Sometimes (not so often) after continuous restarting new kernel could boot up.

Revision history for this message
Phillip Lougher (phillip-lougher) wrote :

This may be a hardware or memory problem with your computer.

Can you run a memory test program? There is a memory test boot menu option on the Feisty liveCD.

Thanks.

Changed in linux-source-2.6.20:
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Dada Priyatosh (dada-p) wrote :

Memory test ok.

Revision history for this message
Dada Priyatosh (dada-p) wrote :

Same with 2.6.20-14

Revision history for this message
Josh Ross (bross-gwlc) wrote :

I get the same error with my MacBookPro. In addition, my keyboard does not work.

Revision history for this message
Dada Priyatosh (dada-p) wrote :

Finally, it was a memory problem. Strange enough, there was no errors with memtest... Anyway.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-source-2.6.20 (Ubuntu) because there has been no activity for 60 days.]

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.