Bug#977262: linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more

2020-12-13 Thread Hans-J. Ullrich
Package: src:linux Version: 5.9.9-1 Severity: important Dear Maintainer, when upgrading from linux-image-5.9.0-3-amd64 to *-5.9.0-4-amd64 and its headers, it is not possible to build the required kernel module for the nividia-packages. This includes latest legacy versions "340xx" as well as

Bug#976635: marked as done (linux-image-arm64: Accelerated crypto modules missing from kernel config)

2020-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2020 11:00:10 + with message-id and subject line Bug#976635: fixed in linux 5.10~rc7-1~exp1 has caused the Debian Bug report #976635, regarding linux-image-arm64: Accelerated crypto modules missing from kernel config to be marked as done. This means that you

Bug#975571: marked as done (linux: No rule to make target 'scripts/module.lds' while building out-of-tree modules)

2020-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2020 11:00:10 + with message-id and subject line Bug#975571: fixed in linux 5.10~rc7-1~exp1 has caused the Debian Bug report #975571, regarding linux: No rule to make target 'scripts/module.lds' while building out-of-tree modules to be marked as done. This

Bug#977005: marked as done (cloud: Additional modules to disable)

2020-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2020 11:00:10 + with message-id and subject line Bug#977005: fixed in linux 5.10~rc7-1~exp1 has caused the Debian Bug report #977005, regarding cloud: Additional modules to disable to be marked as done. This means that you claim that the problem has been dealt

Bug#977004: marked as done (Please enable CONFIG_ATH11K for the XPS 13 9310)

2020-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2020 11:00:10 + with message-id and subject line Bug#977004: fixed in linux 5.10~rc7-1~exp1 has caused the Debian Bug report #977004, regarding Please enable CONFIG_ATH11K for the XPS 13 9310 to be marked as done. This means that you claim that the problem has

Bug#976791: marked as done (Enable CONFIG_SOUNDWIRE (and related drivers))

2020-12-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Dec 2020 11:00:10 + with message-id and subject line Bug#976791: fixed in linux 5.10~rc7-1~exp1 has caused the Debian Bug report #976791, regarding Enable CONFIG_SOUNDWIRE (and related drivers) to be marked as done. This means that you claim that the problem has

Processed: Re: Bug#977245: openssh-server: Kernel error after big rsync or scp

2020-12-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 linux Bug #977245 [openssh-server] openssh-server: Kernel error after big rsync or scp Bug reassigned from package 'openssh-server' to 'linux'. No longer marked as found in versions openssh/1:8.4p1-3. Ignoring request to alter fixed versions of bug

linux_5.10~rc7-1~exp1_source.changes ACCEPTED into experimental, experimental

2020-12-13 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Dec 2020 11:16:29 +0100 Source: linux Architecture: source Version: 5.10~rc7-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Kernel Team Changed-By: Bastian Blank Closes: 975571 976635

devicetrees overlays support

2020-12-13 Thread Vincent Pelletier
Hello, (please keep me CC'ed, I'm not subscribed) I am using the (non-official) Debian port for raspberry pi from raspi.debian.net , and have a device connected to the SPI bus pins on the 40-pins extension connector. In my understanding, the proper approach to interfacing with such device is to

Re: Bug#977245: openssh-server: Kernel error after big rsync or scp

2020-12-13 Thread Colin Watson
Control: reassign -1 linux On Sat, Dec 12, 2020 at 09:53:23PM -0500, Gabe wrote: > After attempting to scp or rsync a directory with many large-ish files > (20-600M) to a remote host, the remote machine will crash. This hasn't > happened > with smaller file transfers; only when the directory

Re: Modern TC schedulers in 5.8+ kernels

2020-12-13 Thread Vincent Blut
Hi, Le 2020-11-26T01:50+0300, engine a écrit : # CONFIG_NET_SCH_FQ_PIE is not set # CONFIG_NET_SCH_ETS is not set These are now enabled in Linux 5.10~rc7-1~exp1. Cheers, Vincent signature.asc Description: PGP signature

Processed: Re: Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #977126 [src:linux] linux: No armel kernel can be booted by grub-efi-arm:armel Added tag(s) moreinfo. -- 977126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: reassign 976648 to src:apt

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 976648 src:apt Bug #976648 [linux-image-amd64] linux-image-amd64: check if there is enough storage space before installing package and warn user if not Bug reassigned from package 'linux-image-amd64' to 'src:apt'. No longer marked as

Bug#939633: More severe #939633 for RP4 on 5.8?

2020-12-13 Thread Ben Hutchings
On Fri, 2020-11-27 at 20:41 -0800, Elliott Mitchell wrote: > found 935456 5.9.6-1~bpo10+1 > quit > > After having spent several hours on kernel compiles and experimenting > with the situation, I'm fairly sure this also applies to > linux-source-5.9. > > Odd thing is, when I booted the device

