From: Markus Ingalsuo <markus.ingalsuo@iki.fi>
To: xen-devel@lists.xensource.com
Subject: Xen 3.0.2 Kernel panic && reboot
Date: Wed, 18 Oct 2006 14:33:26 +0300 [thread overview]
Message-ID: <45361106.2030804@iki.fi> (raw)
Experienced horrible crashes with Xen 3.0.2 and
linux-image-2.6.17-2-xen-k7. This is a debian bugreport but thought I'd
post it here to expose it to the right audience..
Screenshot-photos of the panic can be found at
http://www.osp.fi/xen1.jpg , http://www.osp.fi/xen2.jpg and
http://www.osp.fi/xen3.jpg
//Markus
Package: linux-image-2.6.17-2-xen-k7
Version: 2.6.17-9
Severity: critical
Justification: breaks the whole system
Xen 3.0 unstable in debian etch crashes horribly and reboots the system when booting virtual domains with
linux-image-2.6.17-2-xen-k7 kernel. Took a photo of the panic message and lost some values in the process.
Below is what could be salvaged:
esi: 00000000 edi: 05555000 ebp: 00000104 esp: b0379e0c
ds: 007b es: 007b ss: 0069
Process xenwatch (pid: 7, threadinfo=b0378000 task=b0daba90)
Stack: <0>93e42f51 b0379eac b1c4e080 00000000 b0daba90 b0dab580 b1c4e940 b0da????
0
b037bf58 b0278c25 b0379e94 0000000a b0a61740 00000000 0000000???
00000104 b013444a b0379eac 00004100 b02fd380 00000104 b0a6 1740 b013450???
Call Trace:
<b0278c25> schedule+0x5b9/0x692 <b013444a> handle_IRQ_event+0x43/0x83
<b0134507> __do_IRQ+0x7d/0xce <b0106097> do_IRQ+0x1a/0x25
<b0200ddd> evtchn_do_upcall+0x64/0x9b <b01049dd> hypervisor_callback+0x3d/0????
<b020b03f> netif_map+0x165/0x25e <b020a63f> maybe_connect+0x59/0x209
<b020a66a> maybe_connect+0x84/0x209 <b020440c> xenbus_read_driver_state+0x1??????
<b02068c3> otherend_changed+0x4f/0x54 <b0205981> xenwatch_thread+0x???????
<b020507d> xenwatch_handle_callback+0x12/0x44 <b0205185> xenwatch_thread+0x???????
<b0129a6b> autoremove_wake_function+0x0/0x2d <b01299aa> kthread0+x9f/0xcb
<b012990b> kthread+0x0/0xcb <b0102991> kernel_thread_helper+0x5/0xb
Code: 50 34 75 1e 8b 0d 50 fb 32 b0 89 d0 d3 e8 85 c0 74 08 8b 15 0c d4 34 b0 ??
08 a1 4c fb 32 b0 8b 14 90 c1 e2 0c 8d ba 00 00 00 b0 <8b> 87 04 0c 00 00 8b ??
00 0c 00 00 89 44 24 08 f0 83 04 24 00
EIP: [<b02035c0>] handle_input+0x43/0xf7 SS:ESP 0069:b0379e0c
<0>Kernel panic - not syncing: Fatal exception in interrupt
This is with ACPI on, same result with ACPI off.
lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)
cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 2600+
stepping : 0
cpu MHz : 1908.997
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts
bogomips : 4773.79
Memtest86 has been run with success. No errors found.
Domains:
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 967 1 r----- 39.9
debian1 1 256 1 -b---- 71.9
johnny_osp 2 256 1 -b---- 25.4
Two virtual domains can be booted but a third causes kernel panic and reboot.
free -m:
total used free shared buffers cached
Mem: 967 300 666 0 14 210
-/+ buffers/cache: 76 890
Swap: 1898 0 1898
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-xen-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.17-2-xen-k7 depends on:
ii initramfs-tools 0.82 tools for generating an initramfs
ii linux-modules-2.6.17-2-xen-k7 2.6.17-9 Linux 2.6.17 modules on AMD K7
Versions of packages linux-image-2.6.17-2-xen-k7 recommends:
ii libc6-xen 2.3.6.ds1-4 GNU C Library: Shared libraries [X
-- no debconf information
reply other threads:[~2006-10-18 11:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45361106.2030804@iki.fi \
--to=markus.ingalsuo@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.