I have a test system: Centos 5.2 on an OQO, that has been hanging hard. I have to unplug it and pull the battery so I can then cold start it. This last time all I did was open a terminal window and SU to root, then start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). I was not even making a test phone call at the time. Oh, and the system only runs IPv6, no v4 addressing. So how do I find out what is causing the hard lockups?
Robert Moskowitz wrote:> I have a test system: Centos 5.2 on an OQO, that has been hanging > hard. I have to unplug it and pull the battery so I can then cold start it. > > This last time all I did was open a terminal window and SU to root, then > start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). > I was not even making a test phone call at the time. Oh, and the system > only runs IPv6, no v4 addressing. > > So how do I find out what is causing the hard lockups?if the problem is triggered reproducibly by building SIP C, then just don't use X when starting the build; change to a console (Ctrl-Alt-F1) and watch out for kernel messages indicating a software (kernel) problem. If the problem is due to hardware, there is a chance that memtest86+ will find bad memory. If it's a bad disk, you can check with smartctl. There's are burn-in programs available; I use burnCPU to put load on multi-core systems. Compiling the Linux kernel a hundred times in a row is also a good test; not a single build should fail. HTH, Kay
Robert Moskowitz <rgm at htt-consult.com> wrote: See embedded comments. I'm not familiar with the specific package mentioned but these are just a few standard debugging ideas.> I have a test system: Centos 5.2 on an OQO, that has been hanging > hard. I have to unplug it and pull the battery so I can then cold start it. >I assume this also means that the system runs as expected if you don't take any of the actions described below.> This last time all I did was open a terminal window and SU to root, then > start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). > I was not even making a test phone call at the time.Any chance of trying an earlier version? Especially one that uses an earlier JRE?> Oh, and the system > only runs IPv6, no v4 addressing. >And what happens if you enable IPV4? If possible, can SIP Communicator be configured to use IPV4 instead of V6? If so, does the problem persist?> So how do I find out what is causing the hard lockups? >I'd start with enabling IPV4 addressing since it's fairly trivial to do and then work back toward running an earlier version of the program. You may find something like the JRE wants an IPV4 connection (just wildly speculating here). Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce
On Fri, 2009-03-06 at 13:46 -0500, Robert Moskowitz wrote:> I have a test system: Centos 5.2 on an OQO, that has been hanging > hard. I have to unplug it and pull the battery so I can then cold start it. > > This last time all I did was open a terminal window and SU to root, then > start the lastest build of SIP Communicator (which uses JRE 1.6.0_10). > I was not even making a test phone call at the time. Oh, and the system > only runs IPv6, no v4 addressing. > > So how do I find out what is causing the hard lockups?Looks like you have had some good suggestions on your problem; however, it prompted me to search the CentOS site for OQO. Seems most of the references are related to your posts on this list since you got 4 in Sept. 2008. There's no info on the Wiki. After you get past the current crisis, please consider creating an OQO page under http://wiki.centos.org/HowTos/Laptops Regards, Phil