Your message dated Tue, 31 Jan 2012 12:25:14 -0800 (PST) with message-id <[email protected]> and subject line The described behavior is by design. Has a work around. has caused the Debian Bug report #655920, regarding Rebooting by kexec leaves the old BOOT_IMAGE in /proc/cmdline to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 655920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655920 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: kexec-tools Version: 1:2.0.2-3 Severity: normal I invoke freshly installed kernel images by rebooting with kexec. $ cat /proc/cmdline root=/dev/sda1 ro BOOT_IMAGE=/boot/vmlinuz-3.1.1-1.1 $ uname -r 3.1.8-2.1 $ ls -l /vmlinuz lrwxrwxrwx 1 root root 25 Jan 14 18:08 /vmlinuz -> boot/vmlinuz-3.1.8-2.1 I think 3.1.1-1.1 got there a few weeks ago, when I actually powered down the machine, and afterwards cold boot it. It had that kernel version back then. Is not updating /proc/cmdline expected?
--- End Message ---
--- Begin Message ---Quoting message #10, by the maintainer, to the bug log: Yes, that is correct. /proc/cmdline is what is passed into the kernel by bootloader. You can give the kernel a new command line by using "--append=" option when loading a kexec kernel. This can be done by updating "APPEND=" in /etc/default/kexec. If you do not pass ina new command line option to the newly kexec'd kernel, command line from previous kernel is reused.
--- End Message ---
