Bruce Edge
2010-Aug-30 23:12 UTC
[Xen-devel] Process irqbalance: BUG: unable to handle kernel paging request - with 2.6.32.18 pv-ops & xen 4.0.1
Using Jeremy''s latest 2.6.32 pv-ops kernel for both dom0 and domU, I
get
this BUG at domU boot time.
[ 14.780699] BUG: unable to handle kernel paging request at
00000002dd253558
[ 14.780787] RAX: 0000000000000000 RBX: 0000000000000020 RCX:
0000000000000020
[ 14.780793] RDX: 0000000000000020 RSI: 0000000000000ffe RDI:
0000000000000000
[ 14.780799] RBP: ffff8800717bde68 R08: 0000000000000023 R09:
0000000000000001
[ 14.780806] R10: ffffffff8182d004 R11: 0000000000000000 R12:
0000000000000000
[ 14.780812] R13: 00000002dd253558 R14: 0000000000000ffe R15:
ffff88000b515000
[ 14.780822] FS: 00007feac5f86720(0000) GS:ffff880011423000(0000)
knlGS:0000000000000000
[ 14.780829] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 14.780834] CR2: 00000002dd253558 CR3: 00000000789db000 CR4:
0000000000002660
[ 14.780841] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 14.780847] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 14.780854] Process irqbalance (pid: 880, threadinfo ffff8800717bc000,
task ffff88007306c7e0)
[ 14.780861] Stack:
[ 14.780864] ffffffff819180a0 ffff88000b515000 ffffffff81944798
ffff88000a861da8
[ 14.780874] <0> ffff8800717bdf48 ffff88000aa780a0 ffff8800717bde88
ffffffff8135760b
[ 14.780885] <0> ffff88000a861da8 fffffffffffffffb ffff8800717bdea8
ffffffff814061ef
[ 14.780898] Call Trace:
[ 14.780905] [<ffffffff8135760b>] local_cpus_show+0x4b/0x70
[ 14.780913] [<ffffffff814061ef>] dev_attr_show+0x2f/0x70
[ 14.780921] [<ffffffff811df8ed>] sysfs_read_file+0x10d/0x1f0
[ 14.781108] [<ffffffff8116d018>] vfs_read+0xc8/0x1a0
[ 14.781114] [<ffffffff8116d1f5>] sys_read+0x55/0x90
[ 14.781123] [<ffffffff810151f2>] system_call_fastpath+0x16/0x1b
[ 14.781129] Code: 45 31 e4 83 e1 e0 89 cb 83 eb 20 78 62 66 90 89 d8 89
d9 41 b9 01 00 00 00 c1 f8 06 83 e1 3f 44 8d 42 03 48 98 49 63 fc 44 89 f6
<49> 8b 44 c5 00 49 8d 3c 3f 44 29 e6 41 c1 f8 02 48 d3 e8 89 d1
[ 14.781206] RIP [<ffffffff8134019c>] bitmap_scnprintf+0x5c/0xc0
[ 14.781213] RSP <ffff8800717bde38>
[ 14.781217] CR2: 00000002dd253558
[ 14.781224] ---[ end trace ec14b09e94a4d7d5 ]---
The system appears stable after this, although no additional testing has
been done - this is a fresh conversion from hvm to pvops and has zero
mileage on it.
dom0/domU config is attached - it''s a slightly modified version of
Pasi''s
recommended configs.
There are 4 passed though PCI FC HBAs:
(From domU)
#> lspci
07:00.0 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.1 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.2 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
07:00.3 Fibre Channel: PMC-Sierra Inc. Device 8032 (rev 08)
Here''s the dom0 grub info:
menuentry ''xen-4.0.1'' --class osa-dom0 --class gnu-linux
--class gnu --class
os {
recordfail
insmod lvm
insmod ext2
set root=''(system-dom0_0)''
search --no-floppy --fs-uuid --set 9cde7c5a-26ac-455a-b33c-99ced80cd012
multiboot /boot/xen-4.0.1.gz dummy=dummy dom0_mem=512M dom0_max_vcpus=1
dom0_vcpus_pin=true iommu=1,passthrough,no-intremap loglvl=all
loglvl_guest=all loglevl=10 debug apic=on apic_verbosity=verbose
extra_guest_irqs=80 com1=115200,8n1 console=com1 console_to_ring
xen-pciback.permissive acpi=force numa=on
module /boot/vmlinuz-2.6.32.18-2 dummy=dummy
root=/dev/mapper/system-dom0_0 ro earlyprintk=xen loglevel=10 debug
acpi=force console=hvc0,115200n8
module /boot/initrd.img-2.6.32.18-2
}
The -2 on the kernel version is just to differentiate my own kernel builds.
domU kernel cmdline:
root=UUID=4bfe8bee-981f-4249-af94-12b117a6a9d5 ro iommu=soft swiotlb=force
console=hvc0,115200n8 ip=:127.0.255.255::::eth0:dh
Here''s the dom0/domU config:
#> xm list -l
(domain
(domid 0)
(cpu_weight 256)
(cpu_cap 0)
(bootloader )
(on_crash restart)
(uuid 00000000-0000-0000-0000-000000000000)
(bootloader_args )
(vcpus 1)
(name Domain-0)
(cpus ((0)))
(on_reboot restart)
(on_poweroff destroy)
(maxmem 16777215)
(memory 508)
(shadow_memory 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(cpu_time 2721.96308254)
(online_vcpus 1)
(image (linux (kernel ) (superpages 0) (nomigrate 0) (tsc_mode 0)))
(status 2)
(state r-----)
)
(domain
(domid 15)
(cpu_weight 256)
(cpu_cap 0)
(bootloader /usr/bin/pygrub)
(on_crash destroy)
(uuid 31919cda-8b71-ea43-331d-014413ee01ee)
(bootloader_args )
(vcpus 15)
(description )
(name dpm)
(cpus ((0) (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13)
(14)))
(on_reboot restart)
(on_poweroff destroy)
(maxmem 2048)
(memory 2048)
(shadow_memory 0)
(features )
(on_xend_start ignore)
(on_xend_stop ignore)
(start_time 1283208898.73)
(cpu_time 22.832023675)
(online_vcpus 15)
(image
(linux
(kernel )
(args ''ip=:127.0.255.255::::eth0:dhcp '')
(superpages 0)
(videoram 4)
(pci
((0x0000 0x07 0x00 0x3 0x80 ())
(0x0000 0x07 0x00 0x2 0x88 ())
(0x0000 0x07 0x00 0x1 0x90 ())
(0x0000 0x07 0x00 0x0 0x98 ())
)
)
(serial pty)
(nomigrate 0)
(tsc_mode 0)
(notes
(HV_START_LOW 18446603336221196288)
(FEATURES
''!writable_page_tables|pae_pgdir_above_4gb'')
(VIRT_BASE 18446744071562067968)
(GUEST_VERSION 2.6)
(PADDR_OFFSET 0)
(GUEST_OS linux)
(HYPERCALL_PAGE 18446744071578882048)
(LOADER generic)
(SUSPEND_CANCEL 1)
(PAE_MODE yes)
(ENTRY 18446744071591031296)
(XEN_VERSION xen-3.0)
)
)
)
(status 2)
(state -b----)
(store_mfn 1653142)
(console_mfn 1653141)
(device
(vif
(mac 00:16:3e:00:18:01)
(script /etc/xen/scripts/vif-bridge)
(uuid c100d71a-429d-e3e3-788d-ae55d0b1224a)
(backend 0)
)
)
(device
(console
(protocol vt100)
(location 2)
(uuid 8b82034b-7f7c-3009-7ec6-dffaaecfde19)
)
)
(device
(vbd
(protocol x86_64-abi)
(uuid 1c42cc85-a7b1-8db5-d61d-b7fdb996b459)
(bootable 1)
(dev xvda:sda)
(uname phy:system/dpm_0)
(mode w)
(backend 0)
(VDI )
)
)
(device
(pci
(dev
(slot 0x00)
(domain 0x0000)
(key ''0000:07:00.3@10'')
(bus 0x07)
(vdevfn 0x80)
(func 0x3)
(uuid ef12d3a8-d093-3cc7-019e-59a2094d1621)
)
(dev
(slot 0x00)
(domain 0x0000)
(key ''0000:07:00.2@11'')
(bus 0x07)
(vdevfn 0x88)
(func 0x2)
(uuid dd63274b-596d-8116-720d-d8a5a3b0cc2d)
)
(dev
(slot 0x00)
(domain 0x0000)
(key ''0000:07:00.1@12'')
(bus 0x07)
(vdevfn 0x90)
(func 0x1)
(uuid e5b72fa1-23d0-6e9f-5f15-1b6c20e39d34)
)
(dev
(slot 0x00)
(domain 0x0000)
(key ''0000:07:00.0@13'')
(bus 0x07)
(vdevfn 0x98)
(func 0x0)
(uuid 4c3c7348-1989-e1fb-0dd4-38be150ff572)
)
(uuid 7b9d3620-9aa1-5e9c-6c22-3400b2d648af)
(backend 0)
)
)
Let me know if there''s any other information I can provide.
Thanks
-Bruce
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Aug-31 18:00 UTC
Re: [Xen-devel] Process irqbalance: BUG: unable to handle kernel paging request - with 2.6.32.18 pv-ops & xen 4.0.1
On 08/30/2010 04:12 PM, Bruce Edge wrote:> Using Jeremy''s latest 2.6.32 pv-ops kernel for both dom0 and domU, I > get this BUG at domU boot time. > > [ 14.780699] BUG: unable to handle kernel paging request at > 00000002dd253558 > [ 14.780787] RAX: 0000000000000000 RBX: 0000000000000020 RCX: > 0000000000000020 > [ 14.780793] RDX: 0000000000000020 RSI: 0000000000000ffe RDI: > 0000000000000000 > [ 14.780799] RBP: ffff8800717bde68 R08: 0000000000000023 R09: > 0000000000000001 > [ 14.780806] R10: ffffffff8182d004 R11: 0000000000000000 R12: > 0000000000000000 > [ 14.780812] R13: 00000002dd253558 R14: 0000000000000ffe R15: > ffff88000b515000 > [ 14.780822] FS: 00007feac5f86720(0000) GS:ffff880011423000(0000) > knlGS:0000000000000000 > [ 14.780829] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > [ 14.780834] CR2: 00000002dd253558 CR3: 00000000789db000 CR4: > 0000000000002660 > [ 14.780841] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > 0000000000000000 > [ 14.780847] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > 0000000000000400 > [ 14.780854] Process irqbalance (pid: 880, threadinfo > ffff8800717bc000, task ffff88007306c7e0) > [ 14.780861] Stack: > [ 14.780864] ffffffff819180a0 ffff88000b515000 ffffffff81944798 > ffff88000a861da8 > [ 14.780874] <0> ffff8800717bdf48 ffff88000aa780a0 ffff8800717bde88 > ffffffff8135760b > [ 14.780885] <0> ffff88000a861da8 fffffffffffffffb ffff8800717bdea8 > ffffffff814061ef > [ 14.780898] Call Trace: > [ 14.780905] [<ffffffff8135760b>] local_cpus_show+0x4b/0x70 > [ 14.780913] [<ffffffff814061ef>] dev_attr_show+0x2f/0x70 > [ 14.780921] [<ffffffff811df8ed>] sysfs_read_file+0x10d/0x1f0 > [ 14.781108] [<ffffffff8116d018>] vfs_read+0xc8/0x1a0 > [ 14.781114] [<ffffffff8116d1f5>] sys_read+0x55/0x90 > [ 14.781123] [<ffffffff810151f2>] system_call_fastpath+0x16/0x1b > [ 14.781129] Code: 45 31 e4 83 e1 e0 89 cb 83 eb 20 78 62 66 90 89 > d8 89 d9 41 b9 01 00 00 00 c1 f8 06 83 e1 3f 44 8d 42 03 48 98 49 63 > fc 44 89 f6 <49> 8b 44 c5 00 49 8d 3c 3f 44 29 e6 41 c1 f8 02 48 d3 e8 > 89 d1 > [ 14.781206] RIP [<ffffffff8134019c>] bitmap_scnprintf+0x5c/0xc0 > [ 14.781213] RSP <ffff8800717bde38> > [ 14.781217] CR2: 00000002dd253558 > [ 14.781224] ---[ end trace ec14b09e94a4d7d5 ]--- > > The system appears stable after this, although no additional testing > has been done - this is a fresh conversion from hvm to pvops and has > zero mileage on it. > > dom0/domU config is attached - it''s a slightly modified version of > Pasi''s recommended configs.How many cpus do you have configured and online? J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bruce Edge
2010-Aug-31 18:17 UTC
Re: [Xen-devel] Process irqbalance: BUG: unable to handle kernel paging request - with 2.6.32.18 pv-ops & xen 4.0.1
On Tue, Aug 31, 2010 at 11:00 AM, Jeremy Fitzhardinge <jeremy@goop.org>wrote:> On 08/30/2010 04:12 PM, Bruce Edge wrote: > > Using Jeremy''s latest 2.6.32 pv-ops kernel for both dom0 and domU, I > > get this BUG at domU boot time. > > > > [ 14.780699] BUG: unable to handle kernel paging request at > > 00000002dd253558 > > [ 14.780787] RAX: 0000000000000000 RBX: 0000000000000020 RCX: > > 0000000000000020 > > [ 14.780793] RDX: 0000000000000020 RSI: 0000000000000ffe RDI: > > 0000000000000000 > > [ 14.780799] RBP: ffff8800717bde68 R08: 0000000000000023 R09: > > 0000000000000001 > > [ 14.780806] R10: ffffffff8182d004 R11: 0000000000000000 R12: > > 0000000000000000 > > [ 14.780812] R13: 00000002dd253558 R14: 0000000000000ffe R15: > > ffff88000b515000 > > [ 14.780822] FS: 00007feac5f86720(0000) GS:ffff880011423000(0000) > > knlGS:0000000000000000 > > [ 14.780829] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > > [ 14.780834] CR2: 00000002dd253558 CR3: 00000000789db000 CR4: > > 0000000000002660 > > [ 14.780841] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > > 0000000000000000 > > [ 14.780847] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > > 0000000000000400 > > [ 14.780854] Process irqbalance (pid: 880, threadinfo > > ffff8800717bc000, task ffff88007306c7e0) > > [ 14.780861] Stack: > > [ 14.780864] ffffffff819180a0 ffff88000b515000 ffffffff81944798 > > ffff88000a861da8 > > [ 14.780874] <0> ffff8800717bdf48 ffff88000aa780a0 ffff8800717bde88 > > ffffffff8135760b > > [ 14.780885] <0> ffff88000a861da8 fffffffffffffffb ffff8800717bdea8 > > ffffffff814061ef > > [ 14.780898] Call Trace: > > [ 14.780905] [<ffffffff8135760b>] local_cpus_show+0x4b/0x70 > > [ 14.780913] [<ffffffff814061ef>] dev_attr_show+0x2f/0x70 > > [ 14.780921] [<ffffffff811df8ed>] sysfs_read_file+0x10d/0x1f0 > > [ 14.781108] [<ffffffff8116d018>] vfs_read+0xc8/0x1a0 > > [ 14.781114] [<ffffffff8116d1f5>] sys_read+0x55/0x90 > > [ 14.781123] [<ffffffff810151f2>] system_call_fastpath+0x16/0x1b > > [ 14.781129] Code: 45 31 e4 83 e1 e0 89 cb 83 eb 20 78 62 66 90 89 > > d8 89 d9 41 b9 01 00 00 00 c1 f8 06 83 e1 3f 44 8d 42 03 48 98 49 63 > > fc 44 89 f6 <49> 8b 44 c5 00 49 8d 3c 3f 44 29 e6 41 c1 f8 02 48 d3 e8 > > 89 d1 > > [ 14.781206] RIP [<ffffffff8134019c>] bitmap_scnprintf+0x5c/0xc0 > > [ 14.781213] RSP <ffff8800717bde38> > > [ 14.781217] CR2: 00000002dd253558 > > [ 14.781224] ---[ end trace ec14b09e94a4d7d5 ]--- > > > > The system appears stable after this, although no additional testing > > has been done - this is a fresh conversion from hvm to pvops and has > > zero mileage on it. > > > > dom0/domU config is attached - it''s a slightly modified version of > > Pasi''s recommended configs. > > How many cpus do you have configured and online? > > J > >Lots :-) I''m allocating 14 cores to this domU: (vcpus 14) (cpus ((2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15))) (on_reboot restart) (on_poweroff destroy) (maxmem 2048) (memory 2048) (online_vcpus 14) -Bruce _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Bruce Edge
2010-Sep-02 16:15 UTC
Re: [Xen-devel] Process irqbalance: BUG: unable to handle kernel paging request - with 2.6.32.18 pv-ops & xen 4.0.1
On Tue, Aug 31, 2010 at 11:17 AM, Bruce Edge <bruce.edge@gmail.com> wrote:> > On Tue, Aug 31, 2010 at 11:00 AM, Jeremy Fitzhardinge <jeremy@goop.org>wrote: > >> On 08/30/2010 04:12 PM, Bruce Edge wrote: >> > Using Jeremy''s latest 2.6.32 pv-ops kernel for both dom0 and domU, I >> > get this BUG at domU boot time. >> > >> > [ 14.780699] BUG: unable to handle kernel paging request at >> > 00000002dd253558 >> > [ 14.780787] RAX: 0000000000000000 RBX: 0000000000000020 RCX: >> > 0000000000000020 >> > [ 14.780793] RDX: 0000000000000020 RSI: 0000000000000ffe RDI: >> > 0000000000000000 >> > [ 14.780799] RBP: ffff8800717bde68 R08: 0000000000000023 R09: >> > 0000000000000001 >> > [ 14.780806] R10: ffffffff8182d004 R11: 0000000000000000 R12: >> > 0000000000000000 >> > [ 14.780812] R13: 00000002dd253558 R14: 0000000000000ffe R15: >> > ffff88000b515000 >> > [ 14.780822] FS: 00007feac5f86720(0000) GS:ffff880011423000(0000) >> > knlGS:0000000000000000 >> > [ 14.780829] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b >> > [ 14.780834] CR2: 00000002dd253558 CR3: 00000000789db000 CR4: >> > 0000000000002660 >> > [ 14.780841] DR0: 0000000000000000 DR1: 0000000000000000 DR2: >> > 0000000000000000 >> > [ 14.780847] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: >> > 0000000000000400 >> > [ 14.780854] Process irqbalance (pid: 880, threadinfo >> > ffff8800717bc000, task ffff88007306c7e0) >> > [ 14.780861] Stack: >> > [ 14.780864] ffffffff819180a0 ffff88000b515000 ffffffff81944798 >> > ffff88000a861da8 >> > [ 14.780874] <0> ffff8800717bdf48 ffff88000aa780a0 ffff8800717bde88 >> > ffffffff8135760b >> > [ 14.780885] <0> ffff88000a861da8 fffffffffffffffb ffff8800717bdea8 >> > ffffffff814061ef >> > [ 14.780898] Call Trace: >> > [ 14.780905] [<ffffffff8135760b>] local_cpus_show+0x4b/0x70 >> > [ 14.780913] [<ffffffff814061ef>] dev_attr_show+0x2f/0x70 >> > [ 14.780921] [<ffffffff811df8ed>] sysfs_read_file+0x10d/0x1f0 >> > [ 14.781108] [<ffffffff8116d018>] vfs_read+0xc8/0x1a0 >> > [ 14.781114] [<ffffffff8116d1f5>] sys_read+0x55/0x90 >> > [ 14.781123] [<ffffffff810151f2>] system_call_fastpath+0x16/0x1b >> > [ 14.781129] Code: 45 31 e4 83 e1 e0 89 cb 83 eb 20 78 62 66 90 89 >> > d8 89 d9 41 b9 01 00 00 00 c1 f8 06 83 e1 3f 44 8d 42 03 48 98 49 63 >> > fc 44 89 f6 <49> 8b 44 c5 00 49 8d 3c 3f 44 29 e6 41 c1 f8 02 48 d3 e8 >> > 89 d1 >> > [ 14.781206] RIP [<ffffffff8134019c>] bitmap_scnprintf+0x5c/0xc0 >> > [ 14.781213] RSP <ffff8800717bde38> >> > [ 14.781217] CR2: 00000002dd253558 >> > [ 14.781224] ---[ end trace ec14b09e94a4d7d5 ]--- >> > >> > The system appears stable after this, although no additional testing >> > has been done - this is a fresh conversion from hvm to pvops and has >> > zero mileage on it. >> > >> > dom0/domU config is attached - it''s a slightly modified version of >> > Pasi''s recommended configs. >> >> How many cpus do you have configured and online? >> >> J >> >>I re-ran the same test with 1 cpu/vcpu and the BUG was _not_ present. Incrementing cpus and vcpus to 2 did cause the problem. If there anything else I can do to provide more information that would assist in troubleshooting, just ask. -Bruce> > Lots :-) > > I''m allocating 14 cores to this domU: > > (vcpus 14) > (cpus ((2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15))) > (on_reboot restart) > (on_poweroff destroy) > (maxmem 2048) > (memory 2048) > (online_vcpus 14) > > > -Bruce > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-Sep-02 17:02 UTC
Re: [Xen-devel] Process irqbalance: BUG: unable to handle kernel paging request - with 2.6.32.18 pv-ops & xen 4.0.1
On 09/02/2010 09:15 AM, Bruce Edge wrote:> On Tue, Aug 31, 2010 at 11:17 AM, Bruce Edge <bruce.edge@gmail.com > <mailto:bruce.edge@gmail.com>> wrote: > > > On Tue, Aug 31, 2010 at 11:00 AM, Jeremy Fitzhardinge > <jeremy@goop.org <mailto:jeremy@goop.org>> wrote: > > On 08/30/2010 04:12 PM, Bruce Edge wrote: > > Using Jeremy''s latest 2.6.32 pv-ops kernel for both dom0 and > domU, I > > get this BUG at domU boot time. > > > > [ 14.780699] BUG: unable to handle kernel paging request at > > 00000002dd253558 > > [ 14.780787] RAX: 0000000000000000 RBX: 0000000000000020 RCX: > > 0000000000000020 > > [ 14.780793] RDX: 0000000000000020 RSI: 0000000000000ffe RDI: > > 0000000000000000 > > [ 14.780799] RBP: ffff8800717bde68 R08: 0000000000000023 R09: > > 0000000000000001 > > [ 14.780806] R10: ffffffff8182d004 R11: 0000000000000000 R12: > > 0000000000000000 > > [ 14.780812] R13: 00000002dd253558 R14: 0000000000000ffe R15: > > ffff88000b515000 > > [ 14.780822] FS: 00007feac5f86720(0000) > GS:ffff880011423000(0000) > > knlGS:0000000000000000 > > [ 14.780829] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > > [ 14.780834] CR2: 00000002dd253558 CR3: 00000000789db000 CR4: > > 0000000000002660 > > [ 14.780841] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > > 0000000000000000 > > [ 14.780847] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > > 0000000000000400 > > [ 14.780854] Process irqbalance (pid: 880, threadinfo > > ffff8800717bc000, task ffff88007306c7e0) > > [ 14.780861] Stack: > > [ 14.780864] ffffffff819180a0 ffff88000b515000 > ffffffff81944798 > > ffff88000a861da8 > > [ 14.780874] <0> ffff8800717bdf48 ffff88000aa780a0 > ffff8800717bde88 > > ffffffff8135760b > > [ 14.780885] <0> ffff88000a861da8 fffffffffffffffb > ffff8800717bdea8 > > ffffffff814061ef > > [ 14.780898] Call Trace: > > [ 14.780905] [<ffffffff8135760b>] local_cpus_show+0x4b/0x70 > > [ 14.780913] [<ffffffff814061ef>] dev_attr_show+0x2f/0x70 > > [ 14.780921] [<ffffffff811df8ed>] sysfs_read_file+0x10d/0x1f0 > > [ 14.781108] [<ffffffff8116d018>] vfs_read+0xc8/0x1a0 > > [ 14.781114] [<ffffffff8116d1f5>] sys_read+0x55/0x90 > > [ 14.781123] [<ffffffff810151f2>] > system_call_fastpath+0x16/0x1b > > [ 14.781129] Code: 45 31 e4 83 e1 e0 89 cb 83 eb 20 78 62 > 66 90 89 > > d8 89 d9 41 b9 01 00 00 00 c1 f8 06 83 e1 3f 44 8d 42 03 48 > 98 49 63 > > fc 44 89 f6 <49> 8b 44 c5 00 49 8d 3c 3f 44 29 e6 41 c1 f8 > 02 48 d3 e8 > > 89 d1 > > [ 14.781206] RIP [<ffffffff8134019c>] > bitmap_scnprintf+0x5c/0xc0 > > [ 14.781213] RSP <ffff8800717bde38> > > [ 14.781217] CR2: 00000002dd253558 > > [ 14.781224] ---[ end trace ec14b09e94a4d7d5 ]--- > > > > The system appears stable after this, although no additional > testing > > has been done - this is a fresh conversion from hvm to pvops > and has > > zero mileage on it. > > > > dom0/domU config is attached - it''s a slightly modified > version of > > Pasi''s recommended configs. > > How many cpus do you have configured and online? > > J > > > I re-ran the same test with 1 cpu/vcpu and the BUG was _not_ present. > > Incrementing cpus and vcpus to 2 did cause the problem. > > If there anything else I can do to provide more information that would > assist in troubleshooting, just ask.I haven''t had a chance to look at this, but something odd must be going on; irqbalanced works OK for me (though I don''t generally recommend using it). Do you think you could try and work out what irqbalanced is doing to trigger the problem (ie, what string it is writing into what file)? Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel