Package: src:linux
Version: 5.14.16-1
Severity: normal
Hi,
While writing a script with busybox parsing /proc/bus/input/devices,
I discovered that poll syscall seems to not give correct information
on this file. Before reporting, I checked with a small C program
(in attachment).
The main part of
Package: src:linux
Version: 5.10.84-1
Severity: important
Dear Maintainer,
We have using kernel linux-image-5.10.0-10-amd64 and nftables(0.9.8-3.1)
for a stateless NAT GW. We are using the nftables "raw" tables to
replace statically source and destination addresses for pakets
traversing the host
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Dec 2021 00:18:19 +0100
Source: linux
Architecture: source
Version: 5.16~rc7-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 947179 10
Your message dated Mon, 27 Dec 2021 18:00:38 +
with message-id
and subject line Bug#947179: fixed in linux 5.16~rc7-1~exp1
has caused the Debian Bug report #947179,
regarding linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware
drivers
to be marked as done.
This means that yo
Your message dated Mon, 27 Dec 2021 18:00:38 +
with message-id
and subject line Bug#1002460: fixed in linux 5.16~rc7-1~exp1
has caused the Debian Bug report #1002460,
regarding linux-image-amd64: Missing kernel configuration for Microsoft Laptops
and Surface devices
to be marked as done.
Thi
Processing commands for cont...@bugs.debian.org:
> unarchive 988027
Bug #988027 {Done: Thorsten Glaser } [libklibc-dev] klibc:
sigsetjmp ignores second argument, siglongjmp always restores signals
Unarchived Bug 988027
> fixed 988027 2.0.9-1
Bug #988027 {Done: Thorsten Glaser } [libklibc-dev] kli
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 27 Dec 2021 13:21:16 +0100
Source: linux-base
Architecture: source
Version: 4.7
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 931506 977939
Change
linux-base_4.7_sourceonly.changes uploaded successfully to localhost
along with the files:
linux-base_4.7.dsc
linux-base_4.7.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Mon, 27 Dec 2021 12:33:58 +
with message-id
and subject line Bug#977939: fixed in linux-base 4.7
has caused the Debian Bug report #977939,
regarding linux-base: [INTL:de] updated German man page translation
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 27 Dec 2021 12:33:58 +
with message-id
and subject line Bug#931506: fixed in linux-base 4.7
has caused the Debian Bug report #931506,
regarding linux-base: "are are" in man 1 perf
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 27 Dec 2021 12:46:40 +0100 (CET)
with message-id
and subject line Re: Bug#1002573: (no subject)
has caused the Debian Bug report #1002573,
regarding general: fstrim, 2 errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
No, I am out of here
If the bug is not reproducible for you by now, it is not worth
to persue it
You might want to close this issue
Thanks anyway for your assistance
On Mon, Dec 27, 2021 at 09:10:42AM +0100, detlev schmidtke wrote:
> and I do not agree that this is a sole kernel problem
>
> fstrim --verbose
>
> should report something, anything
We do not have enought information on the systems to determine if this
is the correct behaviour (it can, if no file
Hi Detlev,
On Mon, 27 Dec 2021, detlev schmidtke wrote:
and I do not agree that this is a sole kernel problem
fstrim --verbose
should report something, anything
* there still isn't a text only output (as opposed to an image) of what
you are seeing in the bugreport. So people that get emai
and I do not agree that this is a sole kernel problem
fstrim --verbose
should report something, anything
I checked the SSDs with:
hdparm -I /dev/sda | grep -i TRIM
* Data Set Management TRIM supported (limit 8 blocks)
* Deterministic read ZEROs after TRIM
<<< full reproduction scenario >>>
The two computers, where it does not work, are
- an Intel NUC nuc7pjyhn, first produced in 2021Q2
- an Intel NUC nuc6cayh, first produced in 2016Q4
Both operating systems were procuced with the current Debian Installer,
which is based on Debian 11.2 Bullseye
A
17 matches
Mail list logo
