Re: Bug#989777: Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

[Andrei POPESCU]

Reassign -1 src:linux 5.10.40-1

On Sb, 12 iun 21, 21:11:02, pham...@bluewin.ch wrote:
> Package: kernel 
> Version: 5.10.x-amd64
> Bug Description: My Intel AX210 Wifi and Bluetooth card not work
> Intel indicates on its website that this AX210 card is compatible from kernel 
> 5.10 !?!
> https://www.intel.com/content/www/us/en/support/articles/05511/wireless.html

Please try installing using an image from here:


https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/

> My laptop does not have an RJ-45 port, I do not have access to the internet, 
> nor to my Bluetooth devices such as my mouse, my keyboard, my headphones ;-(
> Best regards.
> Philippe

Reassigning to correct package.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Processed: unarchiving 852749, closing 852749

[Debian Bug Tracking System]

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

> unarchive 852749
Bug #852749 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.9.0-1-amd64: usb-audio-device not working since kernel 4.9.0.1
Unarchived Bug 852749
> # according to followup reporter, which due to archive
> # status did not reach the BTS anymore
> close 852749 5.10.40-1
Bug #852749 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.9.0-1-amd64: usb-audio-device not working since kernel 4.9.0.1
Marked as fixed in versions linux/5.10.40-1.
Bug #852749 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.9.0-1-amd64: usb-audio-device not working since kernel 4.9.0.1
Bug 852749 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Re: release notes mentioning dropped support?

[Justin B Rye]

Paul Gevers wrote:
> +
> +  Hardware that's no longer supported

The contraction "that's" seems out of place in a title - probably we
should just use:

 No longer supported hardware

> +  
> + Due to hardware limitations, it's no longer viable for Debian
> + to build the Linux kernel supporting a
> + number of armel based devices that were supported in
> + buster. The unsupported devices are:

This sounds as if it's talking about one kernel supporting multiple
armel-based devices; if it means one kernel per device, that's plural.

Due to hardware limitations, it's no longer viable for Debian
to build the Linux kernels supporting a
number of armel-based devices that were supported in
buster. The unsupported devices are:

Or maybe:

For a number of armel-based devices that were supported in
buster, it is no longer viable for Debian to build the
required Linux kernels, due to hardware
limitations. The unsupported devices are:

> +  
> +  
> + 
> +   
> + QNAP TS-109/TS-209, TS-119/TS-219 and TS-409
> +   
> + 
> + 
> +   
> + HP Media Vault mv2120
> +   
> + 
> +  
> +  
> + Users of those platforms that wish to upgrade to bullseye
> + nevertheless should keep the buster APT sources enabled and,
> + before upgrading, add an APT preferences file containing
> + something like:

Users of these platforms who wish to upgrade to bullseye
nevertheless should keep the buster APT sources enabled, and
before upgrading should add an APT preferences file containing
something like:

(Or maybe as two sentences, "Before upgrading they should...")

> + 
> +Package: linux-image-marvell
> +Pin: release a=buster
> +Pin-Priority: 900
> + 
> + Obviously, the security support for this configuration will
> + end with the End Of Life of buster.

Obviously, the security support for this configuration will
only last until buster's End Of Life.

> +  
> +
>
>  
> -- 
> 2.30.2
> 





-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package

Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38

[jim_p]

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com

Finally, a sane reply that does not blame nvidia's driver.

I have written above that something must have changed, at least regarding intel
hw, because I was missing the coretemp readings on my conky. However, from the
page you mention, only 2 commits refer to intel and I think both of them are
not related to my hardware.

If it is a kernel issue, which means I will come accross it on any distro I
choose, I should report it on kernel's github page... if it had issue reports.
Besides that, I think I am not smart enough to do it. I reported an similar
issue on openssh (bug 912087) some years ago, but I just could not follow the
conversation until it was resolved, because it was way too technical for me.
Shouldn't a maintainer do that for me like they did for openssh? Now they have
all the logs they need.

The other solution, hopefully, is to wait for the freeze to end, debian to move
to 5.12 or newer and me praying it won't have the same issue.

Re: release notes mentioning dropped support?

[Paul Gevers]

Hi all,

Proposed text for the release notes attached.

On 11-06-2021 21:47, Ben Hutchings wrote:
> On Sat, 2021-06-12 at 03:01 +0900, Roger Shimizu wrote:
>> On Fri, Jun 11, 2021 at 1:22 PM Salvatore Bonaccorso  
>> wrote:
>>> On Thu, Jun 10, 2021 at 11:32:23AM +0200, Paul Gevers wrote:
 On 24-05-2021 06:55, Paul Gevers wrote:
> I happen to own a QNAP (armel) and I spotted in the changelog that it's
> not going to be supported in bullseye. I was wondering, is that
> something that should be mentioned in the release notes? Obviously I
> don't mean because I own it, but I'm betting that support for particular
> hardware pieces has been dropped in the past too. I don't recall
> something like that in the buster release notes, but even if we didn't
> do it in the past, now could be a good moment to start if we think we
> should add it.
>>
>> for armel, the limitation is by:
>> https://salsa.debian.org/kernel-team/linux/-/blob/master/debian/config/armel/defines#L35
>>
>> And from the list in that file, below devices are not supported now.
>> # QNAP TS-119/TS-219: 2097152 - 64 = 2097088
>> # D-Link DNS-323: 1572864 - 8 - 64 = 1572792 (too small, no longer supported)
>> # HP Media Vault mv2120: 2097152 - 8 - 64 = 2097080
>> # QNAP TS-109/TS-209 & TS-409: 2097152 - 8 - 64 = 2097080
>>
>> I guess support for D-Link DNS-323 was dropped since buster, or earlier.
> 
> Yes, since stretch.
> 
>>
> Either way, I was wondering what would happen if I try to upgrade such a
> device. I'm *assuming* that the linux package would detect that the
> image is too big, but what would that leave me? A fully upgraded system
> with an old kernel, or is there any detection before any upgrade
> happens? For owners of such devices, is their only option to stay at
> buster? E.g. is there any chance in building a smaller custom kernel
> with less options enabled or is that impossible because nearly
> everything is build as module?
>>
>> The upgrade of kernel may succeed if /boot still have enough space,
>> but reboot will fail because of the uboot configuration hard coded in
>> those hardware.
> [...]
> 
> My understanding is that these devices load the kernel and initramfs
> from fixed partitions on the on-board flash, not from the filesystem. 
> That's why the limits vary.  flash-kernel is responsible for copying
> the kernel and initramfs to these partitions.  When the kernel is too> 
> Ben.
> 
> large, it will report an error, which should abort the package
> installation.
> 
> To avoid this, users should keep the buster sources enabled and, before
> upgrading, add an APT preferences file containing something like:
> 
> Package: linux-image-marvell
> Pin: release a=buster
> Pin-Priority: 900
> 
> (not tested).  Obviously this will only work as long as buster is
> supported.

As I own one of the unsupported devices, I intend to check if this works
as intended and I'll not push the change until confirmed. If I'm really
brave, I'll even check that flash-kernel errors out in the right way.

Paul
From a58174c17ad3b6cdb19f4e908428f0b0e8bf53c3 Mon Sep 17 00:00:00 2001
From: Paul Gevers 
Date: Sun, 13 Jun 2021 21:30:33 +0200
Subject: [PATCH] issues.dbk: unsupported armel hardware

---
 en/issues.dbk | 34 ++
 1 file changed, 34 insertions(+)

diff --git a/en/issues.dbk b/en/issues.dbk
index 805a15be..01184f9a 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -775,5 +775,39 @@ Environment=SYSTEMD_SULOGIN_FORCE=1
   
 
 
+
+  Hardware that's no longer supported
+  
+	Due to hardware limitations, it's no longer viable for Debian
+	to build the Linux kernel supporting a
+	number of armel based devices that were supported in
+	buster. The unsupported devices are:
+  
+  
+	
+	  
+	QNAP TS-109/TS-209, TS-119/TS-219 and TS-409
+	  
+	
+	
+	  
+	HP Media Vault mv2120
+	  
+	
+  
+  
+	Users of those platforms that wish to upgrade to bullseye
+	nevertheless should keep the buster APT sources enabled and,
+	before upgrading, add an APT preferences file containing
+	something like:
+	
+Package: linux-image-marvell
+Pin: release a=buster
+Pin-Priority: 900
+	
+	Obviously, the security support for this configuration will
+	end with the End Of Life of buster.
+  
+
   
 
-- 
2.30.2



OpenPGP_signature
Description: OpenPGP digital signature

Bug#933013: marked as done (linux-source: kernel panic using CIFS share in smb2_push_mandatory_locks())

[Debian Bug Tracking System]

Your message dated Sun, 13 Jun 2021 12:11:31 -0700 (PDT)
with message-id <60c65863.1c69fb81.8f7b2.6...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #933013,
regarding linux-source: kernel panic using CIFS share in 
smb2_push_mandatory_locks()
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.)


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

