Package: linux-image-3.12-0.bpo.1-kirkwood Version: 3.12.6-2~bpo70+1 Severity: important Dear Maintainer, I run Wheezy on a SheevaPlug. In this system, I added wheezy-backports some time ago, so far so good. I recently upgraded kernel to linux-image-3.12-0.bpo.1-kirkwood. Once I rebooted I found out that system was unbootable. This is what I could see from serial console: --- Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x00000831). Available machine support: ID (hex) NAME 0000089b LaCie d2 Network v2 0000089e LaCie 5Big Network v2 0000089c LaCie 2Big Network v2 00000b44 Marvell OpenRD Ultimate Board 00000939 Marvell OpenRD Client Board 00000915 Marvell OpenRD Base Board 00000691 Marvell RD-88F6192-NAS Development Board 00000692 Marvell RD-88F6281 Reference Board 00000b1e HP t5325 Thin Client 0000085b QNAP TS-119/TS-219 000009c6 QNAP TS-41x ffffffff Marvell Kirkwood (Flattened Device Tree) Please check your kernel config and/or bootloader. --- flash-kernel pacakage is installed and configured so on each kernel upgrade the boot images (kernel and initrd) are upgraded and use on next boot. I had to change u-boot boot parameters so system boots with previous kernel, by then it was 3.11, installed by package linux-image-3.11-0.bpo.2-kirkwood I've surfed BTS and I think this problem is closely related to [0]. This one is solved, but so far it is not for wheezy-backports, hence the booting problem. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731345 Unfortunately, fixed flash-kernel package version is not available for wheezy-backports. Taken all this into consideration, I think linux-image-3.12-0.bpo.1-kirkwood should depend on the proper flash-kernel version (>=3.12) and/or getting fixed flash-kernel package uploaded to wheezy-backports. I'm sending this bug report against linux-image-3.12-0.bpo.1-kirkwood because I think that this package should or could perform pertinent checks in order to avoid boot failures like this. albeit the right fix finally implies uploading fixed flash-kernel version to wheezy-backports. Well, this is my view, but I may well be wrong. What do you think? Pd.: Feel free to contact me for any relevant information. Thanks and regards, -- System Information: Debian Release: 7.3 APT prefers stable APT policy: (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 3.11-0.bpo.2-kirkwood Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Attachment:
signature.asc
Description: This is a digitally signed message part.