linux-kernel - Re: kernel 3.11.6 general protection fault

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 31 Oct 2013 17:44:03 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	emanoil.kotsev@...com.at
Cc:	linux-kernel@...r.kernel.org, intel-gfx@...ts.freedesktop.org
Subject: Re: kernel 3.11.6 general protection fault

Please do not top-post.

On Thu, Oct 31, 2013 at 04:52:54PM +0100, emanoil.kotsev@...com.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.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/