On Wed, Jun 06, 2007 at 12:24:37PM +0200, Frans Pop wrote: > Bastian Blank suggested I post this issue here. It has also been reported > in the Debian BTS as http://bugs.debian.org/427089. > > After applying the patch for the "diagnose 224" issue, there are still > some problems when booting Debian Installer on the Hercules emulator. > > My installed system now boots correctly. But a daily build of the > installer still panics, though at a later point and with very little > information. > > There are also in total six exceptions listed in the boot log for both the > installed system and the installer. The first two were also present when > booting 2.6.18 (with small differences), but the others are new: > > HHCCP014I CPU0000: Addressing exception CODE=0005 ILC=6 > CPU0000: R:10000000: Translation exception 0005 > HHCCP014I CPU0000: Specification exception CODE=0006 ILC=4 > HHCCP014I CPU0000: Operation exception CODE=0001 ILC=4 > [...] > HHCCP014I CPU0000: Specification exception CODE=0006 ILC=4 > HHCCP014I CPU0000: Specification exception CODE=0006 ILC=4 > > Attached are logs for both a successful boot of the installed system and > for the installer. For comparison I've also attached a log for a > successful boot of the same system with 2.6.18. The new exceptions you are seeing are from directed yield (diag 9c), hypfs (diag 224), new ipl/reipl code (diag 308) and new etr code (opcode b216). All of them have proper exception handling. That is not what is causing problems. Looks like your init process is doing something wrong, so it terminates too early (or gets terminated). Can't tell from the output you posted. - To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
