From: Borislav Petkov <bp@alien8.de>
To: "MPhil. Emanoil Kotsev" <Emanoil.Kotsev@fincom.at>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [Intel-gfx] kernel 3.11.6 general protection fault
Date: Sun, 17 Nov 2013 21:05:46 +0100 [thread overview]
Message-ID: <20131117200546.GP27323@pd.tnic> (raw)
In-Reply-To: <201311171745.19339.Emanoil.Kotsev@fincom.at>
On Sun, Nov 17, 2013 at 05:45:18PM +0100, MPhil. Emanoil Kotsev wrote:
> How - new libraries - more exhaustive algorythms - higher cpu usage
> etc. Some of the things M$ is doing on purpose to force you upgrade
> your hardware every 2-3years
That would be too easy and machines would be dying left and right of
overheating. Actually, sane hardware is much more robust than that and
it throttles itself in case of critical temperature levels. And, IMHO
your Dell Latitude D520 should be fine, in that respect. But we'll see.
:-)
> I wanted to first compile the kernel with the debug option you
> mentioned, but while compiling it went to about 75°C.
Yeah, that's still ok if we trust the output saying that 126°C is the
critical temp.
It would be interesting to see what this sensor says right before the
machine locks up.
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-11-17 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 19:58 kernel 3.11.6 general protection fault MPhil. Emanoil Kotsev
2013-11-13 20:09 ` [Intel-gfx] " Daniel Vetter
2013-11-13 20:33 ` Borislav Petkov
2013-11-13 21:19 ` MPhil. Emanoil Kotsev
2013-11-17 11:35 ` MPhil. Emanoil Kotsev
2013-11-17 12:07 ` Borislav Petkov
2013-11-17 14:45 ` MPhil. Emanoil Kotsev
2013-11-17 15:06 ` Borislav Petkov
2013-11-17 16:45 ` MPhil. Emanoil Kotsev
2013-11-17 20:05 ` Borislav Petkov [this message]
2013-11-19 9:21 ` MPhil. Emanoil Kotsev
2013-12-18 20:59 ` MPhil. Emanoil Kotsev
2013-12-18 21:22 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131117200546.GP27323@pd.tnic \
--to=bp@alien8.de \
--cc=Emanoil.Kotsev@fincom.at \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox