Re: next/master boot: 177 boots: 1 failed, 176 passed (next-20180808)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tony Lindgren <tony@xxxxxxxxxxx> writes:

> * Kevin Hilman <khilman@xxxxxxxxxxxx> [180815 17:14]:
>> Mark Brown <broonie@xxxxxxxxxx> writes:
>> 
>> > On Thu, Aug 09, 2018 at 12:33:48AM -0700, Tony Lindgren wrote:
>> >> * Mark Brown <broonie@xxxxxxxxxx> [180808 14:17]:
>> >
>> >> > The diffstat from yesterday is very light, nothing jumps out as being
>> >> > a likely cause.
>> >
>> >> Could it be a bad MMC card?
>> >
>> > It's possible, it's Kevin's lab so he'd need to take a look.
>> >
>> 
>> I changed MMC cards, and it's happier now.
>
> OK
>
>> What's strange is that it was succesfully loading/booting u-boot from
>> MMC, and the card and partitions etc looked fine in a linux pc.
>> Anyways, it's changed out now.
>
> Weird. I guess it's still possible we have some regression
> for lower voltage cards then.

Hmm, I think I spoke to soon, and now I don't think it's the MMC card.

I'm still seeing periodic failures on this board soon after the MMC
init, but only in mainline and next:
https://kernelci.org/boot/omap3-beagle-xm

Also, looking at that URL, you'll see that the failures are only for
multi_v7 but not omap2plus_defconfig.

The step that seems to be happening right after MMC init is unused
regulators being disabled.  Is it possible that multi_v7 is missing some
regulator setup?

Also, the last line in the failure case:

  leds_pwm pwmleds: unable to request PWM for beagleboard::pmu_stat: -517

doesn't happen on the successful omap2plus_defconfig boots either.

Kevin



[Index of Archives]     [Linux Memonry Technology]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux