WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: FYI: Re: [XenPPC] problem of ssh to domU on js21

To: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Subject: Re: FYI: Re: [XenPPC] problem of ssh to domU on js21
From: Hao Yu <yuh@xxxxxxxxxx>
Date: Wed, 1 Nov 2006 14:08:04 -0500
Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Nov 2006 13:45:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <8C333CED-389F-4424-A8B6-9A19E8669F60@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Jimi,

Just found out the problem is not only about 'ssh'. dom0 breaks when I
tried invoke java in dom0. Here are the console message and backtraces.
Just hope the info can help you on the potentially broken xen you mentioned
when you put out the two patches.

Thanks,
Hao

cso83:/ # cpu 0x0: Vector: 400 (Instruction Access) at [c000000031873090]
    pc: 0000000000000000: .__start+0x4000000000000000/0x8
    lr: c0000000000b5e10: .get_vma_policy+0x60/0xd0
    sp: c000000031873310
   msr: 8000000040009032
  current = 0xc000000032626040
  paca    = 0xc00000000058c100
    pid   = 7287, comm = java
enter ? for help
0:mon>

0:mon> t
[link register   ] c0000000000b5e10 .get_vma_policy+0x60/0xd0
[c000000031873310] d0000000002a0fd8 .cxiTraceExit+0x78/0x98 [mmfslinux]
(unreliable)
[c000000031873390] c0000000000b73f4 .alloc_page_vma+0x34/0x140
[c000000031873430] c0000000000a577c .__handle_mm_fault+0xb5c/0xf90
[c000000031873540] c000000000032868 .do_page_fault+0x558/0x830
[c000000031873720] c0000000000048e0 .handle_page_fault+0x20/0x54
--- Exception: 301 (Data Access) at c000000000037830
.__clear_user+0x14/0x7c
[link register   ] c000000000118b28 .padzero+0x88/0x130
[c000000031873a10] c000000000118b00 .padzero+0x60/0x130 (unreliable)
[c000000031873aa0] c00000000011a40c .load_elf_binary+0x8fc/0x1c70
[c000000031873c30] c0000000000dc4c8 .search_binary_handler+0xe8/0x3f0
[c000000031873ce0] c000000000110870 .compat_do_execve+0x1a0/0x2c0
[c000000031873d90] c000000000017724 .compat_sys_execve+0x74/0x100
[c000000031873e30] c00000000000861c syscall_exit+0x0/0x40
--- Exception: c01 (System Call) at 000000000fe10c68
SP (ffde07f0) is in userspace


