Status Update
No update yet.
Comments
ap...@google.com
It doesn't look like this bug has a link to the affected dataset(s) in Earth
Engine. Please reply to this bug with a comment containing a URL of the form
"
If this issue doesn't affect an existing dataset, consider moving in into the "Public Trackers > Earth Engine > Datasets > New Datasets" component. If the dataset is a new or updated version of an existing dataset, you can add the URL of the existing one. And if you cannot add a URL, you can disable future automated messages by adding a comment with "dataset_bug_ranker: disable" on its own line.
Reason: Issue does not contain a dataset URL. dataset_bug_ranker: remind=P7D
ap...@google.com
This is not for a dataset but google earth panels themselves
On Thu, 16 Jan 2025, 13:25 , <buganizer-system@google.com> wrote:
On Thu, 16 Jan 2025, 13:25 , <buganizer-system@google.com> wrote:
ap...@google.com
If this is not the correct place to ask this question could you please
direct me to the appropriate place, many thanks
On Thu, Jan 16, 2025 at 1:39 PM Hope Irvine <hopekathleenirvine@gmail.com>
wrote:
direct me to the appropriate place, many thanks
On Thu, Jan 16, 2025 at 1:39 PM Hope Irvine <hopekathleenirvine@gmail.com>
wrote:
ap...@google.com
You probably just dragged the vertical divider too far to the right. Try dragging it back.
ap...@google.com
Project: chromiumos/third_party/kernel
Branch: chromeos-5.10
commit 2402f349c8523afddb44cf74f826c3f2a382731f
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:25:44 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (all backtrace)
The buddy hard lockup detector should try backtracing on all
CPUs. Right now it doesn't. Copy that bit of logic from the normal
hardlockup detector.
NOTE: On arm64 (the current user of the buddy detector), this won't
(yet) do anything. Soon, hopefully.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id225408348d8a45e68080d08139bc6d9e170000a
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4438220
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5003361
Reviewed-by: Guenter Roeck <groeck@chromium.org>
M kernel/watchdog_buddy_cpu.c
https://chromium-review.googlesource.com/5003361
Branch: chromeos-5.10
commit 2402f349c8523afddb44cf74f826c3f2a382731f
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:25:44 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (all backtrace)
The buddy hard lockup detector should try backtracing on all
CPUs. Right now it doesn't. Copy that bit of logic from the normal
hardlockup detector.
NOTE: On arm64 (the current user of the buddy detector), this won't
(yet) do anything. Soon, hopefully.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id225408348d8a45e68080d08139bc6d9e170000a
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on:
Reviewed-by: Guenter Roeck <groeck@chromium.org>
M kernel/watchdog_buddy_cpu.c
ap...@google.com
Project: chromiumos/third_party/kernel
Branch: chromeos-5.4
commit 28e15645f7f4a7be395d1ea547849792ea4a1339
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:25:44 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (all backtrace)
The buddy hard lockup detector should try backtracing on all
CPUs. Right now it doesn't. Copy that bit of logic from the normal
hardlockup detector.
NOTE: On arm64 (the current user of the buddy detector), this won't
(yet) do anything. Soon, hopefully.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id225408348d8a45e68080d08139bc6d9e170000a
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4438220
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5001978
Reviewed-by: Guenter Roeck <groeck@chromium.org>
M kernel/watchdog_buddy_cpu.c
https://chromium-review.googlesource.com/5001978
Branch: chromeos-5.4
commit 28e15645f7f4a7be395d1ea547849792ea4a1339
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:25:44 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (all backtrace)
The buddy hard lockup detector should try backtracing on all
CPUs. Right now it doesn't. Copy that bit of logic from the normal
hardlockup detector.
NOTE: On arm64 (the current user of the buddy detector), this won't
(yet) do anything. Soon, hopefully.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id225408348d8a45e68080d08139bc6d9e170000a
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on:
Reviewed-by: Guenter Roeck <groeck@chromium.org>
M kernel/watchdog_buddy_cpu.c
ap...@google.com
Project: chromiumos/third_party/kernel
Branch: chromeos-5.4
commit 1b415cbdc4d2258cb37610c4a66039ebffdec9f6
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:15:31 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (sysctl)
The CHROMIUM patch accidentally didn't expose the hardlockup panic
sysctls based on the right config. Fix it.
NOTE: Only one of these two sysctls actually does something with the
current buddy detector. You can turn on/off the hard lockup detector
but it doesn't (yet) support tracing other CPUs.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id88d1fb603308e7210c30e42bb6e4e6a4be65a0c
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4438219
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
(cherry picked from commit 71986679fe52d94286f9051f09b958ecf582c7fc)
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5008220
Commit-Queue: Guenter Roeck <groeck@chromium.org>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
M kernel/sysctl.c
https://chromium-review.googlesource.com/5008220
Branch: chromeos-5.4
commit 1b415cbdc4d2258cb37610c4a66039ebffdec9f6
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:15:31 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (sysctl)
The CHROMIUM patch accidentally didn't expose the hardlockup panic
sysctls based on the right config. Fix it.
NOTE: Only one of these two sysctls actually does something with the
current buddy detector. You can turn on/off the hard lockup detector
but it doesn't (yet) support tracing other CPUs.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id88d1fb603308e7210c30e42bb6e4e6a4be65a0c
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
(cherry picked from commit 71986679fe52d94286f9051f09b958ecf582c7fc)
Reviewed-on:
Commit-Queue: Guenter Roeck <groeck@chromium.org>
Reviewed-by: Guenter Roeck <groeck@chromium.org>
M kernel/sysctl.c
ap...@google.com
Project: chromiumos/third_party/kernel
Branch: chromeos-5.10
commit 9c9acd59e87ef7423808dfc5b4109732a05f78db
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:15:31 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (sysctl)
The CHROMIUM patch accidentally didn't expose the hardlockup panic
sysctls based on the right config. Fix it.
NOTE: Only one of these two sysctls actually does something with the
current buddy detector. You can turn on/off the hard lockup detector
but it doesn't (yet) support tracing other CPUs.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id88d1fb603308e7210c30e42bb6e4e6a4be65a0c
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/4438219
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
(cherry picked from commit 71986679fe52d94286f9051f09b958ecf582c7fc)
Reviewed-on:https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5008219
Reviewed-by: Guenter Roeck <groeck@chromium.org>
Commit-Queue: Guenter Roeck <groeck@chromium.org>
M kernel/sysctl.c
https://chromium-review.googlesource.com/5008219
Branch: chromeos-5.10
commit 9c9acd59e87ef7423808dfc5b4109732a05f78db
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Apr 17 17:15:31 2023
FIXUP: CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus (sysctl)
The CHROMIUM patch accidentally didn't expose the hardlockup panic
sysctls based on the right config. Fix it.
NOTE: Only one of these two sysctls actually does something with the
current buddy detector. You can turn on/off the hard lockup detector
but it doesn't (yet) support tracing other CPUs.
UPSTREAM-TASK=b:172213097
BUG=b:278598383, b:278594093, b:197061987, b:172213097
TEST=echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
Change-Id: Id88d1fb603308e7210c30e42bb6e4e6a4be65a0c
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on:
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
(cherry picked from commit 71986679fe52d94286f9051f09b958ecf582c7fc)
Reviewed-on:
Reviewed-by: Guenter Roeck <groeck@chromium.org>
Commit-Queue: Guenter Roeck <groeck@chromium.org>
M kernel/sysctl.c
Description
To fix
kernel.hung_task_all_cpu_backtraceto enable backtraces on all CPUs when we get a hung task. That work on x86, but unfortunately not on arm64 boards.The problem is that
trigger_all_cpu_backtrace()is a no-op unlessarch_trigger_cpumask_backtrace()is defined for an architecture and that's not defined for arm64.It's actually pretty easy to copy the arm32 implementation for this and use it for arm64 (even I could do it!), but that's a somewhat weak implementation. It doesn't actually use NMIs. As talked about in the original arm32
...even better would be to figure out how to resolve this with