On Mon, May 23, 2016 at 04:40:47PM +0200, Steinar H. Gunderson wrote: > On Mon, May 23, 2016 at 03:47:37PM +0200, Steinar H. Gunderson wrote: > > In this case, it's not just an annoyance, though; they're so many that they > > keep the system from booting unless loglevel is turned down. Cc-ing Mark in > > case he has any insights (I hope I have the right email address). But nobody who works on probe deferral or made any of the suggestions I mentioned in the message you linked to, nor anyone who works on the driver you've identified a bug in... :( > > I don't understand entirely why it tries 2000+ times before it succeeds > Now I do; the initramfs doesn't include i2c-exynos5, and before that is > loaded, s2mps11 (the regulator) can't come up either. > So fixing initramfs-tools to include the driver will seemingly fix (or maybe > more work around) the huge amounts of spam, but this is still a larger issue > that needs resolving. Not really, the issue you're seeing is just a plain resource leak in the driver that happens to blow up worse than normal in your particular configuration. This isn't even something related to probe deferral at the regulator level, the core is complaining that your system description is buggy as it has omitted some of the supplies for the device (notice how it says "using dummy regulator"...). This is happening a lot as the DWC3 driver is leaking, it is happening at all because when the Exynos DWC3 integration creates it PHYs it doesn't map the supplies through to them (it should be registering a supply alias to do this). The patch you linked to was for a completely different error message which is at least related to probe deferral, though fundamentally unless we just stop printing diagnostics (which is getting more and more tempting to be honest) I'm not sure anything is going to fully resolve leaks like this, the best chance you've got is something that explicitly looks at the dependencies like Raphael was proposing.
Attachment:
signature.asc
Description: PGP signature