|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [PATCH 1/2] xen/xenbus: log more information when device state got reset
Ease diagnosing what actually changed.
Signed-off-by: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>
---
drivers/xen/xenbus/xenbus_probe.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/xen/xenbus/xenbus_probe.c
b/drivers/xen/xenbus/xenbus_probe.c
index eb260eceb4d2..a259c8f0fff4 100644
--- a/drivers/xen/xenbus/xenbus_probe.c
+++ b/drivers/xen/xenbus/xenbus_probe.c
@@ -686,7 +686,8 @@ void xenbus_dev_changed(const char *node, struct
xen_bus_type *bus)
* and new one needs to be probed.
*/
dev_warn(&dev->dev,
- "state reset occurred, reconnecting\n");
+ "state reset occurred (xenstore state %u,
local state %u, xenstore backend %u, local backend %u), reconnecting\n",
+ state, dev->state, backend, dev->otherend_id);
dev->vanished = true;
}
if (dev->vanished) {
--
2.54.0
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |