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: Wed, 18 Dec 2013 22:22:33 +0100 [thread overview]
Message-ID: <20131218212233.GE12222@pd.tnic> (raw)
In-Reply-To: <201312182159.22794.Emanoil.Kotsev@fincom.at>
On Wed, Dec 18, 2013 at 09:59:22PM +0100, MPhil. Emanoil Kotsev wrote:
> I was able to solve the issue by removing some of the modules I had in
> xorg.conf. I noticed that it is not the cpu that is overheating, but
> rather the video/graphic card. The area around the "Dell" logo on the
> front of the display is still pretty hot, but the system seem to be
> working fine now and I can not reproduce the issue any more.
Interesting. Which module was that?
It was probably making your GPU go nuts. The more interesting question
is whether this module would behave on your machine normally and only
some buggy incarnation of it would cause the overheating... I.e., it
could be you upgraded X and with the new version the issue started
appearing. Fun.
> I would like to thank you for your precious support and ideas once
> again.
Sure, you're welcome!
:-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-12-18 21:22 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
2013-11-19 9:21 ` MPhil. Emanoil Kotsev
2013-12-18 20:59 ` MPhil. Emanoil Kotsev
2013-12-18 21:22 ` Borislav Petkov [this message]
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=20131218212233.GE12222@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