From: John Weekes <lists.xen@nuclearfallout.net>
To: George Dunlap <george.dunlap@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>
Subject: Re: credit2 BUG_ON triggered
Date: Wed, 20 Apr 2011 10:33:36 -0700 [thread overview]
Message-ID: <4DAF18F0.5090400@nuclearfallout.net> (raw)
In-Reply-To: <1303318285.1955.3629.camel@elijah>
On 4/20/2011 9:51 AM, George Dunlap wrote:
> Yes, please, if you have the time. xen-unstable has some debugging
> output I put there after this failure was seen once in the xen.org
> automated testing. I've been over that code a number of times, and have
> no idea how that bug could be triggering. :-)
>
> Alternately, if you find unstable too unstable (or if you don't want to
> find out), you can revert xen-4.1-testing c/s 22977:6af8e01d3e4a, which
> turns off the debugging code I'd put in for the 4.1 release.
Any version works for me, since this is just for testing purposes (this
isn't a production machine yet).
On xen-unstable, I'm seeing that the domU just hangs after it starts.
The stubdom chews CPU very slowly, but there is no activity on the main
domain:
dallas-dodec226-5 customers # xl list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 1500 4 r-----
4061.2
testvds4 3 803 1
-b---- 0.0
testvds4-dm 4 32 1
-b---- 0.6
It's hanging after this:
(XEN) irq.c:258: Dom3 PCI link 1 changed 0 -> 10
(XEN) HVM3: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:258: Dom3 PCI link 2 changed 0 -> 11
(XEN) HVM3: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:258: Dom3 PCI link 3 changed 0 -> 5
(XEN) HVM3: PCI-ISA link 3 routed to IRQ5
(XEN) HVM3: pci dev 01:2 INTD->IRQ5
(XEN) HVM3: pci dev 01:3 INTA->IRQ10
(XEN) HVM3: pci dev 03:0 INTA->IRQ5
(XEN) HVM3: pci dev 04:0 INTA->IRQ5
(XEN) HVM3: pci dev 02:0 bar 10 size 02000000: f0000008
(XEN) HVM3: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM3: pci dev 04:0 bar 10 size 00020000: f3000000
(XEN) HVM3: pci dev 02:0 bar 14 size 00001000: f3020000
(XEN) HVM3: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM3: pci dev 04:0 bar 14 size 00000040: 0000c101
(XEN) HVM3: pci dev 01:2 bar 20 size 00000020: 0000c141
(XEN) HVM3: pci dev 01:1 bar 20 size 00000010: 0000c161
(XEN) HVM3: Multiprocessor initialisation:
(XEN) HVM3: - CPU0 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8]
... done.
(XEN) HVM3: - CPU1 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8]
... done.
(XEN) HVM3: - CPU2 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8]
... done.
(XEN) HVM3: - CPU3 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8]
... done.
(XEN) HVM3: Testing HVM environment:
(XEN) HVM3: - REP INSB across page boundaries ... passed
(XEN) HVM3: - GS base MSRs and SWAPGS ... passed
(XEN) HVM3: Passed 2 of 2 tests
(XEN) HVM3: Writing SMBIOS tables ...
Killing the domU works properly.
I'll try 4.1-testing again with the patch reversion.
-John
next prev parent reply other threads:[~2011-04-20 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 20:58 credit2 BUG_ON triggered John Weekes
2011-04-20 9:36 ` George Dunlap
2011-04-20 16:12 ` John Weekes
2011-04-20 16:51 ` George Dunlap
2011-04-20 17:33 ` John Weekes [this message]
2011-04-20 19:10 ` John Weekes
2011-04-20 19:29 ` John Weekes
2011-04-26 11:01 ` George Dunlap
2011-04-26 16:45 ` John Weekes
2011-04-26 17:02 ` George Dunlap
2011-04-26 20:15 ` John Weekes
2011-04-27 9:10 ` George Dunlap
2011-04-27 17:24 ` credit2 domU freeze at "Writing SMBIOS tables ..." John Weekes
2011-04-28 13:10 ` George Dunlap
2011-04-28 16:25 ` John Weekes
2011-04-28 16:35 ` George Dunlap
2011-04-28 19:56 ` John Weekes
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=4DAF18F0.5090400@nuclearfallout.net \
--to=lists.xen@nuclearfallout.net \
--cc=george.dunlap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.