linux/poky.git/meta, branch hardknott-3.3.1

build-appliance-image: Update to hardknott head revision

2021-05-17T08:42:25+00:00

(From OE-Core rev: efce6334bf122a64f63d46c1c04e3dbffe298c51) Signed-off-by: Richard Purdie

puzzles: Upstream changed to main branch for development

2021-05-15T16:18:21+00:00

(From OE-Core rev: 1cf4d3f44191c3fc2cb4d056b38f98fae4e8b8e1) Signed-off-by: Richard Purdie (cherry picked from commit 943402b25212408a4ddcfa8a146b645509e138dd) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

linux-firmware: include all relevant files in -bcm4356

2021-05-15T16:18:21+00:00

This currently catches the .clb_blob and .vamrs,rock960.txt, and other .txt files may come in future upstream releases. (From OE-Core rev: 68647eccaf817287df17d5a247b3caf7df9f6840) Signed-off-by: Yann Dirson Signed-off-by: Richard Purdie (cherry picked from commit e332738a8aae0914c58b40faae8b9d7a82fd6a95) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

lsb-release: fix reproducibility failure

2021-05-15T16:18:21+00:00

Make sure help2man output is reproducible. Fixes: | .\"·DO·NOT·MODIFY·THIS·FILE!··It·was·generated·by·help2man·1.022. .\"·DO·NOT·MODIFY·THIS·FILE!··It·was·generated·by·help2man·1.022. | .TH·FSG·"1"·"April·2021"·"FSG·lsb_release·v1.4"·FSG .TH·FSG·"1"·"May·2021"·"FSG·lsb_release·v1.4"·FSG | .SH·NAME 3 .SH·NAME (From OE-Core rev: e73898b59eb79d20082963e629ce6f8cc75103c9) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie (cherry picked from commit 49371207a7f1fe3d3feb7b8b9aabb62b43ae34d1) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

ruby: upgrade 3.0.0 -> 3.0.1

2021-05-15T16:18:21+00:00

(From OE-Core rev: 9fde0b5121b6cda894ef761a526fa4feced02d5f) Signed-off-by: Zheng Ruoqin Signed-off-by: Richard Purdie (cherry picked from commit b6949a028fd31bd04ed0478fb34a58b971f31e1f) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

grub2.inc: remove '-O2' from CFLAGS

2021-05-15T16:18:21+00:00

It fails to boot grub after upgrade grub to 2.06. According to description in https://bugzilla.yoctoproject.org/show_bug.cgi?id=14367 it is introduced by a commit to fix CVE. So remove option '-O2' from CFLAGS rather than revert the commit to avoid the failure. [YOCTO #14367] CC: Tony Battersby (From OE-Core rev: 7520bd4f72d550052774042c542a3d3ee874b363) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie (cherry picked from commit 69805629b8f47fd46a37b7c5cc435982e2ac3d1d) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

dejagnu: needs expect at runtime

2021-05-15T16:18:21+00:00

runtest return an error due to missing expect on the target. Add expect as runtime dependency. (From OE-Core rev: 9dc044fdbd20085dfa99fd4a7189763365334ede) Signed-off-by: Romain Naour Signed-off-by: Richard Purdie (cherry picked from commit d9a3a08edc1efcbe7b02e80be98370792d3c6cc2) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

libcap: Configure Make variables correctly without a horrible hack

2021-05-15T16:18:21+00:00

Occasionally, the build would fail with: make[2]: execvp: mkdir: Argument list too long This turned out to be due to a hacky solution used in the recipe to modify the Makefile, which resulted in one more $(BUILD_CFLAGS) being added to the immediately expanded BUILD_CFLAGS Make variable each time do_configure was executed. After a couple of times, this lead to an environment with a 140 kB BUILD_CFLAGS when mkdir should execute, which resulted in the E2BIG. (From OE-Core rev: 44900610bea76ab8983a899599f78790f6c5f659) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit 116e6b61c585c6f0f7ae6f010bd490bb39914348) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

lttng-modules: backport patches to fix build against 5.12+ kernel

2021-05-15T16:18:21+00:00

