I just tried re-building the initial RAM file system for the 2.6.26-1-s390 kernel image, rerunning zipl, and rebooting. It came up fine. It does not appear to be a problem with the build process for the initial RAM file system. If it is, it is a build problem which is specific to the new kernel image for some reason.
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! dann frazier
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! dann frazier
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL
- Bug#523942: linux-image-2.6.26-2-s390 will not boot! STEPHEN POWELL