Bug#962485: Bug#983583: FTBFS on mips64el and mipsel
YunQiang Su 于2021年3月29日周一 下午4:56写道：
>
> YunQiang Su 于2021年3月29日周一 下午1:31写道：
> >
> > YunQiang Su 于2021年3月29日周一 下午1:06写道：
> > >
> > > YunQiang Su 于2021年3月29日周一 上午11:45写道：
> > > >
> > > > Shengjing Zhu 于2021年3月29日周一 上午11:40写道：
> > > > >
> > > > > On Mon, Mar 29, 2021 at 09:22:29AM +0800, YunQiang Su wrote:
> > > > > > Shengjing Zhu 于2021年3月28日周日 上午12:12写道：
> > > > > > >
> > > > > > > Control: reopen -1
> > > > > > > Control: severity -1 important
> > > > > > >
> > > > > > > On Sat, Mar 27, 2021 at 11:46 PM Adrian Bunk
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > On Sat, Feb 27, 2021 at 02:33:38AM +0800, Shengjing Zhu wrote:
> > > > > > > > > Source: golang-github-sylabs-sif
> > > > > > > > > Version: 1.0.9-2
> > > > > > > > > Severity: serious
> > > > > > > > > X-Debbugs-Cc: z...@debian.org
> > > > > > > > >
> > > > > > > > > Tried 3 times on buildd and failed at same test.
> > > > > > > > >
> > > > > > > > > === RUN TestAddDelObject
> > > > > > > > > unexpected fault address 0xffc8a0c000
> > > > > > > > > fatal error: fault
> > > > > > > > > [signal SIGSEGV: segmentation violation code=0x2
> > > > > > > > > addr=0xffc8a0c000 pc=0x12007ebe4]
> > > > > > > > >
> > > > > > > > > goroutine 22 [running]:
> > > > > > > > > runtime.throw(0x1201b74ed, 0x5)
> > > > > > > > > /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c
> > > > > > > > > fp=0xce3430 sp=0xce3408 pc=0x120040afc
> > > > > > > > > runtime.sigpanic()
> > > > > > > > >
> > > > > > > > > Since it has been built on mipsx before, the failure will
> > > > > > > > > cause it impossible
> > > > > > > > > to fix issue later on these arch.
> > > > > > > > >
> > > > > > > > > It should either be removed from these arch or get fixed.
> > > > > > > >
> > > > > > > > This appears to be fixed now:
> > > > > > > > https://buildd.debian.org/status/package.php?p=golang-github-sylabs-sif
> > > > > > >
> > > > > > > The difference between these builds, seems to be a 5.10 kernel and
> > > > > > > 4.19 kernel on buildd.
> > > > > > >
> > > > > > > I'll reopen this but downgrade the severity, and loop
> > > > > > > debian-mips@ to
> > > > > > > see if it's regression on the kernel side.
> > > > > > >
> > > > > >
> > > > > > And the CPUs are different: Cavium for good and Loongson3A3000 is
> > > > > > bad.
> > > > > >
> > > > >
> > > > > On
> > > > > https://buildd.debian.org/status/logs.php?pkg=golang-github-sylabs-sif&ver=1.0.9-2%2Bb2&arch=mips64el
> > > > >
> > > > > The failed buildd are: mipsel-manda-04, succeeded one are
> > > > > mipsel-aql-01.
> > > > > From the build log,
> > > > >
> > > > > mipsel-manda-04: Kernel: Linux 5.10.0-0.bpo.3-loongson-3
> > > > > mipsel-aql-01: Kernel: Linux 4.19.0-16-loongson-3
> > > > >
> > > >
> > > > Ohh, my mistake: mips-aql-01 vs mipsel-aql-01 ;)
> > > >
> > >
> > > WIth some test.
> > >
> > > This problem is also about O32_FP64 support option.
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962485
> > >
> > > It is quite strange this option may effect mips64el.
> > > Anyway, lets revert it.
> > >
> > > I will continue to dig the real problem.
> > >
> >
> > E, the problem is about Loongson 3A 1000 vs Loongson 3A2000/3000.
> > I test it on
> >
> > 3B1500 + O32_FP64-> workable
> > 3B1500 + nO32_FP64-> workable
> > 3A2000 + O32_FP64-> fail
> > 3A2000 + nO32_FP64-> fail
> >
>
> Sorry, it is not about O32_FP64, it is about memory region.
> Loongson 3A2000+ supports RI/XI, which stop the access of some memory region.
>
> The problem is about Go itself: why it map the datafile writeonly.
>2
I figure out a patch, with which it can build now:
--- golang-github-sylabs-sif-1.0.9/pkg/sif/load.go 2019-12-19
19:58:23.0 +
+++ golang-github-sylabs-sif-1.0.9-patched/pkg/sif/load.go
2021-03-29 09:49:44.789742245 +
@@ -92,7 +92,8 @@
flags := syscall.MAP_PRIVATE
if !rdonly {
- prot = syscall.PROT_WRITE
+ prot = syscall.PROT_WRITE | syscall.PROT_READ
+ // prot = syscall.PROT_WRITE
flags = syscall.MAP_SHARED
}
mmap(2) says that
On some hardware architectures (e.g., i386), PROT_WRITE implies
PROT_READ. It is architecture dependent whether PROT_READ
implies PROT_EXEC or not. Portable programs should always set
PROT_EXEC if they intend to execute code in the new mapping.
So, I guess it is due to architecture differences.
> > >
> > > > > It doesn't seem to have Cavium CPU here.
> > > > >
> > > >
> > > >
> > > > --
> > > > YunQiang Su
> > >
> > >
> > >
> > > --
> > > YunQiang Su
> >
> >
> >
> > --
> > YunQiang Su
>
>
>
> --
> YunQiang Su
--
YunQiang Su
Bug#986124: linux-image-4.19.0-16-amd64: Version 4.19.0-16 breaks lirc and vdr
Package: src:linux Version: 4.19.181-1 Severity: important Upgraded to latest packages and with Kernel 4.19.0-16 lirc stopped working. It cannot find /sys/class/rc and fills every second syslog: Mar 30 00:09:45 supply lircd[296]: lircd-0.10.1[296]: Error: No /sys/class/rc/ devices found Mar 30 00:09:45 supply lircd-0.10.1[296]: Error: No /sys/class/rc/ devices found Booting into 4.19.0-14, lirc work as expected. Breaking of lirc presumably affects vdr (vdr_2.4.1-4~etobi2_amd64.deb / packages.e-tobi.net vdr-experimental buster) as well. Vdr is working as expected on 4.19.0-14 kernel. root@iris:~# cat /etc/lirc/lircd.conf.d/devinput.lircd.conf # Rename to devinput.lircd.dist if not using devinput driver # Re-generate for current kernel using lirc-make-devinput # # Generated by lirc-make-devinput on 4.19.0-14-amd64 # Date: Sun Mar 21 14:29:15 UTC 2021 begin remote namedevinput-64 bits16 eps 30 aeps100 pre_data_bits 16 pre_data0x0001 post_data_bits 32 post_data 0x0001 gap 132799 toggle_bit 0 driver devinput begin codes [...] -- Package-specific info: ** Version: Linux version 4.19.0-16-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.181-1 (2021-03-19) ** Command line: root=/dev/xvda1 ro module.sig_enforce=1 quiet ** Not tainted ** Kernel log: [0.767391] PTP clock support registered [0.767398] EDAC MC: Ver: 3.0.0 [0.767559] PCI: System does not support PCI [0.768390] clocksource: Switched to clocksource xen [0.780534] VFS: Disk quotas dquot_6.6.0 [0.780554] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.780586] hugetlbfs: disabling because there are no supported hugepage sizes [0.780674] AppArmor: AppArmor Filesystem Enabled [0.780693] pnp: PnP ACPI: disabled [0.782345] NET: Registered protocol family 2 [0.782528] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes) [0.782541] TCP established hash table entries: 4096 (order: 3, 32768 bytes) [0.782588] TCP bind hash table entries: 4096 (order: 4, 65536 bytes) [0.782607] TCP: Hash tables configured (established 4096 bind 4096) [0.782647] UDP hash table entries: 256 (order: 1, 8192 bytes) [0.782653] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [0.782703] NET: Registered protocol family 1 [0.782709] NET: Registered protocol family 44 [0.782712] PCI: CLS 0 bytes, default 64 [0.782759] Unpacking initramfs... [0.877237] Freeing initrd memory: 87484K [0.878003] Initialise system trusted keyrings [0.878018] Key type blacklist registered [0.878090] workingset: timestamp_bits=40 max_order=17 bucket_order=0 [0.879648] zbud: loaded [1.129067] Key type asymmetric registered [1.129069] Asymmetric key parser 'x509' registered [1.129090] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247) [1.129123] io scheduler noop registered [1.129124] io scheduler deadline registered [1.129177] io scheduler cfq registered (default) [1.129178] io scheduler mq-deadline registered [1.129305] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [1.129663] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [1.130027] Linux agpgart interface v0.103 [1.130054] AMD IOMMUv2 driver by Joerg Roedel [1.130054] AMD IOMMUv2 functionality not available on this system [1.130163] i8042: PNP: No PS/2 controller found. [1.130163] i8042: Probing ports directly. [1.130984] i8042: No controller found [1.131038] mousedev: PS/2 mouse device common for all mice [1.131089] ledtrig-cpu: registered to indicate activity on CPUs [1.131384] NET: Registered protocol family 10 [1.148036] Segment Routing with IPv6 [1.148070] mip6: Mobile IPv6 [1.148074] NET: Registered protocol family 17 [1.148109] mpls_gso: MPLS GSO support [1.148205] mce: Using 2 MCE banks [1.148228] sched_clock: Marking stable (1147023133, 187741)->(1150917806, -3706932) [1.148522] registered taskstats version 1 [1.148523] Loading compiled-in X.509 certificates [1.205521] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [1.205539] Loaded X.509 cert 'Debian Secure Boot Signer 2021 - linux: 4b6ef5abca669825178e052c84667ccbc0531f8c' [1.205565] zswap: loaded using pool lzo/zbud [1.205694] AppArmor: AppArmor sha1 policy hashing enabled [1.205913] xenbus_probe_frontend: Device with no driver: device/vbd/51713 [1.205914] xenbus_probe_frontend: Device with no driver: device/vbd/51714 [1.205914] xenbus_probe_frontend: Device with no driver: device/vif/0 [1.205939] hctosys: unable to open rtc device (rtc0) [1.207650] Freeing unused kernel image memory:
Bug#985615: marked as done (4.19.0-14-amd64: USB keyboard no longer reliably works, requires restart)
Your message dated Mon, 29 Mar 2021 16:33:27 +0200 with message-id <3050723.YLpZsEB5ZX@bagend> and subject line Re: Bug#985615: Updating metadata has caused the Debian Bug report #985615, regarding 4.19.0-14-amd64: USB keyboard no longer reliably works, requires restart to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel Version: 4.19.0-14-amd64 Bug Description: My keyboard not work once in three when my machine starts => I have to restart it until my USB keyboard is finally recognized and I can enter my password to connect to my workstation ;-( Best regards. Philippe--- End Message --- --- Begin Message --- Version: 4.19.181-1 Apparently my updates opened it again, so close it (again) with a version.--- End Message ---
Bug#985615: Updating metadata
Control: retitle -1 4.19.0-14-amd64: USB keyboard no longer reliably works, requires restart
Processed: Re: Bug#985615: Updating metadata
Processing control commands: > retitle -1 4.19.0-14-amd64: USB keyboard no longer reliably works, requires > restart Bug #985615 [src:linux] Debian 10 Buster - kernel version 4.19.0-14-amd64 Changed Bug title to '4.19.0-14-amd64: USB keyboard no longer reliably works, requires restart' from 'Debian 10 Buster - kernel version 4.19.0-14-amd64'. -- 985615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#985615: Updating metadata
Processing control commands:
> found -1 4.19.171-2
Bug #985615 {Done: "pham...@bluewin.ch" } [src:linux]
Debian 10 Buster - kernel version 4.19.0-14-amd64
Marked as found in versions linux/4.19.171-2 and reopened.
> fixed -1 4.19.181-1
Bug #985615 [src:linux] Debian 10 Buster - kernel version 4.19.0-14-amd64
Marked as fixed in versions linux/4.19.181-1.
--
985615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#985615: Updating metadata
Control: found -1 4.19.171-2 Control: fixed -1 4.19.181-1
Processed: RPi4B 5GHz WiFi problems #985632 & #981616 completely went away by replacing brcmfmac43455-sdio.bin and brcmfmac43455-sdio.clm_blob
Processing control commands: > reassign 981616 firmware-brcm80211 20201218-3 Bug #981616 [firmware-brcm80211] 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display Ignoring request to reassign bug #981616 to the same package Bug #981616 [firmware-brcm80211] 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display Ignoring request to alter found versions of bug #981616 to the same values previously set -- 981616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981616 985632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RPi4B 5GHz WiFi problems #985632 & #981616 completely went away by replacing brcmfmac43455-sdio.bin and brcmfmac43455-sdio.clm_blob
Processing control commands: > reassign 981616 firmware-brcm80211 20201218-3 Bug #981616 [src:linux] 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display Bug reassigned from package 'src:linux' to 'firmware-brcm80211'. No longer marked as found in versions linux/5.10.24-1 and linux/5.10.12-1. Ignoring request to alter fixed versions of bug #981616 to the same values previously set Bug #981616 [firmware-brcm80211] 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display Marked as found in versions firmware-nonfree/20201218-3. -- 981616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981616: RPi4B 5GHz WiFi problems #985632 & #981616 completely went away by replacing brcmfmac43455-sdio.bin and brcmfmac43455-sdio.clm_blob
Control: reassign 981616 firmware-brcm80211 20201218-3 Hi, two RPi4B 5GHz WiFi problems #985632 firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine and #981616 5GHz WiFi does not work with vc4.ko on RPi4 and 4K display completely went away by replacing /lib/firmware/brcm/brcmfmac43455-sdio.bin and /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob by the files at https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm Commit messages at https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm are interesting: Use BCM43456 clm_blob on CYW43455 The previous CYW43455 clm_blob provides limited access to the higher 5GHz channels (100+) - the BCM43456 (surprisingly) seems to work and doesn't have this problem. Huh Update CYW43455 firmware This release fixes the error: Firmware trap: type 0x4 @ epc 0x0007a094 The full version string is: Version 7.45.229 (617f1f5 CY) CRC: 253bd863 Date: Mon 2021-01-04 19:58:58 PST Ucode Ver: 1043.2160 FWID 01-2dbd9d2e See: raspberrypi/linux#3849 Best regards, Ryutaroh Matsumoto
Bug#985615: marked as done (Debian 10 Buster - kernel version 4.19.0-14-amd64)
Your message dated Mon, 29 Mar 2021 14:06:44 +0200 (CEST) with message-id <1134194987.23499.1617019604...@bluewin.ch> and subject line Bug solved with a kernel version 4.19.0-16-amd64 has caused the Debian Bug report #985615, regarding Debian 10 Buster - kernel version 4.19.0-14-amd64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 985615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kernel Version: 4.19.0-14-amd64 Bug Description: My keyboard not work once in three when my machine starts => I have to restart it until my USB keyboard is finally recognized and I can enter my password to connect to my workstation ;-( Best regards. Philippe--- End Message --- --- Begin Message --- Bug solved with a kernel version 4.19.0-16-amd64 Regards. Philippe--- End Message ---
Bug#962485: Bug#983583: FTBFS on mips64el and mipsel
YunQiang Su 于2021年3月29日周一 下午1:31写道： > > YunQiang Su 于2021年3月29日周一 下午1:06写道： > > > > YunQiang Su 于2021年3月29日周一 上午11:45写道： > > > > > > Shengjing Zhu 于2021年3月29日周一 上午11:40写道： > > > > > > > > On Mon, Mar 29, 2021 at 09:22:29AM +0800, YunQiang Su wrote: > > > > > Shengjing Zhu 于2021年3月28日周日 上午12:12写道： > > > > > > > > > > > > Control: reopen -1 > > > > > > Control: severity -1 important > > > > > > > > > > > > On Sat, Mar 27, 2021 at 11:46 PM Adrian Bunk > > > > > > wrote: > > > > > > > > > > > > > > On Sat, Feb 27, 2021 at 02:33:38AM +0800, Shengjing Zhu wrote: > > > > > > > > Source: golang-github-sylabs-sif > > > > > > > > Version: 1.0.9-2 > > > > > > > > Severity: serious > > > > > > > > X-Debbugs-Cc: z...@debian.org > > > > > > > > > > > > > > > > Tried 3 times on buildd and failed at same test. > > > > > > > > > > > > > > > > === RUN TestAddDelObject > > > > > > > > unexpected fault address 0xffc8a0c000 > > > > > > > > fatal error: fault > > > > > > > > [signal SIGSEGV: segmentation violation code=0x2 > > > > > > > > addr=0xffc8a0c000 pc=0x12007ebe4] > > > > > > > > > > > > > > > > goroutine 22 [running]: > > > > > > > > runtime.throw(0x1201b74ed, 0x5) > > > > > > > > /usr/lib/go-1.15/src/runtime/panic.go:1116 +0x6c > > > > > > > > fp=0xce3430 sp=0xce3408 pc=0x120040afc > > > > > > > > runtime.sigpanic() > > > > > > > > > > > > > > > > Since it has been built on mipsx before, the failure will cause > > > > > > > > it impossible > > > > > > > > to fix issue later on these arch. > > > > > > > > > > > > > > > > It should either be removed from these arch or get fixed. > > > > > > > > > > > > > > This appears to be fixed now: > > > > > > > https://buildd.debian.org/status/package.php?p=golang-github-sylabs-sif > > > > > > > > > > > > The difference between these builds, seems to be a 5.10 kernel and > > > > > > 4.19 kernel on buildd. > > > > > > > > > > > > I'll reopen this but downgrade the severity, and loop debian-mips@ > > > > > > to > > > > > > see if it's regression on the kernel side. > > > > > > > > > > > > > > > > And the CPUs are different: Cavium for good and Loongson3A3000 is bad. > > > > > > > > > > > > > On > > > > https://buildd.debian.org/status/logs.php?pkg=golang-github-sylabs-sif&ver=1.0.9-2%2Bb2&arch=mips64el > > > > > > > > The failed buildd are: mipsel-manda-04, succeeded one are mipsel-aql-01. > > > > From the build log, > > > > > > > > mipsel-manda-04: Kernel: Linux 5.10.0-0.bpo.3-loongson-3 > > > > mipsel-aql-01: Kernel: Linux 4.19.0-16-loongson-3 > > > > > > > > > > Ohh, my mistake: mips-aql-01 vs mipsel-aql-01 ;) > > > > > > > WIth some test. > > > > This problem is also about O32_FP64 support option. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962485 > > > > It is quite strange this option may effect mips64el. > > Anyway, lets revert it. > > > > I will continue to dig the real problem. > > > > E, the problem is about Loongson 3A 1000 vs Loongson 3A2000/3000. > I test it on > > 3B1500 + O32_FP64-> workable > 3B1500 + nO32_FP64-> workable > 3A2000 + O32_FP64-> fail > 3A2000 + nO32_FP64-> fail > Sorry, it is not about O32_FP64, it is about memory region. Loongson 3A2000+ supports RI/XI, which stop the access of some memory region. The problem is about Go itself: why it map the datafile writeonly. > > > > > > It doesn't seem to have Cavium CPU here. > > > > > > > > > > > > > -- > > > YunQiang Su > > > > > > > > -- > > YunQiang Su > > > > -- > YunQiang Su -- YunQiang Su
