From: David F Barrera <dfbp@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: RE: Time stopped
Date: Fri, 14 Oct 2005 09:34:45 -0500 [thread overview]
Message-ID: <1129300485.6440.12.camel@dbarrera_tp> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E371@liverpoolst.ad.cl.cam.ac.uk>
Ian,
I tried to reproduce with maxcpus=1 two or three times yesterday, and
the problem did not happen. It is not definitive, though, because xm-
test sometimes does run. But this morning, it hit the bug the first time
through, in the regular test (w/o the maxcpus parm).
On Thu, 2005-10-13 at 20:21 +0100, Ian Pratt wrote:
>
> > x335b:~ # cat /proc/interrupts
>
> You'll need to do this multiple times e.g. 10 seconds appart for us to
> figure out the rate.
>
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38166 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38199 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38238 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38272 Phys-irq peth0
256: 8489111 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
----
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38407 Phys-irq peth0
256: 8582512 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38450 Phys-irq peth0
256: 8582513 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
x335b:~ # cat /proc/interrupts
CPU0
1: 10 Phys-irq i8042
5: 0 Phys-irq acpi
11: 0 Phys-irq ohci_hcd:usb1
12: 110 Phys-irq i8042
15: 28 Phys-irq ide1
22: 9800 Phys-irq ioc0
24: 38482 Phys-irq peth0
256: 8675691 Dynamic-irq timer0
257: 0 Dynamic-irq console
258: 0 Dynamic-irq net-be-dbg
259: 13709 Dynamic-irq xenbus
NMI: 0
LOC: 0
ERR: 0
MIS: 0
>
> > >
> > > If you run something in the background that burns CPU does
> > it make a
> > > difference?
> > I started LTP on dom0 ( and can see console outpu) and it
> > makes no difference.
>
> I think a "while true; do true; done" might be more convincing, but LTP
> is probably good enough.
Did this. Time still static. Other sessions become unresponsive while this runs.
>
> > > In this case, what does xm list show as regards the CPU
> > time consumed
> > > by the domains?
> > x335b:/tmp/ltp-full-20050804 # date
> > Thu Oct 13 13:47:59 CDT 2005
> > x335b:/tmp/ltp-full-20050804 # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 - 4 r----- 96.5
> > 11_create_0 73 16 3 1 -b---- 0.3
> > x335b:/tmp/ltp-full-20050804 # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 - 4 r----- 96.5
> > 11_create_0 73 16 3 1 -b---- 0.3
> > x335b:/tmp/ltp-full-20050804 # xm list
> > Name ID Mem(MiB) CPU VCPUs State Time(s)
> > Domain-0 0 495 - 4 r----- 96.5
> > 11_create_0 73 16 3 1 -b---- 0.3
> > x335b:/tmp/ltp-full-20050804 #
> > x335b:/tmp/ltp-full-20050804 # date
> > Thu Oct 13 13:47:59 CDT 2005
>
> I didn't expect this. Need to think some.
>
> > > Can you narrow down which of the xm-tests actually
> > provoke's the bug?
>
I believe it is 11_create_concurrent_pos.py that's provoking this bug.
> Can you repro using just this test?
I will try.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-10-14 14:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 19:21 Time stopped Ian Pratt
2005-10-14 14:34 ` David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-14 17:51 Stephan Böni
2005-10-14 17:37 Ian Pratt
2005-10-14 16:37 Stephan Böni
2005-10-14 16:47 ` David F Barrera
2005-10-14 15:44 Stephan Böni
2005-10-14 15:23 Stephan Böni
2005-10-14 14:48 Stephan Böni
2005-10-14 15:01 ` David F Barrera
2005-10-14 15:12 ` Ted Kaczmarek
2005-10-14 16:46 ` Steven Hand
2005-10-13 17:29 Ian Pratt
2005-10-13 19:06 ` David F Barrera
2005-10-13 19:21 ` Dan Smith
2005-09-28 20:24 David F Barrera
2005-10-13 15:17 ` David F Barrera
2005-10-13 15:36 ` David F Barrera
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=1129300485.6440.12.camel@dbarrera_tp \
--to=dfbp@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.