All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Olaf Hering <olaf@aepfle.de>,
	xen-devel@lists.xen.org
Subject: Re: sudden hang on boot on AMD Notebook
Date: Wed, 1 Apr 2015 13:28:35 -0400	[thread overview]
Message-ID: <20150401172835.GA4429@l.oracle.com> (raw)
In-Reply-To: <1427900227.13425.18.camel@citrix.com>

On Wed, Apr 01, 2015 at 03:57:07PM +0100, Ian Campbell wrote:
> On Wed, 2015-04-01 at 15:39 +0100, Andrew Cooper wrote:
> > On 01/04/15 14:35, Olaf Hering wrote:
> > > On Mon, Mar 30, Andrew Cooper wrote:
> > >
> > >> On 30/03/15 13:14, Olaf Hering wrote:
> > >>> Just last week I was running staging to test pvscsi on this HP ProBook
> > >>> 6555b, since around Wednesday I think. But todays staging fails to boot.
> > >>> So I started a bisect in xen/, but every attempt to boot xen.gz results
> > >>> in a hang at the same place. Even going back to the state of 4.5.0.
> > >>> Any idea what may cause this hang, and how I can debug it further?
> > >> This smells like an external factor.  Have you changed compiler in that
> > >> time, altered the BIOS settings or updated the firmware?
> > > Nothing like that. I carried the thing around for a week, and started to
> > > run Xen during that time. Since Saturday its back in its usual place and
> > > position. I think I ran Xen on that day, but the bootlogs have no
> > > indication if I really did.
> > >
> > > Yesterday after some poking around in the firmware and running the
> > > selftests I was able to boot Xen again. But today it failed again.
> > >
> > >> Are you able to use the console debugkeys once it gets into this state?
> > > No, it does not react to anything. I think a triple CTRL-A and 'h'
> > > should print the help text? I see the cursor blinking on the display,
> > > not sure if thats an indication that Xen is still alive.
> > 
> > The keyhandlers should be set up by the point, although most of them are
> > deferred to tasklets.  Try the 'i' key which will run synchronously in
> > serial rx irq context.
> 
> Key handlers are only available via serial, I think, and not VGA which
> it sounds like what Olaf is looking at.

You can also use the USB EHCI debug port. It works great on laptops.

> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2015-04-01 17:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 12:14 sudden hang on boot on AMD Notebook Olaf Hering
2015-03-30 12:27 ` Andrew Cooper
2015-04-01 13:35   ` Olaf Hering
2015-04-01 14:39     ` Andrew Cooper
2015-04-01 14:57       ` Ian Campbell
2015-04-01 15:23         ` Olaf Hering
2015-04-02  6:05           ` Olaf Hering
2015-04-01 17:28         ` Konrad Rzeszutek Wilk [this message]
2015-04-02  6:15           ` Olaf Hering
2015-04-02 19:03             ` Konrad Rzeszutek Wilk
2015-04-07  9:40 ` Olaf Hering
2015-04-07 13:51   ` Konrad Rzeszutek Wilk
2015-04-08  7:09     ` Olaf Hering
2015-04-08 14:07       ` Konrad Rzeszutek Wilk

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=20150401172835.GA4429@l.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.org \
    /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.