From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: [next-20250709] Fails to boot on IBM Power Server
Date: Thu, 10 Jul 2025 14:56:38 +0530 [thread overview]
Message-ID: <fe13e9e2-8ac5-46c7-b925-b61d35104ed1@linux.ibm.com> (raw)
Greetings!!!
IBM CI has reported a boot issue on the latest linux-next(20250709)
kernel fails on IBM Power servers.
System entering to emergency mode.
Error:
[ 1.071678] ibmveth 30000002 net0: renamed from eth0
[ 1.074227] ibmvscsi 30000069: SRP_VERSION: 16.a
[ 1.074238] ibmvscsi 30000069: Error -4 opening adapter
[ 1.074255] ibmvscsi 30000069: couldn't initialize crq. rc=-1
[ 1.181132] ibmvscsi 30000069: probe with driver ibmvscsi failed with
error -1
[ 146.631585] dracut-initqueue[320]: Warning: dracut-initqueue:
timeout, still waiting for following initqueue hooks:
[ 146.632266] dracut-initqueue[320]: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fc034bf95-13cb-46a0-b66e-78faa57bc520.sh:
"if ! grep -q After=remote-fs-pre.target
/run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 146.632493] dracut-initqueue[320]: [ -e
"/dev/disk/by-uuid/c034bf95-13cb-46a0-b66e-78faa57bc520" ]
[ 146.632628] dracut-initqueue[320]: fi"
[ 146.633622] dracut-initqueue[320]: Warning: dracut-initqueue:
starting timeout scripts
[ 147.203267] dracut-initqueue[320]: Warning: dracut-initqueue:
timeout, still waiting for following initqueue hooks:
[ 147.204238] dracut-initqueue[320]: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fc034bf95-13cb-46a0-b66e-78faa57bc520.sh:
"if ! grep -q After=remote-fs-pre.target
/run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 147.204460] dracut-initqueue[320]: [ -e
"/dev/disk/by-uuid/c034bf95-13cb-46a0-b66e-78faa57bc520" ]
[ 147.204603] dracut-initqueue[320]: fi"
[ 147.205561] dracut-initqueue[320]: Warning: dracut-initqueue:
starting timeout scripts
[ 147.767680] dracut-initqueue[320]: Warning: dracut-initqueue:
timeout, still waiting for following initqueue hooks:
[ 147.768382] dracut-initqueue[320]: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2fc034bf95-13cb-46a0-b66e-78faa57bc520.sh:
"if ! grep -q After=remote-fs-pre.target
/run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 147.768649] dracut-initqueue[320]: [ -e
"/dev/disk/by-uuid/c034bf95-13cb-46a0-b66e-78faa57bc520" ]
[ 147.768788] dracut-initqueue[320]: fi"
If you happen to fix this, please add below tag.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
next reply other threads:[~2025-07-10 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 9:26 Venkat Rao Bagalkote [this message]
2025-07-10 10:22 ` [next-20250709] Fails to boot on IBM Power Server Stephen Rothwell
2025-07-11 3:56 ` Venkat Rao Bagalkote
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=fe13e9e2-8ac5-46c7-b925-b61d35104ed1@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox