From: Paul Mackerras <paulus@samba.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org, Nathan Lynch <ntl@pobox.com>
Subject: Re: 2.6.20-rc4 Kernel Oops on Maple
Date: Tue, 9 Jan 2007 18:48:19 +1100 [thread overview]
Message-ID: <17827.18627.560100.376047@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1168326195.14763.312.camel@shinybook.infradead.org>
David Woodhouse writes:
> > http://patchwork.ozlabs.org/linuxppc/patch?id=8840
>
> ... which triggers a WARN_ON() which is _supposed_ to be otherwise
> harmless. Unfortunately due to another bug in BUG() handling, the
> warning actually kills the machine instead of just bitching a bit:
> http://patchwork.ozlabs.org/linuxppc/patch?id=8811
Both of those are in my queue to go to Linus very soon.
Paul.
next prev parent reply other threads:[~2007-01-09 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 20:43 2.6.20-rc4 Kernel Oops on Maple Owen Stampflee
2007-01-08 21:04 ` Nathan Lynch
2007-01-09 7:03 ` David Woodhouse
2007-01-09 7:48 ` Paul Mackerras [this message]
2007-01-09 0:40 ` Benjamin Herrenschmidt
2007-01-09 1:17 ` Owen Stampflee
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=17827.18627.560100.376047@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).