Bug 1620289 - Armv7 guest fails to boot on Fedora 29 AArch64 host
Summary: Armv7 guest fails to boot on Fedora 29 AArch64 host
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 29
Hardware: aarch64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-22 21:38 UTC by Paul Whalen
Modified: 2018-08-23 13:31 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-08-23 13:31:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Full boot log (17.81 KB, text/plain)
2018-08-22 21:38 UTC, Paul Whalen
no flags Details
boot with debug (350.33 KB, text/plain)
2018-08-22 21:39 UTC, Paul Whalen
no flags Details

Description Paul Whalen 2018-08-22 21:38:37 UTC
Created attachment 1477991 [details]
Full boot log

Description of problem:
Attempting to boot an armv7 guest on aarch64 in Fedora 29 fails with:

*snip*
         Mounting Kernel Configuration File System...
[    6.755582] kauditd_printk_skb: 3 callbacks suppressed
[    6.755585] audit: type=1701 audit(1534970824.912:14): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=377 comm="systemd" exe="/usr/lib/systemd/systemd" sig=4 res=1
[    6.844949] systemd: 16 output lines suppressed due to ratelimiting
[    7.097846] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   46.824305] audit: type=1701 audit(1534970864.981:15): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=787 comm="dracut-initqueu" exe="/usr/bin/bash" sig=4 res=1
[   46.828778] Core dump to |/bin/false pipe failed
[   45.655434] dracut-initqueue[353]: /lib/dracut-lib.sh: line 445:   787 Illegal instruction     ( . "$f" )
[  105.925535] audit: type=1701 audit(1534970924.082:16): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=1381 comm="udevadm" exe="/usr/bin/udevadm" sig=4 res=1
[  105.941432] systemd-journald[174]: Failed to send WATCHDOG=1 notification message: Connection refused
[  105.950906] Core dump to |/bin/false pipe failed
[  104.784560] dracut-initqueue[353]: /bin/dracut-initqueue: line 77:  1381 Illegal instruction     udevadm settle --exit-if-exists=$hookdir/initqueue/work
[  129.103349] audit: type=1701 audit(1534970947.260:17): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=1620 comm="dracut-initqueu" exe="/usr/bin/bash" sig=4 res=1
[  129.107669] Core dump to |/bin/false pipe failed
[  127.934203] dracut-initqueue[353]: /bin/dracut-initqueue: line 77:  1620 Illegal instruction     sleep 0.5
[  150.475918] audit: type=1701 audit(1534970968.632:18): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=353 comm="dracut-initqueu" exe="/usr/bin/bash" sig=4 res=1
[  150.482348] Core dump to |/bin/false pipe failed
[  221.575720] systemd-journald[174]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected
[  301.575751] systemd-journald[174]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected


Version-Release number of selected component (if applicable):
dracut-048-14.git20180726.fc29

How reproducible:
everytime

Comment 1 Paul Whalen 2018-08-22 21:39:36 UTC
Created attachment 1477992 [details]
boot with debug

Comment 2 Harald Hoyer 2018-08-23 13:31:26 UTC
[   55.466752] dracut-initqueue[353]: /bin/dracut-initqueue: line 77:   717 Illegal instruction     (core dumped) udevadm settle --timeout=0 > /dev/null 2>&1


Well seems like a compiler, CPU, architecture bug... can't do anything about it.

File a bug to whatever component, if you find out why

# udevadm settle --timeout=0 

coredumps.


Note You need to log in before you can comment on or make changes to this bug.