[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
--- Comment From helle...@us.ibm.com 2015-03-11 17:57 EDT--- (In reply to comment #15) > Tested with Ubuntu 15.04 daily build 20150311 and problem is fixed now Thanks, Krishnaja (and Sowmya)! (and Canonical ;- ) Closing. ** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1504 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: Fix Released Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
This bug was fixed in the package kexec-tools - 1:2.0.7-5ubuntu2 --- kexec-tools (1:2.0.7-5ubuntu2) vivid; urgency=medium * Adjust kexec-tools for systems that use vmlinux. (LP: #1416515) -- Chris J ArgesFri, 30 Jan 2015 14:31:10 -0600 ** Changed in: kexec-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: Fix Released Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Branch linked: lp:ubuntu/vivid-proposed/kexec-tools -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
The following patch works for me, and I tested on a ppc64el system. I'll upload into vivid, soon. Should this be fixed for Trusty/Utopic as well? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Patch added: "lp1416515-vivid.debdiff" https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+attachment/4308972/+files/lp1416515-vivid.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Changed in: kexec-tools (Ubuntu) Assignee: (unassigned) => Chris J Arges (arges) ** No longer affects: linux (Ubuntu) ** Changed in: kexec-tools (Ubuntu) Status: New => In Progress ** Changed in: kexec-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Uns
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Also affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in kexec-tools package in Ubuntu: In Progress Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1416515] Re: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled
** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1416515 Title: ISST-LTE:Ubuntu 15.04: "Cannot open `/boot/vmlinuz'" error message on reboot after kdump is enabled Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sowmya G. Parvathi - 2015-01-29 12:43:30 == I have a lpar installed with ubuntu 15.04.I enabled kdump and on reboot getting error message "Cannot open `/boot/vmlinuz`". Steps to recreate: 1. Install ubuntu 15.04 (netboot) 2. sudo passwd root 3. apt-get update, apt-get install openssh-server, apt-get nfs-common 4. service ssh restart 5. apt-get install linux-crashdump: ??? Configuring kexec-tools ?? ? ? ? If you choose this option, a system reboot will trigger a restart into a ? ? kernel loaded by kexec instead of going through the full system boot ? ? loader process. ? ? ? ? Should kexec-tools handle reboots?? ? ? ? ? ? ? ? Selected "Yes" 6. vi /etc/default/grub.d/kexec-tools.cfg (set crashkernel=1024M) 7. update-grub 8. reboot .wait-for-state stop/waiting * Starting userspace bootsplash utility [ OK ] Cannot open `/boot/vmlinuz': No such file or directory * Loading new kernel image into memory... [fail] * Stopping uuidd generator uuidd[ OK ] * Asking all remaining processes to terminate...[ OK ] * All processes ended within 1 seconds... [ OK ] * Stopping NSM status monitor [ OK ] rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w" * Stopping RPC portmapper replacement [ OK ] * Stopping D-Bus system message bus [ OK ] * Stopping NFSv4 id <-> name mapper [ OK ] * Stopping configure virtual network devices[ OK ] * Stopping configure network device security[ OK ] * Deactivating swap... [ OK ] * Will now restart [ 20.328664] reboot: Restarting system lpar will be up, but i am not sure of this error. uname -a Linux pole2lp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux Contact Info: sowpa...@in.ibm.com == Comment: #2 - David Heller - 2015-01-29 14:19:43 == On ppc, it should be looking for a file "vmlinux", not "vmlinuz". The former is the filename on the ppc distributions, the latter on amd64. Can you try editing the grub.cfg to see if that fixes it? if so, it's possible that whichever package modified the grub.cfg here, cannot handle the ppc case and need to be patched == Comment: #3 - Sowmya G. Parvathi - 2015-01-30 05:50:32 == I think the issue is with /etc/default/kexec file and not grub.cfg. kexec: # Defaults for kexec initscript # sourced by /etc/init.d/kexec and /etc/init.d/kexec-load # Load a kexec kernel (true/false) LOAD_KEXEC=true # Kernel and initrd image KERNEL_IMAGE="/boot/vmlinuz" INITRD="/boot/initrd.img" # If empty, use current /proc/cmdline APPEND="" # Load the default kernel from grub config (true/false) USE_GRUB_CONFIG=false Here KERNEL_IMAGE="/boot/vmlinuz" instead of "/boot/vmlinux". I changed vmlinuz to vmlinux, did a reboot and issue did not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
