Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 626982 - More arch testing hardware access for kernel team (or Mike Pagano/Alice Ferrazzi)
Summary: More arch testing hardware access for kernel team (or Mike Pagano/Alice Ferra...
Status: CONFIRMED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Infrastructure
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-03 15:01 UTC by Michał Górny
Modified: 2022-06-16 11:32 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-03 15:01:31 UTC
As mentioned in the recent -dev thread, the kernel team would really use some non-x86 hardware to do build-testing of new kernels. This is especially important to facilitate faster stabilization of minor releases that fix vulnerabilities.

@infra, @arch teams, do we have any hardware we could give access to?
Comment 1 Tobias Klausmann (RETIRED) gentoo-dev 2017-08-03 15:06:30 UTC
For alpha, I am the one who grants access. For those that need/want access, send me:

- desired user name
- SSH RSA or ed25519 key

in a GPG-signed mail and I'll make an account and give your the relevant details.
Comment 2 Matt Turner gentoo-dev 2017-08-03 16:54:16 UTC
For build testing, you can use crossdev to build cross-compilers. Cross compiling the kernel is very easy. Unless you actually want a system to test the kernels on (which is hard), there's no point in having access to non-x86 hardware.
Comment 3 Mike Pagano gentoo-dev 2017-08-03 17:25:55 UTC
Yes, I want real systems that I can build, install , reboot and monitor dmesg.

If this is not feasible, please let me know.

Otherwise, it's not a viable path to stabilization.
Comment 4 Tobias Klausmann (RETIRED) gentoo-dev 2017-08-03 17:35:11 UTC
We (alpha) have exactly 1 dev machine (in the sense of people getting accounts on it). Since 90+% of my alpah AT work happens on, randomly rebooting it is not an option.

While qemu has a runt of alpha emulation, it's not a complete system and therefore not really useful (yet). It also would be dog slow, even compared to our 15-year-old dev machine.

I have an alpha board that I am not really using, I could donate that to the cause, as it were.


*However,* mattst88 and I have been talking about the future of alpha in Gentoo and it is likely we will drop it to only-@system-is-stable state sometime this year, so putting effort into having a randomly-rebootable alpha for kernel testing may be a bit wasted.
Comment 5 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2017-08-04 19:41:44 UTC
mpagano:
If you are willing to put in work on building stages (openstack-ready stage4-cloud needed), infra/me can set you up with bleeding edge arm64 hardware.

Otherwise infra only really has amd64 to offer, preferably on VMs.
Comment 6 Alice Ferrazzi Gentoo Infrastructure gentoo-dev 2017-12-07 13:39:49 UTC
Please add also me to the Kernel Testing resources
Comment 7 John Helmert III archtester Gentoo Infrastructure gentoo-dev Security 2022-06-16 01:07:51 UTC
After almost 5 years, is there still interest in this? As far as I can tell, the kernel team has gotten along relatively well.
Comment 8 Mike Pagano gentoo-dev 2022-06-16 11:32:08 UTC
(In reply to John Helmert III from comment #7)
> After almost 5 years, is there still interest in this? As far as I can tell,
> the kernel team has gotten along relatively well.

Speaking only for myself, I have not had the need lately to chase down bugs on non amd64 archs.