On 2008/01/05 21:11 (GMT+0530) Shibu Basheer apparently typed: > On Jan 5, 2008 9:09 PM, Felix Miata <[EMAIL PROTECTED]> wrote:
>> On 2008/01/05 20:50 (GMT+0530) Shibu Basheer apparently typed: >> > I have a new installation of Open Suse. I find it to randomly shuts >> > down, just like someone accidently presses the power button, or issue >> > the shutodown command. There are no prompts, messages or anything, >> > just starts shutting down closing everything that I've been doing. >> > Any ideas on how to isolate this problem? BTW, this has happened on >> > another computer, but AMD CPUs, only common component was the memory, >> > and a TV card. >> One possibility is an erroneous indication of CPU overheat. If you know how >> and your BIOS provides the means to do so, you can underclock your system by >> about 25% to see if the problem stops. If it does, you'll have to >> troubleshoot the cause of the erroneous indication. IIRC, it is caused by two >> daemons both trying to monitor CPU temp at the same time. >> Another possibility is TV card related. TV cards seem to demand a lot of >> power, maybe more than your power supply can reliably provide. You can >> temporarily remove the card to see if this is your problem. > HI Felix, Thanks for you suggestions. I've ruled both the problem, > because the system is running quite stable in safe mode, and I have > been running a long tv scan with tvtime. Failsafe mode uses acpi=off on cmdline, which would probably disable the ability to monitor CPU temperature or the ability to do anything as a result of the CPU temperature state. > So it looks like it is some kernel parameter, or something that is > enabled during normal bootup? -- "In the beginning was the Word, and the Word was with God, and the Word was God." John 1:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
