linux-signed-i386_6.0.6+2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Mapping sid to unstable.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2022 13:55:44 +0100
Source: linux-signed-i386
Architecture: source
Version: 6.0.6+2
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-i386 (6.0.6+2) unstable; urgency=medium
 .
   * Sign kernel from linux 6.0.6-2
 .
   * Ignore ABI changes for ahci_fill_cmd_slot, phylink_create and
 phylink_generic_validate
Checksums-Sha1:
 b8170eb8443a0d20470df31e49db27a645a4b434 13808 linux-signed-i386_6.0.6+2.dsc
 32daa302d3e789103be0ae42f5797b5c0dfbbcfc 3846000 
linux-signed-i386_6.0.6+2.tar.xz
Checksums-Sha256:
 97b4d1d1f7e2ead503b36dfe499a15eb5a5da05973ebce4ab2deff2ff8b50df7 13808 
linux-signed-i386_6.0.6+2.dsc
 5a8ac825ed98cc04a14dc54e7053c0d2a8f474cd92e4c2972e0f61b8ee49e872 3846000 
linux-signed-i386_6.0.6+2.tar.xz
Files:
 6494e5f3d1cc00a56d97b474c8827c5c 13808 kernel optional 
linux-signed-i386_6.0.6+2.dsc
 5f5203eaf5c8410bd8538f5655576480 3846000 kernel optional 
linux-signed-i386_6.0.6+2.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNhlrwACgkQi0FRiLdO
NzbIRA/8C8gm632e9Y8WsAbPygpJ6lOqWnNkSVU/7K3tlm3MvwKd1TrXgt+N5qX3
pruwMGdX8eKn1iow/N5Vqj4Qj/9siMIC0LWMk0XoFqfACEOt04k+npNaqUSylV5n
/blYZT9wBrnJP9En0boTpb/qpidOAnyF5sPCxek9sHF5qghyYpMhhXfH1L/RWubE
3n+Tas0fpmJ73+JZ4c0XBpz6AWBPvHS2ru+i7WX/NWK/LSVsUokP/P/gdSF2mHKz
lyQfOhMoLwe2AEngy6+doOx/bsvbyg0APuyur7iVeDdmMK+E7S58uxKsOHZTACes
EXegt5pAV4sXC9lMiBsgVbO7BXRqkGyMgUHuAkR0cnWzoOVfYYvHforkLogkMiBS
fj1YHMO+J4zQlMnQI51NBXAluVeQ2FR0upMnYImiLq8o5W8iCR9hssBe1I20cdx7
dPdDRrL94y6E3J9fhMeZU3cmZuPco5Awd9mApk1m3ZaF5km8Le2lsmfv3UZl
AF/fAcyAWu+M4rvHeZTvv0YROqOiWFkvuPRgmI5rRKavVLVvKF72RK5m4JhqIXVi
ymgNt66MFB59B9YT4eXuLqM2jaYm1rYz0enlUI6nLhXMaVnDp3Qy5KEty5GF3NMT
s7XBlvunwGne9Fay2XpPGuLLOa36rFXXmv0zzdszO9dAZFzd69k=
=wfh7
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of linux-signed-i386_6.0.6+2_source.changes

[Debian FTP Masters]

linux-signed-i386_6.0.6+2_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-i386_6.0.6+2.dsc
  linux-signed-i386_6.0.6+2.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1023298: linux: FTBFS on arm64 and armhf (ABI changes)

[Salvatore Bonaccorso]

Source: linux
Version: 6.0.6-2
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: car...@debian.org

Documenting the build failures on arm64 and armhf due to ABI changes:

https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=6.0.6-2&stamp=1667324068&raw=0
https://buildd.debian.org/status/fetch.php?pkg=linux&arch=armhf&ver=6.0.6-2&stamp=1667316319&raw=0

Regards,
Salvatore

RFC: bootloader/initramfs protocol v2

[Bastian Blank]

[Cc Ben as he gave feedback to the last iteration, Luca as he wanted
something actionable]

Hi folks

As I abondened the last try and also learned some new things in the
meantime, I'd like to discuss another try at re-organizing how Debian
does boot loaders and initramfs.  This mail mostly tries to get the goals
and requirements straight.

Please provide feedback.  Also for missing stuff.

Regards,
Bastian

## Goals

- Setup complete boot entries from packaged and generated files
- Support dumb file systems for /boot by default, so boot loaders can
  drop complex file system support.
- Re-create stuff in /boot from scratch
- Remove symlink handling from kernel package
- Single entry point for packages and admins, aka no tool specific
  "update-initramfs" anymore

## Requirements

- Read package files in /usr
- Uses observed state, not changes provided by maintainer scripts
- Dumb writes to /boot. No rename, no sym, hard links. Can use ref
  links if possible.
