Lenovo E585: Device RTL Bluetooth, O2 sdcard, and rtw88. Broken or issues.

[Mike Mestnik]

https://www.mail-archive.com/debian-kernel@lists.debian.org/msg116401.html

Today I learned that BlueTooth doesn't work either.  I looked at the
FAQ a bit and I realise this is the worst way to initiate discussions
regarding broken drivers, but I believe these issues together
demonstrate a systemic problem that should be addressed.

I've identified 3 drivers that are completely inoperable on this device!

Bug#945172: firmware: failed to load rtw88/rtw8822b_fw.bin

[Nelson G]

Package: firmware-realtek
Version: 20190717-2
Severity: normal

Dear Maintainer,

I can't get my WiFi working (Thinkpad E495, realtek wifi card).
I get the following dmesg output

[   10.939826] rtw_pci :03:00.0: firmware: failed to load
rtw88/rtw8822b_fw.bin (-2)
[   10.939884] firmware_class: See https://wiki.debian.org/Firmware for
information about missing firmware
[   10.939942] rtw_pci :03:00.0: Direct firmware load for
rtw88/rtw8822b_fw.bin failed with error -2
[   10.939946] rtw_pci :03:00.0: failed to request firmware
[   10.939994] rtw_pci :03:00.0: failed to load firmware
[   10.940017] rtw_pci :03:00.0: failed to setup chip efuse info
[   10.940037] rtw_pci :03:00.0: failed to setup chip information
[   10.941055] rtw_pci: probe of :03:00.0 failed with error -22


