Bug#1026016: linux-image-6.0.0-5-armmp-lpae: Internal error: Oops: 8000020e [#1] SMP ARM

2022-12-13 Thread w3host
Package: src:linux
Version: 6.0.10-2
Severity: important

Dear Maintainer,

Our linux server is completly freeze using this new 6.x version of kernels 
(uptime: from 4 hours to 2-3 weeks).

Kernel log in console:

KERNEL: 6.0.0-5-armmp-lpae, Debian 6.0.10-2:
[14477.237308] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[14477.243277] rcu: 0-...0: (6 ticks this GP) idle=8934/1/0x4000 
softirq=99901/99903 fqs=1050
[14540.266963] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[14540.272933] rcu: 0-...0: (6 ticks this GP) idle=8934/1/0x4000 
softirq=99901/99903 fqs=3701
[14603.296600] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[14603.302570] rcu: 0-...0: (6 ticks this GP) idle=8934/1/0x4000 
softirq=99901/99903 fqs=6352
[14613.316360] 8<--- cut here ---
[14613.319476] Unable to handle kernel paging request at virtual address 
c3a12b58
[14613.326706] [c3a12b58] *pgd=8040207003, *pmd=4043a0071d(bad)
[14613.333094] Internal error: Oops: 820e [#1] SMP ARM
[14613.338328] Modules linked in: xt_recent nft_limit xt_limit xt_tcpudp 
xt_conntrack nft_compat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 nfc
[14613.338900]  ohci_hcd scsi_mod ehci_platform ehci_hcd musb_hdrc scsi_common 
phy_sun4i_usb udc_core usbcore sunxi_mmc sun4i_drm sun4i_frontend sun4i_tcon 
sunm
[14613.444012] CPU: 0 PID: 263 Comm: sugov:0 Tainted: G C 
6.0.0-5-armmp-lpae #1  Debian 6.0.10-2
[14613.453928] Hardware name: Allwinner sun7i (A20) Family
[14613.459150] PC is at 0xc3a12b58
[14613.462310] LR is at 0x11ac
[14613.465455] pc : []lr : []psr: 60010193
[14613.471720] sp : f09f1db0  ip : 0001  fp : 
[14613.476943] r10:   r9 :   r8 : 2aea5400
[14613.482166] r7 : 2aea5400  r6 : c2443c00  r5 : c2688b40  r4 : 2aea5400
[14613.488692] r3 : 0001  r2 :   r1 : 2aea5400  r0 : 
[14613.495218] Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment 
user
[14613.502441] Control: 30c5387d  Table: 44cce500  DAC: fffd
[14613.508183] Register r0 information: NULL pointer
[14613.512896] Register r1 information: non-paged memory
[14613.517950] Register r2 information: NULL pointer
[14613.522658] Register r3 information: non-paged memory
[14613.527713] Register r4 information: non-paged memory
[14613.532767] Register r5 information: slab kmalloc-192 start c2688b40 pointer 
offset 0 size 192
[14613.541408] Register r6 information: slab kmalloc-192 start c2443c00 pointer 
offset 0 size 192
[14613.550040] Register r7 information: non-paged memory
[14613.555095] Register r8 information: non-paged memory
[14613.560149] Register r9 information: NULL pointer
[14613.564856] Register r10 information: NULL pointer
[14613.569650] Register r11 information: NULL pointer
[14613.57] Register r12 information: non-paged memory
[14613.579584] Process sugov:0 (pid: 263, stack limit = 0xa0a15a9d)
[14613.585597] Stack: (0xf09f1db0 to 0xf09f2000)
[14613.589959] 1da0: 00680040 b4aa67a0 
c2443c00 c099e5c4
[14613.598138] 1dc0: c244 c2443c00 b4aa47a0 c2443480 2aea5400 016e3600 
39387000 
[14613.606315] 1de0:  c099e620 0e4e1c00 c2688b40  2aea5400 
c2443c00 f09f1edc
[14613.614493] 1e00: c0b70a74   c099ee34 2aea5400  
 2aea5400
[14613.622671] 1e20: c171edb0 324c0d96 c171e978 c271ca40 2aea5400 ef690058 
2aea5400 f09f1edc
[14613.630849] 1e40: c0b70a74   c099ef3c c3339200 c3339200 
ef690058 2aea5400
[14613.639027] 1e60: f09f1edc c0b70a74  c0b70aa0 c3339200 c9091480 
c9b67180 ef690058
[14613.647205] 1e80: f09f1edc c0b73794 0001 324c0d96 c271ca40 c3339200 
0007 ef690058
[14613.655383] 1ea0: c3339240 2aea5400 000afc80 324c0d96 c3339200 0007 
ef690058 c9091480
[14613.663561] 1ec0: 2aea5400 000afc80  c0b73b74 0001 c1765ec4 
 2aea5400
[14613.671738] 1ee0: 2aea5400 324c0d96 c3338a00  c17fc4c8 0003 
000ea600 c0b79b90
[14613.679916] 1f00: c9ba2054  0001 c9091500 2e172000 c3338a00 
000ea600 000afc80
[14613.688094] 1f20: 0024 324c0d96 0004 c9ba2040 c9ba2054  
000afc80 c9ba206c
[14613.696272] 1f40: 0001 c160b0a8 c04a1b30 c04a1b80 c9ba2040 c9ba2068 
c32fad00 c17cc5a4
[14613.704450] 1f60: c9ba206c c046fc4c  c3264f80 c32fad00 c046fbc4 
c9ba2068 c99c6880
[14613.712627] 1f80: f09cdb90   c0470a88 c3264f80 c04709b0 
 
[14613.720804] 1fa0:    c0400160   
 
[14613.728981] 1fc0:       
 
[14613.737157] 1fe0:     0013  
 
[14613.745399] Code:   bf3837c0  (c3a12a48)
[14613.751499] ---[ end trace  ]---
[14613.756213] NMI backtrace for cpu 0
[14613.756227] CPU: 0 PID: 263 Comm: sugov:0 Tainted: G  D  C 
6.0

Bug#1026028: Qualcomm NFA725A not working on firmware-linux-nonfree 20221109-4

2022-12-13 Thread Tarek Saier
Package: firmware-linux-nonfree
Version: 20221109-4
Severity: important

Dear Maintainer,

same as the reporter of #1021157, I am also using a ThinkPad T14s Gen3
with the Qualcomm NFA725A wifi card ("Qualcomm Wi-Fi 6E NFA725A 11AX
(2x2) & Bluetooth(R) 5.0" reported in lshw as "QCNFA765 Wireless
Network Adapter").

On a fresh install of Debian 12 from the current ISO
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/bookworm_di_alpha1+nonfree/amd64/iso-cd/
no wireless card is detected. After updating packages, installing
firmware-linux-nonfree, and rebooting, Debian tries to load firmware
(ath11k/WCN6855.hw2.1/amss.bin) but this fails.

dmesg output:
  [2.635425] mhi mhi0: firmware: failed to load
ath11k/WCN6855/hw2.1/amss.bin (-2)
  [2.635435] firmware_class: See https://wiki.debian.org/Firmware
or information about missing firmware
  [2.635444] mhi mhi0: firmware: failed to load
ath11k/WCN6855/hw2.1/amss.bin (-2)
  [2.635448] mhi mhi0: Direct firmware load for
ath11k/WCN6855/hw2.1/amss.bin failed with error -2
  [2.635451] mhi mhi0: Error loading firmware: -2
  [2.635493] ath11k_pci :01:00.0: failed to power up mhi: -110
  [2.635499] ath11k_pci :01:00.0: failed to start mhi: -110
  [2.635506] ath11k_pci :01:00.0: failed to power up :-110

Given that bug report #1021157 was closed with
- firmware-nonfree (20221012-1) unstable
and I am running
- firmware-nonfree 20221109-4 on testing
I assumed the card should work. If I'm missing something please let me know.

Attached:
- dmesg.txt
- lshw.txt
- lspci.txt

Thanks in advance for any insight
Tarek

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

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

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20221109-4
ii  firmware-misc-nonfree  20221109-4

Versions of packages firmware-linux-nonfree recommends:
ii  amd64-microcode  3.20220411.1
ii  intel-microcode  3.20221108.1

firmware-linux-nonfree suggests no packages.

-- no debconf information



Bug#1026028: Qualcomm NFA725A not working on firmware-linux-nonfree 20221109-4

2022-12-13 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo

Hi,

On Tue, Dec 13, 2022 at 02:12:24PM +0100, Tarek Saier wrote:
> Package: firmware-linux-nonfree
> Version: 20221109-4
> Severity: important
> 
> Dear Maintainer,
> 
> same as the reporter of #1021157, I am also using a ThinkPad T14s Gen3
> with the Qualcomm NFA725A wifi card ("Qualcomm Wi-Fi 6E NFA725A 11AX
> (2x2) & Bluetooth(R) 5.0" reported in lshw as "QCNFA765 Wireless
> Network Adapter").
> 
> On a fresh install of Debian 12 from the current ISO
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/bookworm_di_alpha1+nonfree/amd64/iso-cd/
> no wireless card is detected. After updating packages, installing
> firmware-linux-nonfree, and rebooting, Debian tries to load firmware
> (ath11k/WCN6855.hw2.1/amss.bin) but this fails.
> 
> dmesg output:
>   [2.635425] mhi mhi0: firmware: failed to load
> ath11k/WCN6855/hw2.1/amss.bin (-2)
>   [2.635435] firmware_class: See https://wiki.debian.org/Firmware
> or information about missing firmware
>   [2.635444] mhi mhi0: firmware: failed to load
> ath11k/WCN6855/hw2.1/amss.bin (-2)
>   [2.635448] mhi mhi0: Direct firmware load for
> ath11k/WCN6855/hw2.1/amss.bin failed with error -2
>   [2.635451] mhi mhi0: Error loading firmware: -2
>   [2.635493] ath11k_pci :01:00.0: failed to power up mhi: -110
>   [2.635499] ath11k_pci :01:00.0: failed to start mhi: -110
>   [2.635506] ath11k_pci :01:00.0: failed to power up :-110
> 
> Given that bug report #1021157 was closed with
> - firmware-nonfree (20221012-1) unstable
> and I am running
> - firmware-nonfree 20221109-4 on testing
> I assumed the card should work. If I'm missing something please let me know.

The firmware is contained in the firmware-atheros package:

firmware-atheros: /lib/firmware/ath11k/WCN6855/hw2.1/amss.bin

Do you have that one installed as well?

Regards,
Salvatore



Processed: Re: Bug#1026028: Qualcomm NFA725A not working on firmware-linux-nonfree 20221109-4

2022-12-13 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + moreinfo
Bug #1026028 [firmware-linux-nonfree] Qualcomm NFA725A not working on 
firmware-linux-nonfree 20221109-4
Added tag(s) moreinfo.

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



Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u

2022-12-13 Thread Adi Kriegisch
Source: linux
Version: 5.10.158-1

Dear maintainers,

we just upgraded our xen test cluster's kernel to the latest kernel from
s-p-u and noticed that network communication is broken. We do have a
'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
communication is possible for the domU.

We can see packets arrive at the domU and packets leave the domU; but they
never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
counters stay at 0 too).

When migrating the domU back to the other server which has not been
upgraded, the machine is reachable again.

If there is anything we can do to help fixing that issue, we'll gladly do
that!

Thank you very much!

-- Adi


signature.asc
Description: PGP signature


Bug#1026028: Qualcomm NFA725A not working on firmware-linux-nonfree 20221109-4

2022-12-13 Thread Tarek Saier
Hi Salvatore,

thank you for the quick reply.
The firmware-atheros package was missing. Installing it fixed the issue.

Kind regards
Tarek

On Tue, Dec 13, 2022 at 3:04 PM Salvatore Bonaccorso  wrote:
>
> Control: tags -1 + moreinfo
>
> Hi,
>
> On Tue, Dec 13, 2022 at 02:12:24PM +0100, Tarek Saier wrote:
> > Package: firmware-linux-nonfree
> > Version: 20221109-4
> > Severity: important
> >
> > Dear Maintainer,
> >
> > same as the reporter of #1021157, I am also using a ThinkPad T14s Gen3
> > with the Qualcomm NFA725A wifi card ("Qualcomm Wi-Fi 6E NFA725A 11AX
> > (2x2) & Bluetooth(R) 5.0" reported in lshw as "QCNFA765 Wireless
> > Network Adapter").
> >
> > On a fresh install of Debian 12 from the current ISO
> > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/bookworm_di_alpha1+nonfree/amd64/iso-cd/
> > no wireless card is detected. After updating packages, installing
> > firmware-linux-nonfree, and rebooting, Debian tries to load firmware
> > (ath11k/WCN6855.hw2.1/amss.bin) but this fails.
> >
> > dmesg output:
> >   [2.635425] mhi mhi0: firmware: failed to load
> > ath11k/WCN6855/hw2.1/amss.bin (-2)
> >   [2.635435] firmware_class: See https://wiki.debian.org/Firmware
> > or information about missing firmware
> >   [2.635444] mhi mhi0: firmware: failed to load
> > ath11k/WCN6855/hw2.1/amss.bin (-2)
> >   [2.635448] mhi mhi0: Direct firmware load for
> > ath11k/WCN6855/hw2.1/amss.bin failed with error -2
> >   [2.635451] mhi mhi0: Error loading firmware: -2
> >   [2.635493] ath11k_pci :01:00.0: failed to power up mhi: -110
> >   [2.635499] ath11k_pci :01:00.0: failed to start mhi: -110
> >   [2.635506] ath11k_pci :01:00.0: failed to power up :-110
> >
> > Given that bug report #1021157 was closed with
> > - firmware-nonfree (20221012-1) unstable
> > and I am running
> > - firmware-nonfree 20221109-4 on testing
> > I assumed the card should work. If I'm missing something please let me know.
>
> The firmware is contained in the firmware-atheros package:
>
> firmware-atheros: /lib/firmware/ath11k/WCN6855/hw2.1/amss.bin
>
> Do you have that one installed as well?
>
> Regards,
> Salvatore



Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u

2022-12-13 Thread Diederik de Haas
On Tuesday, 13 December 2022 15:40:04 CET Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
> 
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
> communication is possible for the domU.
> 
> If there is anything we can do to help fixing that issue, we'll gladly do
> that!

https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
 describes a (relatively simple) way to test a patch.

I found in current master/6.1 branch 2 commits which may be relevant:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
id=7dfa764e0223a324366a2a1fc056d4d9d4e95491

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
id=9e624651859214fb2c4e442b059eba0aefcd0801

You'd possibly need to backport it to the 5.10 code, but if you can do that 
and test whether the updated kernel fixes the issue, that would be great.

If you have any questions, feel free to ask them.

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


Bug#1026028: marked as done (Qualcomm NFA725A not working on firmware-linux-nonfree 20221109-4)

2022-12-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Dec 2022 17:54:37 +0100
with message-id 
and subject line Re: Bug#1026028: Qualcomm NFA725A not working on 
firmware-linux-nonfree 20221109-4
has caused the Debian Bug report #1026028,
regarding Qualcomm NFA725A not working on firmware-linux-nonfree 20221109-4
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.)


-- 
1026028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-linux-nonfree
Version: 20221109-4
Severity: important

Dear Maintainer,

same as the reporter of #1021157, I am also using a ThinkPad T14s Gen3
with the Qualcomm NFA725A wifi card ("Qualcomm Wi-Fi 6E NFA725A 11AX
(2x2) & Bluetooth(R) 5.0" reported in lshw as "QCNFA765 Wireless
Network Adapter").

On a fresh install of Debian 12 from the current ISO
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/bookworm_di_alpha1+nonfree/amd64/iso-cd/
no wireless card is detected. After updating packages, installing
firmware-linux-nonfree, and rebooting, Debian tries to load firmware
(ath11k/WCN6855.hw2.1/amss.bin) but this fails.

dmesg output:
  [2.635425] mhi mhi0: firmware: failed to load
ath11k/WCN6855/hw2.1/amss.bin (-2)
  [2.635435] firmware_class: See https://wiki.debian.org/Firmware
or information about missing firmware
  [2.635444] mhi mhi0: firmware: failed to load
ath11k/WCN6855/hw2.1/amss.bin (-2)
  [2.635448] mhi mhi0: Direct firmware load for
ath11k/WCN6855/hw2.1/amss.bin failed with error -2
  [2.635451] mhi mhi0: Error loading firmware: -2
  [2.635493] ath11k_pci :01:00.0: failed to power up mhi: -110
  [2.635499] ath11k_pci :01:00.0: failed to start mhi: -110
  [2.635506] ath11k_pci :01:00.0: failed to power up :-110

Given that bug report #1021157 was closed with
- firmware-nonfree (20221012-1) unstable
and I am running
- firmware-nonfree 20221109-4 on testing
I assumed the card should work. If I'm missing something please let me know.

Attached:
- dmesg.txt
- lshw.txt
- lspci.txt

Thanks in advance for any insight
Tarek

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

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

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20221109-4
ii  firmware-misc-nonfree  20221109-4

Versions of packages firmware-linux-nonfree recommends:
ii  amd64-microcode  3.20220411.1
ii  intel-microcode  3.20221108.1

firmware-linux-nonfree suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
H Tarek,

On Tue, Dec 13, 2022 at 04:16:26PM +0100, Tarek Saier wrote:
> Hi Salvatore,
> 
> thank you for the quick reply.
> The firmware-atheros package was missing. Installing it fixed the issue.

Great! Thanks for confirming. 

FTR, you can for instance find which of the firwmare package build
from the firmware-nonfree source contains a specific firmware in the
package desciption (or through other means like apt-file or package
content search).

Regards,
Salvatore--- End Message ---


Bug#1022170: Update

2022-12-13 Thread Rod Webster
I have been able to resolve this issue on one PC by building deb files of
the 6.1 kernel from pristine sources from kernel.org with the PREEMPT_RT
patch applied.
The only change I made using xconfig was to enable the fully preemptible
kernel and set the following keys to permit building of the debs.

scripts/config --disable SYSTEM_REVOCATION_KEYS
scripts/config --disable DEBUG_INFO
scripts/config --enable DEBUG_INFO_NONE
scripts/config --set-str SYSTEM_TRUSTED_KEYS ""


Once this kernel and the R8168-dkms driver for my hardware was installed,
the issue appears to be resolved.

I also built Linuxcnc from source on Arch Linux where the issue was not
evident.

These two data points confirm in my mind the Debian implementation of the
Realtek network device drivers is buggy, certainly for the RT image and
probably for the default image.
I believe this will become a major support issue once Bookworm becomes the
stable release.
It would be great if the kernel team could review this and find a
resolution before then.

Rod Webster

VMN®

www.vmn.com.au

Ph: 1300 896 832

Mob: +61 435 765 611


Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u

2022-12-13 Thread Adi Kriegisch
Dear Diederik,

> > we just upgraded our xen test cluster's kernel to the latest kernel from
> > s-p-u and noticed that network communication is broken. We do have a
> > 'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
> > communication is possible for the domU.
> > 
> > If there is anything we can do to help fixing that issue, we'll gladly do
> > that!
thank you very much for your help!
 
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
>  describes a (relatively simple) way to test a patch.
> 
> I found in current master/6.1 branch 2 commits which may be relevant:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
> id=7dfa764e0223a324366a2a1fc056d4d9d4e95491
This patch did the trick; while digging through the source, I noticed that
this fix is already included in the patch for XSA-423[1][2] referenced at
the oss-sec list.
Obviously the patch for XSA-423v1 has been included in 5.10.158-1 while
XSA-423v2 is the most recent version of the patch. The difference between
the two versions of that patch is exactly the initialization of the variable
'err' that just fixes this issue.
 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?
> id=9e624651859214fb2c4e442b059eba0aefcd0801
This patch does not seem to be necessary as the patch for XSA-424 does
alreay contain a different fix for this issue.

> You'd possibly need to backport it to the 5.10 code, but if you can do that 
> and test whether the updated kernel fixes the issue, that would be great.
Again: thank you very much for the quick response. I can confirm that the
issue is indeed fixed with the first patch; maybe updating to XSA-423v2 is
the more appropriate way to fix the issue.

all the best,
Adi

[1] https://seclists.org/oss-sec/2022/q4/174
[2] https://seclists.org/oss-sec/2022/q4/att-174/xsa423-linux.patch


signature.asc
Description: PGP signature


Processing of linux_5.10.158-2_source.changes

2022-12-13 Thread Debian FTP Masters
linux_5.10.158-2_source.changes uploaded successfully to localhost
along with the files:
  linux_5.10.158-2.dsc
  linux_5.10.158-2.debian.tar.xz
  linux_5.10.158-2_source.buildinfo

Greetings,

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



Bug#1026035: xen netback broken with 5.10.0-20-amd64 in s-p-u

2022-12-13 Thread Salvatore Bonaccorso
Source: linux
Source-Version: 5.10.158-2

Hi Adi,

On Tue, Dec 13, 2022 at 03:40:04PM +0100, Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
> 
> Dear maintainers,
> 
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
> communication is possible for the domU.
> 
> We can see packets arrive at the domU and packets leave the domU; but they
> never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
> counters stay at 0 too).
> 
> When migrating the domU back to the other server which has not been
> upgraded, the machine is reachable again.
> 
> If there is anything we can do to help fixing that issue, we'll gladly do
> that!
> 
> Thank you very much!

This is adressed with a subsequent upload which should hit the archive
soon and hopefully in time for the point release (I did miss to close
this bug with the upload, doing so manually to have proper version
tracking).

Regards,
Salvatore



Processed: tagging 1026035

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

> tags 1026035 + upstream fixed-upstream
Bug #1026035 [src:linux] xen netback broken with 5.10.0-20-amd64 in s-p-u
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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



Bug#1026035: marked as done (xen netback broken with 5.10.0-20-amd64 in s-p-u)

2022-12-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Dec 2022 22:17:33 +0100
with message-id 
and subject line Re: Bug#1026035: xen netback broken with 5.10.0-20-amd64 in 
s-p-u
has caused the Debian Bug report #1026035,
regarding xen netback broken with 5.10.0-20-amd64 in s-p-u
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.)


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

Dear maintainers,

we just upgraded our xen test cluster's kernel to the latest kernel from
s-p-u and noticed that network communication is broken. We do have a
'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
communication is possible for the domU.

We can see packets arrive at the domU and packets leave the domU; but they
never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
counters stay at 0 too).

