All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aniket Sahu <asahu1x@linux.ibm.com>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: npiggin@gmail.com, rathc@linux.ibm.com, milesg@linux.ibm.com,
	harshpb@linux.ibm.com, anushree.mathur@linux.ibm.com,
	misanjum@linux.ibm.com, adityag@linux.ibm.com,
	gautam@linux.ibm.com, thuth@redhat.com, asahu1x@linux.ibm.com
Subject: [PATCH v2 2/2] tests/functional/ppc64: extend ppc64 powernv net device tests
Date: Wed, 16 Sep 2026 16:06:35 +0530	[thread overview]
Message-ID: <20260916103635.7797-3-asahu1x@linux.ibm.com> (raw)
In-Reply-To: <20260916103635.7797-1-asahu1x@linux.ibm.com>

Added console checks as the probe log lines will appear before the
S14Silence-console init scripts.
---
 tests/functional/ppc64/test_powernv.py | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/tests/functional/ppc64/test_powernv.py b/tests/functional/ppc64/test_powernv.py
index f3e05e4d38..200fd2c894 100755
--- a/tests/functional/ppc64/test_powernv.py
+++ b/tests/functional/ppc64/test_powernv.py
@@ -201,9 +201,12 @@ def do_test_ppc64_powernv(self, proc):
 
         self.wait_for_console_pattern("CPU: " + proc + " generation processor")
         self.wait_for_console_pattern("INIT: Starting kernel at ")
+        # NVMe, e1000e, and xHCI are probed synchronously by the kernel
+        # during PCI enumeration, after OPAL hands off to Linux.
+        self.wait_for_console_pattern("nvme nvme0")
+        self.wait_for_console_pattern("e1000e")
+        self.wait_for_console_pattern("xhci_hcd")
         self.wait_for_console_pattern("Run /sbin/init as init process")
-        # Device detection output driven by udev probing is sometimes cut off
-        # from console output, suspect S14silence-console init script.
 
     def test_ppc64_powernv_external_dtb(self):
         self.set_machine('powernv11')
-- 
2.52.0



  parent reply	other threads:[~2026-09-16 10:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 10:36 [PATCH v2 0/2] tests/functional/ppc64: extend ppc64 functional tests Aniket Sahu
2026-09-16 10:36 ` [PATCH v2 1/2] tests/functional/ppc64: extend pseries migration tests Aniket Sahu
2026-09-17  6:46   ` Thomas Huth
2026-09-18 18:45   ` Amit Machhiwal
2026-09-21  5:56     ` Aniket Sahu
2026-09-21  6:41       ` Thomas Huth
2026-09-21  7:22         ` Aniket Sahu
2026-09-18 18:51   ` Amit Machhiwal
2026-09-16 10:36 ` Aniket Sahu [this message]
2026-09-17  6:48   ` [PATCH v2 2/2] tests/functional/ppc64: extend ppc64 powernv net device tests Thomas Huth
2026-09-18 18:53   ` Amit Machhiwal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260916103635.7797-3-asahu1x@linux.ibm.com \
    --to=asahu1x@linux.ibm.com \
    --cc=adityag@linux.ibm.com \
    --cc=anushree.mathur@linux.ibm.com \
    --cc=gautam@linux.ibm.com \
    --cc=harshpb@linux.ibm.com \
    --cc=milesg@linux.ibm.com \
    --cc=misanjum@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rathc@linux.ibm.com \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.