* Ian Pratt (m+Ian.Pratt@xxxxxxxxxxxx) wrote:
> For us, the bug is hard to repro, despite us having tried on several
> different machines (2 and 4 way SMP, Opteron and Xeon, tg3 and e1000
> NICs).
xeon, 4 cpu (2-ht), e1000, 4G
- works fine w/ 32-bit
- dom0 is UP (SMP fails as well)
- this is dom0 only, no xend, no domUs, no bridging
- limiting to 2G works fine, sounds like something with swiotlb
Also, while it was working, I blasted with packets, and eventually got:
irq 19: nobody cared (try booting with the "irqpoll" option)
Call Trace: <IRQ> <ffffffff80148508>{__report_bad_irq+56}
<ffffffff80148721>{note_interrupt+449}
<ffffffff80147dcc>{handle_IRQ_event+76}
<ffffffff80147ec2>{__do_IRQ+162} <ffffffff8011077b>{do_IRQ+75}
<ffffffff802f16b5>{evtchn_do_upcall+117}
<ffffffff8010e5f1>{do_hypervisor_callback+37}
<ffffffff8011ccc5>{ia32_syscall+13}
<ffffffff8010a22a>{hypercall_page+554}
<ffffffff8010a22a>{hypercall_page+554}
<ffffffff802f14de>{force_evtchn_callback+14}
<ffffffff80147db5>{handle_IRQ_event+53} <ffffffff80147ea8>{__do_IRQ+136}
<ffffffff8011077b>{do_IRQ+75} <ffffffff802f16b5>{evtchn_do_upcall+117}
<ffffffff8010e5f1>{do_hypervisor_callback+37} <EOI>
<ffffffff8011ccc5>{ia32_syscall+13}
handlers:
[<ffffffff80377b80>] (ata_interrupt+0x0/0x1b0)
[<ffffffff80396570>] (usb_hcd_irq+0x0/0x70)
Disabling IRQ #19
thanks,
-chris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home