Bug#930904: closed by Salvatore Bonaccorso (Bug#930904: fixed in linux 4.9.184-1)
Hi Julien, On Wed, Jul 17, 2019 at 06:31:15AM +0200, Julien Aubin wrote: > Hi, > > Sadly the bug is still there for Buster. Could you re-open it please ? That should actually not be done. The Debian BTS has the version tracking in place, so for 4.19.37-5 it is still marked as unfixed even if the bug status is done trigered by this acceptance into stretch-proposed-updates by the 4.9.184-1 version. A bug can be closed in multiple versions with the Debian BTS version tracking. Then once the sid and buster upload is done, the bug will be marked as fixed automatically as well for those versions. Regards, Salvatore
Bug#930904: closed by Salvatore Bonaccorso (Bug#930904: fixed in linux 4.9.184-1)
Hi, Sadly the bug is still there for Buster. Could you re-open it please ? Le mar. 16 juil. 2019 à 23:09, Debian Bug Tracking System a écrit : > > This is an automatic notification regarding your Bug report > which was filed against the src:linux package: > > #930904: linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break > Steam (link to fix included) > > It has been closed by Salvatore Bonaccorso . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Salvatore Bonaccorso > by > replying to this email. > > > -- > 930904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930904 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Salvatore Bonaccorso > To: 930904-cl...@bugs.debian.org > Cc: > Bcc: > Date: Tue, 16 Jul 2019 21:07:58 + > Subject: Bug#930904: fixed in linux 4.9.184-1 > Source: linux > Source-Version: 4.9.184-1 > > We believe that the bug you reported is fixed in the latest version of > linux, which is due to be installed in the Debian FTP archive. > > A summary of the changes between this version and the previous one is > attached. > > Thank you for reporting the bug, which will now be closed. If you > have further comments please address them to 930...@bugs.debian.org, > and the maintainer will reopen the bug report if appropriate. > > Debian distribution maintenance software > pp. > Salvatore Bonaccorso (supplier of updated linux package) > > (This message was generated automatically at their request; if you > believe that there is a problem with it please contact the archive > administrators by mailing ftpmas...@ftp-master.debian.org) > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Sat, 29 Jun 2019 09:29:10 +0200 > Binary: linux-doc-4.9 linux-headers-4.9.0-10-common > linux-headers-4.9.0-10-common-rt linux-manual-4.9 linux-source-4.9 > linux-support-4.9.0-10 > Source: linux > Architecture: all source > Version: 4.9.184-1 > Distribution: stretch > Urgency: medium > Maintainer: Debian Kernel Team > Changed-By: Salvatore Bonaccorso > Closes: 866122 930904 > Description: > linux-doc-4.9 - Linux kernel specific documentation for version 4.9 > linux-headers-4.9.0-10-common - Common header files for Linux 4.9.0-10 > linux-headers-4.9.0-10-common-rt - Common header files for Linux 4.9.0-10-rt > linux-manual-4.9 - Linux kernel API manual pages for version 4.9 > linux-source-4.9 - Linux kernel source for version 4.9 with Debian patches > linux-support-4.9.0-10 - Support files for Linux 4.9 > Changes: > linux (4.9.184-1) stretch; urgency=medium > . >* New upstream stable update: > https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.169 > - [x86] power: Fix some ordering bugs in __restore_processor_context() > - [amd64] power/64: Use struct desc_ptr for the IDT in struct > saved_context > - [i386] power/32: Move SYSENTER MSR restoration to > fix_processor_context() > - [x86] power: Make restore_processor_context() sane > - [ppc64el] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM > - [ppc64el] Fix invalid use of register expressions > - [ppc64el] powerpc/64s: Add barrier_nospec > - [ppc64el] powerpc/64s: Add support for ori barrier_nospec patching > - [ppc64el] Avoid code patching freed init sections > - [ppc64el] powerpc/64s: Patch barrier_nospec in modules > - [ppc64el] powerpc/64s: Enable barrier_nospec based on firmware settings > - [ppc64el] Use barrier_nospec in copy_from_user() > - [ppc64el] powerpc/64: Use barrier_nospec in syscall entry > - [ppc64el] powerpc/64s: Enhance the information in cpu_show_spectre_v1() > - [ppc64el] powerpc64s: Show ori31 availability in spectre_v1 sysfs file >not v2 > - [ppc64el] powerpc/64: Disable the speculation barrier from the command >line > - [ppc64el] powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. > - [ppc64el] powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC > - [ppc64el] powerpc/64: Call setup_barrier_nospec() from setup_arch() > - [ppc64el] powerpc/64: Make meltdown reporting Book3S 64 specific > - [ppc64el] asm: Add a patch_site macro & helpers for patching >instructions > - [ppc64el] powerpc/64s: Add new security feature flags for count cache >flush > - [ppc64el] powerpc/64s: Add support for software count cache flush > - [ppc64el] powerpc/pseries: Query hypervisor for count cache flush >settings > - [ppc64el] powerpc/powernv: Query firmware for count cache flush >settings > - [ppc64el] security: Fix spectre_v2 reporting > - [arm64] kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region > - tty: ldisc: add sysctl to prevent autoloading of ldiscs >
Processed: Re: Bug#931584: Solution
Processing commands for cont...@bugs.debian.org: > reassign 931584 src:linux Bug #931584 [steam] Steam failed to connect to servers - Buster Bug #931588 [steam] Steam failed to connect to servers - Buster Bug reassigned from package 'steam' to 'src:linux'. Bug reassigned from package 'steam' to 'src:linux'. No longer marked as found in versions steam/1.0.0.59-4. No longer marked as found in versions steam/1.0.0.59-4. Ignoring request to alter fixed versions of bug #931584 to the same values previously set Ignoring request to alter fixed versions of bug #931588 to the same values previously set > found 931584 4.19.37-4 Bug #931584 [src:linux] Steam failed to connect to servers - Buster Bug #931588 [src:linux] Steam failed to connect to servers - Buster Marked as found in versions linux/4.19.37-4. Marked as found in versions linux/4.19.37-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 931584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931584 931588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932250: linux-image-amd64: adding segfault data
Package: linux-image-amd64 Version: 4.19+105 Followup-For: Bug #932250 adding file with segfault data -- System Information: APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-amd64 depends on: ii linux-image-4.19.0-5-amd64 4.19.37-5 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information xfdesktop[11344]: segfault at 16 ip 7ff9fd0f29ea sp 7b934f00 error 4 in libglib-2.0.so.0.5800.3[7ff9fd0a2000+7e000] 2019-07-17T01:04:04.589422+02:00 debian kernel: [18604.040877] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89 xfdesktop[16727]: segfault at 16 ip 7fe22e9aa9ea sp 7ffd313bc000 error 4 in libglib-2.0.so.0.5800.3[7fe22e95a000+7e000] 2019-07-17T01:04:07.231175+02:00 debian kernel: [18606.685725] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89 gmain[16752]: segfault at 17 ip 7fdada99a9ea sp 7fdad7f7c7c0 error 4 in libglib-2.0.so.0.5800.3[7fdada94a000+7e000] 2019-07-17T01:04:21.214468+02:00 debian kernel: [18620.669154] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89 gmain[16974]: segfault at 1c ip 7f3b5dcc29ea sp 7f3b5b2a45f0 error 4 in libglib-2.0.so.0.5800.3[7f3b5dc72000+7e000] 2019-07-17T01:05:28.070894+02:00 debian kernel: [18687.524814] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89
Bug#932250: linux-image-amd64: random segfaults without taking something down
Package: linux-image-amd64 Version: 4.19+105 Severity: important Hi. Im currently running debian buster kernel and i experienced some segfaults. Segfaults are random, which prevents me from pinpointing the trigger. First i tried disabling overcommit on memory, the behavior stoped. Today it started during installing updates for libreoffice. Two first segfaults were caused by xfdesktop, the two more with gmain. Another odd thing is that the error is in libglib and the code is completly identical. The RAM was tested with memtest86+, memtester. Previous release with backport kernel was working perfectly even with overcommit. I guess there is a small chance of defective hw. My next suspect is apparmor. Im going to use the system with disabled apparmor to see if this problem persist. Thank you I hope this helps make debian more stable and reliable. Have a nice day -- System Information: APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-amd64 depends on: ii linux-image-4.19.0-5-amd64 4.19.37-5 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information
Processed: severity of 932162 is important
Processing commands for cont...@bugs.debian.org: > severity 932162 important Bug #932162 [src:linux] linux-image-4.19.0-5-amd64: Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 932162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
linux_4.9.184-1_allonly.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2019 09:29:10 +0200 Binary: linux-doc-4.9 linux-headers-4.9.0-10-common linux-headers-4.9.0-10-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-10 Source: linux Architecture: all source Version: 4.9.184-1 Distribution: stretch Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 866122 930904 Description: linux-doc-4.9 - Linux kernel specific documentation for version 4.9 linux-headers-4.9.0-10-common - Common header files for Linux 4.9.0-10 linux-headers-4.9.0-10-common-rt - Common header files for Linux 4.9.0-10-rt linux-manual-4.9 - Linux kernel API manual pages for version 4.9 linux-source-4.9 - Linux kernel source for version 4.9 with Debian patches linux-support-4.9.0-10 - Support files for Linux 4.9 Changes: linux (4.9.184-1) stretch; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.169 - [x86] power: Fix some ordering bugs in __restore_processor_context() - [amd64] power/64: Use struct desc_ptr for the IDT in struct saved_context - [i386] power/32: Move SYSENTER MSR restoration to fix_processor_context() - [x86] power: Make restore_processor_context() sane - [ppc64el] powerpc/tm: Limit TM code inside PPC_TRANSACTIONAL_MEM - [ppc64el] Fix invalid use of register expressions - [ppc64el] powerpc/64s: Add barrier_nospec - [ppc64el] powerpc/64s: Add support for ori barrier_nospec patching - [ppc64el] Avoid code patching freed init sections - [ppc64el] powerpc/64s: Patch barrier_nospec in modules - [ppc64el] powerpc/64s: Enable barrier_nospec based on firmware settings - [ppc64el] Use barrier_nospec in copy_from_user() - [ppc64el] powerpc/64: Use barrier_nospec in syscall entry - [ppc64el] powerpc/64s: Enhance the information in cpu_show_spectre_v1() - [ppc64el] powerpc64s: Show ori31 availability in spectre_v1 sysfs file not v2 - [ppc64el] powerpc/64: Disable the speculation barrier from the command line - [ppc64el] powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. - [ppc64el] powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC - [ppc64el] powerpc/64: Call setup_barrier_nospec() from setup_arch() - [ppc64el] powerpc/64: Make meltdown reporting Book3S 64 specific - [ppc64el] asm: Add a patch_site macro & helpers for patching instructions - [ppc64el] powerpc/64s: Add new security feature flags for count cache flush - [ppc64el] powerpc/64s: Add support for software count cache flush - [ppc64el] powerpc/pseries: Query hypervisor for count cache flush settings - [ppc64el] powerpc/powernv: Query firmware for count cache flush settings - [ppc64el] security: Fix spectre_v2 reporting - [arm64] kaslr: Reserve size of ARM64_MEMSTART_ALIGN in linear region - tty: ldisc: add sysctl to prevent autoloading of ldiscs - ipv6: Fix dangling pointer when ipv6 fragment - ipv6: sit: reset ip header pointer in ipip6_rcv - openvswitch: fix flow actions reallocation - qmi_wwan: add Olicard 600 - sctp: initialize _pad of sockaddr_in before copying to user memory - tcp: Ensure DCTCP reacts to losses - vrf: check accept_source_route on the original netdevice - bnxt_en: Reset device on RX buffer errors. - bnxt_en: Improve RX consumer index validity check. - net/mlx5e: Add a lock on tir list - netns: provide pure entropy for net_hash_mix() - net: ethtool: not call vzalloc for zero sized memory request - ip6_tunnel: Match to ARPHRD_TUNNEL6 for dev type - ALSA: seq: Fix OOB-reads from strlcpy - Btrfs: do not allow trimming when a fs is mounted with the nologreplay option - block: do not leak memory in bio_copy_user_iov() - genirq: Respect IRQCHIP_SKIP_SET_WAKE in irq_chip_set_wake_parent() - virtio: Honour 'may_reduce_num' in vring_create_virtqueue - [arm64] futex: Fix FUTEX_WAKE_OP atomic ops with non-zero result value - [x86] xen: Prevent buffer overflow in privcmd ioctl - sched/fair: Do not re-read ->h_load_next during hierarchical load calculation - PCI: Add function 1 DMA alias quirk for Marvell 9170 SATA controller https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.170 - perf/core: Restore mmap record type correctly - ext4: add missing brelse() in add_new_gdb_meta_bg() - ext4: report real fs size after failed resize - [i386] ALSA: sb8: add a check for request_region - IB/mlx4: Fix race condition between catas error reset and aliasguid flows - [x86] thermal/int340x_thermal: Add additional UUIDs - [x86] thermal/int340x_thermal: fix mode setting - perf config: Fix an error in the config template documentation - perf config: Fix a memory leak in
Bug#866371: marked as done (FP register corruption on ppc64el with lock elision)
Your message dated Tue, 16 Jul 2019 21:07:58 + with message-id and subject line Bug#866122: fixed in linux 4.9.184-1 has caused the Debian Bug report #866122, regarding FP register corruption on ppc64el with lock elision 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.) -- 866122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openldap Version: 2.4.44+dfsg-6 Severity: serious https://buildd.debian.org/status/logs.php?pkg=openldap=ppc64el https://buildd.debian.org/status/logs.php?pkg=openldap=ppc64 ... > Starting test060-mt-hot for bdb... running defines.sh Running slapadd to build slapd database... Running slapindex to index slapd database... Starting slapd on TCP/IP port 9011... /<>/openldap-2.4.44+dfsg/debian/build/tests/../servers/slapd/slapd -s0 -f /<>/openldap-2.4.44+dfsg/debian/build/tests/testrun/slapd.1.conf -h ldap://localhost:9011/ -d stats Testing basic monitor search... Monitor searches Testing basic mt-hot search: 1 threads (1 x 5) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 1 -L 1 -l 5 Testing basic mt-hot search: 5 threads (1 x 1) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 5 -L 1 -l 1 Testing basic mt-hot search: 100 threads (5 x 100) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 100 -L 5 -l 100 Random searches Testing random mt-hot search: 1 threads (1 x 5) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -f (objectclass=*) -m 1 -L 1 -l 5 Testing random mt-hot search: 5 threads (1 x 1) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -f (objectclass=*) -m 5 -L 1 -l 1 slapd-mtread failed (139)! > test060-mt-hot failed for bdb (exit 139) Makefile:296: recipe for target 'bdb-mod' failed make[3]: *** [bdb-mod] Error 139 make[3]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build/tests' Makefile:282: recipe for target 'test' failed make[2]: *** [test] Error 2 make[2]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build/tests' Makefile:294: recipe for target 'test' failed make[1]: *** [test] Error 2 make[1]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build' dh_auto_test: make -j8 test VERBOSE=1 returned exit code 2 debian/rules:68: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.9.184-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2019 09:29:10 +0200 Binary: linux-doc-4.9 linux-headers-4.9.0-10-common linux-headers-4.9.0-10-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-10 Source: linux Architecture: all source Version: 4.9.184-1 Distribution: stretch Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 866122 930904 Description: linux-doc-4.9 - Linux kernel specific documentation for version 4.9 linux-headers-4.9.0-10-common - Common header files for Linux 4.9.0-10 linux-headers-4.9.0-10-common-rt - Common header files for Linux 4.9.0-10-rt linux-manual-4.9 - Linux kernel API manual pages for version 4.9 linux-source-4.9 - Linux kernel source for version 4.9 with Debian patches linux-support-4.9.0-10 - Support files for Linux 4.9 Changes: linux (4.9.184-1) stretch; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.169 - [x86] power: Fix some ordering bugs in __restore_processor_context() - [amd64] power/64: Use struct desc_ptr for
Bug#866122: marked as done (FP register corruption on ppc64el with lock elision)
Your message dated Tue, 16 Jul 2019 21:07:58 + with message-id and subject line Bug#866122: fixed in linux 4.9.184-1 has caused the Debian Bug report #866122, regarding FP register corruption on ppc64el with lock elision 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.) -- 866122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openldap Version: 2.4.44+dfsg-6 Severity: important test060-mt-hot for bdb failed twice in a row on the ppc64el buildd (ppc64el-osuosl-01), however a binary-only upload (presumably on a porterbox) built successfully. Starting test060-mt-hot for bdb... running defines.sh Running slapadd to build slapd database... Running slapindex to index slapd database... Starting slapd on TCP/IP port 9011... /<>/openldap-2.4.44+dfsg/debian/build/tests/../servers/slapd/slapd -s0 -f /<>/openldap-2.4.44+dfsg/debian/build/tests/testrun/slapd.1.conf -h ldap://localhost:9011/ -d stats Testing basic monitor search... Monitor searches Testing basic mt-hot search: 1 threads (1 x 5) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 1 -L 1 -l 5 Testing basic mt-hot search: 5 threads (1 x 1) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 5 -L 1 -l 1 Testing basic mt-hot search: 100 threads (5 x 100) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 100 -L 5 -l 100 Random searches Testing random mt-hot search: 1 threads (1 x 5) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -f (objectclass=*) -m 1 -L 1 -l 5 Testing random mt-hot search: 5 threads (1 x 1) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e dc=example,dc=com -f (objectclass=*) -m 5 -L 1 -l 1 slapd-mtread failed (139)! test060-mt-hot failed for bdb (exit 139) Makefile:296: recipe for target 'bdb-mod' failed make[3]: *** [bdb-mod] Error 139 make[3]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build/tests' Makefile:282: recipe for target 'test' failed make[2]: *** [test] Error 2 make[2]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build/tests' Makefile:294: recipe for target 'test' failed make[1]: *** [test] Error 2 make[1]: Leaving directory '/<>/openldap-2.4.44+dfsg/debian/build' dh_auto_test: make -j4 test VERBOSE=1 returned exit code 2 debian/rules:68: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.9.184-1 We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2019 09:29:10 +0200 Binary: linux-doc-4.9 linux-headers-4.9.0-10-common linux-headers-4.9.0-10-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-10 Source: linux Architecture: all source Version: 4.9.184-1 Distribution: stretch Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 866122 930904 Description: linux-doc-4.9 - Linux kernel specific documentation for version 4.9 linux-headers-4.9.0-10-common - Common header files for Linux 4.9.0-10 linux-headers-4.9.0-10-common-rt - Common header files for Linux 4.9.0-10-rt linux-manual-4.9 - Linux kernel API manual pages for version 4.9 linux-source-4.9 - Linux kernel source for version 4.9 with Debian patches linux-support-4.9.0-10 - Support files for Linux 4.9 Changes: linux (4.9.184-1) stretch; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.169 - [x86]
Bug#930904: marked as done (linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break Steam (link to fix included))
Your message dated Tue, 16 Jul 2019 21:07:58 + with message-id and subject line Bug#930904: fixed in linux 4.9.184-1 has caused the Debian Bug report #930904, regarding linux-image-4.19.0-5-amd64: Latest kernel upgrades on unstable break Steam (link to fix included) 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.) -- 930904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.37-5 Severity: important Dear Maintainer, Latest security fixes in the kernel (from 4.19.37-4 onwards) break some apps like at least Steam. The fix already exists as mentioned there : https://www.phoronix.com/scan.php?page=news_item=Steam-Linux-Network-One-Line A workaround exists for Steam but it may not be the case for other apps. Could you please backport the fix and re-release the kernel ? Thanks and regards -- Package-specific info: ** Version: Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-5 (2019-06-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=b762a3a5-b58c-46e5-9fbd-15927e33bdf9 ro apparmor=1 security=apparmor quiet ** Tainted: POE (12289) * Proprietary module has been loaded. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [24717.439314] cache: parent cpu1 should not be sleeping [24717.439513] CPU1 is up [24717.439534] smpboot: Booting Node 0 Processor 2 APIC 0x4 [24717.441249] cache: parent cpu2 should not be sleeping [24717.441460] CPU2 is up [24717.441479] smpboot: Booting Node 0 Processor 3 APIC 0x6 [24717.443255] cache: parent cpu3 should not be sleeping [24717.443486] CPU3 is up [24717.443505] smpboot: Booting Node 0 Processor 4 APIC 0x1 [24717.443993] cache: parent cpu4 should not be sleeping [24717.444307] CPU4 is up [24717.444326] smpboot: Booting Node 0 Processor 5 APIC 0x3 [24717.444743] cache: parent cpu5 should not be sleeping [24717.444944] CPU5 is up [24717.444960] smpboot: Booting Node 0 Processor 6 APIC 0x5 [24717.445376] cache: parent cpu6 should not be sleeping [24717.445594] CPU6 is up [24717.445609] smpboot: Booting Node 0 Processor 7 APIC 0x7 [24717.446037] cache: parent cpu7 should not be sleeping [24717.446817] CPU7 is up [24717.471699] ACPI: Waking up from system sleep state S3 [24717.472540] ACPI: EC: interrupt unblocked [24717.510729] ACPI: EC: event unblocked [24717.511197] sd 0:0:0:0: [sda] Starting disk [24717.511202] sd 1:0:0:0: [sdb] Starting disk [24717.511204] sd 2:0:0:0: [sdc] Starting disk [24717.511208] sd 4:0:0:0: [sdd] Starting disk [24717.512015] serial 00:06: activated [24717.638422] nvme nvme0: Shutdown timeout set to 8 seconds [24717.801991] usb 2-14: reset high-speed USB device number 11 using xhci_hcd [24717.888248] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [24717.888263] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [24717.888306] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [24717.889184] ata1.00: supports DRM functions and may not be fully accessible [24717.889484] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) [24717.889487] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) [24717.889942] ata1.00: supports DRM functions and may not be fully accessible [24717.890490] ata1.00: configured for UDMA/133 [24717.905182] ata4.00: configured for UDMA/100 [24717.929649] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) [24717.929652] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT5._GTF, AE_NOT_FOUND (20180810/psparse-516) [24717.929657] ata6.00: configured for UDMA/100 [24718.434026] usb 2-14.1: reset low-speed USB device number 12 using xhci_hcd [24718.990103] usb 2-14.2: reset low-speed USB device number 13 using xhci_hcd [24719.546162] usb 2-14.3: reset low-speed USB device number 14 using xhci_hcd [24719.847479] OOM killer enabled. [24719.847481] Restarting tasks ... [24719.847718] pci_bus :04: Allocating resources [24719.847749] pci :03:00.0: PCI bridge to [bus 04] [24719.847757] pci :03:00.0: bridge window [io 0x2000-0x2fff] [24719.847770] pci :03:00.0: bridge window [mem 0xd200-0xd21f] [24719.847779] pci :03:00.0: bridge window [mem 0xd220-0xd23f 64bit pref] [24719.870016] done. [24719.875143] PM: suspend exit [24720.535943] e1000e: eth0 NIC Link is Up 1000
Bug#931561: fix bug 931561
git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware mkdir /lib/firmware/mediatek/ cp mediatek/mt7610u.bin /lib/firmware/mediatek/ rmmod mt76x0 modprobe mt76x0 Adapter is working.
Bug#932162: Tested with GDM
Installed gdm3 and set it as default. Everything works and I can reach the Xfce desktop. Issue seems related to LightDM. Em ter, 16 de jul de 2019 09:21, Henry J. Douglas escreveu: > Booted with nomodeset i915.modeset=0 and here are the results. > > No display either. LightDM doesn't start, Xorg doesn't start. >
Processed: Re: Bug#929968: Add missing C_CAN module
Processing control commands: > tag -1 + pending Bug #929968 [src:linux] linux: Missing C_CAN module Added tag(s) pending. -- 929968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#929968: Add missing C_CAN module
Control: tag -1 + pending Hello, I merged your PR and added a changelog entry for it. Best regards Uwe signature.asc Description: PGP signature
Bug#932162: xorg logs with nomodeset
Booted with nomodeset i915.modeset=0 and here are the results. No display either. LightDM doesn't start, Xorg doesn't start. [30.131] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [30.131] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian [30.131] Current Operating System: Linux alq11 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 [30.131] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-amd64 root=/dev/mapper/alq11--vg-root ro quiet nomodeset i915.modeset=0 [30.131] Build Date: 05 March 2019 08:11:12PM [30.131] xorg-server 2:1.20.4-1 (https://www.debian.org/support) [30.131] Current version of pixman: 0.36.0 [30.131]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [30.131] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [30.131] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 16 09:12:39 2019 [30.132] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [30.132] (==) No Layout section. Using the first Screen section. [30.132] (==) No screen section available. Using defaults. [30.132] (**) |-->Screen "Default Screen Section" (0) [30.132] (**) | |-->Monitor "" [30.133] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [30.133] (==) Automatically adding devices [30.133] (==) Automatically enabling devices [30.133] (==) Automatically adding GPU devices [30.133] (==) Max clients allowed: 256, resource mask: 0x1f [30.133] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [30.133]Entry deleted from font path. [30.134] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [30.134] (==) ModulePath set to "/usr/lib/xorg/modules" [30.134] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [30.134] (II) Loader magic: 0x55b6a15a0e20 [30.134] (II) Module ABI versions: [30.134]X.Org ANSI C Emulation: 0.4 [30.134]X.Org Video Driver: 24.0 [30.134]X.Org XInput driver : 24.1 [30.134]X.Org Server Extension : 10.0 [30.136] (++) using VT number 7 [30.136] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [30.139] (--) PCI:*(0@0:2:0) 8086:22b1:1028:0725 rev 33, Mem @ 0x9000/16777216, 0x8000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [30.139] (II) LoadModule: "glx" [30.139] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [30.142] (II) Module glx: vendor="X.Org Foundation" [30.142]compiled for 1.20.4, module version = 1.0.0 [30.142]ABI class: X.Org Server Extension, version 10.0 [30.142] (==) Matched modesetting as autoconfigured driver 0 [30.142] (==) Matched fbdev as autoconfigured driver 1 [30.142] (==) Matched vesa as autoconfigured driver 2 [30.142] (==) Assigned the driver to the xf86ConfigLayout [30.142] (II) LoadModule: "modesetting" [30.142] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [30.142] (II) Module modesetting: vendor="X.Org Foundation" [30.142]compiled for 1.20.4, module version = 1.20.4 [30.142]Module class: X.Org Video Driver [30.142]ABI class: X.Org Video Driver, version 24.0 [30.142] (II) LoadModule: "fbdev" [30.143] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [30.143] (II) Module fbdev: vendor="X.Org Foundation" [30.143]compiled for 1.20.0, module version = 0.5.0 [30.143]Module class: X.Org Video Driver [30.143]ABI class: X.Org Video Driver, version 24.0 [30.143] (II) LoadModule: "vesa" [30.143] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [30.143] (II) Module vesa: vendor="X.Org Foundation" [30.143]compiled for 1.20.1, module version = 2.4.0 [30.143]Module class: X.Org Video Driver [30.143]ABI class: X.Org Video Driver, version 24.0 [30.143] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [30.144] (II) FBDEV: driver for framebuffer: fbdev [30.144] (II) VESA: driver for VESA chipsets: vesa [30.144] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) [30.144] (EE) open /dev/dri/card0: No such file or directory [30.144] (WW) Falling back to old probe method for modesetting [30.144] (EE) open /dev/dri/card0: No such file or directory [
Bug#931901: Ping to Ben Hutchings, identifying possible source of problem
On Tue, 16 Jul 2019 00:15:44 +0100 Ben Hutchings wrote: > I suspect that this bug is a duplicate of bug #928510, for which the > fix missed the buster release (but we can fix it in a point release). > If you run "update-initramfs -u" and reboot, does that fix the > problem? Ah, that does indeed resolve the matter. This was a strange one, to my eyes... but now I know what was really going on. I now have X and the 4.19 kernel at the same time. Many thanks for your efforts - hopefully I won't need to install on any similar machines before this is fixed properly but I will treat this as a "release note" if I do. -- Phil Reynolds mail: phil-deb2...@tinsleyviaduct.com
