New laptop

[Marc-André Laverdière]

Hello,


I recently had some problems of a laptop crashing randomly. I put a
widget on my desktop that shows the CPU temperature and it allowed me
to diagnose the problem. My system was at 75 degrees without doing
anything heavy.

The BIOS update did wonders. I would suggest to do that right away if
there is one released.

I also purposefully slow down the build, by running with nice -n19,
the lowest priority. You can also set some settings in autogen.sh to
limit the number of concurrent processes, but I found the solution to
work well. Also, you can get a fan to put under your laptop for a few
euros/dollars to help it cool down (My personal experience with those
wasn't very satisfactory, but your mileage may vary).

Much cheaper than buying a computer :)


Marc-André LAVERDIÈRE
"Perseverance must finish its work so that you may be mature and complete,
not lacking anything." -James 1:4
http://asimplediscipleslife.blogspot.com/
mlaverd.theunixplace.com



On Fri, Mar 8, 2013 at 5:29 AM, Michael Meeks <michael.meeks at suse.com> wrote:
> Hi José,
>
> On Fri, 2013-03-08 at 00:02 +0100, Christian Lohmaier wrote:
>> On Thu, Mar 7, 2013 at 11:16 PM, José Guilherme Vanz wrote:
>> > Well, I would like to ask a tip for you. I have a dell vostro laptop,
>>> but I cannot use it for contribute in the LO project. The laptop
>>> turns off because of the temperature.
>>
>> This should never happen with the current type of processors (they
>> reduce frequency/switch to a low-performance mode triggered by
>> temperature) - so it is a clear indicator that your fan/heatsink needs
>> a little bit of love (cleaning).
>
>         All of Christian's advice is excellent - hoovering can help; you might
> want to check if there is a BIOS update - they often have bugs in this
> area, or a setting to tweak the fan speed in there. I guess you're
> running Linux - and it's possible that it's not driving the hardware
> quite as the manufacturer intended (ie. for it to run Windows ;-).
>
>         The LibreOffice code-base has quite a long history of killing hardware
> - particularly laptop hardware - and the gnumake / parallelism belting
> the CPU even more intensely and gcc's memory access patterns prolly make
> for some nice pathological test-case ;-)
>
>         Previously sleeps were inserted to add some cooling-off period; failing
> that you could install icecream and tweak it to only run on one CPU (or
> say three if you have four) - which might give some thermal head-room.
>
>         HTH,
>
>                 Michael.
>
> --
> michael.meeks at suse.com  <><, Pseudo Engineer, itinerant idiot
>
> _______________________________________________
> LibreOffice mailing list
> LibreOffice at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libreoffice