[<prev] [next>] [day] [month] [year] [list]
Message-ID: <e0b80506-b3cf-315b-4327-1b988d86031e@googlemail.com>
Date: Mon, 13 Feb 2023 14:12:51 +0000
From: Chris Clayton <chris2553@...glemail.com>
To: ">> ML dri-devel" <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
Karol Herbst <kherbst@...hat.com>,
Ben Skeggs <skeggsb@...il.com>, bskeggs@...hat.com,
Lyude Paul <lyude@...hat.com>,
ML nouveau <nouveau@...ts.freedesktop.org>
Cc: Dave Airlie <airlied@...il.com>
Subject: Fwd: linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
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 +0000
From: Chris Clayton <chris2553@...glemail.com>
To: Dave Airlie <airlied@...il.com>
[ Apologies for the incomplete message I sent a few minutes ago. I should have had more coffee before I started dealing
with email. ]
On 13/02/2023 02:57, Dave Airlie wrote:
> On Sun, 12 Feb 2023 at 00:43, Chris Clayton <chris2553@...glemail.com> 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) <regressions@...mhuis.info> 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 there is still
>>>>> time to fix it and there is one thing I wonder:
>>>>>
>>>>> Did any of the nouveau developers look at the netconsole captures Chris
>>>>> posted more than a week ago to check if they somehow help to track down
>>>>> the root of this problem?
>>>>
>>>> I did now and I can't spot anything. I think at this point it would
>>>> make sense to dump the active tasks/threads via sqsrq keys to see if
>>>> any is in a weird state preventing the machine from shutting down.
>>>
>>> Many thx for looking into it!
>>
>> Yes, thanks Karol.
>>
>> Attached is the output from dmesg when this block of code:
>>
>> /bin/mount /dev/sda7 /mnt/sda7
>> /bin/mountpoint /proc || /bin/mount /proc
>> /bin/dmesg -w > /mnt/sda7/sysrq.dmesg.log &
>> /bin/echo t > /proc/sysrq-trigger
>> /bin/sleep 1
>> /bin/sync
>> /bin/sleep 1
>> kill $(pidof dmesg)
>> /bin/umount /mnt/sda7
>>
>> is executed immediately before /sbin/reboot is called as the final step of rebooting my system.
>>
>> I hope this is what you were looking for, but if not, please let me know what you need
>
Thanks, Dave.
> Another shot in the dark, but does nouveau.runpm=0 help at all?
>
Yes, it does. With runpm=0, both reboot and poweroff work on my laptop. Of course, it also means that the discrete
(NVidia) GPU is now powered on permanently.
Chris
> Dave.
Powered by blists - more mailing lists