When migrating the domU back to the other server which has not been
upgraded, the machine is reachable again.

If there is anything we can do to help fixing that issue, we'll gladly do
that!

Thank you very much!

-- Adi


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.10.158-2

Hi Adi,

On Tue, Dec 13, 2022 at 03:40:04PM +0100, Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
> 
> Dear maintainers,
> 
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After upgrading dom0's kernel, no
> communication is possible for the domU.
> 
> We can see packets arrive at the domU and packets leave the domU; but they
> never arrive at the virtual interface in dom0 (rx counter stays at 0 and error
> counters stay at 0 too).
> 
> When migrating the domU back to the other server which has not been
> upgraded, the machine is reachable again.
> 
> If there is anything we can do to help fixing that issue, we'll gladly do
> that!
> 
> Thank you very much!

This is adressed with a subsequent upload which should hit the archive
soon and hopefully in time for the point release (I did miss to close
this bug with the upload, doing so manually to have proper version
tracking).

Regards,
Salvatore--- End Message ---


linux_5.10.158-2_source.changes ACCEPTED into proposed-updates->stable-new

2022-12-13 Thread Debian FTP Masters
Thank you for your contribution to Debian.

Mapping bullseye to stable.
Mapping stable to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Dec 2022 21:46:50 +0100
Source: linux
Architecture: source
Version: 5.10.158-2
Distribution: bullseye
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux (5.10.158-2) bullseye; urgency=medium
 .
   * xen/netback: fix build warning
