linux-signed-i386_5.18.2+1~bpo11+1_source.changes ACCEPTED into bullseye-backports, bullseye-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jun 2022 13:38:17 +0200
Source: linux-signed-i386
Architecture: source
Version: 5.18.2+1~bpo11+1
Distribution: bullseye-backports
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Changes:
 linux-signed-i386 (5.18.2+1~bpo11+1) bullseye-backports; urgency=medium
 .
   * Sign kernel from linux 5.18.2-1~bpo11+1
 .
   * Rebuild for bullseye-backports:
 - Change ABI number to 0.bpo.1
Checksums-Sha1:
 c89271de6aab39cdb5bbd37714da045999bda7fb 15404 
linux-signed-i386_5.18.2+1~bpo11+1.dsc
 970b0ea2e504188c31c5dd8a8b80af06cef7797b 3786020 
linux-signed-i386_5.18.2+1~bpo11+1.tar.xz
Checksums-Sha256:
 15026b12e53f8907e12d57911749d6bcd3bfcf30db8ac0e30b81232a48694b94 15404 
linux-signed-i386_5.18.2+1~bpo11+1.dsc
 f095a3f92bbd9a6f8d14ed25397f3fcf9becfec8afcecc2afa8aeb008b7f6a93 3786020 
linux-signed-i386_5.18.2+1~bpo11+1.tar.xz
Files:
 1387c5c135b8ddd84dde10533b69abdd 15404 kernel optional 
linux-signed-i386_5.18.2+1~bpo11+1.dsc
 8c62796ef39e0a9a48040824639de2d7 3786020 kernel optional 
linux-signed-i386_5.18.2+1~bpo11+1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmKrhVUACgkQi0FRiLdO
NzZYgA//YAhaQJImIpUR564+F38GAWCF+O7MMuyBEckR1DZYbgw3uq4I5BLeamXf
2qnJbX+sPOVxWZT5pNy8PT9gPn7p7U3BaqmQDR3x1aLq/dZ3HAIRR0Jv5P4oiE2r
+Es9Mgei9ZaNQBH8Zh3WB9ziXH/tf5KPs1X+utBQ3bWOF9Ll6+h7AsME8vUIwnzc
fJIK0Cu9P6NpckvEQkSHcyCv1MCCckwTaCT0SAFwBM2nwnd28tG2xUcxW9q00N9i
W0meucHKWFxP9dUiVabGNPwrfesYYLYx4zV1H4lWxlKUDyUH2xh+gHgvjLvXo1xu
hSS33XnSoxndDRx1bZKjVZ4CckuDPQPTpR0Y6M+EVdOOEK0AipIEg+FR0NUQVYAs
0NkO+euT+RtG4Nyjx9IAYzSZT/b9KB7k8ScxfLqp9X+bz18lBgIWdV5Kevta6alu
n/BzcUQf9I2eR9j/jd5GPs8WokolhRfreAjB+m/VEFW2/sATLtTr9Q+dyYbniACL
hh48xVBDq4ATT8wPF3niMoGKVSCce/pbyyzZuf1nbLgdyY77wZZa7pH8kxVPwKUK
WN8nRS8bfyEmtgPicm0HEOLueMGElrKOruTxkvNle1NAohHxgRtdQXI+fLLjaA8t
O3JiiQFikv9qp4I3+CCZTbYgrr+ZiBr4lN+b6Yl7WbLc5zS6Eps=
=7KIG
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processed: reassign 1013211 to src:linux, reassign 1012797 to iptables, reassign 548074 to src:log4cxx ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1013211 src:linux
Bug #1013211 [kernel] System freeze followed by kernel panic or blank screen
Warning: Unknown package 'kernel'
Bug reassigned from package 'kernel' to 'src:linux'.
No longer marked as found in versions 5.16.0-0.bpo.4-amd64.
Ignoring request to alter fixed versions of bug #1013211 to the same values 
previously set
> reassign 1012797 iptables 1.8.2-4
Bug #1012797 [iptables-1.8.2-4] iptables-1.8.2-4: Segmentation fault caused by 
iptables with no matching rules.
Warning: Unknown package 'iptables-1.8.2-4'
Bug reassigned from package 'iptables-1.8.2-4' to 'iptables'.
Ignoring request to alter found versions of bug #1012797 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1012797 to the same values 
previously set
Bug #1012797 [iptables] iptables-1.8.2-4: Segmentation fault caused by iptables 
with no matching rules.
Marked as found in versions iptables/1.8.2-4.
> reassign 548074 src:log4cxx 0.10.0-1
Bug #548074 {Done: Tobias Frost } [liblog4cxx12] [liblog4cxx] 
Inproper signal handling for spawned threads
Warning: Unknown package 'liblog4cxx12'
Bug reassigned from package 'liblog4cxx12' to 'src:log4cxx'.
Ignoring request to alter found versions of bug #548074 to the same values 
previously set
No longer marked as fixed in versions log4cxx/0.13.0-1.
Bug #548074 {Done: Tobias Frost } [src:log4cxx] [liblog4cxx] 
Inproper signal handling for spawned threads
Marked as found in versions log4cxx/0.10.0-1.
> fixed 548074 0.13.0-1
Bug #548074 {Done: Tobias Frost } [src:log4cxx] [liblog4cxx] 
Inproper signal handling for spawned threads
Marked as fixed in versions log4cxx/0.13.0-1.
> tags 981224 + experimental
Bug #981224 [src:ruby-uglifier] ruby-uglifier: FTBFS: tests fail: 
uglifier_spec.rb:383, uglifier_spec.rb:751
Added tag(s) experimental.
> found 1013218 3.7.2-3
Bug #1013218 [ruby-sprockets] rails: ftbfs SyntaxError: Unexpected token 
'export'
Marked as found in versions ruby-sprockets/3.7.2-3.
> tags 1012774 - sid bookworm
Bug #1012774 {Done: Paul Gevers } [src:git] src:git: fails 
to migrate to testing for too long: piuparts reports issue
Removed tag(s) bookworm and sid.
> notfound 1004701 1.4-1.2
Bug #1004701 {Done: Bastian Germann } [src:ima-evm-utils] 
ima-evm-utils: Backport for bullseye
No longer marked as found in versions ima-evm-utils/1.4-1.2.
> fixed 1004701 1.4-1.2
Bug #1004701 {Done: Bastian Germann } [src:ima-evm-utils] 
ima-evm-utils: Backport for bullseye
Marked as fixed in versions ima-evm-utils/1.4-1.2.
> reassign 1010888 node-dateformat 5.0.3-1
Bug #1010888 {Done: Pirate Praveen } [grunt] grunt: 
autopkgtest failure with node-dateformat 5.0 in experimental - change the 
require of dateformat.js to a dynamic import() which is available in all 
CommonJS modules
Bug reassigned from package 'grunt' to 'node-dateformat'.
No longer marked as found in versions grunt/1.5.2-2.
No longer marked as fixed in versions node-dateformat/5.0.3-2.
Bug #1010888 {Done: Pirate Praveen } [node-dateformat] 
grunt: autopkgtest failure with node-dateformat 5.0 in experimental - change 
the require of dateformat.js to a dynamic import() which is available in all 
CommonJS modules
There is no source info for the package 'node-dateformat' at version '5.0.3-1' 
with architecture ''
Unable to make a source version for version '5.0.3-1'
Marked as found in versions 5.0.3-1.
> fixed 1010888 5.0.3-2
Bug #1010888 {Done: Pirate Praveen } [node-dateformat] 
grunt: autopkgtest failure with node-dateformat 5.0 in experimental - change 
the require of dateformat.js to a dynamic import() which is available in all 
CommonJS modules
There is no source info for the package 'node-dateformat' at version '5.0.3-2' 
with architecture ''
Unable to make a source version for version '5.0.3-2'
Marked as fixed in versions 5.0.3-2.
> affects 1010888 + src:grunt
Bug #1010888 {Done: Pirate Praveen } [node-dateformat] 
grunt: autopkgtest failure with node-dateformat 5.0 in experimental - change 
the require of dateformat.js to a dynamic import() which is available in all 
CommonJS modules
Added indication that 1010888 affects src:grunt
> reassign 984794 calamares-settings-debian
Bug #984794 {Done: Jonathan Carter } [calamares] calamares: 
use eatmydata to speed up last installation step (60remove-live-packages)
Bug reassigned from package 'calamares' to 'calamares-settings-debian'.
No longer marked as found in versions calamares/3.2.36-1.
No longer marked as fixed in versions calamares-settings-debian/12.0.1-1.
> fixed 984794 12.0.1-1
Bug #984794 {Done: Jonathan Carter } 
[calamares-settings-debian] calamares: use eatmydata to speed up last 
installation step (60remove-live-packages)
Marked as fixed in versions calamares-settings-debian/12.0.1-1.
> affects 984794 + src:calamares
Bug #984794 {Done: Jonathan Carter } 
[calamares-settings-debian] calamares: use eatmydata to speed up last 
installation step (60remove-live-packages)
Added 

