Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sparc #1178

Closed
wants to merge 1 commit into from
Closed

Sparc #1178

wants to merge 1 commit into from

Conversation

montjoie
Copy link
Contributor

No description provided.

@gctucker gctucker requested a review from a team May 11, 2022 07:05
@gctucker
Copy link
Contributor

I've started a sparc64_defconfig build on staging:
https://bot.staging.kernelci.org/job/kernel-build/65183/console

@nuclearcat
Copy link
Member

It seems build process failed:

Cancelling nested steps due to timeout
Sending interrupt signal to process
Terminated
script returned exit code 143

@montjoie
Copy link
Contributor Author

The jenkins link is 404, so i cannot saw what failed.

@nuclearcat
Copy link
Member

I think it got deleted due age.
I saved it, but there is not much useful info, just pod failed by some reason.
Probably easier to repeat build and check pod logs if it will fail again.

@gctucker gctucker self-assigned this May 16, 2022
@gctucker
Copy link
Contributor

Yes it should be run by hand to see what's going on.

@gctucker
Copy link
Contributor

Well I tried to build sparc64_defconfig in the Docker image and it didn't go very far:

gcc: warning: ‘-mcpu=’ is deprecated; use ‘-mtune=’ or ‘-march=’ instead
gcc: error: unrecognized argument in option ‘-mcmodel=medlow’
gcc: note: valid arguments to ‘-mcmodel=’ are: 32 kernel large medium small
gcc: error: unrecognized command-line option ‘-mno-fpu’; did you mean ‘-mno-fma’?
make[2]: *** [../scripts/Makefile.build:262: scripts/mod/empty.o] Error 1
make[2]: *** Waiting for unfinished jobs....
gcc: warning: ‘-mcpu=’ is deprecated; use ‘-mtune=’ or ‘-march=’ instead
gcc: error: unrecognized argument in option ‘-mcmodel=medlow’
gcc: note: valid arguments to ‘-mcmodel=’ are: 32 kernel large medium small
gcc: error: unrecognized command-line option ‘-mno-fpu’; did you mean ‘-mno-fma’?
make[2]: *** [../scripts/Makefile.build:99: scripts/mod/devicetable-offsets.s] Error 1
make[1]: *** [/root/linux/Makefile:1134: prepare0] Error 2
make[1]: Leaving directory '/root/linux/build'
make: *** [Makefile:179: sub-make] Error 2
make: Leaving directory '/root/linux'

@gctucker gctucker added the staging-skip Don't test automatically on staging.kernelci.org label Aug 1, 2022
@gctucker
Copy link
Contributor

gctucker commented Aug 3, 2022

@montjoie Please rebase now that #1336 has been merged

@montjoie
Copy link
Contributor Author

@montjoie Please rebase now that #1336 has been merged

Rebased and updated, since arch is now only sparc

@gctucker gctucker removed the staging-skip Don't test automatically on staging.kernelci.org label Mar 16, 2023
@gctucker
Copy link
Contributor

OK removed staging-skip, let's check the results in the next staging jobs.

@gctucker
Copy link
Contributor

@montjoie Jobs got scheduled but failed because there's no sparc rootfs image for baseline:

Resource unavailable at 'http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230310.0/sparc/rootfs.cpio.gz' (404)

https://lava.collabora.dev/scheduler/job/9746088

So please make another PR to fix this.

@mgalka
Copy link

mgalka commented Apr 5, 2023

@montjoie Do you have any updates on it?

@montjoie
Copy link
Contributor Author

montjoie commented Apr 5, 2023

I have kernelci/buildroot#15 which wait merging.

@mgalka
Copy link

mgalka commented Apr 6, 2023

I tested kernelci/buildroot#15 - builds fine with kci_rootfs.
Prepared PR to include sparc64 build for buildroot-baseline rootfs.

Depends on #1866

@gctucker gctucker assigned mgalka and unassigned gctucker Apr 6, 2023
mgalka pushed a commit to mgalka/kernelci-core that referenced this pull request Apr 7, 2023
This is to test PR kernelci#1178. DO NOT MERGE

Signed-off-by: Michal Galka <michal.galka@collabora.com>
mgalka pushed a commit to mgalka/kernelci-core that referenced this pull request Apr 11, 2023
This is to test PR kernelci#1178. DO NOT MERGE

