https://bugzilla.novell.com/show_bug.cgi?id=439018 User bugproxy@us.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=439018#c53 LTC BugProxy <bugproxy@us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http:// --- Comment #53 from LTC BugProxy <bugproxy@us.ibm.com> 2008-11-07 09:06:05 MST --- =Comment: #0================================================= Jeremy M. Savoy <jsavoy@us.ibm.com> - ---Problem Description--- Machine: HS21XM Mongoose Processors: 2 @ 3.0 Ghz (Quad Core Harpertown) Memory: 4 GB System BIOS: BAE145A System BMC: BABT49A System Diags: BAYT36A AMM: BPET34E Operating System: SLES11 Beta1 x86_64 Hardware Setup: HS21XM w/ following options cKVM 4GB uDOC (39R8697) BladeCenter FC Expansion Card SFF 26K4841 Problem: HS21XM powers off unexpectedly under stress while running SLES11 Beta1 64bit. I have an HS21XM with two Harpertown CPU packages installed in it. This blade is running in a BladeCenterH Chassis. The ESW on the blade and the AMM are recorded above (all are probably slightly backlevel). SLES11 Beta1 64bit was installed on the blade successfully. The autoscript generator and TUX was then started on the blade (along with a client mounting the blade for network traffic). All looked normal. I then checked on the HS21XM about an hour later and noticed that it was powered off. The same thing also happened on Crichton and Groucho (which were installed in a BladeCenterE). A look at the management module logs just show a simple "blade powered off" message, with nothing ugly before or after. Also seen on big Lewis, little Lewis, Morrison and Defiant. Setting the Power Management to never and disabling the screen saver seems to get around this. Contact Information = Jeremy Savoy jsavoy@us.ibm.com ---uname output--- SLES 11 Beta 1 (don't have specific uname info with me) Machine Type = HS21XM ---System Hang--- The system is completely powered off ---Steps to Reproduce--- Install SLES 11 Beta1 64 bit on any of the hardware mentioned in the problem description, then log in and let the unit sit. After the power management settings kick in, the unit powers off and must be cold booted. ---Not Yet Classified Component Data--- =Comment: #2================================================= Jeremy M. Savoy <jsavoy@us.ibm.com> - This bug can be seen on any hardware available to you ... just install SLES 11 Beta1 64-bit and then start the OS in runlevel 5 and wait a bit and the machine will power off. Setting the screensaver to "Never" turn on fixes this issue. It seems as though the machine may try to go to sleep, but then cannot be brought out of that state. =Comment: #3================================================= Jonathan R. Thomas <jon.thomas@us.ibm.com> - Can you clarify does the machine power off or just freeze/hang? =Comment: #4================================================= Jeremy M. Savoy <jsavoy@us.ibm.com> - I suspect that the machine is being put into sleep mode and then can't recover, it does not appear "hung" but powered off. You can easily reproduce this issue on any machine and see the behaviour. ------- Comment From jrthomas@btv.ibm.com 2008-10-01 11:28 EDT------- https://bugzilla.linux.ibm.com/mirrorproxy.cgi?distro=novell&eid=431295 ------- Comment From jsavoy@us.ibm.com 2008-10-01 13:23 EDT------- More specifically, if you go into "Control Panel" and select "Screensaver" then select "Power Management", then set the computer to "Never" be put to sleep - if you do this, the defect does not occur. ------- Comment From jon.thomas@us.ibm.com 2008-10-01 11:28 EDT------- I suspect this came from the energy star patch, since this is fixed in b2. Rodrigo? ------- Comment From jsavoy@us.ibm.com 2008-10-09 15:49 EDT------- Novell has disabled by default power managment which would put the machine into sleep mode after a period of inactivity. So this doesn't actually fix the problem, it only prevents it from occurring. If you re-enable the sleep function, your machine will power off, and when you reboot you get an error stating that the machine could not be put into suspend. I think we need the suspend long Danny? Yes. (Seife can tell you more if you have the logs) please attach /var/log/pm-suspend.log after the machine had powered off. Ok. The machine is autosuspending. Because it can not suspend to RAM, it does suspend to disk, which works perfectly and actually resumes fine. So there is no suspend error :-) The problem is a) it is autosuspending at all b) it is showing the suspend error even though it suspended just fine. These are two bugs, that are already logged, however, I don't know their numbers offhand. I'll take the people who know more about those into CC: Will be fixed in Beta5. *** This bug has been marked as a duplicate of bug 439018 *** https://bugzilla.novell.com/show_bug.cgi?id=439018 -- 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.