linux_5.10.120-1~bpo10+1_source.changes ACCEPTED into buster-backports->backports-policy, buster-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 13 Jun 2022 22:46:49 +0200
Source: linux
Architecture: source
Version: 5.10.120-1~bpo10+1
Distribution: buster-backports
Urgency: high
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 1006346 1007799 1008299
Changes:
 linux (5.10.120-1~bpo10+1) buster-backports; urgency=high
 .
   * Rebuild for buster-backports:
 - Change ABI number to 0.bpo.15
 .
 linux (5.10.120-1) bullseye-security; urgency=high
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.114
 - USB: quirks: add a Realtek card reader
 - USB: quirks: add STRING quirk for VCOM device
 - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS
 - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader
 - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB
 - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions
 - xhci: Enable runtime PM on second Alderlake controller
 - xhci: stop polling roothubs after shutdown
 - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms
 - iio: dac: ad5592r: Fix the missing return value.
 - iio: dac: ad5446: Fix read_raw not returning set value
 - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on()
 - iio: imu: inv_icm42600: Fix I2C init possible nack
 - usb: misc: fix improper handling of refcount in uss720_probe()
 - [arm64,x86] usb: typec: ucsi: Fix reuse of completion structure
 - [arm64,x86] usb: typec: ucsi: Fix role swapping
 - usb: gadget: uvc: Fix crash when encoding data for usb request
 - usb: gadget: configfs: clear deactivation flag in
   configfs_composite_unbind()
 - [arm64,armhf] usb: dwc3: Try usb-role-switch first in dwc3_drd_init
 - [arm64,armhf] usb: dwc3: core: Fix tx/rx threshold settings
 - [arm64,armhf] usb: dwc3: core: Only handle soft-reset in DCTL
 - [arm64,armhf] usb: dwc3: gadget: Return proper request status
 - [arm*] usb: phy: generic: Get the vbus supply
 - [arm64,armhf] serial: imx: fix overrun interrupts in DMA mode
 - serial: 8250: Also set sticky MCR bits in console restoration
 - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device
 - [arm64,armhf] arch_topology: Do not set llc_sibling if llc_id is invalid
 - hex2bin: make the function hex_to_bin constant-time
 - hex2bin: fix access beyond string end
 - iocost: don't reset the inuse weight of under-weighted debtors
 - video: fbdev: udlfb: properly check endpoint type
 - iio:imu:bmi160: disable regulator in error path
 - USB: Fix xhci event ring dequeue pointer ERDP update issue
 - [armhf] phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe
 - [armhf] phy: samsung: exynos5250-sata: fix missing device put in probe
   error paths
 - [armhf] OMAP2+: Fix refcount leak in omap_gic_of_init
 - [armhf] bus: ti-sysc: Make omap3 gpt12 quirk handling SoC specific
 - [armhf] phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks
 - [armhf] dts: am3517-evm: Fix misc pinmuxing
 - [armhf] dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35
 - ipvs: correctly print the memory size of ip_vs_conn_tab
 - [armhf] pinctrl: stm32: Do not call stm32_gpio_get() for edge triggered
   IRQs in EOI
 - [arm64,armhf] net: dsa: Add missing of_node_put() in
   dsa_port_link_register_of
 - netfilter: nft_set_rbtree: overlap detection with element re-addition
   after deletion
 - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt
   hook
 - [arm64,armhf] pinctrl: rockchip: fix RK3308 pinmux bits
 - tcp: md5: incorrect tcp_header_len for incoming connections
 - [armhf] pinctrl: stm32: Keep pinctrl block clock enabled when LEVEL IRQ
   requested
 - tcp: ensure to use the most recently sent skb when filling the rate 
sample
 - wireguard: device: check for metadata_dst with skb_valid_dst()
 - sctp: check asoc strreset_chunk in sctp_generate_reconf_event
 - [arm64] dts: imx8mn-ddr4-evk: Describe the 32.768 kHz PMIC clock
 - [arm64] net: hns3: modify the return code of 
