From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: out law <outlaw45k@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Kernel Panic, Call trace
Date: Tue, 4 May 2010 14:01:05 -0400 [thread overview]
Message-ID: <20100504180105.GB32012@phenom.dumpdata.com> (raw)
In-Reply-To: <t2tc37cdc671004300348h46de06d1u2b7ae20760d33250@mail.gmail.com>
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:
> [<ffffffff814555ad>] panic+0x7a/0x133
> [<ffffffff8129d3fd>] find_unbound_irq+0x7a/0x81
> [<ffffffff8129d481>] bind_virq_to_irq+0x7d/0x128
> [<ffffffff8100ee05>] ? xen_timer_interrupt+0x0/0x17b
> [<ffffffff8129d8d7>] bind_virq_to_irqhandler+0x24x0x5a
> [<ffffffff8100edb9>] xen_setup_timer+0x59/0xa5
> [<ffffffff8181ecf1>] xen_time_init+0xb7/0xc0
> [<ffffffff8181f4e8>] x86_late_time_init+0xa/0x11
> [<ffffffff8181ad00>] start_kernel+0x312/0x3b6
> [<ffffffff8181a2c1>] x86_64_start_resevations+0xac/0xb0
> [<ffffffff8181de5c>] xen_start_kernel+0x634/0x63b
prev parent reply other threads:[~2010-05-04 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 10:48 Kernel Panic, Call trace out law
2010-05-04 18:01 ` Konrad Rzeszutek Wilk [this message]
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=20100504180105.GB32012@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=outlaw45k@gmail.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).