From: Ben Skeggs <skeggsb@gmail.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
bskeggs@redhat.com, Karol Herbst <kherbst@redhat.com>,
Lyude Paul <lyude@redhat.com>,
ML nouveau <nouveau@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: linux-6.2-rc4+ hangs on poweroff/reboot: Bisected
Date: Tue, 31 Jan 2023 09:27:54 +1000 [thread overview]
Message-ID: <CACAvsv5iYdF3P8AbyrbYo3zGmYRYhxDWn7WbAR5V9qHpbgBXRA@mail.gmail.com> (raw)
In-Reply-To: <dab6eb81-db3f-8fa1-84ad-9b40e209514b@googlemail.com>
On Tue, 31 Jan 2023 at 09:09, Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi again.
>
> On 30/01/2023 20:19, Chris Clayton wrote:
> > Thanks, Ben.
>
> <snip>
>
> >> 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 how the graphics on my laptop is set up, and have a bit of a worry about whether the firmware might
> > be playing a part in this problem. In order to offload video decoding to the NVidia TU117 GPU, it seems the scrubber
> > firmware must be available, but as far as I know,that has not been released by NVidia. To get it to work, I followed
> > what ubuntu have done and the scrubber in /lib/firmware/nvidia/tu117/nvdec/ is a symlink to
> > ../../tu116/nvdev/scrubber.bin. That, of course, means that some of the firmware loaded is for a different card is being
> > loaded. I note that processing related to firmware is being changed in the patch. Might my set up be at the root of my
> > problem?
> >
> > I'll have a fiddle an see what I can work out.
> >
> > Chris
> >
> >>
> >> Thanks,
> >> Ben.
> >>
> >>>
>
> Well, my fiddling has got my system rebooting and shutting down successfully again. I found that if I delete the symlink
> to the scrubber firmware, reboot and shutdown work again. There are however, a number of other files in the tu117
> firmware directory tree that that are symlinks to actual files in its tu116 counterpart. So I deleted all of those too.
> Unfortunately, the absence of one or more of those symlinks causes Xorg to fail to start. I've reinstated all the links
> except scrubber and I now have a system that works as it did until I tried to run a kernel that includes the bad commit
> I identified in my bisection. That includes offloading video decoding to the NVidia card, so what ever I read that said
> the scrubber firmware was needed seems to have been wrong. I get a new message that (nouveau 0000:01:00.0: fb: VPR
> locked, but no scrubber binary!), but, hey, we can't have everything.
>
> If you still want to get to the bottom of this, let me know what you need me to provide and I'll do my best. I suspect
> you might want to because there will a n awful lot of Ubuntu-based systems out there with that scrubber.bin symlink in
> place. On the other hand,m it could but quite a while before ubuntu are deploying 6.2 or later kernels.
The symlinks are correct - whole groups of GPUs share the same FW, and
we use symlinks in linux-firmware to represent this.
I don't really have any ideas how/why this patch causes issues with
shutdown - it's a path that only gets executed during initialisation.
Can you try and capture the kernel log during shutdown ("dmesg -w"
over ssh? netconsole?), and see if there's any relevant messages
providing a hint at what's going on? Alternatively, you could try
unloading the module (you will have to stop X/wayland/gdm/etc/etc
first) and seeing if that hangs too.
Ben.
>
> Thanks,
>
> Chris
>
> <snip>
next prev parent reply other threads:[~2023-01-30 23:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 20:59 linux-6.2-rc4+ hangs on poweroff/reboot: Bisected Chris Clayton
2023-01-19 14:33 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-19 16:43 ` Linux kernel regression tracking (#update)
2023-01-27 11:20 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-27 11:35 ` Karol Herbst
2023-01-27 19:41 ` Chris Clayton
2023-01-27 19:46 ` Chris Clayton
2023-01-28 5:42 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-28 11:29 ` Chris Clayton
2023-01-30 1:09 ` Ben Skeggs
2023-01-30 20:19 ` Chris Clayton
2023-01-30 23:09 ` Chris Clayton
2023-01-30 23:27 ` Ben Skeggs [this message]
2023-02-01 13:51 ` Chris Clayton
2023-02-02 20:45 ` Chris Clayton
2023-02-08 8:48 ` Chris Clayton
2023-02-10 18:35 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-10 19:01 ` Karol Herbst
2023-02-10 19:33 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-11 13:38 ` Chris Clayton
2023-02-13 2:57 ` Dave Airlie
2023-02-13 9:14 ` Chris Clayton
2023-02-15 10:36 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-02-15 11:09 ` Karol Herbst
2023-02-18 12:22 ` Chris Clayton
2023-02-18 12:25 ` Karol Herbst
2023-02-18 15:19 ` Chris Clayton
2023-02-18 18:55 ` Chris Clayton
2023-02-20 5:35 ` Ben Skeggs
2023-02-20 10:51 ` Chris Clayton
2023-02-20 11:26 ` Karol Herbst
2023-02-20 22:16 ` Ben Skeggs
2023-03-10 9:26 ` Chris Clayton
2023-03-10 10:20 ` Karol Herbst
2023-03-12 13:30 ` Linux regression tracking (Thorsten Leemhuis)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACAvsv5iYdF3P8AbyrbYo3zGmYRYhxDWn7WbAR5V9qHpbgBXRA@mail.gmail.com \
--to=skeggsb@gmail.com \
--cc=bskeggs@redhat.com \
--cc=chris2553@googlemail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).