Bug#1005400: closed by Diederik de Haas (Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware.)

2022-10-29 Thread Salvatore Bonaccorso
Hi,

> Version: 20220913-1
> 
> On Saturday, 12 February 2022 21:40:30 CEST Sebastian Andrzej Siewior wrote:
> > Version: 20210818-1
> > 
> > The orig contains already the AMD SEV firmware in the amd folder:
> > | $ ls -lh amd
> > | 33K Aug 18 13:08 amd_sev_fam17h_model0xh.sbin
> > | 43K Aug 18 13:08 amd_sev_fam17h_model3xh.sbin
> > 
> > Could this be please package? I have an AMD box asking for this.
> 
> They are part of the above version, thus closing.

Actually they are shipped with amd64-microcode instead:

amd64-microcode (3.20220411.1) unstable; urgency=medium

  * Update package data from linux-firmware 20220411:
* New microcode updates from AMD upstream (20220408)
  (closes: #1006444, #1009333)
  + New Microcode patches:
sig 0x00830f10, patch id 0x08301055, 2022-02-15
sig 0x00a00f10, patch id 0x0a001058, 2022-02-10
sig 0x00a00f11, patch id 0x0a001173, 2022-01-31
sig 0x00a00f12, patch id 0x0a001229, 2022-02-10
  + Updated Microcode patches:
sig 0x00800f12, patch id 0x0800126e, 2021/11/11
* New AMD-SEV firmware from AMD upstream (20220308)
  Fixes: CVE-2019-9836 (closes: #970395)
  + New SEV firmware:
Family 17h models 00h-0fh: version 0.17 build 48
Family 17h models 30h-3fh: version 0.24 build 15
Family 19h models 00h-0fh: version 1.51 build 3
  * README: update for new release
  * debian: ship AMD-SEV firmware.
Upstream license is the same license used for amd-ucode

 -- Henrique de Moraes Holschuh   Fri, 15 Apr 2022 18:27:36 
-0300

and 

amd64-microcode: /lib/firmware/amd/amd_sev_fam17h_model0xh.sbin
amd64-microcode: /lib/firmware/amd/amd_sev_fam17h_model3xh.sbin

Regards,
Salvatore



Processed: reassign 1005400 to src:amd64-microcode, closing 1005400

2022-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1005400 src:amd64-microcode
Bug #1005400 {Done: Diederik de Haas } 
[firmware-nonfree] firmware-nonfree: Please package AMD SEV firmware.
Bug reassigned from package 'firmware-nonfree' to 'src:amd64-microcode'.
No longer marked as found in versions 20210818-1.
No longer marked as fixed in versions 20220913-1.
> close 1005400 3.20220411.1
Bug #1005400 {Done: Diederik de Haas } 
[src:amd64-microcode] firmware-nonfree: Please package AMD SEV firmware.
Marked as fixed in versions amd64-microcode/3.20220411.1.
Bug #1005400 {Done: Diederik de Haas } 
[src:amd64-microcode] firmware-nonfree: Please package AMD SEV firmware.
Bug 1005400 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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



Bug#1014451: firmware-brcm80211: brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43455-sdio.txt on a Raspberry Pi 4

2022-10-29 Thread Salvatore Bonaccorso
Hi,

On Sat, Oct 29, 2022 at 12:18:16AM +0200, Diederik de Haas wrote:
> Control: fixed -1 20220913-1
> 
> On Wednesday, 6 July 2022 12:46:16 CEST Enrique wrote:
> > Package: firmware-brcm80211
> > Version: 20210315-3
> > 
> > I have installed pure Debian on a Raspberry Pi 4 and the kernel shows
> > this error messages at boot:
> > 
> > jul 06 11:57:25 alcatraz kernel: brcmfmac mmc0:0001:1: firmware: failed to
> > load brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi 4 Model
> > B.txt (-2)
> 
> This should be resolved with the above mentioned version, uploaded to 
> unstable. As the bug reported seems to only use Stable, I'm not marking it as 
> 'done' (yet). I'll leave that up to the maintainer.

As a though on it: As the BTS can track multiple versions and mark a
bug done in multiple versions in the sense of housekeeping cleanup the
bugs it would rather close it (it can be closed a second time if the
bug get fixed as well in stable with a respective backported version).

Regards,
Salvatore



Processed: tagging 1021157

2022-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1021157 - moreinfo
Bug #1021157 [firmware-atheros] missing firmwares for Qualcomm NFA725A
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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



Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-29 Thread Salvatore Bonaccorso
Hi Christoph,

On Sat, Oct 29, 2022 at 12:36:01AM +0200, Christoph Anton Mitterer wrote:
> Hey Salvatore.
> 
> On Fri, 2022-10-28 at 06:49 +0200, Salvatore Bonaccorso wrote:
> > I did decide to still do so, so we can have the CVE fix migrate
> > finally to testing (which took some time as well given there was the
> > perl transition ongoing).
> 
> Fine for me... I think it would be nice if there was a better mechanism
> to have bugs shown in apt-listbugs out of the box, while still not
> preventing migration to testing.

There is one, involving the release team that they can force a
specific version. In fact I was offlist in contact with Sebastian
Ramacher from the release team who could have done so. In the end the
src:linux was able to migrate on the next run, so downgrading the bug
severity was the quickest action without need to let a release team
emmber intervene.

In the end, yes, the cleanest solution, assuming kernel-team
considered the bug a RC bug, it would have been the right solution to
just ask the release team to force the migration despite of the RC
bug.

> Oh and another off-topic thing:
> 
> Right now the kernel image meta-packages depend on the (secure boot)
> signed version of that... and it seems that these take always longer to
> be available than the unsigned ones.
> 
> However, if people want the nice service to have linux-image-amd64
> installed and pull in just the current package, they need to wait for
> the signed one to become available - even if they don't use secure boot
> at all.
> 
> So question is,.. would it make sense to request that linux-image-amd64
> depends on the signed | unsigned version?

No unfortunately we cannot do that. The reason is similar to what lead
to
https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
or caused bugs like #916927.

In meanwhile furthermore linux-image-amd64 is anyway not anymore from
a separate metapackage but built from linux-signed-amd64.

The signed packages need always longer as this needs action of signing
them trough a seprate manual process of ftp-masters.

> > I did import already 6.0.5 and will upload next so we get the btrfs
> > fix. And I have made the bug now as well again back RC severity.
> 
> Thanks as always for your continued efforts.

Thank you for those encouraging words!

Salvatore



Bug#1006500: marked as done (Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16)

2022-10-29 Thread Salvatore Bonaccorso
Hi,

On Sat, Oct 29, 2022 at 12:31:18AM +0200, Christoph Anton Mitterer wrote:
> Hey Bastian.
> 
> Thanks for fixing.
> 
> Is this going to be backported to bullseye?

We do similar with intel-microcode updates, so maybe this is something
we should consider to. But I think it's to early to think about a
potential 20220913-1~deb11u1 via a bullseye point release.

(just my personal opinion though).

Regards,
Salvatore



Re: Proposed changes to linux package

2022-10-29 Thread Salvatore Bonaccorso
Hi Bastian,

On Sun, Oct 23, 2022 at 03:27:24PM +0200, Bastian Blank wrote:
> On Sat, Oct 22, 2022 at 11:15:05AM +0200, Bastian Blank wrote:
> > On Sat, Oct 22, 2022 at 10:59:30AM +0200, Bastian Blank wrote:
> > > I would like to do some last minute changes to the linux package
> > # Drop special case use of rcX as abi name
> > 
> > While having the ability to distiguish between different RC, it changes
> > the package names every time.
> 
> Or should we just go for 0?  This would also remove the ordering
> weirdness a lot of people experienced.

So instead of having linux-image-6.1.0-rc2-amd64 (for version
6.1~rc2-1~exp1) that would have been linux-image-6.1.0-0-amd64 and so
sorting before linux-image-6.1.0-1-amd64 once we go to an unstable
upload with ABI 1, correct?

Your suggestion sounds like a sensible idea. The distinguishing about
the rc releases would be easier if we retain the former variant, but I
assume concerns for those experimental targeting uploads is less of an
issue.

Ben, opinions on it?

Regards,
Salvatore



Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-29 Thread Vincent Bernat

On 2022-10-29 09:23, Salvatore Bonaccorso wrote:

So question is,.. would it make sense to request that linux-image-amd64
depends on the signed | unsigned version?


No unfortunately we cannot do that. The reason is similar to what lead
to
https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
or caused bugs like #916927.

In meanwhile furthermore linux-image-amd64 is anyway not anymore from
a separate metapackage but built from linux-signed-amd64.

The signed packages need always longer as this needs action of signing
them trough a seprate manual process of ftp-masters.


What about linux-image-amd64-unsigned?



Re: Bug#1005400: closed by Diederik de Haas (Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware.)

2022-10-29 Thread Diederik de Haas
On Saturday, 29 October 2022 09:01:49 CEST Salvatore Bonaccorso wrote:
> > They are part of the above version, thus closing.
> 
> Actually they are shipped with amd64-microcode instead:

Indeed. How come it 'still' shows up in firmware-nonfree's build log?
https://buildd.debian.org/status/fetch.php?pkg=firmware-nonfree&arch=all&ver=20220913-1&stamp=1666990396&raw=0

It was based on that log that I did most/all my recent bug closing.

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


Bug#1001927: firmware-iwlwifi: iwlwifi-8265-36.ucode does not load: Failed to start INIT ucode: -110

2022-10-29 Thread Alexander Prinsier
On Sat, Oct 29, 2022, at 1:00 AM, Diederik de Haas wrote:
> On Sunday, 19 December 2021 04:12:27 CEST Alexander Prinsier wrote:
>> Package: firmware-iwlwifi
>> Version: 20210818-1
>> 
>> Recently did a dist upgrade, which upgraded firmware-iwlwifi to version
>> 20210818-1.
>> 
>> On the next reboot (at least I believe it was the first reboot after the
>> upgrade), my wifi interface is missing.
>> [...] 
>> Seems the new 8265-36 firmware is buggy.
>
> Can you test the recently uploaded version 20220913-1 and update this bug?

I'm not expecting access to the same hardware soon to re-test this, 
unfortunately.



Bug#1023015: linux-image-6.0.0-2-amd64: Laptop fails to resume after opeing lid; worked OK in 5.19.0

2022-10-29 Thread Ralph Martin
Package: src:linux
Version: 6.0.3-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
Close lid of laptop (an LG Gram 16 2022

   * What exactly did you do (or not do) that was effective (or ineffective)?
Reopen it later.

   * What was the outcome of this action?
 Resume screen is shown, but frozen.
 
   * What outcome did you expect instead?
Laptop to resume operation.

In particular, this worked as expected under kernel 5.19.x. I made no other 
changes after installing kernel 6.0.x via an apt full-upgrade and it no longer 
works. Under 5.19.x I made no specific to enable this functionality - it "just 
worked" after installing testing..


-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.3-1 (2022-10-21)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-amd64 
root=UUID=18fed90e-fc02-49a7-b285-3af352f27368 ro quiet

** Tainted: U (64)
 * taint requested by userspace application

** Kernel log:
[6.208434] input: ELAN0E03:00 04F3:3191 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN0E03:00/0018:04F3:3191.0001/input/input11
[6.208606] hid-multitouch 0018:04F3:3191.0001: input,hidraw0: I2C HID v1.00 
Mouse [ELAN0E03:00 04F3:3191] on i2c-ELAN0E03:00
[6.266733] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, 
REV=0x370
[6.266808] thermal thermal_zone6: failed to read out thermal zone (-61)
[6.276450] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[6.276686] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ 
platform, using SOF driver
[6.441511] iwlwifi :00:14.3: firmware: direct-loading firmware 
iwlwifi-so-a0-gf-a0.pnvm
[6.441568] iwlwifi :00:14.3: loaded PNVM version 881c99e1
[6.457088] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000
[6.457471] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[6.457556] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on 
Skylake+ platform, using SOF driver
[6.457576] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 
0002)
[6.457713] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[6.457774] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[6.464746] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
[6.528383] iwlwifi :00:14.3: base HW address: c4:75:ab:0e:c2:48
[6.530830] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5
[6.530833] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
[6.530836] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT 
tables: 2
[6.531830] sof-audio-pci-intel-tgl :00:1f.3: firmware: direct-loading 
firmware intel/sof/sof-adl.ri
[6.531836] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:1:1-3964a
[6.531837] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 
Kernel ABI 3:23:0
[6.531840] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header 
type 3 size 0x30
[6.626693] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 
2:1:1-3964a
[6.626697] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 
Kernel ABI 3:23:0
[6.921351] mc: Linux media interface: v0.10
[6.932491] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[6.939488] videodev: Linux video capture interface: v2.00
[7.249317] Bluetooth: Core ver 2.22
[7.249403] NET: Registered PF_BLUETOOTH protocol family
[7.249405] Bluetooth: HCI device and connection manager initialized
[7.249413] Bluetooth: HCI socket layer initialized
[7.249418] Bluetooth: L2CAP socket layer initialized
[7.249424] Bluetooth: SCO socket layer initialized
[7.304852] usb 1-2: Found UVC 1.50 device LGE FHD Camera (04f2:b772)
[7.337662] input: LGE FHD Camera: LGE FHD Camera as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/input/input12
[7.339440] usb 1-2: Found UVC 1.50 device LGE FHD Camera (04f2:b772)
[7.350208] input: LGE FHD Camera: LGE IR-FHD Came as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.2/input/input13
[7.350300] usbcore: registered new interface driver uvcvideo
[7.459709] usbcore: registered new interface driver btusb
[7.462759] Bluetooth: hci0: Device revision is 0
[7.462769] Bluetooth: hci0: Secure boot is enabled
[7.462771] Bluetooth: hci0: OTP lock is enabled
[7.462773] Bluetooth: hci0: API lock is enabled
[7.462775] Bluetooth: hci0: Debug lock is disabled
[7.462777] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[7.462780] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 
38
[7.472656] bluetooth hci0: firmware

Re: Bug#1005400: closed by Diederik de Haas (Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware.)

2022-10-29 Thread Salvatore Bonaccorso
Hi,

On Sat, Oct 29, 2022 at 10:37:11AM +0200, Diederik de Haas wrote:
> On Saturday, 29 October 2022 09:01:49 CEST Salvatore Bonaccorso wrote:
> > > They are part of the above version, thus closing.
> > 
> > Actually they are shipped with amd64-microcode instead:
> 
> Indeed. How come it 'still' shows up in firmware-nonfree's build log?
> https://buildd.debian.org/status/fetch.php?pkg=firmware-nonfree&arch=all&ver=20220913-1&stamp=1666990396&raw=0
> 
> It was based on that log that I did most/all my recent bug closing.

The files are present in the source and copied to debian/build/install
. But they are then not installed in any of the produced binary
packages in the later install steps for the various binary packages.
(see debian/config/*/defines).

Does this help?

Regards,
Salvatore



Bug#1023016: linux-image-6.0.0-2-amd64: crashes in kernel 6.0.2 (6.0.0-2-amd64) during resume

2022-10-29 Thread karol
Package: src:linux
Version: 6.0.3-1
Severity: normal
X-Debbugs-Cc: karol...@gmail.com

Dear Maintainer,

I noticed several internal crashed in linux kernel after the lates testing 
migration 
(https://tracker.debian.org/news/1378942/linux-signed-amd64-6031-migrated-to-testing/).
This happened today during resume.

They are follow as below:

paź 29 10:55:35 karol kernel: [ cut here ]
paź 29 10:55:35 karol kernel: WARNING: CPU: 4 PID: 20960 at 
kernel/workqueue.c:3066 __flush_work.isra.0+0x270/0x280
paź 29 10:55:35 karol kernel: Modules linked in: btrfs blake2b_generic 
zstd_compress ufs qnx4 hfsplus hfs cdrom minix msdos jfs xfs snd_usb_audio 
snd_usbmidi_lib snd_rawmidi mc ctr ccm snd_ctl_led snd_so>
paź 29 10:55:35 karol kernel:  libarc4 mei btmtk iwlwifi bluetooth 
hid_multitouch cfg80211 jitterentropy_rng sha512_ssse3 sha512_generic drbg 
ansi_cprng processor_thermal_device_pci processor_thermal_dev>
paź 29 10:55:35 karol kernel:  hid_logitech_hidpp hid_logitech_dj usbhid 
hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 hid_generic drm_buddy 
crc32_pclmul xhci_pci crc32c_intel i2c_algo_bit nvme g>
paź 29 10:55:35 karol kernel: CPU: 4 PID: 20960 Comm: systemd-sleep Tainted: G  
  W  6.0.0-2-amd64 #1  Debian 6.0.3-1
paź 29 10:55:35 karol kernel: Hardware name: LENOVO 21CB007BPB/21CB007BPB, BIOS 
N3AET67W (1.32 ) 09/27/2022
paź 29 10:55:35 karol kernel: RIP: 0010:__flush_work.isra.0+0x270/0x280
paź 29 10:55:35 karol kernel: Code: 8b 04 25 c0 fb 01 00 48 89 44 24 40 48 8b 
73 30 8b 4b 28 e9 e3 fe ff ff 40 30 f6 4c 8b 3e e9 21 fe ff ff 0f 0b e9 3a ff 
ff ff <0f> 0b e9 33 ff ff ff e8 94 57 91 00 0f >
paź 29 10:55:35 karol kernel: RSP: 0018:acd4c79c7c50 EFLAGS: 00010246
paź 29 10:55:35 karol kernel: RAX:  RBX: 92a1cab24e68 RCX: 

paź 29 10:55:35 karol kernel: RDX: 0001 RSI: 0001 RDI: 
acd4c79c7c98
paź 29 10:55:35 karol kernel: RBP: 92a1cab24e68 R08: a13ba630 R09: 

paź 29 10:55:35 karol kernel: R10:  R11: 005f R12: 
0001
paź 29 10:55:35 karol kernel: R13: acd4c79c7c50 R14: 0001 R15: 
c155dfa0
paź 29 10:55:35 karol kernel: FS:  7f7b1b8ba940() 
GS:92a8ff50() knlGS:
paź 29 10:55:35 karol kernel: CS:  0010 DS:  ES:  CR0: 80050033
paź 29 10:55:35 karol kernel: CR2: 34f4379f CR3: 00020033a005 CR4: 
00770ee0
paź 29 10:55:35 karol kernel: PKRU: 5554
paź 29 10:55:35 karol kernel: Call Trace:
paź 29 10:55:35 karol kernel:  
paź 29 10:55:35 karol kernel:  ? snd_hda_multi_out_dig_close+0x40/0x40 
[snd_hda_codec]
paź 29 10:55:35 karol kernel:  __cancel_work_timer+0xff/0x190
paź 29 10:55:35 karol kernel:  ? preempt_count_add+0x6a/0xa0
paź 29 10:55:35 karol kernel:  ? _raw_spin_lock_irq+0x19/0x40
paź 29 10:55:35 karol kernel:  hda_codec_pm_prepare+0x15/0x50 [snd_hda_codec]
paź 29 10:55:35 karol kernel:  dpm_prepare+0xc6/0x3e0
paź 29 10:55:35 karol kernel:  dpm_suspend_start+0x1a/0x80
paź 29 10:55:35 karol kernel:  suspend_devices_and_enter+0x13a/0x880
paź 29 10:55:35 karol kernel:  pm_suspend.cold+0x270/0x2fc
paź 29 10:55:35 karol kernel:  state_store+0x68/0xd0
paź 29 10:55:35 karol kernel:  kernfs_fop_write_iter+0x11b/0x1f0
paź 29 10:55:35 karol kernel:  vfs_write+0x241/0x400
paź 29 10:55:35 karol kernel:  ksys_write+0x6b/0xf0
paź 29 10:55:35 karol kernel:  do_syscall_64+0x37/0xc0
paź 29 10:55:35 karol kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
paź 29 10:55:35 karol kernel: RIP: 0033:0x7f7b1bafa3f3
paź 29 10:55:35 karol kernel: Code: 8b 15 21 9a 0f 00 f7 d8 64 89 02 48 c7 c0 
ff ff ff ff eb b7 0f 1f 00 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 
0f 05 <48> 3d 00 f0 ff ff 77 55 c3 0f 1f 40 00 >
paź 29 10:55:35 karol kernel: RSP: 002b:7ffd315a57e8 EFLAGS: 0246 
ORIG_RAX: 0001
paź 29 10:55:35 karol kernel: RAX: ffda RBX: 0004 RCX: 
7f7b1bafa3f3
paź 29 10:55:35 karol kernel: RDX: 0004 RSI: 7ffd315a58d0 RDI: 
0004
paź 29 10:55:35 karol kernel: RBP: 7ffd315a58d0 R08: 0007 R09: 
55ef87703230
paź 29 10:55:35 karol kernel: R10: f42f1c64e625fa0d R11: 0246 R12: 
0004
paź 29 10:55:35 karol kernel: R13: 55ef876ff2d0 R14: 0004 R15: 
7f7b1bbf09e0
paź 29 10:55:35 karol kernel:  
paź 29 10:55:35 karol kernel: ---[ end trace  ]---
paź 29 10:55:35 karol kernel: [ cut here ]

paź 29 10:55:35 karol kernel: [ cut here ]
paź 29 10:55:35 karol kernel: WARNING: CPU: 4 PID: 20960 at 
kernel/workqueue.c:3066 __flush_work.isra.0+0x270/0x280
paź 29 10:55:35 karol kernel: Modules linked in: btrfs blake2b_generic 
zstd_compress ufs qnx4 hfsplus hfs cdrom minix msdos jfs xfs snd_usb_audio 
snd_usbmidi_lib snd_rawmidi mc ctr ccm snd_ctl_led snd_so>
paź 29 10:55:35 karo

Re: Bug#1005400: closed by Diederik de Haas (Re: Bug#1005400: firmware-nonfree: Please package AMD SEV firmware.)

2022-10-29 Thread Diederik de Haas
On Saturday, 29 October 2022 10:59:21 CEST Salvatore Bonaccorso wrote:
> > It was based on that log that I did most/all my recent bug closing.
> 
> The files are present in the source and copied to debian/build/install
> . But they are then not installed in any of the produced binary
> packages in the later install steps for the various binary packages.
> (see debian/config/*/defines).
> 
> Does this help?

Yes it does, thanks.


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


Bug#1023016: linux-image-6.0.0-2-amd64: crashes in kernel 6.0.2 (6.0.0-2-amd64) during resume

2022-10-29 Thread Diederik de Haas
On Saturday, 29 October 2022 11:08:01 CEST karol wrote:
> Package: src:linux
> Version: 6.0.3-1
> 
> I noticed several internal crashed in linux kernel ...
> This happened today during resume.
> 
> They are follow as below:
> 
> paź 29 10:55:35 karol kernel: [ cut here ]
> paź 29 10:55:35 karol kernel: WARNING: CPU: 4 PID: 20960 at
> kernel/workqueue.c:3066 __flush_work.isra.0+0x270/0x280

Commit c0feea594e058223973db94c1c32a830c9807c86 changed `kernel/workqueue.c` 
around line 3066 and is the only change in that file that is part of 6.0 and 
not part of 5.19.
So it would be an interesting test to see if the issue 'goes away' if you'd 
build a kernel with that commit reverted (and boot into it ofc).
Can you try that?

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


Bug#1006500: marked as done (Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16)

2022-10-29 Thread Bastian Blank
On Sat, Oct 29, 2022 at 12:31:18AM +0200, Christoph Anton Mitterer wrote:
> Is this going to be backported to bullseye?

First is needs to settle a bit.

But as you can see, in the past we did produce backports:

| firmware-nonfree | 20210818-1~bpo11+1 | bullseye-backports/non-free | source

Bastian

-- 
Power is danger.
-- The Centurion, "Balance of Terror", stardate 1709.2



Processing of linux-signed-amd64_6.0.5+1_source.changes

2022-10-29 Thread Debian FTP Masters
linux-signed-amd64_6.0.5+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-amd64_6.0.5+1.dsc
  linux-signed-amd64_6.0.5+1.tar.xz

Greetings,

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



linux-signed-amd64_6.0.5+1_source.changes ACCEPTED into unstable

2022-10-29 Thread Debian FTP Masters
Mapping sid to unstable.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Oct 2022 08:53:43 +0200
Source: linux-signed-amd64
Architecture: source
Version: 6.0.5+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-amd64 (6.0.5+1) unstable; urgency=medium
 .
   * Sign kernel from linux 6.0.5-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.4
 - [x86] drm/i915/bios: Validate fp_timing terminator presence
 - [x86] drm/i915/bios: Use hardcoded fp_timing size for generating LFP data
   pointers
 - pinctrl: amd: change dev_warn to dev_dbg for additional feature support
 - [x86] thermal: intel_powerclamp: Use first online CPU as control_cpu
 - io_uring/net: fail zc send when unsupported by socket
 - HID: playstation: stop DualSense output work on remove.
 - HID: playstation: add initial DualSense Edge controller support
 - net: flag sockets supporting msghdr originated zerocopy
 - drm/amd/pm: fulfill SMU13.0.7 cstate control interface
 - drm/amd/pm: add SMU IP v13.0.4 IF version define to V7
 - drm/amd/pm: disable cstate feature for gpu reset scenario
 - drm/amd/pm: fulfill SMU13.0.0 cstate control interface
 - drm/amd/pm: update SMU IP v13.0.4 driver interface version
 - dm clone: Fix typo in block_device format specifier
 - efi: efivars: Fix variable writes without query_variable_store()
 - efi: ssdt: Don't free memory if ACPI table was loaded successfully
 - gcov: support GCC 12.1 and newer compilers
 - io-wq: Fix memory leak in worker creation
 - fbdev/core: Remove remove_conflicting_pci_framebuffers()
 - Revert "ALSA: hda: Fix page fault in snd_hda_codec_shutdown()"
   (Closes: #1022544)
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.5
 - [arm64,armhf] clk: tegra: Fix Tegra PWM parent clock
 - Revert "btrfs: call __btrfs_remove_free_space_cache_locked on cache load
   failure" (Closes: #1022848)
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 6.0.5-rt14
   * Ignore ABI changes doe to removed check_var_size, 
check_var_size_nonblocking
 and remove_conflicting_pci_framebuffers
Checksums-Sha1:
 02bacf7e8bb28546a258118cfde252947c4228d7 8359 linux-signed-amd64_6.0.5+1.dsc
 0ad5e21ee47eb18f40450970392d82dad4628a6a 2932436 
linux-signed-amd64_6.0.5+1.tar.xz
Checksums-Sha256:
 20c164aca2fbdc30b4e908b37ecbeb808803cceea4e1bc9ce9f3b092049db478 8359 
linux-signed-amd64_6.0.5+1.dsc
 89cc56c1c74d6c2ab12c4127b2d93bcf3e38ba5e5dd1928a4eaeb3b36d668127 2932436 
linux-signed-amd64_6.0.5+1.tar.xz
Files:
 0ec969d4dce39fe29eecfa326bdff897 8359 kernel optional 
linux-signed-amd64_6.0.5+1.dsc
 fa16674faae9f907022b9e76115eaf8f 2932436 kernel optional 
linux-signed-amd64_6.0.5+1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNc+bsACgkQi0FRiLdO
NzZJ5xAApO9aI3cTMl2w46mMtCJqOzBkHYiSYGObg/LzHK22FozNUVucpu1NIBHa
9UxW3k1jZY5qn9D6cIYMhMtF2+QQgmQlngBn+JG4xrD0an2mXDC7DEmX9+TWZ2qu
P0Vnfb5cGsUgx7GTGSt4logXUiW87v7Yh0jeoiPJNnItReeZDDUg5qobkn5X9MQt
0ercaHrS6jVjFhC9GooJDGb4g86u0kI2yCPf+sgKY2/wagjcBxqSMrZEyb5/JVC0
tMNkvpNXuj+Ua1rcgr0a/SBHHSkW2s9+UZH9BmmInPDQPpq9yqJji8IKKW5ujRy5
rVmAgZUq2cBJEcMFPYaZ9aMx/ZyW0hCcmIXVdzcQCr4zAhFm51rvnX2Z4smhDhe4
POJS6OjdDWfoWfleZK/tXWlApuhAPdZFRAEND9J4AIbBn6LtoNiL9xy+GDK6HeT7
I8WNsdnZXt6MBbMhFnJvlnNxxeUE+vaxokQkpHC/AyC5L0yKFYVdYk/VM2maKA1d
OxTKGPkCQavEmw0r+/YOOUaqFtA3WKlbe4XJq82C+QZ0q8aMYghOSikP3ANfivOi
cVtThV/tvLE6YClgxHPnUIa6vv6V2bNWnVfD8HuejgwUJsljYQPdmscFU4n3bSe4
YG2J2RMjQieK72fFWdXm2q6JeWFKsmriOGcaVRKmdBDIzQ7exw4=
=RGaB
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Bug#1023025: linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!

2022-10-29 Thread femenia
Package: src:linux
Version: 6.0.3-1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 6.0.0-2-686 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-5) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.3-1 (2022-10-21)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.0.0-2-686 
root=UUID=ae4affb9-b1b9-4ee7-89f9-f74034b3d28b ro single

** Not tainted

** Kernel log:

Oct 29 11:33:39 [localhost] kernel: [   77.829921] [ cut here 
]
Oct 29 11:33:39 [localhost] kernel: [   77.829942] kernel BUG at 
mm/memory.c:2660!
Oct 29 11:33:39 [localhost] kernel: [   77.829961] invalid opcode:  [#1] 
PREEMPT SMP
Oct 29 11:33:39 [localhost] kernel: [   77.829975] CPU: 0 PID: 649 Comm: Xorg 
Not tainted 6.0.0-2-686 #1  Debian 6.0.3-1
Oct 29 11:33:39 [localhost] kernel: [   77.829989] Hardware name: Dell Inc. 
MM061   /0KD882, BIOS A17 06/13/2007
Oct 29 11:33:39 [localhost] kernel: [   77.829998] EIP: 
__apply_to_page_range+0x370/0x470
Oct 29 11:33:39 [localhost] kernel: [   77.830019] Code: 8b 7d cc 81 7d e4 e0 
46 c4 cb 74 0e 89 c2 e9 71 ff ff ff 8d b4 26 00 00 00 00 8b 7d d8 89 c1 e9 3f 
fd ff ff 8d b6 00 00 00 00 <0f> 0b 8d b6 00 00 00 00 85 c0 0f 84 c3 00 00 00 89 
f7 89 c2 c1 ef
Oct 29 11:33:39 [localhost] kernel: [   77.830032] EAX: 0001 EBX: a900 
ECX: c2e13a8c EDX: 02a3
Oct 29 11:33:39 [localhost] kernel: [   77.830043] ESI: a8f9 EDI: a97f 
EBP: c26b3dcc ESP: c26b3d90
Oct 29 11:33:39 [localhost] kernel: [   77.830053] DS: 007b ES: 007b FS: 00d8 
GS: 0033 SS: 0068 EFLAGS: 00210202
Oct 29 11:33:39 [localhost] kernel: [   77.830066] CR0: 80050033 CR2: a8f9 
CR3: 02e13000 CR4: 06d0
Oct 29 11:33:39 [localhost] kernel: [   77.830077] Call Trace:
Oct 29 11:33:39 [localhost] kernel: [   77.830090]  ? 
ktime_get_mono_fast_ns+0x3f/0xe0
Oct 29 11:33:39 [localhost] kernel: [   77.830109]  
apply_to_page_range+0x15/0x20
Oct 29 11:33:39 [localhost] kernel: [   77.830126]  ? 
i915_memcpy_init_early+0x30/0x30 [i915]
Oct 29 11:33:39 [localhost] kernel: [   77.830394]  remap_io_mapping+0x62/0xa0 
[i915]
Oct 29 11:33:39 [localhost] kernel: [   77.830650]  ? 
i915_memcpy_init_early+0x30/0x30 [i915]
Oct 29 11:33:39 [localhost] kernel: [   77.830910]  vm_fault_gtt+0x2fb/0x750 
[i915]
Oct 29 11:33:39 [localhost] kernel: [   77.831214]  ? 
__mod_lruvec_state+0x29/0x30
Oct 29 11:33:39 [localhost] kernel: [   77.831231]  ? 
__mod_lruvec_page_state+0x69/0xb0
Oct 29 11:33:39 [localhost] kernel: [   77.831247]  __do_fault+0x2c/0x120
Oct 29 11:33:39 [localhost] kernel: [   77.831261]  handle_mm_fault+0xa59/0x1020
Oct 29 11:33:39 [localhost] kernel: [   77.831284]  
do_user_addr_fault+0x18d/0x500
Oct 29 11:33:39 [localhost] kernel: [   77.831301]  exc_page_fault+0x51/0x160
Oct 29 11:33:39 [localhost] kernel: [   77.831318]  ? paravirt_BUG+0x10/0x10
Oct 29 11:33:39 [localhost] kernel: [   77.831331]  handle_exception+0x133/0x133
Oct 29 11:33:39 [localhost] kernel: [   77.831346] EIP: 0xb6feff37
Oct 29 11:33:39 [localhost] kernel: [   77.831358] Code: 83 c4 10 85 c0 0f 85 
d8 00 00 00 8b 44 24 30 8b 74 24 0c 89 46 54 e9 02 ff ff ff 8d b4 26 00 00 00 
00 90 8b 44 24 0c 8b 40 28  00 00 00 00 00 8b 44 24 10 8d 90 e0 23 00 00 8b 
02 83 e8 01 89
Oct 29 11:33:39 [localhost] kernel: [   77.831370] EAX: a8f9 EBX: b718f000 
ECX:  EDX: 
Oct 29 11:33:39 [localhost] kernel: [   77.831380] ESI: 0263dd60 EDI: b718f000 
EBP: b6739000 ESP: bfe81970
Oct 29 11:33:39 [localhost] kernel: [   77.831391] DS: 007b ES: 007b FS:  
GS: 0033 SS: 007b EFLAGS: 00210246
Oct 29 11:33:39 [localhost] kernel: [   77.831406]  ? paravirt_BUG+0x10/0x10
Oct 29 11:33:39 [localhost] kernel: [   77.831422] Modules linked in: qrtr 
sunrpc snd_usb_audio snd_hda_codec_hdmi snd_usbmidi_lib snd_rawmidi 
snd_hda_codec_idt b43 snd_hda_codec_generic snd_seq_device snd_hda_intel mc 
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec cordic dell_laptop bcma 
snd_hda_core ledtrig_audio mac80211 snd_hwdep snd_pcm dell_smm_hwmon snd_timer 
libarc4 cfg80211 r852 iTCO_wdt snd sm_common intel_pmc_bxt coretemp 
iTCO_vendor_support nand watchdog soundcore r592 nandcore rfkill pcspkr joydev 
bch mtd memstick serio_raw dell_wmi dell_smbios dcdbas sparse_keymap wmi_bmof 
dell_wmi_descriptor sg rng_core evdev ac acpi_cpufreq parport_pc ppdev lp 
parport fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs 
blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c crc

Processing of linux-signed-arm64_6.0.5+1_source.changes

2022-10-29 Thread Debian FTP Masters
linux-signed-arm64_6.0.5+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-arm64_6.0.5+1.dsc
  linux-signed-arm64_6.0.5+1.tar.xz

Greetings,

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



linux-signed-arm64_6.0.5+1_source.changes ACCEPTED into unstable

2022-10-29 Thread Debian FTP Masters
Mapping sid to unstable.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Oct 2022 08:53:43 +0200
Source: linux-signed-arm64
Architecture: source
Version: 6.0.5+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-arm64 (6.0.5+1) unstable; urgency=medium
 .
   * Sign kernel from linux 6.0.5-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.4
 - [x86] drm/i915/bios: Validate fp_timing terminator presence
 - [x86] drm/i915/bios: Use hardcoded fp_timing size for generating LFP data
   pointers
 - pinctrl: amd: change dev_warn to dev_dbg for additional feature support
 - [x86] thermal: intel_powerclamp: Use first online CPU as control_cpu
 - io_uring/net: fail zc send when unsupported by socket
 - HID: playstation: stop DualSense output work on remove.
 - HID: playstation: add initial DualSense Edge controller support
 - net: flag sockets supporting msghdr originated zerocopy
 - drm/amd/pm: fulfill SMU13.0.7 cstate control interface
 - drm/amd/pm: add SMU IP v13.0.4 IF version define to V7
 - drm/amd/pm: disable cstate feature for gpu reset scenario
 - drm/amd/pm: fulfill SMU13.0.0 cstate control interface
 - drm/amd/pm: update SMU IP v13.0.4 driver interface version
 - dm clone: Fix typo in block_device format specifier
 - efi: efivars: Fix variable writes without query_variable_store()
 - efi: ssdt: Don't free memory if ACPI table was loaded successfully
 - gcov: support GCC 12.1 and newer compilers
 - io-wq: Fix memory leak in worker creation
 - fbdev/core: Remove remove_conflicting_pci_framebuffers()
 - Revert "ALSA: hda: Fix page fault in snd_hda_codec_shutdown()"
   (Closes: #1022544)
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.5
 - [arm64,armhf] clk: tegra: Fix Tegra PWM parent clock
 - Revert "btrfs: call __btrfs_remove_free_space_cache_locked on cache load
   failure" (Closes: #1022848)
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 6.0.5-rt14
   * Ignore ABI changes doe to removed check_var_size, 
check_var_size_nonblocking
 and remove_conflicting_pci_framebuffers
Checksums-Sha1:
 0c8382a6e9861de7954a4137445957ed4fbb185a 7135 linux-signed-arm64_6.0.5+1.dsc
 812c13655147f2d310a40c7ba47a86af90b11502 2690336 
linux-signed-arm64_6.0.5+1.tar.xz
Checksums-Sha256:
 777d4b60277f69252a67cb93ef393025a13fe6ba3fa5a74983794ce19debd24a 7135 
linux-signed-arm64_6.0.5+1.dsc
 2b2e72c21d8d7b682c6f1838506c91c79b126031263a559f53a71a8aca743bdd 2690336 
linux-signed-arm64_6.0.5+1.tar.xz
Files:
 0c9528988d0876162b1c8a256ad6e290 7135 kernel optional 
linux-signed-arm64_6.0.5+1.dsc
 68adefc6560f0cdfdf75f679b4de6048 2690336 kernel optional 
linux-signed-arm64_6.0.5+1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNdHAIACgkQi0FRiLdO
Nzb4hw//Y2FIGHG8t7RfmVncLoYYkEANtxN113ECOpAlHhHtDmewOQ4m52mQeOQ6
SPwlCDNGysgX5D9yPmsvDw7QrX4hXMCR0haBB/MMoq5IFmV5lo5wnX1iVGz4V+Q1
XKVbwdiW9kIrf9m/hu0kpDayImp62unQ3WKic3OQ/1B8yW8ZdSU6QUN7dp79kVI6
t4PmcCECMaynRtLuB8Q/01PS9PSnTDKw7+kjNMAKSm5amdQ8iNFlAfJRmi/GL0ME
DA/DHuQOwP63WAU5Tlk6OR1p3NaV8FLNBLLsqCCBtduNZMK1kHg0aKkH4l0wih8O
V0ot2nvYMXJLPTdD7+UbOyC9PZo6fYgt+ATDHt7Iep8a8Ocs/wIxztIiy33WQA0V
kqQ+9fdSzFz9to8uHLKZyRsxAK3GXbP+RWs5RL4jzghiS9aN4Pbb68q5kD/Ggs7L
DUBIQJ7SI0lVGalTA8VF9qZUaTc6Q8jKAul0FiKN2tZKKo3BGmdTya295BO/Xs5b
OXKgSjxoLQnBsdAyB2e2uC5m5FvTZASj7kNChY1aEv4pVMf8QS98qIFPW+i4GM/7
jqrbLhxv+Xot3E1w271/a59rWGd4RazjIjq7qF57ViYhX+8NMHYMNzGr7jWvtIeO
tD4NyHyg+/LIsqUyvINkOYnFKCw24C/Ck3sgNHuTM/mVs7hQOOI=
=onr7
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Processed: reassign 1021315 to src:linux ..., tagging 1001022, affects 1013228 ..., fixed 1011028 in 1.0.2 ...

2022-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # bts housekeeping
> reassign 1021315 src:linux 5.19.0-2
Bug #1021315 [linux-image-5.19.0-2-arm64] Linux kernel very slow to boot
Warning: Unknown package 'linux-image-5.19.0-2-arm64'
Bug reassigned from package 'linux-image-5.19.0-2-arm64' to 'src:linux'.
No longer marked as found in versions 5.19.0-2.
Ignoring request to alter fixed versions of bug #1021315 to the same values 
previously set
Bug #1021315 [src:linux] Linux kernel very slow to boot
The source 'linux' and version '5.19.0-2' do not appear to match any binary 
packages
Marked as found in versions linux/5.19.0-2.
> retitle 1020192 cycle-quotes: FTBFS with emacs 28: 1 test failed: 
> test-cycle-quotes-triple-quotes retitle 1020164 clojure-mode: FTBFS with 
> emacs 28: 24 tests failed
Bug #1020192 [src:cycle-quotes] cycle-quotes: FTBFS: make: *** [debian/rules:4: 
build] Error 25
Changed Bug title to 'cycle-quotes: FTBFS with emacs 28: 1 test failed: 
test-cycle-quotes-triple-quotes retitle 1020164 clojure-mode: FTBFS with emacs 
28: 24 tests failed' from 'cycle-quotes: FTBFS: make: *** [debian/rules:4: 
build] Error 25'.
> tags 1001022 + experimental
Bug #1001022 {Done: HIGUCHI Daisuke (VDR dai) } 
[ruby-pathutil] ruby-pathutil: Not Ruby 3.0 compatible due to kwargs issues
Added tag(s) experimental.
> affects 1013228 + src:crossbar
Bug #1013228 {Done: Bastian Germann } [python-werkzeug] 
python-werkzeug: Please keep version < 2.1
Added indication that 1013228 affects src:crossbar
> notfixed 1013228 crossbar/21.3.1+dfsg-3
Bug #1013228 {Done: Bastian Germann } [python-werkzeug] 
python-werkzeug: Please keep version < 2.1
No longer marked as fixed in versions crossbar/21.3.1+dfsg-3.
> notfixed 1018919 8.32-4+b1
Bug #1018919 {Done: наб } [coreutils] 
coreutils: stty: default/-a output for characters wrong for disabled ones
No longer marked as fixed in versions 8.32-4+b1.
> reassign 1011028 src:extrepo-data
Bug #1011028 {Done: Thomas Goirand } [extrepo] Wishlist: add 
GitHub CLI repo
Bug reassigned from package 'extrepo' to 'src:extrepo-data'.
No longer marked as found in versions extrepo/0.10.
No longer marked as fixed in versions 1.0.2.
> fixed 1011028 1.0.2
Bug #1011028 {Done: Thomas Goirand } [src:extrepo-data] 
Wishlist: add GitHub CLI repo
Marked as fixed in versions extrepo-data/1.0.2.
> reassign 1017590 fakechroot
Bug #1017590 {Done: Johannes Schauer Marin Rodrigues } 
[src:glibc] glibc 2.34 broke getpwnam calls under fakechroot
Bug reassigned from package 'src:glibc' to 'fakechroot'.
No longer marked as found in versions glibc/2.34-1.
No longer marked as fixed in versions fakechroot/2.20.1+ds-6.
> fixed 1017590 2.20.1+ds-6
Bug #1017590 {Done: Johannes Schauer Marin Rodrigues } 
[fakechroot] glibc 2.34 broke getpwnam calls under fakechroot
Marked as fixed in versions fakechroot/2.20.1+ds-6.
> tags 1007457 + experimental
Bug #1007457 {Done: Bastian Germann } 
[src:ssh-askpass-fullscreen] ssh-askpass-fullscreen: please consider upgrading 
to 3.0 source format
Added tag(s) experimental.
> fixed 1003342 2.34-1
Bug #1003342 {Done: Aurelien Jarno } [libc6] libc6: NIS 
client not working after update to libc6:amd64 2.33-1
Bug #1012097 {Done: Aurelien Jarno } [libc6] NIS broken 
in sid
Marked as fixed in versions glibc/2.34-1.
Marked as fixed in versions glibc/2.34-1.
> tags 1003342 - sid bookworm
Bug #1003342 {Done: Aurelien Jarno } [libc6] libc6: NIS 
client not working after update to libc6:amd64 2.33-1
Bug #1012097 {Done: Aurelien Jarno } [libc6] NIS broken 
in sid
Removed tag(s) bookworm and sid.
Removed tag(s) sid and bookworm.
> tags 1012890 - sid bookworm
Bug #1012890 {Done: Roger Shimizu } 
[src:android-platform-frameworks-base] android-platform-frameworks-base: ftbfs 
with GCC-12
Removed tag(s) bookworm and sid.
> tags 1012572 - sid bookworm
Bug #1012572 {Done: Roger Shimizu } 
[src:android-platform-frameworks-base] android-platform-frameworks-base: FTBFS 
with protobuf 3.20.1+
Removed tag(s) bookworm and sid.
> notfound 1019554 2.3-35
Bug #1019554 {Done: Lance Lin } [anacron] anacron: 
Anacron no longer seems to execute jobs
Bug #1020966 {Done: Lance Lin } [anacron] anacron: after 
update anacron.service is disabled
Bug #1021496 {Done: Lance Lin } [anacron] anacron: 
cron.daily stopped executing a month ago
No longer marked as found in versions anacron/2.3-35.
No longer marked as found in versions anacron/2.3-35.
No longer marked as found in versions anacron/2.3-35.
> notfixed 1022297 20220429+dfsg1-2
Bug #1022297 {Done: Antonio Radici } [src:neomutt] neomutt: 
FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'
No longer marked as fixed in versions neomutt/20220429+dfsg1-2.
> fixed 1022297 20220429+dfsg1-3
Bug #1022297 {Done: Antonio Radici } [src:neomutt] neomutt: 
FTBFS: ./obj-x86_64-linux-gnu/conftest__.c:3: undefined reference to `qsort_s'
Marked as fixed in versions neomutt/20220429+dfsg1-3.
> thanks
Stopping processing here.

Please contact me if you nee

Processed: notfound 1021315 in 5.19.0-2, found 1021315 in 5.19.11-1

2022-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 1021315 5.19.0-2
Bug #1021315 [src:linux] Linux kernel very slow to boot
The source 'linux' and version '5.19.0-2' do not appear to match any binary 
packages
No longer marked as found in versions linux/5.19.0-2.
> found 1021315 5.19.11-1
Bug #1021315 [src:linux] Linux kernel very slow to boot
Marked as found in versions linux/5.19.11-1.
> thanks
Stopping processing here.

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



Processing of linux-signed-i386_6.0.5+1_source.changes

2022-10-29 Thread Debian FTP Masters
linux-signed-i386_6.0.5+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-i386_6.0.5+1.dsc
  linux-signed-i386_6.0.5+1.tar.xz

Greetings,

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



linux-signed-i386_6.0.5+1_source.changes ACCEPTED into unstable

2022-10-29 Thread Debian FTP Masters
Mapping sid to unstable.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 28 Oct 2022 08:53:43 +0200
Source: linux-signed-i386
Architecture: source
Version: 6.0.5+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux-signed-i386 (6.0.5+1) unstable; urgency=medium
 .
   * Sign kernel from linux 6.0.5-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.4
 - [x86] drm/i915/bios: Validate fp_timing terminator presence
 - [x86] drm/i915/bios: Use hardcoded fp_timing size for generating LFP data
   pointers
 - pinctrl: amd: change dev_warn to dev_dbg for additional feature support
 - [x86] thermal: intel_powerclamp: Use first online CPU as control_cpu
 - io_uring/net: fail zc send when unsupported by socket
 - HID: playstation: stop DualSense output work on remove.
 - HID: playstation: add initial DualSense Edge controller support
 - net: flag sockets supporting msghdr originated zerocopy
 - drm/amd/pm: fulfill SMU13.0.7 cstate control interface
 - drm/amd/pm: add SMU IP v13.0.4 IF version define to V7
 - drm/amd/pm: disable cstate feature for gpu reset scenario
 - drm/amd/pm: fulfill SMU13.0.0 cstate control interface
 - drm/amd/pm: update SMU IP v13.0.4 driver interface version
 - dm clone: Fix typo in block_device format specifier
 - efi: efivars: Fix variable writes without query_variable_store()
 - efi: ssdt: Don't free memory if ACPI table was loaded successfully
 - gcov: support GCC 12.1 and newer compilers
 - io-wq: Fix memory leak in worker creation
 - fbdev/core: Remove remove_conflicting_pci_framebuffers()
 - Revert "ALSA: hda: Fix page fault in snd_hda_codec_shutdown()"
   (Closes: #1022544)
 https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.0.5
 - [arm64,armhf] clk: tegra: Fix Tegra PWM parent clock
 - Revert "btrfs: call __btrfs_remove_free_space_cache_locked on cache load
   failure" (Closes: #1022848)
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 6.0.5-rt14
   * Ignore ABI changes doe to removed check_var_size, 
check_var_size_nonblocking
 and remove_conflicting_pci_framebuffers
Checksums-Sha1:
 fa4f835e30512b19ffa85f0fd0b76b40ba4c87d9 13808 linux-signed-i386_6.0.5+1.dsc
 2a2b931137ec7595e570f61f71715aaf217ce15b 3844700 
linux-signed-i386_6.0.5+1.tar.xz
Checksums-Sha256:
 0c63e77335d1d76b33e3faa64f0c392de4050bfc80423612c28225e8faa45351 13808 
linux-signed-i386_6.0.5+1.dsc
 c23036e5f58bae86e2ccd21355aa70bcc22806d33368f9bd6085c3f91ccc7e8e 3844700 
linux-signed-i386_6.0.5+1.tar.xz
Files:
 76258f010b0b5d283392cd90f1adf4e6 13808 kernel optional 
linux-signed-i386_6.0.5+1.dsc
 b15f7e4e07b89706ff1d3802ad6d830c 3844700 kernel optional 
linux-signed-i386_6.0.5+1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfKFfvHEI+gkU+E+di0FRiLdONzYFAmNdT18ACgkQi0FRiLdO
NzYDnw/+NUw8Riy5Ezsmg0M3s96JEaHBt1G+4RkYZ+vrAATar+vaFp1TJlT0CRef
8vlMnt0HfUKiYKQI9faCt+VBqyXr+cRPuLvj8faLc2RTcpzsTc43VnzTYV6x6rgr
dqjhVwufYpHTw5hiHzhymd/dNMgE3h5HUKdD0bqDtKb3yVFYoAt3ItAFeTfBJib7
FE4FO/QA+FdVAiXMt440i6MyY2i5HshoTySJGfnFbjcuLlTEPuTWfNGBLEIOM5JF
fH1iOTEDhGdwPMuh72nG/kwoKVXVkdhgnntFWMPF5tPRKrHfk04vPmOfJE0Ro81i
Ju5JjsoeOPryxqQl0ZMIFYnwU1huqYZ9va8ONuooGEfttGjju4NC9H6AmvkC5nEb
h8ePkBWwdLqWAU7HC5D6/Wc5vMTlrCxLynN/q63aEojxGEdRLAG58JaEkK1SBGml
ONe1Ta++olEoWOAB1M2qbYFViD4qx4cLltwIrSwcG+1xdrrtufyD1E/ICGhPZgwq
y0621pSJ4Uakagwy/1BDDfvlU9GQ1PiBgD7ukSHdBtVvc4Jb0jQ/YyAe68nO
RZX9nGcxyrALcKVRi7qp2M5yNgaGzOKvr7skNwIuTqpg7UG9iFgDEWg6rzBs8KV7
Zb2Ce8m9xRM1sGYt8VHEU5aiOzDXVdPtkNvozWeI1dhU5EQQ6xk=
=0cY+
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Bug#1021157: missing firmwares for Qualcomm NFA725A

2022-10-29 Thread Diederik de Haas
On zaterdag 29 oktober 2022 07:15:19 CEST Vincent Bernat wrote:
> On 2022-10-29 00:50, Diederik de Haas wrote:
> >> The card works just fine with a 5.19 kernel after installing these files
> >> in /usr/lib/firmware/ath11k/WCN6855/hw2.0/:
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLA
> >> N.H SP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/amss.bin
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/1.1/WLA
> >> N.
> >> HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16/m3.bin
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/board-2
> >> .b
> >> in
> >> https://github.com/kvalo/ath11k-firmware/raw/master/WCN6855/hw2.0/regdb.b
> >> in
> >> 
> >> And then creating a symlink from /usr/lib/firmware/ath11k/WCN6855/hw2.1/
> >> to hw2.0/ .
> >> 
> >> (I do not understand the structure of the directories in
> >> WCN6855/hw2.0/1.1/, so I choose the newest files.)
> >> 
> >> Some other firmwares from
> >> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g
> >> it/tree/qca are needed for Bluetooth support and are missing as well:
> >> 
> >> qca/rampatch_usb_00130201.bin
> >> qca/nvm_usb_00130201_gf.bin
> > 
> > I found all the mentioned file names in the buildd log for 20220913-1, so
> > I guess the issue is fixed.
> > Can you verify that and update/close the bug accordingly?
> 
> They are not present.
> 
>   07:14 ❱ dpkg -L firmware-atheros | grep -E '(WCN6855|nvm_usb_00130201)'

Thanks for checking. It turned out my checks were 'incomplete'.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep&q=WCN6855
does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs
the referenced ...SILICONZ_LITE-3.6510.16.
And one commit is for symlinks to hw2.1

qca/rampatch_usb_00130201.bin is also present in the upstream repo, but 
searching for nvm_usb_00130201_gf.bin did not yield any results.

So this looks like upstream does have most of the needed files, albeit a
slightly older version?
I don't know if anything should be done based on this, but figured I'd share
my findings.

HTH,
  Diederik

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


Bug#1023025: linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!

2022-10-29 Thread Diederik de Haas
Control: tag -1 -a11y

On zaterdag 29 oktober 2022 12:33:59 CEST femenia wrote:
> Package: src:linux
> Version: 6.0.3-1
> Severity: grave
> Tags: a11y

I don't see how a11y is relevant here, so removing the tag

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


Processed: Re: Bug#1023025: linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!

2022-10-29 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 -a11y
Bug #1023025 [src:linux] linux-image-6.0.0-2-686: kernel BUG at 
mm/memory.c:2660!
Removed tag(s) a11y.

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



Processed: fixed 950271 in 1.8.6~rc2-1, reassign 1014283 to nvidia-tesla-driver, fixed 1014283 in 510.85.02-1 ...

2022-10-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # bts housekeeping
> fixed 950271 1.8.6~rc2-1
Bug #950271 {Done: Bastian Germann } [netperfmeter] Please 
provide a backported netperfmeter for Buster
Marked as fixed in versions netperfmeter/1.8.6~rc2-1.
> reassign 1014283 nvidia-tesla-driver 510.73.08-3
Bug #1014283 {Done: Andreas Beckmann } 
[nvidia-tesla-510-driver] nvidia-tesla-510-driver: nvidia-powerd is missing, 
but present in original driver
Bug reassigned from package 'nvidia-tesla-510-driver' to 'nvidia-tesla-driver'.
No longer marked as found in versions 
nvidia-graphics-drivers-tesla-510/510.73.08-3.
No longer marked as fixed in versions nvidia-graphics-drivers-tesla/510.85.02-1.
Bug #1014283 {Done: Andreas Beckmann } [nvidia-tesla-driver] 
nvidia-tesla-510-driver: nvidia-powerd is missing, but present in original 
driver
There is no source info for the package 'nvidia-tesla-driver' at version 
'510.73.08-3' with architecture ''
Unable to make a source version for version '510.73.08-3'
Marked as found in versions 510.73.08-3.
> fixed 1014283 510.85.02-1
Bug #1014283 {Done: Andreas Beckmann } [nvidia-tesla-driver] 
nvidia-tesla-510-driver: nvidia-powerd is missing, but present in original 
driver
Marked as fixed in versions nvidia-graphics-drivers-tesla/510.85.02-1.
> notfixed 1007580 1.2.1
Bug #1007580 {Done: Willem van den Akker } [src:gtkterm] 
gtkterm: please consider upgrading to 3.0 source format
The source 'gtkterm' and version '1.2.1' do not appear to match any binary 
packages
No longer marked as fixed in versions gtkterm/1.2.1.
> fixed 1007580 1.2.1-1
Bug #1007580 {Done: Willem van den Akker } [src:gtkterm] 
gtkterm: please consider upgrading to 3.0 source format
Marked as fixed in versions gtkterm/1.2.1-1.
> fixed 1017730 4.2.1-1
Bug #1017730 {Done: Alastair McKinstry } [src:pmix] pmix: 
drop Build-Depends: pandoc
Marked as fixed in versions pmix/4.2.1-1.
> fixed 878165 20190114-1
Bug #878165 {Done: maximilian attems } [firmware-iwlwifi] 
firmware-iwlwifi: Some firmware versions cause 8260 Bluetooth malfunction
Marked as fixed in versions firmware-nonfree/20190114-1.
> fixed 887932 20190114-1
Bug #887932 {Done: maximilian attems } [firmware-iwlwifi] 
firmware-iwlwifi: Bluetooth not working
Marked as fixed in versions firmware-nonfree/20190114-1.
> reassign 1016880 src:r-base
Bug #1016880 {Done: Dirk Eddelbuettel } [src:fbasics] fbasics: 
FTBFS on hppa - /usr/bin/ld: cannot find /usr/lib/gcc/hppa-linux-gnu/11/libgcc.a
Bug reassigned from package 'src:fbasics' to 'src:r-base'.
No longer marked as found in versions fbasics/3042.89.2-1.
No longer marked as fixed in versions r-base/4.2.1-2.
> fixed 1016880 4.2.1-2
Bug #1016880 {Done: Dirk Eddelbuettel } [src:r-base] fbasics: 
FTBFS on hppa - /usr/bin/ld: cannot find /usr/lib/gcc/hppa-linux-gnu/11/libgcc.a
Marked as fixed in versions r-base/4.2.1-2.
> affects 1016880 + src:fbasics
Bug #1016880 {Done: Dirk Eddelbuettel } [src:r-base] fbasics: 
FTBFS on hppa - /usr/bin/ld: cannot find /usr/lib/gcc/hppa-linux-gnu/11/libgcc.a
Added indication that 1016880 affects src:fbasics
> fixed 998055 2.1.0+ds1-1
Bug #998055 {Done: Reinhard Tartler } [conmon] Permission 
on /dev/null are changing from 666 to 777 after running podman as root
Marked as fixed in versions conmon/2.1.0+ds1-1.
> notfixed 998055 2.0.2-1
Bug #998055 {Done: Reinhard Tartler } [conmon] Permission 
on /dev/null are changing from 666 to 777 after running podman as root
No longer marked as fixed in versions 2.0.2-1.
> reassign 992162 src:calamares-settings-debian
Bug #992162 {Done: Jonathan Carter } [calamares] calamares: 
window starts too small, maybe caused by 200% HiDPI display
Bug reassigned from package 'calamares' to 'src: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.3-1.
> fixed 992162 12.0.3-1
Bug #992162 {Done: Jonathan Carter } 
[src:calamares-settings-debian] calamares: window starts too small, maybe 
caused by 200% HiDPI display
Marked as fixed in versions calamares-settings-debian/12.0.3-1.
> affects 992162 + src:calamares
Bug #992162 {Done: Jonathan Carter } 
[src:calamares-settings-debian] calamares: window starts too small, maybe 
caused by 200% HiDPI display
Added indication that 992162 affects src:calamares
> reassign 1005206 src:msgpack-cxx
Bug #1005206 {Done: James McCoy } [libmsgpack-dev] Split 
into separate C and C++ API packages
Bug reassigned from package 'libmsgpack-dev' to 'src:msgpack-cxx'.
No longer marked as found in versions msgpack-c/3.3.0-4.
No longer marked as fixed in versions msgpack-cxx/4.1.1-1.
> fixed 1005206 4.1.1-1
Bug #1005206 {Done: James McCoy } [src:msgpack-cxx] Split 
into separate C and C++ API packages
Marked as fixed in versions msgpack-cxx/4.1.1-1.
> affects 1005206 + libmsgpack-dev
Bug #1005206 {Done: James McCoy } [src:msgpack-cxx] Split 
into separate C and C++ API packages
Added indication that 1005206 affects libmsgpack-

Processing of linux_6.0.3-1~bpo11+1_source.changes

2022-10-29 Thread Debian FTP Masters
linux_6.0.3-1~bpo11+1_source.changes uploaded successfully to localhost
along with the files:
  linux_6.0.3-1~bpo11+1.dsc
  linux_6.0.3-1~bpo11+1.debian.tar.xz
  linux_6.0.3-1~bpo11+1_source.buildinfo

Greetings,

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



Bug#1022900: grub-install, efibootmgr etc. not working with new kernel

2022-10-29 Thread Stephan Verbücheln
For completeness: The problem persists with the new kernel in Sid.

> 6.0.0-2-amd64 / Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux



linux_6.0.3-1~bpo11+1_source.changes is NEW

2022-10-29 Thread Debian FTP Masters
binary:affs-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:affs-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:ata-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:btrfs-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:cdrom-core-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:crc-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:crypto-dm-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:crypto-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:dasd-extra-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:dasd-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:efi-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:event-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-4kc-malta-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-5kc-malta-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-armmp-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-loongson-3-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-marvell-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-mips32r2el-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-mips64r2el-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-octeon-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-powerpc64le-di is NEW.
binary:ext4-modules-6.0.0-0.deb11.2-s390x-di is NEW.
binary:f2fs-modules-6.0.0-0

Bug#1022848: linux: 6.0.5 fixes critical btrfs bug

2022-10-29 Thread Christoph Anton Mitterer
On Sat, 2022-10-29 at 09:23 +0200, Salvatore Bonaccorso wrote:
> 
> No unfortunately we cannot do that. The reason is similar to what
> lead
> to
> https://salsa.debian.org/kernel-team/linux/-/commit/248736d493fcfd0e05cd23f97befe40f5c125c71
> or caused bugs like #916927.

Forgive me my ignorance, but from the package's file list I'd assume
that the signatures are included in the kernel image respectively the
module files themselves?

Is that a must, or could they be standalone signatures?

Cause if the latter, wouldn't something like the following be possible:
- have only one package that actually contains the kernel and modules
  (and that would be available earlier)
- have that depend on a separate package that ships the standalone
  signatures

That would have the benefit that there are no "duplicate" packages, and
people could create a dummy for the signature package with e.g. equivs.

> The signed packages need always longer as this needs action of
> signing
> them trough a seprate manual process of ftp-masters.

Sure, clear.


Best wishes,
Chris.



Bug#1006500: marked as done (Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16)

2022-10-29 Thread Christoph Anton Mitterer
On Sat, 2022-10-29 at 09:44 +0200, Salvatore Bonaccorso wrote:
> We do similar with intel-microcode updates, so maybe this is
> something
> we should consider to. But I think it's to early to think about a
> potential 20220913-1~deb11u1 via a bullseye point release.

It's just that for any bullseye users, this NICs are in principle
broken (at least out of the box) right now.

Anyway... I guess it's not super urgent :-)


Cheers,
Chris.



Bug#1021157: missing firmwares for Qualcomm NFA725A

2022-10-29 Thread Vincent Bernat

On 2022-10-29 20:05, Diederik de Haas wrote:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/?qt=grep&q=WCN6855
does show various results which come very close ...SILICONZ_LITE-3.6510.7 vs
the referenced ...SILICONZ_LITE-3.6510.16.
And one commit is for symlinks to hw2.1

qca/rampatch_usb_00130201.bin is also present in the upstream repo, but
searching for nvm_usb_00130201_gf.bin did not yield any results.

So this looks like upstream does have most of the needed files, albeit a
slightly older version?
I don't know if anything should be done based on this, but figured I'd share
my findings.


I suppose the search engine only works for stuff mentioned directly in 
commit messages. The file present in the repository: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/qca/nvm_usb_00130201_gf.bin.




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

2022-10-29 Thread Gabriel Francisco
Package: linux-headers-6.0.0-2-amd64
Version: 6.0.3-1
Severity: normal
X-Debbugs-Cc: frc.gabr...@gmail.com

Dear Maintainer,

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.

This time I can see this message from dmesg:

[24504.576562] Bluetooth: hci0: RTL: fw version 0xd9a8a0cd
[24504.659770] r8169 :05:00.0 enp5s0: Link is Down
[24504.706018] Bluetooth: MGMT ver 1.22
[24506.722037] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[24509.160942] wlp3s0: authenticate with e4:bf:fa:cc:15:70
[24509.180111] wlp3s0: Invalid HE elem, Disable HE
[24509.299099] wlp3s0: send auth to e4:bf:fa:cc:15:70 (try 1/3)
[24509.305463] wlp3s0: authenticated
[24509.335739] wlp3s0: associate with e4:bf:fa:cc:15:70 (try 1/3)
[24509.337000] wlp3s0: RX AssocResp from e4:bf:fa:cc:15:70 (capab=0x1011 
status=0 aid=3)
[24509.448135] wlp3s0: associated
[24509.448274] wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 
e4:bf:fa:cc:15:70
[24509.512359] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[24510.633689] input: Shure AONIC TW2 (AVRCP) as /devices/virtual/input/input32
[24519.113962] audit: type=1400 audit(1667082607.529:55): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24519.173906] audit: type=1400 audit(1667082607.585:56): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24519.232356] audit: type=1400 audit(1667082607.645:57): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24519.241718] audit: type=1400 audit(1667082607.657:58): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cups-browsed" 
name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=2327 comm="cups-browsed" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[24554.003191] Bluetooth: hci0: Opcode 0x 402 failed: -16
[24595.999699] general protection fault, probably for non-canonical address 
0x867f:  [#1] PREEMPT SMP NOPTI
[24595.999706] CPU: 4 PID: 979 Comm: bluetoothd Not tainted 6.0.0-2-amd64 #1  
Debian 6.0.3-1
[24595.999708] Hardware name: LENOVO 21A4GE/21A4GE, BIOS R1MET49W (1.19 
) 06/27/2022
[24595.999710] RIP: 0010:hci_send_acl+0x21/0x2f0 [bluetooth]
[24595.999739] Code: cc cc 0f 1f 80 00 00 00 00 0f 1f 44 00 00 41 57 49 89 ff 
41 56 41 55 41 54 55 48 89 f5 53 48 83 ec 28 4c 8b 67 18 89 54 24 0c <4d> 8b 8c 
24 80 06 00 00 4c 89 4c 24 18 66 90 0f b7 da 8b 4d 70 2b
[24595.999740] RSP: 0018:a8c8817ffcc0 EFLAGS: 00010286
[24595.999742] RAX: 88da73ec RBX: 0003 RCX: 0003
[24595.999743] RDX:  RSI: 88db1cb2af00 RDI: 88d99e47de00
[24595.999745] RBP: 88db1cb2af00 R08: 88d99dc1f0c0 R09: 000c
[24595.999746] R10: 002a R11:  R12: 7fff
[24595.999746] R13: a8c8817ffe10 R14: 88db1cb2af00 R15: 88d99e47de00
[24595.999747] FS:  7f2851c0e7c0() GS:88df11f0() 
knlGS:
[24595.999749] CS:  0010 DS:  ES:  CR0: 80050033
[24595.999749] CR2: 55e4b0ec2300 CR3: 000107586000 CR4: 00750ee0
[24595.999750] PKRU: 5554
[24595.999751] Call Trace:
[24595.999754]  
[24595.999755]  ? mutex_lock+0xe/0x30
[24595.999761]  l2cap_chan_send+0x12f/0xc60 [bluetooth]
[24595.999787]  ? remove_wait_queue+0x20/0x60
[24595.999791]  ? _raw_spin_unlock_irqrestore+0x23/0x40
[24595.999793]  ? bt_sock_wait_ready+0x128/0x1a0 [bluetooth]
[24595.999812]  l2cap_sock_sendmsg+0x9a/0x100 [bluetooth]
[24595.999833]  sock_sendmsg+0x5f/0x70
[24595.999836]  __sys_sendto+0x11c/0x170
[24595.999840]  __x64_sys_sendto+0x20/0x30
[24595.999841]  do_syscall_64+0x3a/0xc0
[24595.999844]  entry_SYSCALL_64_after_hwframe+0x63/0xcd
[24595.999846] RIP: 0033:0x7f2851b0c2fc
[24595.999848] Code: 02 eb bd 66 2e 0f 1f 84 00 00 00 00 00 90 41 89 ca 64 8b 
04 25 18 00 00 00 85 c0 75 19 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 64 c3 0f 1f 00 41 54 48 83 ec 20 48 89 54 24
[24595.999849] RSP: 002b:7ffd5ae68d68 EFLAGS: 0246 ORIG_RAX: 
002c
[24595.999851] RAX: ffda RBX: 55ceb8074290 RCX: 7f2851b0c2fc
[24595.999852] RDX: 0003 RSI: 55ceb80326b0 RDI: 002a
[24595.999852] RBP: 0003 R08:  R09: 
[24595.999853] R10:  R11: 0246 R12: 55ceb80326b0
[24595.999854] R13: 002a R14: 55ceb8074290 R15: 55ceb8032e60
[2459

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

2022-10-29 Thread Diederik de Haas
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?


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


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

2022-10-29 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 src:linux 6.0.3-1
Bug #1023076 [linux-headers-6.0.0-2-amd64] linux-headers-6.0.0-2-amd64: 
bluetooth crashes after returning from suspend
Bug reassigned from package 'linux-headers-6.0.0-2-amd64' to 'src:linux'.
No longer marked as found in versions linux/6.0.3-1.
Ignoring request to alter fixed versions of bug #1023076 to the same values 
previously set
Bug #1023076 [src:linux] linux-headers-6.0.0-2-amd64: bluetooth crashes after 
returning from suspend
Marked as found in versions linux/6.0.3-1.
> severity -1 important
Bug #1023076 [src:linux] linux-headers-6.0.0-2-amd64: bluetooth crashes after 
returning from suspend
Severity set to 'important' from 'normal'

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



Bug#1017977: Fails to load intel/ibt-20-1-3.sfi

2022-10-29 Thread Olaf Meeuwissen
> Package: linux-image-5.18.0-4-amd64
> Severity: important
>
> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
> Used that to report this bug as the failure to load leaves me without a
> working keyboard.  It's a bluetooth-only keyboard and it not working at
> all is why I've marked this important.

I just want to add that this is still an issue with 6.0.0-2.  Exact same
symptoms.  Keyboard is useless when booting after a poweroff.  Booting
into 5.18.0-3 restores keyboard usability.  A subsequent *reboot* to the
latest linux-image version, as opposed to a poweroff+boot, leaves the
keyboard in a usable state.

Hope this helps,
--
Olaf Meeuwissen



Bug#1013211: problem is gone

2022-10-29 Thread Douglas Silva
I can no longer reproduce this. Currently running Ubuntu 22.10 with kernel 
5.19.0-23-generic. C-states enabled in the BIOS.



Bug#1023085: fails to load on Wireless-AC 9260

2022-10-29 Thread Ash Joubert
Package: firmware-iwlwifi
Version: 20220913-1
Severity: important
X-Debbugs-Cc: a...@transient.nz

Dear Maintainer,

firmware-iwlwifi 20220913-1 fails to load on Intel Corporation Wireless-AC 9260
(rev 29), breaking network connectivity. Downgrading to firmware-iwlwifi
20210818-1, running "update-initramfs -u", and rebooting restores network
connectivity. Relevant log entries attached.

Kind regards,
Ash.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.142

-- no debconf information
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: enabling device ( -> 
0002)
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: firmware: direct-loading 
firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 0
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 1
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 2
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 3
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 4
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 6
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 8
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 9
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
10
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
11
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
15
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
16
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
18
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
19
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
20
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
21
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: WRT: Overriding region id 
28
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
Oct 30 16:15:00 ripley kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: loaded firmware version 
46.9d0122c0.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
Oct 30 16:15:00 ripley kernel: iwlwifi :01:00.0: Detected Intel(R) 
Wireless-AC 9260 160MHz, REV=0x321
Oct 30 16:15:01 ripley kernel: [ cut here ]
Oct 30 16:15:01 ripley kernel: Timeout waiting for hardware access 
(CSR_GP_CNTRL 0x)
Oct 30 16:15:01 ripley kernel: WARNING: CPU: 7 PID: 781 at 
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2128 
__iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi]
Oct 30 16:15:01 ripley kernel: Modules linked in: iwlmvm(+) ipt_REJECT 
nf_reject_ipv4 mac80211 xt_tcpudp libarc4 xt_conntrack nf_conntrack qrtr 
nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter>
Oct 30 16:15:01 ripley kernel:  jbd2 btrfs blake2b_generic zstd_compress 
dm_crypt dm_mod efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq lib>
Oct 30 16:15:01 ripley kernel: CPU: 7 PID: 781 Comm: modprobe Not tainted 
6.0.0-2-amd64 #1  Debian 6.0.5-1
Oct 30 16:15:01 ripley kernel: Hardware name: System manufacturer System 
Product Name/H110I-PLUS, BIOS 4212 07/24/2019
Oct 30 16:15:01 ripley kernel: RIP: 
0010:__iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi]
Oct 30 16:15:01 ripley kernel: Code: 48 89 df e8 a3 db fe ff 4c 89 f7 e8 8b 95 
0c df e9 e3 fe ff ff 89 c6 48 c7 c7 b0 26 34 c1 c6 05 e5 57 03 00 01 e8 3b 20 
07 df <0f> 0b e9 01 ff ff ff 48>
Oct 30 16:15:01 ripley kernel: RSP: 0018:ab5240f6bb60 EFLAGS: 00010282
Oct 30 16:15:01 ripley kernel: RAX:  RBX: 8a2d8b928028 RCX: 

Oct 30 16:15:01 ripley kernel: RDX: 0202 RSI: a0b7ed12 RDI: 

Oct 30 16:15:01 ripley kernel: RBP:  R08:  R09: 
ab5240f6b9e8
Oct 30 16:15:01 ripley kernel: R10: 0003 R11: a12d2128 R12: 
0001
Oct 30 16:15:01 ripley kernel: R13:  R14: 8a2d8b92a974 R15: 
0011
Oct 30 16:15:01 ripley kernel: FS:  7fbf50890480() 
GS:8a30a6d