hclge_get_ring_chain_from_mbx
 - [arm64] net: hns3: add validity check for message data length
 - [arm64] net: hns3: add return value for mailbox handling in PF
 - net/smc: sync err code when tcp connection was refused
 - ip_gre: Make o_seqno start from 0 in native mode
 - ip6_gre: Make o_seqno start from 0 in native mode
 - ip_gre, ip6_gre: Fix race condition on o_seqno in collect_md mode
 - tcp: fix potential xmit stalls caused by TCP_NOTSENT_LOWAT
 - tcp: make sure treq->af_specific is initialized
 - [arm64,armhf] bus: sunxi-rsb: Fix the return value of
   sunxi_rsb_device_create()
 - [arm64,armhf] clk: sunxi: sun9i-mmc: check return value 

linux-signed-amd64_5.18.2+1~bpo11+1_source.changes ACCEPTED into bullseye-backports, bullseye-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jun 2022 13:38:17 +0200
Source: linux-signed-amd64
Architecture: source
Version: 5.18.2+1~bpo11+1
Distribution: bullseye-backports
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Changes:
 linux-signed-amd64 (5.18.2+1~bpo11+1) bullseye-backports; urgency=medium
 .
   * Sign kernel from linux 5.18.2-1~bpo11+1
 .
   * Rebuild for bullseye-backports:
 - Change ABI number to 0.bpo.1
Checksums-Sha1:
 c6077865815ca89fd68a606bd88a89a0db5167f4 9227 
linux-signed-amd64_5.18.2+1~bpo11+1.dsc
 42f841330c5acbd524dedf3be75a9168403edfd5 2866328 
linux-signed-amd64_5.18.2+1~bpo11+1.tar.xz
Checksums-Sha256:
 aa27aca40bb3fcebf2c0591f1c91b5ae3e5070fcd368e48d3df940ac43f0fa76 9227 
linux-signed-amd64_5.18.2+1~bpo11+1.dsc
 5a1c356baf607ea76254dd2865653af60f29b7a34d6b569f6c662513751061d9 2866328 
linux-signed-amd64_5.18.2+1~bpo11+1.tar.xz
Files:
 6f2a5e5453a23f030a5693163174f502 9227 kernel optional 
linux-signed-amd64_5.18.2+1~bpo11+1.dsc
 3ec159dda80ef454b1690d0be1b65017 2866328 kernel optional 
linux-signed-amd64_5.18.2+1~bpo11+1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmKrQTIACgkQi0FRiLdO
NzaOsRAAhywgi4bNmV6A0/kzCMIGOWBM0yu6x3ZTr9d+74pZKn6DnpPjNhngaAzL
CS0McJvArInW7Zmr0qkLxoPQd2lhtrPh/700rqHrHbvbTjCT2EicQiYlXwNgcCG4
5i+YJMjQqm7I/1GeXkoXaO73Ux8pqta22vvzh9q7RvvcMRlHl74TLmgSmthLbqQs
ibvluXBqQOt/dlAglbvWc3e0yofl8lGHVcGkaFMUcxvsDx9zDtWzu+XByBz1uhfZ
e1KLXwjrmvSNybNp1qAEQqokSFpmACQRknqPLZOwduWDY/gIU+TW5mnLvzeKDYzF
LE5bHGUjRPG6YVg4J0j8956OYQ/o3x6WLEgWg/K5mnWplTEzVU588EAlhw1qRiX6
3oi2JJIbNpY0Y3iWovBboIT1uVkwKmWdDWhXdOQx63AFA5xrmjk8Cn95umunhfUs
2tlC4amFbcNdMg6cKVyMAINACFxMAtBzebaHSwAKCW2lUK1RfqkQldXktLnvyBGs
tlfO1qyo13TK6I5VDYO5hDztTxSaysHuWW3Sg5rtaFkVsqpM1KI+caoGN7x7YFJ2
FhxDEXwW5D4EgaHEO1xo5V8huvc0JTmJla190wmkH9+xHnsxGtA7ZZZF3u5xAdEl
nedhaPKwHUdaSaKKv+Cr4SVF50sm1YL+yv7tKEJe0MZzDlCQ/98=
=XTYF
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

linux-signed-arm64_5.18.2+1~bpo11+1_source.changes ACCEPTED into bullseye-backports, bullseye-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Jun 2022 13:38:17 +0200
Source: linux-signed-arm64
Architecture: source
Version: 5.18.2+1~bpo11+1
Distribution: bullseye-backports
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Changes:
 linux-signed-arm64 (5.18.2+1~bpo11+1) bullseye-backports; urgency=medium
 .
   * Sign kernel from linux 5.18.2-1~bpo11+1
 .
   * Rebuild for bullseye-backports:
 - Change ABI number to 0.bpo.1
Checksums-Sha1:
 c1af76afea29d3d52396562236824c379fe7b0b3 7848 
linux-signed-arm64_5.18.2+1~bpo11+1.dsc
 c172d6ee3e7f4cccf6da04465a3a150bdaa9df82 2603428 
linux-signed-arm64_5.18.2+1~bpo11+1.tar.xz
Checksums-Sha256:
 1edc7ebd70fdbcc84ffcb1d479ee6631715165698508720fd7800b363dd6c4e5 7848 
linux-signed-arm64_5.18.2+1~bpo11+1.dsc
 481bcc52a13659884cfa53460cd0505bad8169c862018617b43b4bf44bb771a3 2603428 
linux-signed-arm64_5.18.2+1~bpo11+1.tar.xz
Files:
 b52bac0fefbbe145048a07927f53d62e 7848 kernel optional 
linux-signed-arm64_5.18.2+1~bpo11+1.dsc
 35877087558f48f04b699e689302d9b3 2603428 kernel optional 
