Hi
On Mon, May 20, 2024 at 01:06:52PM +0200, Diederik de Haas wrote:
> >From "Salsa stats for the curious" on debian-project ML:
> On Friday, 12 April 2024 17:32:04 CEST Joerg Jaspert wrote:
> > The VM this all runs on has 8 cores and 32g
>
> I had several thoughts about that:
> - But why doesn't
Dear Neil,
I've applied your patch, and since then there are no lockups. Before
that my application reported a lockup in a minute or two, now it has
been running for half an hour, and still running.
Thanks,
Richard
2024-05-24 01:31 időpontban NeilBrown ezt írta:
On Fri, 24 May 2024, Richard
Dear Neil,
I've stripped the code more, which still triggers the bug for me. On
Bookworm, to get the binary, simply:
$ sudo apt-get install golang
$ go build .
And then give it an nfs mountpoint, e.g.:
$ ./ds /mnt/nfs
Meanwhile, I will try your patch too.
Regards,
Richard
2024-05-24 01:31
On Fri, 24 May 2024, Richard Kojedzinszky wrote:
> Dear devs,
>
> I am attaching a stripped down version of the little program which
> triggers the bug very quickly, in a few minutes in my test lab. It
> turned out that a single NFS mountpoint is enough. Just start the
> program giving it the N
#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #1071263 (http://bugs.debian.org/10712
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setti
Same here, Intel AX201. Bug appears both on 6.1.0-20 and 6.1.0-21
Rémy
On Tue, 7 May 2024 01:07:49 +0200 Udo Richter wrote:
> Hi,
>
> Seeing exactly the same bug with an Broadcom Corp. BCM2045B (BDC-2.1)
> bluetooth device, so its not just the Intel AX211.
>
> Jeremy, thanks for tracking this do
On Thursday, 23 May 2024 17:33:47 CEST Vincent Blut wrote:
> We are just lacking a configuration symbol. Diederik, starting with
> linux 6.8 AMD PMF requires TEE. Do you want me to send a MR?
Sure.
Bit surprised it wouldn't be automatically selected though.
signature.asc
Description: This is a di
Hi Nathan,
Le 2024-05-23 17:12, Nathan MALO a écrit :
> Hello !
>
> Thank you very much for enabling those two features in the kernel.
> Your work is much appreciated !
>
> Maybe I am missing something but I've download the 6.8.9-1 package from
> here
> http://ftp.us.debian.org/debian/pool/main/
Hello !
Thank you very much for enabling those two features in the kernel.
Your work is much appreciated !
Maybe I am missing something but I've download the 6.8.9-1 package from
here
http://ftp.us.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.8.9-amd64_6.8.9-1_amd64.deb
and whil
Dear devs,
I am attaching a stripped down version of the little program which
triggers the bug very quickly, in a few minutes in my test lab. It
turned out that a single NFS mountpoint is enough. Just start the
program giving it the NFS mount as first argument. It will chdir there,
and do fil
Dear devs,
Now bisecting turned out that 3c59366c207e4c6c6569524af606baf017a55c61
is the bad commit for me. Strangely it only affects my dovecot process
accessing data over NFS.
Can you please confirm that this may be a bad commit?
My earlier attached programs may be used to demonstrate/trig
I apologize, I misinterpreted "report back here" but I did not look at the
distribution list or grab "reply all".
I prepared to follow the suggestions, although I was not going to risk that
particular microSD unless it was clearly needed. As I prepared to dd to new
a new SD, I realized that asking
On Thursday, 23 May 2024 09:59:52 CEST Eduardo Casais wrote:
> 4) Determining whether the bug was introduced by the passage from kernel
> 5.10.0 to 6.1.0, or whether it was an error introduced between releases
> of image 6.1.0-*.
>
> Attempted resolution:
>
> I looked at the image versions availa
Dear Maintainers,
Here is some more information about bug report 1071258 affecting my
Lenovo L570.
1) The bug was first reported as 1071236. It was closed by the
maintainer, who suggested it was possibly due to a hardware failure.
Attempted resolution:
Booting the machine (with the Debian
Dear NFS developers,
I am running multiple PODs on a Kubernetes node, they all mount
different NFS shares from the same nfs server. I started to notice
hangups in my dovecot process after I switched to Debian's kernel from
upstream 5.15. You can find Debian bugreport at
https://bugs.debian.or
16 matches
Mail list logo
