13.04 Kernel Panic Not Syncing - Attempted to kill init - error code= 0x0000009

[Andrew Fullam]

I'm having an issue booting 13.04. I did a search on the forum but nothing popped up. Basically, it installs fine but upon a reboot into the installation I get a kernel panic: not syncing: Attempted to kill exitcode=0x00000009.

Hardware:

Processor Quad-Core AMD A8-4500M processor (1.9 GHz, 2.8 GHz with Turboboost, 4 MB L2 cache)
Operating System Windows 8
RAM 8 GB (2 x 4 GB)
Graphics card AMD Radeon HD 7640G Discrete-Class
up to 4.98 GB of dedicated RAM
Screen type HD BrightView LED-backlit
Screen resolution 1366 x 768
Screen size 15.6"
Screen features LED backlit
Hard drive 1 TB (SATA, 5400 rpm)
Optical disk drive SuperMulti DVD±R/RW with double layer support
Memory card reader Digital media card reader
USB 2 x USB 2.0
1 x USB 3.0
FireWire No
Modem/Ethernet Integrated 10/100 BASE-T Ethernet LAN
WiFi 802.11b/g/n
Bluetooth No
TV output VGA
HDMI
Expansion card slot No
Sound Altec Lansing speakers with Dolby Advanced Audio
Dolby Advanced Audio

Thanks

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1172755

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

[Andrew Fullam (andrew-fullam)]

I am unable to access the terminal to run apport due to this bug preventing system boot

[Joseph Salisbury (jsalisbury)]

Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

[Andrew Fullam (andrew-fullam)]

UPDATE: I originally installed 13.04 in work and due to the internet being slow I selected not to install updates while installing. However, last night I performed a fresh install at home and selected to install updates while installing and the problem appears to have disappeared. How would you like me to proceed?

[J. Braun (joerg-z)]

Same here, I had the same with 12.10, but only on one machine. Installation of 13.04 is fine, even one reboot works. But the second or third reboot gives Kernel-Panic. I tried noveau and nvidia drivers, nosetmode, acpi off. Attached are pictures of the screen with messages. The first picture had a USB stick still plugged in.

I can boot this machine from another partition, any logs I could save from the failing installation?

[J. Braun (joerg-z)]

The second picture is without USB-Stick

[J. Braun (joerg-z)]

Here is the first picture again with reduced size

[J. Braun (joerg-z)]

I tried the same with "ubuntu-gnome-13.04-desktop-i386" bootet from USB-Stick. I did not even manage to install anything.

My machine is:

MSI MS-7641/880GMA-E35(FX) (MS-7641), BIOS V11.0 06/03/2011
AMD Athlon(tm) II X2 260
4G Ram
Nvidia GTS 450/PCI/SSE2

[Javier Guerra (a-1avier-n)]

Fixed for my case.

the upstart init executable links to libjson.so.0, the libjson0 package installs a libjson.so.0.1 in the 'trusted' directory /lib/x86_64-linux-gnu/ so far, so good. But i had a /usr/local/lib/libjson.so.0.0.1, which is a lower number, but lddconfig creates a libjson.so.0 link in both cases. When the initramfs finished and tried to execute init, it loaded the wrong library and died.

to diagnose the problem, i added "init=/bin/sh" to the grub boot line, so i get to a shell, where doing "ldd /sbin/init" showed the wrong library. removing the /usr/local/lib/libjson.so.0 link was enough to make it load.

I couldn't make ldconfig change the priority, so in the end i removed the extra library.

[J. Braun (joerg-z)]

Does not help me. The Kernel panics before something is started.

[Lars Düsing (lars.duesing)]

Sorry, but should this error not be filed against systemd (init) or ubiquity (installer) instead of kernel?

[John Greth (johng52c)]

I have the same problem with CentOS and Scientific Linux, so Ubiquity isn't the cause.

[penalvch (penalvch)]

J. Braun / John Greth, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

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

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[penalvch (penalvch)]

Andrew Fullam, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172755/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[maxstevens (mho-607)]

I have the same problem with ubuntu 12.04.3(but not on an earlier version of the lts) as well as 13.10. ElementaryOS works fine as does lubuntuLXLE. Linux mint mate 16 and cinnamon don't work--you get this error.

[penalvch (penalvch)]

maxstevens, thank you for your comment. As this issue is resolved for the original reporter, and is closed Invalid, this report does not cover your problem. Despite this, if you have a bug in Ubuntu, please feel free to file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

Timothy J. Niblett, please do not adjust the Status, especially without a comment on why you are changing it, as this report is considered closed as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172755/comments/14 .