linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: 4.13-rc0: stopped booting on Nokia N900
Date: Mon, 10 Jul 2017 06:06:03 -0700	[thread overview]
Message-ID: <20170710130602.GS3730@atomide.com> (raw)
In-Reply-To: <20170710101608.qdamqomegbjwuweh@earth>

* Sebastian Reichel <sebastian.reichel@collabora.co.uk> [170710 03:16]:
> Hi,
> 
> On Mon, Jul 10, 2017 at 10:13:35AM +0200, Pavel Machek wrote:
> > On Mon 2017-07-10 09:46:10, Pavel Machek wrote:
> > > Hi!
> > > 
> > > First, I got segfault from make:
> > > 
> > > : 0: Can't open
> > > scripts/Makefile.build:561: recipe for target
> > > 'drivers/iio/imu/st_lsm6dsx' failed
> > > make[3]: *** [drivers/iio/imu/st_lsm6dsx] Segmentation fault (core
> > > dumped)
> > > scripts/Makefile.build:561: recipe for target 'drivers/iio/imu' failed
> > > make[2]: *** [drivers/iio/imu] Error 2
> > > scripts/Makefile.build:561: recipe for target 'drivers/iio' failed
> > > make[1]: *** [drivers/iio] Error 2
> > > make[1]: *** Waiting for unfinished jobs....
> > > Makefile:1008: recipe for target 'drivers' failed
> > > make: *** [drivers] Error 2
> > > make: *** Waiting for unfinished jobs....
> > > pavel at duo:/data/l/linux-n900$ ./mkit
> > > 
> > > Then compile worked, but it failed to boot. I've now cleaned caches
> > > and am rebuilding to make sure it is not build machine that has
> > > glitches.
> > > 
> > > No such luck :-(.
> > > 
> > > I tested linux-next relatively recently, and it worked ok.
> > 
> > > af3c8d98508d37541d4bf57f13a984a7f73a328c is broken.
> > > 650fc87 worked ok.
> > 
> > 2b97620 is broken.
> > 
> > commit a51166ce71844ffbb8f78d63647b44dd69e46cf1
> >     Add linux-next specific files for 20170628
> 
> I just rebased my droid4 development branch. I do not have any
> problems with segfaulting toolchain, but boot also fails on OMAP4
> based Droid 4. The problem seems to be SPI being accessed without
> runtime PM (clocks) being enabled:

Care to check if commit c5b3955828ba ("ARM: OMAP4: Fix legacy code
clean-up regression") make that one go away? I have already sent
a pull request for that one.

Regards,

Tony

  reply	other threads:[~2017-07-10 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  7:46 4.13-rc0: stopped booting on Nokia N900 Pavel Machek
2017-07-10  8:13 ` Pavel Machek
2017-07-10 10:02   ` Tony Lindgren
2017-07-10 12:55     ` Sebastian Reichel
2017-07-10 10:16   ` Sebastian Reichel
2017-07-10 13:06     ` Tony Lindgren [this message]
2017-07-10 13:36       ` Sebastian Reichel
2017-07-10 13:46         ` Tony Lindgren

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=20170710130602.GS3730@atomide.com \
    --to=tony@atomide.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 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).