What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
Resolution | --- | WORKSFORME |
This issue was detected on 4.18.3 when using a somewhat reduced developer config. When using our usual full distro kernel config (from Ubuntu), the issue convincingly goes away. Both Jian-Hong and I looked at the differences in the config and couldn't spot anything obvious that would explain different behaviour. There's probably a bug here somewhere, but as it's working on our shipped config I'll close this issue, as we need to focus our time on other issues on this platform.