firmware-realtek/sid installed.
It works correctly on many other distros.



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

Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CO:es (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.135

-- no debconf information

Processed: linux: [dtb] Raspberry Pi 3B+: does not shut down (regression against buster)

[Debian Bug Tracking System]

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

> retitle 941597 linux: [dtb] Raspberry Pi 3B+: does not shut down (regression 
> against buster)
Bug #941597 [src:linux] linux-image-5.2.0-0.bpo.2-arm64: Raspberry Pi 3B+: does 
not shut down (regression against buster)
Changed Bug title to 'linux: [dtb] Raspberry Pi 3B+: does not shut down 
(regression against buster)' from 'linux-image-5.2.0-0.bpo.2-arm64: Raspberry 
Pi 3B+: does not shut down (regression against buster)'.
> found 941597 5.2.9-2~bpo10+1
Bug #941597 [src:linux] linux: [dtb] Raspberry Pi 3B+: does not shut down 
(regression against buster)
Ignoring request to alter found versions of bug #941597 to the same values 
previously set
> found 941597 5.2.17-1~bpo10+1
Bug #941597 [src:linux] linux: [dtb] Raspberry Pi 3B+: does not shut down 
(regression against buster)
Marked as found in versions linux/5.2.17-1~bpo10+1.
> found 941597 5.3.9-3
Bug #941597 [src:linux] linux: [dtb] Raspberry Pi 3B+: does not shut down 
(regression against buster)
Marked as found in versions linux/5.3.9-3.
> thanks
Stopping processing here.

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

Bug#941597: linux: [dtb] Raspberry Pi 3B+: does not shut down (regression against buster)

[Thorsten Glaser]

retitle 941597 linux: [dtb] Raspberry Pi 3B+: does not shut down (regression 
against buster)
found 941597 5.2.9-2~bpo10+1
found 941597 5.2.17-1~bpo10+1
found 941597 5.3.9-3
thanks

As I wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939633#29
this is an issue in the DTB shipped with the 5.x kernel (and it applies
to both 5.2 in backports and 5.3 in sid), working with the DTB from the
buster kernel (with the bpo/sid kernel).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#939633: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)

[Thorsten Glaser]

On Wed, 20 Nov 2019, Thorsten Glaser wrote:

> Please advice as to a fix ☻

By the advice of the original poster of this bugreport, we tried to
use the DTB from the buster kernel instead:

+ cp /usr/lib/linux-image-4.19.0-6-arm64/broadcom/bcm2837-rpi-3-b.dtb 
/boot/firmware/bcm2710-rpi-3-b.dtb
+ cp /usr/lib/linux-image-4.19.0-6-arm64/broadcom/bcm2837-rpi-3-b-plus.dtb 
/boot/firmware/bcm2710-rpi-3-b-plus.dtb
+ cp /usr/lib/linux-image-4.19.0-6-arm64/broadcom/bcm2837-rpi-cm3-io3.dtb 
/boot/firmware/bcm2710-rpi-cm3.dtb

I’m attaching full serial console output of a boot with the stable DTB
and one with the unstable DTB. In both cases, we tried to get the system
to crash; in the 5.x one it died quickly, in the 4.x case we didn’t manage.

Notable differences:

• with the 4.x DTB, 'reboot' works (cf. #941597)
  (like with the stable kernel)
• with the 4.x DTB, WLAN firmware is missing, which does work with 5.x
• with the 4.x DTB, audio is not working (like with the stable kernel)
• with the 4.x DTB, 3D graphics still works (unlike the stable kernel)
• with the 4.x DTB (like the stable kernel), we get some lines à la…
[  570.800140] alloc_contig_range: [33550, 33552) PFNs busy
  … which are almost (but not completely) unheard of with the 5.x DTB
  (and which are, incidentally, also mentioned in #925334)

The 5.x DTB log ends with the CMA having been filled up (by a program
written in python3-pygame, at that) before the crashing line. This is
the same as #925334, except it afterwards crashes with…

[  307.942205] bcm2835-power bcm2835-power: Failed to disable ASB master for v3d

… whereas, in #925334, it continued with…

[  739.334049] vc4_v3d 3fc0.v3d: Failed to allocate memory for tile 
binning: -12. You may need to enable CMA or give it more memory.

… and ceased updating the screen until reboot (but did not crash the
system). *HOWEVER*, we also managed to crash the 5.x system without
overrunning the CMA, earlier, but we forgot to save serial console
output for that run (it was directly before I wrote the previous mail
to this bugreport).

The memory overrunning issue is effectively a local DoS, given it can
be triggered from unprivilegued userspace. (But, as I said above, the
crash can also be triggered without overrunning memory; mostly using
OpenGL.)

It might be useful to diff and bisect the DTB sources (with includes
expanded, probably), but I’ve not got any experience with DTBs or ARM
devices.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**[0.00] Booting Linux on physical CPU 0x00 [0x410fd034]
[0.00] Linux version 5.3.0-2-arm64 (debian-kernel@lists.debian.org) 
(gcc version 9.2.1 20191109 (Debian 9.2.1-19)) #1 SMP Debian 5.3.9-3 
(2019-11-19)
[0.00] Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 128 MiB at 0x3340
[0.00] NUMA: No NUMA configuration found
[0.00] NUMA: Faking a node at [mem 
0x-0x3b3f]
[0.00] NUMA: NODE_DATA [mem 0x3320d840-0x3320efff]
[0.00] Zone ranges:
[0.00]   DMA32[mem 0x-0x3b3f]
[0.00]   Normal   empty
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x3b3f]
[0.00] Initmem setup node 0 [mem 0x-0x3b3f]
[0.00] percpu: Embedded 32 pages/cpu s93016 r8192 d29864 u131072
[0.00] Detected VIPT I-cache on CPU0
[0.00] CPU features: detected: ARM erratum 845719
[0.00] CPU features: kernel page table isolation forced ON by KASLR
[0.00] CPU features: detected: Kernel page table isolation (KPTI)
[0.00] CPU features: detected: ARM erratum 843419
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 238896
[0.00] Policy zone: DMA32
[0.00] Kernel command line: video=HDMI-A-1:1920x1080@60 
dma.dmachans=0x7f35 bcm2709.boardrev=0xa020d3 bcm2709.serial=0xa5e576b6 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=29 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:E5:76:B6 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=ttyS1,115200 
console=tty0 root=/dev/mmcblk0p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0 cma=128M rootwait
[0.00] Dentry cache hash table entries: 131072 (order: 8, 1048576 
bytes, linear)

Bug#932436: marked as done (linux-image-4.9.0-9-amd64: loop devices cannot be removed with losetup -d /dev/loopX)

[Debian Bug Tracking System]

Your message dated Wed, 20 Nov 2019 20:40:36 +0100 (CET)
with message-id 
and subject line Bug#932436: can be closed
has caused the Debian Bug report #932436,
regarding linux-image-4.9.0-9-amd64: loop devices cannot be removed with 
losetup -d /dev/loopX
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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



-- Package-specific info:
** Version:
Linux version 4.9.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.168-1+deb9u3 (2019-06-16)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-9-amd64 root=/dev/mapper/whiteySSD-root ro quiet 
acpi=force console=tty0 console=ttyS0,115200

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

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

** Model information
sys_vendor: FUJITSU
product_name: 
product_version: 
chassis_vendor: FUJITSU
chassis_version: 
bios_vendor: FUJITSU // American Megatrends Inc.
bios_version: V5.0.0.12 R1.19.0 for D3417-B2x   
board_vendor: FUJITSU
board_name: D3417-B2
board_version: S26361-D3417-B2

** Loaded modules:
btrfs
ufs
qnx4
hfsplus
hfs
minix
ntfs
msdos
jfs
xfs
dm_snapshot
dm_bufio
nls_ascii
nls_cp437
vfat
fat
fuse
xt_nat
ipt_MASQUERADE
nf_nat_masquerade_ipv4
ip6table_nat
nf_nat_ipv6
iptable_nat
nf_nat_ipv4
nf_nat
loop
target_core_user
uio
target_core_pscsi
target_core_file
target_core_iblock
iscsi_target_mod
target_core_mod
cpufreq_userspace
cpufreq_conservative
nbd
cpufreq_powersave
uinput
nf_conntrack_ipv6
nf_defrag_ipv6
nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack
nf_conntrack
xt_tcpudp
xt_owner
ipt_REJECT
nf_reject_ipv4
nf_log_ipv6
nf_log_ipv4
nf_log_common
xt_LOG
xt_limit
xt_hashlimit
ip6table_filter
ip6_tables
iptable_filter
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
tun
vboxdrv(O)
bridge
rc_pinnacle_pctv_hd
em28xx_rc
si2157
si2168
i2c_mux
em28xx_dvb
dvb_core
snd_usb_audio
snd_usbmidi_lib
snd_rawmidi
snd_seq_device
arc4
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
kvm_intel
cdc_acm
kvm
rc_core
irqbypass
em28xx
tveeprom
v4l2_common
videodev
media
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_codec_generic
snd_hda_intel
serio_raw
pcspkr
snd_hda_codec
snd_hda_core
snd_hwdep
snd_pcm
snd_timer
snd
iTCO_wdt
iTCO_vendor_support
soundcore
rt2800usb
rt2x00usb
rt2800lib
rt2x00lib
mac80211
joydev
ftdi_sio
usbserial
cfg80211
evdev
crc_ccitt
rfkill
i915
drm_kms_helper
drm
mei_me
mei
i2c_algo_bit
shpchp
sg
wmi
video
acpi_pad
button
ib_iser
rdma_cm
iw_cm
ib_cm
ib_core
configfs
iscsi_tcp
libiscsi_tcp
libiscsi
scsi_transport_iscsi
coretemp
8021q
garp
stp
mrp
llc
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
fscrypto
ecb
mbcache
algif_skcipher
af_alg
dm_crypt
dm_mod
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid0
multipath
linear
raid1
md_mod
sd_mod
hid_generic
usbhid
hid
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
i2c_i801
i2c_smbus
psmouse
ahci
libahci
e1000e
ptp
pps_core
xhci_pci
libata
xhci_hcd
scsi_mod
usbcore
usb_common
r8169
mii

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:590f] (rev 06)
Subsystem: Fujitsu Technology Solutions Device [1734:121c]
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 Skylake PCIe Controller (x16) 
[8086:1901] (rev 06) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Fujitsu Technology Solutions Skylake PCIe 
Controller (x16) [1734:121c]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 
Capabilities: [a0] 

Bug#939633: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)

[Thorsten Glaser]

retitle 939633 linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
notfound 939633 4.19.67-2+deb10u1
notfound 939633 4.19.67-2+deb10u2
found 939633 5.2.9-2~bpo10+1
found 939633 5.2.17-1~bpo10+1
found 939633 5.3.9-3
thanks

We’re currently suffering from a similar situation.

Debian buster/arm64 installation, straight from this script:
https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=posix/mkrpi3b%2Bimg.sh;hb=HEAD

With the buster kernel, the analog audio doesn’t work, and
3D graphics using llvmpipe are really slow, but the system
is, overall, stable.

With the backports kernel and either buster’s raspi3-firmware
or sid’s raspi-firmware (tested both), 3D graphics are accelerated,
poweroff/reboot don’t work, and the system crashes after some
uptime (confirmed it’s not a thermal issue, and the official
PSU is used, so power is enough).

With the sid kernel and sid’s raspi-firmware, the same issue
happens. We managed to get a serial console running, and the
crash message is what led us to this bugreport:

[timestamp] bcm2835-power bcm2835-power: Failed to disable ASB master for v3d

This is a fairly stock setup, with CMA raised to 128M and
consoles fixed (see the outstanding bugreports in the
raspi3-firmware/raspi-firmware package), and video size fixed:

tglase@tglase:/mnt $ grep '^[^#]' etc/default/raspi-firmware
CMA=128M
CONSOLES='ttyS1,115200 tty0'
tglase@tglase:/mnt $ cat etc/default/raspi-firmware-custom 
disable_overscan=1


Incidentally, shortly before, we see this in syslog:

Jan  1 01:00:26 rpi3bplus kernel: [   26.255342] broken atomic modeset 
userspace detected, disabling atomic

Unsure whether it’s related.


Other things are reports in Fedora with instabilities relating
to the RPi 3B+ and power management…

Please advice as to a fix ☻

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Processed: Re: linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)