- Generate initramfs if needed, creates new entry if re-generated
- Keep older stuff (like previous kernel, initramfs) for a short while
- Possible to support multiple targets, like grub, zipl, flash-kernel
- Multiple inputs, plain kernel, UKI, also in one version
- Combinations of inputs, Xen+Linux
- Completely outside of kernel package
- Backward compatible support for stuff packaged in /boot
- Use config for kernel command line

## Open questions

- How to select default entry if supported, just sort by version and use
  newest?  This also works somewhat in BLS.
- How to interface with boot loaders, just absorb all knowledge about
  config and only run install tools if necessary (like with zipl as
  block map based loader)?  grub might get support for BLS, at least
  there exists a patch somewhere, that will make it easier, and we can
  just iterate over config files defining one entry each.

## Prior works

- Current Debian: change based, overwrites by dpkg in /boot, versioned
  by ABI
- systemd install-kernel: only BLS as target, which nothing used by
  default in Debian can read
More?

## File system layout

Some initial ideas about how stuff could look.

### Boot file system (/boot)

This file system might be shared, so everything is somewhat referenced
to the machine id.  This should be somewhat compatible with BLS (type
1).

* /boot/$machineid/
  * ./grub/: config snippets, so we can do "no overwrite"

### Distribution file system (/usr)

* /usr/lib/boot/$package(_$modifier)/
  * ./data: raw data for item
  * ./metadata: info about item in undetermined format

-- 
I'm a soldier, not a diplomat.  I can only tell the truth.
-- Kirk, "Errand of Mercy", stardate 3198.9

Bug#1023289: please include mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin

[Sébastien Villemot]

Package: firmware-misc-nonfree
Version: 20221012-1
Severity: normal

Dear Maintainer,

The MEDIATEK MT7922 chip integrated in my motherboard requires a firmware that 
is
currently not installed by firmware-misc-nonfree for its bluetooth
functionality to work. Note that this firwmare is present in linux-firmware.git:

nov. 01 20:13:24 rama kernel: mt7921e :07:00.0: enabling device ( -> 
0002)
nov. 01 20:13:24 rama kernel: usbcore: registered new interface driver btusb
nov. 01 20:13:24 rama kernel: bluetooth hci0: firmware: failed to load 
mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin (-2)
nov. 01 20:13:24 rama kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
nov. 01 20:13:24 rama kernel: bluetooth hci0: firmware: failed to load 
mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin (-2)
nov. 01 20:13:24 rama kernel: bluetooth hci0: Direct firmware load for 
mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2
nov. 01 20:13:24 rama kernel: Bluetooth: hci0: Failed to load firmware file (-2)
nov. 01 20:13:24 rama kernel: Bluetooth: hci0: Failed to set up firmware (-2)

It would be nice to ship it.

Thanks for your work,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1023076: linux-headers-6.0.0-2-amd64: bluetooth crashes after returning from suspend

[Gabriel Francisco]

Hi Diederik, thank for your quick response!


I installed 6.0.5-1 and during the past few days seems to be working okay.


There is only occasional messages "Bluetooth: hci0: Opcode 0x 402 
failed: -16" that appeared after installing the firmware-linux package 
from unstable, but I'm not sure if that is the cause. Bluetooth is 
working okay so far, I will keep testing and report in case I find issues.



Thanks again and have a good week,

Gabriel Francisco

On 30/10/2022 02:02, Diederik de Haas wrote:

Control: reassign -1 src:linux 6.0.3-1
Control: severity -1 important

On Sunday, 30 October 2022 00:50:25 CEST Gabriel Francisco wrote:

Package: linux-headers-6.0.0-2-amd64
Version: 6.0.3-1
Severity: normal

With this kernel seems to crash bluetooth when returning from
suspend. Few days ago my cursor froze, the computer rebooted and I
couldn't find logs in /var/log/syslog.

I think it might be related to #1021905.

Indeed many similarities, but not exactly the same ...


[24595.999699] general protection fault,
...
[24595.999793]  ? bt_sock_wait_ready+0x128/0x1a0 [bluetooth]

These things are different. I increased severity because of GPF.

Before we look further, can you test 6.0.5-1 available in Unstable?

linux_6.0.6-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2022 13:55:44 +0100
Source: linux
Architecture: source
Version: 6.0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux (6.0.6-2) unstable; urgency=medium
 .
   * Ignore ABI changes for ahci_fill_cmd_slot, phylink_create and
 phylink_generic_validate
