On 24.06.2020 15:25, Mark Brown wrote:
On Wed, Jun 24, 2020 at 01:41:26PM +0200, Andrzej Hajda wrote:In case of error during resource acquisition driver should print error message only in case it is not deferred probe, using probe_err helper solves the issue. Moreover it records defer probe reason for debugging.If we silently ignore all deferred probe errors we make it hard for anyone who is experiencing issues with deferred probe to figure out what they're missing. We should at least be logging problems at debug level so there's something for people to go on without having to hack the kernel source.
But you can always do:
cat /sys/kernel/debug/devices_deferred
And you will find there deferred probe reason (thanks to patch 2/5).
Eventually if you want it in dmesg anyway, one can adjust probe_err function to log probe error on debug level as well.
Regards
Andrzej
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://protect2.fireeye.com/url?k=ef34cf7b-b2ff4845-ef354434-0cc47a31309a-305676031d9eb553&q=1&u=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fdri-devel
|
|
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel