Bug#983586: linux-image-5.10.0-3-amd64: Please configure kernel with CONFIG_AMD_MEM_ENCRYPT=y

[Vincent Blut]

Hi,

Le 2021-02-26 20:26, bs.net a écrit :
> Package: src:linux
> Version: 5.10.13-1
> 
> Dear Maintainer,
> 
> please consider to set the Linux kernel option "CONFIG_AMD_MEM_ENCRYPT=y".
> 
> Without that option it is not possible to enable the memory encryption for AMD
> Secure Memory Encryption (SME).

I sent a merge request [1] to enable this feature, but it was deemed a bit late
for Bullseye.

> Thank you very much.
> 
> With kind regards

Cheers,
Vincent

[1] https://salsa.debian.org/kernel-team/linux/-/merge_requests/322


signature.asc
Description: PGP signature

Processed: tagging 981003

[Debian Bug Tracking System]

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

> tags 981003 + confirmed pending fixed-upstream
Bug #981003 [src:linux] Kernel paniced with null pointer dereference on 
Panasonic CF-SV9 notebook machine
Added tag(s) pending, fixed-upstream, and confirmed.
> thanks
Stopping processing here.

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

Bug#981003: Kernel paniced with null pointer dereference on Panasonic CF-SV9 notebook machine

[Salvatore Bonaccorso]

Hi,

On Fri, Feb 26, 2021 at 11:01:50PM +0900, Kubo Hiroshi wrote:
> Hi Salvatore,
> 
> > Would it be possible for you to test the two patches submitted as
> > https://lore.kernel.org/linux-acpi/20210208120104.204761-1-marcin.slus...@gmail.com/
> > and
> > https://lore.kernel.org/linux-acpi/20210208120104.204761-2-marcin.slus...@gmail.com/
> > ?
> 
> Yes, the first patch worked fine for my notebook machine.
> 
> I applied the fistpatch to the linux-image-5.10.13-1 source, built a
> linux-image-5.10.0-3-amd64-unsigned package,
> installed the package to my machine using dpkg, and the machine
> booted without kernel panic.
> 
> It seems that the second patch is just for comment fix, right? I did
> not applied the second patch.

Yes correct. Thanks for confirming the fix. I just have applied it so
that it can be inclueded in the next upload.

Regards,
Salvatore

Bug#983586: linux-image-5.10.0-3-amd64: Please configure kernel with CONFIG_AMD_MEM_ENCRYPT=y

[bs.net]

Package: src:linux
Version: 5.10.13-1

Dear Maintainer,

please consider to set the Linux kernel option "CONFIG_AMD_MEM_ENCRYPT=y".

Without that option it is not possible to enable the memory encryption for AMD
Secure Memory Encryption (SME).

Thank you very much.

With kind regards

Uploading linux (5.10.19-1)

[Salvatore Bonaccorso]

Hi,

I'm aiming to upload linux version 5.10.19-1 over the weekend. It
imports stable versions up to 5.10.19 containg several important
bugfixes, including security fixes for CVE-2021-20194, CVE-2021-26930,
CVE-2021-26931, CVE-2021-26932.

An ABI bump is included.

There are as well a couple of Debian specific (packaging) changes included,
which we think are still safe at this stage of the release preparation.

I'm listing the changes below:

   * [rt] Update to 5.10.14-rt28
   * Ignore __udp_gso_segment to avoid ABI changes
   * Ignore xhci_init_driver to avoid ABI changes
   * [rt] Update to 5.10.16-rt30
   * [rt] Refresh "tracing: Merge irqflags + preempt counter." for context
 changes
   * [rt] Update to 5.10.17-rt32
   * [rt] Refresh "um: synchronize kmsg_dumper" for context changes
   * [rt] Refresh "printk: move console printing to kthreads" for context
 changes