Checksums-Sha1:
 33d67705abac52a139304a7eeacff5f53fa71491 197238 linux_5.10.158-2.dsc
 7dc25ca2bbaf271dc57d3b7b4e1b5615f182fd49 3487356 linux_5.10.158-2.debian.tar.xz
 eb693403acb03944995cbbfe8166f901e8648276 6847 linux_5.10.158-2_source.buildinfo
Checksums-Sha256:
 938feb8baa4c955c3313eb4e6e03f3f556e86b8a74a578d91691edab29db07f3 197238 
linux_5.10.158-2.dsc
 bfb86bb848fc869105455d59363f2323963278988168b32f54dc71f0eb246b69 3487356 
linux_5.10.158-2.debian.tar.xz
 e57f4db82abe781a6f12162f25f8e00155faa9ef2a0c37aa0e110ce5a9de44db 6847 
linux_5.10.158-2_source.buildinfo
Files:
 50d283d59e8da8fdab724f151ecc7cce 197238 kernel optional linux_5.10.158-2.dsc
 df02a6a5015aefa5bef0e688521bf468 3487356 kernel optional 
linux_5.10.158-2.debian.tar.xz
 3001389d18387042543f290ca430124f 6847 kernel optional 
linux_5.10.158-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmOY5kRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ELlQP/iio3PaIuF93yN4jbYv7Xs/gl7LSE3QA
QBq43UDzwefnxP7rBEUdvOJN55Th0cuvqRU9CtA7hS3yTYfHEomGX+oLliHM3HXo
QshfTRsuhQMU40qv9XPgc8ycNZP6jP+KmmJj2cnq9Hzbezo/Wz8y10jlVJi0BCYv
R8SaceJMMBk46q3LMmseTBU7hGkdR02tR0ANJHdKkLZ6IMS3BTzzeCl6NYy93FTV
A3SljrQahJqaq96qXkLQ5/UjM3Pl10GKy/ZA2AiVF0XicEnK0P8NweFIcGwb5EW8
9jx1ZmVMYkPnMmQ932xABhze+gQ3T+Cj3oMoVBsz8fkTaQExA4+hN2g7hptkXB5z
4Ql2yeH5JW0cXrbGSkl83WQaFiYBLeJX8Z5mHdPz/3IFoMecVHghbdCh+pqIVzIc
WlUIxs8RP56ZWzM3hp9yMwQz7Qjci7v6fJkzKR1/c7uIEEJ0upiiviWUDJit+tby
C6LFR0AqwGMjupfDnSU4/bHapZvsWKPSkZaX2PJ3LfVvJpDdIjwfRX6phBiLmIWu
lby2SH95TIcVfwOMO00yovq0p6LvBx0IrBMokH2XIUyfJxjFhV1q/OKKvZOK5HfX
BMiRxdZ+XVRP7WsoZfP7cwdeHJfvMSGAP6wTVKgyCAwWRaZ/hfBFo+EtoBDDUKzm
D8X3FNS8Apza
=tXUk
-END PGP SIGNATURE-



