From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 3.13: BUG: unable to handle kernel paging request at 00000000b4343e88
Date: Wed, 29 Jan 2014 16:05:45 +0100 [thread overview]
Message-ID: <52E918C9.7030408@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.SOC.1.00.1401280832500.5459@math.ut.ee>
On 28.01.2014 07:33, Meelis Roos wrote:
>>>>>> It looks like gcov exploded when running a module's constructors or
>>>>>> init function, but I'm unable to work out which module it was :(
>>>>> [...]
>>>>>
>>>>>> Maybe it's tg3.
>>>>>>
>>>>>> Could you add `ignore_loglevel' to the kernel boot parameters? That
>>>>>> should make all pr_debug()s come out and they include the module's
>>>>>> name.
>>>>
>>>> I'm not sure if this related, but all 3 kernel logs consistently contain
>>>> this error message:
>>>>
>>>>> [ 0.617401] gcov: could not create file
>>>>
>>>> which should only be shown in case of severe out-of-memory situations or
>>>> duplicate object file names.
>>>>
>>>> Could you retry with the following patch applied (2 times if possible)
>>>> and send dmesg output?
>>>
>>> This seems to be relevant - now there is a reproducible crash during the
>>> printk. Captured end of the backtrace from HP ILO as image, attached.
>>> This is reproducible.
>>
>> Ok, that's a lead. It appears that gcov-kernel receives gcov_info
>> structures in an unexpected format. Based on your previous dmesg output,
>> your kernel was compiled using gcc 4.7.2 which gcov-kernel should be able
>> to handle just fine. Could you please try out this debugging patch
>> (replacing the previous one)? Output will likely be quite verbose, so you
>> might consider using log_buf_len=1M or similar as kernel parameter.
>
> I do not get very far - it still crashes on startuo. PNG attached.
I tried to reproduce this behavior a couple of times with no success.
Could you post your kernel configuration? I've also modified the
debugging patch to ensure that the gcov_info structure passed to
gcov_init() is no longer accessed beyond displaying the first 64
bytes. If you could apply this and send dmesg output, this might
hopefully provide a clue as to why the kernel cannot handle these
data structures correctly.
diff -Naurp a/kernel/gcov/base.c b/kernel/gcov/base.c
--- a/kernel/gcov/base.c
+++ b/kernel/gcov/base.c
@@ -18,6 +18,7 @@
#include <linux/init.h>
#include <linux/module.h>
#include <linux/mutex.h>
+#include <linux/printk.h>
#include "gcov.h"
static int gcov_events_enabled;
@@ -31,6 +32,10 @@ void __gcov_init(struct gcov_info *info)
{
static unsigned int gcov_version;
+ pr_warn("__gcov_init(%p): enter\n", info);
+ print_hex_dump(KERN_WARNING, "", DUMP_PREFIX_ADDRESS, 16, 4, info,
+ 64, true);
+ return;
mutex_lock(&gcov_lock);
if (gcov_version == 0) {
gcov_version = gcov_info_version(info);
diff -Naurp a/kernel/module.c b/kernel/module.c
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -3003,8 +3003,11 @@ static void do_mod_ctors(struct module *
#ifdef CONFIG_CONSTRUCTORS
unsigned long i;
- for (i = 0; i < mod->num_ctors; i++)
+ for (i = 0; i < mod->num_ctors; i++) {
+ pr_warn("Calling mod(%s)->ctors[%ld]=%p\n", mod->name, i,
+ mod->ctors[i]);
mod->ctors[i]();
+ }
#endif
}
next prev parent reply other threads:[~2014-01-29 15:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 10:34 3.13: BUG: unable to handle kernel paging request at 00000000b4343e88 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 [this message]
[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 ` 3.13: BUG: unable to handle kernel paging request at 00000000b4343e88 Meelis Roos
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=52E918C9.7030408@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.