On Thu, 2012-05-17 at 21:26 +0200, Helge Deller wrote: > On 05/15/2012 10:48 PM, John David Anglin wrote: > > We need to debug why your B160L hangs. Can you kill whatever hangs > > from the console? Sometimes the application is still in the foreground. > > Ok, the B160L problem is gone now. > I found the reason for this bug between the chair and the monitor :-) > (it was my fault - sorry .... ) > > But I think we still have a problem. > I'm using 3.4.0-rc7, have pulled all fixes from James "fixes" branch, > and Dave's "vmlinux.lds" patch. > > The 32bit machines (715/64 and B160L) boot nicely into userspace. > The 64bit machine (C3000) crashes directly when switching to userspace. > > Do we still have another problem somewhere? > Or is it introduced because of the vmlinux.lds patch? > (Reminder: without the vmlinux.lds patch the C3000 hangs directly at > bootup after printing memory information...) I'm not seeing it on my rp3410 ... I'm going to have to find the J box (which I think is closest to your C3000 ... that's an astro system) and boot it. > Helge > > VFS: Mounted root (ext3 filesystem) readonly on device 8:3. > Freeing unused kernel memory: 316k freed > Backtrace: > [<10119560>] clear_user_page_asm+0x44/0x6c > [<101195dc>] clear_user_page+0x54/0x6c > [<101bbaa8>] handle_pte_fault+0x5dc/0x7a8 > [<101bbd3c>] handle_mm_fault+0xc8/0x120 > [<101bbffc>] __get_user_pages+0x160/0x3c4 > [<101bc348>] get_user_pages+0x50/0x60 > [<101e169c>] get_arg_page+0x64/0xe8 > [<101e182c>] copy_strings+0x10c/0x248 > [<101e1990>] copy_strings_kernel+0x28/0x44 > [<101e328c>] do_execve+0x2a0/0x36c > [<10120424>] sys_execve+0x44/0x7c > [<10104084>] __execve+0x20/0x34 > [<10133b9c>] vprintk+0x1d8/0x4f4 > [<10133ee8>] printk+0x30/0x40 > [<10118550>] free_initmem+0x154/0x184 > [<10117cbc>] init_post+0xa0/0xd4 > > > Kernel Fault: Code=26 regs=8fc30940 (Addr=0f2ff000) > > YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI > PSW: 00000000000001101111111100001110 Not tainted > r00-03 0006ff0e 00000040 10119560 8fc308c0 > r04-07 106e5820 107d2000 0000000f 10768020 > r08-11 ffeffff1 8fd00ffc 8f49ce40 00000001 > r12-15 00000000 00000017 00000001 00000000 > r16-19 00004400 00000020 00000000 ffffffff > r20-23 00000000 00000000 00000001 00000040 > r24-27 1090aa40 ffeffff1 0000fa40 106e2020 > r28-31 0f2ff000 0007d882 8fc30940 0007d024 > sr00-03 00000000 00000000 00000000 00000000 > sr04-07 00000000 00000000 00000000 00000000 > > IASQ: 00000000 00000000 IAOQ: 10100eec 10100ef0 > IIR: 0f801280 ISR: 00000000 IOR: 0f2ff000 > CPU: 0 CR30: 8fc30000 CR31: de9345e0 > ORIG_R28: 8f812728 > IAOQ[0]: __clear_user_page_asm+0x20/0x70 > IAOQ[1]: __clear_user_page_asm+0x24/0x70 > RP(r2): clear_user_page_asm+0x44/0x6c > Backtrace: > [<10119560>] clear_user_page_asm+0x44/0x6c > [<101195dc>] clear_user_page+0x54/0x6c > [<101bbaa8>] handle_pte_fault+0x5dc/0x7a8 > [<101bbd3c>] handle_mm_fault+0xc8/0x120 > [<101bbffc>] __get_user_pages+0x160/0x3c4 > [<101bc348>] get_user_pages+0x50/0x60 > [<101e169c>] get_arg_page+0x64/0xe8 > [<101e182c>] copy_strings+0x10c/0x248 > [<101e1990>] copy_strings_kernel+0x28/0x44 > [<101e328c>] do_execve+0x2a0/0x36c > [<10120424>] sys_execve+0x44/0x7c > [<10104084>] __execve+0x20/0x34 > [<10133b9c>] vprintk+0x1d8/0x4f4 > [<10133ee8>] printk+0x30/0x40 > [<10118550>] free_initmem+0x154/0x184 > [<10117cbc>] init_post+0xa0/0xd4 > > Kernel panic - not syncing: Kernel Fault What this says is something went wrong in the tmpalias space because it fell through to the fault path. How much memory does this system have (and what's the layout map)? It's 64 bit but you're booting it with a 32 bit kernel ... I'm wondering if there's no space for tmpalias. James -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
