From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Kernel Panic, Call trace Date: Tue, 4 May 2010 14:01:05 -0400 Message-ID: <20100504180105.GB32012@phenom.dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: out law Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Apr 30, 2010 at 12:48:47PM +0200, out law wrote: > amd 64 3500+ > radeon x1650 pro > asus a8n sli deluxe > > > > > Already setup the GSI :9 > zen: acpi sci 9 > ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) > ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 14 high edge) > console: colour VGA+ 80x25 > concole [tty0] enabled > allocated 19660800 bytes of page_cgroup > please try 'cgroup_disable=memory' option if you dont want memeory cgroups > installing xen timer for CPU0 > Kernel Panic - no syncing: No available IRQ to bind to: increase nr_irqs! You need to provide the full serial log. http://wiki.xensource.com/xenwiki/XenSerialConsole > > Pid: 0, comm: swapper Not tainted 2.6.32.9-7.pvps0.qubes.x86_64 #1 Uhh, that looks to be qubes kernel. No idea if there are changes in that kernel - you might want to send this e-mail to qubes mailing list. > Call trace: > [] panic+0x7a/0x133 > [] find_unbound_irq+0x7a/0x81 > [] bind_virq_to_irq+0x7d/0x128 > [] ? xen_timer_interrupt+0x0/0x17b > [] bind_virq_to_irqhandler+0x24x0x5a > [] xen_setup_timer+0x59/0xa5 > [] xen_time_init+0xb7/0xc0 > [] x86_late_time_init+0xa/0x11 > [] start_kernel+0x312/0x3b6 > [] x86_64_start_resevations+0xac/0xb0 > [] xen_start_kernel+0x634/0x63b