[vwnc] Anybody seen lockups like these?
Locked
[vwnc] Anybody seen lockups like these?
 
|
vwnt.exe (VW 7.6 VM) jumped to using 100% of one CPU core and could not be interrupted. No memory growth. I'd only clicked in a code browser window (perhaps involving a store query). Process
Explorer stack information for vwnt.exe showed this:
ntkrnlpa.exe+0x6e9ab
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0 hal.dll+0x2ef2 vwntoe.dll!registerInRt+0x2fb54 Google searches suggest a driver problem. Not sure which driver or why now, but I'm glad my work was saved first.
Paul Baumann
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] Anybody seen lockups like these?
|
|
Was this a perm saved image, by any
chance? From: [hidden email] [mailto:[hidden email]] On Behalf Of Paul Baumann Sent: Monday, November 30, 2009 2:18 PM To: [hidden email] Subject: [vwnc] Anybody seen lockups like these? vwnt.exe (VW 7.6
VM) jumped to using 100% of one CPU core and could not be interrupted.
No memory growth. I'd only clicked in a code browser window (perhaps involving a
store query). Process Explorer stack information for vwnt.exe showed
this:
ntkrnlpa.exe+0x6e9ab
ntkrnlpa.exe!MmIsDriverVerifying+0xbb0 hal.dll+0x2ef2 vwntoe.dll!registerInRt+0x2fb54 Google searches
suggest a driver problem. Not sure which driver or why now, but I'm glad my
work was saved first.
Paul Baumann
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] Anybody seen lockups like these?
|
|
In reply to this post by Paul Baumann
We had a problem like this with XEN that seemed related to clocks differing significantly from CPU to CPU and we had to use the affinity controls to keep the VW image on one CPU. Paul Baumann wrote:
-- Dennis Smith +1 416.798.7948 Cherniak Software Development Corporation Fax: +1 416.798.0948 509-2001 Sheppard Avenue East [hidden email] Toronto, ON M2J 4Z8 <a class="moz-txt-link-freetext" href="sip:dennis@CherniakSoftware.com">sip:dennis@... Canada http://www.CherniakSoftware.com Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] Anybody seen lockups like these?
|
|
I would be very interested in any information related
to VM misbehavior controlled by core / cpu affinity. With that said, I'd
suggest trying a 7.6c or later VM.
Andres. From: [hidden email] [mailto:[hidden email]] On Behalf Of Dennis Smith Sent: Monday, November 30, 2009 4:46 PM To: Paul Baumann Cc: [hidden email] Subject: Re: [vwnc] Anybody seen lockups like these? We had a problem like this with XEN that seemed related to clocks differing significantly from CPU to CPU and we had to use the affinity controls to keep the VW image on one CPU. Paul Baumann wrote:
-- Dennis Smith +1 416.798.7948 Cherniak Software Development Corporation Fax: +1 416.798.0948 509-2001 Sheppard Avenue East [hidden email] Toronto, ON M2J 4Z8 <A class=moz-txt-link-freetext href="sip:dennis@CherniakSoftware.com">sip:dennis@... Canada http://www.CherniakSoftware.com Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: [vwnc] Anybody seen lockups like these?
|
|
Sorry, I just double checked the VM version and found I'd been running 7.5 Apr 16 2007 VM on this box for at least a year now. I thought I'd been using
the 7.6 Feb 14 2008 VM used elsewhere. It was the 7.5 VM that locked on me yesterday. No, no VM technology involved in this configuration.
The clock diff and affinity issues bring back memories. One of those issues had been complicating some very deep debugging I was doing last year. I tried
going back to 7.5 VM on this box and I never configured back to 7.6 even after the presumed 7.6c fix.
Dennis,
Back in Feb'08 I found that assigning affinity fixed VW performance issues that only seemed to happen on Intel hyper-threading processors. I wonder if both
are related to the same problem. Slow down waiting for an exaggerated future time value; freeze waiting for a past time value. The common factor being time reporting variances between HT core switches. VM technology (like VMWare or Xen) might be a another
variation of the same time-diff problem even if not on a HT processor. In any case, it looks like Andres thinks the problem should be fixed in 7.6c or later VM.
Paul Baumann
From: Valloud, Andres [mailto:[hidden email]] Sent: Monday, November 30, 2009 8:50 PM To: Dennis Smith; Paul Baumann Cc: [hidden email] Subject: RE: [vwnc] Anybody seen lockups like these? Importance: High I would be very interested in any information related to VM misbehavior controlled by core / cpu affinity. With that said, I'd suggest trying a 7.6c or
later VM.
Andres.
From: [hidden email] [mailto:[hidden email]] On Behalf Of Dennis Smith Sent: Monday, November 30, 2009 4:46 PM To: Paul Baumann Cc: [hidden email] Subject: Re: [vwnc] Anybody seen lockups like these? We had a problem like this with XEN that seemed related to clocks differing significantly from CPU to CPU and we had to use the affinity controls to keep the VW image on one CPU. Paul Baumann wrote:
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
«
Return to VisualWorks
|
1 view|%1 views
| Free forum by Nabble | Edit this page |