Bug 15100

Created attachment 4947 [details]
poky-master-qemuarm--core-image-sato-frozen

When Narpat was testing chromium in qemuarm (and qemuarm64), he noted that for poky/master the UI  would come up but be 'frozen and greyed out'.  

to reproduce, use poky/master and:
$ bitbake core-image-sato
$ runqemu qemuarm serialstdio publicvnc qemuparams="-m 512"
$ run your vncviewer
See attached.

I confirmed this to be the case and did a qemuarm git bisect to find that the problematic commit is apparently:

❯ git bisect good                                                                                         
b8cac140f4ec37959b788261a0d5559497ce9c1b is the first bad commit                           
commit b8cac140f4ec37959b788261a0d5559497ce9c1b                                                          
Author: Bruce Ashfield <bruce.ashfield@gmail.com>                                                        
Date:   Wed Mar 1 10:13:43 2023 -0500                                                                    
                                                                                                         
    linux-yocto/6.1: update to v6.1.14                                                                   
                                                                                                         
    Updating  to the latest korg -stable release that comprises                                       
    the following commits:       
  ...

FYI, here's the log:
❯ git bisect log
git bisect start
# status: waiting for both good and bad commits
# bad: [71c316576150022a2337777da8274318064ef73f] Revert "ripgrep: add ripgrep-13.0.0"
git bisect bad 71c316576150022a2337777da8274318064ef73f
# status: waiting for good commit(s), bad commit known
# bad: [1ace5646156640ceb9322dd8cb322a58772936a5] puzzles: upgrade to latest revision
git bisect bad 1ace5646156640ceb9322dd8cb322a58772936a5
# status: waiting for good commit(s), bad commit known
# good: [dfa8b896c64182fbf7c22eef4ae7e1948f5279c4] webkitgtk: Fix build on 32bit arm
git bisect good dfa8b896c64182fbf7c22eef4ae7e1948f5279c4
# good: [35b187374905d4e3f0e6a66b183304b56aebe948] libxpm: update 3.5.13 -> 3.5.14
git bisect good 35b187374905d4e3f0e6a66b183304b56aebe948
# good: [557aab215884d10839fa24f797890c99f38e97b2] bitbake: cache/codeparser: Switch to a new BB_CACHEDIR variable for cache location
git bisect good 557aab215884d10839fa24f797890c99f38e97b2
# good: [069e5df6ae3b23659c91a59fd6990fc1a8fd9a92] pkgconfig: use system glib for nativesdk builds
git bisect good 069e5df6ae3b23659c91a59fd6990fc1a8fd9a92
# good: [7a548930d27af2b3034fabe18f51a695d121c70c] musl: Update to tip of trunk
git bisect good 7a548930d27af2b3034fabe18f51a695d121c70c
# bad: [44913cfab42856b8f40e13bac76c5abfa1df0cb2] linux: inherit pkgconfig in kernel.bbclass
git bisect bad 44913cfab42856b8f40e13bac76c5abfa1df0cb2
# good: [33d9b3a8ed186c2d212acb83f715367912010e7f] systemd-systemctl: Create machine-id with "uninitialized" text in it
git bisect good 33d9b3a8ed186c2d212acb83f715367912010e7f
# good: [afd1545a5cead40219727b427607c44e6c192504] linux-yocto/6.1: update to v6.1.12
git bisect good afd1545a5cead40219727b427607c44e6c192504
# bad: [d24ae96060c83604c1eb5a4a2ca3503f827e9bfb] vim: add missing pkgconfig inherit
git bisect bad d24ae96060c83604c1eb5a4a2ca3503f827e9bfb
# bad: [64af4e8abbac727a42ab685471129d1ffbe99b4f] linux-yocto/5.15: update to v5.15.96
git bisect bad 64af4e8abbac727a42ab685471129d1ffbe99b4f
# bad: [b8cac140f4ec37959b788261a0d5559497ce9c1b] linux-yocto/6.1: update to v6.1.14
git bisect bad b8cac140f4ec37959b788261a0d5559497ce9c1b
# good: [aedc70ea0e3df900f04b409979a1dcd99930ab21] linux-yocto/5.15: update to v5.15.94
git bisect good aedc70ea0e3df900f04b409979a1dcd99930ab21
# first bad commit: [b8cac140f4ec37959b788261a0d5559497ce9c1b] linux-yocto/6.1: update to v6.1.14


I haven't yet tried to trace init to see what syscall(s) results in the UI hanging.