linux-signed-arm64_5.18.2+1~bpo11+1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmKrXEkACgkQi0FRiLdO
NzY/iBAAlE/Aif6/XcNRCkaFmUeiGNqHqcKtC8ubdKXpdWqUjLncvW8r8dsFkvRN
6lAdhkjq8u5cNlgnmNbVavLPfzMP7BmEwqWNJIli5SzClWkJJ714owscIKjht/dN
LehntDY6nFC8oMAg3Fxc6znc7wkPm7k8+nkUqOXhQU2umAuqIIexohu/MTqKyaGd
DBWzDD10wm4L/eSp0azgMX73r2ZxxhI50TThbjZgKvF9xbxpFkIPe1PdBMm+zGbE
vZPHDPSOKkLAVTg7SlgvFVy6sy54xOF4HvBxyXrcBwSNZGoRTYSqdoN6aMbcnEyQ
HsD3DxdI0WZbze29QZqVRmGLXt6x4EDsSy4qdvAB8Es2XF9ZoFDT9W1jDqtRMkrT
6Nx16UMvYwAyBFsBAieiLUateIGQ2jaAVlXEtq/FI0k+TCfz/8XdPiajy1Df7e4d
mJIyIL1UWuJbdY4KRnsVobm7y27YYc2m4d4KXGe0e8wXPZ9wr6ROxuaAPogHzuDC
8p+U8VtW1Sjljnm3S1u3t4yesE2snXQowurOGb6A+ZjqTGuV9pFEA+8aGww3cwEQ
/4dGkgqH6Xp2hti7C/9/n1LABWOV/FFW6O1wU1jsGcrs4I7Mc9xn4PKThyhXz28O
4UtYSBAcmmI/ol1Ye7eeLREtBl+a/vKFHevcw1Y6TBuSbc2pGSs=
=Lg8N
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#1012881: linux: ti soc cpufreq not working

[Diederik de Haas]

Always send your replies to the bug report!

[This is therefor just a forward to that bug report]

On Monday, 20 June 2022 10:09:45 CEST Yu-Tung Chang wrote:
> https://lore.kernel.org/linux-arm-kernel/5143369...@ti.com/T/
> https://www.spinics.net/lists/linux-omap/msg138794.html
> 
> Read the link above, ARM_OMAP2PLUS_CPUFREQ is not available for DT
> Boot Systems and has been deprecated
> 
> Yu-Tung Chang  于2022年6月20日周一 16:03写道：
> 
> > https://lore.kernel.org/linux-arm-kernel/5143369...@ti.com/T/
> > 
> > Yu-Tung Chang  于2022年6月20日周一 16:02写道：
> > 
> > > I am doing further testing, It is now certain that
> > > ARM_OMAP2PLUS_CPUFREQ is not set in
> > > arch/arm/configs/omap2plus_defconfig.
> > > 
> > > Diederik de Haas  于2022年6月16日周四 22:50写道：
> > > 
> > > > Control: tag -1 moreinfo
> > > > 
> > > > On Thursday, 16 June 2022 12:16:46 CEST Yu-Tung Chang wrote:
> > > > > Package: linux-image-armmp
> > > > > Version: 5.18.0-1
> > > > > 
> > > > > enable omap2plus_cpufreq causes ti_cpufreq to not work, and
> > > > > omap2plus_cpufreq is no longer used in linux.
> > > > 
> > > > Can you explain ('more') what the actual issue is?
> > > > 
> > > > I went looking in (upstream)'s code and what I could find was this:
> > > > 
> > > > ~/dev/kernel.org/linux$ grep -A4 "config ARM_OMAP2PLUS_CPUFREQ"
> > > > drivers/
> > > > cpufreq/Kconfig.arm
> > > > config ARM_OMAP2PLUS_CPUFREQ
> > > > 
> > > > bool "TI OMAP2+"
> > > > depends on ARCH_OMAP2PLUS
> > > > default ARCH_OMAP2PLUS
> > > > 
> > > > ~/dev/kernel.org/linux$ grep -A11 "config ARM_TI_CPUFREQ"
> > > > drivers/cpufreq/
> > > > Kconfig.arm
> > > > config ARM_TI_CPUFREQ
> > > > 
> > > > bool "Texas Instruments CPUFreq support"
> > > > depends on ARCH_OMAP2PLUS
> > > > default ARCH_OMAP2PLUS
> > > > help
> > > > 
> > > >   This driver enables valid OPPs on the running platform based
> > > >   on
> > > >   values contained within the SoC in use. Enable this in order
> > > >   to
> > > >   use the cpufreq-dt driver on all Texas Instruments platforms
> > > >   that
> > > >   provide dt based operating-points-v2 tables with
> > > >   opp-supported-hw
> > > >   data provided. Required for cpufreq support on AM335x,
> > > >   AM437x,
> > > >   DRA7x, and AM57x platforms.
> > > > 
> > > > I interpreted your bug report as they would be mutually exclusive, but
> > > > that's far from what _I_ understand of the above Kconfig options.
> > > > I can ofc be wrong.



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

Bug#1013255: linux: freescale caam hw crypto drivers not enabled

[Yu-Tung Chang]

Package: linux-image-armmp
Version: 5.18.0-1

It can be found in almost all Freescale ARMv7 SoCs, so it should be enabled.

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Daniel Lewart]

Ben,

> I wrote a script to check for short signatures (and other unexpected
> things) in detached signature files:
> https://salsa.debian.org/kernel-team/kernel-team/-/blob/master/scripts/benh/check-sig-params

Thank you for your excellent detective work!

I tried running your script, but it generates an error (see below).
What am I doing wrong?

Thank you again!
Dan
Urbana, Illinois
---
$ dpkg-query -f='${Package} ${Version}\n' -W python3 python3-asn1crypto
python3 3.9.2-3
python3-asn1crypto 1.4.0-1

$ check-sig-params /lib/modules/5.10.0-15-amd64/kernel/net/netfilter/xt_l2tp.ko
/lib/modules/5.10.0-15-amd64/kernel/net/netfilter/xt_l2tp.ko: Error
parsing asn1crypto.cms.ContentInfo - class should have been universal,
but application was found)

###

Bug#1012100: marked as done (linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and a kernel thread goes wild on Intel Xeon X3430)

[Debian Bug Tracking System]

Your message dated Mon, 20 Jun 2022 18:39:31 +0200
with message-id <4423757.LvFx2qVVIh@bagend>
and subject line Re: Bug#1012100: linux-image-5.17-1: KVM LIBVIRT fails to 
start, slow disk access, and a kernel thread goes wild on Intel Xeon X3430
has caused the Debian Bug report #1012100,
regarding linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and 
a kernel thread goes wild on Intel Xeon X3430
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.)


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

Dear Maintainer,

   * What led up to the situation?
 Upgrading my Debian/testing installation with apt -u dist-upgrade
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 apt -u dist-upgrade
   * What was the outcome of this action?
 The new 5.17-1 kernel has several issues
   * What outcome did you expect instead?
 Working Linux kernel with no issues

currently in Debian/testing, the new 5.17 kernel has several issues.

My LIBVIRT KVM VM instances fail to load with this new kernel.

The disk access is slow in some programs, as for example showing the KVM VM
instances in virt-manager fails due to broken disk access.

After some hours of uptime, a kernel thread goes wild and uses 100% of the CPU.