Bug#977299: Add Support for Intel AX210 Wi-fi and Intel Typhoon Peak Bluetooth

2020-12-13 Thread Chris Dos
Package: linux-image-amd64 Version: 5.10.0 Add support for the new Intel AX210 Wireless Adapter that includes Typhoon Peak Bluetooth. Please see: Support Intel AX210 wifi [8086:2725] Subsystem [8086:4020] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902848 Add support for Intel

Bug#898446: Please reconsider enabling the user namespaces by default

2020-12-13 Thread Ben Hutchings
On Tue, 2020-11-17 at 17:19 +, Ben Hutchings wrote: > On Tue, 2020-11-17 at 11:18 -0500, Antoine Beaupré wrote: > [...] > > Could we get a little more hard data about the attack vectors here? I > > totally trust the security team's "gut feeling" on this, but it would be > > great to be able to

Processed: Re: Bug#977245: openssh-server: Kernel error after big rsync or scp

2020-12-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #977245 [linux] openssh-server: Kernel error after big rsync or scp Added tag(s) moreinfo. -- 977245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#977245: openssh-server: Kernel error after big rsync or scp

2020-12-13 Thread Ben Hutchings
Control: tag -1 moreinfo On Sun, 2020-12-13 at 09:57 +, Colin Watson wrote: [...] > In general kernel oopses are kernel bugs, not userspace bugs, so > reassigning to linux.  I expect that the full contents of the oops > message from syslog would be helpful to the kernel maintainers. Right,

Processed: severity of 971791 is important, tagging 971791, tagging 971791

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 971791 important Bug #971791 [firmware-realtek] firmware-realtek: missing "rtl8822cu_config.bin" in package firmware-realtek Severity set to 'important' from 'normal' > tags 971791 + upstream fixed-upstream Bug #971791

Processed: severity of 976258 is important

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 976258 important Bug #976258 [src:linux] linux: hibernation attempt results in shutdown and unclean filesystem Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#977262: linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more

2020-12-13 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo On Sun, Dec 13, 2020 at 11:47:59AM +0100, Hans-J. Ullrich wrote: > Package: src:linux > Version: 5.9.9-1 > Severity: important > > Dear Maintainer, > > when upgrading from linux-image-5.9.0-3-amd64 to *-5.9.0-4-amd64 and > its headers, it is not possible to build the

Processed: Re: Bug#977262: linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more

2020-12-13 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #977262 [src:linux] linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more Added tag(s) moreinfo. -- 977262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977262 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#974646: ver2_02 is in firmware-misc-nonfree, ver2_01 is not

2020-12-13 Thread Ben Hutchings
Control: reassign -1 src:linux 5.9.11-1 Control: tag -1 upstream fixed-upstream patch On Thu, 2020-12-03 at 18:08 +0100, Manfred Brandl wrote: > reassign 974646 initramfs-tools > > on latest bullseye: > > manfred@thinkpad:~$ apt-file search rkl_dmc > firmware-misc-nonfree:

Processed: Re: Bug#974646: ver2_02 is in firmware-misc-nonfree, ver2_01 is not

2020-12-13 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 5.9.11-1 Bug #974646 [firmware-misc-nonfree] W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_01.bin for module i915 Bug reassigned from package 'firmware-misc-nonfree' to 'src:linux'. No longer marked as found in versions

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Ben Hutchings
Control: tag -1 moreinfo On Fri, 2020-12-11 at 19:09 +0900, Ryutaroh Matsumoto wrote: > Source: linux > Version: 5.9.11-1 > Severity: important > X-Debbugs-Cc: pkg-grub-de...@alioth-lists.debian.net > > Dear Maintainer, > > grub-efi-arm:armel package remains almost unusable for very long time.

Bug#976788: linux-image-5.9.0-4-amd64: nouveau DRM timeout causes machine to freeze

2020-12-13 Thread Philip Stewart
Hello again, I wanted to share a further finding since the bug report was submitted. Following repeated lock-ups making the system practically unusable, I have installed linux-image-5.8.0-2-amd64 (package version 5.8.10-1) from the Debian snapshot archive. Having now tested this 5.8 kernel

Processed: retitle 939633 to Raspberry Pi 2/3 graphics regressions starting with 5.2

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 939633 Raspberry Pi 2/3 graphics regressions starting with 5.2 Bug #939633 [src:linux] linux: Raspberry PI device-trees corrupt on >=5.2 Bug #935456 [src:linux] linux: Raspberry PI device-trees corrupt on >=5.2 Changed Bug title to

Bug#977245: openssh-server: Kernel error after big rsync or scp

