[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axp-redhat
Subject:    Regarding earlier mail, compiling joe, Oops & VFS weirdness..
From:       bert hubert <ahu () vvtp ! tn ! tudelft ! nl>
Date:       1997-04-30 23:38:10
[Download RAW message or body]

First, kudos to the people making all this possible! I've been with linux 
since it fitted on two 5.25" floppies, and now run it on a 96MB 
AlphaStation, donated to my studentassociation by DEC. Way cool!

In my mail from yesterday I mentioned that sometimes it caused an Oops 0 
message, and quoted it, but also said that it sometimes gave VFS errors. 
I have now been able to reproduce this one:

cc -O   -c ublock.c -o ublock.o
cc1: memory violation at pc=1201066a4 rp=120106854 (bad address = 00000000)
VFS: iput: trying to free free inode
VFS: device 4f:a0, inode 0, mode=00000000
cc: Internal compiler error: program cc1 got fatal signal 11
make: *** [ublock.o] Error 1
[root@alpha joe]# ls -l core

This is with a virgin RH4.1 install, avanti-s.gz kernel, loaded directly 
from the cdrom-installed aboot.

When doing an strace of the process, it outputs the following errors:
Unable to find vma for addr 0x120114000
ptrace: umoven: Input/output error
Unable to find vma for addr 0x120114000
ptrace: umoven: Input/output error
Unable to find vma for addr 0x120114000
ptrace: umoven: Input/output error
Unable to find vma for addr 0x120116000
ptrace: umoven: Input/output error

My main question is: is this something to worry about? The problem goes 
away if I disable coredumps, but still the systems seems a tad unstable. 


--
To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com

[prev in list] [next in list] [prev in thread] [next in thread]