On Thu, 18 Jun 2009 18:00:22 +0530 Sachin Sant <sachinp@xxxxxxxxxx> wrote: > Today's Next tree failed to boot on a s390x box. > > 00: Booting default (autotest)... > 00000000002baf7a: a74b0038 aghi %r4,56 > Call Trace: > (<00000000004afc36>¨ console_init+0x36/0x50) > <0000000000498b86>¨ start_kernel+0x53e/0x5ec > <0000000000012020>¨ _ehead+0x20/0x80 > Last Breaking-Event-Address: > <00000000002bafd4>¨ init_section_page_cgroup+0xfc/0x10c > > --- end trace 31fd0ba7d8756001 ¨--- > Kernel panic - not syncing: Attempted to kill the idle task! > CPU: 0 Tainted: G D 2.6.30-autotest-next-20090618 #1 > Process swapper (pid: 0, task: 0000000000445700, ksp: 0000000000498000) > 0000000000000005 0000000000497b10 0000000000000002 0000000000000000 > 0000000000497bb0 0000000000497b28 0000000000497b28 000000000004a01e > 00000000002c4d08 0000000000000000 0000000000000000 000000000000000b > 0000000000000008 0000000000000000 0000000000497b10 0000000000497b88 > 00000000002c4c90 00000000000163aa 0000000000497b10 0000000000497b60 > Call Trace: > (<000000000001630c>¨ show_trace+0xdc/0xec) > <0000000000048f10>¨ panic+0x84/0x1c0 > <000000000004ce3c>¨ do_exit+0x74/0x6f0 > <0000000000016862>¨ die+0x152/0x154 > <000000000001298c>¨ do_no_context+0xa0/0xac > <00000000000131aa>¨ do_protection_exception+0x252/0x260 > <0000000000025fa8>¨ sysc_return+0x0/0x8 > <00000000002baf64>¨ init_section_page_cgroup+0x8c/0x10c > (<00000000004afc36>¨ console_init+0x36/0x50) > <0000000000498b86>¨ start_kernel+0x53e/0x5ec > <0000000000012020>¨ _ehead+0x20/0x80 > 00: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 > 00020E76 > > I haven't played with a s390 box before so not sure if this > is a new problem or me not compiling the kernel properly. > Let me know what other information is required. Boots without problems for me. What is you .config ? -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
