From: Arjan van de Ven <arjan@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: linux-next: revert of "debug: add notifier chain debugging"
Date: Mon, 01 Sep 2008 07:23:58 -0700 [thread overview]
Message-ID: <48BBFAFE.7030808@linux.intel.com> (raw)
In-Reply-To: <20080901182619.cb799b52.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> I have reverted commit 16f9b13de93c8bfdac16b4d15577af2c132358ef ("debug:
> add notifier chain debugging") for today hate typing thas it prevents Powerpc kernels
> from booting. There is (I think) a bug there (__devinit routines are not
> put in the right section as pointed otu by David Woodhouse), but not a
> fatal bug and the above commit makes it one.
well it's a pretty bad bug since there are many places that depend on the kernel text stuff to work.
(backtracing, lockdep, some of the security checks etc). PPC needs to be fixed rather urgently.
but yeah the system kept plodding on.
David also sent a patch to fix it fwiw.
I'm a bit sad to see a debug patch get reverted just because it caught bugs ;-)
at least I assume this is very temporary.
next prev parent reply other threads:[~2008-09-01 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 8:26 linux-next: revert of "debug: add notifier chain debugging" Stephen Rothwell
2008-09-01 14:23 ` Arjan van de Ven [this message]
2008-09-02 8:33 ` Stephen Rothwell
2008-09-02 17:57 ` David Woodhouse
2008-09-02 18:00 ` David Woodhouse
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=48BBFAFE.7030808@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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.