I am also running this new kernel (5.17) on a Debian/testing VMWARE ESXI VPS
instance, at my providers place, where everything works fine. Thus this most
probably an issue with my used hardware.

My hardware is the following:

adrian@g6 ~ % inxi -F
System:
  Host: g6.lan.dac Kernel: 5.16.0-6-amd64 arch: x86_64 bits: 64
Desktop: Enlightenment v: 0.25.3 Distro: Debian GNU/Linux bookworm/sid
Machine:
  Type: Desktop System: HP product: ProLiant ML110 G6 v: N/A
serial: 
  Mobo: Wistron model: ProLiant ML110 G6 serial: 
BIOS: HP v: O27 date: 08/26/2011
CPU:
  Info: quad core model: Intel Xeon X3430 bits: 64 type: MCP cache:
L2: 1024 KiB
  Speed (MHz): avg: 1635 min/max: 1197/2394 cores: 1: 1692 2: 1617 3: 1649
4: 1585
Graphics:
  Device-1: AMD Oland GL [FirePro W2100] driver: radeon v: kernel
  Display: x11 server: X.Org v: 1.21.1.3 with: Xwayland v: 22.1.0 driver:
X: loaded: radeon gpu: radeon resolution: 1920x1200
  OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.16.0-6-amd64 LLVM 13.0.1)
v: 4.5 Mesa 21.3.8
Audio:
  Device-1: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000
  Series]
driver: snd_hda_intel
  Device-2: ASUSTek Xonar U1 Audio Station type: USB
driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.16.0-6-amd64 running: yes
  Sound Server-2: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Broadcom NetXtreme BCM5723 Gigabit Ethernet PCIe driver: tg3
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 64:31:50:d3:c0:f8
  IF-ID-1: br0 state: up speed: 1000 Mbps duplex: unknown
mac: fe:40:ab:83:94:4a
  IF-ID-2: vnet0 state: unknown speed: 10 Mbps duplex: full
mac: fe:54:00:c2:24:94
  IF-ID-3: vnet1 state: unknown speed: 10 Mbps duplex: full
mac: fe:54:00:bf:35:8b
  IF-ID-4: vnet2 state: unknown speed: 10 Mbps duplex: full
mac: fe:54:00:25:b0:8b
  IF-ID-5: vnet3 state: unknown speed: 10 Mbps duplex: full
mac: fe:54:00:4a:c8:69
Drives:
  Local Storage: total: 11.79 TiB used: 5.87 TiB (49.8%)
  ID-1: /dev/sda vendor: Toshiba model: Q300 size: 447.13 GiB
  ID-2: /dev/sdb vendor: A-Data model: SP550 size: 447.13 GiB
  ID-3: /dev/sdc vendor: Toshiba model: HDWE140 size: 3.64 TiB
  ID-4: /dev/sdd vendor: Toshiba model: MG06ACA800E size: 7.28 TiB
Partition:
  ID-1: / size: 437.53 GiB used: 91.98 GiB (21.0%) fs: ext4 dev: /dev/sda3
  ID-2: /boot size: 1.2 GiB used: 272.2 MiB (22.2%) fs: ext4 dev: /dev/sda1
  ID-3: /home size: 3.64 TiB used: 1.76 TiB (48.4%) fs: btrfs
dev: /dev/sdc1
Swap:
  ID-1: swap-1 type: partition size: 46.66 GiB used: 139.5 MiB (0.3%)
dev: /dev/sdb2
Sensors:
  Permissions: Unable to run ipmi sensors. Root privileges required.
  System Temperatures: cpu: 49.0 C mobo: N/A gpu: radeon temp: 39.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 410 Uptime: 1h 1m Memory: 15.62 GiB used: 9.43 GiB (60.4%)
  Shell: Zsh inxi: 3.3.16

Thank you very much, for your kind attention.

Sincerely,

Adrian Kiess


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: HP
product_name: ProLiant ML110 G6
product_version: 
chassis_vendor: HP
chassis_version: N/A
bios_vendor: HP

Bug#1012881: linux: ti soc cpufreq not working

[Yu-Tung Chang]

https://lore.kernel.org/linux-arm-kernel/5143369...@ti.com/T/
https://www.spinics.net/lists/linux-omap/msg138794.html

Read the link above, ARM_OMAP2PLUS_CPUFREQ is not available for DT
Boot Systems and has been deprecated

Diederik de Haas  于2022年6月20日周一 19:00写道：
>
> Always send your replies to the bug report!
>
> [This is therefor just a forward to that bug report]
>
> On Monday, 20 June 2022 10:09:45 CEST Yu-Tung Chang wrote:
> > https://lore.kernel.org/linux-arm-kernel/5143369...@ti.com/T/
> > https://www.spinics.net/lists/linux-omap/msg138794.html
> >
> > Read the link above, ARM_OMAP2PLUS_CPUFREQ is not available for DT
> > Boot Systems and has been deprecated
> >
> > Yu-Tung Chang  于2022年6月20日周一 16:03写道：
> >
> > > https://lore.kernel.org/linux-arm-kernel/5143369...@ti.com/T/
> > >
> > > Yu-Tung Chang  于2022年6月20日周一 16:02写道：
> > >
> > > > I am doing further testing, It is now certain that
> > > > ARM_OMAP2PLUS_CPUFREQ is not set in
> > > > arch/arm/configs/omap2plus_defconfig.
> > > >
> > > > Diederik de Haas  于2022年6月16日周四 22:50写道：
> > > >
> > > > > Control: tag -1 moreinfo
> > > > >
> > > > > On Thursday, 16 June 2022 12:16:46 CEST Yu-Tung Chang wrote:
> > > > > > Package: linux-image-armmp
> > > > > > Version: 5.18.0-1
> > > > > >
> > > > > > enable omap2plus_cpufreq causes ti_cpufreq to not work, and
> > > > > > omap2plus_cpufreq is no longer used in linux.
> > > > >
> > > > > Can you explain ('more') what the actual issue is?
> > > > >
> > > > > I went looking in (upstream)'s code and what I could find was this:
> > > > >
> > > > > ~/dev/kernel.org/linux$ grep -A4 "config ARM_OMAP2PLUS_CPUFREQ"
> > > > > drivers/
> > > > > cpufreq/Kconfig.arm
> > > > > config ARM_OMAP2PLUS_CPUFREQ
> > > > >
> > > > > bool "TI OMAP2+"
> > > > > depends on ARCH_OMAP2PLUS
> > > > > default ARCH_OMAP2PLUS
> > > > >
> > > > > ~/dev/kernel.org/linux$ grep -A11 "config ARM_TI_CPUFREQ"
> > > > > drivers/cpufreq/
> > > > > Kconfig.arm
> > > > > config ARM_TI_CPUFREQ
> > > > >
> > > > > bool "Texas Instruments CPUFreq support"
> > > > > depends on ARCH_OMAP2PLUS
> > > > > default ARCH_OMAP2PLUS
> > > > > help
> > > > >
> > > > >   This driver enables valid OPPs on the running platform based
> > > > >   on
> > > > >   values contained within the SoC in use. Enable this in order
> > > > >   to
> > > > >   use the cpufreq-dt driver on all Texas Instruments platforms
> > > > >   that
> > > > >   provide dt based operating-points-v2 tables with
> > > > >   opp-supported-hw
> > > > >   data provided. Required for cpufreq support on AM335x,
> > > > >   AM437x,
> > > > >   DRA7x, and AM57x platforms.
> > > > >
> > > > > I interpreted your bug report as they would be mutually exclusive, but
> > > > > that's far from what _I_ understand of the above Kconfig options.
> > > > > I can ofc be wrong.
>

