linux-latest_105+deb10u5_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 09 Jul 2020 21:58:28 +0200 Source: linux-latest Architecture: source Version: 105+deb10u5 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-latest (105+deb10u5) buster; urgency=medium . * Update to 4.19.0-10 Checksums-Sha1: d5b07ce36257b5e1d27fb17bd25d21b0c707ae25 11739 linux-latest_105+deb10u5.dsc 77338ac41ac3df194078b765060c95ebc5175013 20420 linux-latest_105+deb10u5.tar.xz 14d349ea88b0d4d148e0c8de8a2f05406834d24d 6423 linux-latest_105+deb10u5_source.buildinfo Checksums-Sha256: 56e59171c362ce4b3511beacfac38cc36abe8f19c8e5015081fee78d3d045954 11739 linux-latest_105+deb10u5.dsc e38bfda88c1b8cfc07c652be3cd0f44f889498a7040f9247583e8cce348f867c 20420 linux-latest_105+deb10u5.tar.xz 1591e13808bc5db096304b79da70b700b2dc9df7bf904cdcce3e564dcaeb2a67 6423 linux-latest_105+deb10u5_source.buildinfo Files: 4d92d44e30814f2681290eb1106ffa02 11739 kernel optional linux-latest_105+deb10u5.dsc 4d2b61ce5a37df822264c0d68d8ef216 20420 kernel optional linux-latest_105+deb10u5.tar.xz 750e5e301c754e64456ef7e23b665218 6423 kernel optional linux-latest_105+deb10u5_source.buildinfo -BEGIN PGP SIGNATURE- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl8Hd2tfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89Ea3UP/jSeOHat099zHrT8b0uYQth/rVGE+ubA B5vUgwkeIF2XBYKZIr9jDeGgtQdlKHqxoJ0HthQyMbPITqBNeRJ5Q/RUbRCqUP1V rFxvDDyb5LmMa267c9OGmxdqgVxOb8yQTgS8g2e4K7lQN+CIi4hTWUuKFYV2hddB RXxhNH7LMwLKzsZIu2pflmeb51Tmtd3aNn/yhLQYcADJqfWaVmOjw2oD2Ckz5yEh lV8Ntvdxe3zEDDBu9lOtaLhjgbguY6Gqh7c4LX2ztXWw0RH/8EVp/Ra8UaSAFXzk OO96AA4o/fXoofUTGH7LYtdICswwdu4uMIr6xuDN4TtIAWzLSDJYy1oVQiIR7795 78YqhCjSfxaDz3xUT1DW5aLWkF5lOXb9T9Q2HyCl1DZ2e5XgSLZGWvevfAJ1FOHb RhDaycjpnxXbkXkdx4zoyJbqjK9S9+1K3WnPn//jPzWFWkjerFTp5skYJAf7ijao GasxBufsExfPpYpHEogiUrGKnP87FaLsVNBFaslxwS0dEqvwUk9Ff6ua1HIk2CVX 3qlzrpcUFzvHLQT6KNdec79TqO9eq7YYGODnA9CjCsbTZbdyTiIn2sBHsj0cm1z/ nEJH5/qSbI4lT5QGJABx2bfei+zBKh2t64FSzKwje1KOlrnSM72eRYyiwRJgPRNf dAWeRNyevh4a =wSvu -END PGP SIGNATURE- Thank you for your contribution to Debian.
linux_4.19.131-1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 09 Jul 2020 04:45:56 +0200
Source: linux
Architecture: source
Version: 4.19.131-1
Distribution: buster
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 958300 960493 962254 963493
Changes:
linux (4.19.131-1) buster; urgency=medium
.
* New upstream stable update:
https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.119
- ext4: fix extent_status fragmentation for plain files
- [arm64] drm/msm: Use the correct dma_sync calls harder
- vti4: removed duplicate log message.
- [arm64] Add part number for Neoverse N1
- [arm64] errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1
#1542419
- [arm64] Fake the IminLine size on systems affected by Neoverse-N1
#1542419
- [arm64] compat: Workaround Neoverse-N1 #1542419 for compat user-space
- watchdog: reset last_hw_keepalive time at start
- scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
- scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
- ceph: return ceph_mdsc_do_request() errors from __get_parent()
- ceph: don't skip updating wanted caps when cap is stale
- scsi: iscsi: Report unbind session event when the target has been
removed
- [x86] ASoC: Intel: atom: Take the drv->lock mutex before calling
sst_send_slot_map()
- nvme: fix deadlock caused by ANA update wrong locking
- ipc/util.c: sysvipc_find_ipc() should increase position index
- [s390x] cio: avoid duplicated 'ADD' uevents
- loop: Better discard support for block devices
- [powerpc*] Revert "powerpc/64: irq_work avoid interrupt when called with
hardware irqs enabled"
- [arm*] pwm: bcm2835: Dynamically allocate base
- perf/core: Disable page faults when getting phys address
- [x86] ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
- xhci: Ensure link state is U3 after setting USB_SS_PORT_LS_U3
- virtio-blk: improve virtqueue error to BLK_STS
- scsi: smartpqi: fix call trace in device discovery
- PCI/ASPM: Allow re-enabling Clock PM
- [x86] KVM: VMX: Zero out *all* general purpose registers after VM-Exit
- cxgb4: fix adapter crash due to wrong MC size
- cxgb4: fix large delays in PTP synchronization
- ipv6: fix restrict IPV6_ADDRFORM operation
- macsec: avoid to set wrong mtu
- macvlan: fix null dereference in macvlan_device_event()
- net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
- [arm64,armhf] net: stmmac: dwmac-meson8b: Add missing boundary to RGMII
TX clock array
- sched: etf: do not assume all sockets are full blown
- tcp: cache line align MAX_TCP_HEADER
- team: fix hang in team_mode_get()
- vrf: Fix IPv6 with qdisc and xfrm
- [armhf] net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled
- [armhf] net: dsa: b53: Fix ARL register definitions
- [armhf] net: dsa: b53: Rework ARL bin logic
- [armhf] net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL
- xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish
- vrf: Check skb for XFRM_TRANSFORMED flag
- KEYS: Avoid false positive ENOMEM error on key read
- ALSA: hda: Remove ASUS ROG Zenith from the blacklist
- ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos
- ALSA: usb-audio: Add connector notifier delegation
- [armhf] iio: st_sensors: rely on odr mask to know if odr can be set
- USB: sisusbvga: Change port variable from signed to unsigned
- USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair
K70 RGB RAPIDFIRE
- USB: early: Handle AMD's spec-compliant identifiers, too
- USB: hub: Fix handling of connect changes during sleep
- vmalloc: fix remap_vmalloc_range() bounds checks
- mm/hugetlb: fix a addressing exception caused by huge_pte_offset
- mm/ksm: fix NULL pointer dereference when KSM zero page is enabled
- ALSA: hda/realtek - Fix unexpected init_amp override
- ALSA: hda/realtek - Add new codec supported for ALC245
- ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif
- ALSA: usb-audio: Filter out unsupported sample rates on Focusrite
devices
- tpm/tpm_tis: Free IRQ if probing fails
- [s390x] KVM: Return last valid slot if approx index is out-of-bounds
- KVM: Check validity of resolved slot when searching memslots
- [x86] KVM: VMX: Enable machine check support for 32bit targets
- tty: hvc: fix buffer overflow during hvc_alloc().
- [x86] tty: rocket, avoid OOB access
- usb-storage: Add unusual_devs entry for JMicron JMS566
- audit: check the length of userspace generated audit records
- ASoC: dapm: fixup dapm kcontrol widget
- iwlwifi: pcie: actually release queue memory in TVQ
Bug#934160: marked as done (NFSv4.2: umask not applied on filesystem without ACL support)
Your message dated Fri, 10 Jul 2020 20:10:09 + with message-id and subject line Bug#962254: fixed in linux 4.19.131-1 has caused the Debian Bug report #962254, regarding NFSv4.2: umask not applied on filesystem without ACL support 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.) -- 962254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nfs-common Version: 1:1.3.4-2.5 Severity: grave Tags: security Justification: user security hole I have an NFS client and server both running Debian. I recently upgraded them both to buster. I discovered today that the regular process umask has been ignored on my nfs mounts since the upgrade, and all files and directories are being created a+rw. On the client, the fstab fstype is nfs4 and the mount options are hard,intr,bg,noatime. The relevant datasets are exported rw,no_root_squash,no_subtree_check from the server. In researching this, I stumbled across https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1779736 and https://bugzilla.redhat.com/show_bug.cgi?id=1667761 which indicate the problem is present elsewhere as well. Adding vers=4.1 to my client's mount options completely resolved the problem. (Though now I have a couple weeks' worth of files with unintentionally open permissions to wade through.) I tagged this as security and grave because it opens up quite a few scenarios for users to receive privileges they shouldn't, and for other potential mischief (placing malicious executables in world-writable directories, etc). The server is indeed running zfs with its default acltype setting (off). As the Ubuntu bug report shows, mounting with noacl doesn't resolve the behavior either. The RedHat bug occurred with an OpenWRT server, unlikely to be running zfs. I do not believe this bug should be pinned down to ZFS; a filesystem not supporting ACLs should not result in umask 0 for all clients in any scenario. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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) LSM: AppArmor: enabled Versions of packages nfs-common depends on: ii adduser 3.118 ii keyutils1.6-6 ii libc6 2.28-10 ii libcap2 1:2.25-2 ii libcom-err2 1.44.5-1 ii libdevmapper1.02.1 2:1.02.155-3 ii libevent-2.1-6 2.1.8-stable-4 ii libgssapi-krb5-21.17-3 ii libk5crypto31.17-3 ii libkeyutils11.6-6 ii libkrb5-3 1.17-3 ii libmount1 2.33.1-0.1 ii libnfsidmap20.25-5.1 ii libtirpc3 1.1.4-0.4 ii libwrap07.6.q-28 ii lsb-base10.2019051400 ii rpcbind 1.2.5-0.3 ii ucf 3.0038+nmu1 Versions of packages nfs-common recommends: ii python 2.7.16-1 Versions of packages nfs-common suggests: pn open-iscsi pn watchdog -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.131-1 Done: Salvatore Bonaccorso 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 962...@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 admini
Bug#963493: marked as done (Repeatable hard lockup running strace testsuite using 4.19.118+2+deb10u1, 4.19.98+1+deb10u1 works fine)
Your message dated Fri, 10 Jul 2020 20:10:09 + with message-id and subject line Bug#963493: fixed in linux 4.19.131-1 has caused the Debian Bug report #963493, regarding Repeatable hard lockup running strace testsuite using 4.19.118+2+deb10u1, 4.19.98+1+deb10u1 works fine 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.) -- 963493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.19.118-2+deb10u1 Severity: serious Hi folks, Trying to reproduce #963462 on my Thinkpad T470, I'm repeatedly getting a hard lockup running the strace testsuite. I've done this 4 times to be sure. Each time it seems to have failed in a slightly different place in the testsuite (suggesting it's not one particular syscall test that's triggering the failure). Only one of the 4 lockups left eny evidence in the logs (reproduced below), so I'm not sure if the error here is actually the root of the problem or not. :-/ The machine is not noticeably running hot or anything while doing these tests. Rebooting back to 4.19.0-8-amd64 (aka 4.9.98+1+deb10u1), I've just run the same testsuite twice in a row and it ran to completion with no lockup. Here's the one bit of log that I did get, in case it's useful. Jun 22 11:36:49 tack kernel: [ 318.195906] futex_wake_op: futex tries to shift op by -849; fix this program Jun 22 11:36:49 tack kernel: [ 318.195910] futex_wake_op: futex tries to shift op by -849; fix this program Jun 22 11:36:49 tack kernel: [ 318.195971] futex_wake_op: futex tries to shift op by -518; fix this program Jun 22 11:36:49 tack kernel: [ 318.195974] futex_wake_op: futex tries to shift op by -518; fix this program Jun 22 11:36:49 tack kernel: [ 318.195977] futex_wake_op: futex tries to shift op by -1; fix this program Jun 22 11:36:49 tack kernel: [ 318.195979] futex_wake_op: futex tries to shift op by -1; fix this program Jun 22 11:36:49 tack kernel: [ 318.199661] futex_wake_op: futex tries to shift op by -849; fix this program Jun 22 11:36:49 tack kernel: [ 318.199674] futex_wake_op: futex tries to shift op by -849; fix this program Jun 22 11:36:49 tack kernel: [ 318.199917] futex_wake_op: futex tries to shift op by -518; fix this program Jun 22 11:36:49 tack kernel: [ 318.199982] futex_wake_op: futex tries to shift op by -518; fix this program Jun 22 11:36:49 tack kernel: [ 318.398755] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-gui de/hw-vuln/l1tf.html for details. Jun 22 11:36:49 tack kernel: [ 318.587324] WARNING: CPU: 2 PID: 32174 at mm/page_alloc.c:4385 __alloc_pages_nodemask+0x241/0x2b0 Jun 22 11:36:49 tack kernel: [ 318.587326] Modules linked in: acpi_call(OE) ipt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo nft_counter nft_chain_nat_ipv4 nf_ nat_ipv4 xt_addrtype nft_compat xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp overlay devlink cpufreq_userspace cpufreq_conser vative cpufreq_powersave ipmi_devintf ipmi_msghandler nf_tables nfnetlink appletalk psnap llc ax25 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) cmac bnep fuse binfmt_misc pktcdvd snd_hda_codec_hdmi btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_hd a_codec_realtek snd_hda_codec_generic videodev media drbg ansi_cprng ecdh_generic nls_ascii nls_cp437 vfat fat arc4 intel_rapl snd_soc_skl msr snd_soc_skl_ipc snd_soc_ sst_ipc Jun 22 11:36:49 tack kernel: [ 318.587344] snd_soc_sst_dsp x86_pkg_temp_thermal intel_powerclamp snd_hda_ext_core coretemp snd_soc_acpi_intel_match iwlmvm snd_soc_ac pi kvm_intel snd_soc_core mac80211 snd_compress wmi_bmof i915 snd_hda_intel iwlwifi kvm snd_hda_codec snd_h da_core irqbypass snd_hwdep evdev intel_cstate joydev snd_pcm_oss drm_kms_helper intel_uncore serio_raw intel_rapl_perf mei_me snd_mixer_oss cfg80211 sg efi_pstore drm pcspkr mei efivars snd_pcm ucsi_acpi snd_timer typec_ucsi i2c_algo_bit iTCO_wdt iTCO_vendor_support intel_pch_thermal typec thinkpad_acpi tpm_crb wmi nvram snd soundcore tpm_tis rfkill video tpm_tis_core battery pcc_cpufreq ac tpm rng_core acpi_pad button parport_pc nfsd ppdev auth_rpcgss lp nfs_acl lockd grace sunrpc parport efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic Jun 22 11:36:49 tack kernel: [ 318.587362] fscrypto ecb btrfs zstd_decompress zstd_compress xxhash algif_skcipher af_alg sr_mod cdrom uas usb_stor
Bug#960493: marked as done (linux-image-4.19.0-9-amd64: Audio regression on HP Pavilion laptop)
Your message dated Fri, 10 Jul 2020 20:10:09 + with message-id and subject line Bug#960493: fixed in linux 4.19.131-1 has caused the Debian Bug report #960493, regarding linux-image-4.19.0-9-amd64: Audio regression on HP Pavilion laptop 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.) -- 960493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.118-2 Severity: important Tags: upstream Dear Maintainer, After installing linux-image-4.19-0-9-amd64 my desktop environment no longer detects the sound card (it reverts to the dummy output) and I get no sound. However "aplay -l" still lists it. I bisected the kernel and found 44cc74947ce02283e4967aa92988b90ec7c25dee is the first broken commit. It appears that 6cacf120de65f336d57bdfd41466b65ed1c569c6 is a follow up commit fixing the problem and indeed v4.19.121 works fine (the regression is fixed). Is it possible to update the package to a later stable release? Thanks, Steve -- Package-specific info: ** Version: Linux version 4.19.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.118-2 (2020-04-29) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-9-amd64 root=UUID=5ed03751-76e2-4d9d-af9f-2410a3a3c954 ro ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 17.224849] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 [ 17.240278] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 17.241418] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 17.242538] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 17.243718] pcieport :00:1c.5:[ 0] RxErr (First) [ 17.248463] iwlwifi :02:00.0: base HW address: dc:53:60:84:4b:30 [ 17.359573] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 17.360190] thermal thermal_zone5: failed to read out thermal zone (-61) [ 17.463309] iwlwifi :02:00.0 wlo1: renamed from wlan0 [ 18.909295] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=600 [ 19.207212] Adding 16447484k swap on /dev/sda5. Priority:-2 extents:1 across:16447484k FS [ 30.743104] ACPI BIOS Error (bug): \_SB.PCI0.RP09.PXSX._DSW: Insufficient arguments - ASL declared 1, ACPI requires 3 (20180810/nsarguments-156) [ 34.090553] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 34.131169] ACPI BIOS Error (bug): \_SB.PCI0.RP09.PXSX._DSW: Insufficient arguments - ASL declared 1, ACPI requires 3 (20180810/nsarguments-156) [ 34.289529] r8169 :03:00.0: firmware: direct-loading firmware rtl_nic/rtl8107e-2.fw [ 34.291136] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE) [ 34.398792] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 34.404294] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 34.418696] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 34.419807] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 34.420949] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 34.422088] pcieport :00:1c.5:[ 0] RxErr (First) [ 34.497221] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 34.498420] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 34.499713] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 34.500927] pcieport :00:1c.5:[ 0] RxErr (First) [ 34.510176] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready [ 34.538890] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 34.540265] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 34.541507] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 34.542741] pcieport :00:1c.5:[ 0] RxErr (First) [ 34.624603] pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 [ 34.626246] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 34.627763] pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 [ 34.629240] pcieport :00:1c.5:[ 0] RxErr
Bug#962254: marked as done (NFSv4.2: umask not applied on filesystem without ACL support)
Your message dated Fri, 10 Jul 2020 20:10:09 + with message-id and subject line Bug#962254: fixed in linux 4.19.131-1 has caused the Debian Bug report #962254, regarding NFSv4.2: umask not applied on filesystem without ACL support 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.) -- 962254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.118+2 Severity: important Somewhere between linux-image-4.19.0-8-amd64/4.19.98+1+deb10u1 and linux-image-4.19.0-9-amd64/4.19.118+2 NFS, in particular v4 got broken. Mounting an appropriate filesystem became unreliable, and once mounted behavior is unpredictable. In particular in the problematic case `umask 022 ; touch foo ; ls -l foo` yields a -rw-rw-rw- file. This occurs if *both* the server *and* client are on 4.19.118+2. I have confirmed this does NOT occur if the server is on a 4.9 kernel. I have also confirmed this does NOT occur if the client is on a 4.9 or 4.19.98+1+deb10u1 kernel. -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445 --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.131-1 Done: Salvatore Bonaccorso 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 962...@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: Thu, 09 Jul 2020 04:45:56 +0200 Source: linux Architecture: source Version: 4.19.131-1 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 958300 960493 962254 963493 Changes: linux (4.19.131-1) buster; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.119 - ext4: fix extent_status fragmentation for plain files - [arm64] drm/msm: Use the correct dma_sync calls harder - vti4: removed duplicate log message. - [arm64] Add part number for Neoverse N1 - [arm64] errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 - [arm64] Fake the IminLine size on systems affected by Neoverse-N1 #1542419 - [arm64] compat: Workaround Neoverse-N1 #1542419 for compat user-space - watchdog: reset last_hw_keepalive time at start - scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login - scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG - ceph: return ceph_mdsc_do_request() errors from __get_parent() - ceph: don't skip updating wanted caps when cap is stale - scsi: iscsi: Report unbind session event when the target has been removed - [x86] ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() - nvme: fix deadlock caused by ANA update wrong locking - ipc/util.c: sysvipc_find_ipc() should increase position index - [s390x] cio: avoid duplicated 'ADD' uevents - loop: Better discard support for block devices - [powerpc*] Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled" - [arm*] pwm: bcm2835: Dynamically allocate base - perf/core: Disable page faults when getting phys address - [x86] ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet - xhci: Ensure link state is U3 after setting USB_SS_PORT_LS_U3 - virtio-blk: improve virtqueue error to BLK_STS - scsi: smartpqi: fix call trace in device discovery - PCI/ASPM: Allow re-enabling Clock PM - [x86] KVM: VMX: Zero out *all* general purpose registers after VM-Exit - cxgb4: fix adapter crash due to wrong MC size - cxgb4: fix large delays in PTP synchronization - ipv6: fix restrict IPV6_
Re: Arch qualification for buster: call for DSA, Security, toolchain concerns
I don't know if this should be a blocker, but the MIPS builders are
still extremely slow for kernel builds. In the worst case (mipsel:
mipsel-aql-{01,02}) it takes about 41 hours, which is 3 times longer
than the next slowest group of builders (armhf: hasse, henze, holby).
This can be a problem for getting security updates out promptly.
Ben.
--
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.
signature.asc
Description: This is a digitally signed message part
Processed: severity of 964494 is serious
Processing commands for cont...@bugs.debian.org: > severity 964494 serious Bug #964494 [src:linux] File system corruption with ext3 + kernel-4.19.0-9-amd64 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 964494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964765: linux-image-5.7.0-1-amd64: booting to black screen on VMware, vmwgfx related
Package: src:linux Version: 5.7.6-1 Severity: important The system boots into a black screen on VMware workstation pro 15.5.6 and the GUI is unusable. The 5.6.0 kernel works. -- Package-specific info: ** Version: Linux version 5.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-14), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP Debian 5.7.6-1 (2020-06-24) ** Command line: BOOT_IMAGE=/vmlinuz-5.7.0-1-amd64 root=/dev/mapper/privatevmlinux--vg-root ro quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: [2.773724] systemd[1]: Condition check resulted in Kernel Configuration File System being skipped. [2.774752] systemd[1]: Starting Apply Kernel Variables... [2.786427] systemd[1]: Mounted FUSE Control File System. [2.787399] systemd[1]: Mounting VMware vmblock fuse mount... [2.792975] systemd[1]: Finished Apply Kernel Variables. [2.806552] systemd[1]: Mounted VMware vmblock fuse mount. [2.812030] systemd[1]: Finished Create Static Device Nodes in /dev. [2.813152] systemd[1]: Starting udev Kernel Device Manager... [2.818757] systemd[1]: Finished Set the console keyboard layout. [2.818960] systemd[1]: Reached target Local File Systems (Pre). [2.886359] systemd[1]: Started udev Kernel Device Manager. [2.952970] systemd[1]: Finished udev Coldplug all Devices. [2.955315] systemd[1]: Starting Helper to synchronize boot up for ifupdown... [2.957032] systemd[1]: Starting Show Plymouth Boot Screen... [2.977976] systemd[1]: Finished Helper to synchronize boot up for ifupdown. [2.986451] systemd[1]: Started Show Plymouth Boot Screen. [2.986672] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. [2.986804] systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. [2.986829] systemd[1]: Reached target Local Encrypted Volumes. [3.092844] ACPI: AC Adapter [ACAD] (on-line) [3.326535] systemd[1]: Started Journal Service. [3.335650] systemd-journald[254]: Received client request to flush runtime journal. [3.437227] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 [3.437285] vmw_vmci :00:07.7: Using capabilities 0xc [3.443082] Guest personality initialized and is active [3.443114] VMCI host device registered (name=vmci, major=10, minor=61) [3.443114] Initialized host personality [3.468629] sr 1:0:0:0: Attached scsi generic sg0 type 5 [3.468668] sd 2:0:0:0: Attached scsi generic sg1 type 0 [3.614815] input: PC Speaker as /devices/platform/pcspkr/input/input6 [3.701227] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [3.705578] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [3.705586] ext2 filesystem being mounted at /boot supports timestamps until 2038 (0x7fff) [3.760924] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer [3.826190] audit: type=1400 audit(1594370944.208:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default" pid=353 comm="apparmor_parser" [3.826193] audit: type=1400 audit(1594370944.208:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-cgns" pid=353 comm="apparmor_parser" [3.826194] audit: type=1400 audit(1594370944.208:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-with-mounting" pid=353 comm="apparmor_parser" [3.826196] audit: type=1400 audit(1594370944.208:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-with-nesting" pid=353 comm="apparmor_parser" [3.859505] audit: type=1400 audit(1594370944.244:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=358 comm="apparmor_parser" [3.945356] audit: type=1400 audit(1594370944.328:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=352 comm="apparmor_parser" [3.945358] audit: type=1400 audit(1594370944.328:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince//sanitized_helper" pid=352 comm="apparmor_parser" [3.945359] audit: type=1400 audit(1594370944.328:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=352 comm="apparmor_parser" [3.945360] audit: type=1400 audit(1594370944.328:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer//sanitized_helper" pid=352 comm="apparmor_parser" [3.957946] Adding 524284k swap on /dev/mapper/privatevmlinux--vg-swap_1. Priority:-2 extents:1 across:524284k FS [4.055802] cryptd: max_cpu_qlen set to 1000 [4.083176] AVX2 version of gcm_enc/dec engaged. [4.083177] AES CTR mode by8 optimization enabled [4.16272
Bug#964781: xhci "ERROR Transfer event TRB DMA ptr not part of current TD" on Dell WD19TB thunderbolt dock
Package: src:linux
Version: 5.7.6-1
Severity: normal
I have a Dell XPS 15 9500 connected to a Dell WD19TB thunderbolt dock
and various periphery connected through the dock, namely:
* USB keyboard
* USB mouse
* HDMI display
* ethernet (according to lsusb also a USB device)
* USB headset
Sometimes all USB devices (keyboard, mouse, ethernet and headset)
connected to the dock get disconnected while the HDMI output continues
to work fine.
I haven't been able to figure out what the exact condition are, under
which this problems occurs. However, I can often reproduce the issue
by playing music from youtube through a headset connected to the
dock. Using a local sound source doesn't reproduce the issue as
reliably.
When the problem occurs, it usually happens like this:
1. I play music via youtube as described above.
2. Around [ 6796.037342] in the kernel log, the sound starts
crackling. The crackling noise seems to correspond with the error
messages starting to appear in the log at the same time.
3. At [ 6837.948460] all USB devices on the dock get disconnected. The
mouse and keyboard stop responding, the ethernet interface vanishes
from `ip a` output and pulseaudio removes the headset as a playback
device and switches to a different output device. However, the
devices are usually still listed by lsusb.
4. I can usually reset the devices to a working condition by issuing
the following commands:
$ echo ":3b:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind
$ echo ":3b:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind
-- Package-specific info:
** Version:
Linux version 5.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0
(Debian 9.3.0-14), GNU ld (GNU Binutils for Debian) 2.34) #1 SMP Debian 5.7.6-1
(2020-06-24)
** Command line:
BOOT_IMAGE=/vmlinuz-5.7.0-1-amd64
root=UUID=b2d71295-5b17-4273-b46b-da957bc247c3 ro quiet splash zswap.enabled=1
** Tainted: PWOE (12801)
* proprietary module was loaded
* kernel issued warning
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
[ 5939.044677] usb 5-2.3.5: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[ 5939.044679] usb 5-2.3.5: Product: Dell dock
[ 5939.051219] hid-generic 0003:413C:B06F.0021: hiddev1,hidraw6: USB HID v1.11
Device [Dell dock] on usb-:3b:00.0-2.3.5/input0
[ 5940.382569] IPv6: ADDRCONF(NETDEV_CHANGE): enxc03ebab88cdb: link becomes
ready
[ 5940.382795] r8152 6-2.4:1.0 enxc03ebab88cdb: carrier on
[ 5945.734624] usb 5-2.3.3: reset low-speed USB device number 7 using xhci_hcd
[ 5946.102811] usb 5-2.3.2.1: reset full-speed USB device number 9 using
xhci_hcd
[ 6066.017094] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[ 6066.162874] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[ 6479.015330] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[ 6479.163027] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[ 6796.037342] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 36
[ 6796.037354] xhci_hcd :3b:00.0: Looking for event-dma ffb81a80
trb-start ffb81a90 trb-end ffb81a90 seg-start ffb81000
seg-end ffb81ff0
[ 6799.587398] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 36
[ 6799.587409] xhci_hcd :3b:00.0: Looking for event-dma ffb81940
trb-start ffb81950 trb-end ffb81950 seg-start ffb81000
seg-end ffb81ff0
[ 6802.689195] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 1
[ 6802.689208] xhci_hcd :3b:00.0: Looking for event-dma ffb81be0
trb-start ffb81bf0 trb-end ffb81bf0 seg-start ffb81000
seg-end ffb81ff0
[ 6802.977106] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 1
[ 6802.977117] xhci_hcd :3b:00.0: Looking for event-dma ffc0bdf0
trb-start ffc0be00 trb-end ffc0be00 seg-start ffc0b000
seg-end ffc0bff0
[ 6803.161146] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 1
[ 6803.161154] xhci_hcd :3b:00.0: Looking for event-dma ffb81980
trb-start ffb81990 trb-end ffb81990 seg-start ffb81000
seg-end ffb81ff0
[ 6803.556231] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 1
[ 6803.556244] xhci_hcd :3b:00.0: Looking for event-dma ffb81250
trb-start ffb81260 trb-end ffb81260 seg-start ffb81000
seg-end ffb81ff0
[ 6803.747123] xhci_hcd :3b:00.0: ERROR Transfer event TRB DMA ptr not part
of current TD ep_index 1 comp_code 1
[ 6803.747138] xhci_hcd :3b:00.0: Looking for event-dma ffb81
Bug#964734: same problem with newer kernel versions
FTR, the problem stays the same also with newer upstream kernel
versions, tested:
- 5.8.0-rc4
- 5.7.8
It always works with reverted commit b88bf6c3b6ff ("PCI: Add boot
interrupt quirk mechanism for Xeon chipsets")
See more details in the upstream bug report.
Regards
Berni
