100 degrees)
Hi, I just wanted to check if I am the only one that has thermal issues with the 3.4 kernel ? I see the following behavior : 1) Load the notebook with a gcc acitivity until all processors are 100% load 2) Shortly after you get notifications that a thermal event is reached (CPU's 3) Kernel reacts and shutdown the system. Strangely enough the same task with an 3.3 kernel can easily survive and also under Windows I do not have any problems. Checking bugs.kernel.org I found something with regards to this effect and they suggested to load the thermal module with nocrt=1 so that the activity on the first trippoint is not initiated. This indeed helps a lot and it seems that even with a high load the notebook doesn't get that hot. Also no shutdown is initiated. I also tried kernel 3.5 from Kernel:HEAD and this one has the same effect with the temperature. However using the nocrt=1 option, I get a different undesired effect. Once the temperature gets to a certain point, the kernel lowers the speed of the CPU's to the lowest point. Once the CPU's are cool'ed down, this maximum speed should be increased again. With kernel 3.4 this works as indicated. With kernel 3.5 however this maximum speed is not changed anymore until a reboot. I also filed the following two bugs for this: https://bugzilla.novell.com/show_bug.cgi?id=773563 https://bugzilla.novell.com/show_bug.cgi?id=767692 Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org