commits January 2023

commits@lists.open-mesh.org

1 participants
283 discussions

[doc] main: Merge branch 'backup-redmine/2021-11-13' (8185e6e1)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit 8185e6e1e6b6e093d7cb86e60079c12978e21743 Merge: 29524222 3adacdf2 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Nov 13 14:18:04 2021 +0100 Merge branch 'backup-redmine/2021-11-13' >--------------------------------------------------------------- batman-adv/Multicast-optimizations-tech.rst | 39 +- devtools/Crashdumps_with_kexec.rst | 586 ++++++++++++++++++++++++++++ devtools/Crashlog_with_pstore.rst | 359 +++++++++++++++++ devtools/Kernel_Debugging.rst | 2 +- devtools/Kernel_debugging_over_JTAG.rst | 28 +- devtools/Kernel_debugging_with_kgdb.rst | 290 +++++++++----- 6 files changed, 1164 insertions(+), 140 deletions(-) Diff suppressed because of size. To see it, use: git diff-tree --patch-with-stat --no-color --find-copies-harder --ignore-space-at-eol --cc 8185e6e1e6b6e093d7cb86e60079c12978e21743

1 0

[doc] main: Kernel_Debugging: Fix index of various pages (5b46234c)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branch : main >--------------------------------------------------------------- commit 5b46234c75d7a3108fbc6690135b159355fce8c7 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Nov 13 14:20:29 2021 +0100 Kernel_Debugging: Fix index of various pages Signed-off-by: Sven Eckelmann <sven(a)narfation.org> >--------------------------------------------------------------- 5b46234c75d7a3108fbc6690135b159355fce8c7 devtools/Kernel_Debugging.rst | 3 --- 1 file changed, 3 deletions(-) diff --git a/devtools/Kernel_Debugging.rst b/devtools/Kernel_Debugging.rst index 6563579e..5628d203 100644 --- a/devtools/Kernel_Debugging.rst +++ b/devtools/Kernel_Debugging.rst @@ -24,9 +24,6 @@ Various .. toctree:: :maxdepth: 1 - Kernel_debugging_with_qemu's_GDB_server - Kernel_debugging_with_kgdb - Kernel_debugging_over_JTAG GDB_Linux_snippets Crashlog_with_pstore Crashdumps_with_kexec

1 0

[doc] backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: devtools/Kernel_debugging_with_kgdb (796b9209)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 796b9209e0cd784d41a09fd6acb4d93ab19d6186 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Nov 13 14:02:49 2021 +0000 doc: devtools/Kernel_debugging_with_kgdb >--------------------------------------------------------------- 796b9209e0cd784d41a09fd6acb4d93ab19d6186 devtools/Kernel_debugging_with_kgdb.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devtools/Kernel_debugging_with_kgdb.textile b/devtools/Kernel_debugging_with_kgdb.textile index cb403ba3..19792de1 100644 --- a/devtools/Kernel_debugging_with_kgdb.textile +++ b/devtools/Kernel_debugging_with_kgdb.textile @@ -351,10 +351,10 @@ h3. Starting up session $ /agent-proxy/agent-proxy '127.0.0.1:5550^127.0.0.1:5551' 0 /dev/ttyUSB0,115200 </code></pre> -To connect to the terminal session, a simple telnet is enough: +To connect to the terminal session, a simple telnet or telnet-like tool is enough: <pre><code class="shell"> -$ telnet localhost 5550 +$ screen //telnet localhost 5550 </code></pre> The setup of the kgdboc must happen exactly as described before. Including the switch to the debugging mode via sysrq.

1 0

