All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Roger Cruz <roger.cruz@virtualcomputer.com>,
	Tim Deegan <Tim.Deegan@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: State of current Xen debugger
Date: Tue, 14 Sep 2010 08:19:24 -0700 (PDT)	[thread overview]
Message-ID: <b409f470-184d-4119-9e27-d944a3d57b5e@default> (raw)
In-Reply-To: <EACA7CA90354A849B1315959042A052C26F50B@BE24.exg4.exghost.com>


[-- Attachment #1.1: Type: text/plain, Size: 2935 bytes --]

A couple of thoughts:

 

Have you tried max_cstate=0 (as a Xen boot option)?

 

Also, you didn't say what version of Xen you are using but playing around with hpet_broadcast (enabling it or force-disabling it as below) might be worth a try.

 

http://lists.xensource.com/archives/html/xen-devel/2010-09/msg00556.html

 

From: Roger Cruz [mailto:roger.cruz@virtualcomputer.com] 
Sent: Tuesday, September 14, 2010 8:56 AM
To: Tim Deegan
Cc: xen-devel@lists.xensource.com
Subject: RE: [Xen-devel] State of current Xen debugger

 

Hi Tim,  good to hear from you again

I had a pretty good inkling that one of you hardcore developers would say that :-)  Yes, it is pretty well wedged.  I can cause the problem more rapidly by dropping to a single CPU.  When the hang happens, the Xen console is completely dead.  None of the special keys work. 

I do have hopes a BIOS upgrade could fix this as a last resort but I want to see if at least I can understand the problem.  We have a few different machines that are exhibiting similar symptoms so I have to see if I can find a work-around without requiring every user to upgrade their BIOS :-(

Just in case, what debugger have you been using?  Are there recent instructions on how to set it up that you can point me to?

Thanks
Roger


-----Original Message-----
From: Tim Deegan [mailto:Tim.Deegan@citrix.com]
Sent: Tue 9/14/2010 10:30 AM
To: Roger Cruz
Cc: xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] State of current Xen debugger

Hi,

At 15:22 +0100 on 14 Sep (1284477779), Roger Cruz wrote:
> I am trying to debug a problem where the hypervisor is hanging hard.
> Not even the NMI watchdog is triggering a reboot.  So I wanted to hook
> up a debugger.

Sorry to bring a counsel of despair but if the NMI watchdog isn't
working then your chances of getting a working debugger are slim.  It's
likely that at least one CPU is very very stuck.  Does the 'd' debug key
work on the serial line when the machine is wedged?

On a more cheerful note, I've twice seen hard hangs like this that
turned out to be hardware issues, fixable with BIOS upgrades.

Cheers,

Tim.

> What is the state of the current debuggers out there?
> Any input on how I should set it up (kdb, gdb, etc) and pointers to a
> good wiki page are much appreciated.  I did perform a Google search
> and found some links but I want to hear from the current developers as
> to what is most stable and useful for debugging this type of hard
> hang.  I only have a serial port PCI-express card to use as the laptop
> has no built in port.

--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.851 / Virus Database: 271.1.1/3119 - Release Date: 09/14/10 02:35:00

[-- Attachment #1.2: Type: text/html, Size: 6897 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-09-14 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 14:22 State of current Xen debugger Roger Cruz
2010-09-14 14:30 ` Tim Deegan
2010-09-14 14:56   ` Roger Cruz
2010-09-14 15:19     ` Dan Magenheimer [this message]
2010-09-14 15:54       ` Roger Cruz
2010-09-15 14:19         ` Roger Cruz
2010-09-28 15:21         ` Roger Cruz
2010-09-28 15:30           ` Keir Fraser
2010-09-28 15:40             ` Roger Cruz
2010-09-28 17:06               ` Keir Fraser
2010-09-28 17:14                 ` Roger Cruz
2010-09-14 15:20     ` Tim Deegan
2010-09-14 16:08       ` Roger Cruz

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=b409f470-184d-4119-9e27-d944a3d57b5e@default \
    --to=dan.magenheimer@oracle.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=roger.cruz@virtualcomputer.com \
    --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.