On 10.03.23 11:20, Karol Herbst wrote:
> On Fri, Mar 10, 2023 at 10:26 AM Chris Clayton
> wrote:
>>
>> Is it likely that this fix will be sumbmitted to mainline during the ongoing
>> 6.3 development cycle?
>>
>
> yes, it's already pushed to drm-misc-fixed, which then will go into
> the current
On Fri, Mar 10, 2023 at 10:26 AM Chris Clayton wrote:
>
> Hi.
>
> Is it likely that this fix will be sumbmitted to mainline during the ongoing
> 6.3 development cycle?
>
yes, it's already pushed to drm-misc-fixed, which then will go into
the current devel cycle. I just don't know when it's the
Hi.
Is it likely that this fix will be sumbmitted to mainline during the ongoing
6.3 development cycle?
Chris
On 20/02/2023 22:16, Ben Skeggs wrote:
> On Mon, 20 Feb 2023 at 21:27, Karol Herbst wrote:
>>
>> On Mon, Feb 20, 2023 at 11:51 AM Chris Clayton
>> wrote:
>>>
>>>
>>>
>>> On
On Mon, 20 Feb 2023 at 21:27, Karol Herbst wrote:
>
> On Mon, Feb 20, 2023 at 11:51 AM Chris Clayton
> wrote:
> >
> >
> >
> > On 20/02/2023 05:35, Ben Skeggs wrote:
> > > On Sun, 19 Feb 2023 at 04:55, Chris Clayton
> > > wrote:
> > >>
> > >>
> > >>
> > >> On 18/02/2023 15:19, Chris Clayton
On Mon, Feb 20, 2023 at 11:51 AM Chris Clayton wrote:
>
>
>
> On 20/02/2023 05:35, Ben Skeggs wrote:
> > On Sun, 19 Feb 2023 at 04:55, Chris Clayton
> > wrote:
> >>
> >>
> >>
> >> On 18/02/2023 15:19, Chris Clayton wrote:
> >>>
> >>>
> >>> On 18/02/2023 12:25, Karol Herbst wrote:
> On Sat,
On 20/02/2023 05:35, Ben Skeggs wrote:
> On Sun, 19 Feb 2023 at 04:55, Chris Clayton wrote:
>>
>>
>>
>> On 18/02/2023 15:19, Chris Clayton wrote:
>>>
>>>
>>> On 18/02/2023 12:25, Karol Herbst wrote:
On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton
wrote:
>
>
>
> On
On Sun, 19 Feb 2023 at 04:55, Chris Clayton wrote:
>
>
>
> On 18/02/2023 15:19, Chris Clayton wrote:
> >
> >
> > On 18/02/2023 12:25, Karol Herbst wrote:
> >> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton
> >> wrote:
> >>>
> >>>
> >>>
> >>> On 15/02/2023 11:09, Karol Herbst wrote:
> On
On 18/02/2023 15:19, Chris Clayton wrote:
>
>
> On 18/02/2023 12:25, Karol Herbst wrote:
>> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton
>> wrote:
>>>
>>>
>>>
>>> On 15/02/2023 11:09, Karol Herbst wrote:
On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
(Thorsten
On 18/02/2023 12:25, Karol Herbst wrote:
> On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton
> wrote:
>>
>>
>>
>> On 15/02/2023 11:09, Karol Herbst wrote:
>>> On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
>>> (Thorsten Leemhuis) wrote:
On 13.02.23 10:14, Chris
On Sat, Feb 18, 2023 at 1:22 PM Chris Clayton wrote:
>
>
>
> On 15/02/2023 11:09, Karol Herbst wrote:
> > On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
> > (Thorsten Leemhuis) wrote:
> >>
> >> On 13.02.23 10:14, Chris Clayton wrote:
> >>> On 13/02/2023 02:57, Dave Airlie
On 15/02/2023 11:09, Karol Herbst wrote:
> On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
> (Thorsten Leemhuis) wrote:
>>
>> On 13.02.23 10:14, Chris Clayton wrote:
>>> On 13/02/2023 02:57, Dave Airlie wrote:
On Sun, 12 Feb 2023 at 00:43, Chris Clayton
wrote:
On Wed, Feb 15, 2023 at 11:36 AM Linux regression tracking #update
(Thorsten Leemhuis) wrote:
>
> On 13.02.23 10:14, Chris Clayton wrote:
> > On 13/02/2023 02:57, Dave Airlie wrote:
> >> On Sun, 12 Feb 2023 at 00:43, Chris Clayton
> >> wrote:
> >>>
> >>>
> >>>
> >>> On 10/02/2023 19:33, Linux
On 13.02.23 10:14, Chris Clayton wrote:
> On 13/02/2023 02:57, Dave Airlie wrote:
>> On Sun, 12 Feb 2023 at 00:43, Chris Clayton wrote:
>>>
>>>
>>>
>>> On 10/02/2023 19:33, Linux regression tracking (Thorsten Leemhuis) wrote:
On 10.02.23 20:01, Karol Herbst wrote:
> On Fri, Feb 10, 2023
Proof, if any where needed, that I should consume more coffee before dealing
with email...
Adding cc recipients that were dropped in my message this morning.
Forwarded Message
Subject: Re: linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
Date: Mon, 13 Feb 2023 09:21:10 +
On 13/02/2023 02:57, Dave Airlie wrote:
> On Sun, 12 Feb 2023 at 00:43, Chris Clayton wrote:
>>
>>
>>
>> On 10/02/2023 19:33, Linux regression tracking (Thorsten Leemhuis) wrote:
>>> On 10.02.23 20:01, Karol Herbst wrote:
On Fri, Feb 10, 2023 at 7:35 PM Linux regression tracking (Thorsten
On Sun, 12 Feb 2023 at 00:43, Chris Clayton wrote:
>
>
>
> On 10/02/2023 19:33, Linux regression tracking (Thorsten Leemhuis) wrote:
> > On 10.02.23 20:01, Karol Herbst wrote:
> >> On Fri, Feb 10, 2023 at 7:35 PM Linux regression tracking (Thorsten
> >> Leemhuis) wrote:
> >>>
> >>> On 08.02.23
On 10.02.23 20:01, Karol Herbst wrote:
> On Fri, Feb 10, 2023 at 7:35 PM Linux regression tracking (Thorsten
> Leemhuis) wrote:
>>
>> On 08.02.23 09:48, Chris Clayton wrote:
>>>
>>> I'm assuming that we are not going to see a fix for this regression before
>>> 6.2 is released.
>>
>> Yeah, looks
On Fri, Feb 10, 2023 at 7:35 PM Linux regression tracking (Thorsten
Leemhuis) wrote:
>
> On 08.02.23 09:48, Chris Clayton wrote:
> >
> > I'm assuming that we are not going to see a fix for this regression before
> > 6.2 is released.
>
> Yeah, looks like it. That's unfortunate, but happens. But
On 08.02.23 09:48, Chris Clayton wrote:
>
> I'm assuming that we are not going to see a fix for this regression before
> 6.2 is released.
Yeah, looks like it. That's unfortunate, but happens. But there is still
time to fix it and there is one thing I wonder:
Did any of the nouveau developers
Hi.
I'm assuming that we are not going to see a fix for this regression before 6.2
is released. Consequently, I've
implemented a (very simple) workaround. All that happens is that in the (sysv)
init script that starts and stops SDDM,
the nouveau module is removed once SDDM is stopped. With
On 30/01/2023 23:27, Ben Skeggs wrote:
> On Tue, 31 Jan 2023 at 09:09, Chris Clayton wrote:
>>
>> Hi again.
>>
>> On 30/01/2023 20:19, Chris Clayton wrote:
>>> Thanks, Ben.
>>
>>
>>
Hey,
This is a complete shot-in-the-dark, as I don't see this behaviour on
*any* of my
On Tue, 31 Jan 2023 at 09:09, Chris Clayton wrote:
>
> Hi again.
>
> On 30/01/2023 20:19, Chris Clayton wrote:
> > Thanks, Ben.
>
>
>
> >> Hey,
> >>
> >> This is a complete shot-in-the-dark, as I don't see this behaviour on
> >> *any* of my boards. Could you try the attached patch please?
> >
>
Hi again.
On 30/01/2023 20:19, Chris Clayton wrote:
> Thanks, Ben.
>> Hey,
>>
>> This is a complete shot-in-the-dark, as I don't see this behaviour on
>> *any* of my boards. Could you try the attached patch please?
>
> Unfortunately, the patch made no difference.
>
> I've been looking at
Thanks, Ben.
On 30/01/2023 01:09, Ben Skeggs wrote:
> On Sat, 28 Jan 2023 at 21:29, Chris Clayton wrote:
>>
>>
>>
>> On 28/01/2023 05:42, Linux kernel regression tracking (Thorsten Leemhuis)
>> wrote:
>>> On 27.01.23 20:46, Chris Clayton wrote:
[Resend because the mail client on my phone
On Sat, 28 Jan 2023 at 21:29, Chris Clayton wrote:
>
>
>
> On 28/01/2023 05:42, Linux kernel regression tracking (Thorsten Leemhuis)
> wrote:
> > On 27.01.23 20:46, Chris Clayton wrote:
> >> [Resend because the mail client on my phone decided to turn HTML on behind
> >> my back, so my reply got
On 28/01/2023 05:42, Linux kernel regression tracking (Thorsten Leemhuis) wrote:
> On 27.01.23 20:46, Chris Clayton wrote:
>> [Resend because the mail client on my phone decided to turn HTML on behind
>> my back, so my reply got bounced.]
>>
>> Thanks Thorsten.
>>
>> I did try to revert but it
On 27.01.23 20:46, Chris Clayton wrote:
> [Resend because the mail client on my phone decided to turn HTML on behind my
> back, so my reply got bounced.]
>
> Thanks Thorsten.
>
> I did try to revert but it didnt revert cleanly and I don't have the
> knowledge to fix it up.
>
> The patch was
[Resend because the mail client on my phone decided to turn HTML on behind my
back, so my reply got bounced.]
Thanks Thorsten.
I did try to revert but it didnt revert cleanly and I don't have the knowledge
to fix it up.
The patch was part of a merge that included a number of related patches.
[Resend because the mail client on my phone dedcided to turn HTML on behinf my
back, so my repluy got bounced.]
Thanks Karol.
I sent the original report to Ben and LKML. Thorsten then added you, Lyude Paul
and the dri-devel and nouveau mail
lists. So you should have received this report on or
Thanks Thorsten.
I did try to revert but it didnt revert cleanly and I don't have the
knowledge to fix it up.
The patch was part of a merge that included a number of related patches.
I'll try to revert the lot and report back.
Chris
On Fri, 27 Jan 2023, 11:20 Linux kernel regression tracking
Hi Karol.
I sent the originsl report to Ben and LKML. Thorsten then added you, Lyude
Paul and the dri-devel and nouveau lists. So you should have received this
report on or about January 19.
Chris
On Fri, 27 Jan 2023, 11:35 Karol Herbst, wrote:
> Where was the original email sent to anyway,
Where was the original email sent to anyway, because I don't have it at all.
Anyhow, I suspect we want to fetch logs to see what's happening, but
due to the nature of this bug it might get difficult.
I'm checking out the laptops I have here if I can reproduce this
issue, but I think all mine
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
@nouveau-maintainers, did anyone take a look at this? The report is
already 8 days old and I don't see a single reply. Sure, we'll likely
get a -rc8, but still it would be good to
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 19.01.23 15:33, Linux kernel regression tracking (Thorsten Leemhuis)
wrote:
> On 18.01.23 21:59, Chris Clayton wrote:
>>
>> # first bad commit:
[adding various lists and the two other nouveau maintainers to the list
of recipients]
For the rest of this mail:
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in
35 matches
Mail list logo
