From: Ermanno Polli (Ermanno.Polli@lnf.infn.it)
Date: Wed Mar 12 2003 - 09:10:03 EST
Hi,
sorry for the long mail, but I couldn't do it shorter. Actually there is
more about it..
I have this problem on tru64 5.0A, on a ES40 server.
Actually it involves the ES40, a dual Pentium PC with Linux SuSe 7.3,
some AlphaStation 600 with Digital Unix 3.2C, and a lot of NFS mounted
disks.
I was doing a copy from a directory to another with tar piped to
another tar (tar c | tar x, in short). The source disk was on an
AlphaStation 600 and the destination disk was on the PC.
In the middle of the copy, the ES40 crashed with "trap: invalid memory
read access from kernel mode". Trying to understand why, I did a ls -lR
on the destination direcory. Well, I saw some symlinks having the
destination file, after the "->", follwed by some text, apparently taken
from some file... There was this "name too long error" and two or three
errors later, the ES40 crashed.
The same tar pipe, issued frome the linux box, succeded!
I opened a call to HP (sigh!) but they told me there was no hardware
failure. Since I only have a hardware maintenance, they helped me
no more..:-(
Yesterday, I had a variant.. I tried both a tar pipe from the linux box
in the tru64 5.0A and a cp -R command. Both followed the same fate: two
crashes.
And the one from cp -R, had a double crash!
>From the crash.data:
trap: invalid memory read access from kernel mode
faulting virtual address: 0x5e4e4e3545202c5a
pc of faulting instruction: 0xfffffc0000276d30
ra contents at time of fault: 0xffffffffffffe000
sp contents at time of fault: 0xfffffe04a2adf558
panic (cpu 1): kernel memory fault
syncing disks...
trap: invalid memory read access from kernel mode
faulting virtual address: 0x0000000000000008
pc of faulting instruction: 0xfffffc00005c16e0
ra contents at time of fault: 0xfffffc00005c16d4
sp contents at time of fault: 0xfffffe04a1f3efb8
and then:
_proc_thread_list_begin:
thread 0xfffffc00275a2000 stopped at [stop_secondary_cpu:1009
,0xfffffc00004f6250] Source not available
_proc_thread_list_end:
The crash form the piped tar was:
trap: invalid memory read access from kernel mode
faulting virtual address: 0x5e4e4e3545202c5a
pc of faulting instruction: 0xfffffc0000276d30
ra contents at time of fault: 0xffffffffffffe000
sp contents at time of fault: 0xfffffe04a2adf508
panic (cpu 0): kernel memory fault
Same va, same pc and same ra. Slightly different ps.
Anyone have any idea about resoving this problem?
I applied all the patches form patch kit #3 to the latest sendmail bug.
Thank you in advance.
Ermanno Polli
ermanno.polli@lnf.infn.it
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:10 EDT