[Debian Bug Tracking System]

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

> retitle 939633 linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree issue?)
Bug #939633 [src:linux] Rpi3+ hangs with kernel 5.2 device_tree
Changed Bug title to 'linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree 
issue?)' from 'Rpi3+ hangs with kernel 5.2 device_tree'.
> notfound 939633 4.19.67-2+deb10u1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree 
issue?)
Ignoring request to alter found versions of bug #939633 to the same values 
previously set
> notfound 939633 4.19.67-2+deb10u2
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree 
issue?)
Ignoring request to alter found versions of bug #939633 to the same values 
previously set
> found 939633 5.2.9-2~bpo10+1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree 
issue?)
Marked as found in versions linux/5.2.9-2~bpo10+1.
> found 939633 5.2.17-1~bpo10+1
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree 
issue?)
Marked as found in versions linux/5.2.17-1~bpo10+1.
> found 939633 5.3.9-3
Bug #939633 [src:linux] linux: rpi3b+ hangs with kernels 5.2, 5.3 (device tree 
issue?)
Marked as found in versions linux/5.3.9-3.
> thanks
Stopping processing here.

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

Bug#945140: linux-image-5.3.0-2-amd64: system occasionally hangs for several minutes

[Vincent Lefevre]

On 2019-11-20 12:52:09 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 5.3.9-2
> Severity: important
> 
> Since yesterday, the system occasionally hangs for several minutes.
> When this happens, I can observe in the journalctl output:
> 
> Nov 19 02:28:43 zira rtkit-daemon[752]: The canary thread is apparently 
> starving. Taking action.
[...]

