From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: David Miller <davem@davemloft.net>,
lkml <linux-kernel@vger.kernel.org>,
sparclinux <sparclinux@vger.kernel.org>
Subject: Re: sparc boot failure due to perf init
Date: Fri, 7 Jan 2011 21:31:19 +0100 [thread overview]
Message-ID: <20110107203119.GA30408@merkur.ravnborg.org> (raw)
In-Reply-To: <1294432055.2016.458.camel@laptop>
On Fri, Jan 07, 2011 at 09:27:35PM +0100, Peter Zijlstra wrote:
> On Fri, 2011-01-07 at 21:23 +0100, Peter Zijlstra wrote:
> > On Fri, 2011-01-07 at 21:18 +0100, Sam Ravnborg wrote:
> > > This was introduced by:
> > > "perf, arch: Cleanup perf-pmu init vs lockup-detector" - 004417a6d468e24399e383645c068b498eed84ad
> > >
> > > I did not see any obvious fix.
> > > (To avoid it is simple - I can disable it in my config).
> >
> > Or you can switch back to arch_initcall() for now, it'll cause the
> > generic watchdog stuff not to work, but that's a lot less important.
> >
> > I'll have a chat with Dave on how to best sort all this.
>
> That is, simply revert the sparc bit for now.
For now I just disabled the option as I am trying to
debug a console related problem and do not need the
perf_event support (or at least I do not know I need it :-) ).
Then you guys can sort it out and I can test any patches
you come up with.
Sam
next prev parent reply other threads:[~2011-01-07 20:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 20:18 sparc boot failure due to perf init Sam Ravnborg
2011-01-07 20:22 ` Sam Ravnborg
2011-01-07 20:23 ` Peter Zijlstra
2011-01-07 20:27 ` Peter Zijlstra
2011-01-07 20:31 ` Sam Ravnborg [this message]
2011-01-09 23:37 ` David Miller
2011-01-10 15:21 ` Peter Zijlstra
2011-01-13 10:55 ` Peter Zijlstra
2011-01-13 12:25 ` Sam Ravnborg
2011-01-13 12:33 ` Peter Zijlstra
2011-01-13 20:25 ` David Miller
2011-01-08 2:23 ` David Miller
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=20110107203119.GA30408@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.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