Bug#1012100: linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and a kernel thread goes wild on Intel Xeon X3430

[Adrian Kieß]

Dear Diederik,

the new kernel:

root@g6 /opt # uname -a
Linux g6.lan.dac 5.18.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.2-1
(2022-06-06) x86_64 GNU/Linux

in Debian/testing works again in the way, that LIBVIRT KVM works again!

I most probably found the reason for the slow disk access on my machine:

Please see this new bug report:

Debian Bug report logs - #1013260
coreutils: /bin/chown very slow in conjunction with storebackup

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013260

Thank you very much for your answer!

Sincerely,

Adrian Kieß

On Mon, 30 May 2022 14:29:29 +0200
Diederik de Haas  wrote:

> Hi Adrian,
> 
> On Monday, 30 May 2022 13:14:26 CEST Adrian Kieß wrote:
> > yes, it works with the kernel 5.16.0-6, but disk access is still slow.
> 
> Ok, but that issue was also happening before 5.17 and is not a new problem.
> Do you have a(n old) kernel (still) installed which does NOT have this slow 
> disk access issue? If it happens on all kernel versions, then a hardware 
> issue 
> becomes much more likely to be the real culprit.
> 
> > For example, virt-manager/viewer sometimes needs a minute to connect to
> > the KVM instances on localhost. But not all applications are this slow;
> > for example the E-Mail client Sylpheed starts as fast as before and is
> > operating at fast speed.
> 
> In your initial report I noticed the following:
> > Network:
> >   Device-1: Broadcom NetXtreme BCM5723 Gigabit Ethernet PCIe driver: tg3
> >   IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 64:31:50:d3:c0:f8
> >   IF-ID-1: br0 state: up speed: 1000 Mbps duplex: unknown
> > mac: fe:40:ab:83:94:4a
> >   IF-ID-2: vnet0 state: unknown speed: 10 Mbps duplex: full
> > mac: fe:54:00:c2:24:94
> >   IF-ID-3: vnet1 state: unknown speed: 10 Mbps duplex: full
> > mac: fe:54:00:bf:35:8b
> >   IF-ID-4: vnet2 state: unknown speed: 10 Mbps duplex: full
> > mac: fe:54:00:25:b0:8b
> >   IF-ID-5: vnet3 state: unknown speed: 10 Mbps duplex: full
> > mac: fe:54:00:4a:c8:69
> 
> Is it normal/expected that IF-ID-[2-5] have "unknown speed: 10 Mbps duplex" ?
> If not, that may be worth looking into.
> 
> > I assume there is also another bug now in the system, not only due to
> > the new kernel. There is also another bug in GDM3, which I also
> > reported: Loading GDM3 after bootup and logging in as normal user is
> > also very, very slow.
> 
> Which sounds like the moment lots of files/data is read from disk to 
> initialize 
> the session, which does point to a disk issue.
> But if the initial boot isn't terribly slow as well, that would be odd.
> Or is /home mounted from another disk?
> 
> > As you suggested, I installed the kernel 5.17.11 from Debian/unstable
> > and booted into this kernel.
> > 
> > virt-manager and my KVM VM instances do work again, but one VM instance
> > failed to load after bootup. I restarted the VM instance, and it is now
> > also operating fine.
> 
> Good, that sounds like major progress :) It looks to me that the KVM problem 
> is now (mostly?) fixed.
> 
> > When opening the virt-viewer instance from virt-manager, connecting to
> > the VM is still very slow with kernel 5.17.11. Something must be wrong
> > I/O wise.
> 
> That still/all points to a disk problem
> 
> > I attached the dmesg output, you requested, as TXT file to this E-mail.
> 
> Couple of things I noticed in the dmesg output:
> 1) "[Firmware Warn]: HEST: Duplicated hardware error source ID: 9."
> https://lkml.org/lkml/2011/6/27/370 seems relevant for that as it provided 
> the 
> better warning, but it also points out that it *is* considered a firmware bug.
> I noticed your BIOS is from 2011. Is there a newer version available? If so, 
> it may be worth trying that out to see if that improves things.
> 
> 2) Several ACPI related warnings.
> No idea if or what should be done with that.
> 
> 3) "kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using 
> workaround" and "kvm: KVM_SET_TSS_ADDR need to be called before entering vcpu"
> That looks like there are still KVM related issues (just not or less fatal)
> There have been other bug reports related to KVM.
> 
> 4) BUG: kernel NULL pointer dereference, address: 000b
> That's never good. The dmesg output also contains a Call Trace and several 
> mentions of KVM, so it looks like there's still something not right about it.
> I have no idea how to interpret those Call (or Stack) Traces, so hopefully 
> someone else chimes in who is familiar with that.
> 
> Cheers,
>   Diederik


-- 
With many greetings from Leipzig, Germany.
Adrian Immanuel Kieß 

Gothaer Straße 34
D-04155 Leipzig

 — < adr...@kiess.onl >

--SYSTEM--
echo "Your fortune cookie: " && /usr/games/fortune -c -s de
> (letzteworte) % Letzte Worte eines Fahrlehrers: "Die Ampel ist rot."

echo "g6.lan.dac uptime: " && /usr/bin/uptime
> 17:17:09 up 2 days, 1:21, 12 users, load average: 1,09, 0,90, 0,85

Processed: Reassign #1013255 to src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1013255 src:linux
Bug #1013255 [linux-image-armmp] linux: freescale caam hw crypto drivers not 
enabled
Bug reassigned from package 'linux-image-armmp' to 'src:linux'.
No longer marked as found in versions 5.18.0-1.
Ignoring request to alter fixed versions of bug #1013255 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ben Hutchings]

