From: "Witold Baryluk" <baryluk@smp.if.uj.edu.pl>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <andi@firstfloor.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Ingo Molnar <mingo@redhat.com>, John Stultz <johnstul@us.ibm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel OOPS in function_graph_tracer due to the 44259b1. More oopses in tracing...
Date: Tue, 31 May 2011 01:46:54 +0200 [thread overview]
Message-ID: <20110530234654.GB14366@smp.if.uj.edu.pl> (raw)
In-Reply-To: <BANLkTi=7k4XbK6JVDp3oOJRAK_7Ox=aWMw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2224 bytes --]
On 05-30 16:14, Andrew Lutomirski wrote:
> On Mon, May 30, 2011 at 12:10 PM, Witold Baryluk
> <baryluk@smp.if.uj.edu.pl> wrote:
> > Hi,
> >
> > I found yesterday a problem when booting system on Pentium-M, 32-bit.
> >
> > I got approximetly this
> >
> > [ 2.459170] Testing tracer function_graph:
> > [ 2.466979] BUG: unable to handle kernel paging request at e421cc10
>
> >
> > Reverting commit 44259b1abfaa8bb819d25d41d71e8e33e25dd36a on top of current
> > kernel make bug disapear.
> >
> > Disabling CONFIG_FUNCTION_GRAPH_TRACER also make bug dispear.
> >
>
> Of course, the most trivial of my patches was the one with the most
> significant bug. Can you try this fix:
>
> http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commitdiff;h=89e1be50c68eb5e58b873dce87bbac627ee18d1f
>
> --Andy
Well, to add more.
It fixed most of crashes and definietl one with function graph tracer.
However in 1/10 of boots I still got some kind of crash, oops or panic.
I repeated 50 times a boot cycle on qemu, and got oopses in attachments.
...
[ 0.036201] CPU: Intel Pentium III (Katmai) stepping 03
[ 0.038551] ftrace: allocating 6263 entries in 13 pages
[ 0.050411] BUG: unable to handle kernel NULL pointer dereference at 00000012
[ 0.051079] IP: [<c106a07f>] note_interrupt+0xf/0x1c0
[ 0.051743] *pdpt = 0000000000000000 *pde = f000ff53f000ff53
...
CRASH
....
[ 0.035682] CPU: Intel Pentium III (Katmai) stepping 03
[ 0.038048] ftrace: allocating 6263 entries in 13 pages
[ 0.050386] BUG: unable to handle kernel paging request at 8a51553a
[ 0.051031] IP: [<c10587cd>] tick_handle_periodic+0x1d/0x90
[ 0.051705] *pdpt = 0000000000000000 *pde = f000ff53f000ff53
...
CRASH
...
[ 1.758224] Testing tracer preemptirqsoff:
[ 1.772287] ------------[ cut here ]------------
[ 1.773193] WARNING: at kernel/lockdep.c:3351 check_flags+0x186/0x190()
...
BOOTING (up to mounting root - not tested more)
...
[ 0.045767] CPU: Intel Pentium III (Katmai) stepping 03
[ 0.048323] ftrace: allocating 6263 entries in 13 pages
CRASH
Details in attachments.
Regards,
Witek
--
Witold Baryluk
[-- Attachment #1.2: config.txt.gz --]
[-- Type: application/octet-stream, Size: 6095 bytes --]
[-- Attachment #1.3: oops1.txt.gz --]
[-- Type: application/octet-stream, Size: 1761 bytes --]
[-- Attachment #1.4: oops2.txt.gz --]
[-- Type: application/octet-stream, Size: 1806 bytes --]
[-- Attachment #1.5: oops3.txt.gz --]
[-- Type: application/octet-stream, Size: 2216 bytes --]
[-- Attachment #1.6: oops4.txt.gz --]
[-- Type: application/octet-stream, Size: 356 bytes --]
[-- Attachment #1.7: oops5.txt.gz --]
[-- Type: application/octet-stream, Size: 3335 bytes --]
[-- Attachment #1.8: oops6.txt.gz --]
[-- Type: application/octet-stream, Size: 3332 bytes --]
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-30 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 16:10 Kernel OOPS in function_graph_tracer due to the 44259b1abfaa8bb819d25d41d71e8e33e25dd36a commit (x86-64: Move vread_tsc into a new file with sensible options) Witold Baryluk
2011-05-30 20:14 ` Andrew Lutomirski
2011-05-30 22:19 ` Witold Baryluk
2011-05-30 23:46 ` Witold Baryluk [this message]
2011-05-31 1:23 ` Kernel OOPS in function_graph_tracer due to the 44259b1. More oopses in tracing Andrew Lutomirski
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=20110530234654.GB14366@smp.if.uj.edu.pl \
--to=baryluk@smp.if.uj.edu.pl \
--cc=andi@firstfloor.org \
--cc=eric.dumazet@gmail.com \
--cc=hpa@zytor.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®