Bug#980864: Linux 5.10.9-1 is prevented from migrating to testing because build fails on mipsel
Package: src:linux Version: 5.10.9-1 Severity: normal According to the tracker page for the linux package, https://tracker.debian.org/pkg/linux under issues preventing migration is one important entry: - missing build on mipsel Looking at the build logs, it seems that the build didn't even start whereas on previous uploads it built fine for the architecture. thanks!
Bug#980864: Linux 5.10.9-1 is prevented from migrating to testing because build fails on mipsel
Hi Salvatore, On Sat, 23 Jan 2021 at 13:13, Salvatore Bonaccorso wrote: > > Christopher, > > On Sat, Jan 23, 2021 at 11:24:21AM +, Christopher Obbard wrote: > > Package: src:linux > > Version: 5.10.9-1 > > Severity: normal > > > > According to the tracker page for the linux package, > > https://tracker.debian.org/pkg/linux > > > > under issues preventing migration is one important entry: > > - missing build on mipsel > > > > Looking at the build logs, it seems that the build didn't even start > > whereas on previous uploads it built fine for the architecture. > > Give it time :). It would not have migrated yet anyway. You can see on > the tracker page it is only 1 day old. I was only uploaded recently, > and mipsel build takes time (on eberlin were it currently builds > usually around 1d and 20h). right, I see on the buildd status page that it is "Building" which really means the package is waiting to build or building. I guess it's the former since no logs are available yet ;-). Thanks again for explaining, and sorry for the noise: the Debian systems can be quite confusing for a relative newcomer and a little explanation is very helpful! > > I will close the bug already, in case it FTBFS on mipsel we can look > at it. > > Regards, > Salvatore
Bug#964036: linux: Please set CONFIG_HWLAT_TRACER=y
Source: linux Severity: wishlist Dear Maintainer, Setting CONFIG_HWLAT_TRACER=y enables a tracer to detect hardware latencies with no overhead when not used. It is not designed to be run on a production system, but is a useful tracer to use in embedded systems. Other distros enable this configuration option, I see no security issues or performance issues for users since this is by-default turned off so has to be enabled at runtime. Thanks, Chris -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#932935:
Also broken for me on Debian Sid amd64 with kernel version linux-image-4.19.0-5-amd64. Same error message. Selecting version 4.19.0-4 in the grub menu makes the error go away. This is a critical error and will no doubt break many systems so belongs to have an appropriate severity.
