All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Boot breaks in -next from LEGACY to LINEAR conversion
Date: Wed, 18 Jul 2012 11:16:13 +0100	[thread overview]
Message-ID: <20120718101612.GE22739@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120718005230.GA15680@linux-sh.org>

On Wed, Jul 18, 2012 at 09:52:30AM +0900, Paul Mundt wrote:
> On Tue, Jul 17, 2012 at 07:57:49PM +0100, Mark Brown wrote:

> > -next fails to boot for me today on my s3c64xx based systems.  Walking
> > back to the last time I tried and bisecting likely branches I find that
> > commit 910139 (irqdomain: Replace LEGACY mapping with LINEAR) is the one
> > that introduces the build break.  Unfortunately the boot fails before I
> > get a console which makes diagnosis somewhat more tricky than would be
> > ideal.  Any ideas?

> Does http://www.spinics.net/lists/linux-sh/msg11995.html fix it for you?

> I did Cc you on the legacy -> linear thread, but perhaps you missed it.

I do remember seeing it, it's a big part of how I isolated that this
patch series was the issue.  To be honest I hadn't got terribly far with
the diagnosis of what the actual breakage is, it took a while to isolate
as it had been a little while since I'd rebased through onto -next and
there's no diagnostics at all from the system when it fails.

I tried applying the patch but the underlying code has changed a lot so
patch gets upset, I'll try to find time to resolve them but can't
guarantee when as things are especially hectic right now.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120718/28ea8fb1/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Rob Herring <rob.herring@calxeda.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: Boot breaks in -next from LEGACY to LINEAR conversion
Date: Wed, 18 Jul 2012 11:16:13 +0100	[thread overview]
Message-ID: <20120718101612.GE22739@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120718005230.GA15680@linux-sh.org>

[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]

On Wed, Jul 18, 2012 at 09:52:30AM +0900, Paul Mundt wrote:
> On Tue, Jul 17, 2012 at 07:57:49PM +0100, Mark Brown wrote:

> > -next fails to boot for me today on my s3c64xx based systems.  Walking
> > back to the last time I tried and bisecting likely branches I find that
> > commit 910139 (irqdomain: Replace LEGACY mapping with LINEAR) is the one
> > that introduces the build break.  Unfortunately the boot fails before I
> > get a console which makes diagnosis somewhat more tricky than would be
> > ideal.  Any ideas?

> Does http://www.spinics.net/lists/linux-sh/msg11995.html fix it for you?

> I did Cc you on the legacy -> linear thread, but perhaps you missed it.

I do remember seeing it, it's a big part of how I isolated that this
patch series was the issue.  To be honest I hadn't got terribly far with
the diagnosis of what the actual breakage is, it took a while to isolate
as it had been a little while since I'd rebased through onto -next and
there's no diagnostics at all from the system when it fails.

I tried applying the patch but the underlying code has changed a lot so
patch gets upset, I'll try to find time to resolve them but can't
guarantee when as things are especially hectic right now.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-18 10:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17 18:57 Boot breaks in -next from LEGACY to LINEAR conversion Mark Brown
2012-07-17 18:57 ` Mark Brown
2012-07-18  0:52 ` Paul Mundt
2012-07-18  0:52   ` Paul Mundt
2012-07-18 10:16   ` Mark Brown [this message]
2012-07-18 10:16     ` Mark Brown
2012-07-18 16:10 ` Mark Brown
2012-07-18 16:10   ` Mark Brown
2012-07-18 16:27   ` Grant Likely
2012-07-18 16:27     ` Grant Likely
2012-07-20  4:30   ` Grant Likely
2012-07-20  4:30     ` Grant Likely
2012-07-20  9:42     ` Mark Brown
2012-07-20  9:42       ` Mark Brown

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=20120718101612.GE22739@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.