2020-12-13 Thread Ben Hutchings
[Reply to all, not just to me] On Sun, 2020-12-13 at 20:11 +, Gabe Alvarez wrote: > I am using the on-board ethernet. > I've checked the files in /var/log, and none of them contain > anything referencing the oopses that have happened; neither does > anything in journalctl. Please advise.

Pulling free firmware-ath9k-htc into the installer

2020-12-13 Thread John Scott
Hi, I'm not subscribed, please CC me. I'm adopting the firmware-ath9k-htc package, which has been FTBFS for a while but I've already found a sponsor and expect my fixes will be uploaded shortly [1]. These are some of the flagship chipsets for free wireless adapters, and although it's good

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Ben Hutchings
On Mon, 2020-12-14 at 05:13 +0900, Ryutaroh Matsumoto wrote: > > The rpi flavour doesn't have those constraints, though.  What would be > > the benefit of booting it in UEFI mode? > > Thank you for paying your attention! > I considered extending autopkgtest-virt-qemu to armel (and other archs) >

Processed: forcibly merging 867677 974106

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 867677 974106 Bug #867677 [initramfs-tools] initramfs-tools: [patch] feature request: provide hook to set host name in InitRAMFS config dynamically Bug #867677 [initramfs-tools] initramfs-tools: [patch] feature request: provide hook

Processed: limit source to initramfs-tools, tagging 971270, tagging 965935

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > limit source initramfs-tools Limiting to bugs with field 'source' containing at least one of 'initramfs-tools' Limit currently set to 'source':'initramfs-tools' > tags 971270 + pending Bug #971270 [initramfs-tools] initramfs-tools: fix warning

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Ryutaroh Matsumoto
> The rpi flavour doesn't have those constraints, though. What would be > the benefit of booting it in UEFI mode? Thank you for paying your attention! I considered extending autopkgtest-virt-qemu to armel (and other archs) testbeds at

Bug#977320: linux-image-4.19.0-9-amd64: Enable CONFIG_BACKLIGHT_PWM

2020-12-13 Thread Pablo Bianucci
Package: src:linux Version: 4.19.118-2+deb10u1 Severity: normal Dear Maintainer, My ASUS Transformer TA102 needs CONFIG_BACKLIGHT_PWM enabled to be able to turn down the screen backlight. Reducing the backlight is critical to extend battery life, so I having the option enabled in the default

Processed: bug 900171 is forwarded to https://salsa.debian.org/kernel-team/firmware-free/-/merge_requests/1 ...

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 900171 > https://salsa.debian.org/kernel-team/firmware-free/-/merge_requests/1 Bug #900171 [src:firmware-free] firmware-free: Recommend or Suggest firmware-ath9k-htc Set Bug forwarded-to-address to

Processed: forcibly merging 968519 965935

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 968519 965935 Bug #968519 [initramfs-tools-core] configure_networking(): race condition with RockPro64: calls ipconfig before NIC is detected Bug #968519 [initramfs-tools-core] configure_networking(): race condition with RockPro64:

Processed: reopening 975018

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 975018 Bug #975018 {Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?= } [initramfs-tools] setup /dev/stdin etc in initramfs-tools Bug reopened Ignoring request to alter fixed versions of bug #975018 to the same values previously set > thanks

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Ben Hutchings
On Mon, 2020-12-14 at 10:24 +0900, Ryutaroh Matsumoto wrote: Hi Ben, thanks again for your response. > We used to provide a 'versatile' flavour on armel, for the ARM > > Versatile boards that QEMU has supported for a long time.  I removed > > this flavour back in 2016 after finding that it had

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Ryutaroh Matsumoto
Hi Ben, > But linux-image-rpi does not have the virtio driver, this option cannot > be used (at least for now). > > Can you try adding it? You should be able to cross-build the kernel > package quite easily if you use the profiles "cross,pkg.linux.notools". > There are generic instructions at >

Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

2020-12-13 Thread Ryutaroh Matsumoto
Hi Ben, thanks again for your response. > We used to provide a 'versatile' flavour on armel, for the ARM > Versatile boards that QEMU has supported for a long time. I removed > this flavour back in 2016 after finding that it had been broken for a > while and no-one had reported it. Adding that

Processed: reassign 977262 to nvidia-legacy-340xx-driver, forcibly merging 976056 977262

2020-12-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 977262 nvidia-legacy-340xx-driver Bug #977262 [src:linux] linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more Bug reassigned from package 'src:linux' to 'nvidia-legacy-340xx-driver'. No longer marked as found in versions

[Question] Why disable CRYPTO_SM4/CRYPTO_SM3?

2020-12-13 Thread 张 宁
Hi, Bastian Blank I find in master branch, CRYPTO_SM4/CRYPTO_SM3 are disabled without clean justification. could you tell us why? https://salsa.debian.org/kernel-team/linux/-/commit/3825c0accbd374d8ed4c9f8a9a516093e41cbe43