From: Borislav Petkov <bp@alien8.de>
To: emanoil.kotsev@fincom.at
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: kernel 3.11.6 general protection fault
Date: Thu, 31 Oct 2013 17:44:03 +0100 [thread overview]
Message-ID: <20131031164403.GG10544@pd.tnic> (raw)
In-Reply-To: <cfb4b5e820828e60ad24be359b6e574b@fincom.at>
Please do not top-post.
On Thu, Oct 31, 2013 at 04:52:54PM +0100, emanoil.kotsev@fincom.at wrote:
> Hi, thanks for swift response.
> Yes, without those modules loaded it hangs as well. Perhaps I did
> not understand you well - do you mean unloaded or not
> compiled/installed, or even blacklisted. I tried only with unloading
> them.
Right, try to build a kernel from pristine 3.11.6 sources without any
vmware code patched in or loaded. To be sure, get the sources anew so
that you don't have any remnants of those modules and build the whole
thing from scratch.
AFAIK, those vendor packages have some hooks into the kernel
installation path so make sure you remove those vmware packages too with
your distro's package manager or however they are being removed.
> The custom stuff is vmware nothing else, but if I remember issues
> popped up after compiling/patching vmware/player for 3.10 As I said
> I noticed this recently when I spent more time watching youtube
> videos, but it could be that this only reveals the problem which was
> persistent before (perhaps after vmplayer patch/modules).
Yeah, from the looks of it, it probably would happen if you do other
things too.
> I'm using the Notebook with a docking station - and I have a same
> notebook with different bios version. Does it make sense to try the
> kernel on a different bios version?
Well, since you started seeing this after patching 3.10, I don't think
the BIOS was the problem so no need to do any BIOS updates for now.
HTH.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-10-31 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 14:00 kernel 3.11.6 general protection fault emanoil.kotsev
2013-10-31 14:37 ` Borislav Petkov
2013-10-31 15:52 ` emanoil.kotsev
2013-10-31 16:44 ` Borislav Petkov [this message]
[not found] ` <201311011018.49670.Emanoil.Kotsev@fincom.at>
2013-11-01 11:27 ` Borislav Petkov
2013-11-01 18:08 ` MPhil. Emanoil Kotsev
-- strict thread matches above, loose matches on Subject: below --
2013-11-13 19:58 MPhil. Emanoil Kotsev
2013-10-31 13:34 emanoil.kotsev
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=20131031164403.GG10544@pd.tnic \
--to=bp@alien8.de \
--cc=emanoil.kotsev@fincom.at \
--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