WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1535] panic: iret exception

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1535] panic: iret exception
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 19 Nov 2009 08:43:22 -0800
Delivery-date: Thu, 19 Nov 2009 08:43:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1535-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1535





------- Comment #6 from micah@xxxxxxxxxx  2009-11-19 08:43 -------
Yesterday we completely swapped the entire machine, where this was
happening, with another identical machine. We just took the disks out of
the one that had been crashing and put them into this other machine.

Today, on the new hardware, it crashed again. Can someone please clarify for me
what kernel I should try, as per my response in comment #2?

Here it is:

[64631.057499] iret exception: 0000 [#1] SMP
[64631.057567] Modules linked in: xt_tcpudp xt_physdev iptable_filter
ip_tables x_tables tun netloop bridge ipv6 loop serio_raw psmouse pcspkr
i2c_i801 i2c_core intel_rng rng_core container button e7xxx_edac shpchp
pci_hotplug edac_core joydev evdev ext3 jbd mbcache serpent xts gf128mul
dm_crypt crypto_blkcipher dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod
ide_cd_mod cdrom ide_disk ata_generic libata dock ide_pci_generic usbhid
hid ff_memless floppy aic79xx scsi_transport_spi scsi_mod piix ide_core
uhci_hcd usbcore e1000 thermal processor fan thermal_sys [last unloaded:
scsi_wait_scan]
[64631.058548]
[64631.058548] Pid: 0, comm: swapper Not tainted (2.6.26-2-xen-686 #1)
[64631.058548] EIP: 0061:[<c0101427>] EFLAGS: 00000086 CPU: 0
[64631.058548] EIP is at 0xc0101427
[64631.058548] EAX: 00000000 EBX: 0000000c ECX: c0389f1c EDX: f5656000
[64631.058548] ESI: 00000037 EDI: ec4975e0 EBP: c03796f0 ESP: c0389f0c
[64631.058548]  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0069
[64631.058548] Process swapper (pid: 0, ti=c0388000 task=c035a1a0
task.ti=c0388000)
[64631.058548] Stack: c023cf54 00000037 ec4975e0 00000000 00000037 c03796c0
c03796c0 00000037
[64631.058548]        ec4975e0 c014aa96 000014a0 c03796c0 00000000 00000037
c0105b00 00000000
[64631.058548]        00000001 0000001f 00000000 c023d76f 00000020 00000002
f5656000 f5656000
[64631.058548] Call Trace:
[64631.058548]  [<c023cf54>] startup_pirq+0xe6/0xef
[64631.058548]  [<c014aa96>] handle_level_irq+0xc9/0xed
[64631.058548]  [<c0105b00>] do_IRQ+0x4d/0x65
[64631.058548]  [<c023d76f>] evtchn_do_upcall+0xfa/0x191
[64631.058548]  [<c010412c>] hypervisor_callback+0x3c/0x44
[64631.058548]  [<c0105f52>] xen_safe_halt+0x9f/0xb3
[64631.058548]  [<c01028ab>] xen_idle+0x1b/0x46
[64631.058548]  [<c0102810>] cpu_idle+0xa8/0xc0
[64631.058548]  =======================
[64631.058548] 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 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
[64631.058548] EIP: [<c0101427>] 0xc0101427 SS:ESP 0069:c0389f0c
[64631.058548] Kernel panic - not syncing: Fatal exception in interrupt
(XEN) Domain 0 crashed: 'noreboot' set - not rebooting.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs