diff options
| author | Chen Yu <[email protected]> | 2016-12-21 17:24:55 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2017-01-11 09:29:33 +0100 |
| commit | 8a18f4284ec94ec56189e7f14495359d3b892a52 (patch) | |
| tree | 209951c6bc4265097a8b79ec39d24d6bcffb8b6b /scripts/gdb/linux/tasks.py | |
| parent | a0244a8df15d8caee8831872b6fc97b676cb15bd (diff) | |
platform: Print the resource range if device failed to claim
Sometimes we have the following error message:
platform MSFT0101:00: failed to claim resource 1
acpi MSFT0101:00: platform device creation failed: -16
But there is not enough information to figure out which resource range
failed to claim.
Thus print the resource range at first-place thus /proc/iomem or
ioports should tell us who already claimed this resource, then
the driver bug or incorrect resource assignment which is running
into this conflict can be diagnosed:
platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
acpi MSFT0101:00: platform device creation failed: -16
Suggested-by: Len Brown <[email protected]>
Reported-by: Wendy Wang <[email protected]>
Signed-off-by: Chen Yu <[email protected]>
Reviewed-by: Mika Westerberg <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/tasks.py')
0 files changed, 0 insertions, 0 deletions