Bugzilla – Bug 1196632
Raspberry Pi 3: kernel errors in journal
Last modified: 2024-06-25 16:40:32 UTC
Raspberry Pi 3 shows kernel errors in journal in openQA: Feb 24 00:00:59.640173 localhost kernel: of_clk_hw_onecell_get: invalid index 15 Feb 24 00:00:59.640443 localhost kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed to get clock: -2 Feb 24 00:00:59.640588 localhost kernel: vc4-drm soc:gpu: failed to bind 3f806000.vec (ops vc4_vec_ops [vc4]): -2 Feb 24 00:01:03.628986 localhost kernel: lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped Feb 24 00:01:03.630784 localhost kernel: lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped See: https://openqa.opensuse.org/tests/2220373/modules/journal_check/steps/10 RPi 2 has similar traces: Feb 24 00:01:05.797966 localhost kernel: of_clk_hw_onecell_get: invalid index 15 Feb 24 00:01:05.798406 localhost kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed to get clock: -2 Feb 24 00:01:05.798737 localhost kernel: vc4-drm soc:gpu: failed to bind 3f806000.vec (ops vc4_vec_ops [vc4]): -2 Feb 24 00:01:05.852969 localhost systemd-udevd[1029]: controlC1: /usr/lib/udev/rules.d/78-sound-card.rules:5 Failed to write ATTR{/sys/devices/platform/soc/3f902000.hdmi/sound/card1/controlC1/../uevent}, ignoring: No such file or directory See: https://openqa.opensuse.org/tests/2220373#step/journal_check/10
This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi3 https://openqa.opensuse.org/tests/2247277 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Guillaume GARDET from comment #0) > Feb 24 00:00:59.640173 localhost kernel: of_clk_hw_onecell_get: invalid > index 15 > Feb 24 00:00:59.640443 localhost kernel: [drm:vc4_vec_bind [vc4]] *ERROR* > Failed to get clock: -2 > Feb 24 00:00:59.640588 localhost kernel: vc4-drm soc:gpu: failed to bind > 3f806000.vec (ops vc4_vec_ops [vc4]): -2 Few clk-raspberrypi downstream module changes are missing upstream. https://lore.kernel.org/all/20220323160859.69572-1-iivanov@suse.de
It seems that v2 from my patches [1] are close to acceptance. [1] https://lore.kernel.org/linux-clk/20220405082503.61041-1-iivanov@suse.de/T/#m2f843c4c831a2dae7ea0f5d2e3007d959464f563
This now affects Leap 15.4 as well: https://openqa.opensuse.org/tests/2283745#step/journal_check/10
OBS is building test kernel package with the fix at the moment. You can watch the build progress at https://build.opensuse.org/project/monitor?project=home%3Aiivanov%3Absc1196632-clks-stable
*** Bug 1198942 has been marked as a duplicate of this bug. ***
v4: https://lore.kernel.org/all/20220428080308.3dtpjgnpzbupqs44@houat/T/
This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi3 https://openqa.opensuse.org/tests/2338964#step/journal_check/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi3 https://openqa.opensuse.org/tests/2406850#step/journal_check/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Can anyone provide the version of the videocore firmware (visible as a date in the kernel log)?
Currently Tumbleweed is using: "Attached to firmware from 2022-07-04T14:41:54" And downstream device tree files from 2022.07.06 and branch rpi-5.18.y. Right now following error is not visible: "... kernel: of_clk_hw_onecell_get: invalid index 15 kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed to get clock: -2 ..." But only because of luck, I would say. Because of out-of-bound access bug that you found in raspberrypi_discover_clocks() driver happily register clock 15, because following is still true (RPI_FIRMWARE_NUM_CLK_ID is 15 in current TW sources) if (clks->id > RPI_FIRMWARE_NUM_CLK_ID). So we need your "clk: bcm: rpi: Prevent out-of-bounds access" patch, but this then I guess, vc4-drm driver will start failing again because of missing clock.
AFAIK the latest firmware has a workaround for the invalid index issue. Yes, the real issue comes from the downstream DTB. It uses the VEC clock from the raspberrypi clock and not from clk-bcm2835 driver. This is different from the mainline DTB. As a temporary solution you could try to make the so called "upstream" overlay behave more like the mainline DTB by using the clk-bcm2835 clock for VEC. The decision to combine DTB, firmware and kernel in the raspberrypi clock driver was really bad and not prospective. Everything is very fine as long all parts are in sync. But it turns into a nightmare in case one part is too old.
(In reply to Stefan Wahren from comment #14) > AFAIK the latest firmware has a workaround for the invalid index issue. > Hm, not sure I get this. Currently RPI_FIRMWARE_GET_CLOCKS return 15 clocks. From 1 to 15 inclusive, so number 15 (VEC) clock is among them. Except that we do out-of-bound access in clks array VEC clock is regitered successfully in the clock provider. > Yes, the real issue comes from the downstream DTB. It uses the VEC clock > from the raspberrypi clock and not from clk-bcm2835 driver. This is > different from the mainline DTB. > I can't find at the moment where I found this sentence, or slightly modified version, but: ".. Platform driver clk-bcm2835 gets an inaccurate clock for VEC (107MHz). Export VEC clock trough clk-raspberrypi which uses the right PLL to get an accurate 108MHz. ..." And somehow I think this was related around 4K60Hz support addition. To me looks like we want to use clk-raspberrypi for VEC clock proivider.
This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos@RPi3 https://openqa.opensuse.org/tests/2498490#step/journal_check/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Maintainer requested to resend v4: https://lore.kernel.org/linux-arm-kernel/20220829152154.147250-1-iivanov@suse.de/T/
Fixes are in clk-next https://lore.kernel.org/linux-arm-kernel/20220930213443.240F9C433D6@smtp.kernel.org/
Commit 1777cb60f7df80d9b4ca3385eca1d2c0bed61cb6 Author: Dom Cobley <popcornmix@gmail.com> Date: Mon Aug 29 18:21:54 2022 +0300 clk: bcm: rpi: Add support for VEC clock Is upstream. $ git describe 1777cb60f7df80d9b4ca3385eca1d2c0bed61cb6 v6.0-rc1-6-g1777cb60f7df Hopefully it will land into kernel-source:stable soon.
SUSE-SU-2022:3998-1: An update that solves 37 vulnerabilities, contains 25 features and has 38 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1152472,1152489,1188238,1194869,1196018,1196632,1199904,1200567,1200692,1200788,1202187,1202686,1202700,1202914,1203098,1203229,1203290,1203435,1203514,1203699,1203701,1203767,1203770,1203802,1203922,1203979,1204017,1204051,1204059,1204060,1204125,1204142,1204166,1204168,1204171,1204241,1204353,1204354,1204355,1204402,1204413,1204415,1204417,1204428,1204431,1204439,1204470,1204479,1204498,1204533,1204569,1204574,1204575,1204619,1204635,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204753,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970 CVE References: CVE-2022-1882,CVE-2022-2153,CVE-2022-28748,CVE-2022-2964,CVE-2022-2978,CVE-2022-3169,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3640,CVE-2022-3646,CVE-2022-3649,CVE-2022-40476,CVE-2022-40768,CVE-2022-41674,CVE-2022-42703,CVE-2022-42719,CVE-2022-42720,CVE-2022-42721,CVE-2022-42722,CVE-2022-43750 JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1649,PED-634,PED-676,PED-678,PED-679,PED-707,PED-732,PED-813,PED-817,PED-822,PED-825,PED-833,PED-842,PED-846,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-9246 Sources used: openSUSE Leap 15.4 (src): kernel-azure-5.14.21-150400.14.21.2, kernel-source-azure-5.14.21-150400.14.21.1, kernel-syms-azure-5.14.21-150400.14.21.1 SUSE Linux Enterprise Module for Public Cloud 15-SP4 (src): kernel-azure-5.14.21-150400.14.21.2, kernel-source-azure-5.14.21-150400.14.21.1, kernel-syms-azure-5.14.21-150400.14.21.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2022:4072-1: An update that solves 32 vulnerabilities, contains 25 features and has 36 fixes is now available. Category: security (important) Bug References: 1065729,1071995,1152472,1152489,1188238,1194869,1196018,1196632,1199904,1200567,1200692,1200788,1202187,1202686,1202700,1202914,1203098,1203229,1203290,1203435,1203514,1203699,1203767,1203802,1203922,1204017,1204142,1204166,1204168,1204171,1204241,1204353,1204354,1204355,1204402,1204413,1204415,1204417,1204428,1204431,1204439,1204470,1204479,1204498,1204533,1204569,1204574,1204575,1204619,1204635,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204753,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970 CVE References: CVE-2022-1882,CVE-2022-2153,CVE-2022-28748,CVE-2022-2964,CVE-2022-2978,CVE-2022-3169,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3640,CVE-2022-3646,CVE-2022-3649,CVE-2022-40476,CVE-2022-40768,CVE-2022-42703,CVE-2022-43750 JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1649,PED-634,PED-676,PED-678,PED-679,PED-707,PED-732,PED-813,PED-817,PED-822,PED-825,PED-833,PED-842,PED-846,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-9246 Sources used: openSUSE Leap 15.4 (src): dtb-aarch64-5.14.21-150400.24.33.1, kernel-64kb-5.14.21-150400.24.33.2, kernel-debug-5.14.21-150400.24.33.2, kernel-default-5.14.21-150400.24.33.2, kernel-default-base-5.14.21-150400.24.33.2.150400.24.11.4, kernel-docs-5.14.21-150400.24.33.2, kernel-kvmsmall-5.14.21-150400.24.33.2, kernel-obs-build-5.14.21-150400.24.33.1, kernel-obs-qa-5.14.21-150400.24.33.1, kernel-source-5.14.21-150400.24.33.1, kernel-syms-5.14.21-150400.24.33.1, kernel-zfcpdump-5.14.21-150400.24.33.2 SUSE Linux Enterprise Workstation Extension 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2 SUSE Linux Enterprise Module for Live Patching 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2, kernel-livepatch-SLE15-SP4_Update_5-1-150400.9.3.4 SUSE Linux Enterprise Module for Legacy Software 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2 SUSE Linux Enterprise Module for Development Tools 15-SP4 (src): kernel-docs-5.14.21-150400.24.33.2, kernel-obs-build-5.14.21-150400.24.33.1, kernel-source-5.14.21-150400.24.33.1, kernel-syms-5.14.21-150400.24.33.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): kernel-64kb-5.14.21-150400.24.33.2, kernel-default-5.14.21-150400.24.33.2, kernel-default-base-5.14.21-150400.24.33.2.150400.24.11.4, kernel-source-5.14.21-150400.24.33.1, kernel-zfcpdump-5.14.21-150400.24.33.2 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-5.14.21-150400.24.33.2, kernel-default-base-5.14.21-150400.24.33.2.150400.24.11.4 SUSE Linux Enterprise High Availability 15-SP4 (src): kernel-default-5.14.21-150400.24.33.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2022:4617-1: An update that solves 96 vulnerabilities, contains 50 features and has 246 fixes is now available. Category: security (important) Bug References: 1023051,1032323,1065729,1071995,1152472,1152489,1156395,1164051,1177471,1184350,1185032,1188238,1189297,1189999,1190256,1190497,1190969,1192968,1193629,1194023,1194592,1194869,1194904,1195480,1195917,1196018,1196444,1196616,1196632,1196867,1196869,1197158,1197391,1197659,1197755,1197756,1197757,1197763,1198189,1198410,1198577,1198702,1198971,1199086,1199364,1199515,1199670,1199904,1200015,1200058,1200268,1200288,1200301,1200313,1200431,1200465,1200494,1200544,1200567,1200622,1200644,1200651,1200692,1200788,1200845,1200868,1200869,1200870,1200871,1200872,1200873,1201019,1201308,1201309,1201310,1201361,1201427,1201442,1201455,1201489,1201610,1201675,1201725,1201726,1201768,1201865,1201940,1201941,1201948,1201954,1201956,1201958,1202095,1202096,1202097,1202113,1202131,1202154,1202187,1202262,1202265,1202312,1202341,1202346,1202347,1202385,1202393,1202447,1202471,1202558,1202623,1202636,1202672,1202681,1202685,1202686,1202700,1202710,1202711,1202712,1202713,1202715,1202716,1202757,1202758,1202759,1202761,1202762,1202763,1202764,1202765,1202766,1202767,1202768,1202769,1202770,1202771,1202773,1202774,1202775,1202776,1202778,1202779,1202780,1202781,1202782,1202783,1202822,1202823,1202824,1202860,1202867,1202872,1202874,1202898,1202914,1202960,1202989,1202992,1202993,1203002,1203008,1203036,1203039,1203041,1203063,1203066,1203067,1203098,1203101,1203107,1203116,1203117,1203138,1203139,1203159,1203183,1203197,1203208,1203229,1203263,1203290,1203338,1203360,1203361,1203389,1203391,1203410,1203435,1203505,1203511,1203514,1203552,1203606,1203664,1203693,1203699,1203767,1203769,1203770,1203794,1203798,1203802,1203829,1203893,1203902,1203906,1203908,1203922,1203935,1203939,1203960,1203969,1203987,1203992,1203994,1204017,1204051,1204059,1204060,1204092,1204125,1204132,1204142,1204166,1204168,1204170,1204171,1204183,1204228,1204241,1204289,1204290,1204291,1204292,1204353,1204354,1204355,1204402,1204405,1204413,1204414,1204415,1204417,1204424,1204428,1204431,1204432,1204439,1204470,1204479,1204486,1204498,1204533,1204569,1204574,1204575,1204576,1204619,1204624,1204631,1204635,1204636,1204637,1204646,1204647,1204650,1204653,1204693,1204705,1204719,1204728,1204745,1204753,1204780,1204810,1204850,1204868,1204926,1204933,1204934,1204947,1204957,1204963,1204970,1205007,1205100,1205111,1205113,1205128,1205130,1205149,1205153,1205220,1205257,1205264,1205282,1205313,1205331,1205332,1205427,1205428,1205473,1205496,1205507,1205514,1205521,1205567,1205616,1205617,1205653,1205671,1205679,1205683,1205700,1205705,1205709,1205711,1205744,1205764,1205796,1205882,1205993,1206035,1206036,1206037,1206045,1206046,1206047,1206048,1206049,1206050,1206051,1206056,1206057,1206113,1206114,1206147,1206149,1206207,1206273,1206391 CVE References: CVE-2016-3695,CVE-2020-16119,CVE-2020-36516,CVE-2021-33135,CVE-2021-4037,CVE-2022-1184,CVE-2022-1263,CVE-2022-1882,CVE-2022-20368,CVE-2022-20369,CVE-2022-2153,CVE-2022-2586,CVE-2022-2588,CVE-2022-2602,CVE-2022-26373,CVE-2022-2639,CVE-2022-2663,CVE-2022-28356,CVE-2022-28693,CVE-2022-2873,CVE-2022-28748,CVE-2022-2905,CVE-2022-2938,CVE-2022-2959,CVE-2022-2964,CVE-2022-2977,CVE-2022-2978,CVE-2022-3028,CVE-2022-3078,CVE-2022-3114,CVE-2022-3169,CVE-2022-3176,CVE-2022-3202,CVE-2022-32250,CVE-2022-32296,CVE-2022-3239,CVE-2022-3303,CVE-2022-33981,CVE-2022-3424,CVE-2022-3435,CVE-2022-3521,CVE-2022-3524,CVE-2022-3526,CVE-2022-3535,CVE-2022-3542,CVE-2022-3545,CVE-2022-3565,CVE-2022-3566,CVE-2022-3567,CVE-2022-3577,CVE-2022-3586,CVE-2022-3594,CVE-2022-3619,CVE-2022-3621,CVE-2022-3625,CVE-2022-3628,CVE-2022-3629,CVE-2022-3633,CVE-2022-3635,CVE-2022-3640,CVE-2022-3643,CVE-2022-3646,CVE-2022-3649,CVE-2022-36879,CVE-2022-36946,CVE-2022-3707,CVE-2022-3903,CVE-2022-39188,CVE-2022-39189,CVE-2022-39190,CVE-2022-40476,CVE-2022-40768,CVE-2022-4095,CVE-2022-41218,CVE-2022-4129,CVE-2022-4139,CVE-2022-41674,CVE-2022-41848,CVE-2022-41849,CVE-2022-41850,CVE-2022-41858,CVE-2022-42328,CVE-2022-42329,CVE-2022-42703,CVE-2022-42719,CVE-2022-42720,CVE-2022-42721,CVE-2022-42722,CVE-2022-42895,CVE-2022-42896,CVE-2022-43750,CVE-2022-4378,CVE-2022-43945,CVE-2022-45869,CVE-2022-45888,CVE-2022-45934 JIRA References: PED-1082,PED-1084,PED-1085,PED-1096,PED-1211,PED-1573,PED-1649,PED-1706,PED-1936,PED-2684,PED-387,PED-529,PED-611,PED-634,PED-652,PED-664,PED-676,PED-678,PED-679,PED-682,PED-688,PED-707,PED-720,PED-729,PED-732,PED-755,PED-763,PED-813,PED-817,PED-822,PED-824,PED-825,PED-833,PED-842,PED-846,PED-849,PED-850,PED-851,PED-856,PED-857,SLE-13847,SLE-18130,SLE-19359,SLE-19924,SLE-20183,SLE-23766,SLE-24572,SLE-24682,SLE-24814,SLE-9246 Sources used: openSUSE Leap Micro 5.3 (src): kernel-rt-5.14.21-150400.15.5.1 openSUSE Leap 15.4 (src): kernel-rt-5.14.21-150400.15.5.1, kernel-rt_debug-5.14.21-150400.15.5.1, kernel-source-rt-5.14.21-150400.15.5.1, kernel-syms-rt-5.14.21-150400.15.5.1 SUSE Linux Enterprise Module for Realtime 15-SP4 (src): kernel-rt-5.14.21-150400.15.5.1, kernel-rt_debug-5.14.21-150400.15.5.1, kernel-source-rt-5.14.21-150400.15.5.1, kernel-syms-rt-5.14.21-150400.15.5.1 SUSE Linux Enterprise Module for Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4-RT_Update_1-1-150400.1.3.1 SUSE Linux Enterprise Micro 5.3 (src): kernel-rt-5.14.21-150400.15.5.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
No error anymore with kernel 6.1.8 on RPi3: https://openqa.opensuse.org/tests/3074487#step/journal_check/31 I think we can close. @Ivan?
Yee, finally! :-)
And closing.