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

[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 linux/5.9.9-1.
Ignoring request to alter fixed versions of bug #977262 to the same values 
previously set
> forcemerge 976056 977262
Bug #976056 {Done: Andreas Beckmann } 
[nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: requires DRM_LEGACY, 
disabled from Linux 5.9.11 onwards
Bug #976056 {Done: Andreas Beckmann } 
[nvidia-legacy-340xx-driver] nvidia-legacy-340xx-driver: requires DRM_LEGACY, 
disabled from Linux 5.9.11 onwards
Added tag(s) moreinfo.
Bug #977262 [nvidia-legacy-340xx-driver] linux-image-5.9.0-4-amd64: 
nvidia-kernel cannot be built any more
Severity set to 'serious' from 'important'
Marked Bug as done
Added indication that 977262 affects linux-image-5.9.0-4-amd64
Marked as fixed in versions nvidia-graphics-drivers-legacy-340xx/340.108-9.
Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.108-8.
Merged 976056 977262
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
976056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976056
977262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Question] Why disable CRYPTO_SM4/CRYPTO_SM3?

[张 宁]

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
https://salsa.debian.org/kernel-team/linux/-/commit/2ea9b54f869dfdcb4ebc2cf0de2e60d3c83ac988

BR.
Ning.

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

[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
> .

Thanks. I will. But please give me some time as I am in my working hour... 
I didn't have experience with u-boot'ing a Debian kernel, so maybe I need some
time to correctly build a qemu bootable image by u-boot-rpi:armel package...
Ryutaroh

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

[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 been broken for a
> > while and no-one had reported it.  Adding that back might be an option,
> > if the Raspberry Pi device emulation in QEMU is slow.  What do you
> think?

If nobody uses linux-image-versatile now, I don't want to request the
kernel team to revive it. It may/might increase the maintainance
effort...

It will, though probably not very much.

The minimum requirements by autopkgtest-virt-qemu are
* VM has at least two serial ports,
* the Linux kernel has a driver for them, and
* the Linux kernel has a driver for a storage attached to the VM.

On the other hand, RPi series has only one serial port by PL011.
So we need to attach another serial port to the VM. For armhf, arm64,
and ppc64el, I was advised to use virtconsole by Simon McVittie,
and it has worked fine as far as I see.

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
.

[...]
> The usual practice is to use u-boot or some other board-specific boot
> loader, which can be configured by the flash-kernel package.  I don't
> think that works in QEMU.

I have not intensively investigated if we can boot linux-image-marvell
by qemu-system-arm and some u-boot Debian package...
I will see it within several days and report it back here.
First I will see u-boot-qemu Debian package and the qemu "virt" machine
can boot linux-image-marvell as suggested at
https://github.com/ARM-software/u-boot/blob/master/doc/README.qemu-arm

It won't - it has very different hardware.  Even the CPU will be
incompatible (ARMv7 whereas marvell is built for v5).

Ben.

linux-image-marvell seems capable of handling PCI serial ports.
Storage options for QEMU VM seems only "ich9-ahci" and "sdhci-pci"...

Best regards, Ryutaroh

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part

Processed: reopening 975018

[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
Stopping processing here.

Please contact me if you need assistance.
-- 
975018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 back might be an option,
> if the Raspberry Pi device emulation in QEMU is slow.  What do you
> think?

If nobody uses linux-image-versatile now, I don't want to request the
kernel team to revive it. It may/might increase the maintainance effort...

The minimum requirements by autopkgtest-virt-qemu are
* VM has at least two serial ports,
* the Linux kernel has a driver for them, and
* the Linux kernel has a driver for a storage attached to the VM.

On the other hand, RPi series has only one serial port by PL011.
So we need to attach another serial port to the VM. For armhf, arm64,
and ppc64el, I was advised to use virtconsole by Simon McVittie,
and it has worked fine as far as I see.

But linux-image-rpi does not have the virtio driver, this option cannot
be used (at least for now). Another option is to attach "pci-serial-2x"
to the qemu VM, but linux-image-rpi does not seem to have a PCI driver...
Yet another option is to attach "qemu-xhci" and "usb-serial" to the VM,
but "usb-serial" behaves much differently from isa/pci-serial and virtconsole
and it cannot be used by the current autopkgtest-virt-qemu as reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973038#40

> The usual practice is to use u-boot or some other board-specific boot
> loader, which can be configured by the flash-kernel package.  I don't
> think that works in QEMU.

I have not intensively investigated if we can boot linux-image-marvell
by qemu-system-arm and some u-boot Debian package...
I will see it within several days and report it back here.
First I will see u-boot-qemu Debian package and the qemu "virt" machine
can boot linux-image-marvell as suggested at
https://github.com/ARM-software/u-boot/blob/master/doc/README.qemu-arm

linux-image-marvell seems capable of handling PCI serial ports.
Storage options for QEMU VM seems only "ich9-ahci" and "sdhci-pci"...

Best regards, Ryutaroh

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

[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 message
Bug #972678 [initramfs-tools] initramfs-tools: bad error message when zstd 
requested but not installed
Added tag(s) pending.
Added tag(s) pending.
> tags 965935 + pending
Bug #965935 [initramfs-tools-core] configure_networking() should wait for 
specified interface
Bug #968519 [initramfs-tools-core] configure_networking(): race condition with 
RockPro64: calls ipconfig before NIC is detected
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
965935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965935
968519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968519
971270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971270
972678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 867677 974106

[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 to set host name in InitRAMFS config dynamically
Marked as found in versions initramfs-tools/0.133+deb10u1.
Bug #974106 [initramfs-tools] initramfs-tools: No hostname for nfs root
Severity set to 'wishlist' from 'normal'
Marked as found in versions initramfs-tools/0.130.
Added tag(s) patch.
Merged 867677 974106
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
867677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867677
974106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 Debian kernel would lead to improving the battery
life in this computer (and similar ones, I imagine).
I can compile my own kernel, but it would be much nicer if the option were
enabled by default in the distribution kernel, since it does not seem to impact
anything negatively in terms of stability or performance.



-- 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+deb10u1 (2020-06-07)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-9-amd64 root=/dev/mapper/eMMC-Root ro fbcon=rotate:1 
quiet

** Not tainted

** Kernel log:
[   10.532244] ath10k_pci :01:00.0: enabling device ( -> 0002)
[   10.535074] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 
reset_mode 0
[   10.580628] hid-multitouch 0003:0B05:183B.0003: input,hiddev1,hidraw2: USB 
HID v1.11 Mouse [ASUS HID Device ASUS HID Device] on usb-:00:14.0-2/input2
[   10.598428] intel_rapl: Found RAPL domain package
[   10.598433] intel_rapl: Found RAPL domain core
[   10.704116] cht-bsw-rt5645 cht-bsw-rt5645: snd-soc-dummy-dai <-> 
media-cpu-dai mapping ok
[   10.704186] cht-bsw-rt5645 cht-bsw-rt5645: snd-soc-dummy-dai <-> 
deepbuffer-cpu-dai mapping ok
[   10.704516] cht-bsw-rt5645 cht-bsw-rt5645: rt5645-aif1 <-> ssp2-port mapping 
ok
[   10.726155] intel_atomisp2_pm :00:03.0: Refused to change power state, 
currently in D3
[   10.788126] input: chtrt5645 Headset as 
/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0/input30
[   10.808751] pci_bus :01: Allocating resources
[   10.808775] pcieport :00:1c.0: bridge window [io  0x1000-0x0fff] to [bus 
01] add_size 1000
[   10.808782] pcieport :00:1c.0: bridge window [mem 0x0010-0x000f 
64bit pref] to [bus 01] add_size 20 add_align 10
[   10.808817] pcieport :00:1c.0: BAR 15: assigned [mem 
0x9100-0x911f 64bit pref]
[   10.808825] pcieport :00:1c.0: BAR 13: assigned [io  0x1000-0x1fff]
[   10.810199] pci :00:03.0: [8086:22b8] type 00 class 0x048000
[   10.810229] pci :00:03.0: reg 0x10: [mem 0x-0x003f]
[   10.810640] pci :00:03.0: BAR 0: assigned [mem 0x91c0-0x91ff]
[   10.821566] pci_bus :01: Allocating resources
[   10.884827] ath10k_pci :01:00.0: firmware: failed to load 
ath10k/pre-cal-pci-:01:00.0.bin (-2)
[   10.884991] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   10.885179] ath10k_pci :01:00.0: firmware: failed to load 
ath10k/cal-pci-:01:00.0.bin (-2)
[   10.901914] ath10k_pci :01:00.0: firmware: direct-loading firmware 
ath10k/QCA9377/hw1.0/firmware-6.bin
[   10.901933] ath10k_pci :01:00.0: qca9377 hw1.1 target 0x05020001 chip_id 
0x003821ff sub 1a3b:2a51
[   10.901937] ath10k_pci :01:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 
0 testmode 0
[   10.903147] ath10k_pci :01:00.0: firmware ver 
WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
[   11.071391] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   11.087072] ath10k_pci :01:00.0: firmware: direct-loading firmware 
ath10k/QCA9377/hw1.0/board-2.bin
[   11.087637] ath10k_pci :01:00.0: board_file api 2 bmi_id N/A crc32 
8aedfa4a
[   11.364547] Bluetooth: Core ver 2.22
[   11.364593] NET: Registered protocol family 31
[   11.364595] Bluetooth: HCI device and connection manager initialized
[   11.364854] Bluetooth: HCI socket layer initialized
[   11.364860] Bluetooth: L2CAP socket layer initialized
[   11.364876] Bluetooth: SCO socket layer initialized
[   11.422382] usbcore: registered new interface driver btusb
[   11.433376] bluetooth hci0: firmware: direct-loading firmware 
qca/rampatch_usb_0302.bin
[   11.433389] Bluetooth: hci0: using rampatch file: 
qca/rampatch_usb_0302.bin
[   11.433393] Bluetooth: hci0: QCA: patch rome 0x302 build 0x3e8, firmware 
rome 0x302 build 0x111
[   11.511886] bluetooth hci0: firmware: direct-loading firmware 
qca/nvm_usb_0302.bin
[   11.511900] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin
[   12.058694] ath10k_pci :01:00.0: Unknown eventid: 118809
[   12.061615] ath10k_pci :01:00.0: Unknown eventid: 90118
[   12.062818] ath10k_pci :01:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp 
max-sta 32 raw 0 hwcrypto 1
[   12.069593] ath: EEPROM regdomain: 0x6a
[   12.069601] ath: EEPROM indicates we should expect a direct regpair map
[   12.069611] ath: Country alpha2 being used: 00
[   12.069615] ath: Regpair used: 0x6a
[   12.128438] ath10k_pci :01:00.0 wlp1s0: renamed from wlan0
[   12.323737] Adding 4118524k swap on /dev/mmcblk0p7.  Priority:-

Processed: forcibly merging 968519 965935

[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: calls ipconfig before NIC is detected
Added tag(s) patch.
Bug #965935 [initramfs-tools-core] configure_networking() should wait for 
specified interface
Severity set to 'important' from 'normal'
Merged 965935 968519
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
965935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965935
968519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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.

You'll need to capture the kernel log using a serial console

or netconsole
.

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

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

[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) 
> testbeds at
> https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100#note_205984
> 
> To boot a qemu disk image by qemu-system-*, a booting firmware seems
> indispensable, as the autopkgtest maintainer does not like giving 
> -kernel=something
> qemu option as
> https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/97#note_205357

OK, this seems like a good reason.

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 back might be an option,
if the Raspberry Pi device emulation in QEMU is slow.  What do you
think?

> A booting firmware for an armel Debian disk image seems only
> the qemu-efi-arm Debian package (is there anything else??).

The usual practice is to use u-boot or some other board-specific boot
loader, which can be configured by the flash-kernel package.  I don't
think that works in QEMU.

Ben.

> So I resorted to the UEFI booting.
> Currently I proposes to use linux-image-armmp-lpae for armel testbed.

-- 
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: bug 900171 is forwarded to https://salsa.debian.org/kernel-team/firmware-free/-/merge_requests/1 ...

[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 
'https://salsa.debian.org/kernel-team/firmware-free/-/merge_requests/1'.
> tags 900171 + patch
Bug #900171 [src:firmware-free] firmware-free: Recommend or Suggest 
firmware-ath9k-htc
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
900171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/100#note_205984

To boot a qemu disk image by qemu-system-*, a booting firmware seems
indispensable, as the autopkgtest maintainer does not like giving 
-kernel=something
qemu option as
https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/97#note_205357

A booting firmware for an armel Debian disk image seems only
the qemu-efi-arm Debian package (is there anything else??).
So I resorted to the UEFI booting.
Currently I proposes to use linux-image-armmp-lpae for armel testbed.

Best regards, Ryutaroh

Pulling free firmware-ath9k-htc into the installer

[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 that the firmware gets built from source in a separate 
package, until now it's been excluded from the installer and Debian 
installations. I've sent a MR for the latter [2], so I'd like to know how to 
best tackle the former.

I think I can build a udeb of my package before the freeze, but I wasn't sure 
if it would be easiest for you to do something else, such as copy the firmware 
into your udeb. I'm not familiar at all with the firmware/d-i aspects of the 
kernel packages, which doesn't appear well documented to me in code comments 
or the manual, but I'm willing to put in the work to make Debian more usable 
with free software and hardware.

One hiccup though is that the firmware is included in firmware-nonfree; to 
avoid 
a filename clash I rename mine to 'htc_*-1.dev.0.fw' and set the kernel option 
to use the "development" firmware. This option would probably need to be set 
outright, or else the module needs to be reloaded. If it's appropriate, I'd be 
good to do a migration where it can be removed from firmware-nonfree and 
firmware-ath9k-htc can take back the file name.

After Bullseye I'd like to start chipping away at making the rest of the free 
firmware buildable from source [3], probably starting with the very similar 
carl9170, although I don't have hardware to test with and wonder if QEMU 
voodoo can make up for it.

P.S. The reporter of [3] pointed out that, even if we're not building it from 
source, some of the firmware may be GPL and the Debian source packages do not 
ship the source code. Although I understand how meritocracy works, this does 
seem like a very serious problem which I'd like to mention in case you haven't 
considered.

Thanks,
John

[1] https://mentors.debian.net/package/open-ath9k-htc-firmware/
[2] https://salsa.debian.org/kernel-team/firmware-free/-/merge_requests/1
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890601#15

signature.asc
Description: This is a digitally signed message part.

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

[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 Bluetooth Device Typhoon Peak (8087:0032)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890130

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

[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 'Raspberry Pi 2/3 graphics regressions starting with 5.2' 
from 'linux: Raspberry PI device-trees corrupt on >=5.2'.
Changed Bug title to 'Raspberry Pi 2/3 graphics regressions starting with 5.2' 
from 'linux: Raspberry PI device-trees corrupt on >=5.2'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
935456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935456
939633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 for several days without incident, it 
appears this is a regression in the 5.9 kernel.


Kind regards,
Phil

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

[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 using the Tianocore implementation
> it came right up with no problems.  I'm getting this odd suspicion
> someone deliberately broke the device-trees in Debian's kernel source.
> The goal being to force everyone onto the Tianocore/ACPI implementation
> and try to kill device-trees.
> 
> Right now I think this is conspiracy theory territory, but I'm left
> wondering how such a serious bug could hang around so long...

We don't patch any of this stuff.  Any bugs in the device trees that we
ship come from the upstream kernel, and need to be fixed there.  No-
one's deliberately breaking this in Debian, and you had better stop
making accusations like that.

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 976258 is important

[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.
-- 
976258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 [firmware-realtek] firmware-realtek: missing "rtl8822cu_config.bin" 
in package firmware-realtek
Added tag(s) fixed-upstream and upstream.
> tags 971791 - newcomer
Bug #971791 [firmware-realtek] firmware-realtek: missing "rtl8822cu_config.bin" 
in package firmware-realtek
Ignoring request to alter tags of bug #971791 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
971791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 976648 to src:apt

[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 found in versions linux-signed-amd64/5.9.11+1.
Ignoring request to alter fixed versions of bug #976648 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
976648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 firmware-nonfree/20200918-1.
Ignoring request to alter fixed versions of bug #974646 to the same values 
previously set
Bug #974646 [src:linux] W: Possible missing firmware 
/lib/firmware/i915/rkl_dmc_ver2_01.bin for module i915
Marked as found in versions linux/5.9.11-1.
> tag -1 upstream fixed-upstream patch
Bug #974646 [src:linux] W: Possible missing firmware 
/lib/firmware/i915/rkl_dmc_ver2_01.bin for module i915
Added tag(s) patch, fixed-upstream, and upstream.

-- 
974646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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: /lib/firmware/i915/rkl_dmc_ver2_02.bin
> 
> root@thinkpad:~# update-initramfs -u -k all
> update-initramfs: Generating /boot/initrd.img-5.0.9-4-686-pae
> W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_01.bin for
> module i915
> update-initramfs: Generating /boot/initrd.img-5.0.9-3-686-pae
> W: Possible missing firmware /lib/firmware/i915/rkl_dmc_ver2_01.bin for
> module i915
> 
> this seems to be a problem with update-initramfs

initramfs-tools just looks at the list of firmware files in each kernel
module it includes.  So if the list is wrong, it's a kernel bug.

We need to pick this upstream commit that updates the requested
firmware versions:

commit 5bf7919d530a2e1456ae602fccf365c213a4db4f
Author: José Roberto de Souza 
Date:   Thu Aug 13 13:00:28 2020 -0700

drm/i915: Update TGL and RKL DMC firmware versions

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: Re: Bug#977126: linux: No armel kernel can be booted by grub-efi-arm:armel

[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

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

[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.
> To boot a kernel in UEFI mode, it must be compiled with CONFIG_EFI.
> But no Debian armel kernel (specifically linux-image-marvell or
> linux-image-rpi) is built with CONFIG_EFI.
> This leaves armel grub-efi-arm package almost useless.

I wasn't aware that this package existed until now...

> For example, trying to boot linux-image-marvell by grub-efi-arm:armel
> shows the following message:
[...]

The marvell flavour is constrained by memory and partition limits on
many of the supported machines, so it is unlikely that we would want to
increase its size further by enabling EFI support.

The rpi flavour doesn't have those constraints, though.  What would be
the benefit of booting it in UEFI mode?

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: Re: Bug#977245: openssh-server: Kernel error after big rsync or scp

[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

[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, we can't do anything useful without that.

Also, are you using the on-board Ethernet or a separate adapter in the
RockPro64?

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

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

[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 evaluate more concretely what we're talking about
> > here.
> > 
> > Local root privilege escalation, basically? Can we get a sense of what
> > those vulerabilities are, say with some example CVEs?
> 
> Yes, local privilege escalation.
> 
> From the advisories I've prepared, I think these are all LPEs that were
> mitigated by our current patch:
[...]
> They seem to have slowed to a trickle at this point.  And there are
> sadly lots of other LPE bugs that it has no effect on.
> 
> > I'm asking because my main concern with security these days is with the
> > web browser. It's this huge gaping hole: every measure we can take to
> > sandbox that thing is become more and more critical, so I wonder if the
> > our tradeoff's evaluation is well adjusted here, especially considering
> > a lot of user_ns consumers are bypassing those restrictions by running
> > as root anyways...
> 
> I tend to agree with this.
[...]

Since no-one contradicted this, I've gone ahead and changed the default
on the master branch.  I added a NEWS entry for linux-image meta-
packages to let people know how to change it back if they want.

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: Re: Bug#977262: linux-image-5.9.0-4-amd64: nvidia-kernel cannot be built any more

[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 problems

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

[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 required kernel module
> for the nividia-packages. This includes latest legacy versions
> "340xx" as well as "390xx". 
> 
> So it is not possible, to use hardware acceleration with graphic
> cards which need these packages.
> 
> I believe, the problem is kernel related, as the nvidia-packages
> were not updated and they still build fine on
> linux-image-5.9.0-3-amd64 (the version, I am running at the moment).
> 
> It would be nice, if you could take a lokk at that, as I believe,
> there are lots of hardware like notebooks, where you can not
> exchange the graphics card easily, if not at all.

Thanks for the report.

Can you post your make.log from the build? (Should be below
/var/lib/dkms/nvidia-legacy-340xx/340.108/build/make.log respectively
patch adapted for the 390xx packages).

I suspect this will be the same as #976056

Regards,
Salvatore

Re: Modern TC schedulers in 5.8+ kernels

[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

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

[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 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disable IIO.
   * Enable BLK_CGROUP_IOCOST.
   * Enable CGROUP_HUGETLB.
 .
   [ Ben Hutchings ]
   * Fix missing module.lds for building out-of-tree modules (Closes: #975571)
 - debian/rules.real: Install module.lds under arch directory
 - kbuild: Look for module.lds under arch directory too
Checksums-Sha1:
 aa2dc71453f71b82eec91f878a0ff8569b1aeead 198949 linux_5.10~rc7-1~exp1.dsc
 82498d06d4ba8ab787f15634d26ecd1a2e5f0efc 121420772 linux_5.10~rc7.orig.tar.xz
 284fde5a65b01a38146a2092bfef93ebf39a2603 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 c48f2382add3b155e8e0ee6684efc2f6b972dfb6 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 78aa2bf26d1ca1cdb3eb4a545176252f8555b6c154835fa174316d51c5d36535 198949 
linux_5.10~rc7-1~exp1.dsc
 45c3009f71d4653810de94619fdee626e95e5ea493dee0c83807ca3f11158966 121420772 
linux_5.10~rc7.orig.tar.xz
 62211d0547a05b59394a0c6b65e778a62d16b61d9e4ebb0d59806192f1571b6a 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 5ba05b33d5384b4e217c0b3981dd3473e86f16101bfb106f50574256e740b055 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Files:
 3afef9d74552315ae422dea0b3760a56 198949 kernel optional 
linux_5.10~rc7-1~exp1.dsc
 0260209563a8ebdd249ba9677f5285a7 121420772 kernel optional 
linux_5.10~rc7.orig.tar.xz
 5e83d0f3f887e44705146c54313c897c 1257744 kernel optional 
linux_5.10~rc7-1~exp1.debian.tar.xz
 603d0f8a9be75caa7f6d2f2413bc3d5c 5792 kernel optional 
linux_5.10~rc7-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEER3HMN63jdS1rqjxLbZOIhYpp/lEFAl/TT48RHHdhbGRpQGRl
Ymlhbi5vcmcACgkQbZOIhYpp/lEFFgf+PRY8ye09c2/iFr/nFS5ttT7iTl4zofu7
wOs4kheG2gzfADonct8o3vr0tP47MR53PAXvutcH4KjcmlgpjECxVO4Z0ytjGpQb
hUqKQwB3PPPrU3VhDlVmhSEQKKj/BsdKjCXOFgNnpoYUFne2PKB1w51Iibmf0kWG
hsHmrqNPq/7MLr9pd8ms95VmMFU5sWLshmClPOqi93F7X7/HbGE0lm0iyB4TPOwk
SXTLFV9/t4aKqDaQEoiytYCBZLaI+bNynpPbSq8K4Rol6NLH0iOiShpphGzJ7TeH
On3kMB3SWRYESbJTQ8RpEEBe3if7iuutvXXHAA+bML89NfzMjh07vw==
=V8DB
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

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

[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 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.)


-- 
977005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.9.11-1
Severity: wishlist

Per discussion in the recent cloud-team meeting, there are several
additional modules that can be disabled in the cloud kernel.  The
proposed candidates for removal is below; please feel free to critique
specific entries if you think there's a need to leave them enabled.

fs/coda/coda.ko (CODA_FS)
fs/reiserfs/reiserfs.ko (REISERFS_FS)
fs/hpfs/hpfs.ko (HPFS_FS)
fs/hfsplus/hfsplus.ko   (HFSPLUS_FS)
fs/hfs/hfs.ko   (HFS_FS)
fs/jfs/jfs.ko   (JFS_FS)
fs/nilfs2/nilfs2.ko (NILFS2_FS)
fs/minix/minix.ko   (MINIX_FS)
fs/ecryptfs/ecryptfs.ko (ECRYPT_FS)

Thanks
noah
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10~rc7-1~exp1
Done: Bastian Blank 

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 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (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: 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 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disable IIO.
   * Enable BLK_CGROUP_IOCOST.
   * Enable CGROUP_HUGETLB.
 .
   [ Ben Hutchings ]
   * Fix missing module.lds for building out-of-tree modules (Closes: #975571)
 - debian/rules.real: Install module.lds under arch directory
 - kbuild: Look for module.lds under arch directory too
Checksums-Sha1:
 aa2dc71453f71b82eec91f878a0ff8569b1aeead 198949 linux_5.10~rc7-1~exp1.dsc
 82498d06d4ba8ab787f15634d26ecd1a2e5f0efc 121420772 linux_5.10~rc7.orig.tar.xz
 284fde5a65b01a38146a2092bfef93ebf39a2603 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 c48f2382add3b155e8e0ee6684efc2f6b972dfb6 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 78aa2bf26d1ca1cdb3eb4a545176252f8555b6c154835fa174316d51c5d36535 198949 
linux_5.10~rc7-1~exp1.dsc
 45c3009f71d4653810de94619fdee626e95e5ea493dee0c83807ca3f11158966 121420772 
linux_5.10~rc7.orig.tar.xz
 62211d0547a05b59394a0c6b65e778a62d16b61d9e4ebb0d59806192f1571b6a 1257744 
linux_5.10~rc7-1~exp1

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

[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 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.)


-- 
977004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Severity: wishlist
thanks

Hello Linux maintainers,

The spiffy new Dell XPS 13 9310 is shipping, but is not sold as supporting
linux yet -- but appears to work great, with the exception of the Qualcomm
Technologies 802.11ax chipset.

I installed Linux from experimental, and am able to confirm the driver is
not loaded. I believe CONFIG_ATH11K could be enabled to support this
platform.

Happy to reproduce and/or try images out to confirm! This isn't a daily
machine yet.

Thank you very much!
  Paul
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10~rc7-1~exp1
Done: Bastian Blank 

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 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (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: 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 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disable IIO.
   * Enable BLK_CGROUP_IOCOST.
   * Enable CGROUP_HUGETLB.
 .
   [ Ben Hutchings ]
   * Fix missing module.lds for building out-of-tree modules (Closes: #975571)
 - debian/rules.real: Install module.lds under arch directory
 - kbuild: Look for module.lds under arch directory too
Checksums-Sha1:
 aa2dc71453f71b82eec91f878a0ff8569b1aeead 198949 linux_5.10~rc7-1~exp1.dsc
 82498d06d4ba8ab787f15634d26ecd1a2e5f0efc 121420772 linux_5.10~rc7.orig.tar.xz
 284fde5a65b01a38146a2092bfef93ebf39a2603 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 c48f2382add3b155e8e0ee6684efc2f6b972dfb6 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 78aa2bf26d1ca1cdb3eb4a545176252f8555b6c154835fa174316d51c5d36535 198949 
linux_5.10~rc7-1~exp1.dsc
 45c3009f71d4653810de94619fdee626e95e5ea493dee0c83807ca3f11158966 121420772 
linux_5.10~rc7.orig.tar.xz
 62211d0547a05b59394a0c6b65e778a62d16b61d9e4ebb0d59806192f1571b6a 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 5ba05b33d5384b4e217c0b3981dd3473e86f16101bfb106f50574256e740b055 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
File

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

[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 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.)


-- 
976791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: linux-image-amd64
Version: 5.9.11-1

Some newer Intel machines (eg high-end 2020 Dell XPS machines) require soundwire for audio, however current Debian 
kernel configs do not include CONFIG_SOUNDWIRE at all. This may depend on #962134 as well, however #962134 can be 
resolved locally without rebuilding packages by copying the related firmware binaries.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10~rc7-1~exp1
Done: Bastian Blank 

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 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (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: 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 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disable IIO.
   * Enable BLK_CGROUP_IOCOST.
   * Enable CGROUP_HUGETLB.
 .
   [ Ben Hutchings ]
   * Fix missing module.lds for building out-of-tree modules (Closes: #975571)
 - debian/rules.real: Install module.lds under arch directory
 - kbuild: Look for module.lds under arch directory too
Checksums-Sha1:
 aa2dc71453f71b82eec91f878a0ff8569b1aeead 198949 linux_5.10~rc7-1~exp1.dsc
 82498d06d4ba8ab787f15634d26ecd1a2e5f0efc 121420772 linux_5.10~rc7.orig.tar.xz
 284fde5a65b01a38146a2092bfef93ebf39a2603 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 c48f2382add3b155e8e0ee6684efc2f6b972dfb6 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 78aa2bf26d1ca1cdb3eb4a545176252f8555b6c154835fa174316d51c5d36535 198949 
linux_5.10~rc7-1~exp1.dsc
 45c3009f71d4653810de94619fdee626e95e5ea493dee0c83807ca3f11158966 121420772 
linux_5.10~rc7.orig.tar.xz
 62211d0547a05b59394a0c6b65e778a62d16b61d9e4ebb0d59806192f1571b6a 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 5ba05b33d5384b4e217c0b3981dd3473e86f16101bfb106f50574256e740b055 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Files:
 3afef9d74552315ae422dea0b3760a56 198949 kernel optional 
linux_5.10~rc7-1~exp1.dsc
 0260209563a8ebdd249ba9677f5285a7 121420772 kernel optional 
linux_5

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

[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 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.)


-- 
975571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.10~rc4-1~exp1
Severity: important

Hi,

building out-of-tree modules againt Linux 5.10 headers in experimental fails 
with

No rule to make target 'scripts/module.lds', needed by 
'/path/to/module.ko'.  Stop.

e.g.

make[3]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/r8168/8.048.03/build/r8168.ko'.  Stop.

make[4]: *** No rule to make target 'scripts/module.lds', needed by 
'/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko'.  Stop.

make[5]: *** No rule to make target 'scripts/module.lds', needed by 
'/usr/src/modules/nvidia-kernel/nvidia-drm.ko'.  Stop.


Andreas
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10~rc7-1~exp1
Done: Bastian Blank 

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 975...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (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: 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 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disable IIO.
   * Enable BLK_CGROUP_IOCOST.
   * Enable CGROUP_HUGETLB.
 .
   [ Ben Hutchings ]
   * Fix missing module.lds for building out-of-tree modules (Closes: #975571)
 - debian/rules.real: Install module.lds under arch directory
 - kbuild: Look for module.lds under arch directory too
Checksums-Sha1:
 aa2dc71453f71b82eec91f878a0ff8569b1aeead 198949 linux_5.10~rc7-1~exp1.dsc
 82498d06d4ba8ab787f15634d26ecd1a2e5f0efc 121420772 linux_5.10~rc7.orig.tar.xz
 284fde5a65b01a38146a2092bfef93ebf39a2603 1257744 
linux_5.10~rc7-1~exp1.debian.tar.xz
 c48f2382add3b155e8e0ee6684efc2f6b972dfb6 5792 
linux_5.10~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 78aa2bf26d1ca1cdb3eb4a545176252f8555b6c154835fa174316d51c5d36535 198949 
linux_5.10~rc7-1~exp1.dsc
 45c3009f71d4653810de94619fdee626e95e5ea493dee0c83807ca3f11158966 121420772 
linux_5.10~rc7.orig.tar.xz
 62211d0547a05b59394a0c6b65e778a62d16b61d9e4ebb0d59806192f1571b6a 1257744 
li

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

[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 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.)


-- 
976635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-arm64
Version: 5.9.6-1~bpo10+1
Severity: important

Dear Maintainer,

Currently, arm64 kernel packages are built with the following Kconfig symbols 
unset:

# CONFIG_CRYPTO_SHA512_ARM64 is not set
# CONFIG_CRYPTO_SHA512_ARM64_CE is not set
# CONFIG_CRYPTO_SHA3_ARM64 is not set
# CONFIG_CRYPTO_SM3_ARM64_CE is not set
# CONFIG_CRYPTO_SM4_ARM64_CE is not set
# CONFIG_CRYPTO_CRCT10DIF_ARM64_CE is not set
# CONFIG_CRYPTO_AES_ARM64_NEON_BLK is not set
# CONFIG_CRYPTO_AES_ARM64_BS is not set

Please consider enabling these as modules. The latter two are especially 
relevant, given that scalar AES is susceptible to known-plaintext attacks on 
the key due to the fact that it is not time invariant. While most arm64 SoCs 
implement the AES instructions and therefore don't rely on these modules, 
notable SoCs such as the Raspberry Pi 3 and 4 can only use the NEON version 
which is not enabled here. (And on these platforms, these are substantially 
faster too)

-- System Information:
Debian Release: 10.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.9.0-0.bpo.2-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-arm64 depends on:
ii  linux-image-5.9.0-0.bpo.2-arm64  5.9.6-1~bpo10+1

linux-image-arm64 recommends no packages.

linux-image-arm64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10~rc7-1~exp1
Done: Bastian Blank 

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 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank  (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: 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 976791 977004 977005
Changes:
 linux (5.10~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Vincent Blut ]
   * net/sched: Enable NET_SCH_ETS and NET_SCH_FQ_PIE as modules.
 .
   [ Bastian Blank ]
   * Enable SOUNDWIRE, SOUNDWIRE_INTEL, SOUNDWIRE_QCOM.
   * Enable SND_SOC_RT700_SDW, SND_SOC_RT711_SDW, SND_SOC_RT715_SDW.
 (closes: #976791)
   * [x86] Enable SND_SOC_SOF_INTEL_SOUNDWIRE_LINK.
   * [x86] Enable SND_SOC_SOF_COMETLAKE_LP_SUPPORT,
 SND_SOC_SOF_ELKHARTLAKE_SUPPORT, SND_SOC_SOF_JASPERLAKE_SUPPORT.
   * [cloud] Disable some further filesystems. (closes: #977005)
   * [cloud] Disable NET_VENDOR_MICROCHIP.
   * [cloud] Disable ICE, IGC.
   * [amd64] Make GVE module.
   * [x86] Enable X86_CPU_RESCTRL.
   * [amd64/cloud] Disable INFINIBAND_USNIC.
   * Enable PSTORE_BLK.
   * Set SQUASHFS_FILE_DIRECT, SQUASHFS_DECOMP_MULTI_PERCPU.
   * Disable EFI_VARS.
   * [x86] Enable APPLE_PROPERTIES.
   * Enable CRYPTO_ECRDSA, CRYPTO_CURVE25519, disable CRYPTO_SM2.
   * Enable CRYPTO_CFB, CRYPTO_OFB, CRYPTO_KEYWRAP, CRYPTO_ADIANTUM.
   * Enable CRYPTO_BLAKE2S, disable CRYPTO_SM3.
   * Enable CRYPTO_AES_TI, disable CRYPTO_SM4.
   * Enable CRYPTO_DRBG_HASH, CRYPTO_DRBG_CTR.
   * Enable SND_SOC_MAX98373_SDW, SND_SOC_RT1308_SDW, SND_SOC_RT5682_SDW.
   * Enable SND_SOC_INTEL_SOUNDWIRE_SOF_MACH.
   * Enable ATH11K. (closes: #977004)
   * [arm64] Enable most accelerated crypto modules. (closes: #976635)
   * [s390x] Disa

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

[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 "390xx". 

So it is not possible, to use hardware acceleration with graphic cards which 
need these packages.

I believe, the problem is kernel related, as the nvidia-packages were not 
updated and they still build fine on linux-image-5.9.0-3-amd64 (the version, I 
am running at the moment).

It would be nice, if you could take a lokk at that, as I believe, there are 
lots of hardware like notebooks, where you can not exchange the graphics card 
easily, if not at all.

Thank you very much for any help!

Best regards

Hans



-- Package-specific info:
** Version:
Linux version 5.9.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-17) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.9-1 (2020-11-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.9.0-3-amd64 
root=UUID=ad01422d-da21-4b7f-ad9e-ce6c459ca494 ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Acer
product_name: Aspire 7520G
product_version: V1.32
chassis_vendor: Acer
chassis_version: N/A
bios_vendor: Acer
bios_version: V1.33
board_vendor: Acer
board_name: Fuquene
board_version: N/A

** Loaded modules:
xfrm_user
xfrm_algo
l2tp_ppp
l2tp_netlink
l2tp_core
ip6_udp_tunnel
udp_tunnel
pppox
ppp_generic
slhc
cmac
ctr
ccm
nf_tables
nfnetlink
cpufreq_conservative
uinput
binfmt_misc
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
mc
ath5k
snd_hda_codec_hdmi
ath
mac80211
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
edac_mce_amd
kvm_amd
snd_hda_intel
ccp
snd_intel_dspcfg
snd_hda_codec
rng_core
snd_hda_core
kvm
joydev
cfg80211
irqbypass
snd_hwdep
snd_pcm_oss
snd_mixer_oss
serio_raw
r852
pcspkr
sm_common
snd_pcm
libarc4
wmi_bmof
nand
k8temp
ir_rc6_decoder
snd_timer
nand_ecc
bch
nandcore
snd
sg
rc_rc6_mce
mtd
r592
memstick
soundcore
ene_ir
evdev
rc_core
ac
button
analog
gameport
isofs
acer_wmi
sparse_keymap
rfkill
vboxvideo
drm_vram_helper
drm_ttm_helper
ttm
drm_kms_helper
cec
nvidia(POE)
usbnet
mii
cpufreq_userspace
cpufreq_ondemand
cpufreq_powersave
powernow_k8
parport_pc
ppdev
lp
parport
loop
drm
fuse
sunrpc
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
ecb
aes_generic
libaes
crypto_simd
cryptd
glue_helper
lrw
gf128mul
algif_skcipher
af_alg
dm_crypt
dm_mod
hid_generic
usbhid
hid
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
crct10dif_common
sr_mod
cdrom
ata_generic
ahci
pata_amd
libahci
ohci_pci
libata
ohci_hcd
psmouse
ehci_pci
ehci_hcd
firewire_ohci
sdhci_pci
usbcore
cqhci
scsi_mod
sdhci
firewire_core
mmc_core
crc_itu_t
forcedeth
usb_common
i2c_nforce2
battery
wmi
video

** PCI devices:
00:00.0 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller 
[10de:0547] (rev a2)
Subsystem: Acer Incorporated [ALI] MCP67 Memory Controller [1025:0126]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP67 ISA Bridge [10de:0548] (rev 
a2)
Subsystem: Acer Incorporated [ALI] MCP67 ISA Bridge [1025:0126]
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: nForce2_smbus
Kernel modules: i2c_nforce2

00:01.2 RAM memory [0500]: NVIDIA Corporation MCP67 Memory Controller 
[10de:0541] (rev a2)
Subsystem: NVIDIA Corporation MCP67 Memory Controller [10de:cb84]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci

00:02.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller 
[10de:055f] (rev a2) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] MCP67 EHCI USB 2.0 Controller 
[1025:0126]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:04.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller 
[10de:055e] (rev a2) (prog-if 10 [OHCI])
Subsystem: Acer Incorporat

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

[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 #977245 to the same values 
previously set

-- 
977245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[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 contains gigabytes of
> data, after about 3GB have been copied. I tried once to scp a similar ammount
> of data from a different client to the same machine, with the same result. The
> commands used were:
> 
>   scp -r ./localdirectory jgmanilla@remotehost:~/
>   rsync -avP ./localdirectory jgmanilla@remotehost:~/
> 
> If you happened to be logged into an ssh session, you may get the following
> message before the system goes down:
> 
>   Message from syslogd@localhost at Dec 12 16:22:24 ...
>kernel:[  406.101940] Internal error: Oops: 9604 [#1] SMP
> 
>   Message from syslogd@localhost at Dec 12 16:22:24 ...
>kernel:[  406.130105] Code: b9402a62 f9405e63 8b020014 dac00e81 
> (f8626814) 
> 
> Expected outcome was for scp and rsync to complete their file transfers
> with no errors.
> 
> The hardware of the remote machine was a RockPro64.
> The client operating systems tested were Gentoo and Arch linux.

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.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

devicetrees overlays support

[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 write a devicetree
overlay declaring the device.
So I wrote one, but then when I tried to confirm it would apply over
the package-provided dtb (using the fdtoverlay command as a simulation
of what would happen during boot), I realised it would not: it fails
with FDT_ERR_NOTFOUND, which I traced to the absence of any __symbols__
in the base dtb.

Rebuilding the devicetree from source, just adding "-@" to the cmd_dtc
rule in scripts/Makefile.lib, and the overlay could be applied by
fdtoverlay, and worked as expected after a reboot on this new dtb.

Given the widespread use of such devices (SPI or otherwise) in the
raspberry pi ecosystem and the widespread use of overlays to interface
with them, wouldn't it be better to provide devicetrees with
__symbols__ ?

Sadly, the commonly available overlays do not expect a Debian kernel,
so they may not apply cleanly. I did not try any myself, but the
raspberrypi.org kernel do contain symbols and elements not present in
vanilla, so this seems likely to happen. Which means either these would
need to be adapted to vanilla dtb (hopefully Debian will not customise
the vanilla dtb), or the vanilla dtb extended to meet the needs. IMHO,
both are out of Debian responsibility, but I thought I should mention
this family of possible issues.

Another possible issue may be that the produced device tree is
substantially larger than without __symbols__: +40% on the "pi zero
wifi". Which seems huge, but this is in fact an increase of only a bit
above 5kB, which, once put next to a kernel image, seems really not
much.

Would there be a particular reason __symbols__ are not output by the
kernel build command ?
Maybe making it optional if the size increase matters for some very
tightly constrained platforms ?

Regards,
-- 
Vincent Pelletier