From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Novotny 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 Message-ID: <4B8BF6BA.1060203@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "'xen-devel@lists.xensource.com'" List-Id: xen-devel@lists.xenproject.org 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, RHCE Virtualization Team (xen userspace), Red Hat