Note sure whether this is a bug related to rtkit-daemon. I've found
the possible culprit (which also explains that I had no problems
before): xpdf takes several GB, even though the PDF file is rather
simple (26 slides, no images...). The consequence is that the machine
is swapping. I suspect a memory leak, possibly when the PDF file is
reloaded (I've been writing slides, thus with many reloads...).

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

linux-signed-arm64_5.3.9+2~bpo10+1_source.changes is NEW

[Debian FTP Masters]

binary:linux-image-5.3.0-0.bpo.2-arm64 is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

linux-signed-i386_5.3.9+2~bpo10+1_source.changes is NEW

[Debian FTP Masters]

binary:linux-image-5.3.0-0.bpo.2-686 is NEW.
binary:linux-image-5.3.0-0.bpo.2-686-pae is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

linux-signed-amd64_5.3.9+2~bpo10+1_source.changes is NEW

[Debian FTP Masters]

binary:linux-image-5.3.0-0.bpo.2-amd64 is NEW.
binary:linux-image-5.3.0-0.bpo.2-cloud-amd64 is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

Bug#939545: Fwd:

[pham...@bluewin.ch]

Post Scriptum :
 
MX Linux 19 OS with which everything is working properly is based on Debian 10 
Buster
 
  
 
 
  Best regards.
 
 
 
 

Bug#939545:

[pham...@bluewin.ch]

Hello,
I have making tests in Debian 10, Mint 19.2 and Ubuntu 18.04, these 3 OS all 
suffer from the same problem with the priose 3.5mm jack that whistles when 
headphones are plugged in and no sound is broadcast.
The problem is related to the Realtek ALC3266 sound card.
If you open the sound settings software, the whistle disappears, as soon as you 
close the whistle comes back.
If you open VLC or any other player, the whistle disappears, as soon as you 
close it the whistle comes back.
When there is no signal sent to the sound card the problem is present.
One way to solve this problem would be to continuously send a "blank" signal 
(just a signal without sound) to this sound card.
After tests, this laptop works perfectly under Debian if it is connected to a 
"Sharkoon Gaming DAC Pro S (USB-DAC)" sound card or on a "USB-3 type C to 3.5 
mm jack adapter". But it does not work properly with the Realtek ALC3266 
integrated sound card.
Yesterday after I made an installation of MX Linux 19 on my laptop that does 
not use "systemd" but "init", I noticed that I have no problems with my 
headphones connected jack 3.5 mm to the Realtek ALC3266 integrated sound card 
 All work perfectly :) But I dont like realy this Linux distribution...