On Mon, 2022-06-20 at 04:38 -0500, Daniel Lewart wrote:
> Ben,
> 
> > I wrote a script to check for short signatures (and other unexpected
> > things) in detached signature files:
> > https://salsa.debian.org/kernel-team/kernel-team/-/blob/master/scripts/benh/check-sig-params
> 
> Thank you for your excellent detective work!
> 
> I tried running your script, but it generates an error (see below).
> What am I doing wrong?
[...]

I don't know, but I'm running it on unstable.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today,
ignorance or apathy?
A.  I don't know and I couldn't care less.


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

Processed: Setting found version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 970639 linux/5.8.7-1
Bug #970639 [src:linux] linux: Enable zswap support via CONFIG_ZSWAP_DEFAULT_ON 
?
Marked as found in versions linux/5.8.7-1.
>
End of message, stopping processing here.

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

Bug#1011513: marked as done (config/Arm64: request enable CONFIG_ARM_PSCI_CPUIDLE)

[Debian Bug Tracking System]

Your message dated Mon, 20 Jun 2022 20:54:38 +0200
with message-id <21f4844bdaf758e97b5193f3c252a9b6f8e39196.ca...@decadent.org.uk>
and subject line Re: Bug#1011513: enable CONFIG_ARM_PSCI_CPUIDLE
has caused the Debian Bug report #1011513,
regarding config/Arm64: request enable CONFIG_ARM_PSCI_CPUIDLE
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.)


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


Hi,

many Arm64 SOCs support psci cpuidle driver.
thus request to enable: CONFIG_ARM_PSCI_CPUIDLE=y
--- End Message ---
--- Begin Message ---
Version: 5.18.2-1

On Mon, 2022-05-30 at 22:31 +0200, Diederik de Haas wrote:
> Control: tag -1 pending
> 
> On Tue, 24 May 2022 19:04:34 +0800 Zhang Ning  wrote:
> > this is the merge request:
> > https://salsa.debian.org/kernel-team/linux/-/merge_requests/479
> 
> As that MR has been merged (into master), I'm tagging it accordingly

This was fixed in the version above, but we forgot to mention this bug
in the changelog.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today,
ignorance or apathy?
A.  I don't know and I couldn't care less.


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

Processed: Setting fixed version as -done didn't do it ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1012100 linux/5.18.2-1
Bug #1012100 {Done: Diederik de Haas } [src:linux] 
linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and a kernel 
thread goes wild on Intel Xeon X3430
Marked as fixed in versions linux/5.18.2-1.
>
End of message, stopping processing here.

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

Processed: Re: Zswap Disabled By Default

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #970639 [src:linux] linux: Enable zswap support via CONFIG_ZSWAP_DEFAULT_ON 
?
Added tag(s) wontfix.

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

Bug#970639: Zswap Disabled By Default

[Ben Hutchings]

Control: tag -1 wontfix

On Tue, 06 Oct 2020 12:24:07 -0400 calumlikesapple...@gmail.com wrote:
> I figured I should ping this, since I don't know that it was properly
> shown to the debian-kernel mailing list.
> 
> > Interestingly it still contains the following note in documentation:
> 
> >   Zswap is a new feature as of v3.11 and interacts heavily with 
> >   memory reclaim.  This interaction has not been fully explored on 
> >   the large set of potential configurations and workloads that 
> >   exist.  For this reason, zswap is a work in progress and should be 
> >   considered experimental.
> 
> > Unless this is not anymore to be considered valid, then 
> > CONFIG_ZSWAP_DEFAULT_ON could be switched on (which should be
> > possible since 5.7-rc1).
> I saw that as well.  However, zswap has gone through a lot of changes
> since then: it is enabled by default on Arch at least, and possibly
> more distributions (I couldn't find the kernel config file for RedHat).

It's part of .  This option
is not enabled in any configuration there.

SUSE kernel configurations are part of
 and they don't enable it
either.

The latest Ubuntu kernel package
doesn't enable it either, though I understand that it's enabled for
some systems through the kernel command line.

> The feature is still maintained, and appears to be bug-free.  I'm
> having a hard time seeing the disadvantage of enabling it.  

"Bug-free", ho ho.

 has a benchmark whee zswap can improve
or worsen performance, depending on configuration.  Frustratingly, that
page doesn't show results for the default configuration (lzo compressor
and zbud allocator).

I'm sure it's a useful feature for some systems, but I think it needs
updated documentation and a more consistent performance benefit before
we could enable it by default.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today,
ignorance or apathy?
A.  I don't know and I couldn't care less.


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

Processed: reassign 825141 to src:linux, forcibly merging 1013249 825141, fixed 825141 in 4.6.1-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 825141 src:linux 4.5.3-2
Bug #825141 [linux] dasd_mod: module verification failed: signature and/or 
required key missing - tainting kernel
Bug reassigned from package 'linux' to 'src:linux'.
No longer marked as found in versions 4.5.3-2.
Ignoring request to alter fixed versions of bug #825141 to the same values 
previously set
Bug #825141 [src:linux] dasd_mod: module verification failed: signature and/or 
required key missing - tainting kernel
Marked as found in versions linux/4.5.3-2.
> forcemerge 1013249 825141
Bug #1013249 [src:linux] virtio_ring: module verification failed: signature 
and/or required key missing - tainting kernel
Bug #1013249 [src:linux] virtio_ring: module verification failed: signature 
and/or required key missing - tainting kernel
Marked as found in versions linux/4.5.3-2.
Bug #825141 [src:linux] dasd_mod: module verification failed: signature and/or 
required key missing - tainting kernel
Severity set to 'important' from 'minor'
Marked as found in versions linux/5.18.5-1.
Merged 825141 1013249
> fixed 825141 4.6.1-1
Bug #825141 [src:linux] dasd_mod: module verification failed: signature and/or 
required key missing - tainting kernel
Bug #1013249 [src:linux] virtio_ring: module verification failed: signature 
and/or required key missing - tainting kernel
Marked as fixed in versions linux/4.6.1-1.
Marked as fixed in versions linux/4.6.1-1.
> found 825141 5.4-1~exp1
Bug #825141 [src:linux] dasd_mod: module verification failed: signature and/or 
required key missing - tainting kernel
Bug #1013249 [src:linux] virtio_ring: module verification failed: signature 
and/or required key missing - tainting kernel
Marked as found in versions linux/5.4-1~exp1.
Marked as found in versions linux/5.4-1~exp1.
> thanks
Stopping processing here.

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