Checksums-Sha1:
 e1d5ac92778b02fdcbeb771fc8bf83aa518f43e1 249241 linux_6.0.6-2.dsc
 6667cc72710049f9d6561c50673a400213b92f98 4117872 linux_6.0.6-2.debian.tar.xz
 c9d65a27a415069d8a80652f721fb5aae7622803 6715 linux_6.0.6-2_source.buildinfo
Checksums-Sha256:
 8e29b885ac3822131953b7e0466991fbb2f8ce63b570dcaec35ece46f1a9ef8b 249241 
linux_6.0.6-2.dsc
 ff4f78eeddb56849294d9e297e7e13ab59295f81d10175c96046c58634fe7184 4117872 
linux_6.0.6-2.debian.tar.xz
 e20bcea42adf9b87e67e0faba667142579e5f124c6fd75f82d0e9ff464629b13 6715 
linux_6.0.6-2_source.buildinfo
Files:
 6da96be8a5ff349d4fd3f5cdbbb73810 249241 kernel optional linux_6.0.6-2.dsc
 f39c91133588011f5f2779f46b04d7b0 4117872 kernel optional 
linux_6.0.6-2.debian.tar.xz
 28656e57cd8f3fa7a40e502eedc37f90 6715 kernel optional 
linux_6.0.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmNhF8NfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EJEcP/RBFUChiD1ucTauVYL6wqOVH/kfwW332
aci99AJKLqxNf1x4LN5cR3VX0XyTNHHylzVpJo2onHbAEKLWh7z26xyDRI2bG8t9
aBG7KnV3oYeGZIYjUCMTEijLwWOeVGestIPKGzgxWWqXAWvizyzVTvrhlL3lGodA
nN0OVNQMttBzeotCKTCcmJbdTKK+JH6+qgBuhR14V7du2EYebWelaufo2NQCXWu7
QM4jnzzxD8MkdQOdy6mihPmDebnU5iZwsO86qryX8ILF+DhuLY0ZdEPIDSa1eUmQ
EM+EOt11nvwPrsbBqtcqb5MpWr4AFfba5dkIUFR5FtQXo8p1AMAjVstfOf5ShKzw
rK4nmpHO4BFWZdj4lI/LHngSHFlXNZDZREB8Ty6PExSAaRy4fxoxAerIWehblYzV
5biMyUe7F0rpN4ei77GhkahjJwjcWX03MlKWAmtUpbOestt/drdRFZecDcrmEYmU
jNTXbbG0+h8JoKhqTd05AeDxurKPmtpNgtjgr9I0AxCyIIFUEujIC6/1kVVlrLts
M+rv7PRQTnCrM9n7JYrUVXnet3x/jEqq0nT9Mya1pgkktNeVm5tUd68Hc0XPtAvc
D6KLecsqCU7NN04CY3x79LW+O+Z6M0lJkQcZt9nsRo8pbQb6TqgDPzU3Dzhf5uWc
cLeTzshXOIYu
=DRra
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of linux_6.0.6-2_source.changes

[Debian FTP Masters]

linux_6.0.6-2_source.changes uploaded successfully to localhost
along with the files:
  linux_6.0.6-2.dsc
  linux_6.0.6-2.debian.tar.xz
  linux_6.0.6-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

Control: tags -1 upstream

Hi Salvatore,

On 2022-11-01 08:05:28 +0100, Salvatore Bonaccorso wrote:
> What happens if you downgrade firmware-iwlwifi to 20210818-1?

Actually, I cannot reproduce the failure with the new kernel, even
with the current firmware-iwlwifi.

I don't know what happened, but there could be random failures with
recent kernels, as other users got exactly the same error:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592

(bug reported in 2020-01) and

  https://bbs.archlinux.org/viewtopic.php?id=271459

(thread started in 2021-11).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1023192 [src:linux] linux-image-6.0.0-2-amd64: Bluetooth no longer works: 
hci0: Reading Intel version command failed (-110)
Added tag(s) upstream.

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

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Salvatore Bonaccorso]

Hi Vincent,

On Tue, Nov 01, 2022 at 02:24:44AM +0100, Vincent Lefevre wrote:
> Hi Salvatore,
> 
> On 2022-10-31 22:27:15 +0100, Salvatore Bonaccorso wrote:
> > There were no Bluetooth related changes in the relatively small 6.0.3
> > to 6.0.5 update and I cannot reproduce the issue. Can you provide the
> > full boot and kernel logs? (ideally from both runs).
> 
> I've attached the journalctl output for the boot:
>   * journal-6.0.5-1
>   * journal-6.0.3-1 after downgrading the kernel.

What happens if you downgrade firmware-iwlwifi to 20210818-1?

(While the one which your HW needs to load is still present in the binary
package there was the removal of old unsupported 3160/7260/7265/8000/8265
firmware which might have an influence).

Regards,
Salvatore