Knowing which modules are loaded can be useful.
/proc/modules is slightly less human-readable than the output of
"lsmod", but also includes the load address, which might plausibly be
useful for decoding a stack trace (although I've never used it for
that myself)
Signed-off-by: Ian Campbell <ian.campb...@citrix.com>
---
ts-logs-capture | 1 +
1 file changed, 1 insertion(+)
diff --git a/ts-logs-capture b/ts-logs-capture
index ab6750d..cb0d371 100755
--- a/ts-logs-capture
+++ b/ts-logs-capture
@@ -202,6 +202,7 @@ sub fetch_logs_host () {
'cat /proc/partitions',
'virsh capabilities',
'cat /proc/self/limits',
+ 'cat /proc/modules',
) {
try_cmd_output_save($cmd);
}
--
2.5.3
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
