possible problems after apt-get upgrade

I did an apt-get upgrade and had some nasty looking stuff appear:

...
Running update-initramfs.
update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood
cryptsetup: WARNING: failed to detect canonical device of /dev/root
cryptsetup: WARNING: could not determine root device from /etc/fstab
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
Examining /etc/kernel/postinst.d.
...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-5-kirkwood
cryptsetup: WARNING: failed to detect canonical device of /dev/root
cryptsetup: WARNING: could not determine root device from /etc/fstab
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
find: `/lib/modules/2.6.32-5-kirkwood/kernel/arch/': No such file or directory
Generating kernel u-boot image... done.
Creating backup of /boot/uImage.
Creating new /boot/uImage.
Generating initrd u-boot image... done.
Creating backup of /boot/uInitrd.
Creating new /boot/uInitrd.

The cryptsetup warnings may not be a big deal since the rootfs isn't encrypted. But I am reluctant to reboot the box until I can have confidence that it will do so successfully. Should I be concerned?

uname -a:
Linux carina 2.6.32-5-kirkwood #1 Wed Oct 20 12:58:44 UTC 2010 armv5tel GNU/Linux

cat /proc/version:
Linux version 2.6.32-5-kirkwood (Debian 2.6.32-26) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Wed Oct 20 12:58:44 UTC 2010

dpkg --list | grep linux-image

The new pkg version should be 2.6.32-35. It should be safe. That's what I'm running. But I don't recall upgrade creating new uImage and uInitrd's, maybe this is new? I've always had to create them manually myself with mkimage after a kernel update so I'm not 100% sure.

If you don't have a serial cable, build one. You will need it sooner or later. At the very least set up netconsole. As long as you can get into the uBoot command line, you can recover from a bad kernel if a backup exists and it looks like it made a backup from the output.

To recover you would do the following from the uBoot command line to recover. (This is taken directly from the default boot command process but run manually so that the last step can be modified to use the backup images):

usb start
run usb_scan
run usb_set_bootargs
mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage-backup; if ext2load usb $usb_device 0x1100000 /boot/uInitrd-backup; then bootm 0x800000 0x1100000; else bootm 0x800000; fi

Otherwise, rename them so that the backups are what will boot, and stay with 2.6.32-26.