Re: LWLock deadlock and gdb advice

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 29, 2015 at 9:26 AM, Andres Freund <span
dir="ltr"><<ahref="mailto:andres@anarazel.de" target="_blank">andres@anarazel.de</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2015-07-29
09:23:32-0700, Jeff Janes wrote:<br /><span class="">> On Tue, Jul 28, 2015 at 9:06 AM, Jeff Janes <<a
href="mailto:jeff.janes@gmail.com">jeff.janes@gmail.com</a>>wrote:<br /> > I've reproduced it again against
commitb2ed8edeecd715c8a23ae462.<br /> ><br /> > It took 5 hours on a 8 core "Intel(R) Xeon(R) CPU E5-2650".<br />
><br/> > I also reproduced it in 3 hours on the same machine with both JJ_torn_page<br /> > and JJ_xid set to
zero(i.e. turned off, no induced crashes), so the<br /> > fault-injection patch should not be necessary to get the
issue..<br/><br /></span>Hm, that's a single socket or dual socket E5-2650 system? That CPU<br /> itself has 8 cores,
andcan work in a dual socket system, that's why I<br /> ask.<br /></blockquote></div><br /></div><div
class="gmail_extra">Itis a virtual machine, and I think a property of the VM software is that any given virtual machine
canonly run on one socket of the underlying hardware.  The real machine is dual socket, though.</div><div
class="gmail_extra"><br/></div><div class="gmail_extra">Cheers,</div><div class="gmail_extra"><br /></div><div
class="gmail_extra">Jeff</div></div>