Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-31-2001, 11:31 AM
|
#1
|
|
LQ Newbie
Registered: Jul 2001
Location: Madison, AL
Distribution: Red Hat
Posts: 7
Rep:
|
Unable to handle kernel paging request at virtual address fe12c000
I am running RedHat 7.1....Mosix 1.0.6....Kernel 2.4.3
We are starting to get these at least once a day on each of our nodes. I think its a Mosix issue but I'm not sure. Any input would help greatly. Here is my oops:
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.7/ (default)
-m /boot/System.map (specified)
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Jul 25 13:30:25 matrix2 kernel: Unable to handle kernel paging request at virtual address fe12c000
Jul 25 13:30:25 matrix2 kernel: c01bb2f6
Jul 25 13:30:25 matrix2 kernel: *pde = 2e70616d
Jul 25 13:30:25 matrix2 kernel: Oops: 0000
Jul 25 13:30:25 matrix2 kernel: CPU: 1
Jul 25 13:30:25 matrix2 kernel: EIP: 0010:[mfs_local_filldir+38/344]
Jul 25 13:30:25 matrix2 kernel: EIP: 0010:[<c01bb2f6>]
Using defaults from ksymoops -t elf32-i386 -a i386
Jul 25 13:30:25 matrix2 kernel: EFLAGS: 00010246
Jul 25 13:30:25 matrix2 kernel: eax: 00000000 ebx: f2e43e9c ecx: fffffffb edx: 00004ff4
Jul 25 13:30:25 matrix2 kernel: esi: f2e43e9c edi: fe12c000 ebp: 00000004 esp: f2e43c08
Jul 25 13:30:25 matrix2 kernel: ds: 0018 es: 0018 ss: 0018
Jul 25 13:30:25 matrix2 kernel: Process find (pid: 898, stackpage=f2e43000)
Jul 25 13:30:25 matrix2 kernel: Stack: f2e43e9c 00000ff4 fffffffe c33fa848 c01508d8 f30cac20 00000001 c0127e8e
Jul 25 13:30:25 matrix2 kernel: 00000000 00000003 f2e43d10 f2e43d1c f7efe7a8 0002ddf9 0023ee05 c3410801
Jul 25 13:30:25 matrix2 kernel: c341ee20 c0155319 c341eea0 c035b998 00000000 c341ee20 c014c0e0 c341eea0
Jul 25 13:30:25 matrix2 kernel: Call Trace: [filldir64+0/780] [in_group_p+30/40] [dput+25/340] [path_walk+2752/3228] [dput+25/340] [path_walk+275
2/3228] [permission+142/152]
Jul 25 13:30:25 matrix2 kernel: Call Trace: [<c01508d8>] [<c0127e8e>] [<c0155319>] [<c014c0e0>] [<c0155319>] [<c014c0e0>] [<c014b2ae>]
Jul 25 13:30:25 matrix2 kernel: [<c0157a94>] [<c0157cf3>] [<c01bb900>] [<c01bb988>] [<c01bb900>] [<c0155319>] [<c01bc495>] [<c01bfa5b>]
Jul 25 13:30:26 matrix2 kernel: [<c01696f4>] [<c01699b1>] [<c0150302>] [<c01bb2d0>] [<c01bb4a8>] [<c01bb2d0>] [<c01508d8>] [<c01bb2c4>]
Jul 25 13:30:26 matrix2 kernel: [<c01508d8>] [<c0150302>] [<c01508d8>] [<c0150c47>] [<c01508d8>] [<c01d93f8>] [<c0108ff4>]
Jul 25 13:30:26 matrix2 kernel: Code: f2 ae f7 d1 49 8d 51 0d 01 56 14 89 54 24 10 8b 46 18 01 44
>>EIP; c01bb2f6 <mfs_local_filldir+26/158> <=====
Trace; c01508d8 <filldir64+0/30c>
Trace; c0127e8e <in_group_p+1e/28>
Trace; c0155319 <dput+19/154>
Trace; c014c0e0 <path_walk+ac0/c9c>
Trace; c0155319 <dput+19/154>
Trace; c014c0e0 <path_walk+ac0/c9c>
Trace; c014b2ae <permission+8e/98>
Trace; c0157a94 <get_new_inode+140/1b4>
Trace; c0157cf3 <iget4+df/e8>
Trace; c01bb900 <compare_mfs_ip+0/38>
Trace; c01bb988 <mfs_iget+50/5c>
Trace; c01bb900 <compare_mfs_ip+0/38>
Trace; c0155319 <dput+19/154>
Trace; c01bc495 <mfs_express_lookup+579/6fc>
Trace; c01bfa5b <mfs_check_completion+133/228>
Trace; c01696f4 <ext2_get_page+20/f0>
Trace; c01699b1 <ext2_readdir+1ed/2f4>
Trace; c0150302 <vfs_readdir+92/ec>
Trace; c01bb2d0 <mfs_local_filldir+0/158>
Trace; c01bb4a8 <mfs_low_readdir+80/b4>
Trace; c01bb2d0 <mfs_local_filldir+0/158>
Trace; c01508d8 <filldir64+0/30c>
Trace; c01bb2c4 <mfs_readdir+d4/e0>
Trace; c01508d8 <filldir64+0/30c>
Trace; c0150302 <vfs_readdir+92/ec>
Trace; c01508d8 <filldir64+0/30c>
Trace; c0150c47 <sys_getdents64+63/11c>
Trace; c01508d8 <filldir64+0/30c>
Trace; c01d93f8 <local_pre_usermode_actions+10/c0>
Trace; c0108ff4 <local_syscall+7/13>
Code; c01bb2f6 <mfs_local_filldir+26/158>
00000000 <_EIP>:
Code; c01bb2f6 <mfs_local_filldir+26/158> <=====
0: f2 ae repnz scas %es%edi),%al <=====
Code; c01bb2f8 <mfs_local_filldir+28/158>
2: f7 d1 not %ecx
Code; c01bb2fa <mfs_local_filldir+2a/158>
4: 49 dec %ecx
Code; c01bb2fb <mfs_local_filldir+2b/158>
5: 8d 51 0d lea 0xd(%ecx),%edx
Code; c01bb2fe <mfs_local_filldir+2e/158>
8: 01 56 14 add %edx,0x14(%esi)
Code; c01bb301 <mfs_local_filldir+31/158>
b: 89 54 24 10 mov %edx,0x10(%esp,1)
Code; c01bb305 <mfs_local_filldir+35/158>
f: 8b 46 18 mov 0x18(%esi),%eax
Code; c01bb308 <mfs_local_filldir+38/158>
12: 01 44 00 00 add %eax,0x0(%eax,%eax,1)
1 warning issued. Results may not be reliable.
Thanks,
Wayne P
|
|
|
|
07-31-2001, 02:25 PM
|
#2
|
|
Senior Member
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243
Rep:
|
Have you check all your file systems - that would be my first port of call. I've only ever managed to get this sorta error during hardware failures.
cheers
Jamie...
|
|
|
|
07-31-2001, 02:31 PM
|
#3
|
|
LQ Newbie
Registered: Jul 2001
Location: Madison, AL
Distribution: Red Hat
Posts: 7
Original Poster
Rep:
|
Yeah but
Everything seems to be functioning normally. The network may be a little slow, but everything else seems fine and I see no other errors.
Thanks,
Wayne
|
|
|
|
07-31-2001, 02:35 PM
|
#4
|
|
Senior Member
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243
Rep:
|
My kenel oops' like these were caused by an intermittent CPU failure. Took ages to track down - I ended up swapping the hardware out piece by piece then using the system for a few days to see what would happen.
cheers
Jamie...
|
|
|
|
07-31-2001, 02:38 PM
|
#5
|
|
LQ Newbie
Registered: Jul 2001
Location: Madison, AL
Distribution: Red Hat
Posts: 7
Original Poster
Rep:
|
Great
Oh well,
If you run into anything else that might help me out just toss it my way. We'll keep plugging away at it.
Thanks,
Wayne P.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 08:35 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|