| Message ID | 1444909328-24761-1-git-send-email-tomeu.vizoso@collabora.com |
|---|---|
| State | Changes Requested, archived |
| Headers | show |
Hi, I've bisected boot failures in next-20151016 down to patches in this branch: On Thu, Oct 15, 2015 at 4:42 AM, Tomeu Vizoso <tomeu.vizoso@collabora.com> wrote: > Tomeu Vizoso (20): > driver core: handle -EPROBE_DEFER from bus_type.match() The machine it happened on was OMAP5UEVM: http://arm-soc.lixom.net/bootlogs/next/next-20151016/omap5uevm-arm-omap2plus_defconfig.html But I've also seen it on tegra2, that one bisected down to: > regulator: core: Probe regulators on demand http://arm-soc.lixom.net/bootlogs/next/next-20151016/seaboard-arm-multi_v7_defconfig.html -Olof -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Oct 16, 2015 at 4:23 PM, Olof Johansson <olof@lixom.net> wrote: > Hi, > > I've bisected boot failures in next-20151016 down to patches in this branch: > > On Thu, Oct 15, 2015 at 4:42 AM, Tomeu Vizoso > <tomeu.vizoso@collabora.com> wrote: >> Tomeu Vizoso (20): >> driver core: handle -EPROBE_DEFER from bus_type.match() > > The machine it happened on was OMAP5UEVM: > > http://arm-soc.lixom.net/bootlogs/next/next-20151016/omap5uevm-arm-omap2plus_defconfig.html So this one is because the MMC node numbering changed. I don't know how to fix that other than with aliases, but that doesn't solve backwards compatibility. > But I've also seen it on tegra2, that one bisected down to: > >> regulator: core: Probe regulators on demand > > http://arm-soc.lixom.net/bootlogs/next/next-20151016/seaboard-arm-multi_v7_defconfig.html This one you need a rootwait I think. The MMC scanning is not guaranteed to be done before the rootfs mounting AFAIK. There may be other problems, but we can't see them since it panics. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, Oct 17, 2015 at 8:19 AM, Rob Herring <robh+dt@kernel.org> wrote: > On Fri, Oct 16, 2015 at 4:23 PM, Olof Johansson <olof@lixom.net> wrote: >> Hi, >> >> I've bisected boot failures in next-20151016 down to patches in this branch: >> >> On Thu, Oct 15, 2015 at 4:42 AM, Tomeu Vizoso >> <tomeu.vizoso@collabora.com> wrote: >>> Tomeu Vizoso (20): >>> driver core: handle -EPROBE_DEFER from bus_type.match() >> >> The machine it happened on was OMAP5UEVM: >> >> http://arm-soc.lixom.net/bootlogs/next/next-20151016/omap5uevm-arm-omap2plus_defconfig.html > > So this one is because the MMC node numbering changed. I don't know > how to fix that other than with aliases, but that doesn't solve > backwards compatibility. Yep, aliases will take care of it in this case. This is where -next fills a great purpose, we can make sure we get those aliases added in before the patches go in. >> But I've also seen it on tegra2, that one bisected down to: >> >>> regulator: core: Probe regulators on demand >> >> http://arm-soc.lixom.net/bootlogs/next/next-20151016/seaboard-arm-multi_v7_defconfig.html > > This one you need a rootwait I think. The MMC scanning is not > guaranteed to be done before the rootfs mounting AFAIK. There may be > other problems, but we can't see them since it panics. Embarrassing, I almost always do this and I'm surprised this machine has been this stable without it. -Olof -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi, this second pull request replaces the last references to device_initcall_sync with late_initcall, as noticed by Frank Rowand. Also fixes the url of the git repo and the wrapping, as suggested by Mark Brown. Thanks, Tomeu The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f: Linux 4.3-rc1 (2015-09-12 16:35:56 -0700) are available in the git repository at: git://git.collabora.com/git/user/tomeu/linux.git on-demand-probes-for-next for you to fetch changes up to c074fef5d36e1c27dfdf7474e23c01a1b044ff98: of/platform: Defer probes of registered devices (2015-10-15 13:25:47 +0200) ---------------------------------------------------------------- Tomeu Vizoso (20): driver core: handle -EPROBE_DEFER from bus_type.match() ARM: amba: Move reading of periphid to amba_match() of/platform: Point to struct device from device node of: add function to allow probing a device from a OF node gpio: Probe GPIO drivers on demand pinctrl: Probe pinctrl devices on demand regulator: core: Probe regulators on demand drm: Probe panels on demand drm/tegra: Probe dpaux devices on demand i2c: core: Probe i2c adapters and devices on demand pwm: Probe PWM chip devices on demand backlight: Probe backlight devices on demand usb: phy: Probe phy devices on demand clk: Probe clk providers on demand pinctrl: Probe pinctrl devices on demand phy: core: Probe phy providers on demand dma: of: Probe DMA controllers on demand power-supply: Probe power supplies on demand driver core: Allow deferring probes until late init of/platform: Defer probes of registered devices drivers/amba/bus.c | 88 +++++++++++++++++++------------------ drivers/base/Kconfig | 18 ++++++++ drivers/base/dd.c | 30 ++++++++++++- drivers/clk/clk.c | 3 ++ drivers/dma/of-dma.c | 3 ++ drivers/gpio/gpiolib-of.c | 5 +++ drivers/gpu/drm/drm_panel.c | 3 ++ drivers/gpu/drm/tegra/dpaux.c | 3 ++ drivers/i2c/i2c-core.c | 4 ++ drivers/of/device.c | 61 +++++++++++++++++++++++++ drivers/of/platform.c | 30 ++++++++----- drivers/phy/phy-core.c | 3 ++ drivers/pinctrl/devicetree.c | 3 ++ drivers/power/power_supply_core.c | 3 ++ drivers/pwm/core.c | 3 ++ drivers/regulator/core.c | 2 + drivers/usb/phy/phy.c | 3 ++ drivers/video/backlight/backlight.c | 3 ++ include/linux/device.h | 4 +- include/linux/of.h | 1 + include/linux/of_device.h | 3 ++ 21 files changed, 219 insertions(+), 57 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html