From: Meelis Roos <mroos@linux.ee>
To: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 3.13: BUG: unable to handle kernel paging request at 00000000b4343e88
Date: Thu, 6 Feb 2014 08:19:05 +0200 (EET) [thread overview]
Message-ID: <alpine.SOC.1.00.1402060818330.10122@math.ut.ee> (raw)
In-Reply-To: <52F26E21.8000101@linux.vnet.ibm.com>
> > Using your config I was able to reproduce the crash and locate the
> > cause. Commit d61931d89b, "x86: Add optimized popcnt variants" adds
> > option -fcall-saved-rdi to the compile flags of lib/hweight.c when
> > compiling for x86_64. Together with options --coverage and -O2, this
> > results in a broken constructor being generated by GCC for this object
> > file which in turn causes __gcov_init() to overwrite random memory
> > locations (a mutex in your case).
>
> Could you give this patch a try? It is a variation of the approach
> proposed in the discussion mentioned earlier and fixes the problem
> on my system.
It works for me too - the machine booted up with no problem.
--
Meelis Roos (mroos@linux.ee)
prev parent reply other threads:[~2014-02-06 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 10:34 Meelis Roos
2014-01-21 22:10 ` Andrew Morton
2014-01-22 15:33 ` Meelis Roos
2014-01-24 13:47 ` Peter Oberparleiter
2014-01-24 20:54 ` Meelis Roos
2014-01-27 15:53 ` Peter Oberparleiter
2014-01-28 6:33 ` Meelis Roos
2014-01-29 15:05 ` Peter Oberparleiter
[not found] ` <alpine.SOC.1.00.1401292242390.12718@math.ut.ee>
2014-01-31 15:50 ` Peter Oberparleiter
2014-02-05 17:00 ` Peter Oberparleiter
2014-02-05 17:36 ` H. Peter Anvin
2014-02-06 14:58 ` Peter Oberparleiter
2014-02-06 15:18 ` [tip:x86/urgent] x86, hweight: Fix BUG when booting with CONFIG_GCOV_PROFILE_ALL=y tip-bot for Peter Oberparleiter
2014-02-06 6:19 ` Meelis Roos [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=alpine.SOC.1.00.1402060818330.10122@math.ut.ee \
--to=mroos@linux.ee \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oberpar@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®