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
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.
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
> >
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
(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
> >
> 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
>
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:
21 matches
Mail list logo