[Impact]

* We got reports of a kernel crash in cifs module with the following
* signature:

BUG: unable to handle kernel NULL pointer dereference at
0038
IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
PGD 0 P4D 0
RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
Call Trace:
cifs_oplock_break+0x12f/0x3d0 [cifs]
process_one_work+0x14d/0x410
worker_thread+0x4b/0x460
kthread+0x105/0x140
[...]

* Low-level analysis (decodecode script output and the objdump of
* the function) revealed that we are crashing in a NULL ptr
* dereference when trying to access "cfile->tlink"; below, a snippet
* of the objdump at function smb2_push_mandatory_locks():
   
[...]
mov 0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile
mov 0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks)
lea 0x18(%r14),%r12
mov 0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink)
cmp %r12,%rbx
mov 0x38(%rax),%rax # <--- TRAP [trying to get cifs_tcon *tl_tcon]
[...]

* After discussing the issue with CIFS maintainers (Steve French and
* Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep
* FileInfo handle live during oplock break")
* [http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple
* reports of this kind of crash.
* The fix was sent to stable kernels and is present in Ubuntu
* kernels 5.0 and newer. We are requesting the SRU for this patch
* here in order to fix the crashes, after reports of successful
* testing with the patch (see below section) and since the patch is
* restricted to the cifs module scope and accepted on linux stable.
* Alternatively the issue is known to be avoided when oplocks are
* disabled using "cifs.enable_oplocks=N" module parameter.

[Test case]

* Unfortunately we cannot reproduce the issue. The patch proposed
* here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we
have a user report of test validation using LISA
(https://github.com/LIS/LISAv2).
* Using xfstest with the exclusions proposed in the link above we
* managed to get the same results as a non-patched kernel, i.e., the
* same tests failed in both kernels, we didn't get worse results
* with the patch. Fio also didn't show noticeable performance
* regression with the patch.

[Regression potential]

* The patch was validated by the cifs filesystem maintainers (in
* fact they suggested its inclusion in Ubuntu) and by the
* aforementioned tests; also, the scope is restricted to cifs only
* so the likelihood of regressions is considered low.
* Due to the nature of the code modification (add a new reference of
* a file handler and manipulate it in different places), I consider
* that if we have a regression it'll manifest as deadlock/blocked
* tasks, not something more serious like crashes or data corruption.


-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 
'bionic'), (100, 'bionic-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-17763-Microsoft
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages linux-source depends on:
pn  linux-source-4.15.0  

linux-source recommends no packages.

linux-source suggests no packages.
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Processed: Re: Bug#932996: linux-image-4.19.0-5-amd64: e1000e driver crashes under high TX load; `ethtool -K eno1 tso off` resolves issue.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #932996 [src:linux] linux-image-4.19.0-5-amd64: e1000e driver crashes under 
high TX load; `ethtool -K eno1 tso off` resolves issue.
Added tag(s) moreinfo.

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

Bug#932996: linux-image-4.19.0-5-amd64: e1000e driver crashes under high TX load; `ethtool -K eno1 tso off` resolves issue.

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

On Thu, Jul 25, 2019 at 09:58:33AM -0700, John wrote:
> Package: src:linux
> Version: 4.19.37-6
> Severity: normal
> 
> Dear Maintainer,
> 
> Observed flaky network interface under high TX load with guest OS
> bridging across eno1 interface. Issue only manifested under load, and
> exhibited flapping in dmesg, e.g.:
> e1000e :00:1f.6 eno1: Reset adapter unexpectedly
> br0: port 1(eno1) entered disabled state).
> 
> Issue appears to be resolved by disabling TSO with:
> `ethtool -K eno1 tso off`
> 
> Googling around suggests this may be a common problem with this driver
> -- possibly should default to tso off? See possibly related links:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766377
> https://serverfault.com/questions/616485/e1000e-reset-adapter-unexpectedly-detected-hardware-unit-hang

Is this issue still triggerable for you with a recent kernel from
either unstable, buster-backports or even mainline without needing to
set tso off?

Regards,
Salvatore

Bug#932168: marked as done (Correct verion of libc-dev not found on security.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 13 Jun 2021 12:06:06 -0700 (PDT)
with message-id <60c6571e.1c69fb81.6cfff.b...@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #932168,
regarding Correct verion of libc-dev not found on security.debian.org
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.)


-- 
932168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-libc-dev
Version: latest

Hi all,

when running a docker build using

FROM tomcat:8.5-jre8
RUN apt-get update && apt-get -y install locales
RUN locale-gen de_DE.UTF-8
RUN dpkg-reconfigure locales
ENV LANG de_DE.UTF-8
ENV LANGUAGE de_DE:en
ENV LC_ALL de_DE.UTF-8
RUN apt-get -y install gcc g++ libc6-dev-i386 g++-multilib

the dependencies fail since the weekend. Reason:

Fetched 53.0 MB in 8s (6156 kB/s)
E: Failed to fetch 
http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-libc-dev_4.9.168-1+deb9u2_amd64.deb
  404  Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?
The command '/bin/sh -c apt-get -y install gcc g++ libc6-dev-i386 
g++-multilib' returned a non-zero code: 100

The issue is the deb9u2, which is missing (but present on mirrors) - only 
deb9u3 is there.

It would be nice if you could provide a workaround if this takes longer to fix.

Best regards and keep up the great work,

David



--
David Hansmann
Core Architect

Smartsteuer GmbH * Lister Meile 27 * 30161 Hannover
Fon +49 (0) 511 / 790 90 316

E-Mail david.hansm...@smartsteuer.de
Web www.smartsteuer.de
Facebook https://www.facebook.com/smartsteuer

Handelsregister HRB 200898 * Amtsgericht Hannover
Gesch?ftsf?hrer Dr. Carsten Thies, Bj?rn Waide
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore--- End Message ---

Bug#973368: Bluetooth mouse can not be connected with kernel linux-image-5.9.0-1-amd64

[Salvatore Bonaccorso]

On Fri, Nov 20, 2020 at 03:16:48PM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi,
> 
> On Thu, Oct 29, 2020 at 10:47:51PM +0800, gulfstream wrote:
> > Package: src:linux
> > Version: 5.9.1-1
> > Severity: important
> > 
> > 
> > After the kernel was upgraded to linux-image-5.9.0-1-amd64 few days
> > ago, the bluetooth mouse can not be connected which can be use with
> > linux-image-5.8.0-3-amd64. If back to linux-image-5.8.0-3-amd64, the
> > blue tooth mouse is also fine.
> 
> The mentioned version is the first one which includes fixes for the
> "BleedingTooth" issues.
> 
> Can you check if applying the changes discussed in
> https://lore.kernel.org/linux-bluetooth/20201024002251.1389267-1-luiz.de...@gmail.com/
> address the issue for you?

Hi, can you confirm: is the issue still reproducible for you with a
recent kernel, the one from Debian testing in meanwhile to 5.10.40-1?

If yes, are you able to test current mainline?

If yes, are the above changes discussed resolving the issue for you?

Regards,
Salvatore

Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38

[Bernhard Übelacker]

Hello Jim,
I am not involved in packaging, but came to this report by chance.



The attached file contains all the changes you devs have made in the kernel
configs from 5.10.28 (-6 package) to 5.10.38/.40 (-7 package). It was made with
meld.
~10 kernel parameters have changed and led to this mess, so I assume it would
be trivial for you to find the faulty one.


These parameters are not all that changed - there are around 1400 patches
added upstream to the kernel between v5.10.28 and v5.10.38.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v5.10.38


Kind regards,
Bernhard

Bug#986822: BUG#986822 Broadwell SST CATPT Sound module

[Vincent Blut]

Hi,

Le 2021-06-05 08:31, Dekks Herton a écrit :
> Hi
> 
> Additional alsa-info script output

From a quick look, alsa-info reports that you're running both PipeWire and
PulseAudio sound servers. While it may not be the root cause of your issue,
if you want to stick with the former, please disable the latter:
$ sudo systemctl --user disable --now pulseaudio.service pulseaudio.socket

Note though that using PipeWire as a substitute to PulseAudio/JACK/ALSA in
Debian 11 is considered experimental.

Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#893912:

[vladikcomper]

Hello,

I have RTL8821AE, and according to my tests, the device functions
perfectly without "rtl_bt/rtl8821a_config.bin" firmware. So I believe
trying to symlink different firmware to this file for the sake of just
bypassing the error message alone can be unnecessary and harmful.

It appears that this specific firmware isn't provided by the
manufacturer and is missing in the latest Linux kernel at the time of
writing (please check:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_bt).


For anyone getting other missing firmware errors regarding the
RTL8821AE device, like "rtl_bt/rtl8821a_fw.bin", please install the
"firmware-realtek" package (make sure to add "non-free" component to
your sources list to make this available).


Some Debian desktop installations seem to misconfigure PulseAudio,
which may result in failing to negotiate connection with Bluetooth
speakers/headphones even when your Bluetooth adapter is fully
functional. The symptom of this problem is usually a "Connection
Failed: Protocol not available" message.
To work around this problem, make sure "pulseaudio-module-bluetooth"
is installed, then run the following:

pactl load-module module-bluetooth-discover


Best regards,
Vladislav

Bug#989010: linux-image-5.10.0-7-amd64: No display (post, grub, boot messages and desktop) after the upgrade to 5.10.38

[jim_p]

Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com

One more week passed with no issues. That's how things are when a kernel works
as it should and the gpu driver is flawless. Stability that matches the one of
a really stable distro or the one of windows 7.

As I expected, there were no replies on my issue, even now that you have full
logs of what was going on. Maybe it was because I did not raise the severity to
critical, so as to "force" you look at it.
Or, one simple word, incompetence. You just want to blame others'
configurations for your faulty builds and hide your irresponsibilities behind
words like "tainted", admit it.

As for the cards, now that they were tested by a different person, the ati is
totally dead and the nvidia one fails to build on 8 out of 10 times. So it is
not my hardware that makes them "seem dead". They ARE dead, thanks to that
garbage kernel update you made.

I read today that debian 11 will be released by the end of July, so I hope
there will be at least one more kernel upgrade until then. I will check if any
of the kernel parameters have changed by then and I will consider testing it
again.

Processed: bug 989778 is forwarded to https://lore.kernel.org/lkml/ymwl4unfbavrd...@eldamar.lan/T/#u

[Debian Bug Tracking System]

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

> forwarded 989778 
> https://lore.kernel.org/lkml/ymwl4unfbavrd...@eldamar.lan/T/#u
Bug #989778 [src:linux,src:xen] linux-image-5.10.0-7-amd64: regression: 
Firewire audio interface fails to work properly
Set Bug forwarded-to-address to 
'https://lore.kernel.org/lkml/ymwl4unfbavrd...@eldamar.lan/T/#u'.
> thanks
Stopping processing here.

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

Bug#989778: Regression in at least 5.10.y and mainline: Firewire audio interface fails to work properly (when booted under Xen)

[Salvatore Bonaccorso]

Hi,

On Sun, Jun 13, 2021 at 06:05:37AM +1000, 小太 wrote:
> Package: src:linux
> Version: 5.10.40-1
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: nos...@kota.moe
> 
> After updating from linux-image-5.10.0-6-amd64, jackd now fails to sync to my
> DICE-compatible firewire audio interface (Profire 610), with the following
> error messages (full log attached):
> 
> > $ jackd -d firewire -v
> > jackdmp 1.9.12
> > ...snip...
> > 00301056761: Warning (StreamProcessorManager.cpp)[ 913] 
> > alignReceivedStreams:
> xrun while aligning streams...
> > 00301056793: Error (StreamProcessorManager.cpp)[ 877] syncStartAll: Could 
> > not
> align streams...
> > 00301056829: Fatal (StreamProcessorManager.cpp)[1025] start: Could not
> syncStartAll...
> > 00301400626: Warning (TimestampedBuffer.cpp)[ 248] calculateRate: 
> > (0x1fa5a20)
> rate ( 708.18713) more that 10% off nominal (rate= 512.0, diff=
> 5665.497, update_period=8)
> > 00301416642: Warning (TimestampedBuffer.cpp)[ 248] calculateRate: 
> > (0x1fa5a20)
> rate ( 686.49011) more that 10% off nominal (rate= 512.0, diff=
> 5491.921, update_period=8)
> > 00301416925: Warning (devicemanager.cpp)[ 925] startStreaming: Failed to
> start SPM!
> > firewire ERR: Could not start streaming threads
> > Cannot start driver
> > JackServer::Start() failed with -1
> > 00301424329: Warning (ieee1394service.cpp)[1509] freeIsoChannel:  Channel 1
> not registered
> > 00301424360: Error (dice_avdevice.cpp)[1440] startstopStreamByIndex: Could
> not deallocate iso channel for SP 1 (ARX 0)
> > 00301424397: Warning (devicemanager.cpp)[ 959] stopStreamingOnDevice: Could
> not stop stream 1 of device 0x1f6e600
> > 00301424406: Warning (devicemanager.cpp)[ 931] startStreaming: Could not 
> > stop
> streaming on device 0x1f6e600!
> > 00301424429: Fatal (ffado.cpp)[ 220] ffado_streaming_start: Could not start
> the streaming system
> > Failed to start server
> > no message buffer overruns
> 
> Additionally, I also tried using the snd-dice driver to expose the audio
> interface directly in ALSA. While the interface did appear and was usable
> there, all inputs came out of my speakers highly distorted, with channels
> bleeding into each other - practically unusable.
> 
> I've reproduced the issue on upstream kernel version v5.13-rc5+
> (ad347abe4a9876b1f65f408ab467137e88f77eb4), and bisected the first bad commit
> down to 85a5a6875ca93dc4efbf20df942ba41d27a917e3.
> 
> To double check commit 85a5a6875ca93dc4efbf20df942ba41d27a917e3 was indeed the
> issue, I built the latest v5.10 kernel v5.10.43 with the commit reverted, and
> indeed the issue went away.
> Unfortunately, the reverse patch would not apply to v5.13-rc5+, since it seems
> like the file has changed too much.

A user in Debian reported the above issue, which was reproducible with
5.13-rc5 and 5.10.y as packaged in Debian and found that 85a5a6875ca9
("swiotlb: don't modify orig_addr in swiotlb_tbl_sync_single") that
introduced the issue.

The full bug log is at https://bugs.debian.org/989778

I'm CC'ing as well the xen-devel list, as it appears from
https://bugs.debian.org/989778#10 that the issue is only exposed when booting
under Xen.

Any ideas?

Regards,
Salvatore