xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Fantu <fantonifabio@tiscali.it>
Cc: xen-devel@lists.xensource.com
Subject: Re: Kernel 2.6.31.6 pv_ops freeze on start
Date: Wed, 13 Jan 2010 10:39:25 -0500	[thread overview]
Message-ID: <20100113153925.GA10380@phenom.dumpdata.com> (raw)
In-Reply-To: <27143153.post@talk.nabble.com>

On Wed, Jan 13, 2010 at 03:05:53AM -0800, Fantu wrote:
> 
> In attachment file output of lspci -vv do on some server (Dell T610 bios
> 1.3.6) with hardy with xen 3.3 from backports
> http://old.nabble.com/file/p27143153/lspcivv.log lspcivv.log 

In your vmlinuz argument line:
root=LABEL=root-raid ro console=hvc0 console=com2,vga earlyprintk=xen

The second console=com2,vga should not be there (that syntax is only
applicable to the Xen command line).

Also add these extra arguments to the Linux command line:
initcall_debug debug loglevel=10

That should out a bit in figuring out where you are stuck.

  reply	other threads:[~2010-01-13 15:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 13:33 Kernel 2.6.31.6 pv_ops freeze on start Fantu
2010-01-07 13:37 ` Pasi Kärkkäinen
2010-01-07 13:43   ` Fantu
2010-01-07 14:01     ` Pasi Kärkkäinen
2010-01-07 17:04   ` Fantu
2010-01-07 21:14     ` Pasi Kärkkäinen
2010-01-08 14:16       ` Fantu
2010-01-21 22:04         ` Jeremy Fitzhardinge
2010-02-16 13:56           ` Fantu
2010-02-16 14:27             ` Pasi Kärkkäinen
2010-02-16 17:49               ` Fantu
2010-02-16 18:31                 ` Pasi Kärkkäinen
2010-02-24  8:39                 ` Fantu
2010-02-24  8:59                   ` Pasi Kärkkäinen
2010-02-24 13:23                     ` Fabio Fantoni
2010-02-26 13:32                   ` Fantu
2010-02-26 14:42                     ` Pasi Kärkkäinen
2010-02-26 15:58                       ` Fantu
2010-03-01  9:54                       ` Fantu
2010-03-01 10:21                         ` Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs! Pasi Kärkkäinen
2010-03-01 10:27                           ` Ian Campbell
2010-03-01 10:32                             ` Ian Campbell
2010-03-01 10:45                               ` Fantu
2010-03-01 11:05                                 ` Ian Campbell
2010-03-01 15:34                                   ` Fantu
2010-03-02  7:09                                     ` Zhang, Xiantao
2010-03-05 10:30                                       ` Fantu
2010-03-05 15:41                                         ` Fantu
2010-04-14 11:46                                           ` Fantu
2010-04-19  9:25                                             ` Fantu
2010-04-19 13:52                                               ` Boot hands - need sync serial console to help Konrad Rzeszutek Wilk
2010-01-13  8:41       ` Kernel 2.6.31.6 pv_ops freeze on start Fantu
2010-01-13  9:12         ` Pasi Kärkkäinen
2010-01-13 11:05           ` Fantu
2010-01-13 15:39             ` Konrad Rzeszutek Wilk [this message]
2010-01-15  7:00               ` Fantu
2010-01-15  7:34                 ` Pasi Kärkkäinen
2010-01-15 17:01                 ` 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=20100113153925.GA10380@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=fantonifabio@tiscali.it \
    --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).