[doc] backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-optimizations-tech (9c8f93ea)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 9c8f93ea2289fb0ca13f73fa7e3af767fb039d59 Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Sun Oct 31 23:51:47 2021 +0000 doc: batman-adv/Multicast-optimizations-tech >--------------------------------------------------------------- 9c8f93ea2289fb0ca13f73fa7e3af767fb039d59 batman-adv/Multicast-optimizations-tech.textile | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/batman-adv/Multicast-optimizations-tech.textile b/batman-adv/Multicast-optimizations-tech.textile index f534c53e..4d41a50a 100644 --- a/batman-adv/Multicast-optimizations-tech.textile +++ b/batman-adv/Multicast-optimizations-tech.textile @@ -79,15 +79,17 @@ Example: ff02::1 (all nodes) | (excl. all nodes addr.) |=. supported without bridges��. Example: 224.0.0.251 (mDNS) |=. supported��. Example: ff12::39 (locally administrated) | -| *routable* |=. supported without bridges��. -Example: 239.1.2.3 (locally administrated) |=. supported��. +| *routable* |=. supported��. +Example: 239.1.2.3 (locally administrated) |=. supported��. Example: ff0e::101 (NTP) | ��: These addresses cannot be considered for optimization towards nodes which have a bridge interface on top of their batman interface as they are not snoopable. See [[multicast-optimizations-flags#BATADV_MCAST_WANT_ALL_UNSNOOPABLES]] for details. ��: In bridged scenarios, an IGMP/MLD querier needs to be present in the mesh. Also, a 3.17 kernel or newer is required. -��: Routable IPv4 multicast addresses in bridged scenarios are not supported yet. See [[multicast-optimizations-tech#routable-multicast-addresses]] for details. +��: Routable IPv4 multicast addresses in bridged scenarios require a 5.14 kernel or newer and "batman-adv 2021.2":https://www.open-mesh.org/news/104 or newer. Before that only supported without bridges. + +��: With a 5.14 kernel or newer and "batman-adv 2021.2":https://www.open-mesh.org/news/104 or newer proper "MRD":https://www.rfc-editor.org/rfc/rfc4286.html support is used to detect multicast routers. Otherwise with batman-adv v2019.3 until v2021.1 multicast routers are "guessed" by listeners on ff02::2. Which will "overestimate" by including unicast routers without multicast routing, too. For details on IPv4 and IPv6 multicast address ranges check out this detailed article on "Wikipedia":https://en.wikipedia.org/wiki/Multicast_address.

1 0

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit c7592a83369c97e8d60b0295a82c18eeba7750f8 Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Sun Oct 31 23:58:36 2021 +0000 doc: batman-adv/Multicast-optimizations-tech >--------------------------------------------------------------- c7592a83369c97e8d60b0295a82c18eeba7750f8 batman-adv/Multicast-optimizations-tech.textile | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/batman-adv/Multicast-optimizations-tech.textile b/batman-adv/Multicast-optimizations-tech.textile index 4d41a50a..7c2664a2 100644 --- a/batman-adv/Multicast-optimizations-tech.textile +++ b/batman-adv/Multicast-optimizations-tech.textile @@ -95,9 +95,7 @@ For details on IPv4 and IPv6 multicast address ranges check out this detailed ar h3. Routable multicast addresses -For routable multicast addresses, further consideration has to be given: The according multicast packets not only need to be forwarded to any multicast listener on the local link, but to any multicast router, too. Otherwise off-link listeners, which are only reachable via a layer 3 multicast router, would not receive these multicast packets anymore. - -batman-adv currently detects IPv6 multicast routers by searching for ff02::2 all-routers multicast listeners (which overestimates by including unicast routers, too). For proper IPv4+IPv6 multicast router detection "Multicast Router Discovery":https://tools.ietf.org/search/rfc4286 needs to be implemented in batman-adv (implemented in the bridge, tapping into this is still ToDo). +For routable multicast addresses, further consideration has to be given: The according multicast packets not only need to be forwarded to any multicast listener on the local link, but to any multicast router, too. Otherwise off-link listeners, which are only reachable via a layer 3 multicast router, would not receive these multicast packets anymore. batman-adv detects node local multicast routers through _/proc/sys/net/<ipv4|ipv6>/conf/<iface>/mc_forwarding_ and uses a bridge's "Multicast Router Discovery":https://tools.ietf.org/search/rfc4286 capabilities for bridged-in hosts. h2. Limitations

1 0

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 4f9ff16454760bcb145808e06ce18d9d0bf17f9d Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Mon Nov 1 00:04:43 2021 +0000 doc: batman-adv/Multicast-optimizations-tech >--------------------------------------------------------------- 4f9ff16454760bcb145808e06ce18d9d0bf17f9d batman-adv/Multicast-optimizations-tech.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Multicast-optimizations-tech.textile b/batman-adv/Multicast-optimizations-tech.textile index 7c2664a2..de43133f 100644 --- a/batman-adv/Multicast-optimizations-tech.textile +++ b/batman-adv/Multicast-optimizations-tech.textile @@ -89,7 +89,7 @@ Example: ff0e::101 (NTP) | ��: Routable IPv4 multicast addresses in bridged scenarios require a 5.14 kernel or newer and "batman-adv 2021.2":https://www.open-mesh.org/news/104 or newer. Before that only supported without bridges. -��: With a 5.14 kernel or newer and "batman-adv 2021.2":https://www.open-mesh.org/news/104 or newer proper "MRD":https://www.rfc-editor.org/rfc/rfc4286.html support is used to detect multicast routers. Otherwise with batman-adv v2019.3 until v2021.1 multicast routers are "guessed" by listeners on ff02::2. Which will "overestimate" by including unicast routers without multicast routing, too. +��: With a 5.14 kernel or newer and "batman-adv 2021.2":https://www.open-mesh.org/news/104 or newer proper "MRD":https://www.rfc-editor.org/rfc/rfc4286.html support is used to detect multicast routers. Otherwise with "batman-adv v2019.3":https://www.open-mesh.org/news/92 until v2021.1 multicast routers are "guessed" by listeners on ff02::2. Which will "overestimate" by including unicast routers without multicast routing, too. For details on IPv4 and IPv6 multicast address ranges check out this detailed article on "Wikipedia":https://en.wikipedia.org/wiki/Multicast_address.

1 0

14 Jan '23

1 0

[doc] backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: devtools/Crashdumps_with_kexec (9348b3e8)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 9348b3e8d8cb4b7b920001e9e241a8c718c59730 Author: Sven Eckelmann <sven(a)narfation.org> Date: Thu Oct 21 12:35:13 2021 +0000 doc: devtools/Crashdumps_with_kexec >--------------------------------------------------------------- 9348b3e8d8cb4b7b920001e9e241a8c718c59730 devtools/Crashdumps_with_kexec.textile | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/devtools/Crashdumps_with_kexec.textile b/devtools/Crashdumps_with_kexec.textile index a7201076..9f273b4f 100644 --- a/devtools/Crashdumps_with_kexec.textile +++ b/devtools/Crashdumps_with_kexec.textile @@ -131,7 +131,7 @@ h3. ath79 The setup under ath79 is significantly more complicated. It already starts with the problem that the normal kernel and the crashkernel are completely different ones. This is the result of the missing relocation support and the inability of kexec to load an uImage with appended DTB. -Another problem is the <code>CONFIG_HARDENED_USERCOPY=y</code> which prevents kexec under MIPS at the moment. So just disable it in in the kernel configuration. Also make sure that the devicetree for the device already reserves some space for the crashkernel. In this example, it is a 128MB device and 32 MB are reserved at the 64MB boundary +Another problem is the <code>CONFIG_HARDENED_USERCOPY=y</code> which prevents kexec under MIPS at the moment. So just disable it in in the kernel configuration. Also make sure that the devicetree for the device already reserves some space for the crashkernel. In this example, it is a 128MB device and 32 MB are reserved at the 16MB boundary <pre> diff --git a/target/linux/generic/config-5.4 b/target/linux/generic/config-5.4 @@ -153,7 +153,7 @@ index e922d23d2c..0d24b4c041 100644 chosen { - bootargs = "console=ttyS0,115200n8"; -+ bootargs = "console=ttyS0,115200n8 crashkernel=32M@0x04000000"; ++ bootargs = "console=ttyS0,115200n8 crashkernel=32M@0x01000000"; }; aliases { @@ -164,7 +164,7 @@ This should be visible when booting this device: <pre><code class="shell"> root@OpenWrt:/# cat /proc/iomem |grep -e 'System RAM' -e 'Crash kernel' 00000000-07ffffff : System RAM - 04000000-05ffffff : Crash kernel + 01000000-02ffffff : Crash kernel </code></pre> The device should of course also have the kexec support enabled in OpenWrt's <code>.config</code> @@ -230,7 +230,7 @@ index e37b728554..24892b7435 100644 + +CONFIG_CRASH_DUMP=y +CONFIG_PROC_VMCORE=y -+CONFIG_PHYSICAL_START=0x04000000 ++CONFIG_PHYSICAL_START=0x01000000 </code></pre> As mentioned earlier, this kernel is not yet ready to be used because the device tree must be embedded:

1 0

[doc] backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: devtools/Crashdumps_with_kexec (cc16d588)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit cc16d58848bb3b09954291a8ef2f3c120659d99f Author: Sven Eckelmann <sven(a)narfation.org> Date: Thu Oct 21 12:43:01 2021 +0000 doc: devtools/Crashdumps_with_kexec >--------------------------------------------------------------- cc16d58848bb3b09954291a8ef2f3c120659d99f devtools/Crashdumps_with_kexec.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devtools/Crashdumps_with_kexec.textile b/devtools/Crashdumps_with_kexec.textile index 9f273b4f..c63235c1 100644 --- a/devtools/Crashdumps_with_kexec.textile +++ b/devtools/Crashdumps_with_kexec.textile @@ -203,7 +203,7 @@ index 54067570a2..8a88b5f140 100644 </code></pre> -The next major part is to prepare a kernel which can be booted by kexec, supports crashdump and is running from the correct physical address. The former requires that the dtb is embedded as part of the elf binary - which is not how OpenWrt is currently building the ath79 kernels. Luckily, it only requires a config change (<code>CONFIG_MIPS_RAW_APPENDED_DTB=y</code> to <code>CONFIG_MIPS_ELF_APPENDED_DTB=y</code>) and some binutils commands (objcopy, strip, ...). The setup of crashdump is also just a couple of configuration settings. The most important setting is <code>CONFIG_PHYSICAL_START</code> which must match the address in <code>crashkernel</code> +The next major part is to prepare a kernel which can be booted by kexec, supports crashdump and is running from the correct physical address. The former requires that the dtb is embedded as part of the elf binary - which is not how OpenWrt is currently building the ath79 kernels. Luckily, it only requires a config change (<code>CONFIG_MIPS_RAW_APPENDED_DTB=y</code> to <code>CONFIG_MIPS_ELF_APPENDED_DTB=y</code>) and some binutils commands (objcopy, strip, ...). The setup of crashdump is also just a couple of configuration settings. The most important setting is <code>CONFIG_PHYSICAL_START</code> which must match the address in <code>crashkernel</code> + 0x80000000 (the address where physical pages are mapped to in the virtual address space for this architecture). <pre><code class="diff"> diff --git a/target/linux/ath79/config-5.4 b/target/linux/ath79/config-5.4 @@ -230,7 +230,7 @@ index e37b728554..24892b7435 100644 + +CONFIG_CRASH_DUMP=y +CONFIG_PROC_VMCORE=y -+CONFIG_PHYSICAL_START=0x01000000 ++CONFIG_PHYSICAL_START=0x81000000 </code></pre> As mentioned earlier, this kernel is not yet ready to be used because the device tree must be embedded:

1 0

[doc] backup-redmine/2021-11-13,backup-redmine/2021-12-11,backup-redmine/2022-01-08,backup-redmine/2022-02-12,backup-redmine/2022-03-12,backup-redmine/2022-04-09,backup-redmine/2022-05-07,backup-redmine/2022-06-11,backup-redmine/2022-08-06,backup-redmine/2022-10-07,backup-redmine/2022-11-14,backup-redmine/2023-01-14,main: doc: devtools/Crashdumps_with_kexec (d139ec33)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

1 0

← Newer
1
...
11
12
13
14
15
16
17
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits January 2023