https://bugzilla.novell.com/show_bug.cgi?id=229165 ------- Comment #8 from alpha096@tpg.com.au 2006-12-16 01:53 MST ------- Went into BIOS - NIL setting for shut-down of due temp is available at variable temp setting. P.S did not shut-down per-say. It went into a type of suspend where the PC had the light on and when power button pressed there was no BOOT or POST..... Will try to decompress missing files and re-compress IF they are desperately required...Please advise. As previously stated system was in suspend type mode, however there was no image to recall from Disk or RAM. This has happened twice during backup via Kdar of my /home directory and system log showed temp at critical. I was unable to save as my /home directory was trashed and could not be repaired. Using Kdar I was backing up to an NFS drive, both RAID0 and encrypted partitions and during boot of the PC that ran Kdar, (NFS- Notify) during both took over half an hour and then this same type of suspend action. That system had to be re-installed – however I was just about to save, but could not a log that looked something like this Dec 16 18:35:23 multivac-ii kernel: CPU0: Temperature critical Dec 16 18:35:23 multivac-ii kernel: CPU1: Temperature critical Dec 16 18:35:23 multivac-ii kernel: CPU1: Running in modulated clock mode Dec 16 18:35:23 multivac-ii kernel: CPU0: Running in modulated clock mode I will open hardware to check CPU fan above heat sink is operable. ALL other 3 fans operable. Hardware is P4 HT 3.2 1.g GB RAM. Mean time have Dynamic Frequency scaling to via BIOS to 37.?%. On both occasions the ambient temp was above 33C and DISK I/O and CPU at MAX. Kdar is re-noun for gulping resources to the limit. NO changes have been made to sysconfig settings. Please advise any other log type info I can provide. As I said this is not isolated to 1bit of hardware – at different points in time – normally using Kdar backup the PC has “suspended itself” as described above. The title may be misleading – It may well be that the totality of the applications running caused the event and System Management was the straw that broke. Will advise status of CPU Fax tomorrow – current 18:53 GMT +10 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.