These go actually go just in the same class as the import of the new stable
versions.

   * Bump ABI to 4
 .
   * [x86] Enable PWM_CRC (Closes: #982808)
   * net/can: Enable CAN_J1939 as module
   * misc/eeprom: Enable EEPROM_EE1004 as module (Closes: #983495)

Those seemed very low risk to have additionally enabled, and user requested
them to have support respetively.

 .
   * bpf: enable CONFIG_BPF_LSM on all architectures. Not active by default,
 by explicitly setting CONFIG_LSM to include all other LSMs but not bpf.

We decided to include this because it will not be active by default but allows
people to start experimenting and developing bpf programs that can be attached
to LSM hooks (Luca Bocassi is Cc'ed here in case you have questions on that).

Regards,
Salvatore


signature.asc
Description: PGP signature

Bug#890343: linux: make fq_codel default for default_qdisc

[Vincent Blut]

Hi,

Le 2021-01-21 00:43, Ben Hutchings a écrit :
> On Wed, 2021-01-20 at 14:46 -0800, Noah Meyerhans wrote:
> > On Wed, Jan 20, 2021 at 11:39:16PM +0100, Vincent Blut wrote:
> > > > We could do that.  However, in the past (earlier in this bug,
> > > > even) it's
> > > > been pointed out that other packages should not be responsible
> > > > for
> > > > setting kernel policies, so changes like this should be the
> > > > responsibility of the kernel packages.  That seems like a
> > > > sensible
> > > > position to take.
> > > 
> > > If this is the position of the kernel team, then fine. But some
> > > packages *do*
> > > tweak kernel parameters using the sysctl interface mechanism. So
> > > does the kernel
> > > team provides documention about what is acceptable?
> > 
> > I think the distinction is that the other packages that tweak sysctl
> > values don't claim to be doing so on behalf of the kernel team.  If
> > the
> > kernel team is responsible for the values being set, then the
> > settings
> > should come from a package that the kernel team owns, not some other
> > package.
> 
> Right, maybe in linux-base?  Although that might annoy derivatives that
> want different defaults.
> 
> procps is the wrong place, not just because it's out of our hands, but
> because systemd applies sysctl configuration now and procps is
> optional.

Is there a definitive answer from the kernel team about how this should be
implemented? In the meantime, Noah sent [1].

> Ben.

Cheers,
Vincent

[1] https://salsa.debian.org/kernel-team/linux/-/merge_requests/309/diffs


signature.asc
Description: PGP signature

Bug#940821: NFS Caching broken in 4.19.37

[Anton Ivanov]

On 26/02/2021 15:03, Timo Rothenpieler wrote:
I think I can reproduce this, or something that at least looks very 
similar to this, on 5.10. Namely on 5.10.17 (On both Client and Server).


I think this is a different issue - see below.



We are running slurm, and since a while now (coincides with updating 
from 5.4 to 5.10, but a whole bunch of other stuff was updated at the 
same time, so it took me a while to correlate this) the logs it writes 
have been truncated, but only while they're being observed on the 
client, using tail -f or something like that.


Looks like this then:

On Server:

store01 /srv/export/home/users/timo/TestRun # ls -l slurm-41101.out
-rw-r--r-- 1 timo timo 1931 Feb 26 15:46 slurm-41101.out
store01 /srv/export/home/users/timo/TestRun # wc -l slurm-41101.out
61 slurm-41101.out


On Client:

timo@login01 ~/TestRun $ ls -l slurm-41101.out
-rw-r--r-- 1 timo timo 1931 Feb 26 15:46 slurm-41101.out
timo@login01 ~/TestRun $ wc -l slurm-41101.out
24 slurm-41101.out


See https://gist.github.com/BtbN/b9eb4fc08ccc53bb20087bce0bf9f826 for 
the respective file-contents.


If I run the same test job, wait until its done, and then look at its 
slurm.out file, it matches between NFS Client and Server.
If I tail -f the slurm.out on an NFS client, the file stops getting 
updated on the client, but keeps getting more logs written to it on 
the NFS server.


The slurm.out file is being written to by another NFS client, which is 
running on one of the compute nodes of the system. It's being reads 
from a login node.


These are two different clients, then what you see is possible on NFS 
with client side caching. If you have multiple clients reading/writing 
to the same files you usually need to tune the caching options and/or 
use locking. I suspect that if you leave it for a while (until the cache 
expires) it will sort itself out.


In my test-case it is just one client, it missed a file deletion and 
nothing short of an unmount and remount fixes that. I have waited for 30 
mins+. It does not seem to refresh or expire. I also see the opposite 
behavior - the bug shows up on 4.x up to at least 5.4. I do not see it 
on 5.10.


Brgds,







Timo


On 21.02.2021 16:53, Anton Ivanov wrote:

Client side. This seems to be an entirely client side issue.

A variety of kernels on the clients starting from 4.9 and up to 5.10 
using 4.19 servers. I have observed it on a 4.9 client versus 4.9 
server earlier.


4.9 fails, 4.19 fails, 5.2 fails, 5.4 fails, 5.10 works.

At present the server is at 4.19.67 in all tests.

Linux jain 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 
(2019-11-11) x86_64 GNU/Linux


I can set-up a couple of alternative servers during the week, but so 
far everything is pointing towards a client fs cache issue, not a 
server one.


Brgds,






--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/

Bug#940821: NFS Caching broken in 4.19.37

[Timo Rothenpieler]

I think I can reproduce this, or something that at least looks very 
similar to this, on 5.10. Namely on 5.10.17 (On both Client and Server).


We are running slurm, and since a while now (coincides with updating 
from 5.4 to 5.10, but a whole bunch of other stuff was updated at the 
same time, so it took me a while to correlate this) the logs it writes 
have been truncated, but only while they're being observed on the 
client, using tail -f or something like that.


Looks like this then:

On Server:

store01 /srv/export/home/users/timo/TestRun # ls -l slurm-41101.out
-rw-r--r-- 1 timo timo 1931 Feb 26 15:46 slurm-41101.out
store01 /srv/export/home/users/timo/TestRun # wc -l slurm-41101.out
61 slurm-41101.out


On Client:

timo@login01 ~/TestRun $ ls -l slurm-41101.out
-rw-r--r-- 1 timo timo 1931 Feb 26 15:46 slurm-41101.out
timo@login01 ~/TestRun $ wc -l slurm-41101.out
24 slurm-41101.out


See https://gist.github.com/BtbN/b9eb4fc08ccc53bb20087bce0bf9f826 for 
the respective file-contents.


If I run the same test job, wait until its done, and then look at its 
slurm.out file, it matches between NFS Client and Server.
If I tail -f the slurm.out on an NFS client, the file stops getting 
updated on the client, but keeps getting more logs written to it on the 
NFS server.


The slurm.out file is being written to by another NFS client, which is 
running on one of the compute nodes of the system. It's being reads from 
a login node.




Timo


On 21.02.2021 16:53, Anton Ivanov wrote:

Client side. This seems to be an entirely client side issue.

A variety of kernels on the clients starting from 4.9 and up to 5.10 
using 4.19 servers. I have observed it on a 4.9 client versus 4.9 server 
earlier.


4.9 fails, 4.19 fails, 5.2 fails, 5.4 fails, 5.10 works.

At present the server is at 4.19.67 in all tests.

Linux jain 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) 
x86_64 GNU/Linux


I can set-up a couple of alternative servers during the week, but so far 
everything is pointing towards a client fs cache issue, not a server one.


Brgds,






smime.p7s
Description: S/MIME Cryptographic Signature

firmware-nonfree_20210208-3_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Feb 2021 14:31:24 +0100
Source: firmware-nonfree
Binary: firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x 
firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-intelwimax 
firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas 
firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom 
firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc 
firmware-qlogic firmware-realtek firmware-samsung firmware-siano 
firmware-ti-connectivity
Architecture: source all
Version: 20210208-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: maximilian attems 
Description:
 firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
 firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards
 firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
 firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
 firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards
 firmware-cavium - Binary firmware for Cavium Ethernet adapters
 firmware-intel-sound - Binary firmware for Intel sound DSPs
 firmware-intelwimax - Binary firmware for Intel WiMAX Connection
 firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and 
pvrusb2 d
 firmware-iwlwifi - Binary firmware for Intel Wireless cards
 firmware-libertas - Binary firmware for Marvell wireless cards
 firmware-linux - Binary firmware for various drivers in the Linux kernel 
(metapack
 firmware-linux-nonfree - Binary firmware for various drivers in the Linux 
kernel (metapack
 firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel
 firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
 firmware-netronome - Binary firmware for Netronome network adapters
 firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 
3100 Se
 firmware-qcom-media - Binary firmware for Qualcomm graphics/video (dummy 
package)
 firmware-qcom-soc - Binary firmware for Qualcomm SoCs
 firmware-qlogic - Binary firmware for QLogic HBAs
 firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters
 firmware-samsung - Binary firmware for Samsung MFC video codecs
 firmware-siano - Binary firmware for Siano MDTV receivers
 firmware-ti-connectivity - Binary firmware for TI Connectivity wifi and 
BT/FM/GPS adapters
Closes: 983561
Changes:
 firmware-nonfree (20210208-3) unstable; urgency=medium
 .
   * misc-nonfree: Add missing config files for cxgb4 (closes: #983561)
   * Add missing intel firmwares in iwlwifi, intel-sound, misc-nonfree.
   * Ship all Qualcomm Atheros Bluetooth firmwares.
   * Complete all MediaTek firmwares.
 Thanks to Cyril Brulebois .
Checksums-Sha1:
 632579fe0dbc5c7eef9d9fc0681fa5cd1b81fc4d 3940 firmware-nonfree_20210208-3.dsc
 d0339a42edf20c42d5a3a783427e3982c708948a 789632 
firmware-nonfree_20210208-3.debian.tar.xz
 5b93115f9d811798478636c5454e915272ec3fe2 5687208 
firmware-amd-graphics_20210208-3_all.deb
 7025db4b5d18676c7351028e8ef86885b5cc7f6d 10022316 
firmware-atheros_20210208-3_all.deb
 e17a83f644f924bc431cb3aa47b6dccbd51aa93d 107580 
firmware-bnx2_20210208-3_all.deb
 2b9e1ee7f94ab27279e88e958cb663477e9f85ad 3401844 
firmware-bnx2x_20210208-3_all.deb
 6b4af432432929d918d9148c3e4b072dc93689f7 5015064 
firmware-brcm80211_20210208-3_all.deb
 9cdd800d69551032f8718fd4b33986ed653d9d48 655684 
firmware-cavium_20210208-3_all.deb
 f71a6a66197005ace77bf5bbd5c4984efc7e82c3 799392 
firmware-intel-sound_20210208-3_all.deb
 edd48c92fe16e5bbbe51b8e1c5a5850ba91cec56 1199048 
firmware-intelwimax_20210208-3_all.deb
 f79f8e878104a2845b068e07e1988e4d79600481 256496 
firmware-ipw2x00_20210208-3_all.deb
 734705716e616c8d0c182db30439c9812d7f769c 113952 
firmware-ivtv_20210208-3_all.deb
 a211246b62599034ad16ea9458fbb4449b60a580 12395212 
firmware-iwlwifi_20210208-3_all.deb
 67e5b006459ef4787b4fb8571871601e69768b6d 17653236 
firmware-libertas_20210208-3_all.deb
 4740364255da00866ea7d73532033935a7d2c703 22668 
firmware-linux-nonfree_20210208-3_all.deb
 640ac498a8f261cf46c972e030fd7ea28020ab9b 22924 
firmware-linux_20210208-3_all.deb
 0379fb676057e989d6d5b625c2e1d3fd2b62fc01 7823604 
firmware-misc-nonfree_20210208-3_all.deb
 cdf5cf916c4b1da0a697891aebfbbd8aec438cb6 275580 
firmware-myricom_20210208-3_all.deb
 540347a6694075d998f3456320f61867fedad4ff 1737296 
firmware-netronome_20210208-3_all.deb
 2b97c975d3bb8f2150e80ab2d980f21743093b39 1246828 
firmware-netxen_20210208-3_all.deb
 88b3ec1eccd7d050752bba60ea810a44ee39a3a6 12826 
firmware-nonfree_20210208-3_amd64.buildinfo
 e307928e3adf6def3c928e5810538b1ac842270b 22976 
firmware-qcom-media_20210208-3_all.deb
 46b6351ca42ab9aefc267ba175a49e4f78d67a25 14078356 
firmware-qcom-soc_20210208-3_all.deb
 2170f9d071ed37c828d270af66e9e1ea260632e0 3765072 

Bug#983561: marked as done (firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others)

[Debian Bug Tracking System]

Your message dated Fri, 26 Feb 2021 14:26:36 +
with message-id 
and subject line Bug#983561: fixed in firmware-nonfree 20210208-3
has caused the Debian Bug report #983561,
regarding firmware-misc-nonfree: broken-symlink 
/lib/firmware/cxgb4/t4-config.txt and others
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.)


-- 
983561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-misc-nonfree
Version: 20210208-2
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
X-Debbugs-Cc: t...@mirbsd.de

firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt -> 
configs/t4-config-default.txt
firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t5-config.txt -> 
configs/t5-config-default.txt
firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t6-config.txt -> 
configs/t6-config-default.txt





-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.139

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: firmware-nonfree
Source-Version: 20210208-3
Done: maximilian attems 

We believe that the bug you reported is fixed in the latest version of
firmware-nonfree, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated firmware-nonfree 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Feb 2021 14:31:24 +0100
Source: firmware-nonfree
Binary: firmware-amd-graphics firmware-atheros firmware-bnx2 firmware-bnx2x 
firmware-brcm80211 firmware-cavium firmware-intel-sound firmware-intelwimax 
firmware-ipw2x00 firmware-ivtv firmware-iwlwifi firmware-libertas 
firmware-linux firmware-linux-nonfree firmware-misc-nonfree firmware-myricom 
firmware-netronome firmware-netxen firmware-qcom-media firmware-qcom-soc 
firmware-qlogic firmware-realtek firmware-samsung firmware-siano 
firmware-ti-connectivity
Architecture: source all
Version: 20210208-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: maximilian attems 
Description:
 firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
 firmware-atheros - Binary firmware for Qualcomm Atheros wireless cards
 firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
 firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
 firmware-brcm80211 - Binary firmware for Broadcom/Cypress 802.11 wireless cards
 firmware-cavium - Binary firmware for Cavium Ethernet adapters
 firmware-intel-sound - Binary firmware for Intel sound DSPs
 firmware-intelwimax - Binary firmware for Intel WiMAX Connection
 firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and 
pvrusb2 d
 firmware-iwlwifi - Binary firmware for Intel Wireless cards
 firmware-libertas - Binary firmware for Marvell wireless cards
 firmware-linux - Binary firmware for various drivers in the Linux kernel 
(metapack
 firmware-linux-nonfree - Binary firmware for various drivers in the Linux 
kernel (metapack
 firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel
 firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
 firmware-netronome - Binary firmware for Netronome network adapters
 firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 
3100 Se
 

Bug#981003: Kernel paniced with null pointer dereference on Panasonic CF-SV9 notebook machine

[Kubo Hiroshi]

Hi Salvatore,

> Would it be possible for you to test the two patches submitted as
> https://lore.kernel.org/linux-acpi/20210208120104.204761-1-marcin.slus...@gmail.com/
> and
> https://lore.kernel.org/linux-acpi/20210208120104.204761-2-marcin.slus...@gmail.com/
> ?

Yes, the first patch worked fine for my notebook machine.

I applied the fistpatch to the linux-image-5.10.13-1 source, built a 
linux-image-5.10.0-3-amd64-unsigned package,
installed the package to my machine using dpkg, and the machine booted without 
kernel panic.

It seems that the second patch is just for comment fix, right? I did not 
applied the second patch.

Best regards,

--
Hiroshi Kubo

Processing of firmware-nonfree_20210208-3_amd64.changes

[Debian FTP Masters]

firmware-nonfree_20210208-3_amd64.changes uploaded successfully to localhost
along with the files:
  firmware-nonfree_20210208-3.dsc
  firmware-nonfree_20210208-3.debian.tar.xz
  firmware-amd-graphics_20210208-3_all.deb
  firmware-atheros_20210208-3_all.deb
  firmware-bnx2_20210208-3_all.deb
  firmware-bnx2x_20210208-3_all.deb
  firmware-brcm80211_20210208-3_all.deb
  firmware-cavium_20210208-3_all.deb
  firmware-intel-sound_20210208-3_all.deb
  firmware-intelwimax_20210208-3_all.deb
  firmware-ipw2x00_20210208-3_all.deb
  firmware-ivtv_20210208-3_all.deb
  firmware-iwlwifi_20210208-3_all.deb
  firmware-libertas_20210208-3_all.deb
  firmware-linux-nonfree_20210208-3_all.deb
  firmware-linux_20210208-3_all.deb
  firmware-misc-nonfree_20210208-3_all.deb
  firmware-myricom_20210208-3_all.deb
  firmware-netronome_20210208-3_all.deb
  firmware-netxen_20210208-3_all.deb
  firmware-nonfree_20210208-3_amd64.buildinfo
  firmware-qcom-media_20210208-3_all.deb
  firmware-qcom-soc_20210208-3_all.deb
  firmware-qlogic_20210208-3_all.deb
  firmware-realtek_20210208-3_all.deb
  firmware-samsung_20210208-3_all.deb
  firmware-siano_20210208-3_all.deb
  firmware-ti-connectivity_20210208-3_all.deb

Greetings,

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

Re: firmware-nonfree 20210208-1 upload

[maximilian attems]

Following up today with 20210208-3 due to missing cxgb4 config files
pointed at with the new symlinks. The search led into important missing
firmwares in intel-sound, misc-nonfree and atheros, which are now added.

-- 
maks


signature.asc
Description: PGP signature

Processed: Re: Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[Debian Bug Tracking System]

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

> severity 983561 important
Bug #983561 [firmware-misc-nonfree] firmware-misc-nonfree: broken-symlink 
/lib/firmware/cxgb4/t4-config.txt and others
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[Thorsten Glaser]

maximilian attems dixit:

>are there other dangling symlinks besides this three mentioned ones?

adequate reported only these three for this package; you can find
dangling symlinks, generally, with: (thanks XTaran)

find -L . -type l -ls

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[maximilian attems]

On Fri, Feb 26, 2021 at 12:17:50PM +0100, Cyril Brulebois wrote:
> kibi@tokyo:~/debian-kernel/firmware-nonfree.git$ 
> ./debian/bin/check_upstream.py | sort | grep 'in any binary package'
> I: amd/amd_sev_fam17h_model0xh.sbin is not included in any binary package
> I: amd/amd_sev_fam17h_model3xh.sbin is not included in any binary package

need to recheck if those are not meant to be in the microcode amd64 guy.

> I: cadence/mhdp8546.bin is not included in any binary package

hmm

> →   I: cxgb4/configs/t4-config-default.txt is not included in any binary 
> package
> →   I: cxgb4/configs/t5-config-default.txt is not included in any binary 
> package
> I: cxgb4/configs/t5-config-hashfilter.txt is not included in any binary 
> package
> →   I: cxgb4/configs/t6-config-default.txt is not included in any binary 
> package
> I: cxgb4/configs/t6-config-hashfilter.txt is not included in any binary 
> package

fixed.

> I: inside-secure/eip197_minifw/ifpp.bin is not included in any binary 
> package
> I: inside-secure/eip197_minifw/ipue.bin is not included in any binary 
> package

no idea.

> I: intel/dsp_fw_cnl_v1191.bin is not included in any binary package
> I: intel/fw_sst_0f28_ssp0.bin is not included in any binary package
> I: intel/irci_irci_ecr-master_20161208_0213_20170112_1500.bin is not 
> included in any binary package
> I: iwlwifi-9000-pu-b0-jf-b0-43.ucode is not included in any binary package
> I: iwlwifi-9260-th-b0-jf-b0-43.ucode is not included in any binary package

will fix soonish.

> I: mediatek/mt7622_n9.bin is not included in any binary package
> I: mediatek/mt7622_rom_patch.bin is not included in any binary package
> I: mediatek/mt8183/scp.img is not included in any binary package

hmm.

> I: mellanox/mlxsw_spectrum2-29.2000.2308.mfa2 is not included in any 
> binary package

mellanox is kind of excluded irc.

> I: meson/vdec/g12a_h264.bin is not included in any binary package
> I: meson/vdec/g12a_hevc_mmu.bin is not included in any binary package
> I: meson/vdec/g12a_vp9.bin is not included in any binary package
> I: meson/vdec/gxbb_h264.bin is not included in any binary package
> I: meson/vdec/gxl_h263.bin is not included in any binary package
> I: meson/vdec/gxl_h264.bin is not included in any binary package
> I: meson/vdec/gxl_hevc.bin is not included in any binary package
> I: meson/vdec/gxl_hevc_mmu.bin is not included in any binary package
> I: meson/vdec/gxl_mjpeg.bin is not included in any binary package
> I: meson/vdec/gxl_mpeg12.bin is not included in any binary package
> I: meson/vdec/gxl_mpeg4_5.bin is not included in any binary package
> I: meson/vdec/gxl_vp9.bin is not included in any binary package
> I: meson/vdec/gxm_h264.bin is not included in any binary package
> I: meson/vdec/sm1_hevc_mmu.bin is not included in any binary package
> I: meson/vdec/sm1_vp9_mmu.bin is not included in any binary package
> I: microchip/mscc_vsc8574_revb_int8051_29e8.bin is not included in any 
> binary package
> I: microchip/mscc_vsc8584_revb_int8051_fb48.bin is not included in any 
> binary package

another hmm

> I: qca/nvm_00230302.bin is not included in any binary package
> I: qca/nvm_00440302_eu.bin is not included in any binary package
> I: qca/nvm_00440302_i2s_eu.bin is not included in any binary package
> I: qca/nvm_usb_0302_eu.bin is not included in any binary package

those I'll fix too.

> I: qed/qed_init_values_zipped-8.37.7.0.bin is not included in any binary 
> package
> I: r8a779x_usb3_v1.dlmem is not included in any binary package
> I: r8a779x_usb3_v2.dlmem is not included in any binary package
> I: r8a779x_usb3_v3.dlmem is not included in any binary package
> I: rtw88/README is not included in any binary package
> I: ti-keystone/ks2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin is not included in 
> any binary package

oh well none of those appear to generate much attention.


thank you!

-- 
maks


signature.asc
Description: PGP signature

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[maximilian attems]

On Fri, Feb 26, 2021 at 12:08:55PM +0100, Cyril Brulebois wrote:
> > 
> > Link: cxgb4/t4-config.txt -> configs/t4-config-default.txt
> > Link: cxgb4/t5-config.txt -> configs/t5-config-default.txt
> > Link: cxgb4/t6-config.txt -> configs/t6-config-default.txt
> 
> debian/config/misc-nonfree/defines looks like it might be missing the
> targets of the symlinks (cxgb4/configs/t?-config-default.txt), meaning
> the File entries get installed in the build directory through the WHENCE
> processing, but those files aren't listed in the FILES variable when
> building the binary package, so they don't end up being actually shipped,
> hence the broken symlinks?

thank you a lot for the prompt look and indeed those config files
were not added, updated the repo to fix that in next upload.

are there other dangling symlinks besides this three mentioned ones?

best,

-- 
maks


signature.asc
Description: PGP signature

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[Cyril Brulebois]

Cyril Brulebois  (2021-02-26):
> debian/config/misc-nonfree/defines looks like it might be missing the
> targets of the symlinks (cxgb4/configs/t?-config-default.txt), meaning
> the File entries get installed in the build directory through the WHENCE
> processing, but those files aren't listed in the FILES variable when
> building the binary package, so they don't end up being actually shipped,
> hence the broken symlinks?

This hypothesis seems to be confirmed by running the check_upstream.py
script:

kibi@tokyo:~/debian-kernel/firmware-nonfree.git$ 
./debian/bin/check_upstream.py | sort | grep 'in any binary package'
I: amd/amd_sev_fam17h_model0xh.sbin is not included in any binary package
I: amd/amd_sev_fam17h_model3xh.sbin is not included in any binary package
I: cadence/mhdp8546.bin is not included in any binary package
→   I: cxgb4/configs/t4-config-default.txt is not included in any binary package
→   I: cxgb4/configs/t5-config-default.txt is not included in any binary package
I: cxgb4/configs/t5-config-hashfilter.txt is not included in any binary 
package
→   I: cxgb4/configs/t6-config-default.txt is not included in any binary package
I: cxgb4/configs/t6-config-hashfilter.txt is not included in any binary 
package
I: inside-secure/eip197_minifw/ifpp.bin is not included in any binary 
package
I: inside-secure/eip197_minifw/ipue.bin is not included in any binary 
package
I: intel/dsp_fw_cnl_v1191.bin is not included in any binary package
I: intel/fw_sst_0f28_ssp0.bin is not included in any binary package
I: intel/irci_irci_ecr-master_20161208_0213_20170112_1500.bin is not 
included in any binary package
I: iwlwifi-9000-pu-b0-jf-b0-43.ucode is not included in any binary package
I: iwlwifi-9260-th-b0-jf-b0-43.ucode is not included in any binary package
I: mediatek/mt7622_n9.bin is not included in any binary package
I: mediatek/mt7622_rom_patch.bin is not included in any binary package
I: mediatek/mt8183/scp.img is not included in any binary package
I: mellanox/mlxsw_spectrum2-29.2000.2308.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2000.2714.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2007.1168.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2008.1036.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2008.1310.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2008.1312.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2008.2018.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum2-29.2008.2304.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum3-30.2007.1168.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum3-30.2008.1036.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum3-30.2008.1310.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum3-30.2008.1312.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum3-30.2008.2018.mfa2 is not included in any binary 
package
I: mellanox/mlxsw_spectrum3-30.2008.2304.mfa2 is not included in any binary 
package
I: meson/vdec/g12a_h264.bin is not included in any binary package
I: meson/vdec/g12a_hevc_mmu.bin is not included in any binary package
I: meson/vdec/g12a_vp9.bin is not included in any binary package
I: meson/vdec/gxbb_h264.bin is not included in any binary package
I: meson/vdec/gxl_h263.bin is not included in any binary package
I: meson/vdec/gxl_h264.bin is not included in any binary package
I: meson/vdec/gxl_hevc.bin is not included in any binary package
I: meson/vdec/gxl_hevc_mmu.bin is not included in any binary package
I: meson/vdec/gxl_mjpeg.bin is not included in any binary package
I: meson/vdec/gxl_mpeg12.bin is not included in any binary package
I: meson/vdec/gxl_mpeg4_5.bin is not included in any binary package
I: meson/vdec/gxl_vp9.bin is not included in any binary package
I: meson/vdec/gxm_h264.bin is not included in any binary package
I: meson/vdec/sm1_hevc_mmu.bin is not included in any binary package
I: meson/vdec/sm1_vp9_mmu.bin is not included in any binary package
I: microchip/mscc_vsc8574_revb_int8051_29e8.bin is not included in any 
binary package
I: microchip/mscc_vsc8584_revb_int8051_fb48.bin is not included in any 
binary package
I: qca/nvm_00230302.bin is not included in any binary package
I: qca/nvm_00440302_eu.bin is not included in any binary package
I: qca/nvm_00440302_i2s_eu.bin is not included in any binary package
I: qca/nvm_usb_0302_eu.bin is not included in any binary package
I: qed/qed_init_values_zipped-8.37.7.0.bin is not included in any binary 
package
I: r8a779x_usb3_v1.dlmem is not included in any binary package
I: 

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[Cyril Brulebois]

(Total firmware-* newbie, grain of salt, use with caution, etc.)

maximilian attems  (2021-02-26):
> > Usertags: adequate broken-symlink
> > X-Debbugs-Cc: t...@mirbsd.de
> > 
> > firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt -> 
> > configs/t4-config-default.txt
> > firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t5-config.txt -> 
> > configs/t5-config-default.txt
> > firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t6-config.txt -> 
> > configs/t6-config-default.txt

For the record:

$ dpkg --contents 
binary-firmware-misc-nonfree/firmware-misc-nonfree_20210208-2_all.deb | grep 
cxgb4/
./lib/firmware/cxgb4/
./lib/firmware/cxgb4/aq1202_fw.cld
./lib/firmware/cxgb4/bcm8483.bin
./lib/firmware/cxgb4/t4fw-1.24.17.0.bin
./lib/firmware/cxgb4/t5fw-1.24.17.0.bin
./lib/firmware/cxgb4/t6fw-1.24.17.0.bin
./lib/firmware/cxgb4/t4-config.txt -> configs/t4-config-default.txt
./lib/firmware/cxgb4/t4fw.bin -> t4fw-1.24.17.0.bin
./lib/firmware/cxgb4/t5-config.txt -> configs/t5-config-default.txt
./lib/firmware/cxgb4/t5fw.bin -> t5fw-1.24.17.0.bin
./lib/firmware/cxgb4/t6-config.txt -> configs/t6-config-default.txt
./lib/firmware/cxgb4/t6fw.bin -> t6fw-1.24.17.0.bin

> why is this a broken symlink? this is what upstream wants in WHENCE:
> 
> Link: cxgb4/t4-config.txt -> configs/t4-config-default.txt
> Link: cxgb4/t5-config.txt -> configs/t5-config-default.txt
> Link: cxgb4/t6-config.txt -> configs/t6-config-default.txt

debian/config/misc-nonfree/defines looks like it might be missing the
targets of the symlinks (cxgb4/configs/t?-config-default.txt), meaning
the File entries get installed in the build directory through the WHENCE
processing, but those files aren't listed in the FILES variable when
building the binary package, so they don't end up being actually shipped,
hence the broken symlinks?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[maximilian attems]

> Usertags: adequate broken-symlink
> X-Debbugs-Cc: t...@mirbsd.de
> 
> firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt -> 
> configs/t4-config-default.txt
> firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t5-config.txt -> 
> configs/t5-config-default.txt
> firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t6-config.txt -> 
> configs/t6-config-default.txt

why is this a broken symlink? this is what upstream wants in WHENCE:

Link: cxgb4/t4-config.txt -> configs/t4-config-default.txt
Link: cxgb4/t5-config.txt -> configs/t5-config-default.txt
Link: cxgb4/t6-config.txt -> configs/t6-config-default.txt

-- 
maks

Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others

[Thorsten Glaser]

Package: firmware-misc-nonfree
Version: 20210208-2
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate broken-symlink
X-Debbugs-Cc: t...@mirbsd.de

firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt -> 
configs/t4-config-default.txt
firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t5-config.txt -> 
configs/t5-config-default.txt
firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t6-config.txt -> 
configs/t6-config-default.txt





-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 
'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.139

-- no debconf information