Ubuntu

Linux 3.13.0.30-generic fails with Kernel panic not syncing

Asked by Orion

Following an automatic update a couple of weeks ago, Linux 3.13.0.30-generic the computer fails with a Kernel panic not syncing error. (recreated below).

I can use GRUB to load Linux 3.13.0.29-generic and the system will then boot.

How can I force the system to boot to Linux 3.13.0.29-generic?

I am running Ubuntu 14.04 LTS, as the only OS, on a Toshiba Satellite L675D
Processor: AMD Phenom(tm) II N640 Dual-Core Processor × 2
Graphics: Gallium 0.4 on AMD RS880
OS Type: 32 Bit

/init: exec: line 352: run-init: not found
[ 3.315244] Kernel panic not syncing: Attempted to kill init! exitcode=0x00
[ 3.315244]
[ 3.317307] CPU: 1 PID: 1 Comm: init Not tainted 3.13.0-30-generic #55-Ubuntu
1 Hardware name: TOSHIBA Satellite L675D/NALAE, BIOS 1.7
[ 3.317307] 00000000 00000000 f30e1f28 c1933e00 f68ca000 f30e1f8c c164a82c c182ba58
[ 3.317307] c1aa9c80 f30e1f28 c1933e00 f68ca000 f30a8000 f30e1f8c c105911f c182bd7c
[ 3.317307] 00000200 00000014 b76e7150 00000001 00000001 00000002 f30e1f88 c117929c
[ 3.317307] Call Trace:
[ 3.317307] [<c164f6f3>] dump_stack+0x41/0x52
[ 3.317307] [<c164182c>] panic+0x87/0x8f0
[ 3.317307] [<c105911f>] do_exit+0x8ef/0x1b0
[ 3.317307] [<c117929c>] ? vfs_write+0x13c/0x1b0
[ 3.317307] [<c1059194.] do_group_exit+0x34/0xa0
[ 3.317307] [<c1059216>] Sys_exit_group+0x34/0xa0
[ 3.317307] [<c165d9cd>] sysenter_do_call*0x12/0x28

I manually shutdown and get to the Ubuntu startup options windo and choose Linux 3.13.0-29 to start up the computer.

How can I uninstall 3.13.0-30 or correct the problem?

I am running only Ubuntu on a Toshiba Satellite
Processor: AMD Phenom(tm) II N640 Dual-Core Processor × 2
Graphics: Gallium 0.4 on AMD RS880
OS Type: 32 Bit

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Orion
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

What is the output of:

dpkg -l | grep linux-image

Thanks

Revision history for this message
Orion (orion-j-dix) said : 		#2

 dpkg -l | grep linux-image
rc linux-image-3.11.0-18-generic 3.11.0-18.32 i386 Linux kernel image for version 3.11.0 on 32 bit x86 SMP
ii linux-image-3.11.0-19-generic 3.11.0-19.33 i386 Linux kernel image for version 3.11.0 on 32 bit x86 SMP
rc linux-image-3.13.0-24-generic 3.13.0-24.47 i386 Linux kernel image for version 3.13.0 on 32 bit x86 SMP
ii linux-image-3.13.0-27-generic 3.13.0-27.50 i386 Linux kernel image for version 3.13.0 on 32 bit x86 SMP
ii linux-image-3.13.0-29-generic 3.13.0-29.53 i386 Linux kernel image for version 3.13.0 on 32 bit x86 SMP
ii linux-image-3.13.0-30-generic 3.13.0-30.55 i386 Linux kernel image for version 3.13.0 on 32 bit x86 SMP
rc linux-image-3.5.0-17-generic 3.5.0-17.28 i386 Linux kernel image for version 3.5.0 on 32 bit x86 SMP
ii linux-image-3.5.0-47-generic 3.5.0-47.71 i386 Linux kernel image for version 3.5.0 on 32 bit x86 SMP
rc linux-image-extra-3.11.0-18-generic 3.11.0-18.32 i386 Linux kernel extra modules for version 3.11.0 on 32 bit x86 SMP
ii linux-image-extra-3.11.0-19-generic 3.11.0-19.33 i386 Linux kernel extra modules for version 3.11.0 on 32 bit x86 SMP
rc linux-image-extra-3.13.0-24-generic 3.13.0-24.47 i386 Linux kernel extra modules for version 3.13.0 on 32 bit x86 SMP
ii linux-image-extra-3.13.0-27-generic 3.13.0-27.50 i386 Linux kernel extra modules for version 3.13.0 on 32 bit x86 SMP
ii linux-image-extra-3.13.0-29-generic 3.13.0-29.53 i386 Linux kernel extra modules for version 3.13.0 on 32 bit x86 SMP
ii linux-image-extra-3.13.0-30-generic 3.13.0-30.55 i386 Linux kernel extra modules for version 3.13.0 on 32 bit x86 SMP
rc linux-image-extra-3.5.0-17-generic 3.5.0-17.28 i386 Linux kernel image for version 3.5.0 on 32 bit x86 SMP
ii linux-image-extra-3.5.0-47-generic 3.5.0-47.71 i386 Linux kernel image for version 3.5.0 on 32 bit x86 SMP
ii linux-image-generic 3.13.0.30.36 i386 Generic Linux kernel image

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Run these 4 commands:

