Feisty doesn't boot anymore

[Kristoffer Bergström]

After the updates this morning I don't get past the smallest little bar of orange. The computer freezes and caps lock and scroll lock start blinking. On recovery mode boot, this is what I get:

ata5: SATA link up 1.5 Gbps (Sstatus 113 Scontrol 300)
ata5.00: ata_hpa_resize 1: sectors = 586114704, hpa_sectors = 15689360
ata5.00: ATA-7: Maxtor 6L300S0, BACEIG20, max UDMA/133
ata5.00: 586114704 sectors, mult. 2: LBA48 NCQ (depth 31/32)

HARDWARE ERROR
CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f
TSC 10cbe73e09
This is not a software problem!
Run through mcelog --ascii to decode and contact your hardware vendor.
Kernel panic - not syncing: Machine check

This on Ubuntu 7.04 beta amd64
Hardware:
Asus A8N-E
AMD64X2 3800+
2 gb RAM
GeForce 6600
Hard-drives:
WDC WD2500YD-01NVB1
Maxtor 6L300S0
ST310014A

I'm going to try and install an old kernel and tell you how it goes. I'm on the livecd now.

[Thierry Lemaire (thierry-lemaire)]

I have the same problem with the last kernel update (2.6.20.14.23).

After the smallest bar of orange (ubuntu start) I can read this message :

busybox v1.1.13

/bin/sh : can't access tty; job control turned off (initramfs)

So I boot with the previous kernel (2.6.2.13) and it works fine

[Kristoffer Bergström (kabtoffe)]

Reverting linux-image-2.6.20-14-generic_2.6.20-14.23 to linux-image-2.6.20-14-generic_2.6.20-14.22 fixes this problem.

[gmlion (gm-l)]

This is a common problem. The kernel upgrade is in fact experimental still. The kernel team is already working on a solution. What will help should be dmesg output from -14.22 and -14.23 (this kernel) as well as "lspci -vvn".

[gmlion (gm-l)]

This is a duplicate. Anyway the fix seems to have been committed.

[Toni Hermoso Pulido (toniher)]

I have got the same problem in a MacBook Pro 15'. It happened in previous kernel during Feisty. A regression?

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!