From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: linux-parisc@vger.kernel.org
Subject: Re: linux-next boot failure
Date: Mon, 21 Mar 2011 11:37:29 -0500 [thread overview]
Message-ID: <1300725449.10634.23.camel@mulgrave.site> (raw)
In-Reply-To: <20110320201614.GA25287@hiauly1.hia.nrc.ca>
On Sun, 2011-03-20 at 16:16 -0400, John David Anglin wrote:
> The current linux-next tree fails to boot on parisc. I have seen
> the same panic on two different systems. 2.6.38-rc5-next-20110218
> is ok. 2.6.38-rc8-next-20110311 failed to boot. The backtrace is
> the same in all cases.
I don't see this in get head as of this morning, so it's likely in an
unmerged branch. If you can find it, I might be able to have the
culprit fix it before it does get merged.
James
P.S. I also try not to run -next around the merge window, because it
gets very unstable (all the rules violators trying to get a last fix in)
prev parent reply other threads:[~2011-03-21 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 20:16 linux-next boot failure John David Anglin
2011-03-21 16:37 ` James Bottomley [this message]
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=1300725449.10634.23.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=linux-parisc@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