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-users

[Xen-users] Constan kernel oopses involving vfs_stat_fd and vfs_lstat_fd

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Constan kernel oopses involving vfs_stat_fd and vfs_lstat_fd
From: Phil Evans <xenmail@xxxxxxxxxxxx>
Date: Fri, 24 Mar 2006 18:15:39 +0000
Delivery-date: Fri, 24 Mar 2006 18:17:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Windows/20051201)
I am using the Xen version that comes with FC5 (although this has also happened on FC4 and CentOS 4.2 with other versions of Xen), and am having a problem with the kernel constantly oopsing in a similar way. Here is one of them:

Mar 24 10:03:14 hydra kernel: <1>Unable to handle kernel NULL pointer dereference at virtual address 0000003c
Mar 24 10:03:14 hydra kernel:  printing eip:
Mar 24 10:03:14 hydra kernel: c0161676
Mar 24 10:03:14 hydra kernel: *pde = ma 39c9c067 pa 332e7067
Mar 24 10:03:14 hydra kernel: *pte = ma 00000000 pa 55555000
Mar 24 10:03:14 hydra kernel: Oops: 0000 [#15]
Mar 24 10:03:14 hydra kernel: SMP
Mar 24 10:03:14 hydra kernel: Modules linked in: nls_utf8 cifs xt_tcpudp xt_physdev iptable_filter ip_tables x_tables bridge autofs4 hidp l2cap bluetooth ipv6 video button battery ac lp parport_pc parport nvram uhci_hcd ehci_hcd sg e1000 i2c_i801 i2c _core i6300esb e752x_edac edac_mc dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd ata_piix libata sd_mod scsi_mod
Mar 24 10:03:14 hydra kernel: CPU:    3
Mar 24 10:03:14 hydra kernel: EIP:    0061:[<c0161676>]    Not tainted VLI
Mar 24 10:03:14 hydra kernel: EFLAGS: 00010246   (2.6.15-1.2054_FC5xen0 #1)
Mar 24 10:03:14 hydra kernel: EIP is at vfs_getattr+0x35/0xa5
Mar 24 10:03:14 hydra kernel: eax: 00000000 ebx: f3e937b8 ecx: f3fea440 edx: c09f82c8 Mar 24 10:03:14 hydra kernel: esi: c09f82c8 edi: ec005f70 ebp: f3fea440 esp: ec005edc
Mar 24 10:03:14 hydra kernel: ds: 007b   es: 007b   ss: 0069
Mar 24 10:03:15 hydra smartd[1893]: smartd received signal 15: Terminated
Mar 24 10:03:15 hydra kernel: Process pidof (pid: 9695, threadinfo=ec004000 task=c04a0df0)
Mar 24 10:03:15 hydra smartd[1893]: smartd is exiting (exit status 0)
Mar 24 10:03:15 hydra kernel: Stack: <0>00000000 ec005efc bfb53f10 ec004000 c0161715 f3fea440 c09f82c8 ec005f70 Mar 24 10:03:15 hydra kernel: c09f82c8 f3fea440 00000000 c02f5603 f1b3c994 00000000 00000001 00000000 Mar 24 10:03:15 hydra kernel: f3fe76b8 000003e4 ec02008c f1b3c994 c02f5613 40000010 00000000 00000000 Mar 24 10:03:15 hydra kernel: Call Trace:
Mar 24 10:03:15 hydra kernel:  [<c0161715>] vfs_lstat_fd+0x2f/0x42
Mar 24 10:03:15 hydra kernel:  [<c02f5603>] _spin_unlock+0x6/0x8
Mar 24 10:03:15 hydra kernel:  [<c02f5613>] _spin_lock+0x6/0x8
Mar 24 10:03:15 hydra kernel:  [<c0161760>] vfs_lstat+0xf/0x13
Mar 24 10:03:15 hydra kernel:  [<c0161774>] sys_lstat64+0x10/0x26
Mar 24 10:03:15 hydra kernel:  [<c011323d>] do_page_fault+0x0/0x6a8
Mar 24 10:03:15 hydra kernel:  [<c0104b3d>] syscall_call+0x7/0xb
Mar 24 10:03:15 hydra kernel: Code: 24 18 8b 7c 24 1c 8b 5e 18 f6 83 a1 01 00 00 02 75 13 56 55 a1 a0 cc 42 c0 ff 90 c4 00 00 00 59 5a 85 c0 75 71 8b 83 b8 00 00 00 <8b> 48 3c 85 c9 74 12 89 7c 24 1c 89 74 24 18 89 6c 24 14 5b 5e

These oopses *always* have either "vfs_stat_fd" or "vfs_lstat_fd" at the top of the call trace. Does anyone know why this might be? If it is any help here is the output from lspci so you know what hardware I have (it is a SuperMicro motherboard):

00:00.0 Host bridge: Intel Corporation E7320 Memory Controller Hub (rev 0c)
00:02.0 PCI bridge: Intel Corporation E7525/E7520/E7320 PCI Express Port A (rev 0c) 00:03.0 PCI bridge: Intel Corporation E7525/E7520/E7320 PCI Express Port A1 (rev 0c)
00:1c.0 PCI bridge: Intel Corporation 6300ESB 64-bit PCI-X Bridge (rev 02)
00:1d.0 USB Controller: Intel Corporation 6300ESB USB Universal Host Controller (rev 02) 00:1d.1 USB Controller: Intel Corporation 6300ESB USB Universal Host Controller (rev 02) 00:1d.4 System peripheral: Intel Corporation 6300ESB Watchdog Timer (rev 02) 00:1d.5 PIC: Intel Corporation 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02) 00:1d.7 USB Controller: Intel Corporation 6300ESB USB2 Enhanced Host Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 0a)
00:1f.0 ISA bridge: Intel Corporation 6300ESB LPC Interface Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 6300ESB SATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 6300ESB SMBus Controller (rev 02)
03:03.0 Ethernet controller: Intel Corporation 82541GI/PI Gigabit Ethernet Controller 03:04.0 Ethernet controller: Intel Corporation 82541GI/PI Gigabit Ethernet Controller
04:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)

Could someone pleeeease help me with this it's driving me crazy!

Thanks,
Phil Evans.

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

<Prev in Thread] Current Thread [Next in Thread>