Bug#524571: linux-image-2.6.26-2-xen-686 crashs as Dom0
Package: linux-image-2.6.26-2-xen-686
Version: 2.6.26-15
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-6-xen-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-2-xen-686 depends on:
ii initramfs-tools 0.92o tools for generating an
initramfs
ii linux-modules-2.6.26-2-xen-68 2.6.26-15 Linux 2.6.26 modules on i686
Versions of packages linux-image-2.6.26-2-xen-686 recommends:
ii libc6-xen 2.7-18 GNU C Library: Shared
libraries [X
Versions of packages linux-image-2.6.26-2-xen-686 suggests:
ii grub 0.97-47lenny2 GRand Unified Bootloader
(Legacy v
pn linux-doc-2.6.26 <none> (no description available)
-- no debconf information
I've updatetedt my xen system from etch to lenny. Running
2.6.26-2-xen-686 causes the Dom0 to crash after a few hours or days. The
System runs stable using the 2.6.18-6-xen-686 from etch.
The only imnformation that I have, is the console output after the crash.
With Kernel 2.6.26-1-xen:
23137.857500] Pid: 0, comm: swapper Not tainted (2.6.26-1-xen-686 #1)
[23137.857529] EIP: 0061:[<c0105f60>] EFLAGS: 00010246 CPU: 1
[23137.857561] EIP is at xen_safe_halt+05xa5/0xb3
[23137.857588] EAX: 00000001 EXB: 00000001 ECX: 00000000 EDX: cf855f90
[23137.857617] ESI: 00000001 EDI: 00000001 EBP: 00000000 ESP; cf855f88
[23137.857645] DS: 0000 ES: 007b FS: 00d8 GS: 0000 SS: 0069
[23137.857674] Process swapper (pid: 0, ti=cf854000 task=cf84d0c0
task.ti=cf854000)
[23137.857702] Stack: ffffffff 00000001 8a66a95d 00001504 00000000
00000000 ffffffff c01028ab
[23137.857814] c0102810 00000000 00000000 00000000 00000000
00000000 00000000 00000000
[23137.857925] 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000
[23137.858036] Call Trace:
[23137.858087] [<c01028ab>] xen_idle+0x1b/0x46
[23137.858123] [<c0102810>] cpu_idle+0xa8/0xc0
[23137.858170] =======================
[23137.858195] Code: 89 44 24 08 c7 44 24 10 00 00 00 00 e8 ba b3 ff ff
85 c0 74 04 0f 0b eb fe bb 01 00 00 00 89 c1 e8 46 b4 ff ff 64 a1 04 b0
3b c0 >f0> 0f b3 05 00 26 3d c0 83 c4 14 5b 5e c3 55 57 56 53 89 c3 83
[23137.859768] EIP: [<c0105f60>] xen_safe_halt+0xa5/0xb3 SS:ESP
0069:cf855f88
[23137.860924] ---[end trace 5a85f119b7b5c3de ]---
[23137.861062 Kernel panic - not syncing: Attempted to kill the idle task!
With Kernel 2.6.26-2-xen:
[11823.755788] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
[11823.755825] Process swaper (pid: 0, ti=c0388000 task=c035a1a0
task.ti=c0388000)
[11823.755861] Stack: c023cb20 00000000 00000000 00000018 00000018
c0378b20 c0378b20 00000018
[11823.756009] ce39cbc0 c014aa8e 00000900 c0378b20 00000000
00000018 c0105b08 00000013
[11823.756158] 00000000 0000001f 00000000 c023d33b 00000000
00000001 f5656000 f5656000
[11823.756309] Call Trace:
[11823.756362] [<c023cb20>] startup_pirq+0xe6/0xef
[11823.756430] [<c014aa8e>] handle_level_irg+0xc9/0xed
[11823.756489] [<c0105b08>] do_IRQ+0x4d/0x65
[11823.756546] [<c023d33b>] evtchn_do_upcall+0xfa/0x191
[11823.756546] [<c0104136>] hypervisor_callback+0x46/0x4e
[11823.756546] [<c0105f5a>] xen_safe_halt+0x9f/0xb3
[11823.756546] [<c01028ab>] xen_idle+0x1b/0x46
[11823.756546] [<c0102810>] cpu_idle+0xa8/0xc0
[11823.756546] =======================
[11823.756546] Code: cc cc cc cc b8 20 00 00 00 cd 82 c3 cc cc cc cc cc
cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 21 00 00 00 cd
82 >c3> cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
[11823.756546] EIP: [<c0101427>] 0xc0101427 SS:ESP 0069:c0389f0c
[11823.756546] Kernel panic - not syncing: Fatal exception in interrupt
If these are to few information, please tell me how I could get more
information for you.
Another strange behaviour:
Kernel 2.6.26-2-xen
lenny:~# ping 192.168.10.53
PING 192.168.10.53 (192.168.10.53) 56(84) bytes of data.
64 bytes from 192.168.10.53: icmp_seq=1 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=2 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=3 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=4 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=5 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=6 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=7 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=8 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=9 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=10 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=11 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=12 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=13 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=14 ttl=128 time=0.000 ms
64 bytes from 192.168.10.53: icmp_seq=15 ttl=128 time=0.000 ms
^C
--- 192.168.10.53 ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14000ms
rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms
Kernel 2.6.18-6-xen
lenny:~# ping 192.168.10.53
PING 192.168.10.53 (192.168.10.53) 56(84) bytes of data.
64 bytes from 192.168.10.53: icmp_seq=1 ttl=128 time=0.406 ms
64 bytes from 192.168.10.53: icmp_seq=2 ttl=128 time=0.500 ms
64 bytes from 192.168.10.53: icmp_seq=3 ttl=128 time=0.336 ms
64 bytes from 192.168.10.53: icmp_seq=4 ttl=128 time=0.301 ms
64 bytes from 192.168.10.53: icmp_seq=5 ttl=128 time=0.266 ms
64 bytes from 192.168.10.53: icmp_seq=6 ttl=128 time=0.345 ms
64 bytes from 192.168.10.53: icmp_seq=7 ttl=128 time=0.312 ms
64 bytes from 192.168.10.53: icmp_seq=8 ttl=128 time=0.403 ms
64 bytes from 192.168.10.53: icmp_seq=9 ttl=128 time=0.365 ms
64 bytes from 192.168.10.53: icmp_seq=10 ttl=128 time=0.453 ms
64 bytes from 192.168.10.53: icmp_seq=11 ttl=128 time=0.293 ms
64 bytes from 192.168.10.53: icmp_seq=12 ttl=128 time=0.384 ms
64 bytes from 192.168.10.53: icmp_seq=13 ttl=128 time=0.346 ms
64 bytes from 192.168.10.53: icmp_seq=14 ttl=128 time=0.309 ms
64 bytes from 192.168.10.53: icmp_seq=15 ttl=128 time=0.282 ms
^C
--- 192.168.10.53 ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14000ms
rtt min/avg/max/mdev = 0.266/0.353/0.500/0.065 ms
best regards
S. Pfeffer
Reply to: