memory fault after "cd xxx"

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

memory fault after "cd xxx"

Pierre Frenkiel
hi,
I get a "memory fault" after doing "cd" to a given directory. Here is
the command sequencet:

    PFR2 /d11a/pfr2-bak/lib->>cd  i386-linux-gnu/
    Memory fault
    -ksh: line 408: 7567: Memory fault
    Memory fault
    PFR2 /d11a/pfr2-bak/lib/i386-linux-gnu->>free -m
    Memory fault
    PFR2 /d11a/pfr2-bak/lib/i386-linux-gnu->>cd ..
    -ksh: line 325: 7574: Memory fault
    Memory fault
    Memory fault
    PFR2 /d11a/pfr2-bak/lib->>free -m
               total        used        free      shared  buff/cache   available
Mem:           3125         372        1668          24        1084        2365
Swap:          1128           0        1128
PFR2 /d11a/pfr2-bak/lib->>

I don't have this problem with any other directory
After a fsck on the corresponding partition, the same error occurs.

Can anybody explain that?

best regards,
--
Pierre Frenkiel

Reply | Threaded
Open this post in threaded view
|

Re: memory fault after "cd xxx"

Nicholas Geovanis-2


On Thu, Jul 11, 2019 at 2:11 AM Pierre Frenkiel <[hidden email]> wrote:
hi,
I get a "memory fault" after doing "cd" to a given directory. Here is
the command sequencet:

    PFR2 /d11a/pfr2-bak/lib->>cd  i386-linux-gnu/
    Memory fault
    -ksh: line 408: 7567: Memory fault
    Memory fault
    PFR2 /d11a/pfr2-bak/lib/i386-linux-gnu->>free -m
    Memory fault
    PFR2 /d11a/pfr2-bak/lib/i386-linux-gnu->>cd ..
    -ksh: line 325: 7574: Memory fault
    Memory fault
    Memory fault
    PFR2 /d11a/pfr2-bak/lib->>free -m
.... 

I don't have this problem with any other directory
After a fsck on the corresponding partition, the same error occurs.
Can anybody explain that?

Hmmm. How about checking your RAM , a memtest.
 
best regards,
--
Pierre Frenkiel

Reply | Threaded
Open this post in threaded view
|

Re: memory fault after "cd xxx"

Pierre Frenkiel
On Thu, 11 Jul 2019, Nicholas Geovanis wrote:

> Hmmm. How about checking your RAM , a memtest.

thanks for your answer, but meanwhile, I upgraded fron  Stretch to Buster,
and the problem disappeared...
I don't know whether the fix comes from the upgrade, or just the reboot...

best regards,
--
Pierre Frenkiel