sudo dpkg -P linux-image-3.11.0-18-generic linux-image-3.13.0-24-generic linux-image-3.5.0-17-generic

sudo dpkg -P linux-image-extra-3.11.0-18-generic linux-image-extra-3.13.0-24-generic linux-image-extra-3.5.0-17-generic

sudo apt-get --purge remove linux-image-3.11.0-19-generic linux-image-3.13.0-27-generic linux-image-3.5.0-47-generic

sudo apt-get --purge remove linux-image-extra-3.11.0-19-generic linux-image-extra-3.13.0-27-generic linux-image-extra-3.5.0-47-generic

You will have the 3.13.0-29 and 3.13.0-30 kernel remaining which should clear up space and may help

Revision history for this message
Orion (orion-j-dix) said : 		#4

No luck, still having to manually force a shutdown and restart. I tried using both Linux 3.13.0.30-generic and the Linux 3.13.0.30-recovery options. I can get the machine to run only if I select Linux 3.13.0.29-generic.

Is there a means to trap or log the startup error?

This seems to be a corruption in the Linux 3.13.0.30-generic startup.

Revision history for this message
Orion (orion-j-dix) said : 		#5

Let me try a different tack.

I need to edit GRUB so that the PC does not try to load Linux 3.13.0.30-generic but instead uses Linux 3.13.0.29-generic.

When attempting to start using Linux 3.13.0.30-generic, I get the following error screen and have to choose Linux 3.13.0.29-generic to boot.

/init: exec: line 352: run-init: not found
[ 3.315244] Kernel panic not syncing: Attempted to kill init! exitcode=0x00
[ 3.315244]
[ 3.317307] CPU: 1 PID: 1 Comm: init Not tainted 3.13.0-30-generic #55-Ubuntu
1 Hardware name: TOSHIBA Satellite L675D/NALAE, BIOS 1.7
[ 3.317307] 00000000 00000000 f30e1f28 c1933e00 f68ca000 f30e1f8c c164a82c c182ba58
[ 3.317307] c1aa9c80 f30e1f28 c1933e00 f68ca000 f30a8000 f30e1f8c c105911f c182bd7c
[ 3.317307] 00000200 00000014 b76e7150 00000001 00000001 00000002 f30e1f88 c117929c
[ 3.317307] Call Trace:
[ 3.317307] [<c164f6f3>] dump_stack+0x41/0x52
[ 3.317307] [<c164182c>] panic+0x87/0x8f0
[ 3.317307] [<c105911f>] do_exit+0x8ef/0x1b0
[ 3.317307] [<c117929c>] ? vfs_write+0x13c/0x1b0
[ 3.317307] [<c1059194.] do_group_exit+0x34/0xa0
[ 3.317307] [<c1059216>] Sys_exit_group+0x34/0xa0
[ 3.317307] [<c165d9cd>] sysenter_do_call*0x12/0x28

Revision history for this message
Orion (orion-j-dix) said : 		#6

You clearly screwed something up that is most easily resolved by backing up your files and reinstalling the system.