kernel panic on boot - not syncing attempted to kill init

[Rob Pearman]

Karmic (9.10) beta downloaded c. 01.30am BST on 19/09/2009 - ubuntu-9.10-beta-desktop-i386.iso

Having burned the ISO to CD and booted from it I get a kernel panic after choosing my language and attempting to boot the live CD.

Digital camera screen image and HardInfo output attached.

It looks like this is a re-occurrence of a problem we had in previous releases running the 32 bit kernel on 64 bit processors - see bug #173797.

I'm running an Asrock 2Core1333-2.66G motherboard with Intel 2140 CPU.

Note I can boot from the downloaded ISO using VirtualBox without any problems.

[Rob Pearman (rob-pearman)]

And HardInfo report...

[Rob Pearman (rob-pearman)]

Looks like the problem is still apparent in Lucid beta 1. Screen shot attached.

[Jeremy Foshee (jeremyfoshee)]

Hi Rob,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 456790

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Rob Pearman (rob-pearman)]

Hi Jeremy, thanks for picking this up again.

I've downloaded the development release from the URL you sent me and it still fails when trying to boot from the latest i386 ISO. I think it's the same reason / messages but I'll double-check and post an update / screen shot soon, along with the output of the apport-collect command.

As this seems to be a re-occurrence of an earlier problem (#173797), have you looked at the resolution of that one?

Thanks
Rob

[Rob Pearman (rob-pearman)]

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.UTF-8
Uname: Linux 2.6.28-18-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Rob Pearman (rob-pearman)]

I downloaded the linux-image-2.6.34-999-generic_2.6.34-999.201005121008_i386.deb kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ just now and having tried to boot with this kernel get the same fault. I'll upload a screen print in case there are any subtle or important differences.

[Rob Pearman (rob-pearman)]

Tried the Maverick beta with the same (or at least very similar) results.
What I presume are the key messages are as follows:
>>>>>>>>>>>>>>>>>>>>>
Code: Bad EIP value
EIP: [01c00f01>] 0x1c00f01 SS:ESP 0068:f7079f0f
CR2: 0000000001c00f01
Kernel Panic - not syncing: Attempted to kill init!
Pid: 1, comm: swapper Tainted: G D 2.6.36-19-generic #28-Ubuntu
<<<<<<<<<<<<<<<<<<<<<
Screen dump of the screen on failure also attached, containing the call trace

Help!

[Rob Pearman (rob-pearman)]

Massive relief as this problem has been resolved by upgrading my BIOS from the ASRock site, here:

http://www.asrock.com/mb/download.asp?Model=2Core1333-2.66G&o=BIOS

Maverick live CD boots normally, installed to hard disk and booted OK from there.

With thanks to everyone who has tried to help me on this, please close the call.

Best regards
Rob

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.