From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer
Date: Tue, 03 Jan 2012 19:02:53 -0500 [thread overview]
Message-ID: <1325635373.12696.4.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120102134856.GA32673@elte.hu>
On Mon, 2012-01-02 at 14:48 +0100, Ingo Molnar wrote:
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > Just to give you an impression of how a failure looks like, the
> > serial console just stops printing mid-line:
> >
> > [ 53.212942] calling vt1211_init+0x0/0x9b @ 1
> > [ 53.212971] initcall vt1211_init+0x0/0x9b returned -19 after 23 usecs
> > [ 53.212975] calling sm_vt8231_init+0x0/0x1b @ 1
> > Booting 'Fedora'
> >
> > and the next message is GRUB's 'Booting ...' line.
>
> here's another one:
>
> [ 53.224579] calling sm_via686a_init+0x0/0x1b @ 1
> [ 53.224622] bus: 'pci': add driver via686a
> Booting 'Fedora
>
> This occured after a series of 50 successful bootups ...
>
> Unfortunately this means that the 'baseline' numbers are
> probably not reliable.
Hi Ingo,
I have a machine that seems to lock up 100% of the time when the bad
commit is used.
I started with tip/master (1bc2a3035df) and merged in my branch (this
patch set) and applied your config and it locks up in different places.
I booted it 4 times, and it locked up 4 times.
Then I tried your config against my branch, and I booted it 10 times
without failure. Can you crash it with just my branch?
I then tried it against just tip/master, and it again locked up the two
times I booted it.
I then looked at the merge you did with Linus's branch:
c7f46b7aa4ae5cbef32eb5e016512a14f936affa
Checked that out, and booted it twice with your config, and it booted
without failure both times.
I'm currently running a ktest git bisect and will let it run over night.
As building a allyesconfig takes a bit of time. I'm hoping that it will
be done by tomorrow.
-- Steve
next prev parent reply other threads:[~2012-01-04 0:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 12:36 Steven Rostedt
2011-12-21 12:36 ` [PATCH 01/16] ftrace: Fix unregister ftrace_ops accounting Steven Rostedt
2011-12-21 12:36 ` [PATCH 02/16] ftrace: Do not function trace inlined functions Steven Rostedt
2011-12-21 12:36 ` [PATCH 03/16] ftrace: Allow archs to modify code without stop machine Steven Rostedt
2011-12-21 12:36 ` [PATCH 04/16] ftrace: Remove usage of "freed" records Steven Rostedt
2011-12-21 12:36 ` [PATCH 05/16] ftrace: Allocate the mcount record pages as groups Steven Rostedt
2011-12-21 12:36 ` [PATCH 06/16] ftrace: Replace record newlist with record page list Steven Rostedt
2011-12-21 12:36 ` [PATCH 07/16] ftrace: Sort the mcount records on each page Steven Rostedt
2011-12-21 12:36 ` [PATCH 08/16] ftrace: Use bsearch to find record ip Steven Rostedt
2011-12-21 12:36 ` [PATCH 09/16] ftrace: Fix ftrace hash record update with notrace Steven Rostedt
2011-12-21 12:36 ` [PATCH 10/16] ftrace: Create ftrace_hash_empty() helper routine Steven Rostedt
2011-12-21 12:36 ` [PATCH 11/16] ftrace: Allow other users of function tracing to use the output listing Steven Rostedt
2011-12-21 12:36 ` [PATCH 12/16] ftrace: Decouple hash items from showing filtered functions Steven Rostedt
2011-12-21 12:36 ` [PATCH 13/16] tracing: Have stack_tracer use a separate list of functions Steven Rostedt
2011-12-21 12:36 ` [PATCH 14/16] ftrace: Allow access to the boot time function enabling Steven Rostedt
2011-12-21 12:36 ` [PATCH 15/16] tracing: Have stack tracing set filtered functions at boot Steven Rostedt
2011-12-21 12:36 ` [PATCH 16/16] tracing: Factorize filter creation Steven Rostedt
2012-01-01 18:09 ` [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer Ingo Molnar
2012-01-02 10:58 ` Ingo Molnar
2012-01-02 13:48 ` Ingo Molnar
2012-01-02 15:10 ` Ingo Molnar
2012-01-04 0:02 ` Steven Rostedt [this message]
2012-01-04 0:12 ` Steven Rostedt
2012-01-04 5:01 ` Steven Rostedt
2012-01-04 14:11 ` Ingo Molnar
2012-01-04 17:05 ` Steven Rostedt
2012-01-04 18:39 ` Ingo Molnar
2012-01-05 9:19 ` Ingo Molnar
2012-01-05 11:46 ` Steven Rostedt
2012-01-05 12:16 ` Steven Rostedt
2012-01-06 4:58 ` Steven Rostedt
2012-01-06 8:51 ` Ingo Molnar
2012-01-06 12:10 ` Steven Rostedt
2012-01-06 15:29 ` Steven Rostedt
2012-01-07 12:20 ` Ingo Molnar
2012-01-07 12:25 ` Ingo Molnar
2012-01-07 22:32 ` Steven Rostedt
2012-01-08 11:38 ` Ingo Molnar
2012-01-02 19:33 ` Steven Rostedt
2012-01-06 5:04 ` Steven Rostedt
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=1325635373.12696.4.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®