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 15:36:36 -0500
Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Nov 2006 13:46:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <B2F45F46-BA2B-4D97-9B3F-3E91244C4F16@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,

It's great you can reproduce the problem. I do not recall that I have seen
those lines. I need to check it in 30 mins. Right now, the environment is
under rebuilding.

Thanks,
Hao



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




Thanks Hao, I'm able to reproduce this.
The only reason we can actually use anything is because networking is
Soooo forgiving.
I think I have the solution to this, it will require some re-writing
which should get done by the end of the week.

BTW: you should have gotten lines like:
   (XEN) (file=grant_table.c, line=356) Bad handle (2).
   (XEN) (file=grant_table.c, line=356) Bad handle (13).
   (XEN) (file=grant_table.c, line=356) Bad handle (6).
   gnt_unmap: -2
   (XEN) (file=grant_table.c, line=356) Bad handle (16).
   gnt_unmap: -2
   (XEN) (file=grant_table.c, line=356) Bad handle (2).

out of the machine console, do you see those as well?

Thanks.
-JX
On Nov 1, 2006, at 12:18 PM, Hao Yu wrote:

> Hi, Here is backtrace message from the 0.mon> console
>
> 0:mon> t
> [c0000000006ab530] c0000000002dbf7c .network_tx_buf_gc+0x11c/0x2f0
> (unreliable)
> [c0000000006ab610] c0000000002deed4 .netif_int+0x54/0x120
> [c0000000006ab6b0] c00000000008b824 .handle_IRQ_event+0x84/0x100
> [c0000000006ab750] c00000000008ba70 .__do_IRQ+0x1d0/0x2b0
> [c0000000006ab810] c0000000002c777c .evtchn_do_upcall+0x11c/0x170
> [c0000000006ab8d0] c0000000000445a0 .xen_get_irq+0x10/0x30
> [c0000000006ab950] c00000000000bf10 .do_IRQ+0x70/0x100
> [c0000000006ab9d0] c0000000000041ec hardware_interrupt_entry+0xc/0x10
> --- Exception: 501 (Hardware Interrupt) at c00000000003bcc0
> .plpar_hcall_norets+0x10/0x1c
> [link register   ] c000000000045534 .HYPERVISOR_sched_op+0x124/0x150
> [c0000000006abcc0] c0000000005a06e0 (unreliable)
> [c0000000006abd70] c00000000004609c .xen_power_save+0x7c/0xa0
> [c0000000006abdf0] c000000000012060 .cpu_idle+0xe0/0x150
> [c0000000006abe70] c0000000000095dc .rest_init+0x3c/0x60
> [c0000000006abef0] c00000000052d958 .start_kernel+0x278/0x2e0
> [c0000000006abf90] c0000000000084fc .start_here_common+0x50/0x54
> 0:mon> X
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=32
> Modules linked in:
> NIP: C0000000002DBFB0 LR: C0000000002DBF8C CTR: C0000000002DEE80
> REGS: c0000000006ab2b0 TRAP: 0300   Not tainted  (2.6.17-Xen)
> MSR: 8000000000001432 <ME,IR,DR>  CR: 28555582  XER: 60055555
> DAR: 00000000000000C2, DSISR: 0000000040000000
> TASK = c0000000005748a0[0] 'swapper' THREAD: c0000000006a8000 CPU: 0
> GPR00: 0000000000000000 C0000000006AB530 C0000000006A9718
> C00000003FFB9678
> GPR04: 0000000000000000 C00000000071B5D8 C0000000006AB510
> 0000000000000000
> GPR08: 0000000000000000 0000000000000003 D000080080000000
> 00000000000000C2
> GPR12: 8000000000009032 C000000000575100 5555555555555555
> 5555555555555555
> GPR16: 5555555555555555 5555555555555555 5555555555555555
> C00000003FFB8000
> GPR20: C000000000568100 C00000003FFB8670 0000000000000004
> 000000000000004C
> GPR24: 0000000000000048 0000000000000020 0000000000000002
> 000000000000004B
> GPR28: 0000000000000004 C00000003FFB9680 C0000000005FB020
> C00000003FFB8500
> NIP [C0000000002DBFB0] .network_tx_buf_gc+0x150/0x2f0
> LR [C0000000002DBF8C] .network_tx_buf_gc+0x12c/0x2f0
> Call Trace:
> [C0000000006AB530] [C0000000002DBF7C] .network_tx_buf_gc+0x11c/0x2f0
> (unreliable)
> [C0000000006AB610] [C0000000002DEED4] .netif_int+0x54/0x120
> [C0000000006AB6B0] [C00000000008B824] .handle_IRQ_event+0x84/0x100
> [C0000000006AB750] [C00000000008BA70] .__do_IRQ+0x1d0/0x2b0
> [C0000000006AB810] [C0000000002C777C] .evtchn_do_upcall+0x11c/0x170
> [C0000000006AB8D0] [C0000000000445A0] .xen_get_irq+0x10/0x30
> [C0000000006AB950] [C00000000000BF10] .do_IRQ+0x70/0x100
> [C0000000006AB9D0] [C0000000000041EC] hardware_interrupt_entry+0xc/
> 0x10
> --- Exception: 501 at .plpar_hcall_norets+0x10/0x1c
>     LR = .HYPERVISOR_sched_op+0x124/0x150
> [C0000000006ABCC0] [C0000000005A06E0] 0xc0000000005a06e0 (unreliable)
> [C0000000006ABD70] [C00000000004609C] .xen_power_save+0x7c/0xa0
> [C0000000006ABDF0] [C000000000012060] .cpu_idle+0xe0/0x150
> [C0000000006ABE70] [C0000000000095DC] .rest_init+0x3c/0x60
> [C0000000006ABEF0] [C00000000052D958] .start_kernel+0x278/0x2e0
> [C0000000006ABF90] [C0000000000084FC] .start_here_common+0x50/0x54
> Instruction dump:
> 809d000c 387f1178 4bfec5c9 60000000 38000000 397a00c0 901d000c
> 60000000
> e93f0170 7d35c92a fb9f0170 7c2004ac <7c005828> 3000ffff 7c00592d
> 40c2fff4
>  <0>Kernel panic - not syncing: Fatal exception in interrupt
>  <0>Rebooting in 180 seconds..
>
> Hao Yu
>
>
>
>
>
>              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




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