On Mon, Jun 29, 2009 at 03:14:40PM +0530, Sachin Sant wrote: > I still have problems booting next with SLQB on a s390 box. > > Write protected kernel read-only data: 0x12000 - 0x446fff > Experimental hierarchical RCU implementation. > Experimental hierarchical RCU init done. > console ÝttyS0¨ enabled > Unable to handle kernel pointer dereference at virtual kernel address (null) > Oops: 0004 #1¨ SMP > Modules linked in: > CPU: 0 Not tainted 2.6.31-rc1-autotest-next-20090629 #1 > Process swapper (pid: 0, task: 0000000000447700, ksp: 0000000000498000) > Krnl PSW : 0700200180000000 00000000002be00c (init_section_page_cgroup+0x8c/0x10 > c) > R:0 T:1 IO:1 EX:1 Key:0 M:0 W:0 P:0 AS:0 CC:2 PM:0 EA:3 > Krnl GPRS: 0000000000000000 0000000000000028 0000000000000010 0000000000000010 > 000003e040000000 0000000000010000 0000000000498a28 0000000000000000 > 00000000004cc000 00000000004bb408 00000000004cc010 0000000080808000 > 0000000000280000 00000000002d1cf0 00000000004aa69e 0000000000497ed0 > Krnl Code: 00000000002be000: a7c90000 lghi %r12,0 > 00000000002be004: a7f40031 brc 15,2be066 > 00000000002be008: 41102018 la %r1,24(%r2) > >00000000002be00c: e34020100024 stg %r4,16(%r2) > 00000000002be012: a7a90000 lghi %r10,0 > 00000000002be01c: e3a020000024 stg %r10,0(%r2) > 00000000002be022: a74b0038 aghi %r4,56 > Call Trace: > (<00000000004b0bbe>¨ console_init+0x36/0x50) > <000000000049897a>¨ start_kernel+0x312/0x3c0 > <0000000000012020>¨ _ehead+0x20/0x80 > Last Breaking-Event-Address: > <00000000002be07c>¨ 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.31-rc1-autotest-next-20090629 #1 > Process swapper (pid: 0, task: 0000000000447700, ksp: 0000000000498000) > 0000000000000005 0000000000497b20 0000000000000002 0000000000000000 > 0000000000497bc0 0000000000497b38 0000000000497b38 0000000000049fc2 > 00000000002c7cf0 0000000000000000 0000000000000000 000000000000000b > 0000000000000008 0000000000000000 0000000000497b20 0000000000497b98 > 00000000002c7c78 00000000000163aa 0000000000497b20 0000000000497b70 > Call Trace: > (<000000000001630c>¨ show_trace+0xdc/0xec) > <0000000000048eb0>¨ panic+0x84/0x1c0 > <000000000004ce70>¨ do_exit+0x74/0x6f0 > <0000000000016862>¨ die+0x152/0x154 > <000000000001298c>¨ do_no_context+0xa0/0xac > <00000000000131aa>¨ do_protection_exception+0x252/0x260 > <0000000000025f7c>¨ sysc_return+0x0/0x8 > <00000000002be00c>¨ init_section_page_cgroup+0x8c/0x10c > (<00000000004b0bbe>¨ console_init+0x36/0x50) > <000000000049897a>¨ start_kernel+0x312/0x3c0 > <0000000000012020>¨ _ehead+0x20/0x80 > 01: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 00020E3E > > With SLUB machine boots fine. Should i be testing this(SLQB/s390) > combination ? No, just stay with SLUB/SLAB for the time being. Maybe the backtrace looks familiar to Nick? -- 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
