Control: tag -1 moreinfo
Hi Julian,
On Thursday, 12 January 2023 19:31:37 CET Julian Groß wrote:
> My computer just froze on Kernel version 5.19.11-1. Though nothing got
> logged.
What's the current status on this bug?
Currently there is a version 6.1.15 in Testing/Unstable and it would be
On Thu, 12 Jan 2023 18:31:37 + =?UTF-8?Q?Julian_Gro=c3=9f?=
wrote:
My computer just froze on Kernel version 5.19.11-1. Though nothing got
logged.
Now I don't know if this is the same issue and newer kernels just behave
better in terms of logging, or if this is a different issue..
I
My computer just froze on Kernel version 5.19.11-1. Though nothing got
logged.
Now I don't know if this is the same issue and newer kernels just behave
better in terms of logging, or if this is a different issue..
I guess I will add a second screen to my computer, open journalctl on
there,
On Thu, 12 Jan 2023 15:41:03 +0100 Diederik de Haas
wrote:
> "Currently, I am using git bisect to narrow down the window of possible
> commits, but since the issue appears seemingly random, it will take many
> months to identify the offending commit this way."
>
> Why? It *could* be that the
Hi Julian,
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
> http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
The following paragraph may not be ideally formulated:
"Currently, I am using
Control: forwarded -1
http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
>
On Wed, 11 Jan 2023 21:49:45 +0100 Diederik de Haas
wrote:
> So the next thing to do, is present the issue to the relevant upstream
> maintainers. Searching for "nvme controller is down" brought up another bug
> (but that happened pretty instantly) and in there the request was made to
> report
On Wednesday, 11 January 2023 19:28:25 CET Julian Groß wrote:
> On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas
> wrote:
> > https://wiki.debian.org/DebianKernel/GitBisect describes a procedure
> > to find the exact commit which introduced the issue you reported, but it's
> > often faster
On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas
wrote:
> https://wiki.debian.org/DebianKernel/GitBisect describes a procedure
to find
> the exact commit which introduced the issue you reported, but it's often
> faster to first narrow down the range using snapshot.d.o.
The way I understand
Control: found -1 6.0~rc7-1~exp1
On Wednesday, 11 January 2023 15:04:30 CET Julian wrote:
> 6.0~rc7-1~exp1 is also broken.
>
> I will go through https://wiki.debian.org/DebianKernel/GitBisect and see
> what I can find. Thankfully the documentation is quite comprehensive.
That would be great,
6.0~rc7-1~exp1 is also broken.
I will go through https://wiki.debian.org/DebianKernel/GitBisect and see what I
can find.
Thankfully the documentation is quite comprehensive.
Thanks for your help.
> Unstable currently has version 6.1.4-1, could you try that to see
whether the
> issue is already resolved?
Version 6.1.4-1 shows the same issue.
> If not, then we need to figure out when the issue first occurred.
> Via
Control: found -1 6.0.10-1
On Monday, 9 January 2023 13:20:08 CET Julian Groß wrote:
> when running Linux Kernel version 6.0.12 or 6.0.10, my system seemingly
> randomly freezes due to the filesystem being set to read-only due to an
> issue with my nvme controller.
> The issue does *not* appear
13 matches
Mail list logo