0:mon> X
Oops: Kernel access of bad area, sig: 11 [#1]
SMP NR_CPUS=32 NUMA
Modules linked in: mmfs mmfslinux tracedev
NIP: 0000000000000000 LR: C0000000000B5E10 CTR: 0000000000000000
REGS: c000000031873090 TRAP: 0400   Tainted: PF      (2.6.17-Xen)
MSR: 8000000040009032 <EE,ME,IR,DR>  CR: 84224488  XER: 00000000
TASK = c000000032626040[7287] 'java' THREAD: c000000031870000 CPU: 0
GPR00: 0000000000000000 C000000031873310 0000000000000000 C000000075CE59E8
GPR04: 0000000010024316 0000000010024316 C0000000000AFFFC C000000075CE59E8
GPR08: 0000000000000000 D0000000002E5E58 0000000000000000 0000000000000000
GPR12: D0000000002B97E8 C00000000058C100 6DB6DB6DB6DB6DB7 0000000000000000
GPR16: C0000000318734A0 00000000100214E8 0000000000000000 C000000000000000
GPR20: C000000075DB7000 C000000075CE59E8 C0000000756A0998 0000000010024316
GPR24: 0000000010024000 C000000031ADE210 0000000000000120 0000000010024316
GPR28: 00000000000200D2 C000000031AD8120 C0000000005BB350 C000000075CE59E8
NIP [0000000000000000] .__start+0x4000000000000000/0x8
LR [C0000000000B5E10] .get_vma_policy+0x60/0xd0
Call Trace:
[C000000031873310] [D0000000002A0FD8] .cxiTraceExit+0x78/0x98 [mmfslinux]
(unreliable)
[C000000031873390] [C0000000000B73F4] .alloc_page_vma+0x34/0x140
[C000000031873430] [C0000000000A577C] .__handle_mm_fault+0xb5c/0xf90
[C000000031873540] [C000000000032868] .do_page_fault+0x558/0x830
[C000000031873720] [C0000000000048E0] .handle_page_fault+0x20/0x54
--- Exception: 301 at .__clear_user+0x14/0x7c
    LR = .padzero+0x88/0x130
[C000000031873A10] [C000000000118B00] .padzero+0x60/0x130 (unreliable)
[C000000031873AA0] [C00000000011A40C] .load_elf_binary+0x8fc/0x1c70
[C000000031873C30] [C0000000000DC4C8] .search_binary_handler+0xe8/0x3f0
[C000000031873CE0] [C000000000110870] .compat_do_execve+0x1a0/0x2c0
[C000000031873D90] [C000000000017724] .compat_sys_execve+0x74/0x100
[C000000031873E30] [C00000000000861C] syscall_exit+0x0/0x40
Instruction dump:
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
 <3>Badness in __mutex_unlock_slowpath at
/root/xen-maria-latest/linux/linux-xen-ppc/kernel/mutex.c:209
Call Trace:
[C000000031B7F240] [C00000000000F864] .show_stack+0x54/0x1f0 (unreliable)
[C000000031B7F2F0] [C0000000000278E8] .program_check_exception+0x508/0x6a0
[C000000031B7F3D0] [C0000000000044EC] program_check_common+0xec/0x100
--- Exception: 700 at .__mutex_unlock_slowpath+0x21c/0x230
    LR = .gpfs_fill_super+0x768/0x818 [mmfslinux]
[C000000031B7F6C0] [C000000031B7F760] 0xc000000031b7f760 (unreliable)
[C000000031B7F760] [D0000000002AD5B4] .gpfs_fill_super+0x768/0x818
[mmfslinux]
[C000000031B7F870] [C0000000000D6F68] .get_sb_nodev+0x88/0x150
[C000000031B7F910] [D0000000002AD6BC] .gpfs_get_sb+0x58/0xd0 [mmfslinux]
[C000000031B7F9A0] [C0000000000D66EC] .vfs_kern_mount+0x7c/0x170
[C000000031B7FA40] [C0000000000D683C] .do_kern_mount+0x4c/0x80
[C000000031B7FAE0] [C0000000000F795C] .do_mount+0x31c/0x8f0
[C000000031B7FD70] [C000000000110A68] .compat_sys_mount+0xd8/0x2b0
[C000000031B7FE30] [C00000000000861C] syscall_exit+0x0/0x40






                                                                           
             Jimi Xenidis                                                  
             <jimix@xxxxxxxxxx                                             
             .com>                                                      To 
                                       Hao Yu/Watson/IBM@IBMUS             
             11/01/2006 12:01                                           cc 
             PM                        xen-ppc-devel@xxxxxxxxxxxxxxxxxxx   
                                                                   Subject 
                                       FYI: Re: [XenPPC] problem of ssh to 
                                       domU on js21                        
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




Thank you Hao for posting the issue to the list!
I'll be posting this highly experimental patch to the list shortly.
-JX

On Nov 1, 2006, at 11:55 AM, Hao Yu wrote:

>
> With Jimi's new patch, the ping works fine, lasting forever (stayed
> for 1.5
> hours). However, I could not stop it using ^C or ^Z .
>
> The problem here is when I try to use ssh, domU crashes with following
> messages
>
> cso232:/ # passwd
> Changing password for root.
> New Password:
> Bad password: too simple
> Reenter New Password:
> Password changed.
> cso232:/ # cpu 0x0: Vector: 300 (Data Access) at [c0000000006ab2b0]
>     pc: c0000000002dbfb0: .network_tx_buf_gc+0x150/0x2f0
>     lr: c0000000002dbf8c: .network_tx_buf_gc+0x12c/0x2f0
>     sp: c0000000006ab530
>    msr: 8000000000001032
>    dar: c2
>  dsisr: 40000000
>   current = 0xc0000000005748a0
>   paca    = 0xc000000000575100
>     pid   = 0, comm = swapper
> enter ? for help
> 0:mon>
>
> Here is the complete message of booting domU and the crash: (See
> attached
> file: p-ssh-domu.txt)
>
> Regards,
> Hao Yu
>
> <p-ssh-domu.txt>
> _______________________________________________
> Xen-ppc-devel mailing list
> Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ppc-devel




_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel