xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Wang2 <wei.wang2@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"keir@xen.org" <keir@xen.org>
Subject: Re: AMD IOMMU related boot failure due to page coalescing c/s 23767
Date: Fri, 19 Aug 2011 18:12:56 +0200	[thread overview]
Message-ID: <201108191812.56614.wei.wang2@amd.com> (raw)
In-Reply-To: <20046.34925.817296.402826@mariner.uk.xensource.com>

Oh, that is another issue that I haven't got time to look at...
you could use iommu=no-perdev-vector-map to workaround this.
Thanks,
Wei

On Friday 19 August 2011 17:59:41 Ian Jackson wrote:
> I wrote:
> > The machine in question does have a reasonable amount of RAM.  And
> > yes, thanks, your patch fixes it for me.
>
> But wait, actually it now crashes later !
>
> (XEN) Assertion 'test_bit(vector, cfg->used_vectors)' failed at
> io_apic.c:455 (XEN) ----[ Xen-4.2-unstable  x86_64  debug=y  Not tainted
> ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff82c48015e062>]
> smp_irq_move_cleanup_interrupt+0x24d/0x2 cf
> (XEN) RFLAGS: 0000000000010046   CONTEXT: hypervisor
> (XEN) rax: 0000000000000000   rbx: 0000000000000051   rcx: ffff82c4802e0c60
> (XEN) rdx: 0000000000000051   rsi: 0000000000000001   rdi: ffff83021fe011b8
> (XEN) rbp: ffff82c4802a7e28   rsp: ffff82c4802a7da8   r8:  0000000000000001
> (XEN) r9:  ffff83021fff0108   r10: ffff83021fffa580   r11: 000000057f8429e5
> (XEN) r12: 0000000000000022   r13: ffff83021ff00890   r14: ffff83021fe011b4
> (XEN) r15: ffff82c4802a7f18   cr0: 000000008005003b   cr4: 00000000000006f0
> (XEN) cr3: 00000000dfcac000   cr2: 00000000c4463c80
> (XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0033   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff82c4802a7da8:
> (XEN)    ffff82c4802a7f18 ffff82c4802a7de8 ffff82c4802a7f18
> ffff82c4802a7f18 (XEN)    ffff82c4802e0c60 ffff82c4802e0c60
> 0000005100000000 0000000000000000 (XEN)    ffff82c4802e0700
> 0000000000000002 ffff82c4802a7e10 ffff82c4802a7f18 (XEN)   
> ffff82c480253150 ffff82c4802a7f18 00000004481ab3c7 ffff82c4802502c0 (XEN)  
>  00007d3b7fd581a7 ffff82c48014e000 ffff82c4802502c0 00000004481ab3c7 (XEN) 
>   ffff82c4802a7f18 ffff82c480253150 ffff82c4802a7ee0 ffff82c4802a7f18 (XEN)
>    000000057f8429e5 ffff83021fffa580 ffff83021fff0108 0000000000000001
> (XEN)    0000000000000000 0000000000000000 ffff82c4802e06f0
> ffff82c4802e1180 (XEN)    0000000000000000[    7.392316] A 0000002000000000
> ffff82c480154153 0000 00000000e008DDRCONF(NETDEV_U
> (XEN)    0000000000000246 ffff82c4802a7ee0 0000000000000000
> ffff82c4802a7f10P): eth0: link i
> (XEN)    ffff82c4801571e6 0000000000000000 ffff8300dfafe000
> 0000000000000000s no t ready
>
> (XEN)    ffff8300dfcef000 ffff82c4802a7d48 0000000000000000
> 0000000000000000 (XEN)    0000000000000000 0000000000000000
> 00000000c4b7bec4 00000000b7d902c8 (XEN)    0000000000000000
> 0000000000000000 0000000000000000 0000000000000000 (XEN)   
> 0000000000000001 00000000c4463c80 0000000000000002 00000000c441d300 (XEN)  
>  0000000020185067 0000000e00000003 00000000c104da9e 0000000000000061 (XEN) 
>   0000000000000202 00000000c4b7beb0 0000000000000069 0000000000000000 (XEN)
>    0000000000000000 0000000000000000 0000000000000000 0000000000000000
> (XEN)    ffff8300dfafe000 0000000000000000 0000000000000000
> (XEN) Xen call trace:
> (XEN)    [<ffff82c48015e062>] smp_irq_move_cleanup_interrupt+0x24d/0x2cf
> (XEN)    [<ffff82c48014e000>] irq_move_cleanup_interrupt+0x30/0x40
> (XEN)    [<ffff82c480154153>] default_idle+0x81/0x86
> (XEN)    [<ffff82c4801571e6>] idle_loop+0x55/0x69
> (XEN)
> [    7.393691] i(XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Assertion 'test_bit(vector, cfg->used_vectors)' failed at
> io_apic.c:455 gb: eth0 NIC Lin(XEN)
> ****************************************
> (XEN)
> k is Up 1000 Mbp(XEN) Reboot in five seconds...
> s Full Duplex, F(XEN) Assertion 'test_bit(vector, cfg->used_vectors)'
> failed at io_apic.c:455
> (XEN) ----[ Xen-4.2-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff82c48015e062>]
>  smp_irq_move_cleanup_interrupt+0x24d/0x2cf
> (XEN) RFLAGS: 0000000000010046   CONTEXT: hypervisor
> (XEN) rax: 0000000000000000   rbx: 0000000000000031   rcx: ffff82c4802e0c60
> (XEN) rdx: 0000000000000031   rsi: 0000000000000002   rdi: ffff83021fe00fb8
> (XEN) rbp: ffff82c4802a7968   rsp: ffff82c4802a78e8   r8:  0000000000000000
> (XEN) r9:  0000000000000048   r10: 00000000fffffffc   r11: 00000000fffffffe
> (XEN) r12: 000000000000001e   r13: ffff83021ff00790   r14: ffff83021fe00fb4
> (XEN) r15: ffff82c4802a7f18   cr0: 000000008005003b   cr4: 00000000000006f0
> (XEN) cr3: 00000000dfcac000   cr2: 00000000c4463c80
> (XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0033   ss: 0000   cs: e008
> (XEN) Xen stack trace from rsp=ffff82c4802a78e8:
> (XEN)    ffff82c4802a7f18 ffff82c4802a7928 ffff82c4802a7f18
> ffff82c4802a7f18 (XEN)    ffff82c4802e0c60 ffff82c4802e0c60
> 0000003100000000 ffff82c4802a7aa8 (XEN)    ffff82c4802a7938
> ffff82c48013b831 ffff82c4802a7968 ffff83021fe00280 (XEN)   
> 0000000000000200 0000000000000004 ffff82c4802a7aa8 ffff82c4802c6568 (XEN)  
>  00007d3b7fd58667 ffff82c48014e000 ffff82c4802c6568 ffff82c4802a7aa8 (XEN) 
>   0000000000000004 0000000000000200 ffff82c4802a7a98 ffff83021fe00280 (XEN)
>    00000000fffffffe 00000000fffffffc 0000000000000048 0000000000000000
> (XEN)    0000000000000000 0000000000000000 ffff82c4802a7f18
> 0000000000000002 (XEN)    ffff83021fe002b4 0000002000000000
> ffff82c480123d9c 000000000000e008 (XEN)    0000000000000246
> ffff82c4802a7a20 0000000000000000 ffff82c480162be2 (XEN)   
> ffff82c480123df4 ffff82c4802a7a58 0000000000000004 ffff83021fe002b4 (XEN)  
>  ffff82c400000004 ffff82c4802a7e38 ffff82c4802a7a78 ffff82c48013aa69 (XEN) 
>   ffff82c4802a7a78 ffff82c4802457e0 0000000000000082 ffff82c48023532e (XEN)
>    00000000000001c7 0000000000000061 00007d3b7fd58537 ffff82c48015b3b6
> (XEN)    0000000000000061 00000000000001c7 ffff82c48023532e
> 0000000000000082 (XEN)    ffff82c4802a7b88 ffff82c4802457e0
> 00000000fffffffe 00000000fffffffc (XEN)    0000000000000048
> 0000000000000000 0000000000000000 0000000000000000 (XEN)   
> ffff82c4802a7f18 0000000000000002 ffff82c48025d3a0 000000f100000000 (XEN)  
>  ffff82c480176905 000000000000e008 0000000000000246 ffff82c4802a7b58 (XEN) 
>   0000000000000000 ffff82c4801768fd 0000138880245802 ffff82c4802457e0 (XEN)
> Xen call trace:
> (XEN)    [<ffff82c48015e062>] smp_irq_move_cleanup_interrupt+0x24d/0x2cf
> (XEN)    [<ffff82c48014e000>] irq_move_cleanup_interrupt+0x30/0x40
> (XEN)    [<ffff82c480123d9c>] _spin_unlock_irq+0x44/0x45
> (XEN)    [<ffff82c48015b3b6>] common_interrupt+0x26/0x30
> (XEN)    [<ffff82c480176905>] machine_restart+0x3d/0x1e2
> (XEN)    [<ffff82c48013b13d>] panic+0x18d/0x199
> (XEN)    [<ffff82c48017f85b>] do_invalid_op+0x3d1/0x458
> (XEN)    [<ffff82c480219d36>] handle_exception_saved+0x30/0x6e
> (XEN)    [<ffff82c48015e062>] smp_irq_move_cleanup_interrupt+0x24d/0x2cf
> (XEN)    [<ffff82c48014e000>] irq_move_cleanup_interrupt+0x30/0x40
> (XEN)    [<ffff82c480154153>] default_idle+0x81/0x86
> (XEN)    [<ffff82c4801571e6>] idle_loop+0x55/0x69
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) Assertion 'test_bit(vector, cfg->used_vectors)' failed at
> io_apic.c:455 (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...

  reply	other threads:[~2011-08-19 16:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 13:19 AMD IOMMU related boot failure due to page coalescing c/s 23767 Ian Jackson
2011-08-19 13:55 ` Wei Wang2
2011-08-19 13:58   ` Logging xen dmesg John Backes
2011-08-19 14:24     ` Pasi Kärkkäinen
2011-08-19 14:25     ` Keir Fraser
2011-08-19 14:55 ` AMD IOMMU related boot failure due to page coalescing c/s 23767 Wei Wang2
2011-08-19 15:57   ` Ian Jackson
2011-08-19 15:59     ` Ian Jackson
2011-08-19 16:12       ` Wei Wang2 [this message]
2011-08-19 16:16         ` Ian Jackson
2011-08-19 16:29           ` Keir Fraser
2011-08-19 16:30         ` Ian Jackson
2011-08-22 11:29       ` George Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201108191812.56614.wei.wang2@amd.com \
    --to=wei.wang2@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).