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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-bugs] [Bug 1428] New: dom0 crash

from [bugzilla-daemon] [Permanent Link][Original]
To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1428] New: dom0 crash
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 12 Mar 2009 13:25:39 -0700
Delivery-date: Thu, 12 Mar 2009 13:27:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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=1428

           Summary: dom0 crash
           Product: Xen
           Version: 3.0 (general)
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: xenbugs@xxxxxxxxxxxxxx


running 3.3.1 xend (from gitco.de repo) and a locally patched centos 5.2 64bit
dom0 (and also several 5.2 32bit domU, one with PCI passthru)

I get crashes after a few days of uptime, previously this was due to an "IRQ
nobody cared" which seems to have be "cured" by noirqdebug options.

Now dom0 has crashed again as follows

stack segment: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:1c.2/0000:04:00.0/irq
CPU 0
Modules linked in: pciback xt_physdev netloop netbk blktap blkbk ipt_MASQUERADE
iptable_nat ip_nat xt_state ip_conntrack nfnetlink ipt_REJECT xt_tcpudp
iptable_filter ip_tables x_tables bridge ipv6 xfrm_nalgo crypto_api autofs4
eeprom ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp
libiscsi scsi_transport_iscsi nls_utf8 loop dm_multipath raid456 xor video sbs
backlight i2c_ec button battery asus_acpi ac parport_pc lp parport
snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event
snd_seq snd_seq_device i2c_i801 sr_mod sata_mv snd_pcm_oss snd_mixer_oss cdrom
video_buf compat_ioctl32 ir_kbd_i2c snd_pcm snd_timer i2c_core ata_generic
shpchp floppy snd soundcore snd_page_alloc ir_common videodev v4l1_compat
serio_raw sky2 v4l2_common pcspkr serial_core sg dm_snapshot dm_zero dm_mirror
dm_mod usb_storage pata_marvell ahci libata sd_mod scsi_mod raid1 ext3 jbd
uhci_hcd ohci_hcd ehci_hcd
Pid: 17717, comm: 0logwatch Not tainted 2.6.18-92.1.22.el5.centos.plus.jab.1xen
#1
RIP: e030:[<ffffffff80209c3e>]  [<ffffffff80209c3e>] __d_lookup+0xdb/0xff
RSP: e02b:ffff88019899bc18  EFLAGS: 00010206
RAX: 6901bc6278085a33 RBX: ffff8801dd54aed0 RCX: 0000000000000014
RDX: 00000000000f326e RSI: ffff88019899bcb8 RDI: ffff8801dd4b99c0
RBP: 6901bc6278085a33 R08: ffff88019899bbc8 R09: 0000000000000000
R10: ffff88019899bc28 R11: 0000000000000048 R12: ffff8801dd4b99c0
R13: ffff88019899bcb8 R14: 0000000089ba569b R15: 0000000000000006
FS:  00002ba6f4ac6220(0000) GS:ffffffff805ad000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process 0logwatch (pid: 17717, threadinfo ffff88019899a000, task
ffff8801e8d467e0)
Stack:  ffff88019ed6e03b  00000000000041ed  0000000000000000  ffff8801c3eee700
 ffff8801ee8ec080  ffff88019899be48  ffff88019899bcb8  ffffffff8020d129
 0000000000000000  ffff88019899bcc8
Call Trace:
 [<ffffffff8020d129>] do_lookup+0x2c/0x1e6
 [<ffffffff8020a008>] __link_path_walk+0x3a6/0xf42
 [<ffffffff8020eb44>] link_path_walk+0x5c/0xe5
 [<ffffffff802673f7>] do_page_fault+0xfae/0x12e0
 [<ffffffff8020c8eb>] _atomic_dec_and_lock+0x39/0x57
 [<ffffffff8020cf81>] do_path_lookup+0x270/0x2e8
 [<ffffffff80212c07>] getname+0x15b/0x1c1
 [<ffffffff802241ae>] __user_walk_fd+0x37/0x4c
 [<ffffffff802290b2>] vfs_stat_fd+0x1b/0x4a
 [<ffffffff802673f7>] do_page_fault+0xfae/0x12e0
 [<ffffffff8020c8eb>] _atomic_dec_and_lock+0x39/0x57
 [<ffffffff80223f54>] sys_newstat+0x19/0x31
 [<ffffffff80260295>] tracesys+0x47/0xb6
 [<ffffffff802602f9>] tracesys+0xab/0xb6

Code: 48 8b 45 00 0f 18 08 48 8d 5d e8 44 39 73 30 75 e6 e9 70 ff
RIP  [<ffffffff80209c3e>] __d_lookup+0xdb/0xff
 RSP <ffff88019899bc18>
 <0>Kernel panic - not syncing: Fatal exception
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

If it's of significance, PCI device 00:1c.0 as mentioned in the last sysfs
message is a PCI bridge, but not the bridge that is "in front" of the PCI
devices passed through into the domU, however the bridge is "in front" of my
PCI-X SATA controller, which is sharing a physical interrupt with a PCI device
passed to a domU - coincidence?

# lspci -tv
-[0000:00]-+-00.0  Intel Corporation 82X38/X48 Express DRAM Controller
           +-01.0-[0000:01]--+-00.0  ATI Technologies Inc RV370 [Sapphire X550
Silent]
           |                 \-00.1  ATI Technologies Inc RV370 secondary
[Sapphire X550 Silent]
           +-1a.0  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
#4
           +-1a.1  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
#5
           +-1a.2  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
#6
           +-1a.7  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller
#2
           +-1b.0  Intel Corporation 82801I (ICH9 Family) HD Audio Controller
           +-1c.0-[0000:05-07]--+-00.0-[0000:07]----01.0  Marvell Technology
Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller
           |                    \-00.1-[0000:06]--
           +-1c.2-[0000:04]----00.0  Marvell Technology Group Ltd. 88E8056
PCI-E Gigabit Ethernet Controller
           +-1c.3-[0000:03]----00.0  Marvell Technology Group Ltd. 88E8056
PCI-E Gigabit Ethernet Controller
           +-1c.4-[0000:02]----00.0  Marvell Technology Group Ltd. 88SE6145
SATA II PCI-E controller
           +-1d.0  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
#1
           +-1d.1  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
#2
           +-1d.2  Intel Corporation 82801I (ICH9 Family) USB UHCI Controller
#3
           +-1d.7  Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller
#1
           +-1e.0-[0000:08]--+-00.0  Philips Semiconductors SAA7130 Video
Broadcast Decoder
           |                 +-01.0  Philips Semiconductors SAA7130 Video
Broadcast Decoder
           |                 \-03.0  VIA Technologies, Inc. IEEE 1394 Host
Controller
           +-1f.0  Intel Corporation 82801IR (ICH9R) LPC Interface Controller
           +-1f.2  Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA
AHCI Controller
           \-1f.3  Intel Corporation 82801I (ICH9 Family) SMBus Controller


-- 
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
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 1428] New: dom0 crash, bugzilla-daemon <=
Previous by Date:  [Xen-bugs] [Bug 1421] Hypervisor freeze on bootup, bugzilla-daemon
Next by Date:  [Xen-bugs] [Bug 1429] New: XSM-ACM module not working on Xen 3.3.1, bugzilla-daemon
Previous by Thread:  [Xen-bugs] [Bug 1421] Hypervisor freeze on bootup, bugzilla-daemon
Next by Thread:  [Xen-bugs] [Bug 1429] New: XSM-ACM module not working on Xen 3.3.1, bugzilla-daemon
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy