Re: Request: Enable Symbols for Lenovo Thinkpad P14s Gen4 (AMD)

2023-12-11 Thread Salvatore Bonaccorso
Hi Michael,

On Mon, Dec 11, 2023 at 06:36:39PM -0500, Michael T. Kloos wrote:
> > On Mon, Dec 11, 2023 at 04:20:21PM -0500, Michael T. Kloos wrote:
> >> I have recently acquired a new Lenovo Thinkpad P14s Gen4 (AMD) laptop.  
> >> Nearly 
> >> everything worked out of the box on Debian expect for the build-in 
> >> microphone.  
> >> To get that working, I needed to rebuild the kernel with the following 
> >> symbols 
> >> enabled: 
> >>
> >> CONFIG_SND_SOC_AMD_PS=m
> >> CONFIG_SND_SOC_AMD_PS_MACH=m
> >>
> >> I'm not familar with how Debian decides what to enable in their Kernels, 
> >> but I 
> >> would like to request these symbols be enabled upstream.  
> > This change is already pending in the packaging repository:
> > https://salsa.debian.org/kernel-team/linux/-/commit/64417bdec91911a83f5b575561e63d1494a94492
> > Cf. https://bugs.debian.org/1055649
> >
> > Regards,
> > Salvatore
> 
> Copy that.

Michael, sorry I lost you. What do you mean?

Regards,
Salvatore



Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Steve VanDevender
Salvatore Bonaccorso writes:
 > Control: tags -1 + moreinfo
 > 
 > Hi Steve,
 > 
 > On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote:
 > > Package: src:linux
 > > Version: 6.1.66-1
 > > Severity: grave
 > > Tags: upstream
 > > Justification: renders package unusable
 > > 
 > > I would have tried to report this from the 6.1.66 kernel but once a
 > > suspend is attempted network access is also broken so I have had to
 > > reboot into a working kernel in order to report the bug.
 > > 
 > > The problem may be related to the wireless network drivers since some
 > > processes that can't be frozen for suspend are NetworkManager,
 > > wpa-supplicant, and iw.
 > > 
 > > I have included boot messages from the affected kernel through an
 > > attempt to suspend the system including the traces from the processes
 > > that seem to get wedged by an attempt to suspend.
 >
 > I cannot test for the regression explicitly myself, but 6.1.67 was
 > released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for
 > non-range use""). Would you be in the position of do a test build with
 > that commit (or with 6.1.67 upstream) to verify your issue goes away?

I was able to build a test kernel from the Debian sources for 6.1.66
and the patch from 6.1.67 (thanks to Diederik's instructions) and
install it on my laptop and it does solve the problem with
suspend/resume.

I did forget to include that this problem must have been introduced
after 6.1.64 (which I ran for a few days) since that kernel version
did not have the suspend/resume problem.  But the commit reverted in
6.1.67 was clearly the cause of the problem.

 > Regards,
 > Salvatore



Bug#1058072: linux-image-6.5.0-0.deb12.1-amd64: Backport 6.5 kernel for bookworm is very good

2023-12-11 Thread debian user
Package: src:linux
Version: 6.5.3-1~bpo12+1
Severity: wishlist
Tags: upstream

Dear Maintainer,

$ uptime
 19:56:14 up 27 days,  8:01,  3 users,  load average: 0.69, 0.49, 0.45

$ apt policy linux-image-6.5.0-0.deb12.1-amd64
linux-image-6.5.0-0.deb12.1-amd64:
  Installed: 6.5.3-1~bpo12+1
  Candidate: 6.5.3-1~bpo12+1
  Version table:
 *** 6.5.3-1~bpo12+1 100
100 /var/lib/dpkg/status

I wish you the the best.  I wish you all the best.

Thanks,
bw

-- Package-specific info:
** Version:
Linux version 6.5.0-0.deb12.1-amd64 (debian-kernel@lists.debian.org) (gcc-12 
(Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.5.3-1~bpo12+1 (2023-10-08)

** Command line:
BOOT_IMAGE=/vmlinuz root=UUID=2c03d937-09c2-4f1f-9d40-4901f2cdd3f0 ro quiet 
splash loglevel=3

** Tainted: W (512)
 * kernel issued warning

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

** Model information
sys_vendor: HP
product_name: HP Laptop 15-ef2xxx
product_version: 
chassis_vendor: HP
chassis_version: Chassis Version
bios_vendor: AMI
bios_version: F.30
board_vendor: HP
board_name: 887A
board_version: 59.22

** Loaded modules:
sr_mod
cdrom
ccm
xpad
ff_memless
rfcomm
cmac
algif_hash
algif_skcipher
af_alg
ipheth
qrtr
bnep
intel_rapl_msr
sunrpc
intel_rapl_common
binfmt_misc
btusb
btrtl
btbcm
nls_ascii
edac_mce_amd
snd_ctl_led
btintel
nls_cp437
snd_hda_codec_realtek
kvm_amd
btmtk
snd_hda_codec_generic
vfat
bluetooth
ledtrig_audio
kvm
snd_hda_codec_hdmi
rtw88_8822ce
fat
snd_hda_intel
rtw88_8822c
irqbypass
sha3_generic
snd_soc_dmic
snd_acp3x_pdm_dma
snd_acp3x_rn
uvcvideo
snd_intel_dspcfg
rtw88_pci
jitterentropy_rng
ghash_clmulni_intel
snd_soc_core
videobuf2_vmalloc
snd_intel_sdw_acpi
rtw88_core
snd_hda_codec
sha512_ssse3
snd_compress
uvc
sha512_generic
snd_hda_core
videobuf2_memops
snd_pci_acp6x
ctr
snd_hwdep
mac80211
videobuf2_v4l2
snd_pci_acp5x
aesni_intel
drbg
hp_wmi
snd_pcm
videodev
libarc4
snd_rn_pci_acp3x
crypto_simd
ansi_cprng
sparse_keymap
snd_timer
snd_acp_config
videobuf2_common
cryptd
ecdh_generic
cfg80211
joydev
sp5100_tco
platform_profile
snd
snd_soc_acpi
apple_mfi_fastcharge
mc
rapl
ecc
wmi_bmof
pcspkr
k10temp
watchdog
rfkill
soundcore
ccp
snd_pci_acp3x
sg
ac
amd_pmc
acpi_tad
hid_multitouch
serio_raw
evdev
msr
parport_pc
ppdev
lp
parport
fuse
loop
efi_pstore
dm_mod
configfs
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
btrfs
blake2b_generic
xor
raid6_pq
libcrc32c
crc32c_generic
sd_mod
ums_realtek
uas
usb_storage
amdgpu
scsi_mod
scsi_common
amdxcp
drm_buddy
gpu_sched
i2c_algo_bit
nvme
drm_suballoc_helper
nvme_core
drm_display_helper
t10_pi
cec
crc64_rocksoft
rc_core
crc64
xhci_pci
drm_ttm_helper
crc_t10dif
xhci_hcd
ttm
hid_generic
crct10dif_generic
usbcore
drm_kms_helper
crct10dif_pclmul
crc32_pclmul
i2c_hid_acpi
video
i2c_hid
drm
crc32c_intel
i2c_piix4
usb_common
crct10dif_common
battery
button
wmi
hid

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Hewlett-Packard Company Renoir/Cezanne Root Complex 
[103c:887a]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP 
Bridge [1022:1453]
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:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 51)
Subsystem: Advanced Micro Devices, Inc. 

Re: Request: Enable Symbols for Lenovo Thinkpad P14s Gen4 (AMD)

2023-12-11 Thread Michael T. Kloos
> On Mon, Dec 11, 2023 at 04:20:21PM -0500, Michael T. Kloos wrote:
>> I have recently acquired a new Lenovo Thinkpad P14s Gen4 (AMD) laptop.  
>> Nearly 
>> everything worked out of the box on Debian expect for the build-in 
>> microphone.  
>> To get that working, I needed to rebuild the kernel with the following 
>> symbols 
>> enabled: 
>>
>> CONFIG_SND_SOC_AMD_PS=m
>> CONFIG_SND_SOC_AMD_PS_MACH=m
>>
>> I'm not familar with how Debian decides what to enable in their Kernels, but 
>> I 
>> would like to request these symbols be enabled upstream.  
> This change is already pending in the packaging repository:
> https://salsa.debian.org/kernel-team/linux/-/commit/64417bdec91911a83f5b575561e63d1494a94492
> Cf. https://bugs.debian.org/1055649
>
> Regards,
> Salvatore

Copy that.



Re: Request: Enable Symbols for Lenovo Thinkpad P14s Gen4 (AMD)

2023-12-11 Thread Salvatore Bonaccorso
Hi,

On Mon, Dec 11, 2023 at 04:20:21PM -0500, Michael T. Kloos wrote:
> I have recently acquired a new Lenovo Thinkpad P14s Gen4 (AMD) laptop.  
> Nearly 
> everything worked out of the box on Debian expect for the build-in 
> microphone.  
> To get that working, I needed to rebuild the kernel with the following 
> symbols 
> enabled: 
> 
> CONFIG_SND_SOC_AMD_PS=m
> CONFIG_SND_SOC_AMD_PS_MACH=m
> 
> I'm not familar with how Debian decides what to enable in their Kernels, but 
> I 
> would like to request these symbols be enabled upstream.  

This change is already pending in the packaging repository:
https://salsa.debian.org/kernel-team/linux/-/commit/64417bdec91911a83f5b575561e63d1494a94492
Cf. https://bugs.debian.org/1055649

Regards,
Salvatore



Request: Enable Symbols for Lenovo Thinkpad P14s Gen4 (AMD)

2023-12-11 Thread Michael T. Kloos
I have recently acquired a new Lenovo Thinkpad P14s Gen4 (AMD) laptop.  Nearly 
everything worked out of the box on Debian expect for the build-in microphone.  
To get that working, I needed to rebuild the kernel with the following symbols 
enabled: 

CONFIG_SND_SOC_AMD_PS=m
CONFIG_SND_SOC_AMD_PS_MACH=m

I'm not familar with how Debian decides what to enable in their Kernels, but I 
would like to request these symbols be enabled upstream.  

Thank you, 

Michael





Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Kevin Price
Breaking news:

Am 11.12.23 um 19:14 schrieb Salvatore Bonaccorso:
> I have put binary packages for amd64 built in
> https://people.debian.org/~carnil/tmp/linux/1057967/

I confirm this test kernel is working fine for me, even with non-free
broadcom-sta.

(sent from
"
cat /proc/version

Linux version 6.1.0-0.a.test-amd64 (debian-kernel@lists.debian.org)
(gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian)
2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1a~test (2023-12-11)
"

through

"
modinfo wl

filename:   /lib/modules/6.1.0-0.a.test-amd64/updates/dkms/wl.ko
license:MIXED/Proprietary
alias:  pci:v*d*sv*sd*bc02sc80i*
depends:cfg80211
…"
)

Thank you Salvatore. Let's get this into stable soon.
-- 
Kevin Price



Bug#1058052: linux-image-6.1.0-15-amd64 breaks suspend

2023-12-11 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo

Hi,

On Mon, Dec 11, 2023 at 04:02:16PM -0300, Dr. André Desgualdo Pereira wrote:
> Package: src:linux
> Version: 6.1.66-1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>Updating the kernel.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>Booting from an older kernel fix the issue.
>* What was the outcome of this action?
>Bug is fixed by using an older kernel version.
>* What outcome did you expect instead?
>I expect updating the kernel doesn't break functionality.
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached

Can you please attach the boot logs as well, which might be including
traces we are interested in to better understand the problem?

Regards,
Salvatore



Processed: Re: Bug#1058052: linux-image-6.1.0-15-amd64 breaks suspend

2023-12-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #1058052 [src:linux] linux-image-6.1.0-15-amd64 breaks suspend
Added tag(s) moreinfo.

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



Processed: closing 1058028

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 1058028
Bug #1058028 [src:linux] linux-image-6.1.0-14-amd64 breaks suspend
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#1057843: linux: ext4 data corruption in 6.1.64-1

2023-12-11 Thread Salvatore Bonaccorso
As there were some questions along in this thread let me summarize
some points:

The issue affects fs/ext4 code, so no other filesystems are affected
(e.g. btrfs).

The issue affects all kernels which have the commit 91562895f803
("ext4: properly sync file size update after O_SYNC direct IO") from
6.7-rc1 (which is present in 6.6.3, 6.5.13 and 6.1.64) but when commit
936e114a245b ("iomap: update ki_pos a little later in
iomap_dio_complete") from 6.5-rc1 is missing (which was backported to
5.15.142 and 6.1.66 additionally).

The only upstream combination where that reverse and missing commit
happened was 6.1.64 and 6.1.65. 

Debian is affected as per 6.1.64-1 upload which was the kernel aimed
for 12.3 point release.

The issue affects file corruption when direct IO writes are involved.
O_DIRECT writes did not properly update current file position after
the write so data and file was getting mangled.

While this does not affect every write ever happend on the system on a
ext4 filesystem with a broken kernel, O_DIRECT writes might be quite
common in in programms trying to get high performance. It might be
argued that it is not that common, but it's not inexistant.

TTOMK, such file corruptions cannot be easily detected. Candidates to
check are every modified file written since booted with the broken
kernel 6.1.64-1.

Poeple still not having booted into 6.1.66-1 are urged to do so.

Regards,
Salvatore



Bug#1058052: linux-image-6.1.0-15-amd64 breaks suspend

2023-12-11 Thread Dr . André Desgualdo Pereira
Package: src:linux
Version: 6.1.66-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   Updating the kernel.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Booting from an older kernel fix the issue.
   * What was the outcome of this action?
   Bug is fixed by using an older kernel version.
   * What outcome did you expect instead?
   I expect updating the kernel doesn't break functionality.

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


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

** Model information
sys_vendor: CLEVO
product_name: P150HMx
product_version: Not Applicable
chassis_vendor: CLEVO   
chassis_version: Not Applicable
bios_vendor: American Megatrends Inc.
bios_version: 4.6.4
board_vendor: CLEVO
board_name: P150HMx
board_version: Not Applicable

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: CLEVO/KAPOK Computer 2nd Generation Core Processor Family 
DRAM Controller [1558:5102]
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 E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [1558:5102]
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:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family MEI 
Controller [1558:5102]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) (prog-if 20 [EHCI])
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family USB 
Enhanced Host Controller [1558:5102]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family 
High Definition Audio Controller [1558:5102]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 [8086:1c10] (rev b5) (prog-if 00 [Normal decode])
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 [1558:5102]
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:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 2 [8086:1c12] (rev b5) (prog-if 00 [Normal decode])
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 [1558:5102]
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:1c.2 PCI bridge [0604]: Intel 

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Salvatore Bonaccorso
Hi,

On Mon, Dec 11, 2023 at 01:27:07PM +0100, Kevin Price wrote:
> Thank you Salvatore!
> 
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> > It still would be helpfull if you can get to the logs of the previous
> > boot. After booting back in the working kernel, do you have anything
> > sensible logged in the previous boot log? If so can you share that
> > please?
> 
> Sure. Here's my boot.log.

I was more interested to get some nformation from the kernel. If you
get dmesg output that would be good, maybe the journalctl from the bug
otherwise, which will help to get more context.

> 
> The first one at "Mon Dec 11 00:54:03 CET 2023" is the faulty 6.1.0-15.
> 
> The 2nd one at "Mon Dec 11 01:13:38 CET 2023" is the working 6.1.0-13.
> 
> Need any more logfiles or testing? I intend to test
> debian-live-12.4.0-amd64-gnome.iso on my computer, IOT rule out any
> local config peculiarities, FWIW.
> 
> > I'm right now curious to find out if we see the same as
> > #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> > cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> > issue.
> 
> Please let me know what kernel version you want me to test, if they're
> provides as debian binaries. I'd be glad to help, probably not only for
> my own sake. Bear with me I'm unwilling to build kernel packages myself,
> due to lack of computing resources. HTH

I have put binary packages for amd64 built in
https://people.debian.org/~carnil/tmp/linux/1057967/

*but* they are completely unofficial builds. To give assurance of
provenance I have generated a sha256sum file as well for the uploaded
files and signed it with my key in the Debian keyring.

If you personal policy allows you to install such packages please test
with those, otherwise we need you to have built your own packages.

Regards,
Salvatore



Bug#1057843: Bug patching

2023-12-11 Thread Sergiu
Hi

Any new information, when will this be patched?
There are packages that can not be installed like nvidia-driver because
while installing it updates the system and the process fails.

Isn't possible to remove from the repo the corrupted kernel so that people
can install other packages?


Regards,
Sergiu


[bts-link] source package firmware-nonfree

2023-12-11 Thread debian-bts-link
#
# bts-link upstream status pull for source package firmware-nonfree
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #1057656 (http://bugs.debian.org/1057656)
# Bug title: firmware-amd-graphics: No display on Raphael in 20230625-1, please 
revert DMCUB updates
#  * https://gitlab.freedesktop.org/drm/amd/-/issues/2666
#  * remote status changed: (?) -> closed
usertags 1057656 + status-closed

thanks



Bug#1057843: linux: ext4 data corruption in 6.1.64-1

2023-12-11 Thread Dennis Grevenstein
On Mon, 11 Dec 2023 10:38:40 +0100 helios.sola...@gmx.ch wrote:
> I have been running debian 12.3 with kernel 6.1.64-1 for a few hours,
> how can I find out whether the file system has been corrupted?

yes, I would also appreciate an explanation who could be affected,
how to diagnose the problem, and what needs to be done.
Please note that not all the users of Debian stable are kernel hackers
who will be able to look at the filesystem code and understand the
full extent of the problem.

thanks,
Dennis



Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Kevin Price
Control: affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64

@other affected users: What wifi drivers are you using, and do they
taint your kernel?

Am 11.12.23 um 13:27 schrieb Kevin Price:
> Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:

> Need any more logfiles or testing?

Is it syslog that might help you better, or any other log? Just let me
know please. I'd love to help figure this out with mutual support.

> I intend to test debian-live-12.4.0-amd64-gnome.iso

*drumroll* Now this comes as a surprise to me.
debian-live-12.4.0-amd64-gnome displays none of the bad behavior, even
when actively using wifi. Apart from firmware, there's no non-free
involved in debian-live.

So could it be just some local configuration choice of mine, and of all
the other affected users? Some years-old but possibly now poor choice of
drivers/firmware maybe? I faintly remember having tried a free driver on
this card at least two debian releases ago, but it worked so bad I had
to switch to a non-free one:
https://packages.debian.org/bookworm/broadcom-sta-dkms

Which since has been upgraded with each debian release.

Another Test: My old hardware has a physical RF kill switch. So I booted
up 6.1.0-15 with it turned off: *drumroll* Works fine. So wifi seems to
be singled out as the culprit in my case. (or possibly bluetooth, but I
strongly doubt)

See attachments regarding my wifi. Shame on me, if anyone ever
suggested: "Never file a bug against a tainted kernel", because I did.
But maybe it was good to do so. Because this bug is still very relevant,
as it affects not only me, but renders multiple people's computers
practically unusable when upgrading to 6.1.0-15. Not like "wifi gone
bad", but "computer gone bad". This shouldn't happen within a stable
debian release IMHO, and thus justifies some fairly high level of
severity, IMHO. "critical", IDK. You own this bug, you decide.

Now I conclude that 6.1.0-15 not only breaks src:broadcom-sta, but also
vice versa. Are there any other wifi drivers affected?

>> I'm right now curious to find out if we see the same as
>> #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
>> cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
>> issue.

Now that sounds to me like exactly what caused this. Good to know that
upstream has already reverted this regression. Please let me know what
else to test or contribute, so that we can look forward to a debian
stable 6.1 kernel without this bug.

@Salvatore: Thanks a ton for your excellent work. Very much appreciated.

HTH
-- 
Kevin Pricesudo lspci -vvs2:0
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn 
Wireless Network Adapter (rev 01)
Subsystem: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless 
Network Adapter
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
Address:   Data: 
Capabilities: [d0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 
unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- 
SlotPowerLimit 10W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ 
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L1, Exit Latency 
L1 <64us
ClockPM+ Surprise- LLActRep+ BwNot- ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1
TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
Capabilities: [100 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
AdvNonFatalErr-
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- 
ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog:    
Capabilities: [13c v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
  

Processed: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + src:broadcom-sta linux-image-6.1.0-15-amd64
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Added indication that 1057967 affects src:broadcom-sta and 
linux-image-6.1.0-15-amd64

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



Bug#1057967: Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Diederik de Haas
On Monday, 11 December 2023 12:29:01 CET Salvatore Bonaccorso wrote:
> I cannot test for the regression explicitly myself, but 6.1.67 was
> released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for
> non-range use""). Would you be in the position of do a test build with
> that commit (or with 6.1.67 upstream) to verify your issue goes away?

On Monday, 11 December 2023 12:37:44 CET Salvatore Bonaccorso wrote:
> I'm right now curious to find out if we see the same as
> #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> issue.

https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
describes an easy way to test it and the patch you should use is attached.From db46c77f3d51d24402731ea181b2a591e7dd1ac3 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman 
Date: Mon, 11 Dec 2023 10:16:15 +0100
Subject: [PATCH] Revert "wifi: cfg80211: fix CQM for non-range use"
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This reverts commit 307a6525c82a5a1bc5364711ece92c2d2487e1ad which is
commit 7e7efdda6adb385fbdfd6f819d76bc68c923c394 upstream.

It needed to have commit 076fc8775daf ("wifi: cfg80211: remove wdev
mutex") applied to properly work, otherwise regressions happen.

Link: https://lore.kernel.org/r/e374bb16-5b13-44cc-b11a-2f4eefb1e...@manjaro.org
Link: https://lore.kernel.org/r/87sf4belmm@turtle.gmx.de
Link: https://lore.kernel.org/r/20231210213930.61378-1-...@leolam.fr
Reported-by: L??o Lam 
Reported-by: Sven Joachim 
Reported-by: Philip M??ller 
Cc: Johannes Berg 
Signed-off-by: Greg Kroah-Hartman 
---
 net/wireless/core.h|  1 -
 net/wireless/nl80211.c | 50 --
 2 files changed, 19 insertions(+), 32 deletions(-)

diff --git a/net/wireless/core.h b/net/wireless/core.h
index ee980965a7cf..e1accacc6f23 100644
--- a/net/wireless/core.h
+++ b/net/wireless/core.h
@@ -297,7 +297,6 @@ struct cfg80211_cqm_config {
 	u32 rssi_hyst;
 	s32 last_rssi_event_value;
 	enum nl80211_cqm_rssi_threshold_event last_rssi_event_type;
-	bool use_range_api;
 	int n_rssi_thresholds;
 	s32 rssi_thresholds[];
 };
diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
index 42c858219b34..b19b5acfaf3a 100644
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@ -12574,6 +12574,10 @@ static int cfg80211_cqm_rssi_update(struct cfg80211_registered_device *rdev,
 	int i, n, low_index;
 	int err;
 
+	/* RSSI reporting disabled? */
+	if (!cqm_config)
+		return rdev_set_cqm_rssi_range_config(rdev, dev, 0, 0);
+
 	/*
 	 * Obtain current RSSI value if possible, if not and no RSSI threshold
 	 * event has been received yet, we should receive an event after a
@@ -12648,6 +12652,18 @@ static int nl80211_set_cqm_rssi(struct genl_info *info,
 	wdev->iftype != NL80211_IFTYPE_P2P_CLIENT)
 		return -EOPNOTSUPP;
 
+	if (n_thresholds <= 1 && rdev->ops->set_cqm_rssi_config) {
+		if (n_thresholds == 0 || thresholds[0] == 0) /* Disabling */
+			return rdev_set_cqm_rssi_config(rdev, dev, 0, 0);
+
+		return rdev_set_cqm_rssi_config(rdev, dev,
+		thresholds[0], hysteresis);
+	}
+
+	if (!wiphy_ext_feature_isset(>wiphy,
+ NL80211_EXT_FEATURE_CQM_RSSI_LIST))
+		return -EOPNOTSUPP;
+
 	if (n_thresholds == 1 && thresholds[0] == 0) /* Disabling */
 		n_thresholds = 0;
 
@@ -12655,20 +12671,6 @@ static int nl80211_set_cqm_rssi(struct genl_info *info,
 	old = rcu_dereference_protected(wdev->cqm_config,
 	lockdep_is_held(>mtx));
 
-	/* if already disabled just succeed */
-	if (!n_thresholds && !old)
-		return 0;
-
-	if (n_thresholds > 1) {
-		if (!wiphy_ext_feature_isset(>wiphy,
-	 NL80211_EXT_FEATURE_CQM_RSSI_LIST) ||
-		!rdev->ops->set_cqm_rssi_range_config)
-			return -EOPNOTSUPP;
-	} else {
-		if (!rdev->ops->set_cqm_rssi_config)
-			return -EOPNOTSUPP;
-	}
-
 	if (n_thresholds) {
 		cqm_config = kzalloc(struct_size(cqm_config, rssi_thresholds,
 		 n_thresholds),
@@ -12683,26 +12685,13 @@ static int nl80211_set_cqm_rssi(struct genl_info *info,
 		memcpy(cqm_config->rssi_thresholds, thresholds,
 		   flex_array_size(cqm_config, rssi_thresholds,
    n_thresholds));
-		cqm_config->use_range_api = n_thresholds > 1 ||
-	!rdev->ops->set_cqm_rssi_config;
 
 		rcu_assign_pointer(wdev->cqm_config, cqm_config);
-
-		if (cqm_config->use_range_api)
-			err = cfg80211_cqm_rssi_update(rdev, dev, cqm_config);
-		else
-			err = rdev_set_cqm_rssi_config(rdev, dev,
-		   thresholds[0],
-		   hysteresis);
 	} else {
 		RCU_INIT_POINTER(wdev->cqm_config, NULL);
-		/* if enabled as range also disable via range */
-		if (old->use_range_api)
-			err = rdev_set_cqm_rssi_range_config(rdev, dev, 0, 0);
-		else
-			err = rdev_set_cqm_rssi_config(rdev, dev, 0, 0);
 	}
 
+	err = cfg80211_cqm_rssi_update(rdev, dev, cqm_config);
 	if (err) {
 		rcu_assign_pointer(wdev->cqm_config, old);
 		

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Grand T
Hello
Up to now 6.1.67 is not available for my configuration

apt list | grep linux-image-6.1*

linux-image-6.1.0-11-686-dbg/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-pae-dbg/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-pae-unsigned/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-pae/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686-unsigned/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-686/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-amd64-dbg/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-amd64-unsigned/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-amd64/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-cloud-amd64-dbg/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-cloud-amd64-unsigned/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-cloud-amd64/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-rt-686-pae-dbg/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-rt-686-pae-unsigned/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-rt-686-pae/stable-security 6.1.38-4 i386
linux-image-6.1.0-11-rt-amd64-dbg/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-rt-amd64-unsigned/stable-security 6.1.38-4 amd64
linux-image-6.1.0-11-rt-amd64/stable-security 6.1.38-4 amd64
linux-image-6.1.0-12-686-dbg/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-pae-dbg/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-pae-unsigned/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-pae/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686-unsigned/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-686/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-amd64-dbg/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-amd64-unsigned/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-amd64/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-cloud-amd64-dbg/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-cloud-amd64-unsigned/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-cloud-amd64/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-rt-686-pae-dbg/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-rt-686-pae-unsigned/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-rt-686-pae/stable-security 6.1.52-1 i386
linux-image-6.1.0-12-rt-amd64-dbg/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-rt-amd64-unsigned/stable-security 6.1.52-1 amd64
linux-image-6.1.0-12-rt-amd64/stable-security 6.1.52-1 amd64
linux-image-6.1.0-13-686-dbg/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-pae-dbg/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-pae-unsigned/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-pae/stable 6.1.55-1 i386
linux-image-6.1.0-13-686-unsigned/stable 6.1.55-1 i386
linux-image-6.1.0-13-686/stable 6.1.55-1 i386
linux-image-6.1.0-13-amd64-dbg/stable 6.1.55-1 amd64
linux-image-6.1.0-13-amd64-unsigned/stable 6.1.55-1 amd64
linux-image-6.1.0-13-amd64/stable,now 6.1.55-1 amd64  [installé]
linux-image-6.1.0-13-cloud-amd64-dbg/stable 6.1.55-1 amd64
linux-image-6.1.0-13-cloud-amd64-unsigned/stable 6.1.55-1 amd64
linux-image-6.1.0-13-cloud-amd64/stable 6.1.55-1 amd64
linux-image-6.1.0-13-rt-686-pae-dbg/stable 6.1.55-1 i386
linux-image-6.1.0-13-rt-686-pae-unsigned/stable 6.1.55-1 i386
linux-image-6.1.0-13-rt-686-pae/stable 6.1.55-1 i386
linux-image-6.1.0-13-rt-amd64-dbg/stable 6.1.55-1 amd64
linux-image-6.1.0-13-rt-amd64-unsigned/stable 6.1.55-1 amd64
linux-image-6.1.0-13-rt-amd64/stable 6.1.55-1 amd64
linux-image-6.1.0-14-amd64/now 6.1.64-1 amd64  [installé, local]
linux-image-6.1.0-15-686-dbg/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-pae-dbg/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-pae-unsigned/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-pae/stable 6.1.66-1 i386
linux-image-6.1.0-15-686-unsigned/stable 6.1.66-1 i386
linux-image-6.1.0-15-686/stable 6.1.66-1 i386
linux-image-6.1.0-15-amd64-dbg/stable 6.1.66-1 amd64
linux-image-6.1.0-15-amd64-unsigned/stable 6.1.66-1 amd64
linux-image-6.1.0-15-amd64/stable 6.1.66-1 amd64
linux-image-6.1.0-15-cloud-amd64-dbg/stable 6.1.66-1 amd64
linux-image-6.1.0-15-cloud-amd64-unsigned/stable 6.1.66-1 amd64
linux-image-6.1.0-15-cloud-amd64/stable 6.1.66-1 amd64
linux-image-6.1.0-15-rt-686-pae-dbg/stable 6.1.66-1 i386
linux-image-6.1.0-15-rt-686-pae-unsigned/stable 6.1.66-1 i386
linux-image-6.1.0-15-rt-686-pae/stable 6.1.66-1 i386
linux-image-6.1.0-15-rt-amd64-dbg/stable 6.1.66-1 amd64
linux-image-6.1.0-15-rt-amd64-unsigned/stable 6.1.66-1 amd64
linux-image-6.1.0-15-rt-amd64/stable 6.1.66-1 amd64
linux-image-6.5.0-5-686-dbg/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-pae-dbg/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-pae-unsigned/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-pae/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686-unsigned/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-686/unstable,testing 6.5.13-1 i386
linux-image-6.5.0-5-amd64-dbg/unstable,testing 6.5.13-1 amd64
linux-image-6.5.0-5-amd64-unsigned/unstable,testing 6.5.13-1 amd64

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Kevin Price
Thank you Salvatore!

Am 11.12.23 um 12:37 schrieb Salvatore Bonaccorso:
> It still would be helpfull if you can get to the logs of the previous
> boot. After booting back in the working kernel, do you have anything
> sensible logged in the previous boot log? If so can you share that
> please?

Sure. Here's my boot.log.

The first one at "Mon Dec 11 00:54:03 CET 2023" is the faulty 6.1.0-15.

The 2nd one at "Mon Dec 11 01:13:38 CET 2023" is the working 6.1.0-13.

Need any more logfiles or testing? I intend to test
debian-live-12.4.0-amd64-gnome.iso on my computer, IOT rule out any
local config peculiarities, FWIW.

> I'm right now curious to find out if we see the same as
> #1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
> cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
> issue.

Please let me know what kernel version you want me to test, if they're
provides as debian binaries. I'd be glad to help, probably not only for
my own sake. Bear with me I'm unwilling to build kernel packages myself,
due to lack of computing resources. HTH
-- 
Kevin Price Mon Dec 11 00:54:03 CET 2023 
/: clean, 635496/28696576 files, 99342237/114756608 blocks
 Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System...
[  OK  ] Finished systemd-cryptsetup@cryptswap1.service - Cryptography Setup for cryptswap1.
[  OK  ] Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System.
[  OK  ] Reached target blockdev@dev-mapper-cryptswap1.target - Block Device Preparation for /dev/mapper/cryptswap1.
[  OK  ] Reached target cryptsetup.target - Local Encrypted Volumes.
[  OK  ] Finished systemd-binfmt.service - Set Up Additional Binary Formats.
[  OK  ] Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
 Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
 Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
 Starting modprobe@loop.service - Load Kernel Module loop...
 Starting systemd-resolved.service - Network Name Resolution...
 Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...
[  OK  ] Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[  OK  ] Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[  OK  ] Finished modprobe@loop.service - Load Kernel Module loop.
[  OK  ] Found device dev-mapper-cryptswap1.device - /dev/mapper/cryptswap1.
 Activating swap dev-mapper-cryptswap1.swap - /dev/mapper/cryptswap1...
[  OK  ] Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
[  OK  ] Activated swap dev-mapper-cryptswap1.swap - /dev/mapper/cryptswap1.
[  OK  ] Reached target swap.target - Swaps.
[  OK  ] Finished apparmor.service - Load AppArmor profiles.
[  OK  ] Started systemd-resolved.service - Network Name Resolution.
[  OK  ] Reached target nss-lookup.target - Host and Network Name Lookups.
[  OK  ] Reached target sysinit.target - System Initialization.
[  OK  ] Started cups.path - CUPS Scheduler.
[  OK  ] Started anacron.timer - Trigger anacron every hour.
[  OK  ] Started apt-daily.timer - Daily apt download activities.
[  OK  ] Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started logrotate.timer - Daily rotation of log files.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started ntpsec-rotate-stats.timer - Rotate ntpd stats daily.
[  OK  ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Reached target paths.target - Path Units.
[  OK  ] Reached target timers.target - Timer Units.
[  OK  ] Listening on avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Listening on dbus.socket - D-Bus System Message Bus Socket.
 Starting 

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Diederik de Haas
On Monday, 11 December 2023 13:01:58 CET Grand T wrote:
> Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few
> days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range
> use." That patch ended up regressing Linux wireless support with deadlocks
> in the IWD wireless daemon hangs on shutdown, and related issues with
> user-space network managers

Kernel 6.6.6 fixes an issue introduced in 6.6.5, but both have NOT been 
uploaded to Debian. If they were, that would've been to Experimental or 
Unstable, where breakage from time to time should be expected.

Kernel 6.1.67 *is* relevant and is also a revert of that commit.

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


Bug#1057967:

2023-12-11 Thread Jason Zarin
I think it highly likely that it's that wifi reversion noted up thread.

On my system, wifi hangs (broadcom-sta-dkms) and causes network manager to
hit 100% according to top.

Problem not present in kernels 6.1.0-13&14 and back port 6.5.


Bug#1058028: linux-image-6.1.0-14-amd64 breaks suspend

2023-12-11 Thread Diederik de Haas
On Monday, 11 December 2023 12:46:40 CET Dr.  André Desgualdo Pereira wrote:
> Package: src:linux
> Version: 6.1.64-1
> Severity: important

Stop using that kernel version ASAP! 
It has an ext4 bug which could cause data loss. See
https://bugs.debian.org/1057843 and
https://www.debian.org/News/2023/20231210


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


Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Stephan Verbücheln
Hello everybody

Unfortunately, I can confirm the same problems for 2014 Macbook Pro
(Intel CPU and graphics).

At first I thought the network problem was due to the proprietary
Broadcom WLAN driver because network connectivity was the most obvious
problem. However, the problems persisted after removing all proprietary
(broadcom-sta) and custom (facetimehd) kernel modules.

Regards
Stephan


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


Processed: your mail

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 1057967 src:linux
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Added indication that 1057967 affects src:linux
> notfound 1057967 linux/6.1.64-1
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Ignoring request to alter found versions of bug #1057967 to the same values 
previously set
> found 1057967 linux/6.1.66-1
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Ignoring request to alter found versions of bug #1057967 to the same values 
previously set
> thanks
Stopping processing here.

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



Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Grand T
Hello
For my case:
Is that a surprise if the problem is that one?

wifi: cfg80211: fix CQM for non-range use



https://www.phoronix.com/news/Linux-6.6.6-Released
 Linux 6.6.6 is out with just a sole change for dealing with another headache: 
WiFi regressions.

Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few 
days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range use." 
That patch ended up regressing Linux wireless support with deadlocks in the IWD 
wireless daemon hangs on shutdown, and related issues with user-space network 
managers


Bug#1051643: linux-image-6.1.0-11-686-pae: kernel BUG at mm/usercopy.c:101!

2023-12-11 Thread Klaus Rein

I can confirm that the bug still exists in 6.1.0-15-686-pae:

# uname -a
Linux cobra 6.1.0-15-686-pae #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 
(2023-12-09) i686 GNU/Linux


# apt-get update
Get:1 http://security.debian.org/debian-security bookworm-security 
InRelease [48.0 kB]

Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]
0% [2 InRelease 0 B/151 kB 0%] [1 InRelease 0 B/48.0 kB 0%]

[  614.150786] usercopy: Kernel memory exposure attempt detected from 
kmap (offset 0, size 16384)!

[  614.150908] [ cut here ]
[  614.150909] kernel BUG at mm/usercopy.c:101!
[  614.150947] invalid opcode:  [#1] PREEMPT SMP PTI
[  614.150983] CPU: 0 PID: 3018 Comm: http Not tainted 6.1.0-15-686-pae 
#1  Debian 6.1.66-1
[  614.151011] Hardware name: VMware, Inc. VMware Virtual Platform/440BX 
Desktop Reference Platform, BIOS 6.00 11/12/2020

[  614.151066] EIP: usercopy_abort+0x65/0x67
[  614.151104] Code: 44 cb bb 10 ce b2 d1 89 4d f0 b9 2b 48 b1 d1 0f 45 
cb ff 75 0c ff 75 08 57 52 56 50 ff 75 f0 51 68 b0 cd b2 d1 e8 61 88 ff 
ff <0f> 0b 56 31 d2 b8 5a ce b2 d1 ff 75 ec 8b 4d f0 e8 86 ff ff ff 56

[  614.151177] EAX: 0053 EBX: d1b2ce10 ECX: f6fcfa00 EDX: f6fc9e90
[  614.151215] ESI: d1b438fc EDI: d1b438fc EBP: c2b75c90 ESP: c2b75c5c
[  614.151255] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00010286
[  614.151310] CR0: 80050033 CR2: b7761ec0 CR3: 02bce000 CR4: 001506f0
[  614.151363] Call Trace:
[  614.151390]  ? __die_body.cold+0x14/0x1a
[  614.151424]  ? __die+0x21/0x26
[  614.151453]  ? die+0x28/0x50
[  614.151470]  ? do_trap+0xbb/0xe0
[  614.151485]  ? do_error_trap+0x4c/0x60
[  614.151501]  ? usercopy_abort+0x65/0x67
[  614.151532]  ? exc_overflow+0x40/0x40
[  614.151564]  ? exc_invalid_op+0x44/0x60
[  614.151604]  ? usercopy_abort+0x65/0x67
[  614.151656]  ? handle_exception+0x133/0x133
[  614.151705]  ? exc_overflow+0x40/0x40
[  614.151780]  ? usercopy_abort+0x65/0x67
[  614.151816]  ? exc_overflow+0x40/0x40
[  614.151897]  ? usercopy_abort+0x65/0x67
[  614.151977]  __check_object_size.cold+0xae/0xae
[  614.152034]  simple_copy_to_iter+0x1c/0x40
[  614.152113]  __skb_datagram_iter+0x163/0x320
[  614.152186]  skb_copy_datagram_iter+0x2d/0x80
[  614.152635]  ? skb_free_datagram+0x20/0x20
[  614.153028]  tcp_recvmsg_locked+0x582/0x8a0
[  614.153461]  tcp_recvmsg+0x6f/0x1e0
[  614.153845]  ? tcp_recv_timestamp+0x240/0x240
[  614.154203]  inet_recvmsg+0x54/0x130
[  614.154555]  ? security_socket_recvmsg+0x41/0x60
[  614.154911]  sock_recvmsg+0x73/0x90
[  614.155261]  ? ipip_gso_segment+0x30/0x30
[  614.155597]  sock_read_iter+0x84/0xe0
[  614.155924]  vfs_read+0x288/0x2c0
[  614.156259]  ksys_read+0xab/0xe0
[  614.156570]  __ia32_sys_read+0x15/0x20
[  614.156870]  __do_fast_syscall_32+0x68/0xb0
[  614.157155]  ? __ia32_sys_pselect6_time32+0x4c/0x80
[  614.157435]  ? exit_to_user_mode_prepare+0x32/0x170
[  614.157712]  ? syscall_exit_to_user_mode+0x29/0x40
[  614.157986]  ? __do_fast_syscall_32+0x72/0xb0
[  614.158270]  ? exit_to_user_mode_prepare+0x9d/0x170
[  614.158541]  ? irqentry_exit_to_user_mode+0x16/0x20
[  614.158833]  do_fast_syscall_32+0x29/0x60
[  614.159102]  do_SYSENTER_32+0x15/0x20
[  614.159392]  entry_SYSENTER_32+0x98/0xf1
[  614.159664] EIP: 0xb7f6d559
[  614.159931] Code: 03 74 c0 01 10 05 03 74 b8 01 10 06 03 74 b4 01 10 
07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 
80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76

[  614.160864] EAX: ffda EBX: 0003 ECX: 015bcd09 EDX: fee7
[  614.161200] ESI: b721cff4 EDI:  EBP: 015b2f20 ESP: bf9bd970
[  614.161526] DS: 007b ES: 007b FS:  GS: 0033 SS: 007b EFLAGS: 0246
[  614.161856] Modules linked in: xt_tcpudp xt_conntrack nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink 
vsock_loopback vmw_vsock_virtio_transport_common 
vmw_vsock_vmci_transport vsock binfmt_misc xfs libcrc32c intel_rapl_msr 
ppdev intel_rapl_common rapl vmw_balloon pcspkr vmwgfx drm_ttm_helper 
ttm vmw_vmci drm_kms_helper parport_pc parport button ac joydev evdev 
serio_raw sg drm loop fuse efi_pstore configfs ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_mod dax sd_mod t10_pi 
crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_common 
sr_mod cdrom ata_generic crc32c_intel psmouse mptspi ata_piix mptscsih 
mptbase libata scsi_transport_spi e1000 scsi_mod i2c_piix4 scsi_common 
floppy

[  614.165246] ---[ end trace  ]---
[  614.165664] EIP: usercopy_abort+0x65/0x67
[  614.166085] Code: 44 cb bb 10 ce b2 d1 89 4d f0 b9 2b 48 b1 d1 0f 45 
cb ff 75 0c ff 75 08 57 52 56 50 ff 75 f0 51 68 b0 cd b2 d1 e8 61 88 ff 
ff <0f> 0b 56 31 d2 b8 5a ce b2 d1 ff 75 ec 8b 4d f0 e8 86 ff ff ff 56

[  614.167439] EAX: 0053 EBX: d1b2ce10 ECX: f6fcfa00 EDX: f6fc9e90
[  614.167975] ESI: d1b438fc EDI: d1b438fc EBP: c2b75c90 ESP: c2b75c5c
[  614.168465] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 EFLAGS: 00010286

Bug#1058028: linux-image-6.1.0-14-amd64 breaks suspend

2023-12-11 Thread Dr . André Desgualdo Pereira
Package: src:linux
Version: 6.1.64-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   Updating the kernel.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Booting from an older kernel fix the issue.
   * What was the outcome of this action?
   Bug is fixed by using an older kernel version.
   * What outcome did you expect instead?
   I expect updating the kernel doesn't break functionality.

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


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

** Model information
sys_vendor: CLEVO
product_name: P150HMx
product_version: Not Applicable
chassis_vendor: CLEVO   
chassis_version: Not Applicable
bios_vendor: American Megatrends Inc.
bios_version: 4.6.4
board_vendor: CLEVO
board_name: P150HMx
board_version: Not Applicable

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: CLEVO/KAPOK Computer 2nd Generation Core Processor Family 
DRAM Controller [1558:5102]
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 E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [8086:0101] (rev 09) (prog-if 00 [Normal 
decode])
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port [1558:5102]
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:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family MEI 
Controller [1558:5102]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) (prog-if 20 [EHCI])
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family USB 
Enhanced Host Controller [1558:5102]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 05)
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family 
High Definition Audio Controller [1558:5102]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 [8086:1c10] (rev b5) (prog-if 00 [Normal decode])
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 [1558:5102]
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:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 2 [8086:1c12] (rev b5) (prog-if 00 [Normal decode])
Subsystem: CLEVO/KAPOK Computer 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 [1558:5102]
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:1c.2 PCI bridge [0604]: Intel 

Processed: reassign 1057967 to src:linux

2023-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1057967 src:linux 6.1.66-1
Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my 
physical bookworm/gnome computer largely unusable
Bug reassigned from package 'linux-image-6.1.0-15-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.1.66+1.
Ignoring request to alter fixed versions of bug #1057967 to the same values 
previously set
Bug #1057967 [src:linux] linux-image-6.1.0-15-amd64 renders my physical 
bookworm/gnome computer largely unusable
Marked as found in versions linux/6.1.66-1.
> thanks
Stopping processing here.

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



Processed: Re: Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my 
physical bookworm/gnome computer largely unusable
Added tag(s) moreinfo.

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



Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo

Hi Kevin,

On Mon, Dec 11, 2023 at 02:55:50AM +0100, Kevin Price wrote:
> Package: linux-image-6.1.0-15-amd64
> Version: 6.1.66-1
> Severity: critical
> Control: -1 notfound 6.1.64-1
> 
> When booting 6.1.0-15, my physical amd64/bookworm/gnome computer
> misbehaves in many ways, rendering it largely unusable. With kernels up
> to 6.1.0-13, and even briefly with the otherwise broken 6.1.0-14, all of
> this seemed fine.
> 
> Misbehavior includes, not limited to:
> 
> 1. Most actions take considerably longer than usual.
> 
> 2. The GDM greeter has an English keyboard layout, which otherwise is
> German. (Login works.)
> 
> 3. There seems to be no network connectivity. No WiFi icon. "ping
> 8.8.8.8" returns IIRC network unreachable.
> 
> 4. Launching Firefox does apparently nothing.
> 
> 5. Launching gnome-terminal does work, but some basic commands just
> freeze, such as "ip a" or "sudo dmesg". sudo hangs before prompting for
> the passphrase. At that stage, even "sudo -i", I cannot interrupt with "^C".
> 
> 6. Shutting down takes ages, with systemd waiting for a bunch of
> processes (sudo) and services to terminate, most of the latter seem to
> be somehow network-related, but you tell me which aren't.
> 
> After more that 10 min I used hard power-off, leaving my ext4 dirty, but
> being perfectly able to boot any of 6.1.0-12 through -15, with -12 and
> -13 working properly, and -15 showing the exact same misbehavior
> reproducibly.
> 
> I'll attach all I could get out of reportbug running under 6.1.0-15, and
> please let me know what further testing I may perform IOT help you.
> Please also specify whether you'd like me to do that testing under
> 6.1.0-15, in which I cannot even invoke sudo, or under 6.1.0-13, which
> will do anything fine.

It still would be helpfull if you can get to the logs of the previous
boot. After booting back in the working kernel, do you have anything
sensible logged in the previous boot log? If so can you share that
please? I'm right now curious to find out if we see the same as
#1057969 and if the upstream commit db46c77f3d51 ("Revert "wifi:
cfg80211: fix CQM for non-range use"") in 6.1.67 upstream fixes the
issue.

Regards,
Salvatore



Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo

Hi Steve,

On Sun, Dec 10, 2023 at 07:41:15PM -0800, Steve VanDevender wrote:
> Package: src:linux
> Version: 6.1.66-1
> Severity: grave
> Tags: upstream
> Justification: renders package unusable
> 
> I would have tried to report this from the 6.1.66 kernel but once a
> suspend is attempted network access is also broken so I have had to
> reboot into a working kernel in order to report the bug.
> 
> The problem may be related to the wireless network drivers since some
> processes that can't be frozen for suspend are NetworkManager,
> wpa-supplicant, and iw.
> 
> I have included boot messages from the affected kernel through an
> attempt to suspend the system including the traces from the processes
> that seem to get wedged by an attempt to suspend.
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached
> 2023-12-10T18:48:54.150384-08:00 glitch kernel: [0.00] microcode: 
> microcode updated early to revision 0x21, date = 2019-02-13
> 2023-12-10T18:48:54.151278-08:00 glitch kernel: [0.00] Linux version 
> 6.1.0-15-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 
> 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 
> 6.1.66-1 (2023-12-09)
> 2023-12-10T18:48:54.151283-08:00 glitch kernel: [0.00] Command line: 
> BOOT_IMAGE=/vmlinuz-6.1.0-15-amd64 root=/dev/mapper/glitch-root ro quiet
> 2023-12-10T18:48:54.151286-08:00 glitch kernel: [0.00] BIOS-provided 
> physical RAM map:
> 2023-12-10T18:48:54.151288-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x-0x0009d7ff] usable
> 2023-12-10T18:48:54.151289-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x0009d800-0x0009] reserved
> 2023-12-10T18:48:54.151290-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x000e-0x000f] reserved
> 2023-12-10T18:48:54.151297-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x0010-0x1fff] usable
> 2023-12-10T18:48:54.151298-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x2000-0x201f] reserved
> 2023-12-10T18:48:54.151299-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x2020-0x40003fff] usable
> 2023-12-10T18:48:54.151300-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x40004000-0x40004fff] reserved
> 2023-12-10T18:48:54.151301-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x40005000-0xcec2] usable
> 2023-12-10T18:48:54.151302-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xcec3-0xdae9efff] reserved
> 2023-12-10T18:48:54.151303-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xdae9f000-0xdaf9efff] ACPI NVS
> 2023-12-10T18:48:54.151306-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xdaf9f000-0xdaffefff] ACPI data
> 2023-12-10T18:48:54.151307-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xdafff000-0xdf9f] reserved
> 2023-12-10T18:48:54.151308-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xf800-0xfbff] reserved
> 2023-12-10T18:48:54.151309-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfec0-0xfec00fff] reserved
> 2023-12-10T18:48:54.151310-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfed08000-0xfed08fff] reserved
> 2023-12-10T18:48:54.151311-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfed1-0xfed19fff] reserved
> 2023-12-10T18:48:54.151319-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfed1c000-0xfed1] reserved
> 2023-12-10T18:48:54.151320-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xfee0-0xfee00fff] reserved
> 2023-12-10T18:48:54.151321-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0xffc0-0x] reserved
> 2023-12-10T18:48:54.151322-08:00 glitch kernel: [0.00] BIOS-e820: 
> [mem 0x0001-0x00011e5f] usable
> 2023-12-10T18:48:54.151323-08:00 glitch kernel: [0.00] NX (Execute 
> Disable) protection: active
> 2023-12-10T18:48:54.151324-08:00 glitch kernel: [0.00] SMBIOS 2.7 
> present.
> 2023-12-10T18:48:54.151327-08:00 glitch kernel: [0.00] DMI: LENOVO 
> 2306CTO/2306CTO, BIOS G2ETA7WW (2.67 ) 09/09/2016
> 2023-12-10T18:48:54.151328-08:00 glitch kernel: [0.00] tsc: Fast TSC 
> calibration using PIT
> 2023-12-10T18:48:54.151329-08:00 glitch kernel: [0.00] tsc: Detected 
> 2494.294 MHz processor
> 2023-12-10T18:48:54.151330-08:00 glitch kernel: [0.001086] e820: update 
> [mem 0x-0x0fff] usable ==> reserved
> 2023-12-10T18:48:54.151331-08:00 glitch kernel: [0.001089] e820: remove 
> [mem 0x000a-0x000f] usable
> 2023-12-10T18:48:54.151332-08:00 glitch kernel: [

Processed: Re: Bug#1057969: linux-image-6.1.0-15-amd64: suspend/resume broken in 6.1.66 on Lenovo Thinkpad X230

2023-12-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #1057969 [src:linux] linux-image-6.1.0-15-amd64: suspend/resume broken in 
6.1.66 on Lenovo Thinkpad X230
Added tag(s) moreinfo.

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



Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-11 Thread Grand T
Hello all

Same issue here

The update to  linux-image-6.1.0-15-amd64 broke the system

Despite this

Calcul de la mise à jour…
Les NOUVEAUX paquets suivants seront installés :
  linux-headers-6.1.0-15-amd64 linux-headers-6.1.0-15-common
  linux-image-6.1.0-15-amd64
Les paquets suivants seront mis à jour :
  gir1.2-adw-1 gir1.2-gst-plugins-bad-1.0 gir1.2-gtk-4.0
  gir1.2-javascriptcoregtk-4.0 gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.0
  gir1.2-webkit2-4.1 git git-man gstreamer1.0-plugins-bad libadwaita-1-0
  libavif16 libavif16:i386 libglib2.0-0 libglib2.0-0:i386 libglib2.0-bin
  libglib2.0-data libgstreamer-plugins-bad1.0-0 libgtk-4-1 libgtk-4-common
  libiw30 libjavascriptcoregtk-4.0-18 libjavascriptcoregtk-4.1-0
  libopencv-calib3d406 libopencv-core406 libopencv-dnn406
  libopencv-features2d406 libopencv-flann406 libopencv-imgproc406
  libopencv-objdetect406 libopencv-video406 libostree-1-1 librpm9 librpmbuild9
  librpmio9 librpmsign9 libruby3.1 libwebkit2gtk-4.0-37 libwebkit2gtk-4.1-0
  linux-headers-amd64 linux-image-amd64 linux-kbuild-6.1 rpm rpm-common
  rpm2cpio ruby3.1 sudo wireless-tools

..

Paramétrage de linux-image-6.1.0-15-amd64 (6.1.66-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-14-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-14-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-15-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-15-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-15-amd64.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j2 KERNELRELEASE=6.1.0-15-amd64 KVER=6.1.0-15-amd64
Signing module /var/lib/dkms/broadcom-sta/6.30.223.271/build/wl.ko
Cleaning build area...

wl.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.1.0-15-amd64/updates/dkms/
depmod...
dkms autoinstall on 6.1.0-15-amd64/x86_64 succeeded for broadcom-sta
dkms: autoinstall for kernel: 6.1.0-15-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-15-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found background image: Lucienne-boot.png
Found linux image: /boot/vmlinuz-6.1.0-15-amd64
Found initrd image: /boot/initrd.img-6.1.0-15-amd64
Found linux image: /boot/vmlinuz-6.1.0-14-amd64
Found initrd image: /boot/initrd.img-6.1.0-14-amd64
Found linux image: /boot/vmlinuz-6.1.0-13-amd64
Found initrd image: /boot/initrd.img-6.1.0-13-amd64
Found memtest86+x64 image: /boot/memtest86+x64.bin
done


When i start in recoery mode I saw the service NetworkManager-wait-online hangs.
No more wifi up
And I cant do anything to get the hand on terminal to solve the problem

The 6.1.0.14 is remains ok



Bug#1057843: linux: ext4 data corruption in 6.1.64-1

2023-12-11 Thread helios . solaris

I have been running debian 12.3 with kernel 6.1.64-1 for a few hours,
how can I find out whether the file system has been corrupted?