From: out law <outlaw45k@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Kernel Panic, Call trace
Date: Fri, 30 Apr 2010 12:48:47 +0200 [thread overview]
Message-ID: <t2tc37cdc671004300348h46de06d1u2b7ae20760d33250@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1102 bytes --]
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!
Pid: 0, comm: swapper Not tainted 2.6.32.9-7.pvps0.qubes.x86_64 #1
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
[-- Attachment #1.2: Type: text/html, Size: 1275 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-04-30 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 10:48 out law [this message]
2010-05-04 18:01 ` Kernel Panic, Call trace 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=t2tc37cdc671004300348h46de06d1u2b7ae20760d33250@mail.gmail.com \
--to=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).