login
Header Space

 
 

debugging system freeze

April 23, 2008 - 9:25am
Submitted by Anonymous on April 23, 2008 - 9:25am.
Linux

I have a particular problem: when I try to compile a C/C++ file the whole systems stops (no network, mouse, etc)

I replaced every part of the system (CPU, Memory, motherboard, Hard disk, video card) and
I get the same result (which points to a software problem)

Currently specs:
Biostar NF4ST-A9
550W power supply
Atlon x64 +3800 (dual core)
NVIDIA video card (6600, same problem issue with the NVIDIA video drivers and non NVIDIA drivers)
160GB SATA (Maxtor)
2 GB memory (Viking)

OS Suse 10.1 (tried 10.2 system is not stable, 10.3 system is unusable)

Any suggestions to how to proceed and find what the issue is? I configured syslog to log into another machine; I found out that I have processing for about 5 seconds before the system freezes, but nothing in the log. I run memtest for one day and no memory issues, when Using 10.1 I can develop java applications (which as everybody knowns are big in resources (the IDE alone takes 450GB, the app server another 300GB of memory) but I do not have any freezes

Thanks

thanks

April 25, 2008 - 9:07am
Anonymous (not verified)

thanks for all the help and support

Some motherboard chipsets

April 25, 2008 - 8:47pm
Anonymous (not verified)

Some motherboard chipsets tend to have problems with APIC, try passing the 'noapic' boot parameter.

Thanks

April 27, 2008 - 5:31am
Anonymous (not verified)

I tried to not use APIC (acpi=off system does not boot (can not find the SATA harddisk) tried with acpi=oldboot and same problem. System just freeze. I do not get anything on the logs.

Thanks

APIC, *not* ACPI, they are

April 29, 2008 - 5:50am
Anonymous (not verified)

APIC, *not* ACPI, they are completely different and unrelated things.

thanks for catching the typo

May 7, 2008 - 4:45pm
Anonymous (not verified)

Thanks very much for your help, got a logic analyzer and borrowed a POD. The problem is the memory controller, is not refreshing the memory correctly. The solution was to change the mem speed to 333 and it solves the issue

Thanks

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
speck-geostationary