I hope that these additional indications will allow you to solve this bug which 
seems to exist since several years and has never been solved...
I hope that with a new look at this bug, that you finally will fix it !!!
Best regards.

Bug#945157: Wrong system time on DHCOM i.MX6 due to missing RTC driver

[Johann Neuhauser]

Package: linux-image-4.19.0-6-armmp
Version: 4.19.67-2+deb10u2
X-Debbugs-CC: debian-kernel@lists.debian.org, wa...@debian.org, 
m...@debian.org, b...@decadent.org.uk, car...@debian.org

When booting on DHCOM i.MX6 Quad with device tree "imx6q-dhcom-pdk2.dtb"

we always have a wrong system time.
This behavior is related to the missing RTC driver in the config of armmp.

I suggest adding "CONFIG_RTC_DRV_RV3029C2=y" to the config file
"debian/config/armhf/config" in the repo 
"https://salsa.debian.org/kernel-team/linux;.

Regards,



Johann Neuhauser

DH electronics GmbH

linux-signed-amd64_5.3.9+2~bpo10+1_source.changes REJECTED

[Debian FTP Masters]

ACL automatic-source-uploads: hijacks are not allowed 
(binary=linux-image-amd64, other-source=linux-latest)

binary:linux-image-5.3.0-0.bpo.2-amd64 is NEW.
binary:linux-image-5.3.0-0.bpo.2-cloud-amd64 is NEW.

===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

linux-signed-i386_5.3.9+2~bpo10+1_source.changes REJECTED

[Debian FTP Masters]

ACL automatic-source-uploads: hijacks are not allowed (binary=linux-image-686, 
other-source=linux-latest)

binary:linux-image-5.3.0-0.bpo.2-686 is NEW.
binary:linux-image-5.3.0-0.bpo.2-686-pae is NEW.

===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

Processing of linux-signed-i386_5.3.9+2~bpo10+1_source.changes

[Debian FTP Masters]

linux-signed-i386_5.3.9+2~bpo10+1_source.changes uploaded successfully to 
localhost
along with the files:
  linux-signed-i386_5.3.9+2~bpo10+1.dsc
  linux-signed-i386_5.3.9+2~bpo10+1.tar.xz

Greetings,

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

Processing of linux-signed-amd64_5.3.9+2~bpo10+1_source.changes

[Debian FTP Masters]

linux-signed-amd64_5.3.9+2~bpo10+1_source.changes uploaded successfully to 
localhost
along with the files:
  linux-signed-amd64_5.3.9+2~bpo10+1.dsc
  linux-signed-amd64_5.3.9+2~bpo10+1.tar.xz

Greetings,

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

Bug#944420: Upstream bug report

[Philipp Klaus Krause]

Upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=205589

Bug#944420: Two more confirmations

[Philipp Klaus Krause]

Two more Manjaro users with of the green screen hang on XFCE start using
3400G with a 5.x kernel: One in the thread mentined above, the other in
https://forum.manjaro.org/t/kernel-question-amd-ryzen-5-2400g-with-radeon-vega-graphics/106683

Bug#945140: linux-image-5.3.0-2-amd64: system occasionally hangs for several minutes

[Vincent Lefevre]

Package: src:linux
Version: 5.3.9-2
Severity: important

Since yesterday, the system occasionally hangs for several minutes.
When this happens, I can observe in the journalctl output:

