xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Crash on boot with 2.6.37-rc8-git3
Date: Thu, 6 Jan 2011 09:56:04 -0500	[thread overview]
Message-ID: <20110106145604.GA3404@dumpdata.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1101052302270.24673@vega1.dur.ac.uk>

On Wed, Jan 05, 2011 at 11:11:03PM +0000, M A Young wrote:
> On Wed, 5 Jan 2011, Konrad Rzeszutek Wilk wrote:
> 
> >Ahh, I hit this. Can you try 'stable/bug-fixes' branch of mine?
> >It has "xen/irq: Don't fall over when nr_irqs_gsi > nr_irqs." patch
> >which will fix the below problem you are seeing.
> >
> >But I am not sure if it fixes the problem you are having with hardware?
> 
> That fixes the kvm boot, but unfortunately booting directly on the
> hardware doesn't. Incidentally it is definitely turning debug
> options off that trigger the crash, as I realized I was building a
> kernel-debug package as well as a kernel package from the same

Ok, I think we need a serial output. I don't remember if you said that
your docking station has a serial port or not.

If the docking station does not, this card ought to do the trick:

http://www.newegg.com/Product/Product.aspx?Item=N82E16839328018&Tpk=SDEXP15005

You can use under Xen as a normal PCI type serial card. For details:

http://wiki.xensource.com/xenwiki/XenSerialConsole

> source RPM, and it boots with the debug kernel but not the ordinary
> kernel.

> 
> 	Michael Young

  reply	other threads:[~2011-01-06 14:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 22:01 Crash on boot with 2.6.37-rc8-git3 M A Young
2011-01-05 15:43 ` Konrad Rzeszutek Wilk
2011-01-05 23:11   ` M A Young
2011-01-06 14:56     ` Konrad Rzeszutek Wilk [this message]
2011-01-07  0:37       ` M A Young
2011-01-07 19:18         ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2011-01-07 20:34 M A Young
2011-01-07 21:23 ` Konrad Rzeszutek Wilk
2011-01-08  0:10   ` M A Young
2011-01-10 18:42     ` Konrad Rzeszutek Wilk
2011-01-10 21:43       ` M A Young
2011-01-16 20:48       ` M A Young
2011-01-16 20:56         ` Keir Fraser
2011-01-18  0:52       ` M A Young
2011-01-19 22:54         ` M A Young
2011-01-20 19:24           ` Konrad Rzeszutek Wilk
2011-01-20 22:39             ` M A Young
2011-01-21 15:27               ` Konrad Rzeszutek Wilk
2011-01-21 21:43                 ` M A Young
2011-01-24 14:14                   ` Konrad Rzeszutek Wilk
2011-01-24 23:12                     ` M A Young
2011-01-25 12:03                       ` Stefano Stabellini
2011-01-25 13:24                         ` Ian Campbell
2011-01-25 13:31                           ` Stefano Stabellini
2011-01-25 13:45                             ` Ian Campbell
2011-01-25 15:19                               ` Stefano Stabellini
2011-01-25 15:52                                 ` Konrad Rzeszutek Wilk
2011-01-25 15:56                                   ` Stefano Stabellini
2011-01-25 16:05                                     ` M A Young
2011-01-24 19:04                   ` Stefano Stabellini
2011-01-25  0:22                     ` M A Young

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=20110106145604.GA3404@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=m.a.young@durham.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).