linux-kernel - Re: 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>] [day] [month] [year] [list]

Message-ID: <CALYGNiPqcFxZp_WJYx4XV8TWkvsjs3XihSqLeP1=ZHU3xqrmOw@mail.gmail.com>
Date:	Wed, 21 May 2014 01:44:27 +0400
From:	Konstantin Khlebnikov <koct9i@...il.com>
To:	Martin <martin@...inoussheep.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: General protection fault - bug report 3.12.18

On Tue, May 20, 2014 at 11:40 PM, Martin <martin@...inoussheep.net> wrote:
>> I've looked into second crash. Just because gmail has marked that
>> email as important for some reason =)
>>
>> In function tid_fd_revalidate(), in line "file = fcheck_files(files,
>> fd)" file = is 0x0000000004000000 instead of valid pointer or NULL.
>> This value has only one non-zero bit, so this looks like memory
>> curruption.
>>
>> More likely this is hardware problem. Please check you memory with
>> memtest86 and/or try to replace it.
>
> Many thanks for looking into this, I was a bit worried that would be the
> answer as I've seen other crashes in what seem like random places.
>
> I already ran memtest86+ and it ran clean overnight and all day, so I
> thought it might just be a kernel bug still.
>
> Any other ideas how I could prove it to be a hardware issue?

I guess, only by replacing pieces.
As I see this is Lenovo Yoga2, this reminds me recent problems in
their firmware in T540 (or so).

You could run user-space memory tester like "memtester" in backround
while linux works.
Maybe it could catch that memory corruption. Probably it appears only
in particular situation.

>
> Regards,
> M
>
>
>
--
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/