Nov 19 02:28:43 zira rtkit-daemon[752]: The canary thread is apparently 
starving. Taking action.
Nov 19 02:28:43 zira rtkit-daemon[752]: Demoting known real-time threads.
Nov 19 02:28:43 zira rtkit-daemon[752]: Successfully demoted thread 20029 of 
process 19666.
Nov 19 02:28:43 zira rtkit-daemon[752]: Successfully demoted thread 20028 of 
process 19666.
Nov 19 02:28:43 zira rtkit-daemon[752]: Successfully demoted thread 19666 of 
process 19666.
Nov 19 02:28:43 zira rtkit-daemon[752]: Demoted 3 threads.

Nov 20 04:13:07 zira rtkit-daemon[747]: The canary thread is apparently 
starving. Taking action.
Nov 20 04:13:07 zira rtkit-daemon[747]: Demoting known real-time threads.
Nov 20 04:13:07 zira rtkit-daemon[747]: Successfully demoted thread 2057 of 
process 1567.
Nov 20 04:13:07 zira rtkit-daemon[747]: Successfully demoted thread 2056 of 
process 1567.
Nov 20 04:13:07 zira rtkit-daemon[747]: Successfully demoted thread 1567 of 
process 1567.
Nov 20 04:13:07 zira rtkit-daemon[747]: Demoted 3 threads.

Nov 20 12:33:37 zira rtkit-daemon[747]: The canary thread is apparently 
starving. Taking action.
Nov 20 12:33:37 zira rtkit-daemon[747]: Demoting known real-time threads.
Nov 20 12:33:38 zira rtkit-daemon[747]: Demoted 0 threads.

Possibly related, with also the messages about rtkit-daemon:

  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1712858

"Occasionally, the system freezes: display does not show mouse move,
clock display does not update itself, ssh impossible."

Ditto here. It is also said "But the machine remains pingable"
but I have not tried ping.

-- Package-specific info:
** Version:
Linux version 5.3.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191109 (Debian 9.2.1-19)) #1 SMP Debian 5.3.9-2 (2019-11-12)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-2-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Not tainted

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
nft_counter
nf_tables
nfnetlink
psnap
llc
cpufreq_conservative
cpufreq_userspace
intel_rapl_msr
intel_rapl_common
cpufreq_powersave
cmac
bnep
x86_pkg_temp_thermal
intel_powerclamp
coretemp
iwlmvm
snd_hda_codec_hdmi
btusb
btrtl
mei_wdt
mac80211
btbcm
btintel
bluetooth
kvm
binfmt_misc
irqbypass
libarc4
nouveau
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
intel_cstate
iwlwifi
uvcvideo
videobuf2_vmalloc
videobuf2_memops
intel_uncore
snd_hda_intel
videobuf2_v4l2
snd_hda_codec
intel_rapl_perf
ttm
drbg
videobuf2_common
cfg80211
joydev
snd_hda_core
hp_wmi
videodev
drm_kms_helper
snd_hwdep
serio_raw
pcspkr
snd_pcm
ansi_cprng
iTCO_wdt
mei_me
sparse_keymap
mc
snd_timer
ecdh_generic
snd
ecc
rtsx_pci_ms
tpm_infineon
iTCO_vendor_support
drm
wmi_bmof
sg
memstick
watchdog
soundcore
mxm_wmi
rfkill
mei
i2c_algo_bit
ie31200_edac
battery
evdev
tpm_tis
tpm_tis_core
tpm
hp_accel
lis3lv02d
rng_core
button
input_polldev
ac
hp_wireless
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sr_mod
cdrom
sd_mod
hid_apple
hid_generic
usbhid
hid
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
libahci
aesni_intel
xhci_pci
libata
xhci_hcd
aes_x86_64
crypto_simd
cryptd
ehci_pci
glue_helper
ehci_hcd
scsi_mod
e1000e
psmouse
rtsx_pci
usbcore
i2c_i801
lpc_ich
mfd_core
ptp
pps_core
usb_common
video
wmi

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eth0 inet dhcp

allow-hotplug enx02060b0e
iface enx02060b0e inet dhcp
allow-hotplug enp0s20u2
iface enp0s20u2 inet dhcp
allow-hotplug enp0s20u9
iface enp0s20u9 inet dhcp
allow-hotplug enp0s20u10
iface enp0s20u10 inet dhcp


** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic eth0
   valid_lft 71454sec preferred_lft 71454sec
inet6 fe80::328d:99ff:fe25:ad3f/64 scope link 
   valid_lft forever preferred_lft forever
3: wlp61s0:  mtu 1500