From b143433180ad0f4100a9e5d5ad1e6255f0a64622 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?= Date: Mon, 3 Aug 2026 05:08:01 +0200 Subject: [PATCH] xen/xenbus: log more information when device state got reset MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ease diagnosing what actually changed. Signed-off-by: Marek Marczykowski-Górecki Reviewed-by: Juergen Gross Signed-off-by: Juergen Gross Message-ID: <20260803030822.4104093-1-marmarek@invisiblethingslab.com> --- 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 fafb2b84fa5c..111849756e0c 100644 --- a/drivers/xen/xenbus/xenbus_probe.c +++ b/drivers/xen/xenbus/xenbus_probe.c @@ -687,7 +687,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) {