| Summary: | [Yocto 2.2.2] crosstap doesn't work | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Yi Zhao <yi.zhao> | ||||
| Component: | kernel | Assignee: | Armin Kuster <akuster> | ||||
| Status: | VERIFIED FIXED | QA Contact: | Yi Zhao <yi.zhao> | ||||
| Severity: | normal | ||||||
| Priority: | Medium+ | CC: | bruce.ashfield, jose.perez.carranza, richard.purdie, tom.zanussi, yi.zhao | ||||
| Version: | 2.2.2 | ||||||
| Target Milestone: | 2.2.2 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Yi Zhao
2017-06-02 07:23:13 UTC
according to https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=summary 4.8 support happened after the 3.0 release. they bumped kernel support with commit https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=commit;h=7d27ff5084d61a6f8c4843e934f666ed07832c30 6 months after 3.0 Linux version 4.4 seems to be the oldest kernel version support in 3.0 according to the release notes https://sourceware.org/ml/systemtap/2016-q1/msg00179.html = Examples of tested kernel versions 2.6.18 (RHEL 5 x86 and x86_64) 2.6.32 (RHEL 6 x86 and x86_64) 3.10.0 (RHEL 7 x86_64) 4.1.6 (Fedora 22 x86_64) 4.3.4 (Fedora 22 x86_64) 4.6.0-rc0 (Fedora rawhide x86_64) 3.1 supports = Examples of tested kernel versions 2.6.18 (RHEL 5 x86 and x86_64) 2.6.32 (RHEL 6 x86 and x86_64) 3.10.0 (RHEL 7 x86_64) 4.1.6 (Fedora 22 x86_64) 4.3.4 (Fedora 22 x86_64) 4.6.0-rc0 (Fedora rawhide x86_64) 4.6.0-rc6 (Fedora rawhide x86_64) 4.8.10-200 (Fedora 24 x86_64) 4.10.0-rc0 (Fedora rawhide x86_64) 4.10.0-rc6 (Fedora rawhide x86_64) 4.10.0-rc8 (Fedora rawhide x86_64) I am leaning toward "invalid" configuration on a 4.8 kernel Sounds like we might want to update to 3.1 in the next respin of 2.2.2? (In reply to comment #3) > Sounds like we might want to update to 3.1 in the next respin of 2.2.2? can do. will do a dry run to see if its brings in more issues than what it may be fixing. I backported the update from pyro update sitting in akuster/morty-next http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/meta/recipes-kernel/systemtap?h=akuster/morty-next&id=8974fd4709336b532369b084fd8c803647af289a code in motry. need to retest http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=morty&id=604b2b2c6c0a9c09098fccf958c94ea7ba8b082b Verified with 2.2.2 rc2. Git rev: morty/60402978fe3648bf560b3386c6e9dd661cdf2083 |