Re: [Xen-ia64-devel] Xen/IPF Unstable CS#18286, dom0 CS#633 StatusReport --- some call trace in dom0

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

Hi. Thank you for testing.

I think the issues was resolved by the patch from Alex Williamson.
The c/s is 624:87413eba04ab in the x86 tree.
This morning I merged the i64 tree with the x86 tree so that this
should disappear.

thanks,

On Mon, Aug 11, 2008 at 09:13:38AM +0800, Zhang, Jingke wrote:
> Hi all,
>     All the test cases can pass with Cset#18286. When I check the 'dmesg', I 
> found the unknown hypercalls was gone.
>     But I met many call trace (39 times) printed out. My dom0 source is 
> Cset#633.
> =============================================
> ACPI: Device [CSFF] status [00000008]: functional but not present; setting 
> present
> ACPI: PCI Root Bridge [CSFF] (0000:ff)
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> BUG: warning at 
> /home/build/nightly/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:28/pci_bus_probe_wrapper()
> 
> Call Trace:
>  [<a00000010001db20>] show_stack+0x40/0xa0
>                                 sp=e00000007f5cfbe0 bsp=e00000007f5c91b0
>  [<a00000010001dbb0>] dump_stack+0x30/0x60
>                                 sp=e00000007f5cfdb0 bsp=e00000007f5c9198
>  [<a0000001006b8a90>] pci_bus_probe_wrapper+0x150/0x180
>                                 sp=e00000007f5cfdb0 bsp=e00000007f5c9170
>  [<a0000001005ffea0>] driver_probe_device+0x100/0x1e0
>                                 sp=e00000007f5cfdc0 bsp=e00000007f5c9138
>  [<a0000001006001a0>] __driver_attach+0xc0/0x160
>                                 sp=e00000007f5cfdc0 bsp=e00000007f5c9108
>  [<a0000001005ff140>] bus_for_each_dev+0x80/0x100
>                                 sp=e00000007f5cfdc0 bsp=e00000007f5c90d0
>  [<a0000001005ffcc0>] driver_attach+0x40/0x60
>                                 sp=e00000007f5cfde0 bsp=e00000007f5c90b0
>  [<a0000001005fe8c0>] bus_add_driver+0xe0/0x2c0
>                                 sp=e00000007f5cfde0 bsp=e00000007f5c9070
>  [<a0000001006006f0>] driver_register+0x170/0x1a0
>                                 sp=e00000007f5cfde0 bsp=e00000007f5c9050
>  [<a00000010050fda0>] __pci_register_driver+0xa0/0x100
>                                 sp=e00000007f5cfde0 bsp=e00000007f5c9028
>  [<a000000100c81e20>] pcistub_init+0x200/0x380
>                                 sp=e00000007f5cfde0 bsp=e00000007f5c8fd0
>  [<a000000100011900>] init+0x320/0x840
>                                 sp=e00000007f5cfe00 bsp=e00000007f5c8f98
>  [<a00000010001bfd0>] kernel_thread_helper+0x30/0x60
>                                 sp=e00000007f5cfe30 bsp=e00000007f5c8f70
>  [<a0000001000110e0>] start_kernel_thread+0x20/0x40
>                                 sp=e00000007f5cfe30 bsp=e00000007f5c8f70
> BUG: warning at 
> /home/build/nightly/linux-2.6.18-xen.hg/drivers/xen/core/pci.c:28/pci_bus_probe_wrapper()
> 
> ...... Another 38 times of the call trace were omitted in the letter
> 
> 
> Detail Xen/IA64 Unstable Cset #18286 Status Report
> ============================================================
> Test Result Summary:
>         # total case:   17
>         # passed case: 17
>         # failed case:   0
> ============================================================
> Testing Environment:
>         platform: Tiger4
>         processor: Itanium 2 Processor
>         logic Processors number: 8 (2 processors with Dual Core)
>         pal version: 9.68
>         service os: RHEL5u2 IA64 SMP with 2 VCPUs
>         vti guest os: RHEL5u2 & RHEL4u3
>         xenU guest os: RHEL4u4
>         xen ia64 unstable tree: 18286
>         xen schedule: credit
>         gfw: open guest firmware Cset#126
> ============================================================
> Detailed Test Results:
> 
> Passed case Summary                     Description
>         Save&Restore                    Save&Restore
>         VTI_Live-migration                      Linux VTI live-migration
>         Two_UP_VTI_Co           UP_VTI (mem=256)
>         One_UP_VTI                         1 UP_VTI (mem=256)
>         One_UP_XenU                     1 UP_xenU(mem=256)
>         SMPVTI_LTP                      VTI (vcpus=4, mem=512) run LTP
>         SMPVTI_and_SMPXenU      1 VTI + 1 xenU (mem=256 vcpus=2)
>         Two_SMPXenU_Coexist     2 xenU (mem=256, vcpus=2)
>         One_SMPVTI_4096M                1 VTI (vcpus=2, mem=4096M)
>         SMPVTI_Network                  1 VTI (mem=256,vcpu=2) and'ping'
>         SMPXenU_Network         1 XenU (vcpus=2) and 'ping'
>         One_SMP_XenU                    1 SMP xenU (vcpus=2)
>         One_SMP_VTI                     1 SMP VTI (vcpus=2)
>         SMPVTI_Kernel_Build             VTI (vcpus=4) and do KernelBuild
>         UPVTI_Kernel_Build              1 UP VTI and do kernel build
>         SMPVTI_Windows                  SMPVTI windows(vcpu=2)
>         SMPWin_SMPVTI_SMPxenU   SMPVTI Linux/Windows & XenU
> -----------------------------------------------------------------------
> 
> 
> Thanks,
> Zhang Jingke
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

-- 
yamahata

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