[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-bugs] [Bug 780] New: dom0 panic with netbak/netfront as modules on IA64. (again)
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=780 Summary: dom0 panic with netbak/netfront as modules on IA64. (again) Product: Xen Version: unstable Platform: IA64 OS/Version: All Status: NEW Severity: major Priority: P3 Component: Guest-OS AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx ReportedBy: takebe_akio@xxxxxxxxxxxxxx I try to use netback/netfron as modules on ia64. When I enabled network, dom0 panic and the following message is shown. (XEN) *** CALLED SAL_SET_VECTORS 1. IGNORED... (XEN) MCA related initialization done SMP: Allowing 1 CPUs, 0 hotplug CPUs Built 1 zonelists Kernel command line: root=/dev/hda1 ro 3 PID hash table entries: 2048 (order: 11, 65536 bytes) lookup_domain_mpa: d 0xf000000007c0c080 id 3 current 0xf000000007c30000 id 0 (XEN) lookup_domain_mpa: bad mpa 0xffffc019064 (=> 0x20000000) (XEN) Warning: UC to WB for mpaddr=ffffc019064 kernel BUG at drivers/xen/netback/netback.c:630! swapper[0]: bugcheck! 0 [1] Modules linked in: netloop netbk blkbk Pid: 0, CPU 0, comm: swapper psr : 0000001008026010 ifs : 800000000000099a ip : [<a00000020003e870>] Not tainted ip is at net_rx_action+0xd70/0x18e0 [netbk] unat: 0000000000000000 pfs : 800000000000099a rsc : 0000000000000008 rnat: 0000000000000040 bsps: 000000000000000a pr : 000000000005a6a5 ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f csd : 0000000000000000 ssd : 0000000000000000 b0 : a00000020003e870 b6 : a0000001000baa60 b7 : a000000100614b40 f6 : 1003e0000000000000028 f7 : 1003e28f5c28f5c28f5c3 f8 : 1003e00000000000000fa f9 : 1003e0000000032000000 f10 : 1003e000000003b9aca00 f11 : 1003ed6bf94d5e57a42bd r1 : a000000101024d10 r2 : a000000100e492f8 r3 : a000000100e492f8 r8 : 0000000000000034 r9 : f100000000000001 r10 : 0000000000000000 r11 : f100000000004c20 r12 : a000000100c0fb20 r13 : a000000100c08000 r14 : 0000000000004000 r15 : 0000000000000001 r16 : f100000000004c18 r17 : e00000001a1dfde8 r18 : 0000000000000000 r19 : 0000000000000004 r20 : 0000000000000000 r21 : 0000000000000000 r22 : a000000100c08f14 r23 : e00000001a1d8040 r24 : e000000001015208 r25 : e000000001015200 r26 : e0000000010151e0 r27 : 0000000000000073 r28 : a000000100c08030 r29 : e000000001014a88 r30 : 0000000000000000 r31 : 0000000000000000 Call Trace: [<a00000010001af70>] show_stack+0x50/0xa0 sp=a000000100c0f690 bsp=a000000100c09430 [<a00000010001b840>] show_regs+0x820/0x840 sp=a000000100c0f860 bsp=a000000100c093e0 [<a0000001000416d0>] die+0x1d0/0x3e0 sp=a000000100c0f860 bsp=a000000100c09398 [<a000000100041920>] die_if_kernel+0x40/0x60 sp=a000000100c0f880 bsp=a000000100c09368 [<a000000100041b70>] ia64_bad_break+0x230/0x480 sp=a000000100c0f880 bsp=a000000100c09340 [<a000000100068900>] xen_leave_kernel+0x0/0x3b0 sp=a000000100c0f950 bsp=a000000100c09340 [<a00000020003e870>] net_rx_action+0xd70/0x18e0 [netbk] sp=a000000100c0fb20 bsp=a000000100c09270 [<a000000100091a00>] tasklet_action+0x300/0x5a0 sp=a000000100c0fbb0 bsp=a000000100c09238 [<a000000100090550>] __do_softirq+0x1f0/0x380 sp=a000000100c0fbb0 bsp=a000000100c091a8 [<a000000100090820>] do_softirq+0x140/0x2a0 sp=a000000100c0fbb0 bsp=a000000100c09140 [<a000000100090b90>] irq_exit+0x70/0xa0 sp=a000000100c0fbb0 bsp=a000000100c09128 [<a00000010068fd90>] evtchn_do_upcall+0x170/0x240 sp=a000000100c0fbb0 bsp=a000000100c090a0 [<a000000100068900>] xen_leave_kernel+0x0/0x3b0 sp=a000000100c0fbb0 bsp=a000000100c090a0 [<e000000000000810>] 0xe000000000000810 sp=a000000100c0fd80 bsp=a000000100c09050 [<a000000100069070>] xen_pal_call_static+0xd0/0x100 sp=a000000100c0fd80 bsp=a000000100c09030 <0>Kernel panic - not syncing: Aiee, killing interrupt handler! (XEN) Domain 0 crashed: rebooting machine in 5 seconds. I look like this issue is caused by the following patches. http://xenbits.xensource.com/ext/xen-ia64-unstable.hg?cs=c757ebffd500 We can probably resolve this issue. 1. Tristan's xencomm patches is applied. (I test by using xen-ia64-unstable, but these patches have some issue.) 2. revert the below patch. (I have not test yet.) 3. built in these modules. (I have not test yet.) I think the best way is 1. But Tristan's patches still have some issues. Best Regards, Akio Takebe -- Configure bugmail: http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ Xen-bugs mailing list Xen-bugs@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-bugs
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |