[Wien] Wien2k stops completely

[Gerhard H Fecher]

I remember that I had two (+) years ago a similar problem.
The computer was freezing in some part of the program (most probably in lapw1) 
and sometimes switched off. Which of the cases was erratic and different if I 
was running different programs in parallel. If you hit nowadays some of the 
powersaving features it may also restart by itself.
The problem was gone after new installation of Linux and the Fortran compiler 
(ifc at that time, I guess) with newer Versions. It was at a time when some 
of the gnu cc libraries and versions changed. I had the problem on two 
identical computers and I had to do a complete new installation,  an update 
of the installed Linux did not help.

I assume it was a predecessor of the error that is now usually the SIGSEGV 
segmentation fault.
The bad thing with the oftenly occuring SIGSEGV error is that it seems not to 
be catchable. If you have a program that accidentially writes to a bad 
(unwanted) place in memory than all kind of strange things can happen, even 
if it is supposed that this is not possible and forbidden by the operating 
system (it may appear more often in Windows compared to Linux). I assume that 
C programmers can do that easily.

Good luck
Gerhard


Am Donnerstag, 16. März 2006 14:55 schrieb jjlee at nsrrc.org.tw:
> Dear ALL,
>  
>  
>  
>     Thanks a lots your suggestions.
>  
>    I also ever suspected the faluts came form memory failure, so I checked 
by two method:
>  
>   1. Before Installing Linux, I run the memtest86 for one whole day, there 
is no error message.
>   2. run ten small jobs synchronally that fully occupied the 4GB memory( use 
"top" to monitor), then it's all OK! no problem.
>  
>   So, now I suppose that the memory seem no problem. 
>  
> Sincerely yours
>  
>  
> JJLee
> 
> -----Original Message----- 
> From: wien-bounces at zeus.theochem.tuwien.ac.at 代理 Michael Gurnett 
> Sent: 2006/3/16 [星期四] 下午 03:24 
> To: A Mailing list for WIEN2k users 
> Cc: 
> Subject: Re: [Wien] Wien2k stops completely
> 
> 
> 
> Only time I saw behaviour like this it turned out that one of the memory
> sticks was bad on the computer. Could be worth doing a memcheck.
> 
> Michael
> 
> On Thu, 2006-03-16 at 14:58 +0800, jjlee_nsrrc wrote:
> > Dear Dr. Konior
> >
> >
> >
> >       I also encountered the same situation, most interesting part is,
> > everytime the crash point is different. Once upon a time, the identiacl 
job
> > can run more than 40 cycles, but most of time, only one cycle, then the
> > computer is totally crashed. Until now, I do not know how can I deal with
> > it. I also tried many different Linux system and compiler, but same
> > situation.
> >
> > ps, I use 2 X Xeon 3.2 CPU, 4 GB Priority check ram, mother board is TYAN
> > S2676
> >
> >
> > Sincerely yours
> >
> >
> > jjlee
> >
> >
> >
> > ----- Original Message -----
> > From: <konior at if.uj.edu.pl>
> > To: "A Mailing list for WIEN2k users" <wien at zeus.theochem.tuwien.ac.at>
> > Sent: Thursday, March 16, 2006 2:24 AM
> > Subject: [Wien] Wien2k stops completely
> >
> >
> > > Dear Wien2k users,
> > >
> > > We installed Wien2k and run test for simple systems without any problem.
> > >
> > > Then, the trouble came when I started calculations for bigger systems,
> > > around 20 atoms par
> > > unit cell or more. For some unknown reasons, the 'lapw1c' part either
> > > stops the whole
> > > computer completely or sometimes makes the computer reset. Even more
> > > surprisingly, I
> > > checked that running Wien2k with for the same system generally goes
> > > further (in time, but
> > > not always till the end of the iteration) if simultaneously another
> > > program is running.
> > >
> > > The machine is 2 x Xeon 3.2 GHz with 8 GB RAM, plus the Mandriva Linux,
> > > the compiler is
> > > Lahey Fortran 95 for Linux. Previously, with the Fedora Linux plus IFORT 
I
> > > found the same
> > > behavior.
> > >
> > > I run Wien2k on many variations, on one, two, three, or four processors,
> > > alone or with some
> > > other programs running. I suspect that probably our machine (memory,
> > > motherboard,
> > > processor) has some failure, but how to prove it?
> > >
> > > Did anyone of you have similar problems? Any help or suggestions would 
be
> > > appreciated.
> > >
> > >
> > > Greetings,
> > >
> > > --
> > > Jerzy Konior
> > > Institute of Physics
> > > Jagellonian University
> > > Krakow, Poland
> > >
> > >
> > > Pozdrawiam,
> > >
> > > --
> > > Jerzy Konior
> > >
> > >
> > > _______________________________________________
> > > Wien mailing list
> > > Wien at zeus.theochem.tuwien.ac.at
> > > http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
> > >
> >
> >
> > _______________________________________________
> > Wien mailing list
> > Wien at zeus.theochem.tuwien.ac.at
> > http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
> >
> 
> _______________________________________________
> Wien mailing list
> Wien at zeus.theochem.tuwien.ac.at
> http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
> 
> 
>