Thanks Hao, I'm able to reproduce this.
The only reason we can actually use anything is because networking is
S 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
[c06ab530] c02dbf7c .network_tx_buf_gc+0x11c/0x2f0
(unreliable)
[c06ab610] c02deed4 .netif_int+0x54/0x120
[c06ab6b0] c008b824 .handle_IRQ_event+0x84/0x100
[c06ab750] c008ba70 .__do_IRQ+0x1d0/0x2b0
[c06ab810] c02c777c .evtchn_do_upcall+0x11c/0x170
[c06ab8d0] c00445a0 .xen_get_irq+0x10/0x30
[c06ab950] c000bf10 .do_IRQ+0x70/0x100
[c06ab9d0] c00041ec hardware_interrupt_entry+0xc/0x10
--- Exception: 501 (Hardware Interrupt) at c003bcc0
.plpar_hcall_norets+0x10/0x1c
[link register ] c0045534 .HYPERVISOR_sched_op+0x124/0x150
[c06abcc0] c05a06e0 (unreliable)
[c06abd70] c004609c .xen_power_save+0x7c/0xa0
[c06abdf0] c0012060 .cpu_idle+0xe0/0x150
[c06abe70] c00095dc .rest_init+0x3c/0x60
[c06abef0] c052d958 .start_kernel+0x278/0x2e0
[c06abf90] c00084fc .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: C02DBFB0 LR: C02DBF8C CTR: C02DEE80
REGS: c06ab2b0 TRAP: 0300 Not tainted (2.6.17-Xen)
MSR: 80001432 ME,IR,DR CR: 2882 XER: 6005
DAR: 00C2, DSISR: 4000
TASK = c05748a0[0] 'swapper' THREAD: c06a8000 CPU: 0
GPR00: C06AB530 C06A9718
C0003FFB9678
GPR04: C071B5D8 C06AB510
GPR08: 0003 D8008000
00C2
GPR12: 80009032 C0575100
GPR16:
C0003FFB8000
GPR20: C0568100 C0003FFB8670 0004
004C
GPR24: 0048 0020 0002
004B
GPR28: 0004 C0003FFB9680 C05FB020
C0003FFB8500
NIP [C02DBFB0] .network_tx_buf_gc+0x150/0x2f0
LR [C02DBF8C] .network_tx_buf_gc+0x12c/0x2f0
Call Trace:
[C06AB530] [C02DBF7C] .network_tx_buf_gc+0x11c/0x2f0
(unreliable)
[C06AB610] [C02DEED4] .netif_int+0x54/0x120
[C06AB6B0] [C008B824] .handle_IRQ_event+0x84/0x100
[C06AB750] [C008BA70] .__do_IRQ+0x1d0/0x2b0
[C06AB810] [C02C777C] .evtchn_do_upcall+0x11c/0x170
[C06AB8D0] [C00445A0] .xen_get_irq+0x10/0x30
[C06AB950] [C000BF10] .do_IRQ+0x70/0x100
[C06AB9D0] [C00041EC] hardware_interrupt_entry+0xc/
0x10
--- Exception: 501 at .plpar_hcall_norets+0x10/0x1c
LR = .HYPERVISOR_sched_op+0x124/0x150
[C06ABCC0] [C05A06E0] 0xc05a06e0 (unreliable)
[C06ABD70] [C004609C] .xen_power_save+0x7c/0xa0
[C06ABDF0] [C0012060] .cpu_idle+0xe0/0x150
[C06ABE70] [C00095DC] .rest_init+0x3c/0x60
[C06ABEF0] [C052D958] .start_kernel+0x278/0x2e0
[C06ABF90] [C00084FC] .start_here_common+0x50/0x54
Instruction dump:
809d000c 387f1178 4bfec5c9 6000 3800 397a00c0 901d000c
6000
e93f0170 7d35c92a fb9f0170 7c2004ac 7c005828 3000 7c00592d
40c2fff4
0Kernel panic - not syncing: Fatal exception in interrupt
0Rebooting in 180 seconds..
Hao Yu
Jimi Xenidis
[EMAIL PROTECTED]
.com
To
Hao Yu/Watson/[EMAIL PROTECTED]
11/01/2006
12:01 cc
PMxen-ppc-
[EMAIL PROTECTED]
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