linux_5.10.158-2_source.changes ACCEPTED into proposed-updates

2022-12-13 Thread Debian FTP Masters
Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Dec 2022 21:46:50 +0100
Source: linux
Architecture: source
Version: 5.10.158-2
Distribution: bullseye
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Changes:
 linux (5.10.158-2) bullseye; urgency=medium
 .
   * xen/netback: fix build warning
Checksums-Sha1:
 33d67705abac52a139304a7eeacff5f53fa71491 197238 linux_5.10.158-2.dsc
 7dc25ca2bbaf271dc57d3b7b4e1b5615f182fd49 3487356 linux_5.10.158-2.debian.tar.xz
 eb693403acb03944995cbbfe8166f901e8648276 6847 linux_5.10.158-2_source.buildinfo
Checksums-Sha256:
 938feb8baa4c955c3313eb4e6e03f3f556e86b8a74a578d91691edab29db07f3 197238 
linux_5.10.158-2.dsc
 bfb86bb848fc869105455d59363f2323963278988168b32f54dc71f0eb246b69 3487356 
linux_5.10.158-2.debian.tar.xz
 e57f4db82abe781a6f12162f25f8e00155faa9ef2a0c37aa0e110ce5a9de44db 6847 
linux_5.10.158-2_source.buildinfo
Files:
 50d283d59e8da8fdab724f151ecc7cce 197238 kernel optional linux_5.10.158-2.dsc
 df02a6a5015aefa5bef0e688521bf468 3487356 kernel optional 
