thr3ads.net - Xen users - [Xen-users] Constan kernel oopses involving vfs_stat_fd and vfs_lstat

If this information is useful, please help other people find it:
Share via:

Phil Evans

2006-Mar-24 18:15 UTC

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

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@lists.xensource.com
http://lists.xensource.com/xen-users

James Morris

2006-Mar-24 20:41 UTC

head link

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

On Fri, 24 Mar 2006, Phil Evans wrote:
> 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:
What sort of filesystem is this happening on?

-- 
James Morris
<jmorris@redhat.com>



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

Phil Evans

2006-Mar-24 22:30 UTC

head link

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

All of the filesystems that I am using are ext3.  Also, since the last 
message I have also received this error:

Mar 24 13:01:17 hydra kernel: kernel BUG at lib/radix-tree.c:610!
Mar 24 13:01:17 hydra kernel: invalid opcode: 0000 [#1]
Mar 24 13:01:17 hydra kernel: SMP
Mar 24 13:01:17 hydra kernel: Modules linked in: xt_tcpudp xt_physdev 
iptable_filter ip_tables x_tables bridge autofs4 hidp l2cap bluetooth 
ipv6 vid
eo 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_mir
ror dm_mod ext3 jbd ata_piix libata sd_mod scsi_mod
Mar 24 13:01:17 hydra kernel: CPU:    0
Mar 24 13:01:17 hydra kernel: EIP:    0061:[<c01cc786>]    Not tainted VLI
Mar 24 13:01:17 hydra kernel: EFLAGS: 00010046   (2.6.15-1.2054_FC5xen0 #1)
Mar 24 13:01:17 hydra kernel: EIP is at 
radix_tree_gang_lookup_tag+0xa5/0x173
Mar 24 13:01:17 hydra kernel: eax: ffffffff   ebx: 00000080   ecx: 
00000002   edx: 00000000
Mar 24 13:01:17 hydra kernel: esi: c04a3e48   edi: ea536f44   ebp: 
00000002   esp: c04a3d98
Mar 24 13:01:17 hydra kernel: ds: 007b   es: 007b   ss: 0069
Mar 24 13:01:17 hydra kernel: Process pdflush (pid: 190, 
threadinfo=c04a2000 task=f3f56650)
Mar 24 13:01:17 hydra kernel: Stack: <0>00000002 00000000 00000fff 
00000000 00000000 00000006 c04a3e48 0000000e
Mar 24 13:01:17 hydra kernel:        ec14e238 c04a3e48 ec14e244 c04a3e88 
c013d802 ec14e238 c04a3e48 00000000
Mar 24 13:01:17 hydra kernel:        0000000e 00000000 c04a3e40 c04a3f54 
ec14e234 ec14e234 c0143e3d 
ec14e234                                        Mar 24 13:01:17 hydra 
kernel: Call Trace:
Mar 24 13:01:17 hydra kernel:  [<c013d802>] find_get_pages_tag+0x2f/0x6b
Mar 24 13:01:17 hydra kernel:  [<c0143e3d>] pagevec_lookup_tag+0x1e/0x25
Mar 24 13:01:17 hydra kernel:  [<c0178a6b>] mpage_writepages+0x2b3/0x2ff
Mar 24 13:01:17 hydra kernel:  [<f48af6e9>] 
ext3_ordered_writepage+0x0/0x15d [ext3]
Mar 24 13:01:17 hydra kernel:  [<c02f4138>] schedule+0x604/0x66f
Mar 24 13:01:17 hydra kernel:  [<c0142bef>] do_writepages+0x30/0x39
Mar 24 13:01:17 hydra kernel:  [<c01771f1>] 
__writeback_single_inode+0x196/0x32b
Mar 24 13:01:17 hydra kernel:  [<c0143479>] pdflush+0x0/0x1c2
Mar 24 13:01:17 hydra kernel:  [<c02f565f>] _spin_lock_irqsave+0x22/0x27
Mar 24 13:01:17 hydra kernel:  [<c0142409>]
read_page_state_offset+0x47/0x5f
Mar 24 13:01:17 hydra kernel:  [<c0177850>] sync_sb_inodes+0x190/0x250
Mar 24 13:01:17 hydra kernel:  [<c0143479>] pdflush+0x0/0x1c2
Mar 24 13:01:17 hydra kernel:  [<c0177b14>] writeback_inodes+0x8c/0xdc
Mar 24 13:01:17 hydra kernel:  [<c0142eee>] background_writeout+0x66/0x8e
Mar 24 13:01:17 hydra kernel:  [<c0143588>] pdflush+0x10f/0x1c2
Mar 24 13:01:17 hydra kernel:  [<c0142e88>] background_writeout+0x0/0x8e
Mar 24 13:01:17 hydra kernel:  [<c012df5a>] kthread+0xa0/0xcd
Mar 24 13:01:17 hydra kernel:  [<c012deba>] kthread+0x0/0xcd
Mar 24 13:01:17 hydra kernel:  [<c01029ad>] kernel_thread_helper+0x5/0xb
Mar 24 13:01:17 hydra kernel: Code: 24 14 d3 e8 83 e0 3f 89 04 24 eb 47 
8b 54 24 44 8d 84 d7 00 01 00 00 8b 0c 24 0f a3 48 04 19 c0 85 c0 74 11 83 7
c 8f 04 00 75 34 <0f> 0b 62 02 c5 8d 31 c0 eb 2a ba 01 00 00 00 8a 4c 24 
14 d3 e2

As with the other kernel errors I''m getting, this one does also appear 
to be filesystem-based.  Also FYI, it is version 3.0.0 that comes with FC5.

Thanks.


James Morris wrote:> On Fri, 24 Mar 2006, Phil Evans wrote:
>
>   
>> 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:
>>     
>
> What sort of filesystem is this happening on?
>
>   

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

Xen users - Mar 2006 - Constan kernel oopses involving vfs_stat_fd and vfs_lstat_fd

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

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

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