Bug#969443: arm64: please backport stolen time support to buster kernel (Re: src:linux: none)
On Wed, Sep 02, 2020 at 06:09:46PM -0700, Jonathan Nieder wrote: > > Subject: src:linux: none > > It looks like you forgot to include a subject line? *sigh* Computers are hard. > The relevant series is a4b28f5c6798 (Merge remote-tracking branch > 'kvmarm/kvm-arm64/stolen-time' into kvmarm-master/next, 2019-10-24). > It may be possible to try applying it if you are interested. That is the series I had in mind, yes. I will open a merge request once I have one prepared and tested. > That said, for this kind of issue that is about new features instead > of hardware support, my advice would be to use a more current kernel > from backports instead. That's not an option for users requiring security support. While the prevelance of arm64-based clouds is still relatively low, it is growing. As it becomes more common, the lack of visibility into CPU steal time will become a significant issue for people running in these environments, hence the "important" severity. noah
Bug#969443: arm64: please backport stolen time support to buster kernel (Re: src:linux: none)
tags 969443 + upstream fixed-upstream severity 969443 wishlist retitle 969443 arm64: please backport stolen time support to buster kernel quit Hi, Noah Meyerhans wrote: > Subject: src:linux: none It looks like you forgot to include a subject line? > When used in virtual machine environments, Linux on amd64 is able to report > "steal time" to the guest. This functionality has been supported by Linux > on amd64 for years, but was only added to arm64 with Linux 5.5. > > As Debian and arm64 are increasingly used in virtual environments, including > cloud environments, the ability to report steal time is increasingly > important for system monitoring and performance analysis. Thus, I'd like to > request that CPU steal time accounting support for arm64 be backported to > buster, if possible. Thanks for reporting. The relevant series is a4b28f5c6798 (Merge remote-tracking branch 'kvmarm/kvm-arm64/stolen-time' into kvmarm-master/next, 2019-10-24). It may be possible to try applying it if you are interested. That said, for this kind of issue that is about new features instead of hardware support, my advice would be to use a more current kernel from backports instead. Thanks and hope that helps, Jonathan
Processed: arm64: please backport stolen time support to buster kernel (Re: src:linux: none)
Processing commands for cont...@bugs.debian.org: > tags 969443 + upstream fixed-upstream Bug #969443 [src:linux] src:linux: none Added tag(s) upstream and fixed-upstream. > severity 969443 wishlist Bug #969443 [src:linux] src:linux: none Severity set to 'wishlist' from 'important' > retitle 969443 arm64: please backport stolen time support to buster kernel Bug #969443 [src:linux] src:linux: none Changed Bug title to 'arm64: please backport stolen time support to buster kernel' from 'src:linux: none'. > quit Stopping processing here. Please contact me if you need assistance. -- 969443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969443: src:linux: none
Package: src:linux Version: 4.19.132-1 Severity: important Tags: buster When used in virtual machine environments, Linux on amd64 is able to report "steal time" to the guest. This functionality has been supported by Linux on amd64 for years, but was only added to arm64 with Linux 5.5. As Debian and arm64 are increasingly used in virtual environments, including cloud environments, the ability to report steal time is increasingly important for system monitoring and performance analysis. Thus, I'd like to request that CPU steal time accounting support for arm64 be backported to buster, if possible. noah
Bug#945077: marked as done (firmware-linux: Missing firmware for Intel bluetooth device 22560 makes adapter not available)
Your message dated Wed, 2 Sep 2020 23:02:24 +0200
with message-id <20200902210224.gc770...@photino.stro.at>
and subject line Re: firmware-linux: Missing firmware for Intel bluetooth
device 22560 makes adapter not available
has caused the Debian Bug report #945077,
regarding firmware-linux: Missing firmware for Intel bluetooth device 22560
makes adapter not available
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.)
--
945077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-linux
Version: 20190717-2
Severity: important
Nov 16 16:35:17 Nesbitt kernel: [ 11.106019] bluetooth hci0: firmware: failed
to load intel/ibt-19-32-4.sfi (-2)
Nov 16 16:35:17 Nesbitt kernel: [ 11.106021] bluetooth hci0: Direct firmware
load for intel/ibt-19-32-4.sfi failed with error -2
Bluetooth adapter is not working without this file ("no adapters found"). After
manually
adding the firmware file (and the .ddc) it does work.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages firmware-linux depends on:
ii firmware-linux-free 3.4
ii firmware-linux-nonfree 20190717-2
Versions of packages firmware-linux recommends:
ii amd64-microcode 3.20191021.1
ii intel-microcode 3.20191115.1
firmware-linux suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 20200721-1
done
files were added.
thanks.--- End Message ---
Bug#969433: linux-image-4.19.0-10-amd64: sluggish and jittery, [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request.
Package: src:linux Version: 4.19.132-1 Severity: normal -- Package-specific info: ** Version: Linux version 4.19.0-10-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-10-amd64 root=/dev/mapper/lappy--vg-root ro quiet module_blacklist=mei_me ** Not tainted ** Kernel log: [10932.246340] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10933.861829] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10933.911908] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10933.961969] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10934.012027] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10934.062089] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10934.112167] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10934.162228] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10934.212294] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10934.262352] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10935.845841] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10935.895918] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10935.945979] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10935.996040] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10936.046101] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10936.096164] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10936.146225] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10936.196285] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10936.246343] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10937.861750] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10937.911823] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10937.961876] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10938.011933] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10938.061992] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10938.112065] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10938.162125] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10938.212186] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10938.262244] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10939.845677] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10939.895742] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10939.945794] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10939.995851] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10940.045906] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10940.095972] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10940.146034] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10940.196095] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10940.246152] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10941.861647] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10941.911724] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10941.961784] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10942.011848] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10942.061908] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10942.111982] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10942.162040] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. [10942.212106] [drm:fw_domains_get
firmware-nonfree 20200817-1 upload
Tomorrow will upload this release. best, -- maks signature.asc Description: PGP signature
Bug#965074: Patches to make multicast proccesing on CDC NCM drivers
On Wed, Sep 02, 2020 at 03:27:28PM +0200, Santiago Ruano Rincón wrote: > El 02/09/20 a las 14:05, Greg KH escribió: > > On Wed, Sep 02, 2020 at 01:47:18PM +0200, Santiago Ruano Rincón wrote: > > > El 30/07/20 a las 16:07, Oliver Neukum escribió: > > > > Am Donnerstag, den 30.07.2020, 15:53 +0200 schrieb Santiago Ruano > > > > Rincón: > > > > > Hi, > > > > > > > > > > Miguel Rodríguez sent this set of patches two years ago to fix the > > > > > lack > > > > > of multicast processing on CDC NCM driver: > > > > > > > > > > https://www.spinics.net/lists/linux-usb/msg170611.html > > > > > https://www.spinics.net/lists/linux-usb/msg170603.html > > > > > https://www.spinics.net/lists/linux-usb/msg170567.html > > > > > https://www.spinics.net/lists/linux-usb/msg170568.html > > > > > > > > > > I've using a DKMS version of them, available in > > > > > https://github.com/stbuehler/fixed-cdc-ether-ncm/tree/wip/patches > > > > > since more than a year ago, and they are working fine with my Dell > > > > > D6000 > > > > > docking station. IPv6 connectivity is broken without them. > > > > > > > > > > Is there any chance to consider those patches (or what would be needed > > > > > to make it happen)? > > > > > It would be great to have them upstream! > > > > > > > > Hi, > > > > > > > > they have been merged on Wednesday. > > > … > > > > > > Great, thanks! > > > > > > It would be possible to apply/backport Miguel's patches (along with > > > 5fd99b5d9950d6300467ded18ff4e44af0b4ae55) to stable versions please? > > > > I don't see that git commit id in Linus's tree, are you sure it is > > correct? > > I should had mention it is found in linux-next, sorry. Please see > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969365#10 Ah, nothing I can do with patches that are not yet in Linus's tree. > > > FWIW, in the context of Debian, I'm personally interested in 4.19.y. > > > > What specific list of commits are you wanting to see backported? > > This: > > 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6 > e10dcb1b6ba714243ad5a35a11b91cc14103a9a9 > e506addeff844237d60545ef4f6141de21471caf > 0226009ce0f6089f9b31211f7a2703cf9a327a01 These do not look like bugfixes, but a new feature being added for this driver. So why not just use a newer kernel version for this feature? thanks, greg k-h
Bug#965074: Patches to make multicast proccesing on CDC NCM drivers
El 02/09/20 a las 14:05, Greg KH escribió: > On Wed, Sep 02, 2020 at 01:47:18PM +0200, Santiago Ruano Rincón wrote: > > El 30/07/20 a las 16:07, Oliver Neukum escribió: > > > Am Donnerstag, den 30.07.2020, 15:53 +0200 schrieb Santiago Ruano > > > Rincón: > > > > Hi, > > > > > > > > Miguel Rodríguez sent this set of patches two years ago to fix the lack > > > > of multicast processing on CDC NCM driver: > > > > > > > > https://www.spinics.net/lists/linux-usb/msg170611.html > > > > https://www.spinics.net/lists/linux-usb/msg170603.html > > > > https://www.spinics.net/lists/linux-usb/msg170567.html > > > > https://www.spinics.net/lists/linux-usb/msg170568.html > > > > > > > > I've using a DKMS version of them, available in > > > > https://github.com/stbuehler/fixed-cdc-ether-ncm/tree/wip/patches > > > > since more than a year ago, and they are working fine with my Dell D6000 > > > > docking station. IPv6 connectivity is broken without them. > > > > > > > > Is there any chance to consider those patches (or what would be needed > > > > to make it happen)? > > > > It would be great to have them upstream! > > > > > > Hi, > > > > > > they have been merged on Wednesday. > > … > > > > Great, thanks! > > > > It would be possible to apply/backport Miguel's patches (along with > > 5fd99b5d9950d6300467ded18ff4e44af0b4ae55) to stable versions please? > > I don't see that git commit id in Linus's tree, are you sure it is > correct? I should had mention it is found in linux-next, sorry. Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969365#10 > > FWIW, in the context of Debian, I'm personally interested in 4.19.y. > > What specific list of commits are you wanting to see backported? This: 37a2ebdd9e597ae1a0270ac747883ea8f6f767b6 e10dcb1b6ba714243ad5a35a11b91cc14103a9a9 e506addeff844237d60545ef4f6141de21471caf 0226009ce0f6089f9b31211f7a2703cf9a327a01 Thanks, -- santiago signature.asc Description: PGP signature
firmware-nonfree_20200721-1~bpo10+1_amd64.changes ACCEPTED into buster-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 02 Sep 2020 20:51:50 +0900 Source: firmware-nonfree Binary: firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-intelwimax firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc firmware-qlogic firmware-realtek firmware-samsung firmware-siano firmware-ti-connectivity Architecture: source all Version: 20200721-1~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer: Debian Kernel Team Changed-By: Roger Shimizu Description: firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards firmware-bnx2 - Binary firmware for Broadcom NetXtremeII firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards firmware-cavium - Binary firmware for Cavium Ethernet adapters firmware-intel-sound - Binary firmware for Intel sound DSPs firmware-intelwimax - Binary firmware for Intel WiMAX Connection firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 d firmware-iwlwifi - Binary firmware for Intel Wireless cards firmware-libertas - Binary firmware for Marvell wireless cards firmware-linux - Binary firmware for various drivers in the Linux kernel (metapack firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel (meta-pac firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel firmware-myricom - Binary firmware for Myri-10G Ethernet adapters firmware-netronome - Binary firmware for Netronome network adapters firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 3100 Se firmware-qcom-media - Binary firmware for Qualcomm graphics/video (dummy package) firmware-qcom-soc - Binary firmware for Qualcomm SoCs firmware-qlogic - Binary firmware for QLogic HBAs firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters firmware-samsung - Binary firmware for Samsung MFC video codecs firmware-siano - Binary firmware for Siano MDTV receivers firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and BT/FM/GPS adapters Closes: 962972 968272 Changes: firmware-nonfree (20200721-1~bpo10+1) buster-backports; urgency=medium . * Team upload. * Rebuild for buster-backports. . firmware-nonfree (20200721-1) unstable; urgency=medium . * New upstream version: - QCA: Update WCN3991 FW files - amdgpu: add UVD firmware for SI asics - QCA: Update Bluetooth firmware for QCA6390 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - QCA: Add correct bin file for WCN3991 - Update binary firmware for MT7663 based devices to include firmware offload feature and low power feature. - rtl_nic: update firmware for RTL8125B - Update to 20200629111339 version to aligh SDK. Mainly fix DFS false alarm. * add RTL8822C WoW firmware (closes: #968272) * add RTL8152/RTL8153 firmware (closes: #962972) . [ Jeremy Stanley ] * brcm80211: include the NVRAM config file needed by GPD Pocket and Win UMPCs Checksums-Sha1: e2074d801cc31c539e5986396695543e83908e84 4003 firmware-nonfree_20200721-1~bpo10+1.dsc 5c7cd17a5362dd2252f7fff7933d8bc47a04ecc2 783816 firmware-nonfree_20200721-1~bpo10+1.debian.tar.xz a2a1289612b04314a5b24e9d056c36b15680fa1b 4682084 firmware-amd-graphics_20200721-1~bpo10+1_all.deb a2866b3be384c46624b52a2f33d083ee2da93b47 5708212 firmware-atheros_20200721-1~bpo10+1_all.deb 1de451f0a719cebf3a9c77f6a123ddb7f30eb80b 105952 firmware-bnx2_20200721-1~bpo10+1_all.deb 66c8a26b7460933f6f7ef5e7af3edb3e010301da 3400256 firmware-bnx2x_20200721-1~bpo10+1_all.deb ddfbdd8c543c3a6f32272c6fd540f1dd298591f7 4282816 firmware-brcm80211_20200721-1~bpo10+1_all.deb 4eb22f2fc892a725e84a4652329188bd796f9698 652936 firmware-cavium_20200721-1~bpo10+1_all.deb a60278f741d6fdee8e33da9283a596ed59955e21 763928 firmware-intel-sound_20200721-1~bpo10+1_all.deb c9adc23acad3810e66e5656f5ac7b3a92d799c92 1197076 firmware-intelwimax_20200721-1~bpo10+1_all.deb 7ea8dff5d16b8f695fab2610c79cb389511d3249 254592 firmware-ipw2x00_20200721-1~bpo10+1_all.deb 186c2ec0e5916affc9a26bc0dca60399245aaeae 112460 firmware-ivtv_20200721-1~bpo10+1_all.deb f3cd2c01407944010b9e0736c97ce7cf20bcd4df 9965928 firmware-iwlwifi_20200721-1~bpo10+1_all.deb
Processing of firmware-nonfree_20200721-1~bpo10+1_amd64.changes
firmware-nonfree_20200721-1~bpo10+1_amd64.changes uploaded successfully to localhost along with the files: firmware-nonfree_20200721-1~bpo10+1.dsc firmware-nonfree_20200721-1~bpo10+1.debian.tar.xz firmware-amd-graphics_20200721-1~bpo10+1_all.deb firmware-atheros_20200721-1~bpo10+1_all.deb firmware-bnx2_20200721-1~bpo10+1_all.deb firmware-bnx2x_20200721-1~bpo10+1_all.deb firmware-brcm80211_20200721-1~bpo10+1_all.deb firmware-cavium_20200721-1~bpo10+1_all.deb firmware-intel-sound_20200721-1~bpo10+1_all.deb firmware-intelwimax_20200721-1~bpo10+1_all.deb firmware-ipw2x00_20200721-1~bpo10+1_all.deb firmware-ivtv_20200721-1~bpo10+1_all.deb firmware-iwlwifi_20200721-1~bpo10+1_all.deb firmware-libertas_20200721-1~bpo10+1_all.deb firmware-linux-nonfree_20200721-1~bpo10+1_all.deb firmware-linux_20200721-1~bpo10+1_all.deb firmware-misc-nonfree_20200721-1~bpo10+1_all.deb firmware-myricom_20200721-1~bpo10+1_all.deb firmware-netronome_20200721-1~bpo10+1_all.deb firmware-netxen_20200721-1~bpo10+1_all.deb firmware-nonfree_20200721-1~bpo10+1_amd64.buildinfo firmware-qcom-media_20200721-1~bpo10+1_all.deb firmware-qcom-soc_20200721-1~bpo10+1_all.deb firmware-qlogic_20200721-1~bpo10+1_all.deb firmware-realtek_20200721-1~bpo10+1_all.deb firmware-samsung_20200721-1~bpo10+1_all.deb firmware-siano_20200721-1~bpo10+1_all.deb firmware-ti-connectivity_20200721-1~bpo10+1_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#965074: Patches to make multicast proccesing on CDC NCM drivers
On Wed, Sep 02, 2020 at 01:47:18PM +0200, Santiago Ruano Rincón wrote: > El 30/07/20 a las 16:07, Oliver Neukum escribió: > > Am Donnerstag, den 30.07.2020, 15:53 +0200 schrieb Santiago Ruano > > Rincón: > > > Hi, > > > > > > Miguel Rodríguez sent this set of patches two years ago to fix the lack > > > of multicast processing on CDC NCM driver: > > > > > > https://www.spinics.net/lists/linux-usb/msg170611.html > > > https://www.spinics.net/lists/linux-usb/msg170603.html > > > https://www.spinics.net/lists/linux-usb/msg170567.html > > > https://www.spinics.net/lists/linux-usb/msg170568.html > > > > > > I've using a DKMS version of them, available in > > > https://github.com/stbuehler/fixed-cdc-ether-ncm/tree/wip/patches > > > since more than a year ago, and they are working fine with my Dell D6000 > > > docking station. IPv6 connectivity is broken without them. > > > > > > Is there any chance to consider those patches (or what would be needed > > > to make it happen)? > > > It would be great to have them upstream! > > > > Hi, > > > > they have been merged on Wednesday. > … > > Great, thanks! > > It would be possible to apply/backport Miguel's patches (along with > 5fd99b5d9950d6300467ded18ff4e44af0b4ae55) to stable versions please? I don't see that git commit id in Linus's tree, are you sure it is correct? > FWIW, in the context of Debian, I'm personally interested in 4.19.y. What specific list of commits are you wanting to see backported? thanks, greg k-h
Bug#965074: Patches to make multicast proccesing on CDC NCM drivers
El 30/07/20 a las 16:07, Oliver Neukum escribió: > Am Donnerstag, den 30.07.2020, 15:53 +0200 schrieb Santiago Ruano > Rincón: > > Hi, > > > > Miguel Rodríguez sent this set of patches two years ago to fix the lack > > of multicast processing on CDC NCM driver: > > > > https://www.spinics.net/lists/linux-usb/msg170611.html > > https://www.spinics.net/lists/linux-usb/msg170603.html > > https://www.spinics.net/lists/linux-usb/msg170567.html > > https://www.spinics.net/lists/linux-usb/msg170568.html > > > > I've using a DKMS version of them, available in > > https://github.com/stbuehler/fixed-cdc-ether-ncm/tree/wip/patches > > since more than a year ago, and they are working fine with my Dell D6000 > > docking station. IPv6 connectivity is broken without them. > > > > Is there any chance to consider those patches (or what would be needed > > to make it happen)? > > It would be great to have them upstream! > > Hi, > > they have been merged on Wednesday. … Great, thanks! It would be possible to apply/backport Miguel's patches (along with 5fd99b5d9950d6300467ded18ff4e44af0b4ae55) to stable versions please? FWIW, in the context of Debian, I'm personally interested in 4.19.y. Best regards, -- Santiago signature.asc Description: PGP signature
