xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Fwd: Re: Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs!
Date: Mon, 01 Mar 2010 18:17:46 +0100	[thread overview]
Message-ID: <4B8BF6BA.1060203@redhat.com> (raw)

On 03/01/2010 03:25 PM, Ian Campbell wrote:

>  On Mon, 2010-03-01 at 14:21 +0000, Michal Novotny wrote:
>
>>  Hi,
>>  well, I tried reverting this patch and both applying and not applying
>>  the new one from Ian but there is still kernel oops. Error image is
>>  attached. Also, I tried disabling CONFIG_SPARSE_IRQ (i.e. setting this
>>  to n) but no luck. Still the same issue.
>>
>  This isn't the same panic, this is failing to mount a root filesystem.
>  Probably a missing driver modules or an incorrect initrd or something
>  like that.
>
>  Ian.
>
>
>
Yeah, I can see that now but this root was working fine with
kernel-2.6.18.8 for xen so may be a missing driver is the real issue
because it's after initrd already and even booting to single user mode
or emergency mode is not working so this seems that is cannot see the
root because of missing driver but the driver should be there I guess
(this should be a SAS drive). Well, needs a little more investigation.

Thanks,
Michal

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

             reply	other threads:[~2010-03-01 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 17:17 Michal Novotny [this message]
2010-03-02  9:19 ` Fwd: Re: Kernel 2.6.31.6 pv_ops freeze on start, No available IRQ to bind to, increase nr_irqs! Ian Campbell

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=4B8BF6BA.1060203@redhat.com \
    --to=minovotn@redhat.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 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).