The malta subtargets for mips64 and mips64el fail to start the init process at boot, resulting in a boot loop. The issue was raised and analyzed within FS#3277. Investigation suggested code near the [vdso] memory area of the process was long jumping into a region inaccessible to the process, e.g. init: - preinit - init: Launched preinit instance, pid=522 do_page_fault(): sending SIGSEGV to init for invalid read access from 0000000000000360 epc = 0000000000000360 in init[aaab42b000+4000] ra = 000000fffee385e0 in Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Rebooting in 1 seconds.. Note the low-memory read access and epc are the same. Upstream kernel 5.6 included a relevant patch and discussion: * d3f703c4359f ("mips: vdso: fix 'jalr t9' crash in vdso code") Disassembly of the failing kernel's vdso.so confirmed presence of the telltale long jumps, e.g.: 00000000000007c0 <__vdso_clock_getres@@LINUX_2.6>: [...] 7dc: 0320f809 jalr t9 [...] Restore booting mips64/mips64el malta by backporting the above commit: * 310-v5.6-mips-vdso-fix-jalr-t9-crash-in-vdso-code.patch Fixes: 54310a3aa02f ("malta: add kernel 5.4 config") Fixes: FS#3277 Ref: https://bugs.openwrt.org/index.php?do=details&task_id=3277 Signed-off-by: Tony Ambardar <firstname.lastname@example.org>
|1 day ago|
|.github||2 years ago|
|config||5 days ago|
|include||3 days ago|
|package||23 hours ago|
|scripts||3 days ago|
|target||22 hours ago|
|toolchain||4 days ago|
|tools||1 day ago|
|.gitattributes||8 years ago|
|.gitignore||1 month ago|
|BSDmakefile||13 years ago|
|Config.in||2 years ago|
|LICENSE||1 week ago|
|Makefile||1 month ago|
|README.md||1 week ago|
|feeds.conf.default||1 month ago|
|logo.svg||1 week ago|
|rules.mk||5 days ago|
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
To build your own firmware you need a GNU/Linux, BSD or MacOSX system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
gcc binutils bzip2 flex python3 perl make find grep diff unzip gawk getopt subversion libz-dev libc-dev
./scripts/feeds update -a to obtain all the latest package definitions
defined in feeds.conf / feeds.conf.default
./scripts/feeds install -a to install symlinks for all obtained
packages into package/feeds/
make menuconfig to select your preferred configuration for the
toolchain, target system & firmware packages.
make to build your firmware. This will download all sources, build the
cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen
applications for your target system.
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
opkg. If you’re looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
OpenWrt Packages: Community repository of ported packages.
OpenWrt Routing: Packages specifically focused on (mesh) routing.
For a list of supported devices see the OpenWrt Hardware Database
OpenWrt is licensed under GPL-2.0