Total jobs: 182
Total errors: 51 (28.02%)
LAVA errors: 0 (0.00%)
Test errors: 42 (23.08%)
Job errors: 6 (3.30%)
Infra errors: 3 (1.65%)
Canceled jobs: 0 (0.00%)
Device type: qrb5165-rb5
Total jobs: 77
Total errors: 24 (31.17%)
Error type: Job
Error count: 5 (6.49%)
Error: expect-shell-connection timed out
Count: 1 (1.30%)
IDs:
rb5-07:
7947741
Error: No match for error type 'Job', message 'login-action timed out after 713 seconds'
Count: 1 (1.30%)
IDs:
rb5-03:
7947663
Error: No match for error type 'Job', message 'login-action timed out after 875 seconds'
Count: 1 (1.30%)
IDs:
rb5-05:
7947662
Error: No match for error type 'Job', message 'login-action timed out after 712 seconds'
Count: 1 (1.30%)
IDs:
rb5-03:
7947487
Error: No match for error type 'Job', message 'login-action timed out after 874 seconds'
Count: 1 (1.30%)
IDs:
rb5-07:
7947486
Error type: Test
Error count: 17 (22.08%)
Error: No match for error type 'Test', message 'tradefed - adb device lost[74d67c95]'
Count: 2 (2.60%)
IDs:
rb5-03:
7947700 7947737
Error: No match for error type 'Test', message 'tradefed - adb device lost[93dcfd96]'
Count: 1 (1.30%)
IDs:
rb5-01:
7947720
Error: Device NOT found!
Count: 5 (6.49%)
IDs:
rb5-03:
7947550 7947649 7947653 7947704 7947706
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds'
Count: 2 (2.60%)
IDs:
rb5-03:
7947672 7947697
Error: No match for error type 'Test', message 'lava-test-interactive timed out after 600 seconds'
Count: 1 (1.30%)
IDs:
rb5-03:
7947694
Error: No match for error type 'Test', message 'tradefed - adb device lost[4fc7b22]'
Count: 3 (3.90%)
IDs:
rb5-06:
7947460 7947488 7947670
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 594 seconds'
Count: 1 (1.30%)
IDs:
rb5-03:
7947669
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 597 seconds'
Count: 2 (2.60%)
IDs:
rb5-03:
7947423 7947484
Error type: Infrastructure
Error count: 2 (2.60%)
Error: Connection closed
Count: 2 (2.60%)
IDs:
rb5-05:
7947450 7947510
Device type: dragonboard-845c
Total jobs: 105
Total errors: 27 (25.71%)
Error type: Test
Error count: 25 (23.81%)
Error: Device NOT found!
Count: 5 (4.76%)
IDs:
db845c-02:
7931920 7947544
db845c-09:
7931918 7931951 7947903
Error: No match for error type 'Test', message 'tradefed - adb device lost[db2a494d]'
Count: 4 (3.81%)
IDs:
db845c-02:
7931911 7947634 7947689 7947857
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 597 seconds'
Count: 1 (0.95%)
IDs:
db845c-09:
7947802
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 598 seconds'
Count: 7 (6.67%)
IDs:
db845c-02:
7931932 7947541
db845c-09:
7931950 7931953 7931972 7931975 7947801
Error: No match for error type 'Test', message 'tradefed - adb device lost[3419ccc6]'
Count: 1 (0.95%)
IDs:
db845c-06:
7947753
Error: No match for error type 'Test', message 'The network seems not available, as the ping command failed'
Count: 4 (3.81%)
IDs:
db845c-01:
7931913 7931934 7947680
db845c-02:
7931937
Error: No match for error type 'Test', message 'tradefed - adb device lost[fbf682a2]'
Count: 1 (0.95%)
IDs:
db845c-09:
7947543
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 53998 seconds'
Count: 1 (0.95%)
IDs:
db845c-06:
7946128
Error: No match for error type 'Test', message 'lava-docker-test-shell timed out after 594 seconds'
Count: 1 (0.95%)
IDs:
db845c-09:
7931912
Error type: Job
Error count: 1 (0.95%)
Error: expect-shell-connection timed out
Count: 1 (0.95%)
IDs:
db845c-04:
7947752
Error type: Infrastructure
Error count: 1 (0.95%)
Error: Connection closed
Count: 1 (0.95%)
IDs:
db845c-07:
7931927
On Wed, 23 Oct 2024 at 20:47, Alex Bennée <alex.bennee(a)linaro.org> wrote:
> Agreed. However I think we were masking a calling issue that:
>
> /* Actual RAM size depends on initial RAM and device memory settings */
> [VIRT_MEM] = { GiB, LEGACY_RAMLIMIT_BYTES },
>
> And:
>
> -m 4G
>
> make no sense with no ARM_LPAE (which the kernel didn't have)
QEMU can't tell if the guest the user wants to boot
understands LPAE or not; it just provides the 4GB
of RAM, PCIe window above 4GB, etc, and describes them
in the dtb. It's up to the guest kernel to correctly
handle the >32bit addresses in the dtb, i.e. if it is
non-LPAE to ignore those resources it can't access
because they're out of range.
-- PMM
On Wed, Oct 23, 2024, at 19:47, Alex Bennée wrote:
>> On Sun, Oct 20, 2024, at 17:39, Naresh Kamboju wrote:
>> On non-LPAE arm32, this broke the existing behavior for
>> large 32-bit memory sizes. The obvious fix is to change
>> back the PAGE_MASK definition for 32-bit arm to a signed
>> number.
>
> Agreed. However I think we were masking a calling issue that:
>
> /* Actual RAM size depends on initial RAM and device memory settings */
> [VIRT_MEM] = { GiB, LEGACY_RAMLIMIT_BYTES },
>
> And:
>
> -m 4G
>
> make no sense with no ARM_LPAE (which the kernel didn't have) but if you
> pass -machine virt,gic-version=3,highmem=off (the default changed awhile
> back) you will get a warning:
>
> qemu-system-arm: Addressing limited to 32 bits, but memory exceeds it
> by 1073741824 bytes
>
> but I guess that didn't trigger for some reason before this patch?
I did not look at the full log, but I don't think there is a
problem between kernel and qemu, this is just a kernel regression
that can happen on any real or virtual platform with a lot of
memory.
I would guess that "highmem=off" was not even set here, so
there was probably no warning, and you would still see the
same kernel bug with qemu-system-aarch64 and its larger
limit for highmem=off.
Arnd