Signed-off-by: Michal Galka <michal.galka@collabora.com>
mgalka pushed a commit to mgalka/kernelci-core that referenced this pull request Apr 19, 2023
This is to test PR kernelci#1178. DO NOT MERGE

Signed-off-by: Michal Galka <michal.galka@collabora.com>
@mgalka
Copy link

mgalka commented Apr 19, 2023

@montjoie It seems that the PR have now everything to be run on staging. There are rootfs and qemu docker images with sparc64 tools on board, but for some reason I cannot see tests results on the dashboard.
Is there something specific that needs to be set for qemu device to accept this tests?

@mgalka
Copy link

mgalka commented Apr 26, 2023

@montjoie It seems that the PR have now everything to be run on staging. There are rootfs and qemu docker images with sparc64 tools on board, but for some reason I cannot see tests results on the dashboard. Is there something specific that needs to be set for qemu device to accept this tests?

@montjoie ping?

@montjoie
Copy link
Contributor Author

Sorry I am on holidays, but I will try to check soon.

@montjoie
Copy link
Contributor Author

Just did a quick check, the qemu worker was dead, I restarted it.

@montjoie
Copy link
Contributor Author

Job fails with Job error: Invalid job data: ["Resource unavailable at 'http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230421.0/sparc/rootfs.cpio.gz' (404)"]

@mgalka
Copy link

mgalka commented May 3, 2023

Job fails with Job error: Invalid job data: ["Resource unavailable at 'http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230421.0/sparc/rootfs.cpio.gz' (404)"]

Ah, this is probably because of the recent rootfs images update, let me fix it and I'll check if it runs fine now.

mgalka pushed a commit to mgalka/kernelci-core that referenced this pull request May 3, 2023
This is to test PR kernelci#1178. DO NOT MERGE

Signed-off-by: Michal Galka <michal.galka@collabora.com>
@mgalka
Copy link

mgalka commented May 4, 2023

Job fails with Job error: Invalid job data: ["Resource unavailable at 'http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230421.0/sparc/rootfs.cpio.gz' (404)"]

I updated rootfs images config so it should be using staging images placed at https://storage.staging.kernelci.org/images/rootfs/buildroot/buildroot-baseline/20230418.0/

@montjoie Could you have another look at it

@gctucker
Copy link
Contributor

@montjoie Please take a look or this will need to be closed if there's no update next week.

@montjoie
Copy link
Contributor Author

rootfs are still not found https://lava.baylibre.com/scheduler/job/3656501

@gctucker
Copy link
Contributor

Please add sparc - sparc64 to the map in YAML

@montjoie
Copy link
Contributor Author

montjoie commented Jun 16, 2023

Please add sparc - sparc64 to the map in YAML

I tried:

--- a/config/core/test-configs.yaml
+++ b/config/core/test-configs.yaml
@@ -14,6 +14,7 @@ file_system_types:
       armel:   [{arch: arm}]
       x86:     [{arch: i386}, {arch: x86_64}]
       mipsel:  [{arch: mips}]
+      sparc:   [{arch: sparc64, endian: big}]


```no change

@montjoie
Copy link
Contributor Author

I will update the PR, but seems few kernel are built on staging, I cannot successful boot (next is failling).

Since kernelCI builds sparc64 defconfig, we could now boot some sparc64 qemu.
From the 3 qemu machine, only sun4u is easy to add.

Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
@gctucker
Copy link
Contributor

OK so either someone fixes Sparc on linux-next or we get a build on staging with a stable kernel revision known to work well. How about 6.1?

@montjoie
Copy link
Contributor Author

OK so either someone fixes Sparc on linux-next or we get a build on staging with a stable kernel revision known to work well. How about 6.1?

In fact we need #1963

@gctucker
Copy link
Contributor

Yes. But which stable kernel version is known to work with Sparc64?

@gctucker
Copy link
Contributor

gctucker commented Jul 5, 2023

Adding skip label because of #1994

@gctucker gctucker added the staging-skip Don't test automatically on staging.kernelci.org label Jul 5, 2023
@nuclearcat
Copy link
Member

I am closing PR related to legacy and SPARC. We might open topic again when we finish migrating legacy configurations to Maestro

@nuclearcat nuclearcat closed this Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
staging-skip Don't test automatically on staging.kernelci.org
Projects
Development

Successfully merging this pull request may close these issues.

4 participants