Bug#1013180: Undelivered Mail Returned to Sender

[Ben Hutchings]

On Sat, 2022-06-18 at 17:43 +0200, Diederik de Haas wrote:
> On zaterdag 18 juni 2022 17:13:33 CEST you wrote:
> > I'm sorry to have to inform you that your message could not
> > be delivered to one or more recipients. It's attached below.
> > 
> > : host scaledteam.ru[81.30.221.145] said: 550 5.1.1
> > : Recipient address rejected: User unknown in
> > local recipient table (in reply to RCPT TO command)
> 
> Close now or wait some days?

Try changing the local part from "scaled" not "sacled".

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.


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

Bug#1013180: Undelivered Mail Returned to Sender

[Ben Hutchings]

On Tue, 2022-06-21 at 02:08 +0200, Ben Hutchings wrote:
> On Sat, 2022-06-18 at 17:43 +0200, Diederik de Haas wrote:
> > On zaterdag 18 juni 2022 17:13:33 CEST you wrote:
> > > I'm sorry to have to inform you that your message could not
> > > be delivered to one or more recipients. It's attached below.
> > > 
> > > : host scaledteam.ru[81.30.221.145] said: 550 5.1.1
> > > : Recipient address rejected: User unknown in
> > > local recipient table (in reply to RCPT TO command)
> > 
> > Close now or wait some days?
> 
> Try changing the local part from "scaled" not "sacled".

... from "sacled" to "scaled", even.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.


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

Bug#1000870: marked as done (nvidia: module verification failed: signature and/or required key missing - tainting kernel)

[Debian Bug Tracking System]

Your message dated Tue, 21 Jun 2022 01:48:16 +0200
with message-id <688c2e87e2e7a6194bf37ccd420e54af9dc5c7ff.ca...@decadent.org.uk>
and subject line Re: nvidia: module verification failed: signature and/or 
required key  missing - tainting kernel
has caused the Debian Bug report #1000870,
regarding nvidia: module verification failed: signature and/or required key 
missing - tainting kernel
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.)


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

I can find in the journalctl logs:

  cventin kernel: nvidia: module verification failed: signature and/or required 
key missing - tainting kernel

It seems that this has occurred since the legacy nvidia driver is used
(*nvidia-legacy-390xx-*).

The same issue has been confirmed in Ubuntu:

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

and according to the comments, this is a bug.

-- Package-specific info:
** Version:
Linux version 5.15.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.15.5-1 (2021-11-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.15.0-2-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 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: Dell Inc.
product_name: Precision Tower 7810
product_version: 01
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A07
board_vendor: Dell Inc.
board_name: 0GWHMW
board_version: A00

** Loaded modules:
nvidia_uvm(POE)
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
cpufreq_ondemand
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
intel_rapl_msr
intel_rapl_common
sb_edac
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
ghash_clmulni_intel
aesni_intel
crypto_simd
cryptd
dell_smbios
snd_hda_codec_realtek
dell_wmi_descriptor
rfkill
mei_wdt
video
snd_hda_codec_generic
dcdbas
rapl
snd_hda_codec_hdmi
ledtrig_audio
intel_cstate
dell_smm_hwmon
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
intel_uncore
snd_hda_codec
iTCO_wdt
intel_wmi_thunderbolt
intel_pmc_bxt
pcspkr
iTCO_vendor_support
watchdog
snd_hda_core
snd_hwdep
snd_pcm
snd_timer
sg
snd
mei_me
mei
soundcore
evdev
nvidia_drm(POE)
drm_kms_helper
cec
rc_core
nvidia_modeset(POE)
nvidia(POE)
binfmt_misc
ipmi_devintf
ipmi_msghandler
parport_pc
drm
ppdev
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
hid_generic
usbhid
hid
sr_mod
cdrom
ahci
xhci_pci
libahci
ata_generic
ehci_pci
crct10dif_pclmul
xhci_hcd
crct10dif_common
libata
crc32_pclmul
ehci_hcd
crc32c_intel
e1000e
usbcore
scsi_mod
i2c_i801
lpc_ich
ptp
i2c_smbus
pps_core
usb_common
scsi_common
wmi
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 
DMI2 [8086:2f00] (rev 02)
Subsystem: Dell Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 [1028:0618]
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 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 1 [8086:2f02] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 1 [8086:2f03] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 2 [8086:2f04] (rev 02) (prog-if 

Processed (with 3 errors): Re: Bug#1013249: virtio_ring: module verification failed: signature and/or required key missing - tainting kernel

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1013249 [src:linux] virtio_ring: module verification failed: signature 
and/or required key missing - tainting kernel
Severity set to 'important' from 'normal'
> forcemerge -1 825141
Bug #1013249 [src:linux] virtio_ring: module verification failed: signature 
and/or required key missing - tainting kernel
Unable to merge bugs because:
package of #825141 is 'linux' not 'src:linux'
Failed to forcibly merge 1013249: Did not alter merged bugs.

> fixed -1 4.6.1-1
Failed to add fixed on 1013249: failed to get lock on 
/srv/bugs.debian.org/spool/lock/1013249 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1013249 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> found -1 5.4-1~exp1
Failed to add found on 1013249: failed to get lock on 
/srv/bugs.debian.org/spool/lock/1013249 -- Unable to lock 
/srv/bugs.debian.org/spool/lock/1013249 Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/1013249 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


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

Bug#1013249: virtio_ring: module verification failed: signature and/or required key missing - tainting kernel

[Ben Hutchings]

Control: severity -1 important
Control: forcemerge -1 825141
Control: fixed -1 4.6.1-1
Control: found -1 5.4-1~exp1

On Mon, 2022-06-20 at 11:34 +0900, Ryutaroh Matsumoto wrote:
> Package: src:linux
> Version: 5.18.5-1
> Severity: normal
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
> X-Debbugs-Cc: debian-ri...@lists.debian.org
> 
> Dear Maintainer,
> 
> I do not expect a kernel module in a genuine Debian kernel package
> taints a kernel. But I see the following message in dmesg on
> QEMU RISCV64 virt machine:
> 
> [8.038025] virtio_ring: module verification failed: signature and/or 
> required key missing - tainting kernel
[...]


Yes, this is not right.  Ideally we would be signing modules on all
architectures, but currently we don't do that.  We should configure the
kernel not to expect signatures on other architectures, but these
settings have got out of sync.

This was broken and then fixed once before, so I'm merging this with
the earlier report and noting the version where this seems to have
regressed.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.


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