It's like déjà vu all over again:
#942881 - snd-hda-codec-hdmi signature corruption
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Thank you!
Dan
Urbana, Illinois
Hi ,
This issue can be replicated by executing the above mentioned code on
debian9 and debian10 OS. The compiler arguments I used is g++ debian.cc
(debian.cc is the file name). After compiling we need to check the output
file(i.e Result). In the output file focus on the 'used' field of "free -m"
Hi,
On Mon, 2022-07-04 at 22:00 +0200, Ansgar wrote:
> The correct signature (using OpenSSL) has:
>
> +---
> > 138 256: OCTET STRING
> > : 00 00 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C B6
> +---[ data.ko.p7s.success ]
>
> The incorrect signature from the YK has:
>
>
Hi,
I experimented a bit more and could reproduce the problem with a local
YK (Yubikey 4, Firmware 4.3.7) and a known private key and certificate.
The correct signature (using OpenSSL) has:
+---
| 138 256: OCTET STRING
|: 00 00 45 75 A8 93 B1 B1 37 0A 53 69 82 BB
On Mon, Jul 04, 2022 at 08:45:05PM +0200, g.l. gragnani wrote:
> I don't know if this is a bug in initramfs-tools or in lvm2 or something else.
That's #1014314 in lvm2.
Greetings
Marc
--
-
Marc Haber | "I don't
Package: initramfs-tools
Version: 0.141
Severity: important
Dear Maintainer,
after the last upgrade I received the following message:
Setting up lvm2 (2.03.15-1) ...
Installing new version of config file /etc/lvm/lvm.conf ...
Installing new version of config file /etc/lvm/lvmlocal.conf ...
On Mon, 2022-07-04 at 14:04 +0200, Ansgar wrote:
> On Sun, 19 Jun 2022 12:59:55 +0200 Ben Hutchings wrote:
> > > I'm now looking at whether the missing bytes are recoverable (e.g. are
> > > they always zeroes).
> > [...]
> >
> > I wrote a script to try all possible byte values for 2 bytes before
On Sun, 19 Jun 2022 12:59:55 +0200 Ben Hutchings wrote:
> > I'm now looking at whether the missing bytes are recoverable (e.g. are
> > they always zeroes).
> [...]
>
> I wrote a script to try all possible byte values for 2 bytes before or
> after the short signature. For this particular file,
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 21.06.22 11:35, Thorsten Leemhuis wrote:
> [TLDR: I'm adding this regression
Processing control commands:
> tags -1 + patch
Bug #1014319 [initramfs-tools] depmod: WARNING: could not open
modules.builtin.modinfo at
/var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
directory
Added tag(s) patch.
--
1014319:
Control: tags -1 + patch
On 2022-07-04 10:00 +0200, Vincent Lefevre wrote:
> On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote:
>> When update-initramfs runs I receive the following message:
>>
>> depmod: WARNING: could not open modules.builtin.modinfo at
>>
On 2022-07-04 10:00:04 +0200, Vincent Lefevre wrote:
> On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote:
> > When update-initramfs runs I receive the following message:
> >
> > depmod: WARNING: could not open modules.builtin.modinfo at
> > /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64:
On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote:
> When update-initramfs runs I receive the following message:
>
> depmod: WARNING: could not open modules.builtin.modinfo at
> /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
> directory
I also got such a warning on two
13 matches
Mail list logo