linux_5.10.158-2.debian.tar.xz
 3001389d18387042543f290ca430124f 6847 kernel optional 
linux_5.10.158-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmOY5kRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ELlQP/iio3PaIuF93yN4jbYv7Xs/gl7LSE3QA
QBq43UDzwefnxP7rBEUdvOJN55Th0cuvqRU9CtA7hS3yTYfHEomGX+oLliHM3HXo
QshfTRsuhQMU40qv9XPgc8ycNZP6jP+KmmJj2cnq9Hzbezo/Wz8y10jlVJi0BCYv
R8SaceJMMBk46q3LMmseTBU7hGkdR02tR0ANJHdKkLZ6IMS3BTzzeCl6NYy93FTV
A3SljrQahJqaq96qXkLQ5/UjM3Pl10GKy/ZA2AiVF0XicEnK0P8NweFIcGwb5EW8
9jx1ZmVMYkPnMmQ932xABhze+gQ3T+Cj3oMoVBsz8fkTaQExA4+hN2g7hptkXB5z
4Ql2yeH5JW0cXrbGSkl83WQaFiYBLeJX8Z5mHdPz/3IFoMecVHghbdCh+pqIVzIc
WlUIxs8RP56ZWzM3hp9yMwQz7Qjci7v6fJkzKR1/c7uIEEJ0upiiviWUDJit+tby
C6LFR0AqwGMjupfDnSU4/bHapZvsWKPSkZaX2PJ3LfVvJpDdIjwfRX6phBiLmIWu
lby2SH95TIcVfwOMO00yovq0p6LvBx0IrBMokH2XIUyfJxjFhV1q/OKKvZOK5HfX
BMiRxdZ+XVRP7WsoZfP7cwdeHJfvMSGAP6wTVKgyCAwWRaZ/hfBFo+EtoBDDUKzm
D8X3FNS8Apza
=tXUk
-END PGP SIGNATURE-