Add the following patches from stable-2.12 branch of lttng repository to fix errors when building lttng-modules against 5.12+ kernel since they are not present on the release 2.12.5: - 17cd2dc9 fix: block: add a disk_uevent helper (v5.12) - 127135b6 fix backport: block: add a disk_uevent helper (v5.12) - 853d5903 fix: mm, tracing: kfree event name mismatching with provider kmem (v5.12) (From OE-Core rev: 86bcab9e9f4ee5e06f7db8c75d4b983fd2be59d2) Signed-off-by: Vinicius Aquino Signed-off-by: Richard Purdie (cherry picked from commit 2538ba2b3490e3599d9ccd637aa8486ea428f1b0) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

linux-yocto/5.4: qemuppc32: reduce serial shutdown issues

2021-05-15T16:18:21+00:00

Integrating the following commit(s) to linux-yocto/5.4: qemuppc32: reduce serial issues seen on shutdown Richard reported: We've been seeing a lot of the qemuppc shutdown issue and I decided to look into it. The really worrying thing looking at the logs locally is the serial ports are showing irq issues and becoming disabled as nobody would handle them. Errors like: [ 9.194886] irq 36: nobody cared (try booting with the "irqpoll" option) [ 9.198712] CPU: 0 PID: 127 Comm: bootlogd Not tainted [ 9.202283] Call Trace: [ 9.205611] [d1005f00] [c00a0da8] __report_bad_irq+0x50/0x138 (unreliable) [ 9.209347] [d1005f30] [c00a0cc0] note_interrupt+0x324/0x378 [ 9.212855] [d1005f70] [c009d138] handle_irq_event+0xe8/0x104 [ 9.216353] [d1005fa0] [c00a1d9c] handle_fasteoi_irq+0xc0/0x29c [ 9.219960] [d1005fc0] [c009b798] generic_handle_irq+0x40/0x5c [ 9.223496] [d1005fd0] [c00075d0] __do_irq+0x58/0x188 [ 9.226948] [d1005ff0] [c0010040] call_do_irq+0x20/0x38 [ 9.230391] [d29eda60] [c0007788] do_IRQ+0x88/0xfc [ 9.233860] [d29eda90] [c0016454] ret_from_except+0x0/0x14 [ 9.237288] --- interrupt: 501 at __setup_irq+0x3c4/0x838 [ 9.237288] LR = __setup_irq+0x790/0x838 [ 9.244155] [d29edb88] [c009f0a4] request_threaded_irq+0x114/0x1c8 [ 9.247672] [d29edbb8] [c07a5a18] pmz_startup+0x17c/0x32c [ 9.251203] [d29edbd8] [c07a1140] uart_port_startup+0x184/0x2f8 [ 9.254651] [d29edc08] [c07a1974] uart_port_activate+0x78/0xf4 [ 9.258141] [d29edc28] [c07839f8] tty_port_open+0xd4/0x170 [ 9.261579] [d29edc58] [c079db74] uart_open+0x2c/0x48 [ 9.265116] [d29edc68] [c077a288] tty_open+0x168/0x640 [ 9.268574] [d29edcd8] [c0280be8] chrdev_open+0x138/0x2a4 [ 9.272123] [d29edd18] [c027421c] do_dentry_open+0x228/0x410 [ 9.275643] [d29edd48] [c028e9f4] path_openat+0xb04/0xf28 [ 9.279184] [d29eddd8] [c02917e4] do_filp_open+0x120/0x164 [ 9.282535] [d29ede98] [c0276238] do_sys_openat2+0xd8/0x19c [ 9.285790] [d29edee8] [c0276574] sys_openat+0x88/0xdc [ 9.289096] [d29edf38] [c00160d8] ret_from_syscall+0x0/0x34 [ 9.292620] --- interrupt: c01 at 0xfec3738 [ 9.292620] LR = 0xfec36e0 [ 9.299035] handlers: [ 9.302312] [<7f7f7da8>] pmz_interrupt [ 9.305541] Disabling IRQ #36 (and the irqpoll option does not help) This is problematic as the shutdown test uses the serial interface to shut down the system. If the serial interface fails to login or run the command, game over for the test. CONFIG_SERIAL_PMACZILOG_CONSOLE complicates that handling, but doesn't provide any output or capabilities that we need. So we disable it here, and reduce the chances of issues during shutdown. (From OE-Core rev: aca5873e830d3b66f00cad4fa03982cc4ec5b445) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie (cherry picked from commit 42355cb73049ee7a4af0f539a2a5b7d4ee1abc65) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie